modprobe: ERROR: could not insert 'evdi': Invalid argument

[sawtooth]

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:

# ./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.

if you look into the proposed logs, you can clearly see that the evdi module is not loaded. For example:

# 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.

Any ideas how to circumvent this? Is it really the intel driver? I must say it hasn't really improved the graphics performance (though I see less tearing, but maybe it's wishful thinking) since a certain opengl geometry viewer I am using still works more smoothly on my x220.

Thanks a lot!

[tuxrocket]

Any luck? I'm getting the same errors.

[mlukaszek]

Hi,

Thanks for the report. This looks like a symbol mismatch between modules:

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

Can you capture full logs using the support tool, so we know exactly what are the details of the environment?

Thanks,
Michal

[checksum]

I am getting the same symbol errors trying to install driver on Ubuntu 15.10, with kernel 4.2. How to correct?

[mlukaszek]

As I commented in another thread: can you try rebuilding modules registered with DKMS?

dkms autoinstall

should do the trick.

Thanks,
Michal

[chrisvo]

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.