Unable to install DisplayLink driver on Ubuntu 15.10

[laserdex]

Hi,

I am a new user on Ubuntu. I'm currently running Ubuntu 15.10 and trying to install displaylink driver version 1.1.62. I tried following the instructions on http://support.displaylink.com/knowl...ware-on-ubuntu
but can't seem to install.

I currently get this error: Job for displaylink.service failed because the control process exited with error code. See "systemctl status displaylink.service" and "journalctl -xe" for details.

Do need some help.

Thank you.

[mlukaszek]

Have you run the command to check the details? I suspect something went wrong with EVDI kernel module compilation and the job does not start because modprobing evdi fails. Please attach logs.

Cheers,
Michal

[laserdex]

I hope I have posted the right 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 15.10
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.
"
and

"systemctl status displaylink.service
● displaylink.service - DisplayLink Manager Service
Loaded: loaded (/lib/systemd/system/displaylink.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2016-08-22 21:22:08 SGT; 1s ago
Process: 5384 ExecStartPre=/sbin/modprobe evdi (code=exited, status=1/FAILURE)

Aug 22 21:22:08 wx-ubuntu systemd[1]: Failed to start DisplayLink Manager Service.
Aug 22 21:22:08 wx-ubuntu systemd[1]: displaylink.service: Unit entered failed state.
Aug 22 21:22:08 wx-ubuntu systemd[1]: displaylink.service: Failed with result 'exit-code'.
"

and

"


journalctl -xe
--
-- Unit displaylink.service has failed.
--
-- The result is failed.
Aug 22 21:22:23 wx-ubuntu systemd[1]: displaylink.service: Unit entered failed state.
Aug 22 21:22:23 wx-ubuntu systemd[1]: displaylink.service: Failed with result 'exit-code'.
Aug 22 21:22:29 wx-ubuntu systemd[1]: displaylink.service: Service hold-off time over, scheduling res
Aug 22 21:22:29 wx-ubuntu systemd[1]: Stopped DisplayLink Manager Service.
-- Subject: Unit displaylink.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit displaylink.service has finished shutting down.
Aug 22 21:22:29 wx-ubuntu systemd[1]: Starting DisplayLink Manager Service...
-- Subject: Unit displaylink.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit displaylink.service has begun starting up.
Aug 22 21:22:29 wx-ubuntu modprobe[5397]: modprobe: ERROR: could not insert 'evdi': Required key not
Aug 22 21:22:29 wx-ubuntu systemd[1]: displaylink.service: Control process exited, code=exited status
Aug 22 21:22:29 wx-ubuntu systemd[1]: Failed to start DisplayLink Manager Service.
-- Subject: Unit displaylink.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit displaylink.service has failed.
--
-- The result is failed.
Aug 22 21:22:29 wx-ubuntu systemd[1]: displaylink.service: Unit entered failed state.
Aug 22 21:22:29 wx-ubuntu systemd[1]: displaylink.service: Failed with result 'exit-code'.
Aug 22 21:22:34 wx-ubuntu systemd[1]: displaylink.service: Service hold-off time over, scheduling res
Aug 22 21:22:34 wx-ubuntu systemd[1]: Stopped DisplayLink Manager Service.
-- Subject: Unit displaylink.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit displaylink.service has finished shutting down.
Aug 22 21:22:34 wx-ubuntu systemd[1]: Starting DisplayLink Manager Service...
-- Subject: Unit displaylink.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit displaylink.service has begun starting up.
Aug 22 21:22:34 wx-ubuntu modprobe[5400]: modprobe: ERROR: could not insert 'evdi': Required key not
Aug 22 21:22:34 wx-ubuntu systemd[1]: displaylink.service: Control process exited, code=exited status
Aug 22 21:22:34 wx-ubuntu systemd[1]: Failed to start DisplayLink Manager Service.
-- Subject: Unit displaylink.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit displaylink.service has failed.
--
-- The result is failed.
Aug 22 21:22:34 wx-ubuntu systemd[1]: displaylink.service: Unit entered failed state.
Aug 22 21:22:34 wx-ubuntu systemd[1]: displaylink.service: Failed with result 'exit-code'.
lines 2241-2296/2296 (END)
"

[mlukaszek]

OK, so:

EVDI kernel module built successfully

but:

Process: 5384 ExecStartPre=/sbin/modprobe evdi (code=exited, status=1/FAILURE)

because:

Aug 22 21:22:29 wx-ubuntu modprobe[5397]: modprobe: ERROR: could not insert 'evdi': Required key not

The evdi kernel module is not signed. Sign it yourself, or disable secure boot.

Cheers,
Michal

[laserdex]

Hi Michal,

May I know how do I sign the evdi kernel module manually? I tried googling it but it did not really make much sense to me. Do appreciate your help on this

[mlukaszek]

Since we're also using DKMS, the steps for signing evdi will be similar to VirtualBox modules:

https://askubuntu.com/questions/7606...-to-keep-secur

Hope this helps.

Cheers,
Michal