Ubuntu 15.10 + Dell XPS 13 + Dell D3100 Dock

[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

[fightling]

I have the same problem on a ThinkPad Carbon X1 with ubuntu wily.

since the last kernel update my DisplayLink dock isn't working proper at all. No graphics (xrandr doesn't show the linked displays and also eth over the link breaks down every minute).

I tried what you suggested without success:

$ sudo dkms autoinstall

Kernel preparation unnecessary for this kernel.  Skipping...

Kernel preparation unnecessary for this kernel.  Skipping...

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
Building module:
cleaning build area...
Building module:
cleaning build area....
.
make KERNELRELEASE=4.2.0-30-generic -d V=1 -C /lib/modules/4.2.0-30-generic/build M=/var/lib/dkms/i915-3.9-3.8/0.02/build...make KERNELRELEASE=4.2.0-30-generic -d V=1 -C /lib/modules/4.2.0-30-generic/build M=/var/lib/dkms/i915-3.4-3.2/0.04/build....
make KERNELRELEASE=4.2.0-30-generic -d V=1 -C /lib/modules/4.2.0-30-generic/build M=/var/lib/dkms/i915-3.15-3.13/0.01/build.....(bad exit status: 2)
(bad exit status: 2)
.(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.2.0-30-generic (x86_64)
Consult /var/lib/dkms/i915-3.15-3.13/0.01/build/make.log for more information.
Error! Bad return status for module build on kernel: 4.2.0-30-generic (x86_64)
Consult /var/lib/dkms/i915-3.9-3.8/0.02/build/make.log for more information.
Error! Bad return status for module build on kernel: 4.2.0-30-generic (x86_64)
Consult /var/lib/dkms/i915-3.4-3.2/0.04/build/make.log for more information.

[mlukaszek]

What's in /var/lib/dkms/i915-3.4-3.2/0.04/build/make.log then? Note that it's the i915 module that has problems with recompiling...

Cheers,
Michal

[fightling]

Et voilà!

file attached.

can't even download my own attachment because I'm a Junior Member? m(

[mlukaszek]

/var/lib/dkms/i915-3.4-3.2/0.04/build/include/drm/drmP.h:77:17: fatal error: drm.h: No such file or directory

You need libdrm-dev package (exact name depending on the distribution) to be installed first.

Hope this helps,

Cheers,
Michal

[Maurix]

I also had to modify driver source as follows:

evdi_modeset.c:148

drm_dev_set_unique(dev, dev_name(dev->dev));

evdi_encoder.c:72

status = drm_encoder_init(dev, encoder, &evdi_enc_funcs, DRM_MODE_ENCODER_TMDS, dev_name(dev->dev));

[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*"