02-14-2018, 07:06 PM | #1 |
Junior Member
Join Date: Feb 2018
Posts: 2
|
DisplayLink Won't Install on Ubuntu 17.10
Hi Folks,
Getting a strange issue with the latest versions of Ubuntu. Doesn't matter the distro or spin I'm using as the problem persists across the below version/spins/derivatives of Ubuntu. Ubuntu 16.04.3 & 17.10 Ubuntu Mate 16.04.3 & 17.10 Ubuntu Budgie 16.04.3 & 17.10 Linux Mint (latest version) Elementary OS (Loki) I update the OS, install DKMS then go to run the setup script and this is the output for all the above distros: Verifying archive integrity... All good. Uncompressing DisplayLink Linux Driver 4.1.9 100% DisplayLink Linux Software 4.1.9 install script called: install Distribution discovered: Ubuntu 17.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-ubuntu-1604/DisplayLinkManager Installing libraries Installing firmware packages Installing licence file Adding udev rule for DisplayLink DL-3xxx/5xxx devices Please read the FAQ http://support.displaylink.com/knowl...hooting-ubuntu So obviously it's failing. Are there any logs that I can nab that might tell us why? If so how can I get them for you? Thanks, Balt |
02-15-2018, 07:22 AM | #2 |
Senior Member
Join Date: Feb 2010
Posts: 386
|
This looks like a successful installation, the information about FAQ is important to read though. Logs can be captured by Linux Support Tool: https://support.displaylink.com/know...to-displaylink
Regards, Michal |
02-16-2018, 09:38 AM | #3 |
Junior Member
Join Date: Feb 2018
Posts: 3
|
Similar Issue...
Hi, I have exactly the same issue,
Do have a look at the attachments, I ran the DLSupport Tool and have attached the logs |
02-16-2018, 09:52 AM | #4 |
Senior Member
Join Date: Feb 2010
Posts: 386
|
@boltbeard: your logs show you're running with:
[ 0.000000] Secure boot enabled and kernel locked down As with any DKMS-built module, evdi, which is a part of the driver package cannot be run unsigned. You need to either sign the module yourself (harder), or disable secure boot in your BIOS settings. Cheers, Michal |
02-16-2018, 03:47 PM | #5 |
Junior Member
Join Date: Feb 2018
Posts: 3
|
@mlukaszek: I am not too happy with the option of disabling secure boot in the BIOS, I'll take the signing the module harder myself option.
Although I'm open to any option that helps me use the dock properly. I'm not that good a developer, but if your could point me to the guide/documentation of both the options I'll be happy to do this and see if it solves the problem, if it does, it may solve a lot of other peoples problems too. Thanks in advance and best regards |
02-16-2018, 11:03 PM | #6 |
Super Moderator
Join Date: Jan 2015
Posts: 437
|
DisplayLink has posted this information here -> https://support.displaylink.com/know...-with-uefi-sec
They have all their Ubuntu support information listed here -> https://support.displaylink.com/know...hooting-ubuntu |
02-19-2018, 03:00 PM | #7 |
Junior Member
Join Date: Feb 2018
Posts: 2
|
So after a bit of poking around I discovered something in both Ubuntu 17.10 and Ubuntu Budgie 17.10. If you open 'Display' the external monitors don't show up. What I had to do was hit Fn+F8 on my laptop's keyboard (a Dell) to push the extend the display when connected to the dock. Once I did that one monitor came to life and the second monitor was still dark but both showed up in 'displays'. A little tweaking there and hitting 'Apply' made both external displays work. Weird that they weren't automatically extended to (like every other OS we use). Oh well. Hope this helps some folks.
|
02-20-2018, 07:21 AM | #8 | ||
Junior Member
Join Date: Feb 2018
Posts: 3
|
Quote:
Quote:
|
||
|
|