Problem on new Ubuntu 22.04

[davidng]

I am on Proxmox 7.2, and passthrough the displaylink usb to the new VM.
I download the ubuntu-22.04-desktop-amd64.iso from official ubuntu website, and install on this VM
I did not install anything else, as this build is to test the displaylink.


then I donwload the latest displaylink driver from
https://www.synaptics.com/products/d...wnloads/ubuntu
DisplayLink USB Graphics Software for Ubuntu
Ubuntu 20.04, Ubuntu 22.04
Release: 5.6 | May 20, 2022

I then follow the installation guide

sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install dkms
sudo apt-get install libdrm-dev
sudo chmod +x ./displaylink-driver-5.6.0-59.176.run
sudo ./displaylink-driver-5.6.0-59.176.run

after the above command, WithOut Reboot,
I see the displaylink is working.
I checked, it is showing I am using Wayland, NOT X11

echo $XDG_SESSION_TYPE

then I reboot,
displaylink no longer works.
I checked again, it is now showing I am using X11

echo $XDG_SESSION_TYPE

there is no "gear" icon on the user login screen, so I have no way of selecting wayland or x11 on the login screen.
I try to change back to wayland by purge nvidia drive, modifying below config
but reboot, it still show I am using X11, and displaylink is not working.

sudo apt purge nvidia-*
sudo nano /etc/gdm3/custom.conf
add text
WaylandEnable=true

the only way I can make it work is to uninstall the displaylink driver, and install it again, after the driver installation like above, it work again, but then, after reboot, the display link will not work again.


Please help,
1. How can I force ubuntu to use Wayland, so that displaylink works?
or
2. How can I make displaylink work on X11?



My device is WavLink WL-UG3501H
and the usb info is

lsusb
Bus 010 Device 002: ID 17e9:4301 DisplayLink USB3 to HDMI

[davidng]

it seems a bug in the gdm3, as report on below link, in that thread, someone said it got fixed on April
but now is Aug, and I already update to the latest, problem still appear.

https://askubuntu.com/questions/1402...or-wayland-x11

[Ralph]

11/5/2022

I also am having issues with the driver install. I'm running Ubuntu 22.04 ( 5.15.0-50-generic ) after attempting to install and thus needed to revert to the previous kernel after my system would no longer boot. After reverting to kernel 5.15.0-50, the same error occurs.

The installation log from the attempt.

root@ubuntu:/home/ralph/Downloads/displaylink# ./displaylink-driver-5.6.1-59.184.run
Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing DisplayLink Linux Driver 5.6.1-59.184 100%
Distribution discovered: Ubuntu 22.04.1 LTS

Installing
[ Installing EVDI ]
[[ Installing EVDI DKMS module ]]
Creating symlink /var/lib/dkms/evdi/1.12.0/source -> /usr/src/evdi-1.12.0

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.15.0-52-generic all INCLUDEDIR=/lib/modules/5.15.0-52-generic/build/include KVERSION=5.15.0-52-generic DKMS_BUILD=1...(bad exit status: 2)
ERROR (dkms apport): binary package for evdi: 1.12.0 not found
Error! Bad return status for module build on kernel: 5.15.0-52-generic (x86_64)
Consult /var/log/displaylink/evdi_install_make.2022-11-02-1208.log for more information.
Deleting module evdi-1.12.0 completely from the DKMS tree.
ERROR: Failed to install evdi to the kernel tree.
root@ubuntu:/home/ralph/Downloads/displaylink#

Manually attempting to install evdi-dkms

root@ubuntu:/home/ralph/Downloads/displaylink# apt install evdi-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
libevdi0
The following NEW packages will be installed:
evdi-dkms libevdi0
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/43.1 kB of archives.
After this operation, 214 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package evdi-dkms.
(Reading database ... 315931 files and directories currently installed.)
Preparing to unpack .../evdi-dkms_1.9.1-1ubuntu5_all.deb ...
Unpacking evdi-dkms (1.9.1-1ubuntu5) ...
Selecting previously unselected package libevdi0.
Preparing to unpack .../libevdi0_1.9.1-1ubuntu5_amd64.deb ...
Unpacking libevdi0 (1.9.1-1ubuntu5) ...
Setting up evdi-dkms (1.9.1-1ubuntu5) ...
Loading new evdi-1.9.1 DKMS files...
Building for 5.15.0-52-generic
Building initial module for 5.15.0-52-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/evdi-dkms.0.crash'
Error! Bad return status for module build on kernel: 5.15.0-52-generic (x86_64)
Consult /var/lib/dkms/evdi/1.9.1/build/make.log for more information.
dpkg: error processing package evdi-dkms (--configure):
installed evdi-dkms package post-installation script subprocess returned error exit status 10
Setting up libevdi0 (1.9.1-1ubuntu5) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
Errors were encountered while processing:
evdi-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

