Ubuntu 15.10 + Dell XPS 13 + Dell D3100 Dock - Page 2

chrisvo · 03-25-2016, 01:15 PM

Uninstalling the Intel driver fixed the problem. It appears there is an incompatibility between the version of libdrm used in the latest Intel driver and the version that is used by the displaylink driver.

fightling · 03-27-2016, 10:30 AM

Quote:

Originally Posted by chrisvo

Uninstalling the Intel driver fixed the problem. It appears there is an incompatibility between the version of libdrm used in the latest Intel driver and the version that is used by the displaylink driver.

How did you do that?

unfulvio · 04-02-2016, 06:05 PM

I uninstalled the Intel drivers using Synaptic package manager

basically I looked for packages marked by intel and with source 01.org - I switched them all to use Ubuntu/Wily own packages -- this operation was successfull and I've downgraded to Ubuntu bundled drivers

but still, I would get the same error as chrisvo even after this after installing and trying to start the displaylink manager - same error

perhaps I missed something -- any clues?

thanks!

unfulvio · 04-03-2016, 01:16 PM

I've finally managed to clean my Intel Graphics for Linux drivers following instructions at

http://theclonker.de/archive/89 (in my case I changed the origin of packages to wily, since I use 15.10)

then installing again the Displaylink driver, it was successful

however this solution wasn't optimal.. I noticed a decrease in battery performance and a bug in Google Chrome that forced me to disable the hardware acceleration there - this was fixed by installing the Intel drivers...

mvczettritz · 01-05-2017, 02:12 PM

Ehlo,

I've encountered a very similar issue, while setting my Ubuntu 16.10 up.
Some debugging showed that I had no linux-image-extra-*-generic kernel installed/ loaded. Therefore the drm.ko Kernel module was not present and could not be loaded.
This can be checked easily by running 'modinfo drm', if the program complains about 'no module found' you should check 'dpkg --list | grep linux-image-extra' to see if you have a kernel that comes with drm.
Once installed and rebooted the journalctl errors went away.

Thanks,
Michel/Tofu

01-05-2017, 02:12 PM	#5
mvczettritz Junior Member Join Date: Jan 2017 Posts: 1	drm symbols not found Ehlo, I've encountered a very similar issue, while setting my Ubuntu 16.10 up. Some debugging showed that I had no linux-image-extra-*-generic kernel installed/ loaded. Therefore the drm.ko Kernel module was not present and could not be loaded. This can be checked easily by running 'modinfo drm', if the program complains about 'no module found' you should check 'dpkg --list \| grep linux-image-extra' to see if you have a kernel that comes with drm. Once installed and rebooted the journalctl errors went away. Thanks, Michel/Tofu

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-25-2016, 01:15 PM	#1
chrisvo Junior Member Join Date: Mar 2016 Posts: 9	Uninstalling the Intel driver fixed the problem. It appears there is an incompatibility between the version of libdrm used in the latest Intel driver and the version that is used by the displaylink driver.

04-02-2016, 06:05 PM	#3
unfulvio Junior Member Join Date: Mar 2016 Posts: 8	I uninstalled the Intel drivers using Synaptic package manager basically I looked for packages marked by intel and with source 01.org - I switched them all to use Ubuntu/Wily own packages -- this operation was successfull and I've downgraded to Ubuntu bundled drivers but still, I would get the same error as chrisvo even after this after installing and trying to start the displaylink manager - same error perhaps I missed something -- any clues? thanks!

04-03-2016, 01:16 PM	#4
unfulvio Junior Member Join Date: Mar 2016 Posts: 8	I've finally managed to clean my Intel Graphics for Linux drivers following instructions at http://theclonker.de/archive/89 (in my case I changed the origin of packages to wily, since I use 15.10) then installing again the Displaylink driver, it was successful however this solution wasn't optimal.. I noticed a decrease in battery performance and a bug in Google Chrome that forced me to disable the hardware acceleration there - this was fixed by installing the Intel drivers...