Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

1 votes
1 answers
4898 views
How to install DisplayLink driver on LinuxMint 17.3
I have a USB 3.0 docking station connected with my laptop having LinuxMint 17.3. I can't manage to install DisplayLink driver on it. I could make it work with Ubuntu 15.04, but with LinuxMint it wan't recognize external monitor, even though there is no error message during the install procedure. I t...
I have a USB 3.0 docking station connected with my laptop having LinuxMint 17.3. I can't manage to install DisplayLink driver on it. I could make it work with Ubuntu 15.04, but with LinuxMint it wan't recognize external monitor, even though there is no error message during the install procedure. I tried to follow some proposal on DisplayLink forum , and I tried to modify installation file so SYSTEMINITDAEMON had systemd or upstart values, but none of these worked. Since I already found some posts reported it worked for LinuxMint 17.2, I guess it's possible, but I couldn't find exact instructions if something else should be changed in installation script.
zoran jeremic (111 rep)
Jan 22, 2016, 07:48 PM • Last activity: Jul 14, 2025, 11:12 PM
0 votes
0 answers
71 views
External Monitor Not Working via DisplayLink (JUA365) on Fedora 42
I’m running Fedora 42 installed on an external NVMe (2TB) drive connected to my MacBook Pro (Early 2015). My system setup is as follows: CPU: Intel i7 (Broadwell, MacBook Pro) Graphics: Intel Iris 6100 Fedora Version: Fedora 42 (Workstation) Display Adapter: JUA365 - USB™ 3.0 to Dual HDMI™ Multi-Mon...
I’m running Fedora 42 installed on an external NVMe (2TB) drive connected to my MacBook Pro (Early 2015). My system setup is as follows: CPU: Intel i7 (Broadwell, MacBook Pro) Graphics: Intel Iris 6100 Fedora Version: Fedora 42 (Workstation) Display Adapter: JUA365 - USB™ 3.0 to Dual HDMI™ Multi-Monitor Adapter (DisplayLink based) DisplayLink Driver: Installed EVDI module: Loaded Secure Boot: Disabled DisplayLink service: Running fine Everything seems installed properly — but the external monitor still doesn’t turn on or get detected. I've tried: Manually restarting displaylink-driver.service Reinstalling EVDI via DKMS Reconnecting and powering monitor Verified logs (journalctl) — no clear errors I’m wondering if anyone using JUA365 or similar DisplayLink adapters has encountered and solved this issue on Fedora 41/42? Is there a known issue with DisplayLink adapters (like JUA365) on Fedora 42? Could this be a missing udev rule or a permissions/device node creation issue? Anyone using a similar setup successfully? Any tips, logs to check, or workarounds would be greatly appreciated. Thanks in advance!
Mr.Simple (1 rep)
Jun 30, 2025, 03:53 PM • Last activity: Jun 30, 2025, 04:34 PM
0 votes
0 answers
38 views
DisplayLink USB device flooding dmesg with "reset high-speed USB device"
System: Ubuntu 24.04 Kernel 6.11.0-25-generic Lenovo Thinkpad P1 Gen 3 Asus MB166B (the source of the messages) I get the message *reset high-speed USB device number ## using xhci_hcd* approximately once per second. The actual display is working fine with no visible indication that something is wron...
System: Ubuntu 24.04 Kernel 6.11.0-25-generic Lenovo Thinkpad P1 Gen 3 Asus MB166B (the source of the messages) I get the message *reset high-speed USB device number ## using xhci_hcd* approximately once per second. The actual display is working fine with no visible indication that something is wrong. The only reason I noticed it is that an unrelated issue had me looking at messages. Issue persists on both onboard USB2.0 ports, I don't have a dock/powered hub handy to test on. Log below starts with plugging the device in:
[  +6.712272] usb 1-1: new high-speed USB device number 17 using xhci_hcd
[  +0.128517] usb 1-1: New USB device found, idVendor=2109, idProduct=2817, bcdDevice=90.63
[  +0.000017] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000006] usb 1-1: Product: USB2.0 Hub             
[  +0.000006] usb 1-1: Manufacturer: VIA Labs, Inc.         
[  +0.000004] usb 1-1: SerialNumber: 000000000
[  +0.001873] hub 1-1:1.0: USB hub found
[  +0.000200] hub 1-1:1.0: 5 ports detected
[  +0.123112] usb 2-1: new SuperSpeed USB device number 12 using xhci_hcd
[  +0.040264] usb 2-1: New USB device found, idVendor=2109, idProduct=0817, bcdDevice=90.63
[  +0.000016] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000008] usb 2-1: Product: USB3.0 Hub             
[  +0.000005] usb 2-1: Manufacturer: VIA Labs, Inc.         
[  +0.000005] usb 2-1: SerialNumber: 000000000
[  +0.002157] hub 2-1:1.0: USB hub found
[  +0.000340] hub 2-1:1.0: 4 ports detected
[  +0.352781] [UFW BLOCK] IN=wlp0s20f3 OUT= MAC= SRC=192.168.88.15 DST=239.255.255.250 LEN=635 TOS=0x00 PREC=0x00 TTL=1 ID=8665 DF PROTO=UDP SPT=37455 DPT=3702 LEN=615 
[  +0.125527] usb 1-1.5: new high-speed USB device number 18 using xhci_hcd
[  +0.077666] usb 1-1.5: New USB device found, idVendor=2109, idProduct=8888, bcdDevice= 0.01
[  +0.000017] usb 1-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  +0.003396] hid-generic 0003:2109:8888.0017: ignoring exceeding usage max
[  +0.002481] input: HID 2109:8888 as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.5/1-1.5:1.0/0003:2109:8888.0017/input/input62
[  +0.080831] hid-generic 0003:2109:8888.0017: input,hidraw4: USB HID v1.10 Keyboard [HID 2109:8888] on usb-0000:00:14.0-1.5/input0
[  +0.001304] hid-generic 0003:2109:8888.0018: ignoring exceeding usage max
[  +0.003104] input: HID 2109:8888 Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.5/1-1.5:1.1/0003:2109:8888.0018/input/input63
[  +0.051646] input: HID 2109:8888 System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.5/1-1.5:1.1/0003:2109:8888.0018/input/input64
[  +0.000364] hid-generic 0003:2109:8888.0018: input,hidraw5: USB HID v1.10 Device [HID 2109:8888] on usb-0000:00:14.0-1.5/input1
[  +0.154186] usb 2-1.1: new SuperSpeed USB device number 13 using xhci_hcd
[  +0.012786] usb 2-1.1: New USB device found, idVendor=17e9, idProduct=ff0e, bcdDevice=30.19
[  +0.000007] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000003] usb 2-1.1: Product: MB166B
[  +0.000002] usb 2-1.1: Manufacturer: DisplayLink
[  +0.000001] usb 2-1.1: SerialNumber: 5959595M9595
[  +1.839833] usb 1-1.5: reset high-speed USB device number 18 using xhci_hcd
[  +1.408020] usb 1-1.5: reset high-speed USB device number 18 using xhci_hcd
[  +1.407799] usb 1-1.5: reset high-speed USB device number 18 using xhci_hcd
[  +0.868799] evdi: [I] (card4) Opened by Task 42965 (DisplayLinkMana) of process 42937 (DisplayLinkMana)
[  +0.000712] evdi: [I] (card4) Added i2c adapter bus number 10
[  +0.000003] evdi: [I] (card4) Connected with Task 42949 (DisplayLinkMana) of process 42937 (DisplayLinkMana)
[  +0.000003] evdi: [I] (card4) Connector state: connected
[  +0.066899] evdi: [I] (card4) Connector state: connected
[  +0.000051] evdi: [I] (card4) Edid property set
[  +0.000108] evdi: [I] (card4) Connector state: connected
[  +0.000035] evdi: [I] (card4) Edid property set
[  +0.095260] evdi: [W] evdi_gem_mmap:411 Don't allow imported objects to be mapped: owner: i915
[  +0.000054] evdi: [I] (card4) Notifying display power state: on
[  +0.000007] evdi: [I] (card4) Notifying mode changed: 1920x1080@60; bpp 32; pixel format XR24 little-endian (0x34325258)
[  +0.000004] evdi: [I] (card4) Notifying display power state: on
[  +0.018939] evdi: [W] evdi_painter_connect:900 (card4) Double connect - replacing 00000000df79fc64 with 00000000df79fc64
[  +0.000006] evdi: [I] (card4) Connected with Task 42960 (DisplayLinkMana) of process 42937 (DisplayLinkMana)
[  +0.000002] evdi: [I] (card4) Connector state: connected
[  +0.002838] evdi: [I] (card4) Notifying mode changed: 1920x1080@60; bpp 32; pixel format XR24 little-endian (0x34325258)
[  +0.000005] evdi: [I] (card4) Notifying display power state: on
[  +0.082424] evdi: [I] (card4) Connector state: connected
[  +0.000051] evdi: [I] (card4) Edid property set
[  +0.271481] usb 1-1.5: reset high-speed USB device number 18 using xhci_hcd
[ and so on…] usb 1-1.5: reset high-speed USB device number 18 using xhci_hcd
[ and so on…] usb 1-1.5: reset high-speed USB device number 18 using xhci_hcd
I'll add that I did see the 2014 question with a similar title , but that appears to be specific to one mouse and this is... isn't.
ASTX813 (186 rep)
May 20, 2025, 03:26 PM
0 votes
0 answers
56 views
monitor is unknown
I installed a additional touchscreen to my laptop over displaylink. The screen itself works fine. But the vendor / model / serialno is set to "unknown". I need these value to map the touchscreen to the monitor. How can I name the display correct? EDID seems to be correct. hwinfo --monitor shows corr...
I installed a additional touchscreen to my laptop over displaylink. The screen itself works fine. But the vendor / model / serialno is set to "unknown". I need these value to map the touchscreen to the monitor. How can I name the display correct? EDID seems to be correct. hwinfo --monitor shows correct data. .config/monitor.xml is unknown. I'm running Fedora 40 / gnome 46 / wayland
mxsteini (1 rep)
Oct 22, 2024, 08:02 PM
0 votes
0 answers
19 views
Display Vendor, Product and Serialnumber unknown
I installed my new TETRA split keyboard. https://www.kickstarter.com/projects/747287659/tetra-keyboard-split-touch-type Keyboard and display works fine. But I cannot map the touch event to the display because it is not recogniced. ``` 3099 2160 1 DP-9 unknown unknown unknown 1280 800 60.004 ``` I'm...
I installed my new TETRA split keyboard. https://www.kickstarter.com/projects/747287659/tetra-keyboard-split-touch-type Keyboard and display works fine. But I cannot map the touch event to the display because it is not recogniced.
3099
      2160
      1
      
        
          DP-9
          unknown
          unknown
          unknown
        
        
          1280
          800
          60.004
