crashdummy/Displaylink

Project ID: 86824

Description

Displaylink

Note: This is a reference driver for supported DisplayLink® USB graphics device that is incorporated in your dock, adapter or monitor. However, please note that your original equipment manufacturer (OEM) provides drivers for your specific monitor, dock or adapter on their website, etc. DisplayLink recommends that you check with your OEM about recommended driver updates for your monitor, dock or adapter. An OEM may not provide technical support for issues that arise from the use of this driver.

sudo modinfo -n evdi /lib/modules/5.10.19-200.fc33.x86_64/extra/evdi.ko.xz sudo unxz $(modinfo -n evdi) sudo /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 ./MOK.priv \ ./MOK.der /lib/modules/$(uname -r)/extra/evdi.ko sudo xz -f /lib/modules/$(uname -r)/extra/evdi.ko

Now any display, hdmi and/or dvi ports on your docking station should work, and the displaylink-driver.service should run.

Hardware-specific behavior

Dell D6000

When used with the Dell D6000 docking station, DisplayLink 5.1.26 regularly loses communication with attached monitors, causing them to go blank and enter power-saving mode. At the time the monitors blank, the kernel logs two error messages:

kernel: usb <xxx>: Disable of device-initiated U1 failed. kernel: usb <xxx>: Disable of device-initiated U2 failed.

To work around this issue, disable power management for the audio device by commenting out a line in /etc/pulse/default.pa:

### Automatically suspend sinks/sources that become idle for too long # load-module module-suspend-on-idle

Installation Instructions

Installation

Well basically just install it.

# dnf copr enable crashdummy/Displaylink # dnf update # dnf install displaylink -y

This will install basically everything similiar to the new apt repository of synaptics. You can verify everythings working.

$ dkms status evdi/1.12.0, 6.3.0-0.rc7.20230423gt622322f5.361.vanilla.fc38.x86_64, x86_64: installed evdi/1.12.0, 6.3.0-362.vanilla.fc38.x86_64, x86_64: installed $ 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: active (running) since Mon 2023-04-24 09:14:16 CEST; 2h 3min ago Process: 5512 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS) Main PID: 5515 (DisplayLinkMana) Tasks: 52 (limit: 37501) Memory: 199.0M CPU: 17min 43.068s CGroup: /system.slice/displaylink-driver.service └─5515 /usr/libexec/displaylink/DisplayLinkManager Apr 24 09:14:16 crashphyrus systemd[1]: Starting displaylink-driver.service - DisplayLink Driver Service... Apr 24 09:14:16 crashphyrus systemd[1]: Started displaylink-driver.service - DisplayLink Driver Service.

Secure boot

To use displaylink-rpm and the evdi kernel module with secure boot enabled on Fedora you need to sign the module with an enrolled Machine Owner Key (MOK).

First create a self signed MOK:

openssl req -new -x509 -newkey rsa:2048 -keyout MOK.priv -outform DER -out \ MOK.der -nodes -days 36500 -subj "/CN=Displaylink/"

Then register the MOK with secure boot:

sudo mokutil --import MOK.der

Then reboot your Fedora host and follow the instructions to enroll the key.

Now you can sign the evdi module. This must be done for every kernel upgrade:

Active Releases

The following unofficial repositories are provided as-is by owner of this project. Contact the owner directly for bugs or issues (IE: not bugzilla).

Release Architectures Repo Download
Fedora 38 x86_64 (468)* Fedora 38 (124 downloads)
Fedora 39 x86_64 (719)* Fedora 39 (272 downloads)
Fedora 40 x86_64 (243)* Fedora 40 (56 downloads)

* Total number of downloaded packages.