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

mlukaszek · 02-26-2016, 11:15 AM

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

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

Thanks,
Michal

checksum · 03-19-2016, 06:29 AM

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

mlukaszek · 03-22-2016, 10:39 AM

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

Code:

dkms autoinstall

should do the trick.

Thanks,
Michal

chrisvo · 03-25-2016, 12:19 PM

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.

mlukaszek · 03-25-2016, 12:35 PM

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

chrisvo · 03-25-2016, 10:26 PM

Quote:

What are the Intel drivers that you're using exactly?

https://01.org/linuxgraphics/downloads/intel-graphics-installer-linux-1.4.0

Quote:

Are they open sourced or binary?

Not sure. The installer hides much from the user, but it appears to install a different version of libdrm and then installs an i915 driver (it seems to put source for this driver in /usr/src and install via dkms)

I might try installing via the source tarball instead of the Ubuntu installer to see if it changes anything.

checksum · 03-26-2016, 12:27 AM

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

unfulvio · 03-31-2016, 05:08 PM

I might have the same problem

is there a workaround that doesn't break the intel installation and allows displaylink service to run?

03-22-2016, 10:39 AM	#3
mlukaszek 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 should do the trick. Thanks, Michal

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

03-19-2016, 06:29 AM	#2
checksum 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-25-2016, 12:19 PM	#4
chrisvo 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, 12:35 PM	#5
mlukaszek 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-26-2016, 12:27 AM	#7
checksum 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	#8
unfulvio 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?