Debian ERROR:: usb 1-1.2: usbfs: interface 0 claimed by usb-storage while 'DeviceMana
1 Attachment(s)
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 Code:
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 The details of the usb device show an "unrecognized element": Code:
Bus 001 Device 013: ID 17e9:0199 DisplayLink I have UEFI (unsecured) running on the Intel system, and maybe "interface 0" is the EFI partition. Code:
fdisk -l 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 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: |
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 Code:
Bus 001 Device 009: ID 17e9:0199 DisplayLink |
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 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. |
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 |
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. |
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 |
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 |
Quote:
|
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 Code:
vim /usr/bin/dlconfig 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. |
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 |
All times are GMT. The time now is 11:53 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.