I may be experiencing issues with the installation of evdi-dkms, but reviewing the forum, I am unable to locate a solution.

Thanks in advance

Any ideas on how to proceed would be a help.

Thanks

Ralph

[Ralph]

After troubleshooting for a considerable time, I remembered that I had previously installed Virtualbox on my system. After removing Virtualbox, the issue installing has been resolved and Displaylink is now working again.

Hopefully, this helps someone else experiencing the same issue.

[thatLockwood]

I had the same issue after upgrading a Ubuntu to from 16.04 to 20.04 and then 22.04 in the same afternoon. When I tried the manual evdi-dkms install I noted some info about missing kernel headers in the log which got me to re-installing the headers.

After rebooting the standard DisplayLink install worked! I'm happily using the drivers with dual monitors on the latest Ubuntu 22.04 on Wayland (Nvidia open source drivers).

Steps:
1. Re-install headers

sudo apt install --reinstall linux-headers-$(uname -r)

2. Reboot

sudo shutdown -r now

[udippel]

Used to be most happy with DisplayLink, earlier, working with a laptop hidden in my drawer, and all screen content on an external monitor.
Then I was hit by that SIGABRT in _iris_batch_flush from iris_fence_flush() bug in ubuntu. After quite some time, a fix was found. Updated to 22.04.1 yesterday, only to find that there is just no DisplayLink-display.
So sad!

Alas, the 'fix found' by thatLockwood is no real fix: using wayland. That's what we had learned earlier. I need a fix for x11.

[Norber.OK]

I have the same displaylink device:
Bus 002 Device 002: ID 17e9:4301 DisplayLink USB3 to HDMI

After upgrading to Ubuntu 22.04 I was not able to display correctly, then I realized that I was having issues with libdvd-pkg so:

1.)
sudo dpkg-reconfigure libdvd-pkg
2.)
sudo apt install --reinstall linux-headers-$(uname -r)
3.)
sudo ./displaylink-driver-5.6.1-59.184.run
4.)
reboot


That worked for me for x11.

[Jonathan Allan]

I did all the steps for installation. I followed the instructions on the official website, followed the forum tips, but nothing works.

When searching for the drive, it lists normally. But the screen does not signal.

lsusb -d 17e9:
Bus 001 Device 002: ID 17e9:03c1 DisplayLink USB graphic adapter

Any tips?

[Thomas Sehrt]

There is a work-around, but unfortunately not the final solution.

My system information:
kernel release
user@linux-laptop:~$ uname -r
6.2.0-32-generic

kernel version
user@linux-laptop:~$ uname -v
#32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2

Check that the DisplayLink device is recognized on the USB bus
user@linux-laptop:~$ lsusb -d 17e9:
user@linux-laptop:~$

DisplayLink is not working. Now I reboot the system within the recovery mode.
GNU GRUB version 2.06
I choose from the lst:
Ubuntu, with Linux 6.2.0-31-generic (recovery mode)

Now all works fine.
user@linux-laptop:~$ lsusb -d 17e9:
Bus 004 Device 003: ID 17e9:6006 DisplayLink Dell Universal Dock D6000
user@linux-laptop:~$

The system information is identical to above. Why is the kernel release
6.2.0-32-generic
running and not
6.2.0-31-generic
as slected from Bootloader?

After several boots the original mis-behaviour is back.

Maybe can this description help to find out what the real root cause for disappearing of the functionality of DisplayLink is.

[rthyriur]

I have a docking station which connects: monitor (HDMI), mouse, keyboard, webcam and printer.
My biggest problem with D-Link on Ubuntu 22.04 is when connecting USB A cable. Then one of three scenario occur:

1) Keyboard and mouse doesn't work. If I type something, nothing happens. If I move the mouse, nothing happens. However, external monitor work.

2) Keyboard and mouse works, but monitor doesn't work. I know this by looking on the monitor of laptop.

3) Keyboard, mouse and monitor works. This is the best case, but happens 1 time of 10 tries.

I didn't have this kind of problems with older Ubuntu LTS versions.

Edit: Very interesting, I just had scenario 1). I disconnected webcam and connected it again. Then I got scenario 3.

I also had the problem that my output sound was gone. See attached screenshot.
I read and tried all commands related to pulseaudio. I had the same problem with Linux Mint
The only thing that works with 100% certainty. is to disconnect my docking station.
100% of the time, the sound options is back.
Webcam got built in mic and speaker. It is generic webcam, can't see any brand.