Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Linux Drivers do not work with Ubuntu 15.10 / Kernel 4.2 #15

Closed
unfulvio opened this issue Mar 31, 2016 · 13 comments
Closed

Linux Drivers do not work with Ubuntu 15.10 / Kernel 4.2 #15

unfulvio opened this issue Mar 31, 2016 · 13 comments

Comments

@unfulvio
Copy link

I have a Lenovo Thinkvision LT1421

I'm running Ubuntu 15.10 / Kernel 4.2.0-34-generic

I downloaded the linux driver at http://www.displaylink.com/downloads/ubuntu

and ran the bash script, but it failed:

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 15.10
WARNING: Kernel version 4.2.0-34-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
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.

result of systemctl status displaylink.service -l:

displaylink.service - DisplayLink Manager Service
   Loaded: loaded (/lib/systemd/system/displaylink.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Thu 2016-03-31 10:44:44 CEST; 43ms ago
  Process: 8316 ExecStartPre=/sbin/modprobe evdi (code=exited, status=1/FAILURE)

Mar 31 10:44:44 moshimoshi systemd[1]: Failed to start DisplayLink Manager Service.
Mar 31 10:44:44 moshimoshi systemd[1]: displaylink.service: Unit entered failed state.
Mar 31 10:44:44 moshimoshi systemd[1]: displaylink.service: Failed with result 'exit-code'.

result of journalctl -xe:

Mar 31 10:45:47 moshimoshi kernel: evdi: disagrees about version of symbol drm_fb_helper_initial_config
Mar 31 10:45:47 moshimoshi kernel: evdi: Unknown symbol drm_fb_helper_initial_config (err -22)
Mar 31 10:45:47 moshimoshi kernel: evdi: disagrees about version of symbol drm_framebuffer_reference
Mar 31 10:45:47 moshimoshi kernel: evdi: Unknown symbol drm_framebuffer_reference (err -22)
Mar 31 10:45:47 moshimoshi kernel: evdi: disagrees about version of symbol drm_gem_put_pages
Mar 31 10:45:47 moshimoshi kernel: evdi: Unknown symbol drm_gem_put_pages (err -22)
Mar 31 10:45:47 moshimoshi kernel: evdi: disagrees about version of symbol drm_connector_unplug_all
Mar 31 10:45:47 moshimoshi kernel: evdi: Unknown symbol drm_connector_unplug_all (err -22)
Mar 31 10:45:47 moshimoshi kernel: evdi: disagrees about version of symbol drm_crtc_helper_set_config
Mar 31 10:45:47 moshimoshi kernel: evdi: Unknown symbol drm_crtc_helper_set_config (err -22)
Mar 31 10:45:47 moshimoshi kernel: evdi: disagrees about version of symbol drm_prime_gem_destroy
Mar 31 10:45:47 moshimoshi kernel: evdi: Unknown symbol drm_prime_gem_destroy (err -22)
Mar 31 10:45:47 moshimoshi modprobe[8411]: modprobe: ERROR: could not insert 'evdi': Invalid argument
Mar 31 10:45:47 moshimoshi systemd[1]: displaylink.service: Control process exited, code=exited status=1
Mar 31 10:45:47 moshimoshi systemd[1]: Failed to start DisplayLink Manager Service.
-- Subject: Unit displaylink.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit displaylink.service has failed.
-- 
-- The result is failed.
Mar 31 10:45:47 moshimoshi systemd[1]: displaylink.service: Unit entered failed state.
Mar 31 10:45:47 moshimoshi systemd[1]: displaylink.service: Failed with result 'exit-code'.

Is there anything I can do or try? Anybody got this to work with Ubuntu 15.10?

I understood that support for kernel 4.x is absent, but soon 16.04 LTS is out of beta next month and current 15.x and 16.x will be probably the most used distros with kernel 4.x - is there plan to support it anytime soon?

Thanks
This was referenced Mar 31, 2016
Closed
Closed
@displaylink-mlukaszek
Copy link
Contributor

I think this has been reported on DisplayLink's forum, too. Root cause looks like an Intel driver compiled with a different version of libdrm.

@unfulvio
Copy link
Author

thanks, is there any known workaround without causing problems to the main graphics adapter?

I tried sudo apt-get autoremove --purge intel-linux-graphics-installer

but it didn't do a difference, I think it only uninstalls the Intel installer but not the dependencies

@ajbogh
Copy link
Contributor

ajbogh commented Mar 31, 2016

@unfulvio, does your version include the code from PR #10? If not then you might want to modify the files, otherwise you'll need the latest version with PR #10's code.

@unfulvio
Copy link
Author

@ajbogh thanks, I tried the following

  1. uninstalled the driver using sudo bash displaylink-installer uninstall
  2. unpacked again the driver using bash displaylink-driver-1.0.335.run --noexec --keep
  3. replaced the contents of evdi-1.0.335-src.tar.gz with the files found in /module which include the changes in commit from PR Modifying for Linux 4.5 compatibility #10
  4. ran again the installed with sudo bash displaylink-installer install

the result is always the same at the end of the install process:

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

@unfulvio
Copy link
Author

I made another attempt by downgrading grphics drivers to wily (Ubuntu 15.10), thus uninstalling Intel Linux Graphic Drivers 1.4

I did this using Synaptic Package Manager, looked for all Intel packages, and those with https://01.org/l as origin - I ticked them all to downgrade to wily instead of intel origin

this worked successfully and I've restarted afterwards

I've then repeated the steps above (uninstalled and reinstalled Displayink driver, also restarted)

unofrtunately the problem persists - I think installation is ok, but the displaylink service doesn't function (see logs at the beginning of this issue)

I've made another test re-installing the intel drivers later, no difference...

@unfulvio
Copy link
Author

unfulvio commented Apr 2, 2016 •
edited
Loading

I managed to fix the issue using this

http://theclonker.de/archive/89

and uninstalled the Intel Graphics drivers completely -- evidently my approach using Synaptic didn't work well

it took a couple of restarts, then installing the drivers provided by Displaylink site

I have only one issue left -- the screen looks only to be working well while attached on AC via USB hub. It does come with a dual-usb cable but it seems like Ubuntu is not sending enough power still. I'm trying to solve this without needing a powered hub, which would kill the purpose of having a displaylink unit in the first place. I suspect Ubuntu is not sending power on the second usb port. It's not the cable, I tried with another.

@unfulvio unfulvio closed this as completed Apr 2, 2016
@slampenny
Copy link

@unfulvio That link is dead. Any chance you remember what it said? I'm having this same issue.

@unfulvio
Copy link
Author

unfulvio commented Aug 5, 2016

hey @slampenny... as far as I remember the issue came with intel supplied drivers which used a modified package incompatible with displaylink drivers

that link I think suggested a method for removing intel drivers? i can't really remember sorry -- you can do via terminal or using synaptic manager

anyway, all issues are gone since ubuntu 16.04 and latest version of linux drivers published after this ticket was originally open

I think Intel hasn't released yet their drivers for Ubuntu 16.04 -- I haven't run in any performance issue with the native open source drivers yet... would like to use the optimized drivers at some point, will see by then if I will run into the same displaylink issues again... but at least I will have an idea of the problem

hope it helps

cheers

@manfred-chebli
Copy link

anyway, all issues are gone since ubuntu 16.04 and latest version of linux drivers published after this ticket was originally open

I'm not sure about this. I'm having the same problem with ubuntu 16.04 ...

@drmclean
Copy link

drmclean commented Sep 26, 2016 •
edited
Loading

Same. 16:04 install doesn't work suggestions very welcome.

Command:
sudo ./displaylink-driver-1.2.58.run

Output:

Verifying archive integrity... All good.
Uncompressing DisplayLink Linux Driver 1.2.58  100%  
DisplayLink Linux Software 1.2.58 install script called: install
Distribution discovered: Ubuntu 16.04.1 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-ubuntu-1604/DisplayLinkManager
Installing libraries
Installing firmware packages
Installing license file
Adding udev rule for DisplayLink DL-3xxx/5xxx devices
Job for dlm.service failed because the control process exited with error code. See "systemctl status dlm.service" and "journalctl -xe" for details.

Command: systemctl status dlm.service
Output:

dlm.service - DisplayLink Manager Service
   Loaded: loaded (/lib/systemd/system/dlm.service; static; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 2016-09-26 12:10:54 BST; 4s ago
  Process: 30719 ExecStartPre=/sbin/modprobe evdi (code=exited, status=1/FAILURE)
    Tasks: 0
   Memory: 0B
      CPU: 0

Sep 26 12:10:54 drmclean-bboxx systemd[1]: Failed to start DisplayLink Manager Service.
Sep 26 12:10:54 drmclean-bboxx systemd[1]: dlm.service: Unit entered failed state.
Sep 26 12:10:54 drmclean-bboxx systemd[1]: dlm.service: Failed with result 'exit-code'.

Command: journalctl -xe
Output:

Sep 26 12:11:44 drmclean-bboxx modprobe[30823]: modprobe: ERROR: could not insert 'evdi': Required key not available
-- Unit displaylink.service has begun starting up.
Sep 26 12:11:44 drmclean-bboxx modprobe[30823]: modprobe: ERROR: could not insert 'evdi': Required key not available
Sep 26 12:11:44 drmclean-bboxx systemd[1]: displaylink.service: Control process exited, code=exited status=1
Sep 26 12:11:44 drmclean-bboxx systemd[1]: Failed to start DisplayLink Manager Service.
-- Subject: Unit displaylink.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit displaylink.service has failed.
-- 
-- The result is failed.
Sep 26 12:11:44 drmclean-bboxx systemd[1]: displaylink.service: Unit entered failed state.
Sep 26 12:11:44 drmclean-bboxx systemd[1]: displaylink.service: Failed with result 'exit-code'.
Sep 26 12:11:46 drmclean-bboxx systemd[1]: dlm.service: Service hold-off time over, scheduling restart.
Sep 26 12:11:46 drmclean-bboxx systemd[1]: Stopped DisplayLink Manager Service.
-- Subject: Unit dlm.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dlm.service has finished shutting down.
Sep 26 12:11:46 drmclean-bboxx systemd[1]: Starting DisplayLink Manager Service...
-- Subject: Unit dlm.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dlm.service has begun starting up.
Sep 26 12:11:46 drmclean-bboxx modprobe[30827]: modprobe: ERROR: could not insert 'evdi': Required key not available
Sep 26 12:11:46 drmclean-bboxx systemd[1]: dlm.service: Control process exited, code=exited status=1
Sep 26 12:11:46 drmclean-bboxx systemd[1]: Failed to start DisplayLink Manager Service.
-- Subject: Unit dlm.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dlm.service has failed.
-- 
-- The result is failed.
Sep 26 12:11:46 drmclean-bboxx systemd[1]: dlm.service: Unit entered failed state.
Sep 26 12:11:46 drmclean-bboxx systemd[1]: dlm.service: Failed with result 'exit-code'.
Sep 26 12:11:49 drmclean-bboxx systemd[1]: displaylink.service: Service hold-off time over, scheduling restart.
Sep 26 12:11:49 drmclean-bboxx systemd[1]: Stopped DisplayLink Manager Service.
-- Subject: Unit displaylink.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit displaylink.service has finished shutting down.
Sep 26 12:11:49 drmclean-bboxx systemd[1]: Starting DisplayLink Manager Service...
-- Subject: Unit displaylink.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit displaylink.service has begun starting up.
Sep 26 12:11:49 drmclean-bboxx modprobe[30830]: modprobe: ERROR: could not insert 'evdi': Required key not available
Sep 26 12:11:49 drmclean-bboxx systemd[1]: displaylink.service: Control process exited, code=exited status=1
Sep 26 12:11:49 drmclean-bboxx systemd[1]: Failed to start DisplayLink Manager Service.
-- Subject: Unit displaylink.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit displaylink.service has failed.
-- 
-- The result is failed.
Sep 26 12:11:49 drmclean-bboxx systemd[1]: displaylink.service: Unit entered failed state.
Sep 26 12:11:49 drmclean-bboxx systemd[1]: displaylink.service: Failed with result 'exit-code'.

@displaylink-mlukaszek
Copy link
Contributor

Sep 26 12:11:46 drmclean-bboxx modprobe[30827]: modprobe: ERROR: could not insert 'evdi': Required key not available

Have a look at the end of this announcement on DisplayLink forum. evdi kernel module is not signed.

@ethermeister
Copy link

@slampenny leaving this here for reference of anyone that stumbles upon this... https://theclonker.de/removing-the-intel-linux-graphics-driver/

@danbroz
Copy link

danbroz commented Sep 27, 2017

http://web.archive.org/web/20161105062920/https://theclonker.de/removing-the-intel-linux-graphics-driver/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@ajbogh @unfulvio @slampenny @ethermeister @drmclean @displaylink-mlukaszek @danbroz @manfred-chebli