Why not just ask the code to be included in the next linux kernel?.

There is a good rpm creator that downloads your driver and creates a fedora RPM package but my distro does not support systemd scriplets.

Unfortunately I don't know how to modify the .specs file.

https://github.com/displaylink-rpm/displaylink-rpm

Come on guys!!!

Regards

Thanks Eder Franco. It worked for me on 18.04

I was able to get working by following:
https://support.displaylink.com/knowledgebase/articles/1181623-displaylink-ubuntu-driver-after-recent-x-upgrades
as mentioned by Andor and finally following Eder's instructions

Try the PADOKA PPA for the stable Intel drivers. Also, you'll need to disable Page Flip in your xorg.conf file.

I am using Ubuntu 17.10, and the steps to get it working are:

- Install DKMS package;
- Remove the cable from usb port;
- Run the installation;
- Reboot and disable security boot on motherboard settings;
- Reconnect the cable;
- Reboot;

Everything is just working fine after this.

I am using Ubuntu 17.10, and the steps to get it working are:

- Install DKMS package;
- Remove the cable from usb port;
- Run the installation;
- Reboot and disable security boot on motherboard settings;
- Replace the cable;
- Reboot;

Everything is just working fine after this.

>> modprobe[12034]: modprobe: ERROR: could not insert 'evdi': Required key not available

Nearly the same error message as above, but substantially the same. I do not believe this is an error from DisplayLink. In my case, it was because of my default BIOS security settings.

My UEFI Bios Secure boot setting was active. I believe it was preventing all third party drivers, DisplayLink included, from installing.

From here: https://askubuntu.com/questions/762254/why-do-i-get-required-key-not-available-when-install-3rd-party-kernel-modules (The post by Pilot6)

It shows two ways to disable it. For my Ubuntu 16.04 LTS, I used:

sudo apt install mokutil
sudo mokutil --disable-validation
..

It will ask you to set up a password of at least 8 chars. Write it down. When you reboot it will ask for random chars within that password string.. char 2, char 7, etc. You will then be able to disable secure boot.

Everything came up fine after this.

got exactly the same problem

Disconnect the usb port to the dock station and rerun the driver installation. That worked for me.

Umm, ok, this was last October, and it's now almost February. Buehler? ... Anyone? ...