|
|
Thread Tools | Search this Thread | Display Modes |
09-22-2015, 06:16 AM | #1 |
Junior Member
Join Date: Sep 2015
Posts: 1
|
modprobe: ERROR: could not insert 'evdi': Invalid argument
Hello,
first of all, thanks for providing a linux driver! It allowed me at least to start working with my XPS 13 in a multiscreen setup just about when I was thinking of returning it. I have an XPS 13 2015 and the D3100 USB3 docking station, running Ubuntu Gnome 15.04 with 3.19.0-28-generic. I could run with 2 external screens plus the onboard monitor, even though I had a relatively poor graphics performance with lots of tearing and a refresh lag. But it worked, kind of buggy, but it worked. I then tried to install the recently released (for 15.04) Intel Graphics driver for linux, in hopes I would get a performance at least equal to my 6 year old ThinkPad x220. Since then, however, I can not start the DLM service, even though I updated to the newest displaylink-driver-1.0.138. When I run the executable, I get: Code:
# ./displaylink-driver-1.0.138.run install Verifying archive integrity... All good. Uncompressing DisplayLink Linux Driver 1.0.138 100% DisplayLink Linux Software 1.0.138 install script called: install install Distribution discovered: Ubuntu 15.04 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. See "systemctl status displaylink.service" and "journalctl -xe" for details. Code:
# journalctl -xe ... more symbol errors like below ... Sep 22 08:09:41 sawtoothxps kernel: evdi: Unknown symbol drm_crtc_helper_set_config (err -22) Sep 22 08:09:41 sawtoothxps kernel: evdi: disagrees about version of symbol drm_prime_gem_destroy Sep 22 08:09:41 sawtoothxps kernel: evdi: Unknown symbol drm_prime_gem_destroy (err -22) Sep 22 08:09:41 sawtoothxps modprobe[29997]: modprobe: ERROR: could not insert 'evdi': Invalid argument Sep 22 08:09:41 sawtoothxps systemd[1]: displaylink.service: control process exited, code=exited status=1 Sep 22 08:09:41 sawtoothxps 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 22 08:09:41 sawtoothxps systemd[1]: Unit displaylink.service entered failed state. Sep 22 08:09:41 sawtoothxps systemd[1]: displaylink.service failed. Thanks a lot! |
02-25-2016, 08:59 PM | #2 |
Junior Member
Join Date: Feb 2016
Posts: 1
|
Any luck? I'm getting the same errors.
|
02-26-2016, 10:15 AM | #3 |
Senior Member
Join Date: Feb 2010
Posts: 386
|
Hi,
Thanks for the report. This looks like a symbol mismatch between modules: Code:
Sep 22 08:09:41 sawtoothxps kernel: evdi: Unknown symbol drm_crtc_helper_set_config (err -22) Sep 22 08:09:41 sawtoothxps kernel: evdi: disagrees about version of symbol drm_prime_gem_destroy Sep 22 08:09:41 sawtoothxps kernel: evdi: Unknown symbol drm_prime_gem_destroy (err -22) Sep 22 08:09:41 sawtoothxps modprobe[29997]: modprobe: ERROR: could not insert 'evdi': Invalid argument Thanks, Michal |
03-19-2016, 05:29 AM | #4 |
Junior Member
Join Date: Mar 2016
Posts: 3
|
I am getting the same symbol errors trying to install driver on Ubuntu 15.10, with kernel 4.2. How to correct?
|
03-22-2016, 09:39 AM | #5 |
Senior Member
Join Date: Feb 2010
Posts: 386
|
As I commented in another thread: can you try rebuilding modules registered with DKMS?
Code:
dkms autoinstall Thanks, Michal |
03-25-2016, 11:19 AM | #6 |
Junior Member
Join Date: Mar 2016
Posts: 9
|
This is the same problem I'm having. The module builds fine, but insmod / modprobe fails to load it with these messages. This is on Ubuntu wily, kernel 4.2.0-34-generic, with latest intel drivers installed.
|
03-25-2016, 11:35 AM | #7 |
Senior Member
Join Date: Feb 2010
Posts: 386
|
OK,
What are the Intel drivers that you're using exactly? Are they open sourced or binary? I don't see why this could happen if they were also compiled on your machine with the same version of drm... Unless I'm missing something. Cheers, Michal |
03-25-2016, 09:26 PM | #8 | ||
Junior Member
Join Date: Mar 2016
Posts: 9
|
Quote:
Quote:
I might try installing via the source tarball instead of the Ubuntu installer to see if it changes anything. |
||
03-25-2016, 11:27 PM | #9 |
Junior Member
Join Date: Mar 2016
Posts: 3
|
dkms autoinstall does not fix for me either
Verifying archive integrity... All good. Uncompressing DisplayLink Linux Driver 1.0.335 100% DisplayLink Linux Software 1.0.335 install script called: install 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 The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). Job for displaylink.service failed because the control process exited with error code. See "systemctl status displaylink.service" and "journalctl -xe" for details. The computer I'm trying to get it working on is a NUC - not sure if that matters. http://www.intel.com/content/www/us/...nuc6i5syk.html |
03-31-2016, 05:08 PM | #10 |
Junior Member
Join Date: Mar 2016
Posts: 8
|
I might have the same problem
is there a workaround that doesn't break the intel installation and allows displaylink service to run? |
|
|