I'm running Fedora 40 / Gnome 46 / wayland. The display is connected via displaylink on usb-c.
Michael Stein (1 rep)
Oct 18, 2024, 05:36 PM
3 votes
1 answers
909 views
displaylink-driver not installable with 6.1.0-25-amd64 kernel
Is there a fix I can do on my system? Should I file a bug evdi or another bug tracking of a package? The last kernel update failed. I had to remove the `evdi` package. Thereafter the update succeeded. I need evdi for [displaylink-driver package][1] to use a docking station. When trying to install `d...
Is there a fix I can do on my system? Should I file a bug evdi or another bug tracking of a package? The last kernel update failed. I had to remove the evdi package. Thereafter the update succeeded. I need evdi for displaylink-driver package to use a docking station. When trying to install displaylink-driver I get below terminal output with a postprocess error having exit code 10. The mentioned make.log is here . There are not many options for me to get the docking station to work. One bug filed for pop os seems to address this, however, unanswered. It is not the first time I install this package, so one comment in the release note pointing to uefi sec workaround should not bother me. However, tried it, and failed, because I cannot install evdi package. The evdi bug tracker has one issue with post installation return code 10 , however, this one is old and refers to older kernel. With the kernkel 6.1.0-24-amd64 kernel it worked before.
# apt install displaylink-driver
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  linux-headers-6.1.0-21-common
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  evdi
Suggested packages:
  update-notifier-common
The following NEW packages will be installed:
  displaylink-driver evdi
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/6,905 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Selecting previously unselected package evdi.
(Reading database ... 268277 files and directories currently installed.)
Preparing to unpack .../evdi_1.14.6-100_amd64.deb ...
Unpacking evdi (1.14.6-100) ...
Selecting previously unselected package displaylink-driver.
Preparing to unpack .../displaylink-driver_6.0.0-24_amd64.deb ...
Unpacking displaylink-driver (6.0.0-24) ...
Setting up evdi (1.14.6-100) ...
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Creating symlink /var/lib/dkms/evdi/1.14.6/source -> /usr/src/evdi-1.14.6

Building module:
Cleaning build area...
make -j16 KERNELRELEASE=6.1.0-25-amd64 all INCLUDEDIR=/lib/modules/6.1.0-25-amd64/build/include KVERSION=6.1.0-25-amd64 DKMS_BUILD=1...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.0-25-amd64 (x86_64)
Consult /var/lib/dkms/evdi/1.14.6/build/make.log for more information.
dpkg: error processing package evdi (--configure):
 installed evdi package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of displaylink-driver:
 displaylink-driver depends on evdi (>= 1.14.4); however:
  Package evdi is not configured yet.
 displaylink-driver depends on evdi (<< 1.15.0); however:
  Package evdi is not configured yet.

dpkg: error processing package displaylink-driver (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 evdi
 displaylink-driver
E: Sub-process /usr/bin/dpkg returned an error code (1)
Regarding Stephen Kitts question:
$ cat synaptics.list 
deb [signed-by=/usr/share/keyrings/synaptics-repository-keyring.gpg] https://www.synaptics.com/sites/default/files/Ubuntu/  stable main
deb [signed-by=/usr/share/keyrings/synaptics-repository-keyring.gpg] https://www.synaptics.com/sites/default/files/Ubuntu/  stable non-free
Stefan Bollmann (249 rep)
Sep 29, 2024, 07:53 AM • Last activity: Sep 29, 2024, 09:57 AM
0 votes
0 answers
51 views
Using xorg.conf creating 2 x servers?
So I have 2 displaylink displays, each shows as a framebuffer device, fb0, and fb1. I am using raspberry pi os, and it will show on one display, but the other is blank, however if I move the cursor over, it shows as an x, which I think indicates it is a blank xserver. I have tried all sorts of diffe...
So I have 2 displaylink displays, each shows as a framebuffer device, fb0, and fb1. I am using raspberry pi os, and it will show on one display, but the other is blank, however if I move the cursor over, it shows as an x, which I think indicates it is a blank xserver. I have tried all sorts of different xorg.conf variations, and tried to enable xinemera which does nothing and does not appear at all in the log when enabled. I can address each display using DISPLAY=:0.1 or 0, and lets me open apps. if I use DISPLAY=0.1 xrandr I get details on one of the displays, but they seem separate. my xorg.conf: Section "Device" Identifier "FBDEV 0" Driver "fbdev" Option "fbdev" "/dev/fb0" EndSection Section "Device" Identifier "FBDEV 1" Driver "fbdev" Option "fbdev" "/dev/fb1" EndSection Section "Monitor" Identifier "Monitor0" EndSection Section "Monitor" Identifier "Monitor1" EndSection Section "Screen" Identifier "DL1" Device "FBDEV 0" Monitor "Monitor0" EndSection Section "Screen" Identifier "DL2" Device "FBDEV 1" Monitor "Monitor1" EndSection Section "ServerLayout" Identifier "Default Layout" Screen 0 "DL1" 0 0 Screen 1 "DL2" RightOf "DL1" Option "Xinemera" "on" EndSection and the corresponding log file: X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 [ 634.407] Build Operating System: linux Raspbian [ 634.407] Current Operating System: Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 [ 634.407] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=E4:5F:01:AF:76:E0 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=84c4adaf-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [ 634.408] Build Date: 29 April 2024 03:20:14PM [ 634.408] xorg-server 2:1.20.11-1+rpt3+deb11u13 (https://www.debian.org/support) [ 634.408] Current version of pixman: 0.40.0 [ 634.408] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 634.408] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 634.408] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 15 14:47:23 2024 [ 634.409] (==) Using config file: "/etc/X11/xorg.conf" [ 634.409] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 634.409] (==) ServerLayout "Default Layout" [ 634.409] (**) |-->Screen "DL1" (0) [ 634.409] (**) | |-->Monitor "Monitor0" [ 634.410] (**) | |-->Device "FBDEV 0" [ 634.410] (**) |-->Screen "DL2" (1) [ 634.410] (**) | |-->Monitor "Monitor1" [ 634.411] (**) | |-->Device "FBDEV 1" [ 634.412] (**) Option "Debug" "dmabuf_capable" [ 634.412] (==) Automatically adding devices [ 634.412] (==) Automatically enabling devices [ 634.412] (==) Automatically adding GPU devices [ 634.412] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 634.412] (WW) The directory "/usr/share/fonts/X11/misc" does not exist. [ 634.412] Entry deleted from font path. [ 634.412] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 634.412] Entry deleted from font path. [ 634.412] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 634.412] Entry deleted from font path. [ 634.412] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 634.412] Entry deleted from font path. [ 634.412] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [ 634.412] Entry deleted from font path. [ 634.412] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 634.412] Entry deleted from font path. [ 634.412] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 634.412] Entry deleted from font path. [ 634.412] (==) FontPath set to: built-ins [ 634.412] (==) ModulePath set to "/usr/lib/xorg/modules" [ 634.412] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 634.413] (II) Loader magic: 0x20cf40 [ 634.413] (II) Module ABI versions: [ 634.413] X.Org ANSI C Emulation: 0.4 [ 634.413] X.Org Video Driver: 24.1 [ 634.413] X.Org XInput driver : 24.1 [ 634.413] X.Org Server Extension : 10.0 [ 634.415] (++) using VT number 7 [ 634.415] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 634.419] (II) xfree86: Adding drm device (/dev/dri/card1) [ 634.420] (II) xfree86: Adding drm device (/dev/dri/card0) [ 634.421] (II) no primary bus or device found [ 634.421] falling back to /sys/devices/platform/gpu/drm/card1 [ 634.421] (II) LoadModule: "glx" [ 634.421] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 634.425] (II) Module glx: vendor="X.Org Foundation" [ 634.425] compiled for 1.20.11, module version = 1.0.0 [ 634.425] ABI class: X.Org Server Extension, version 10.0 [ 634.425] (II) LoadModule: "fbdev" [ 634.425] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 634.426] (II) Module fbdev: vendor="X.Org Foundation" [ 634.426] compiled for 1.20.3, module version = 0.5.0 [ 634.426] Module class: X.Org Video Driver [ 634.426] ABI class: X.Org Video Driver, version 24.0 [ 634.426] (II) FBDEV: driver for framebuffer: fbdev [ 634.426] (WW) Falling back to old probe method for fbdev [ 634.426] (II) Loading sub module "fbdevhw" [ 634.426] (II) LoadModule: "fbdevhw" [ 634.426] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 634.427] (II) Module fbdevhw: vendor="X.Org Foundation" [ 634.427] compiled for 1.20.11, module version = 0.0.2 [ 634.427] ABI class: X.Org Video Driver, version 24.1 [ 634.427] (II) FBDEV(0): using /dev/fb0 [ 634.427] (II) FBDEV(1): using /dev/fb1 [ 634.427] (II) FBDEV(0): Creating default Display subsection in Screen section "DL1" for depth/fbbpp 16/16 [ 634.427] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16 [ 634.428] (==) FBDEV(0): RGB weight 565 [ 634.428] (==) FBDEV(0): Default visual is TrueColor [ 634.428] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) [ 634.428] (II) FBDEV(0): hardware: udlfb (video memory: 676kB) [ 634.428] (DB) xf86MergeOutputClassOptions unsupported bus type 0 [ 634.428] (**) FBDEV(0): Option "fbdev" "/dev/fb0" [ 634.428] (II) FBDEV(0): checking modes against framebuffer device... [ 634.428] (II) FBDEV(0): checking modes against monitor... [ 634.428] (II) FBDEV(0): Virtual size is 1440x240 (pitch 1440) [ 634.428] (**) FBDEV(0): Built-in mode "current": 27.0 MHz, 15.1 kHz, 57.9 Hz [ 634.428] (II) FBDEV(0): Modeline "current"x0.0 27.00 1440 1770 1774 1792 240 254 256 260 -hsync +vsync -csync (15.1 kHz b) [ 634.428] (==) FBDEV(0): DPI set to (96, 96) [ 634.428] (II) Loading sub module "fb" [ 634.428] (II) LoadModule: "fb" [ 634.429] (II) Loading /usr/lib/xorg/modules/libfb.so [ 634.429] (II) Module fb: vendor="X.Org Foundation" [ 634.429] compiled for 1.20.11, module version = 1.0.0 [ 634.429] ABI class: X.Org ANSI C Emulation, version 0.4 [ 634.429] (**) FBDEV(0): using shadow framebuffer [ 634.429] (II) Loading sub module "shadow" [ 634.429] (II) LoadModule: "shadow" [ 634.430] (II) Loading /usr/lib/xorg/modules/libshadow.so [ 634.430] (II) Module shadow: vendor="X.Org Foundation" [ 634.430] compiled for 1.20.11, module version = 1.1.0 [ 634.430] ABI class: X.Org ANSI C Emulation, version 0.4 [ 634.430] (II) FBDEV(1): Creating default Display subsection in Screen section "DL2" for depth/fbbpp 16/16 [ 634.430] (==) FBDEV(1): Depth 16, (==) framebuffer bpp 16 [ 634.430] (==) FBDEV(1): RGB weight 565 [ 634.430] (==) FBDEV(1): Default visual is TrueColor [ 634.430] (==) FBDEV(1): Using gamma correction (1.0, 1.0, 1.0) [ 634.430] (II) FBDEV(1): hardware: udlfb (video memory: 676kB) [ 634.430] (DB) xf86MergeOutputClassOptions unsupported bus type 0 [ 634.430] (**) FBDEV(1): Option "fbdev" "/dev/fb1" [ 634.430] (II) FBDEV(1): checking modes against framebuffer device... [ 634.430] (II) FBDEV(1): checking modes against monitor... [ 634.430] (II) FBDEV(1): Virtual size is 1440x240 (pitch 1440) [ 634.431] (**) FBDEV(1): Built-in mode "current": 27.0 MHz, 15.1 kHz, 57.9 Hz [ 634.431] (II) FBDEV(1): Modeline "current"x0.0 27.00 1440 1770 1774 1792 240 254 256 260 -hsync +vsync -csync (15.1 kHz b) [ 634.431] (==) FBDEV(1): DPI set to (96, 96) [ 634.431] (II) Loading sub module "fb" [ 634.431] (II) LoadModule: "fb" [ 634.431] (II) Loading /usr/lib/xorg/modules/libfb.so [ 634.431] (II) Module fb: vendor="X.Org Foundation" [ 634.431] compiled for 1.20.11, module version = 1.0.0 [ 634.431] ABI class: X.Org ANSI C Emulation, version 0.4 [ 634.431] (**) FBDEV(1): using shadow framebuffer [ 634.431] (II) Loading sub module "shadow" [ 634.431] (II) LoadModule: "shadow" [ 634.432] (II) Loading /usr/lib/xorg/modules/libshadow.so [ 634.432] (II) Module shadow: vendor="X.Org Foundation" [ 634.432] compiled for 1.20.11, module version = 1.1.0 [ 634.432] ABI class: X.Org ANSI C Emulation, version 0.4 [ 634.432] (==) FBDEV(0): Backing store enabled [ 634.433] (==) FBDEV(0): DPMS enabled [ 634.433] (==) FBDEV(1): Backing store enabled [ 634.433] (==) FBDEV(1): DPMS enabled [ 634.433] (II) Initializing extension Generic Event Extension [ 634.434] (II) Initializing extension SHAPE [ 634.435] (II) Initializing extension MIT-SHM [ 634.436] (II) Initializing extension XInputExtension [ 634.437] (II) Initializing extension XTEST [ 634.437] (II) Initializing extension BIG-REQUESTS [ 634.438] (II) Initializing extension SYNC [ 634.438] (II) Initializing extension XKEYBOARD [ 634.439] (II) Initializing extension XC-MISC [ 634.439] (II) Initializing extension SECURITY [ 634.440] (II) Initializing extension XFIXES [ 634.440] (II) Initializing extension RENDER [ 634.441] (II) Initializing extension RANDR [ 634.441] (II) Initializing extension COMPOSITE [ 634.442] (II) Initializing extension DAMAGE [ 634.442] (II) Initializing extension MIT-SCREEN-SAVER [ 634.443] (II) Initializing extension DOUBLE-BUFFER [ 634.443] (II) Initializing extension RECORD [ 634.444] (II) Initializing extension DPMS [ 634.444] (II) Initializing extension Present [ 634.445] (II) Initializing extension DRI3 [ 634.445] (II) Initializing extension X-Resource [ 634.445] (II) Initializing extension XVideo [ 634.446] (II) Initializing extension XVideo-MotionCompensation [ 634.446] (II) Initializing extension SELinux [ 634.446] (II) SELinux: Disabled on system [ 634.446] (II) Initializing extension GLX [ 634.446] (II) AIGLX: Screen 0 is not DRI2 capable [ 634.523] (II) IGLX: Loaded and initialized swrast [ 634.523] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 634.523] (II) AIGLX: Screen 1 is not DRI2 capable [ 634.536] (II) IGLX: Loaded and initialized swrast [ 634.536] (II) GLX: Initialized DRISWRAST GL provider for screen 1 [ 634.536] (II) Initializing extension XFree86-VidModeExtension [ 634.537] (II) Initializing extension XFree86-DGA [ 634.537] (II) Initializing extension XFree86-DRI [ 634.537] (II) Initializing extension DRI2 [ 634.638] (II) config/udev: Adding input device Logitech Wireless Keyboard PID:4075 (/dev/input/event4) [ 634.639] (**) Logitech Wireless Keyboard PID:4075: Applying InputClass "libinput keyboard catchall" [ 634.639] (II) LoadModule: "libinput" [ 634.639] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so [ 634.643] (II) Module libinput: vendor="X.Org Foundation" [ 634.643] compiled for 1.20.8, module version = 0.30.0 [ 634.643] Module class: X.Org XInput Driver [ 634.643] ABI class: X.Org XInput driver, version 24.1 [ 634.643] (II) Using input driver 'libinput' for 'Logitech Wireless Keyboard PID:4075' [ 634.643] (**) Logitech Wireless Keyboard PID:4075: always reports core events [ 634.643] (**) Option "Device" "/dev/input/event4" [ 634.643] (**) Option "_source" "server/udev" [ 634.655] (II) event4 - Logitech Wireless Keyboard PID:4075: is tagged by udev as: Keyboard [ 634.655] (II) event4 - Logitech Wireless Keyboard PID:4075: device is a keyboard [ 634.656] (II) event4 - Logitech Wireless Keyboard PID:4075: device removed [ 634.676] (II) libinput: Logitech Wireless Keyboard PID:4075: needs a virtual subdevice [ 634.676] (**) Option "config_info" "udev:/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.1/0003:046D:C534.0003/0003:046D:4075.0005/input/input29/event4" [ 634.676] (II) XINPUT: Adding extended input device "Logitech Wireless Keyboard PID:4075" (type: MOUSE, id 6) [ 634.676] (**) Option "AccelerationScheme" "none" [ 634.676] (**) Logitech Wireless Keyboard PID:4075: (accel) selected scheme none/0 [ 634.676] (**) Logitech Wireless Keyboard PID:4075: (accel) acceleration factor: 2.000 [ 634.676] (**) Logitech Wireless Keyboard PID:4075: (accel) acceleration threshold: 4 [ 634.684] (II) event4 - Logitech Wireless Keyboard PID:4075: is tagged by udev as: Keyboard [ 634.684] (II) event4 - Logitech Wireless Keyboard PID:4075: device is a keyboard [ 634.689] (II) config/udev: Adding input device Logitech Wireless Mouse (/dev/input/event5) [ 634.689] (**) Logitech Wireless Mouse: Applying InputClass "libinput pointer catchall" [ 634.689] (II) Using input driver 'libinput' for 'Logitech Wireless Mouse' [ 634.689] (**) Logitech Wireless Mouse: always reports core events [ 634.689] (**) Option "Device" "/dev/input/event5" [ 634.689] (**) Option "_source" "server/udev" [ 634.698] (II) event5 - Logitech Wireless Mouse: is tagged by udev as: Mouse [ 634.698] (II) event5 - Logitech Wireless Mouse: device is a pointer [ 634.699] (II) event5 - Logitech Wireless Mouse: device removed [ 634.732] (**) Option "config_info" "udev:/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.1/0003:046D:C534.0003/0003:046D:4091.0006/input/input30/event5" [ 634.732] (II) XINPUT: Adding extended input device "Logitech Wireless Mouse" (type: MOUSE, id 7) [ 634.732] (**) Option "AccelerationScheme" "none" [ 634.732] (**) Logitech Wireless Mouse: (accel) selected scheme none/0 [ 634.732] (**) Logitech Wireless Mouse: (accel) acceleration factor: 2.000 [ 634.732] (**) Logitech Wireless Mouse: (accel) acceleration threshold: 4 [ 634.740] (II) event5 - Logitech Wireless Mouse: is tagged by udev as: Mouse [ 634.741] (II) event5 - Logitech Wireless Mouse: device is a pointer [ 634.745] (II) config/udev: Adding input device Logitech Wireless Mouse (/dev/input/mouse2) [ 634.745] (II) No input driver specified, ignoring this device. [ 634.745] (II) This device may have been added with another device file. [ 634.749] (II) config/udev: Adding input device eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 (/dev/input/event2) [ 634.749] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: Applying InputClass "libinput touchscreen catchall" [ 634.749] (II) Using input driver 'libinput' for 'eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163' [ 634.749] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: always reports core events [ 634.749] (**) Option "Device" "/dev/input/event2" [ 634.749] (**) Option "_source" "server/udev" [ 634.757] (II) event2 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: is tagged by udev as: Touchscreen [ 634.757] (II) event2 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: device is a touch device [ 634.758] (II) event2 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: device removed [ 634.772] (**) Option "config_info" "udev:/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/0003:0EEF:C001.0001/input/input14/event2" [ 634.772] (II) XINPUT: Adding extended input device "eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163" (type: TOUCHSCREEN, id 8) [ 634.772] (**) Option "AccelerationScheme" "none" [ 634.772] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: (accel) selected scheme none/0 [ 634.772] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: (accel) acceleration factor: 2.000 [ 634.772] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: (accel) acceleration threshold: 4 [ 634.780] (II) event2 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: is tagged by udev as: Touchscreen [ 634.780] (II) event2 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: device is a touch device [ 634.784] (II) config/udev: Adding input device eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 (/dev/input/mouse0) [ 634.784] (II) No input driver specified, ignoring this device. [ 634.784] (II) This device may have been added with another device file. [ 634.788] (II) config/udev: Adding input device eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN (/dev/input/event3) [ 634.788] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: Applying InputClass "libinput pointer catchall" [ 634.788] (II) Using input driver 'libinput' for 'eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN' [ 634.788] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: always reports core events [ 634.788] (**) Option "Device" "/dev/input/event3" [ 634.788] (**) Option "_source" "server/udev" [ 634.796] (II) event3 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: is tagged by udev as: Mouse [ 634.797] (II) event3 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: device is a pointer [ 634.797] (II) event3 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: device removed [ 634.812] (**) Option "config_info" "udev:/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/0003:0EEF:C001.0001/input/input16/event3" [ 634.812] (II) XINPUT: Adding extended input device "eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN" (type: MOUSE, id 9) [ 634.812] (**) Option "AccelerationScheme" "none" [ 634.812] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: (accel) selected scheme none/0 [ 634.812] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: (accel) acceleration factor: 2.000 [ 634.812] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: (accel) acceleration threshold: 4 [ 634.820] (II) event3 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: is tagged by udev as: Mouse [ 634.821] (II) event3 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: device is a pointer [ 634.825] (II) config/udev: Adding input device eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN (/dev/input/js0) [ 634.825] (II) No input driver specified, ignoring this device. [ 634.825] (II) This device may have been added with another device file. [ 634.828] (II) config/udev: Adding input device eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN (/dev/input/mouse1) [ 634.828] (II) No input driver specified, ignoring this device. [ 634.828] (II) This device may have been added with another device file. [ 634.832] (II) config/udev: Adding input device eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 (/dev/input/event6) [ 634.832] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: Applying InputClass "libinput touchscreen catchall" [ 634.832] (II) Using input driver 'libinput' for 'eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163' [ 634.832] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: always reports core events [ 634.832] (**) Option "Device" "/dev/input/event6" [ 634.832] (**) Option "_source" "server/udev" [ 634.841] (II) event6 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: is tagged by udev as: Touchscreen [ 634.841] (II) event6 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: device is a touch device [ 634.842] (II) event6 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: device removed [ 634.860] (**) Option "config_info" "udev:/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.2/1-1.2.4.2:1.0/0003:0EEF:C002.0004/input/input26/event6" [ 634.860] (II) XINPUT: Adding extended input device "eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163" (type: TOUCHSCREEN, id 10) [ 634.860] (**) Option "AccelerationScheme" "none" [ 634.860] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: (accel) selected scheme none/0 [ 634.860] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: (accel) acceleration factor: 2.000 [ 634.860] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: (accel) acceleration threshold: 4 [ 634.868] (II) event6 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: is tagged by udev as: Touchscreen [ 634.869] (II) event6 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163: device is a touch device [ 634.873] (II) config/udev: Adding input device eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 (/dev/input/mouse3) [ 634.873] (II) No input driver specified, ignoring this device. [ 634.873] (II) This device may have been added with another device file. [ 634.877] (II) config/udev: Adding input device eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN (/dev/input/event7) [ 634.877] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: Applying InputClass "libinput pointer catchall" [ 634.877] (II) Using input driver 'libinput' for 'eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN' [ 634.877] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: always reports core events [ 634.877] (**) Option "Device" "/dev/input/event7" [ 634.877] (**) Option "_source" "server/udev" [ 634.886] (II) event7 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: is tagged by udev as: Mouse [ 634.887] (II) event7 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: device is a pointer [ 634.887] (II) event7 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: device removed [ 634.908] (**) Option "config_info" "udev:/sys/devices/platform/scb/fe9c0000.xhci/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4.2/1-1.2.4.2:1.0/0003:0EEF:C002.0004/input/input28/event7" [ 634.908] (II) XINPUT: Adding extended input device "eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN" (type: MOUSE, id 11) [ 634.908] (**) Option "AccelerationScheme" "none" [ 634.908] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: (accel) selected scheme none/0 [ 634.908] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: (accel) acceleration factor: 2.000 [ 634.908] (**) eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: (accel) acceleration threshold: 4 [ 634.916] (II) event7 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: is tagged by udev as: Mouse [ 634.917] (II) event7 - eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN: device is a pointer [ 634.921] (II) config/udev: Adding input device eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN (/dev/input/js1) [ 634.922] (II) No input driver specified, ignoring this device. [ 634.922] (II) This device may have been added with another device file. [ 634.925] (II) config/udev: Adding input device eGalax Inc. eGalaxTouch P80H32 8032 v01 k4.08.163 UNKNOWN (/dev/input/mouse4) [ 634.925] (II) No input driver specified, ignoring this device. [ 634.925] (II) This device may have been added with another device file. [ 634.928] (II) config/udev: Adding input device vc4-hdmi-0 (/dev/input/event0) [ 634.928] (**) vc4-hdmi-0: Applying InputClass "libinput keyboard catchall" [ 634.928] (II) Using input driver 'libinput' for 'vc4-hdmi-0' [ 634.928] (**) vc4-hdmi-0: always reports core events [ 634.928] (**) Option "Device" "/dev/input/event0" [ 634.928] (**) Option "_source" "server/udev" [ 634.931] (II) event0 - vc4-hdmi-0: is tagged by udev as: Keyboard Pointingstick [ 634.932] (II) event0 - vc4-hdmi-0: device is a pointer [ 634.932] (II) event0 - vc4-hdmi-0: device is a keyboard [ 634.934] (II) event0 - vc4-hdmi-0: device removed [ 634.948] (II) libinput: vc4-hdmi-0: needs a virtual subdevice [ 634.948] (**) Option "config_info" "udev:/sys/devices/platform/soc/fef00700.hdmi/rc/rc0/input12/event0" [ 634.948] (II) XINPUT: Adding extended input device "vc4-hdmi-0" (type: MOUSE, id 12) [ 634.948] (**) Option "AccelerationScheme" "none" [ 634.948] (**) vc4-hdmi-0: (accel) selected scheme none/0 [ 634.948] (**) vc4-hdmi-0: (accel) acceleration factor: 2.000 [ 634.948] (**) vc4-hdmi-0: (accel) acceleration threshold: 4 [ 634.952] (II) event0 - vc4-hdmi-0: is tagged by udev as: Keyboard Pointingstick [ 634.953] (II) event0 - vc4-hdmi-0: device is a pointer [ 634.953] (II) event0 - vc4-hdmi-0: device is a keyboard [ 634.956] (II) config/udev: Adding input device vc4-hdmi-1 (/dev/input/event1) [ 634.956] (**) vc4-hdmi-1: Applying InputClass "libinput keyboard catchall" [ 634.956] (II) Using input driver 'libinput' for 'vc4-hdmi-1' [ 634.956] (**) vc4-hdmi-1: always reports core events [ 634.956] (**) Option "Device" "/dev/input/event1" [ 634.956] (**) Option "_source" "server/udev" [ 634.960] (II) event1 - vc4-hdmi-1: is tagged by udev as: Keyboard Pointingstick [ 634.961] (II) event1 - vc4-hdmi-1: device is a pointer [ 634.961] (II) event1 - vc4-hdmi-1: device is a keyboard [ 634.962] (II) event1 - vc4-hdmi-1: device removed [ 634.980] (II) libinput: vc4-hdmi-1: needs a virtual subdevice [ 634.980] (**) Option "config_info" "udev:/sys/devices/platform/soc/fef05700.hdmi/rc/rc1/input13/event1" [ 634.980] (II) XINPUT: Adding extended input device "vc4-hdmi-1" (type: MOUSE, id 13) [ 634.980] (**) Option "AccelerationScheme" "none" [ 634.980] (**) vc4-hdmi-1: (accel) selected scheme none/0 [ 634.980] (**) vc4-hdmi-1: (accel) acceleration factor: 2.000 [ 634.980] (**) vc4-hdmi-1: (accel) acceleration threshold: 4 [ 634.984] (II) event1 - vc4-hdmi-1: is tagged by udev as: Keyboard Pointingstick [ 634.985] (II) event1 - vc4-hdmi-1: device is a pointer [ 634.985] (II) event1 - vc4-hdmi-1: device is a keyboard [ 635.005] (**) Logitech Wireless Keyboard PID:4075: Applying InputClass "libinput keyboard catchall" there is a tad more but doesnt seem relevant
Peterdagrape (1 rep)
Jul 15, 2024, 02:06 PM
0 votes
3 answers
5478 views
Displaylink not detecting external monitors on archlinux
Anyone who has/is successfully using Display link with evdi for external monitor on his arch linux? I’ve been struggling to make it work. I was on lts kernel before and learnt evdi is working best with latest arch kernel 5.16, so i switched to latest kernel. Even then it fails to work. I do see exte...
Anyone who has/is successfully using Display link with evdi for external monitor on his arch linux? I’ve been struggling to make it work. I was on lts kernel before and learnt evdi is working best with latest arch kernel 5.16, so i switched to latest kernel. Even then it fails to work. I do see external monitors with display link when i use dmesg. But i never get the external monitor activate. If it helps, I’m using Hp USB C docking station. I could share more info if needed. I have been following arch wiki for display link. I have tried mode setting and other trouble shooting tips/workarounds in wiki. None of it worked yet. Hardware used: System76 Lemur Pro 10 Any help or guidance is appreciated. #evdi #displaylink #arch
Prakash Vishwakarma (119 rep)
Mar 8, 2022, 10:03 PM • Last activity: Jun 13, 2024, 09:03 AM
1 votes
0 answers
185 views
Why do DisplayLink monitors stop working after suspend in 6.x kernel?
# Symptoms 2 out of 4 monitors don't light up after suspend. This is a similar problem as [this post][1] but not quite the same. # Hardware - Dell XPS 9320 plus (i7-1280P) - [UD22 Dock][2] - 4 monitors # OS - LinuxMint 21.2 with kernel 5.19.0-50 (all is well except, 10-15% chance, 1 of the monitors...
# Symptoms 2 out of 4 monitors don't light up after suspend. This is a similar problem as this post but not quite the same. # Hardware - Dell XPS 9320 plus (i7-1280P) - UD22 Dock - 4 monitors # OS - LinuxMint 21.2 with kernel 5.19.0-50 (all is well except, 10-15% chance, 1 of the monitors doesn't revive after suspend and I just need to reboot) - LinuxMint 21.2 with kernel 6.2.0-26 (where the problem occurs) # Software - DisplayLink driver 5.6.1, 5.7.0, 5.8.0 Standalone Installer # Other info Unlike this post , the service is always "loaded" and "active (running)" even when 2 monitors don't revive.
$ sudo systemctl status displaylink-driver.service 

        ● displaylink-driver.service - DisplayLink Driver Service
     Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static)
     Active: active (running) since Mon 2023-08-14 09:06:37 EDT; 1h 48min ago
    Process: 1240 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install $(ls -t /usr/src | grep evdi | head -n1  | sed -e "s:-:/:") && modprobe evdi) (code=exited, status=0/SUCCESS)

   Main PID: 1243 (DisplayLinkMana)
      Tasks: 53 (limit: 37856)
     Memory: 103.3M
        CPU: 24min 30.305s
     CGroup: /system.slice/displaylink-driver.service
             └─1243 /opt/displaylink/DisplayLinkManager

Aug 14 09:06:37 xps-9320 systemd[1] : Starting DisplayLink Driver Service...
Aug 14 09:06:37 xps-9320 systemd[1] : Started DisplayLink Driver Service.
# What I tried: 1. Upgrade the DisplayLink driver to 5.7.0 then 5.8.0 2. Upgrade evdi to 1.13.1 then 1.14.1 3. Restart the service Nothing worked. So far the most effective way is to logout/login, which is much faster than reboot. Somehow the DisplayLink driver causes a long hanging (120 secs) during startup/reboot. # Updates 1. Oct 31, 2023 - problem solved after upgrading to kernel 6.2.0-36 2. Jan 17, 2024 - upgrading from Linux Mint 21.2 to 21.3 somehow stopped the service. I had to start the service manually.
$ sudo systemctl start displaylink-driver.service
dunkirk (11 rep)
Aug 11, 2023, 06:26 PM • Last activity: Jan 17, 2024, 05:07 PM
0 votes
0 answers
157 views
Monitor for virtual ubuntu
I had arm-based server ubuntu and I showed outside temperature to it's monitor over FIM. For some reasons I had to move to server with some virtual machines and I installed server ubuntu on it. I would like to do the similar as before. I have USB-to-VGA adapter from DisplayLink.com. I connected it t...
I had arm-based server ubuntu and I showed outside temperature to it's monitor over FIM.
For some reasons I had to move to server with some virtual machines and I installed server ubuntu on it.
I would like to do the similar as before. I have USB-to-VGA adapter from DisplayLink.com. I connected it to host and connected to virtual machine, installed driver for Ubuntu. And ubuntu sees my monitor. It shows some messages but not console. So it shows the following: ls /sys/class/drm/*/edid | xargs -i{} sh -c "echo {}; parse-edid Are there any ideas on how to redirect main monitor of Ubuntu to this external monitor? Thanks. Rg, Dmitry
Dmitry Senashenko (21 rep)
Nov 13, 2023, 08:33 PM • Last activity: Nov 21, 2023, 10:43 AM
0 votes
0 answers
270 views
DisplayLink provider does not show up with USBC Lenovo dock
Trying to run two screens connected to a ThinkPad USBC dock, which is connected to my laptop via USBC. The dock is connected as it charges and works with external mouse / keyboard. I have followed the instructions to the letter on DisplayLink section of the arch wiki. When running `xrandr --listprov...
Trying to run two screens connected to a ThinkPad USBC dock, which is connected to my laptop via USBC. The dock is connected as it charges and works with external mouse / keyboard. I have followed the instructions to the letter on DisplayLink section of the arch wiki. When running xrandr --listproviders, only one provider shows up. The displaylink provider does not show up: `Providers: number : 1 Provider 0: id: 0x48 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 4 outputs: 6 associated providers: 0 name:modesetting` I have tried all versions of evdi (evdi, evdi-git, evdi-compat-git). udl is installed and running and I have edited the 20-evdi.conf file. I have updated my system, re installed displaylink, all versions of evdi, etc. I have tried any debugging solutions I can find.
Sam (9 rep)
Sep 6, 2023, 07:39 AM
0 votes
1 answers
226 views
modinfo: ERROR: Module udl not found
Error occurs when running `modinfo udl` Using kernel 6.4.11-arch2-1. In my config I have: CONFIG_DRM_UDL=m # CONFIG_FB_UDL is not set `modinfo udlfb` returns the same error. This problem arose when debugging an issue with displaylink. Displaylink does not run at all and I believe it is due to the ud...
Error occurs when running modinfo udl Using kernel 6.4.11-arch2-1. In my config I have: CONFIG_DRM_UDL=m # CONFIG_FB_UDL is not set modinfo udlfb returns the same error. This problem arose when debugging an issue with displaylink. Displaylink does not run at all and I believe it is due to the udl module missing. I have followed all debugging steps on the archlinux wiki and anything eles I can find on here/google. How can I resolve this?
Sam (9 rep)
Aug 30, 2023, 08:48 AM • Last activity: Sep 3, 2023, 07:28 AM
1 votes
1 answers
1061 views
Is it possible to reactivate (not reload) a driver from running kernel?
Struggling with some devices often not functioning upon [suspend][1], I came across the SE U&L question of [reloading drivers](https://unix.stackexchange.com/questions/113828/how-to-find-and-reload-specific-driver-from-kernel). In my case, a few devices are not detected, and I can see the driver (di...
Struggling with some devices often not functioning upon suspend , I came across the SE U&L question of [reloading drivers](https://unix.stackexchange.com/questions/113828/how-to-find-and-reload-specific-driver-from-kernel). In my case, a few devices are not detected, and I can see the driver (displaylink-driver.service) is loaded but inactive/dead.  So, is it possible to start drivers up again? $ lsusb # missing usb devices (detected by $ lsusb before the issue) Bus 004 Device 005: ID 17ef:a357 Lenovo USB3.1 Hub Bus 004 Device 004: ID 17ef:a359 Lenovo ThinkPad Lan Bus 004 Device 003: ID 17e9:6015 DisplayLink ThinkPad Hybrid USB-C with USB-A Dock Bus 004 Device 002: ID 17ef:a356 Lenovo USB3.1 Hub $ sudo systemctl status displaylink-driver.service ● displaylink-driver.service - DisplayLink Driver Service Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static) Active: inactive (dead) May 26 14:50:56 debija systemd[1] : Starting DisplayLink Driver Service... May 26 14:50:56 debija systemd[1] : Started DisplayLink Driver Service. May 26 18:03:21 debija systemd[1] : Stopping DisplayLink Driver Service... May 26 18:03:22 debija systemd[1] : displaylink-driver.service: Succeeded. May 26 18:03:22 debija systemd[1] : Stopped DisplayLink Driver Service. May 26 18:03:22 debija systemd[1] : displaylink-driver.service: Consumed 41min 25.761s CPU time.
Johan (439 rep)
May 26, 2023, 08:10 PM • Last activity: Aug 11, 2023, 01:53 PM
0 votes
0 answers
985 views
xrandr --rotate inverted is making a kind of mirror effect
I use a script to setup all my screen when I plug my laptop on my dock ```bash xrandr --output eDP1 --off xrandr --output DVI-I-2-2 --mode 1920x1080 --pos 0x0 --rotate inverted xrandr --output DP1 --mode 1920x1080 --pos 1920x0 --primary xrandr --output DVI-I-1-1 --mode 1920x1080 --pos 3840x0 ``` But...
I use a script to setup all my screen when I plug my laptop on my dock
xrandr --output eDP1 --off
xrandr --output DVI-I-2-2 --mode 1920x1080 --pos 0x0 --rotate inverted
xrandr --output DP1 --mode 1920x1080 --pos 1920x0 --primary
xrandr --output DVI-I-1-1 --mode 1920x1080 --pos 3840x0
But the rotated screen is not really rotated... Some stuff are rotated, some not. What is not rotated : - Mouse cursor - Wallpaper - Any window display What is rotated : - Windows button (I mean actions, so to interact with a window you have to click where the button is supposed to be and not where it's displayed) - The side of the screen where mouse come in and out I tried it on gnome and pantheon desktop, and screen are plugged on displayLink (dell d-6000) dock. Do you guys have any idea ? Thanks
Kermito (21 rep)
Jan 19, 2023, 09:46 PM • Last activity: Jun 1, 2023, 10:35 AM
1 votes
0 answers
782 views
Why after suspend only sometimes not detect USB, or deactivates driver (and how to fix)? monitors, Displaylink, Debian
Two monitors sometimes wake up from suspend, and other times they do not [e.g.][1]. _Specifically_, entering suspend and hitting the keyboard seems to wake up the monitors the first time. But clicking suspend the second time the monitors remain black. As a result USB devices connecting the monitors...
Two monitors sometimes wake up from suspend, and other times they do not e.g. . _Specifically_, entering suspend and hitting the keyboard seems to wake up the monitors the first time. But clicking suspend the second time the monitors remain black. As a result USB devices connecting the monitors to the laptop with Displaylink cannot be found, and the Displaylink driver is deactivated. Only reboot works. Other usb connected devices to the dock work, such as keyboard and mouse. The issue seems independent of the lid position and does not occur 'intermittently' . How to troubleshoot? Is the issue due to DisplayLink, suspend, or something else? The following did _not_ work: - turn off USB autosuspend and blacklist in tlp or TLP UI. - thunderbolt-tools , tbtadm approve-all and checking with lspci devices. - Unplugging hdmi or usb-c of the dock. I would not know what I would be doing: - remove /etc/pm/sleep.d/displaylink.sh. - udev rules - blacklist - powertop Some possible involved files
/etc/tlp.conf 
/sys/bus/usb/devices/usb3/power/wakeup

/usr/lib/systemd/system-sleep/displaylink.sh
/usr/lib/systemd/system/displaylink-driver.service
/etc/udev/rules.d/99-displaylink.rules
/etc/pm/sleep.d/10_displaylink
/opt/displaylink/suspend.sh
/etc/pm/sleep.d/10_displaylink
___log__: suspend causes evdi to be disconnected/closed?_
$ sudo dmesg -w | grep Display

[    3.306247] usb 4-1.2: Manufacturer: DisplayLink
[    7.395781] evdi: [I] (card1) Opened by Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[    7.397744] evdi: [I] (card1) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[    7.399740] evdi: [I] (card2) Opened by Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[    7.401344] evdi: [I] (card2) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[    9.889337] evdi: [I] (card1) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[    9.912344] evdi: [I] (card2) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[ 1849.616093] evdi: [I] (card1) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[ 1849.616521] evdi: [I] (card2) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[ 7301.667983] evdi: [I] (card1) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[ 7301.668399] evdi: [I] (card2) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11442.370372] evdi: [I] (card1) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11442.370503] evdi: [I] (card2) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.506775] evdi: [I] (card1) Disconnected from Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.534477] evdi: [I] (card1) Closed by Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.536880] evdi: [I] (card2) Disconnected from Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.542512] evdi: [I] (card2) Closed by Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)

