usbcore: registered new interface driver uas usbcore: registered new interface driver usb-storage usb-storage 1-4.7.2.2:2.0: USB Mass Storage device detected usb 1-4.7.2.2: Manufacturer: DisplayLink usb 1-4.7.2.2: Product: Mini USB Monitor usb 1-4.7.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 I have UEFI (unsecured) running on the Intel system, and maybe "interface 0" is the EFI partition.Ĭode: usb 1-4.7.2.2: New USB device found, idVendor=17e9, idProduct=0199 (Bus Powered)Given the "partial black box" associated with DisplayLink, I don't know if usbfs is an error at the evdi level or the DisplayLink level, but it appears to be a collision similar to IRQ conflicts. The details of the usb device show an "unrecognized element":Ĭode: Bus 001 Device 013: ID 17e9:0199 DisplayLinkīDeviceClass 0 (Defined at Interface level)īInterfaceClass 255 Vendor Specific Class From my perspective, it appears that their is some sort of "irq-like conflict" with usb-storage meaning DisplayLink DeviceManager_0 is not "smart" to account for previous elements. usb 1-1.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 sr 2:0:0:0: Attached scsi generic sg1 type 5 sr 2:0:0:0: scsi3-mmc drive: 8x/40x writer xa/form2 cdda tray scsi host2: scsi scan: INQUIRY result too short (5), using 36 usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.4: New USB device found, idVendor=0eef, idProduct=0001 usb 1-1.4: new full-speed USB device number 14 using xhci_hcd usb-storage 1-1.2:2.0: USB Mass Storage device detected usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Code: usb 1-1.2: New USB device found, idVendor=17e9, idProduct=0199
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |