|
|
Thread Tools | Search this Thread | Display Modes |
05-17-2016, 12:47 PM | #1 |
Junior Member
Join Date: May 2016
Posts: 3
|
Dell Precision M3800 / DisplayLink D3100 - displaylink.service failed because ...
Hi DisplayLink team and forum colleagues,
I installed new DisplayLink D3100 driver (1.1.62) on a fresh Ubuntu 16.04 and I get the same error. Reading on internet on some other forums it seems to be a problem with intel graphic driver or something but I'm not 100% sure. I installed Ubuntu 16.04 several times +/- Download software updates option and +/- Install third party software option but the result is the same. DisplayLink service won't start and the display inserted in D3100 is not recognized. Displaylink Driver Installation log: Code:
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. Code:
sudo service displaylink status [sudo] password for crionita: ● displaylink.service - DisplayLink Manager Service Loaded: loaded (/lib/systemd/system/displaylink.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Ma 2016-05-17 15:21:44 EEST; 2s ago Process: 9304 ExecStartPre=/sbin/modprobe evdi (code=exited, status=1/FAILURE) mai 17 15:21:44 UWstation systemd[1]: Failed to start DisplayLink Manager Service. mai 17 15:21:44 UWstation systemd[1]: displaylink.service: Unit entered failed state. mai 17 15:21:44 UWstation systemd[1]: displaylink.service: Failed with result 'exit-code'. Code:
sudo ./DLSupportTool --debug Could someone tell me what should I do 'cuz, obviously, DisplayLink service doesn't start. Any support, help solving this is much appreciated. PS1: the same laptop with Ubuntu 15.10 + DisplayLink Driver 1.0.335 worked fine. PS2: another laptop but the same model with Ubuntu 16.04 + DisplayLink Driver 1.1.62 works fine. wtf?!?! Last edited by chrysstyann; 05-17-2016 at 01:21 PM. |
05-17-2016, 01:33 PM | #2 |
Senior Member
Join Date: Feb 2010
Posts: 386
|
This looks odd. The reason it doesn't work is evdi kernel module not being loaded at all, although from the installation it looks like DKMS successfully built it.
Can you inspect what actually happened in DKMS? Perhaps the build actually failed, but the script does not quite get it? Look for clues in /var/lib/dkms. Thanks, Michal |
05-17-2016, 01:51 PM | #3 |
Junior Member
Join Date: May 2016
Posts: 3
|
Hey,
How did you figure it out that evdi kernel module is not loaded at all? I'm a beginner so.. inspecting what happen in DKMS (/var/lib/dkms) won't enlighten me. So, the problem is at the DisplayLink driver installation process? Anyways, I installed Ubuntu 16.04 2-3 times by now. Is there a possibility that evdi kernel module failed every time (I got the same error every time). What would be the easiest way to fix this issue? LE: got it. From the machine_info.txt Code:
DL driver version: 1.1.62 EVDI kernel module version: None Code:
sudo ./displaylink-driver-1.0.335.run Verifying archive integrity... All good. Uncompressing DisplayLink Linux Driver 1.0.335 100% DisplayLink Linux Software 1.0.335 install script called: install Distribution discovered: Ubuntu 16.04 LTS WARNING: Kernel version 4.4.0-22-generic is not supported. Highest supported version is 3.19. 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 Code:
DL driver version: 1.0.335 EVDI kernel module version: None 1. Why the newest driver gets an error on installation process and the old one no? 2. Why the older driver installation process is fine (besides kernel warning which should be 3.19) and in machine_info.txt evdi kernel module is none? 3. Is there a problem with DKMS package ? Should I install and older version? If yes, where should I find it? Last edited by chrysstyann; 05-17-2016 at 02:07 PM. |
05-17-2016, 02:10 PM | #4 |
Senior Member
Join Date: Feb 2010
Posts: 386
|
It can also be seen here - loading the module is necessary for DisplayLinkManager service to start:
Code:
Process: 9304 ExecStartPre=/sbin/modprobe evdi (code=exited, status=1/FAILURE) Cheers, Michal |
05-17-2016, 02:13 PM | #5 | |
Senior Member
Join Date: Feb 2010
Posts: 386
|
Quote:
Cheers, Michal |
|
05-17-2016, 03:17 PM | #6 |
Junior Member
Join Date: May 2016
Posts: 3
|
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: Code:
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. Last edited by chrysstyann; 05-17-2016 at 03:30 PM. |
08-06-2016, 04:07 PM | #7 |
Junior Member
Join Date: Aug 2016
Posts: 3
|
Same issue here.
Also ubuntu 16.04, XPS 13 Very frustrating as I bought this laptop and the D3100 docking together. Thanks in advance |
08-08-2016, 08:24 AM | #8 |
Junior Member
Join Date: Aug 2016
Posts: 1
|
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 Last edited by CUnknown; 08-08-2016 at 02:49 PM. |
08-12-2016, 11:03 AM | #9 | |
Junior Member
Join Date: Jul 2016
Posts: 4
|
Quote:
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 |
|
|
|