# a little more dmseg output
[11293.477299] evdi: [I] (card2) Notifying display power state: off
[11293.477327] evdi: [I] (card1) Notifying display power state: off
[11293.479051] evdi: [I] (card2) Notifying display power state: off
[11293.479737] evdi: [I] (card1) Notifying display power state: off
[11302.597210] PM: suspend entry (s2idle)
[11302.613795] Filesystems sync: 0.016 seconds
[11302.614152] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[11302.614496] (NULL device *): firmware: direct-loading firmware regulatory.db
[11302.614516] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
[11302.615831] (NULL device *): firmware: direct-loading firmware iwlwifi-8265-36.ucode
[11302.615962] Freezing user space processes ... (elapsed 0.003 seconds) done.
[11302.619720] OOM killer disabled.
[11302.619723] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[11302.621413] printk: Suspending console(s) (use no_console_suspend to debug)
[11302.892991] e1000e: EEE TX LPI TIMER: 00000011
[11302.930826] ACPI: EC: interrupt blocked
[11438.215551] ACPI: EC: interrupt unblocked
[11438.233739] pcieport 0000:00:1c.2: Intel SPT PCH root port ACS workaround enabled
[11438.233740] pcieport 0000:00:1c.0: Intel SPT PCH root port ACS workaround enabled
[11439.737330] pcieport 0000:00:1d.0: Intel SPT PCH root port ACS workaround enabled
[11441.218576] pcieport 0000:00:1c.4: Intel SPT PCH root port ACS workaround enabled
[11441.537943] usb 1-10: reset full-speed USB device number 7 using xhci_hcd
[11441.699720] OOM killer enabled.
[11441.699723] Restarting tasks ... 
[11441.699875] pci_bus 0000:08: Allocating resources
[11441.699914] pci_bus 0000:3c: Allocating resources
[11441.713490] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[11441.714617] done.
[11441.778266] PM: suspend exit
[11441.943765] evdi: [I] (card1) Notifying display power state: on
[11441.943785] evdi: [I] (card1) Notifying mode changed: 2560x1440@60; bpp 32; pixel format XR24 little-endian (0x34325258)
[11441.943786] evdi: [I] (card1) Notifying display power state: on
[11441.953580] evdi: [I] (card2) Notifying display power state: on
[11441.953595] evdi: [I] (card2) Notifying mode changed: 1920x1080@60; bpp 32; pixel format XR24 little-endian (0x34325258)
[11441.953596] evdi: [I] (card2) Notifying display power state: on
[11441.957136] psmouse serio1: synaptics: queried max coordinates: x [..5678], y [..4720]
[11441.987991] psmouse serio1: synaptics: queried min coordinates: x [1264..], y [1132..]
[11442.370370] evdi: [W] evdi_painter_connect:883 (card1) Double connect - replacing 00000000249f7991 with 00000000249f7991
[11442.370372] evdi: [I] (card1) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11442.370374] evdi: [I] (card1) Connector state: connected
[11442.370502] evdi: [W] evdi_painter_connect:883 (card2) Double connect - replacing 00000000d81e37fa with 00000000d81e37fa
[11442.370503] evdi: [I] (card2) Connected with Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11442.370504] evdi: [I] (card2) Connector state: connected
[11445.432016] evdi: [I] (card1) Notifying mode changed: 2560x1440@60; bpp 32; pixel format XR24 little-endian (0x34325258)
[11445.432022] evdi: [I] (card1) Notifying display power state: on
[11445.444692] evdi: [I] (card2) Notifying mode changed: 1920x1080@60; bpp 32; pixel format XR24 little-endian (0x34325258)
[11445.444698] evdi: [I] (card2) Notifying display power state: on
[11495.853579] e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down
[11495.863841] evdi: [I] (card2) Notifying display power state: off
[11495.863875] evdi: [I] (card1) Notifying display power state: off
[11495.865487] evdi: [I] (card2) Notifying display power state: off
[11495.868225] evdi: [I] (card1) Notifying display power state: off
[11498.374912] PM: suspend entry (s2idle)
[11498.387093] Filesystems sync: 0.012 seconds
[11498.387319] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[11498.387679] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
[11498.387682] (NULL device *): firmware: direct-loading firmware regulatory.db
[11498.388599] (NULL device *): firmware: direct-loading firmware iwlwifi-8265-36.ucode
[11498.388662] Freezing user space processes ... (elapsed 0.004 seconds) done.
[11498.392991] OOM killer disabled.
[11498.392994] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[11498.394918] printk: Suspending console(s) (use no_console_suspend to debug)
[11498.466114] hub 4-1:1.0: hub_ext_port_status failed (err = -71)
[11498.473177] usb 4-1.4: Port disable: can't disable remote wake
[11498.481987] usb 4-1-port4: cannot disable (err = -71)
[11498.596552] usb 4-1-port4: device 4-1.4 not suspended yet
[11498.641355] e1000e: EEE TX LPI TIMER: 00000011
[11503.725305] xhci_hcd 0000:3c:00.0: xHCI host not responding to stop endpoint command.
[11503.725312] xhci_hcd 0000:3c:00.0: USBSTS: 0x00000000
[11503.725321] xhci_hcd 0000:3c:00.0: xHCI host controller not responding, assume dead
[11503.725344] xhci_hcd 0000:3c:00.0: HC died; cleaning up
[11503.749658] ACPI: EC: interrupt blocked
[11549.036097] ACPI: EC: interrupt unblocked
[11549.054131] pcieport 0000:00:1c.0: Intel SPT PCH root port ACS workaround enabled
[11549.054135] pcieport 0000:00:1c.2: Intel SPT PCH root port ACS workaround enabled
[11550.541723] pcieport 0000:00:1d.0: Intel SPT PCH root port ACS workaround enabled
[11552.003809] pcieport 0000:00:1c.4: Intel SPT PCH root port ACS workaround enabled
[11552.314323] usb 1-10: reset full-speed USB device number 7 using xhci_hcd
[11552.487970] OOM killer enabled.
[11552.487973] Restarting tasks ... 
[11552.488140] pci_bus 0000:08: Allocating resources
[11552.488177] pci_bus 0000:3c: Allocating resources
[11552.488237] usb 4-1.2: USB disconnect, device number 3
[11552.491498] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[11552.495234] evdi: [I] Detached from parent device
[11552.495237] evdi: [I] Detached from parent device
[11552.495386] usb 4-1.3: USB disconnect, device number 4
[11552.495433] cdc_ether 4-1.3:2.0 enx806d973a4123: unregister 'cdc_ether' usb-0000:3c:00.0-1.3, CDC Ethernet Device
[11552.496390] usb 4-1: USB disconnect, device number 2
[11552.501152] done.
[11552.506775] evdi: [I] (card1) Disconnected from Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.506780] evdi: [I] (card1) Removing i2c adapter bus number 8
[11552.534477] evdi: [I] (card1) Closed by Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.536880] evdi: [I] (card2) Disconnected from Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.536882] evdi: [I] (card2) Removing i2c adapter bus number 9
[11552.538087] usb 4-1.4: USB disconnect, device number 5
[11552.542512] evdi: [I] (card2) Closed by Task 1054 (DesktopManagerE) of process 919 (DisplayLinkMana)
[11552.567133] PM: suspend exit
[11552.738946] psmouse serio1: synaptics: queried max coordinates: x [..5678], y [..4720]
[11552.769228] psmouse serio1: synaptics: queried min coordinates: x [1264..], y [1132..]
[11665.969996] usb 1-9: USB disconnect, device number 6
[11666.277389] usb 1-9: new full-speed USB device number 13 using xhci_hcd
[11666.427964] usb 1-9: New USB device found, idVendor=06cb, idProduct=009a, bcdDevice= 1.64
[11666.427973] usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[11666.427978] usb 1-9: SerialNumber: a9fd9886e55f
[11668.237192] usb 1-9: USB disconnect, device number 13
[11669.029351] usb 1-9: new full-speed USB device number 14 using xhci_hcd
[11669.179964] usb 1-9: New USB device found, idVendor=06cb, idProduct=009a, bcdDevice= 1.64
[11669.179973] usb 1-9: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[11669.179978] usb 1-9: SerialNumber: a9fd9886e55f
_displaylink-driver.service becomes inactive and usb device is not registered - after suspend_
$ sudo systemctl status displaylink-driver.service 
● displaylink-driver.service - DisplayLink Driver Service
     Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static)
     Active: inactive (dead)

