Ubuntu 15.10 + Dell XPS 13 + Dell D3100 Dock

[chrisvo]

Thank you for your response. However the command does not do anything:

vo@ninja:~/Downloads/drivers$ sudo dkms status
bcmwl, 6.30.223.248+bdcom, 4.2.0-16-generic, x86_64: installed
bcmwl, 6.30.223.248+bdcom, 4.2.0-34-generic, x86_64: installed
evdi, 1.0.335, 4.2.0-34-generic, x86_64: installed
i915-4.3.3-4.2.0, 2, 4.2.0-16-generic, x86_64: installed
i915-4.3.3-4.2.0, 2, 4.2.0-34-generic, x86_64: installed
vo@ninja:~/Downloads/drivers$ sudo dkms autoinstall --verbose
vo@ninja:~/Downloads/drivers$

I'll try working with the source code, thanks.

Originally Posted by mlukaszek

Have you attempted to recompile the evdi kernel module after you updated?
The command

dkms autoinstall

should rebuild all modules for the running kernel - this should include evdi.

As far as the source code is concerned, evdi is an open-source project and you can access it in DisplayLink's GitHub. DisplayLink Ubuntu drivers currently use master branch for releases.

Thanks,
Michal

[chrisvo]

Manually building and installing the evdi driver (through dkms) does not fix the problem; it builds and installs successfully but the module won't load:

root@ninja:/usr/src/evdi-1.0.335devel# modprobe evdi
modprobe: ERROR: could not insert 'evdi': Invalid argument
root@ninja:/usr/src/evdi-1.0.335devel# journalctl -xe
Mar 24 10:05:06 ninja kernel: evdi: Unknown symbol drm_platform_init (err -22)
Mar 24 10:05:06 ninja kernel: evdi: disagrees about version of symbol drm_add_edid_modes
Mar 24 10:05:06 ninja kernel: evdi: Unknown symbol drm_add_edid_modes (err -22)
Mar 24 10:05:06 ninja kernel: evdi: disagrees about version of symbol drm_framebuffer_unreference
Mar 24 10:05:06 ninja kernel: evdi: Unknown symbol drm_framebuffer_unreference (err -22)
Mar 24 10:05:06 ninja kernel: evdi: disagrees about version of symbol drm_gem_object_release
Mar 24 10:05:06 ninja kernel: evdi: Unknown symbol drm_gem_object_release (err -22)
Mar 24 10:05:06 ninja kernel: evdi: disagrees about version of symbol drm_send_vblank_event
Mar 24 10:05:06 ninja kernel: evdi: Unknown symbol drm_send_vblank_event (err -22)
Mar 24 10:05:06 ninja kernel: evdi: disagrees about version of symbol drm_fb_helper_fill_var
Mar 24 10:05:06 ninja kernel: evdi: Unknown symbol drm_fb_helper_fill_var (err -22)
Mar 24 10:05:06 ninja kernel: evdi: disagrees about version of symbol drm_gem_dumb_destroy
Mar 24 10:05:06 ninja kernel: evdi: Unknown symbol drm_gem_dumb_destroy (err -22)
Mar 24 10:05:06 ninja kernel: evdi: disagrees about version of symbol drm_gem_handle_create
Mar 24 10:05:06 ninja kernel: evdi: Unknown symbol drm_gem_handle_create (err -22)
Mar 24 10:05:06 ninja kernel: evdi: disagrees about version of symbol drm_object_attach_property
Mar 24 10:05:06 ninja kernel: evdi: Unknown symbol drm_object_attach_property (err -22)
Mar 24 10:05:06 ninja kernel: evdi: disagrees about version of symbol drm_helper_mode_fill_fb_struct
Mar 24 10:05:06 ninja kernel: evdi: Unknown symbol drm_helper_mode_fill_fb_struct (err -22)
Mar 24 10:05:06 ninja kernel: evdi: disagrees about version of symbol drm_mode_copy
...

[mlukaszek]

Are you sure modprobe is actually loading the version you've built? I bet you still have the previous version installed in the kernel module tree. Verbose switch for modprobe should tell you that.

It should be possible to insmod the module you built. If that works, remove the module from /lib/modules/..., copy your rebuilt version over, and run depmod -a to regenerate dependency info - that should heal modprobe.

The longer way for fixing dkms should be:

export EVDI="evdi/1.0.335"
dkms remove $EVDI --all
dkms add $EVDI
dkmd build $EVDI
dkms install $EVDI

Cheers,
Michal

[chrisvo]

Are you sure modprobe is actually loading the version you've built?

Yes, I removed the old one and built and installed (both manually and using dkms) the version from git. I tried both devel and master branches. It builds fine, but refuses to be loaded, filling the log with messages about "evdi: Unknown symbol drm *" and "evdi: disagrees about version of drm*"

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

[fightling]

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?

[chrisvo]

How did you do that?

This post has pretty good instructions for removal of the Intel driver, if you used the Intel installer:
http://askubuntu.com/questions/34339...-center-driver

[unfulvio]

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]

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

[chrisvo]

I noticed a decrease in battery performance and a bug in Google Chrome that forced me to disable the hardware acceleration there

Yes, it would be ideal to be able to use the latest Intel drivers with the DisplayLink driver...

Also with the DisplayLink driver I've noticed high CPU usage even when I am not connected to the docking station, where I've had to manually kill DisplayLinkManager.