|
|
Thread Tools | Search this Thread | Display Modes |
03-01-2018, 02:25 AM | #1 |
Junior Member
Join Date: Feb 2018
Posts: 8
|
Debian ERROR:: usb 1-1.2: usbfs: interface 0 claimed by usb-storage while 'DeviceMana
Hi, I followed the instructions to install the necessary elements for DisplayLink and evdi on Debian
Code:
Linux ats 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64 Code:
NUC6CAYH. I get the service dlm to start, but it doesn't recognize the second device with Code:
xrandr --listproviders Code:
# mokutil --sb-state SecureBoot disabled Code:
[ 305.820086] usb 1-1.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 [ 306.814074] usb 1-1.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 ... I decided to unplug and plug-in the monitor (Xenarc 708TSU: https://www.xenarcdirect.com/708TSU.html with eGalax touch drivers) which loads as a "usb-storage" deviceClass and then the flooding error returns Code:
[ 241.005037] usb 1-1.2: New USB device found, idVendor=17e9, idProduct=0199 [ 241.005044] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 241.005048] usb 1-1.2: Product: Mini USB Monitor [ 241.005052] usb 1-1.2: Manufacturer: DisplayLink [ 241.005055] usb 1-1.2: SerialNumber: 100179 [ 241.013017] usb-storage 1-1.2:2.0: USB Mass Storage device detected [ 241.014100] scsi host2: usb-storage 1-1.2:2.0 [ 241.098143] usb 1-1.4: new full-speed USB device number 14 using xhci_hcd [ 241.220893] usb 1-1.4: New USB device found, idVendor=0eef, idProduct=0001 [ 241.220901] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 241.220905] usb 1-1.4: Product: USB TouchController [ 241.220909] usb 1-1.4: Manufacturer: eGalax Inc. [ 241.224900] input: eGalax Inc. USB TouchController as /devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:0EEF:0001.0008/input/input24 [ 241.225832] input: eGalax Inc. USB TouchController as /devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:0EEF:0001.0008/input/input25 [ 241.226457] hid-generic 0003:0EEF:0001.0008: input,hidraw0: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-0000:00:15.0-1.4/input0 [ 242.027122] scsi host2: scsi scan: INQUIRY result too short (5), using 36 [ 242.027135] scsi 2:0:0:0: CD-ROM PQ: 0 ANSI: 0 [ 242.028527] sr 2:0:0:0: [sr0] scsi3-mmc drive: 8x/40x writer xa/form2 cdda tray [ 242.028911] sr 2:0:0:0: Attached scsi CD-ROM sr0 [ 242.029191] sr 2:0:0:0: Attached scsi generic sg1 type 5 [ 305.820086] usb 1-1.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 [ 306.814074] usb 1-1.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 [ 307.820878] usb 1-1.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 ... The details of the usb device show an "unrecognized element": Code:
Bus 001 Device 013: ID 17e9:0199 DisplayLink Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x17e9 DisplayLink idProduct 0x0199 bcdDevice 1.36 iManufacturer 1 DisplayLink iProduct 2 Mini USB Monitor iSerial 3 100179 bNumConfigurations 2 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 2 iConfiguration 1 DisplayLink bmAttributes 0xc0 Self Powered MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 66 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 1b 5f 01 00 19 05 00 01 03 00 04 04 01 00 03 d0 00 02 04 00 bd 1f 00 01 04 01 02 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x0a EP 10 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 2 Device Status: 0x0000 (Bus Powered) I have UEFI (unsecured) running on the Intel system, and maybe "interface 0" is the EFI partition. Code:
fdisk -l Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 6895FA57-00ED-4EEA-90E3-F083259BFE0E Device Start End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 217974783 216924160 103.4G Linux filesystem /dev/sda3 217974784 234440703 16465920 7.9G Linux swap Defining the device as "bInterfaceClass 8 Mass Storage" seems odd to me and is possibly linked to the "claimed by usb-storage" component of the error. In the end, the software is installed, appears to run as expected, but because of this flooding message Code:
[ 359.142245] usb 1-1.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 [ 360.148960] usb 1-1.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 ... As a result, I believe the xrandr never sees the new device as a monitor. Thoughts? ats_2018-02-28T06%3A33%3A46.461726.zip http://md5.mshaffer.com/ats_2018-02-...:46.461726.zip [sidebar note: The error file within the zip is trying to report to /var/crash which doesn't exist... I would suggest either updating the crash location to maybe /var/log/displaylink/crash/ or create the folder with a symlink to /var/crash ... this path seems to be a RHEL type structure which is odd] monte {x: |
03-06-2018, 06:27 PM | #2 |
Junior Member
Join Date: Feb 2018
Posts: 8
|
I reinstalled with Legacy BIOS to see if UEFI did anything... same errors.
Of note, the detection of the device as "usb-storage" or "uas" - this seems to be the fundamental problem. From DMESG. Code:
[ 3.223077] usb 1-4.7.2.2: New USB device found, idVendor=17e9, idProduct=0199 [ 3.223081] usb 1-4.7.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3.223082] usb 1-4.7.2.2: Product: Mini USB Monitor [ 3.223084] usb 1-4.7.2.2: Manufacturer: DisplayLink [ 3.223085] usb 1-4.7.2.2: SerialNumber: 100144 [ 3.243460] usb-storage 1-4.7.2.2:2.0: USB Mass Storage device detected [ 3.243773] scsi host2: usb-storage 1-4.7.2.2:2.0 [ 3.244106] usbcore: registered new interface driver usb-storage [ 3.245774] usbcore: registered new interface driver uas [ 3.309859] usb 1-4.7.2.4: new full-speed USB device number 10 using xhci_hcd [ 3.415940] usb 1-4.7.2.4: New USB device found, idVendor=0eef, idProduct=0001 [ 3.415945] usb 1-4.7.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.415948] usb 1-4.7.2.4: Product: USB TouchController [ 3.415950] usb 1-4.7.2.4: Manufacturer: eGalax Inc. [ 3.418955] input: eGalax Inc. USB TouchController as /devices/pci0000:00/0000:00:15.0/usb1/1-4/1-4.7/1-4.7.2/1-4.7.2.4/1-4.7.2.4:1.0/0003:0EEF:0001.0004/input/input19 [ 3.419332] input: eGalax Inc. USB TouchController as /devices/pci0000:00/0000:00:15.0/usb1/1-4/1-4.7/1-4.7.2/1-4.7.2.4/1-4.7.2.4:1.0/0003:0EEF:0001.0004/input/input20 [ 3.419583] hid-generic 0003:0EEF:0001.0004: input,hidraw3: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-0000:00:15.0-4.7.2.4/input0 [ 3.432054] usbcore: registered new interface driver usbtouchscreen [ 3.578719] evdi: loading out-of-tree module taints kernel. [ 3.580727] evdi: [I] Initialising logging on level 5 [ 3.580729] evdi: [I] Atomic driver:no [ 3.650168] usb 1-4.7.2.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 [ 3.902464] [drm] RC6 on [ 4.254469] scsi host2: scsi scan: INQUIRY result too short (5), using 36 [ 4.254475] scsi 2:0:0:0: CD-ROM PQ: 0 ANSI: 0 [ 4.254991] scsi 2:0:0:0: Attached scsi generic sg1 type 5 [ 4.263376] sr 2:0:0:0: [sr0] scsi3-mmc drive: 8x/40x writer xa/form2 cdda tray [ 4.263379] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 4.263784] sr 2:0:0:0: Attached scsi CD-ROM sr0 [ 4.281204] xhci_hcd 0000:00:15.0: WARN Event TRB for slot 8 ep 8 with no TDs queued? [ 4.644348] usb 1-4.7.2.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 [ 5.649379] usb 1-4.7.2.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 [ 6.654684] usb 1-4.7.2.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 [ 7.661063] usb 1-4.7.2.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 Code:
Bus 001 Device 009: ID 17e9:0199 DisplayLink Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x17e9 DisplayLink idProduct 0x0199 bcdDevice 1.36 iManufacturer 1 DisplayLink iProduct 2 Mini USB Monitor iSerial 3 100144 bNumConfigurations 2 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 2 iConfiguration 1 DisplayLink bmAttributes 0xc0 Self Powered MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 66 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 1b 5f 01 00 19 05 00 01 03 00 04 04 01 00 03 d0 00 02 04 00 bd 1f 00 01 04 01 02 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x0a EP 10 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 2 Device Status: 0x0000 (Bus Powered) |
03-08-2018, 02:35 PM | #3 |
Junior Member
Join Date: Feb 2018
Posts: 8
|
Linux Mint
So I tried the same instructions on Linux Mint.
Here is a fresh install without any display-link drivers: Code:
[ 3.681825] usb 1-4.7.2.2: new high-speed USB device number 9 using xhci_hcd [ 3.786614] usb 1-4.7.2.2: New USB device found, idVendor=17e9, idProduct=0199 [ 3.786616] usb 1-4.7.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3.786618] usb 1-4.7.2.2: Product: Mini USB Monitor [ 3.786620] usb 1-4.7.2.2: Manufacturer: DisplayLink [ 3.786621] usb 1-4.7.2.2: SerialNumber: 100144 [ 3.893839] usb 1-4.7.2.4: new full-speed USB device number 10 using xhci_hcd [ 3.949002] lp: driver loaded but no devices found [ 3.956310] ppdev: user-space parallel port driver [ 3.999260] usb 1-4.7.2.4: New USB device found, idVendor=0eef, idProduct=0001 [ 3.999263] usb 1-4.7.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.999265] usb 1-4.7.2.4: Product: USB TouchController [ 3.999267] usb 1-4.7.2.4: Manufacturer: eGalax Inc. [ 4.002637] input: eGalax Inc. USB TouchController as /devices/pci0000:00/0000:00:15.0/usb1/1-4/1-4.7/1-4.7.2/1-4.7.2.4/1-4.7.2.4:1.0/0003:0EEF:0001.0004/input/input10 [ 4.002792] input: eGalax Inc. USB TouchController as /devices/pci0000:00/0000:00:15.0/usb1/1-4/1-4.7/1-4.7.2/1-4.7.2.4/1-4.7.2.4:1.0/0003:0EEF:0001.0004/input/input11 [ 4.002946] hid-generic 0003:0EEF:0001.0004: input,hidraw3: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-0000:00:15.0-4.7.2.4/input0 [ 4.080488] usbcore: registered new interface driver usbtouchscreen [ 4.607476] usb-storage 1-4.7.2.2:2.0: USB Mass Storage device detected [ 4.617295] scsi host2: usb-storage 1-4.7.2.2:2.0 [ 4.619445] usbcore: registered new interface driver usb-storage [ 4.628264] usbcore: registered new interface driver uas Notice the usb is first recognized as DisplayLink [1-4.7.2.2] and then later, within that USB chain, it recognizes a storage device [1-4.7.2.2:2.0] ... I believe that is the core of the main error. How to fix? After installing driver ... Code:
[ 7810.940999] evdi: loading out-of-tree module taints kernel. [ 7810.941100] evdi: module verification failed: signature and/or required key missing - tainting kernel [ 7810.943360] evdi: [I] Initialising logging on level 5 [ 7810.943362] evdi: [I] Atomic driver:no [ 7810.991826] usb 1-4.7.2.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 [ 7811.217607] xhci_hcd 0000:00:15.0: WARN Event TRB for slot 8 ep 8 with no TDs queued? [ 7811.338902] xhci_hcd 0000:00:15.0: WARN Event TRB for slot 8 ep 8 with no TDs queued? [ 7811.971245] usb 1-4.7.2.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 [ 7812.975663] usb 1-4.7.2.2: usbfs: interface 0 claimed by usb-storage while 'DeviceManager_0' sets config #1 Last edited by mshaffer; 03-08-2018 at 02:38 PM. |
03-09-2018, 07:51 AM | #4 |
Senior Member
Join Date: Feb 2010
Posts: 386
|
This device uses an older, DL-1x5 chip. You should not install DisplayLink driver for it, they are driven by kernel inbox "udl" module.
Some DL-1x5 devices have multiple USB configurations, and they come up in configuration 2 by default which is mass-storage - this way Windows could see them as disk with drivers. The Windows software, once installed switched such devices to configuration 1. So, if you switch the device to configuration 1 manually, udl driver should pick it up. This can be also automated with udev rules, see https://libdlo.freedesktop.org/wiki/DeviceQuirks/ for inspiration and more detailed explanation. Thanks, Michal Last edited by mlukaszek; 03-09-2018 at 01:19 PM. |
03-09-2018, 01:15 PM | #5 | |
Junior Member
Join Date: Feb 2018
Posts: 8
|
Quote:
Indeed the Xenarck is DL-165. I will try and follow udev rules: https://libdlo.freedesktop.org/wiki/DeviceQuirks/ To be clear: I don't install an DisplayLink driver and use built-in utilities associated with libdlo (libusb-dev) I then hack the udev rules to get config#1 to match correctly? Thanks for the reply I will give it a whirl. |
|
03-09-2018, 01:21 PM | #6 |
Senior Member
Join Date: Feb 2010
Posts: 386
|
You don't need any other utilities. udl is a kernel space driver for DL-1x5 that does not need anything extra in userspace to expose a /dev/dri/cardX (DRM) node that can be then used by X modesetting driver or anything else using libdrm.
Cheers, Michal |
03-09-2018, 02:06 PM | #7 | |
Junior Member
Join Date: Feb 2018
Posts: 8
|
Quote:
** UNRECOGNIZED: 1b 5f 01 00 19 05 00 01 03 00 04 04 01 00 03 d0 00 02 04 00 bd 1f 00 01 04 01 02 Code:
Bus 001 Device 009: ID 17e9:0199 DisplayLink Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x17e9 DisplayLink idProduct 0x0199 bcdDevice 1.36 iManufacturer 1 DisplayLink iProduct 2 Mini USB Monitor iSerial 3 100144 bNumConfigurations 2 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 2 iConfiguration 1 DisplayLink bmAttributes 0xc0 Self Powered MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 66 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 1b 5f 01 00 19 05 00 01 03 00 04 04 01 00 03 d0 00 02 04 00 bd 1f 00 01 04 01 02 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x0a EP 10 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 bNumConfigurations 2 Device Status: 0x0000 (Bus Powered) |
|
03-09-2018, 02:16 PM | #8 |
Junior Member
Join Date: Feb 2018
Posts: 8
|
From the OS alone, how can we identify which version of DL-1x5, DL-3xxx, DL-5xxx we have. Is it recorded in the USB description. If so, what element?
|
03-12-2018, 12:27 AM | #9 | |
Junior Member
Join Date: Feb 2018
Posts: 8
|
Quote:
I am trying to follow your limited instructions. The link you provided has a lot of broken links. Create Rule Code:
#vim /etc/udev/rules.d/60-displaylink.rules # DisplayLink devices always have the active configuration on configuration #1 SYSFS{idVendor}=="17e9", SYSFS{bConfigurationValue}=="2", RUN+="/usr/bin/dlconfig /sys%p/bConfigurationValue" Code:
vim /usr/bin/dlconfig #! /bin/bash if [ -e /sys$1/device/bConfigurationValue ]; then echo 1 > /sys$1/device/bConfigurationValue fi; if [ -e /sys$1/bConfigurationValue ]; then echo 1 > /sys$1/bConfigurationValue fi; Code:
udevadm control --reload-rules && udevadm trigger Do I need dlm? how to start/stop? will it start show up in xrandr ... I am looking for a step-by-step solution if you can provide it... Thanks. |
|
03-12-2018, 10:31 AM | #10 |
Senior Member
Join Date: Feb 2010
Posts: 386
|
The driver we release for Linux only supports devices using newer chips than DL-1x5. As our release note states, support for older devices is provided by the Linux kernel community.
If you have the right udev rule around that echoes 1 to the bConfigurationValue of the usb device in sysfs, then after replugging the device udl should see your device and you should see evidence of it in your dmesg log. Cheers, Michal |
Tags |
debian, error messages, linux, linux problems, usbfs |
|
|