May 26 14:50:56 debija systemd[1] : Starting DisplayLink Driver Service...
May 26 14:50:56 debija systemd[1] : Started DisplayLink Driver Service.
May 26 18:03:21 debija systemd[1] : Stopping DisplayLink Driver Service...
May 26 18:03:22 debija systemd[1] : displaylink-driver.service: Succeeded.
May 26 18:03:22 debija systemd[1] : Stopped DisplayLink Driver Service.
May 26 18:03:22 debija systemd[1] : displaylink-driver.service: Consumed 41min 25.761s CPU time.

$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0bda:0328 Realtek Semiconductor Corp. USB3.0-CRW
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 014: ID 06cb:009a Synaptics, Inc. Metallica MIS Touch Fingerprint Reader
Bus 001 Device 004: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 009: ID 1395:0025 Sennheiser Communications Headset [PC 8]
Bus 001 Device 012: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse
Bus 001 Device 011: ID 145f:020c Trust Trust Ergo Mouse
Bus 001 Device 010: ID 04b4:5218 Cypress Semiconductor Corp. USB-Serial Bridge
Bus 001 Device 008: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 005: ID 17ef:1029 Lenovo USB2.0 Hub             
Bus 001 Device 002: ID 17ef:1028 Lenovo USB2.0 Hub             
Bus 001 Device 007: ID 056a:5144 Wacom Co., Ltd Pen and multitouch sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


