![]() |
|
|||||||
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
|
|
#1 | |
|
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. |
|
|
|
|
|
|
#2 |
|
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 |
|
|
|
|
|
#3 | |
|
Junior Member
Join Date: Feb 2018
Posts: 8
|
Quote:
|
|
|
|
|
|
|
#4 |
|
Senior Member
Join Date: Feb 2010
Posts: 386
|
No, they should be fine together. The rule for setting the bConfigurationValue should only fire for devices which have configuration 2 by default, and it'd switch them to 1, allowing udl to see it - this would apply for DL-1x5.
The udev rule that we install for evdi (that starts DLM) is specific enough that it should not match old devices. Cheers, Michal |
|
|
|
![]() |
| Tags |
| debian, error messages, linux, linux problems, usbfs |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|