02-02-2022, 08:51 AM | #1 |
Junior Member
Join Date: Feb 2022
Posts: 4
|
Upgrade Ubuntu 18.04 / 20.04 DisplayLink broken
Hi there,
after upgrading from Ubuntu 18.04 to 20.04 my previous perfectly working display link is broken. Also many different tries to fix it failed. So going back to community and asking for a new approach. Having a HP 840 G3 and G4 (on both same issue) Tried also different DisplayLink USB Docks with same result Only stable working Dock is the original HP Dock via Dock-Port of Laptop, but uses other connection path. Here my system Code:
uname -a Linux 5.4.0-96-generic #109-Ubuntu SMP Code:
sudo displaylink-installer --help DisplayLink Linux Software 5.4.1-55.174 install script called: --help Distribution discovered: Ubuntu 20.04.3 LTS Installs DisplayLink Linux Software, version 5.4.1-55.174. I have also installed the latest evdi via documented path here https://displaylink.org/forum/showpo...53&postcount=3 Code:
dkms status evdi, 1.10.0, 5.4.0-96-generic, x86_64: installed evdi, 1.10.0, 5.4.0-97-generic, x86_64: installed tp_smapi, 0.43, 5.3.0-61-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-96-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-97-generic, x86_64: installed virtualbox, 6.1.26, 5.3.0-61-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-96-generic, x86_64: installed virtualbox, 6.1.26, 5.4.0-97-generic, x86_64: installed wireguard, 1.0.20201112, 5.3.0-61-generic, x86_64: installed wireguard, 1.0.20201112, 5.4.0-96-generic, x86_64: installed (WARNING! Diff between built and installed module!) wireguard, 1.0.20201112, 5.4.0-97-generic, x86_64: installed (WARNING! Diff between built and installed module!) Code:
lsusb Bus 002 Device 003: ID 17e9:4307 DisplayLink Bus 002 Device 002: ID 2109:0813 VIA Labs, Inc. USB3.0 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 05c8:0383 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP HD Camera Bus 001 Device 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 03f0:521d HP, Inc HP hs3110 HSPA+ Mobile Broadband Device Bus 001 Device 014: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse Bus 001 Device 013: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 001 Device 012: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 007: ID 2109:2813 VIA Labs, Inc. USB2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Code:
systemctl status displaylink-driver.service ● displaylink-driver.service - DisplayLink Driver Service Loaded: loaded (/lib/systemd/system/displaylink-driver.service; static; vendor preset: enabled) Active: active (running) since Wed 2022-02-02 10:28:44 CET; 16min ago Process: 112893 ExecStartPre=/bin/sh -c modprobe evdi || (dkms install $(ls -t /usr/src | grep evdi | head -n1 | s> Main PID: 112898 (DisplayLinkMana) Tasks: 6 (limit: 37705) Memory: 7.0M CGroup: /system.slice/displaylink-driver.service └─112898 /opt/displaylink/DisplayLinkManager Feb 02 10:28:44 systemd[1]: Starting DisplayLink Driver Service... Feb 02 10:28:44 systemd[1]: Started DisplayLink Driver Service. Code:
cat /etc/X11/default-display-manager /usr/sbin/gdm3 Code:
grep '/usr/s\?bin' /etc/systemd/system/display-manager.service ExecStart=/usr/sbin/gdm3 Can anyone help me out of the dark? Code:
xrandr --listproviders Providers: number : 1 Provider 0: id: 0x49 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 9 associated providers: 0 name:Intel Last edited by hkais; 02-08-2022 at 04:18 PM. |
02-19-2022, 07:06 AM | #2 |
Junior Member
Join Date: Feb 2022
Posts: 4
|
noone around with a idea?
|
07-04-2022, 08:23 PM | #3 |
Junior Member
Join Date: Feb 2022
Posts: 4
|
installed 5.6.0 version and still same issue
really no hints? |
07-05-2022, 03:33 PM | #4 |
Junior Member
Join Date: Jul 2022
Posts: 2
|
Same Problem
I am having the same problem. I also noticed that trying to restart displaylink-driver.service
gives the error: Code:
modprobe: ERROR: could not insert 'evdi': Operation not permitted Module evdi/1.11.0 already installed on kernel 5.15.0-40-generic (x86_64). modprobe: ERROR: could not insert 'evdi': Operation not permitted Failed to start DisplayLink Driver Service |
07-05-2022, 03:47 PM | #5 |
Junior Member
Join Date: Jul 2022
Posts: 2
|
Here is the Fix
https://github.com/displaylink-rpm/d...-rpm/issues/66
You need to disable Wayland Then you need to turn off secure boot in your BIOS. In fact I just tested this without disabling Wayland and it works just fine. Disabling secure boot is all you need to do if you are getting the same error as me when you restart displaylink-driver.service Last edited by hambling; 07-05-2022 at 04:25 PM. |
Thread Tools | Search this Thread |
Display Modes | |
|
|