DisplayLink on Fedora Asahi Remix 38

I bought a displaylink adapater hoping to use it to connect my external display. I had some issues and thought to try the direct hdmi connection in my mac m1 pro as two weeks ago I did see some updates. I am happy to report it is working for me.

I have a dell monitor.

Thank you,

Hello,

I have a problem with dkms. i got this error:

Ɨ dkms.service - Builds and install new kernel modules through DKMS
     Loaded: loaded (/usr/lib/systemd/system/dkms.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Tue 2023-12-12 18:42:00 IST; 55s ago
       Docs: man:dkms(8)
    Process: 892 ExecStart=/usr/sbin/dkms autoinstall --verbose --kernelver 6.6.3-404.asahi.fc39.aarch64+16k (code=exited, status=11)
   Main PID: 892 (code=exited, status=11)
        CPU: 4.952s

Dec 12 18:42:00 fedora dkms[1082]: (bad exit status: 2)
Dec 12 18:42:00 fedora dkms[1606]: Error! Bad return status for module build on kernel: 6.6.3-404.asahi.fc39.aarch64+16k (aarch64)
Dec 12 18:42:00 fedora dkms[1606]: Consult /var/lib/dkms/evdi/1.14.1/build/make.log for more information.
Dec 12 18:42:00 fedora dkms[892]: dkms autoinstall on 6.6.3-404.asahi.fc39.aarch64+16k/aarch64 failed for evdi(10)
Dec 12 18:42:00 fedora dkms[1607]: Error! One or more modules failed to install during autoinstall.
Dec 12 18:42:00 fedora dkms[1607]: Refer to previous errors for more information.
Dec 12 18:42:00 fedora systemd[1]: dkms.service: Main process exited, code=exited, status=11/n/a
Dec 12 18:42:00 fedora systemd[1]: dkms.service: Failed with result 'exit-code'.
Dec 12 18:42:00 fedora systemd[1]: Failed to start dkms.service - Builds and install new kernel modules through DKMS.
Dec 12 18:42:00 fedora systemd[1]: dkms.service: Consumed 4.952s CPU time.

anyone have a solution please ?

The current evdi version seem to be incompatible with the latest kernel version. You need to rebuild and install evdi yourself:

git clone https://github.com/Bidski/evdi.git evdi-bidski
sudo mkdir /usr/src/evdi-1.14.1
sudo cp evdi-bidski/module/* /usr/src/evdi-1.14.1/
sudo dkms build -m evdi -v 1.14.1 --force
sudo dkms install -m evdi -v 1.14.1

then reboot and you should be good to go. Works for me on Gnome but not on Sway.

Source: [CLOSED] Evdi/Displaylink broken after kernel update / Kernel & Hardware / Arch Linux Forums

I have installed on my macbook m1 pro with fedora 38 and it works without problems, but you should compile the evdi drivers first

after following the different steps you guys posted on fedora 39 (that is the evdi recompilation and install of the different packages) I can see that dkms is not crashing anymore but my displaylink-driver keeps crashing and when I start the process with -debug -logging I get random strings any idea ?

After recompiling evdi, I finally managed to open a second screen connected to my MacBook Air (M2) running F39.

This setup is not hot-pluggable, i.e. nothing happens, when I connect an HDMI-adapter and an external screen.

It also does not work with Apple’s Multiport Adapter. Probably this thing is not DisplayLink compatible.

However, when I connect my old HP TPA-B01 USB-C docking station and reboot, the LED on the docking station starts flashing.

After thatsystemctl status displaylink-driver.service still reports a FAILURE.
But, after a systemctl restart displaylink-driver.service my second display comes up.

The maximum resolution is 1920x1080, although the display is 4K-capable (LG bu50nst), but this is probably a limitation of the HP docking station. I’ll try another DisplayLink-compatible docking station and report.

I’ve also seen, that not all HDMI displays seem to work (I did not succeed, e.g. with an older Sony FullHD display).

I’ve found performance to be fairly bad using the upstream driver. There’s already a hack in there
for better performance for amdgpu. If I also apply that for asahi It feels like a native display.
If anyone wants to try, you can install as above:

git clone https://github.com/sdirkwinkel/evdi.git evdi-sdirkwinkel
sudo mkdir /usr/src/evdi-1.14.1
sudo cp evdi-sdirkwinkel/module/* /usr/src/evdi-1.14.1/
sudo dkms build -m evdi -v 1.14.1 --force
sudo dkms install -m evdi -v 1.14.1

Hello everyone,

having recently switched from MacOS to Fedora Asahi Remix 38 I am admittedly still half-baked when it comes to Linux. So I’m hoping for your help!

I have downloaded the driver package and tried to install it. However, the installation is rejected due to missing dependencies although they are already installed:

# sudo /displaylink-driver-5.8.0-63.33.run
Verifying archive integrity...  100%   MDS checksums are Ok. All good.
Uncompressing DisplayLink Linux Driver 5.8.0-63.33  100%
WARNING: This is not an officially supported distribution.
Please use DisplayLink Forum for getting help if you find issues.
[ Installing dependencies ]
Need to update package list. apt update? (Yn) y
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Unsatisfied dependencies. Missing component: mokutil pkg-config libdrm libc6.
This is a fatal error, camot install DisplayLink Linux Software. 

# sudo dnf -y install mokutil
Letzte Prüfung auf abgelaufene Metadaten: vor 0:11:25 am Mo 04 Mãr 2024 15:49:29 CET. 
allow vendor change is disabled. This option is currently not supported for downgrade and distro-sync commands 
Das Paket mokutil-2:0.6.0-7.fc39.aarch64 ist bereits installiert.

# sudo dnf -y install pkg-config
Letzte Prüfung auf abgelaufene Metadaten: vor 0:11:35 am Mo 84 Mar 2024 15:49:29 CET. 
allow vendor change is disabled. This option is currently not supported for downgrade and distro sync commands 
Das Paket pkgconf-pkg-config-1.9.5-2.fc39.aarch64 ist bereits installiert.

# sudo dnf -y install libdrm
Letzte Prüfung auf abgelaufene Metadaten: vor 0:11:42 am Mo 04 Mar 2024 15:49:29 CET. 
allow vendor change is disabled. This option is currently not supported for downgrade and distro-sync commands 
Das Paket libdrm-2.4.120-1.fc39.aarch64 ist bereits installiert.

Can someone please help me?
I would be very grateful - thank you very much!

Gramais

maybe try this (from a post above):
sudo dnf install libdrm libdrm-devel kernel-16k-devel dkms kernel-headers

Thank you @steffen - but unfortunately I had no luck … :frowning:

Any other ideas? Anyone?

# sudo dnf install libdrm libdrm-devel kernel-16k-devel dkms kernel-headers

Letzte Prüfung auf abgelaufene Metadaten: vor 2:14:26 am Do 14 Mär 2024 13:36:31 CET.
allow_vendor_change is disabled. This option is currently not supported for downgrade and distro-sync commands
Das Paket libdrm-2.4.120-1.fc39.aarch64 ist bereits installiert.
Das Paket libdrm-devel-2.4.120-1.fc39.aarch64 ist bereits installiert.
Das Paket kernel-16k-devel-6.6.3-413.asahi.fc39.aarch64 ist bereits installiert.
Das Paket dkms-3.0.12-1.fc39.noarch ist bereits installiert.
Das Paket kernel-headers-6.6.3-413.asahi.fc39.aarch64 ist bereits installiert.
AbhƤngigkeiten sind aufgelƶst.
Nichts zu tun.
Fertig!

# sudo ./displaylink-driver-5.8.0-63.33.run 

Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing DisplayLink Linux Driver 5.8.0-63.33  100%  
WARNING: This is not an officially supported distribution.
Please use DisplayLink Forum for getting help if you find issues.
[ Installing dependencies ]
Need to update package list.
apt update? (Y/n) y

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
All packages are up to date.
Unsatisfied dependencies. Missing component: mokutil pkg-config libdrm libc6.
This is a fatal error, cannot install DisplayLink Linux Software.
# 

For me, it’s not working with a ā€˜Lenovo usb-c mini dock’ on my MacBook Pro M1. I think the dock in not supported.

The DisplayLink installation gave an error in its output, but finished with a success message.
I did try to compile the evdi module but got this message:

Module evdi/1.14.1 already installed on kernel 6.6.3-414.asahi.fc39.aarch64+16k (aarch64), skip. You may override by specifying --force.

When checking the status, I get this output:

systemctl status displaylink-driver.service
ā—‹ displaylink-driver.service - DisplayLink Driver Service
     Loaded: loaded (/usr/lib/systemd/system/displaylink-driver.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

Is it worth trying to use libdlo?

Hello there.

I’ve been trying to run Hyprland over Displaylink without success.
Has anyone been more successful than me ?

I’m running into the same issues as in this thread.

If anyone has leads, it’s the only thing that keeps me away from asahi for the moment.

Just to let this helpful thread up to date.
Displaylink solution is still working (mac book air M2, fedora 40, kernel 6.8.9-406), only with the hack from Steffen concerning evdi :

git clone https://github.com/sdirkwinkel/evdi.git evdi-sdirkwinkel
sudo mkdir /usr/src/evdi-1.14.1
sudo cp evdi-sdirkwinkel/module/* /usr/src/evdi-1.14.1/
sudo dkms build -m evdi -v 1.14.1 --force
sudo dkms install -m evdi -v 1.14.1

Furthurmore, I’m using an old displaylink ready device dell DA100 with USB-A input, connected to the mac book air through an USB-C dock.

Hell, thanks very much for your answer.

I’m able to use DisplayLink in GNOME, probably KDE Plasma, but when using Hyprland WM it just crashes. I also have strange behaviors when using i3 / Sway (i3 on Wayland).

Also, even though it works, under GNOME for X11, it’s very very laggy with very poor performance (graphically speaking). Better on GNOME for Wayland but still not great.

Do you have any idea ?

I’ve been trying to get this to work, but I get an error when running the displaylink-driver.xxx.run file. It is reporing:

make -j10 KERNELRELEASE=6.10.5-400.asahi.fc40.aarch64+16k all INCLUDEDIR=/lib/modules/6.10.5-400.asahi.fc40.aarch64+16k/build/include KVERSION=6.10.5-400.asahi.fc40.aarch64+16k DKMS_BUILD=1
Error! Bad return status for module build on kernel: 6.10.5-400.asahi.fc40.aarch64+16k (aarch64)
Consult /var/lib/dkms/evdi/1.14.4/build/make.log for more information.

However I am not seeing a file at /var/lib/dkms/evdi/1.14.4/build/make.log

I ended up manually building using this repo and it worked! GitHub - displaylink-rpm/displaylink-rpm: RPM sources for the DisplayLink USB display adapters

1 Like

I have used DisplayLink only once in my classroom, but it had some problems with the resolution and I did not use it for some time now.

Does this work in 41?

https://www.displaylink.org/forum/showthread.php?t=69415

I understand eDP → DP2HDMI and Type-C DP are not supported on MBP 17,1. Are there other options for this device?