RPM sources for the DisplayLink USB display adapters
This is the recipe for building the DisplayLink driver in a RPM package for Fedora and CentOS. This driver supports the following device families: - DL-6xxx - DL-5xxx - DL-41xx - DL-3xxx
The package includes the Open Source evdi library.
Packages get automatically built by Travis CI and get uploaded to GitHub releases.
In order to compile the driver, just use make. The Makefile should download the file for you.
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.derThen 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:
$ 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 $ xz -f /lib/modules/$(uname -r)/extra/evdi.koNow any display, hdmi and/or dvi ports on your docking station should work, and the displaylink.service should run.
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 : Disable of device-initiated U1 failed. kernel: usb : Disable of device-initiated U2 failed.
To work around this issue, disable power management for the audio device by commenting out a line in
### Automatically suspend sinks/sources that become idle for too long # load-module module-suspend-on-idle
Generally we want to track the current stable release of the evdi library. However, Fedora kernels are often much newer than those officially supported by that release and it is not uncommon for a new kernel to completely break the build. This can leave you in a situation where you cannot upgrade your kernel without sacrificing your displaylink devices. This is not great if the new kernel has important security or performance fixes.
Fortunately the evdi developers are usually pretty quick to make the appropriate fixes on their
develbranch. You can build a version of the rpm that uses the current edvi
Of course this
develbranch will also include some experimental and less tested changes that may break things in other unexpected ways. So you should prefer the mainline build if it works, but if it breaks, you have the option of making a
The easiest way to contribute with the package is to fork it and send a pull request in GitHub.
There are two main kind of contributions: either a new upstream version is released or a modification in the packaging is proposed.
There is a variable called
RELEASEfor packaging purposes. That variable should be set to 1 when contributing a new upstream version release, and incremented in one when adding any other functionality to the specfile for the same upstream version.
From time to time, DisplayLink will update their driver. We try to do so, but for that we usually rely on pull requests.
We manage three different upstream numbers for versioning:
These variables need to be changed in the following places:
DAEMON_VERSIONis the DisplayLinkManager version
VERSIONis currently the evdi driver version
?download_id=query parameter in DisplayLink website to download the zip
VERSIONis the same as in the Makefile
DAEMON_VERSIONis the same version as in Makefile
Also, please update the changelog at the bottom of the displaylink.spec file.
When changing a packaging rule, please increment the
RELEASEvariable by one in both displaylink.spec and .travis.yml (so that Travis can release the new artifact automatically).