Dell Precision M3800 / DisplayLink D3100 - displaylink.service failed because ...

[mlukaszek]

Originally Posted by chrysstyann

Hey,
The installation log says that evdi kernel module is installed but on machine_info.txt is saying something else.

DL driver version: 1.0.335
EVDI kernel module version: None

The support tool is actually trying to query a running, loaded evdi kernel module. Seeing "None" here indicates you can't read /sys/modules/evdi/version - which may mean that it either doesn't exist (module is not loaded), or you don't have permissions to read it.

Cheers,
Michal

[chrysstyann]

I have installed Ubuntu 16.04 again because I messed things there.
Now, after the installation I run just:
1. sudo apt-get update (for repos);
2. sudo apt-get install dkms;
3. sudo ./displaylink-driver-1.1.62.run;
...and nothing else.
Do you think I have to run something else first?
According to installation page, "If you are on an amd64 system that boots with UEFI, you will also need the matching signed kernel: sudo apt-get install linux-signed-generic-lts-utopic". My machine is with UEFI but to another laptop (same model) I didn't install linux-signed-generic-lts-utopic (also UEFI enabled in BIOS) and the display port is working like a charm.

And I have the same logs:

sudo ./displaylink-driver-1.1.62.run
Verifying archive integrity... All good.
Uncompressing DisplayLink Linux Driver 1.1.62  100%  
DisplayLink Linux Software 1.1.62 install script called: install
Distribution discovered: Ubuntu 16.04 LTS
Installing
Configuring EVDI DKMS module
Registering EVDI kernel module with DKMS
Building EVDI kernel module with DKMS
Installing EVDI kernel module to kernel tree
EVDI kernel module built successfully
Installing x64/DisplayLinkManager
Installing libraries
Installing firmware packages
Installing license file
Adding udev rule for DisplayLink DL-3xxx/5xxx devices
Starting DLM systemd service
Created symlink from /etc/systemd/system/graphical.target.wants/displaylink.service to /lib/systemd/system/displaylink.service.
Job for displaylink.service failed because the control process exited with error code. See "systemctl status displaylink.service" and "journalctl -xe" for details.

Attached is the folder in /var/lib/dkms. Please rename dkms.zip to dkms.tar as I couldn't attach it otherwise.

[Mrmice]

Same issue here.
Also ubuntu 16.04, XPS 13
Very frustrating as I bought this laptop and the D3100 docking together.

Thanks in advance

[CUnknown]

It looks like I'm having the same issue after a complete reinstall of Ubuntu 16.04 to enable full disk encryption and secure boot.

Previously, it was working fine (also Ubuntu 16.04 x64).

In the syslog it shows the error message: modprobe[11418]: modprobe: ERROR: could not insert 'evdi': Required key not available

[Bacms]

Originally Posted by CUnknown

It looks like I'm having the same issue after a complete reinstall of Ubuntu 16.04 to enable full disk encryption and secure boot.

Previously, it was working fine (also Ubuntu 16.04 x64).

In the syslog it shows the error message: modprobe[11418]: modprobe: ERROR: could not insert 'evdi': Required key not available

You probably need to re-sign your new kernel. This happens to me every time ubuntu updates it's kernel. Simply type:

sudo /usr/src/linux-headers-4.4.0-31-generic/scripts/sign-file sha256 ./EVDI.priv ./EVDI.der $(modinfo -n evdi)

Replacing the version of the headers by your own version