# missing usb devices (detected by $ lsusb before the issue)
Bus 004 Device 005: ID 17ef:a357 Lenovo USB3.1 Hub             
Bus 004 Device 004: ID 17ef:a359 Lenovo ThinkPad Lan
Bus 004 Device 003: ID 17e9:6015 DisplayLink ThinkPad Hybrid USB-C with USB-A Dock
Bus 004 Device 002: ID 17ef:a356 Lenovo USB3.1 Hub
Johan (439 rep)
May 23, 2023, 08:57 AM • Last activity: May 31, 2023, 09:14 AM
4 votes
1 answers
9808 views
Debian recognizes usb-c docking station, but monitors do not work
With Debian stable and proprietary drivers on a Lenovo x1 3rd gen--but not with MS windows 10 on an older Lenovo laptop (using the usb-c to usb-a) and a HP laptop (using usb-c)--I have a problem with the *ThinkPad Hybrid USB-C with USB-A Dock*: The USB-devices mouse, keyboard, and headset works fine...
With Debian stable and proprietary drivers on a Lenovo x1 3rd gen--but not with MS windows 10 on an older Lenovo laptop (using the usb-c to usb-a) and a HP laptop (using usb-c)--I have a problem with the *ThinkPad Hybrid USB-C with USB-A Dock*: The USB-devices mouse, keyboard, and headset works fine; but the two monitors do not (akin to Pauxlo's experience ). What to do? 1. forget about using this docking station (costly) 2. install Ubuntu (well, Debian is otherwise nice and installed) 3. try to make DisplayLink for Ubuntu [2] [3] work on Debian (may be quite involved) 4. ask the question elsewhere e.g. on the displaylink forum, on the linux-hardware.org forum, et cetera. 5. other alternatives I have found related issues, some which are solved, others which are still unsolved: - detected on Debian 11 and Debian Testing with "snd_usb_audio" driver according to linux-hardware.org - Debian Buster with a link to solution for arch linux - solutions and non-solutions [7] [8] for Ubuntu distributions - issue on Fedora, solution on RHEL8 and so on - in case of high resolution, apt-get install evdi-dkms libevdi0 has been suggested for Debian [10]
$ lsusb
Bus 004 Device 011: ID 17e9:6015 DisplayLink ThinkPad Hybrid USB-C with USB-A Dock
Johan (439 rep)
Apr 14, 2023, 05:50 PM • Last activity: Apr 16, 2023, 08:21 AM
1 votes
0 answers
727 views
How to setup displaylink to keep working even after a restart
I have setup display link on my elementary OS, but each time i restart my laptop, seems like all the settings gets reset and i have to reinstall display link to get it working again. I do however notice some weird logs while i setup display link executing this command `displaylink-debian/5.6.1/displ...
I have setup display link on my elementary OS, but each time i restart my laptop, seems like all the settings gets reset and i have to reinstall display link to get it working again. I do however notice some weird logs while i setup display link executing this command displaylink-debian/5.6.1/displaylink-driver-5.6.1-59.184.run results in the log below
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing DisplayLink Linux Driver 5.6.1-59.184  100%  
Distribution discovered: elementary OS 5.1.7 Hera

Installing
[ Installing EVDI ]
[[ Installing EVDI DKMS module ]]

Creating symlink /var/lib/dkms/evdi/1.12.0/source ->
                 /usr/src/evdi-1.12.0

DKMS: add completed.

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j8 KERNELRELEASE=4.15.0-166-generic all INCLUDEDIR=/lib/modules/4.15.0-166-generic/build/include KVERSION=4.15.0-166-generic DKMS_BUILD=1....
cleaning build area...

DKMS: build completed.

evdi.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.15.0-166-generic/extra/

depmod....

DKMS: install completed.
[[ Installing module configuration files ]]
[[ Installing EVDI library ]]
make: Entering directory '/tmp/tmp.nWZNY8zKBb/evdi/library'
cc -I../module -std=gnu99 -fPIC -D_FILE_OFFSET_BITS=64    -c -o evdi_lib.o evdi_lib.c
cc evdi_lib.o -shared -Wl,-soname,libevdi.so.0 -o libevdi.so.1.12.0 -lc -lgcc 
cp libevdi.so.1.12.0 libevdi.so
make: Leaving directory '/tmp/tmp.nWZNY8zKBb/evdi/library'
[ Installing x64-ubuntu-1604/DisplayLinkManager ]
[ Installing libraries ]
[ Installing firmware packages ]
[ Installing licence file ]
[ Adding udev rule for DisplayLink DL-3xxx/4xxx/5xxx/6xxx devices ]
logname: no login name
Failed to get session path: No session 'SESSION' known
logname: no login name
Failed to get session path: No session 'SESSION' known
[ Adding upstart and powermanager sctripts ]
logname: no login name
Failed to get session path: No session 'SESSION' known
logname: no login name
Failed to get session path: No session 'SESSION' known

Please read the FAQ
http://support.displaylink.com/knowledgebase/topics/103927-troubleshooting-ubuntu 

Installation complete!

Please reboot your computer if you're intending to use Xorg.
logname: no login name
Failed to get session path: No session 'SESSION' known
at this point my external monitors start working, but once i restart, i have to start the installation from the very beginning. i suspect the cause for this is somewhere in these logs which keep appearing at the very end
logname: no login name
Failed to get session path: No session 'SESSION' known
suggestions please **System Details** elementary OS 5.1.7 Hera Built on Ubuntu 18.04.6 LTS Linux 4.15.0-166-generic GTK 3.22.30 Quad-Core Intel® Core™ i5-8250U CPU @ 1.60GHz Intel Corporation UHD Graphics 620 (rev 07) Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21)
Kennedy (113 rep)
Feb 7, 2023, 08:01 AM
1 votes
0 answers
2164 views
How to get three displays on Linux Mint 21
This is a follow-up on [How to get 3 monitors working in Linux Mint 18](https://unix.stackexchange.com/questions/311798/how-to-get-3-monitors-working-in-linux-mint-18). I am on a Dell Laptop with one HDMI output, but the cables are plugged in on a dock. I highly doubt that the laptop brand/type/vers...
This is a follow-up on [How to get 3 monitors working in Linux Mint 18](https://unix.stackexchange.com/questions/311798/how-to-get-3-monitors-working-in-linux-mint-18) . I am on a Dell Laptop with one HDMI output, but the cables are plugged in on a dock. I highly doubt that the laptop brand/type/version plays any role since anyone has the problem *(unless they have two graphic cards in a desktop pc perhaps?)*. I cannot add more than one other monitor to my Linux Mint 21, plugged in at the laptop, which has just one graphical output. Even on Ubuntu, there is just the official [DisplayLink USB Graphics Software for Ubuntu](https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu) for 20.04 and 22.04, but not for 21.04, though for Ubuntu, there was a fix for this to update the firmware on the dock, see [Ubuntu 21.04 displaylink not working - DisplayLink Forum](https://www.displaylink.org/forum/showthread.php?t=67714) , taken from [Ubuntu 21.04 with three external monitors - Ask Ubuntu](https://askubuntu.com/a/1350597/1110856) . And that would not even work since it is needed for Linux Mint, which only builds on Ubuntu, but needs its own driver for the screens. For Linux Mint, I found much the same problems for earlier versions, like [Setting up multiple screens. - Linux Mint Forums](https://forums.linuxmint.com/viewtopic.php?t=287087) . *(needless to say, but for anyone of you testing this, you need to restart your machine after any DisplayLink driver change)* How to get three screens/displays/monitors on Linux Mint 21?
questionto42 (587 rep)
Jan 15, 2023, 07:45 PM • Last activity: Jan 15, 2023, 08:32 PM
0 votes
1 answers
988 views
Manjaro Sway monitor screen through DisplayLink not working
I am trying to have my Lenovo DisplayLink to work with Manjaro Sway but so far could not manage to have screen signal going through it. I updated my linux to kernel 5.15 I installed the corresponding linux-headers to properly install evdi I installed displayconnect When I run `systemctl start displa...
I am trying to have my Lenovo DisplayLink to work with Manjaro Sway but so far could not manage to have screen signal going through it. I updated my linux to kernel 5.15 I installed the corresponding linux-headers to properly install evdi I installed displayconnect When I run systemctl start displaylink.service It crashes When I log back in a shell without and start sway manually it gives the following error:
00:00:00.032 [ERROR] [wlr] [EGL] command: eglQueryDeviceStringEXT, error: EGL_BAD_PARAMETER (0x300c), message: "eglQueryDeviceStringEXT"
00:00:00.032 [ERROR] [wlr] [EGL] command: eglQueryDeviceStringEXT, error: EGL_BAD_PARAMETER (0x300c), message: "eglQueryDeviceStringEXT"
MESA-LOADER: failed to open evdi: /usr/lib/dri/evdi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
failed to load driver: evdi
kmsro: driver missing
MESA-LOADER: failed to open evdi: /usr/lib/dri/evdi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
failed to load driver: evdi
kmsro: driver missing
00:00:00.067 [ERROR] [wlr] [render/egl.c:424] Failed to get DRM device: No such device
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open evdi: /usr/lib/dri/evdi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
failed to load driver: evdi
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
kmsro: driver missing
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open evdi: /usr/lib/dri/evdi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/dri, suffix _dri)
failed to load driver: evdi
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
kmsro: driver missing
2022-09-16 14:02:33 - [swaybg-1.1.1/main.c:579] Missing a required Wayland interface
Any help would be greetly appreciated
zakrapovic (466 rep)
Sep 16, 2022, 12:10 PM • Last activity: Dec 16, 2022, 10:45 PM
3 votes
1 answers
2326 views
How to avoid DisplayLink dock monitors disconnecting intermittently?
## Symptoms Every few minutes/hours the displays connected to the USB3 DisplayLink dock turn off for a few seconds and back on again. ## Hardware - Dell docking station model D6000 - USB3 connection to HP laptop (happens on at least three different models) - DisplayPort connections to two HP monitor...
## Symptoms Every few minutes/hours the displays connected to the USB3 DisplayLink dock turn off for a few seconds and back on again. ## Hardware - Dell docking station model D6000 - USB3 connection to HP laptop (happens on at least three different models) - DisplayPort connections to two HP monitors ## OS - Arch Linux - Ubuntu 20.04 ## Software - displaylink 5.3.1.34-4 and other versions ## Logs I was lucky to catch only a few log entries in the journal while one of these instances happened. I've included *all* the raw logs around this time, including before the disconnect and after the reconnect:
Dec 04 09:54:25 host gnome-shell: libinput error: event5  -       Das Keyboard: client bug: event processing lagging behind by 14ms, your system is too slow
Dec 04 09:55:43 host kernel: usb 4-1.1: Disable of device-initiated U1 failed.
Dec 04 09:55:43 host kernel: usb 4-1.1: Disable of device-initiated U2 failed.
Dec 04 09:55:43 host kernel: cdc_ncm 4-1.1:1.5 ens4u1u1i5: unregister 'cdc_ncm' usb-0000:37:00.0-1.1, CDC NCM
Dec 04 09:55:43 host NetworkManager:   [1607028943.8418] device (ens4u1u1i5): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Dec 04 09:55:43 host dhcpcd: ens4u1u1i5: removing interface
Dec 04 09:55:43 host kernel: usb 4-1.1: Set SEL for device-initiated U1 failed.
Dec 04 09:55:43 host kernel: usb 4-1.1: Set SEL for device-initiated U2 failed.
Dec 04 09:55:44 host kernel: usb 4-1.1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Dec 04 09:55:44 host kernel: usb 4-1.1: Warning! Unlikely big volume range (=767), cval->res is probably wrong.
Dec 04 09:55:44 host kernel: usb 4-1.1:  FU [Mic Capture Volume] ch = 2, val = -4592/7680/16
Dec 04 09:55:44 host kernel: usb 4-1.1: Warning! Unlikely big volume range (=672), cval->res is probably wrong.
Dec 04 09:55:44 host kernel: usb 4-1.1:  FU [Dell USB Audio Playback Volume] ch = 6, val = -10752/0/16
Dec 04 09:55:44 host upowerd: treating change event as add on /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:37:00.0/usb4/4-1/4-1.1
Dec 04 09:55:44 host kernel: cdc_ncm 4-1.1:1.5: MAC-Address: 9c:eb:e8:f2:8e:31
Dec 04 09:55:44 host kernel: cdc_ncm 4-1.1:1.5: setting rx_max = 16384
Dec 04 09:55:44 host kernel: cdc_ncm 4-1.1:1.5: setting tx_max = 16384
Dec 04 09:55:44 host kernel: cdc_ncm 4-1.1:1.5 usb0: register 'cdc_ncm' at usb-0000:37:00.0-1.1, CDC NCM, 9c:eb:e8:f2:8e:31
Dec 04 09:55:44 host kernel: usb 4-1.1: usbfs: process 173165 (ActiveCommandQu) did not claim interface 0 before use
Dec 04 09:55:44 host NetworkManager:   [1607028944.2517] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/9)
Dec 04 09:55:44 host systemd-udevd: Using default interface naming scheme 'v245'.
Dec 04 09:55:44 host boltd: probing: started 
Dec 04 09:55:44 host systemd-udevd: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 04 09:55:44 host kernel: cdc_ncm 4-1.1:1.5 ens4u1u1i5: renamed from usb0
Dec 04 09:55:44 host upowerd: treating change event as add on /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:37:00.0/usb4/4-1/4-1.1
Dec 04 09:55:44 host NetworkManager:   [1607028944.2787] device (usb0): interface index 8 renamed iface from 'usb0' to 'ens4u1u1i5'
Dec 04 09:55:44 host NetworkManager:   [1607028944.2835] device (ens4u1u1i5): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Dec 04 09:55:44 host NetworkManager:   [1607028944.2859] settings: (ens4u1u1i5): created default wired connection 'Wired connection 1'
Dec 04 09:55:44 host systemd-udevd: Using default interface naming scheme 'v245'.
Dec 04 09:55:44 host systemd-udevd: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Dec 04 09:55:44 host dhcpcd: ens4u1u1i5: waiting for carrier
Dec 04 09:55:44 host dhcpcd: ens4u1u1i5: waiting for carrier
Dec 04 09:55:44 host kernel: cdc_ncm 4-1.1:1.5 ens4u1u1i5: network connection: disconnected
Dec 04 09:55:47 host boltd: probing: timeout, done:  (2000000)
## Other This has been observed by a bunch of people on similar software and hardware, not just the ones above. It also happens on Windows 10, for example.
l0b0 (53368 rep)
Dec 3, 2020, 09:29 PM • Last activity: Dec 15, 2022, 11:45 AM
Showing page 1 of 20 total questions