No, we're do not package releases to .deb/.rpm/other - I think distro maintainers know specifics of their distros better than us...

Cheers,
Michal

Hi Michal,

So, I just installed the new driver (displaylink-driver-1.3.52) to test but this doesn't work at all with this monitor :-/

Looking at syslog I can see it getting detected as a USB device but doesn't appear to do anything after that.

Please post logs. Also, make sure that you allow the screen to be connected for about a minute before you give up and unplug - there is a different firmware used with the device when you switch driver versions.

Cheers,
Michal

Hi Michal,


Ok, so there seems like several different things going on on my machine - Id been previously using the nvidia X server + intel X server (I need the nvidia one for USBC monitor support) but using the intel server, changed via nvidia-settings, for use with the external monitor on the road as that worked OK with driver 1.1.62.

Now, it seems that if I try to install or uninstall with the intel server in use, the machine locks up completely with no associated information in syslog.

So off the back of that I've rolled everything back to use nouveau temporarily. Now it seems I can reinstall 1.3.52 which I've plugged in and left for a few minutes. It still doesn't work but syslog looks as follows which is a step closer but repeats ad-nauseum :

Feb 20 15:22:16 zed systemd[1]: Started Session c3 of user pev.
Feb 20 15:22:19 zed kernel: [ 40.769570] usb 1-1: new high-speed USB device number 7 using xhci_hcd
Feb 20 15:22:19 zed kernel: [ 40.949372] usb 1-1: New USB device found, idVendor=17e9, idProduct=ff05
Feb 20 15:22:19 zed kernel: [ 40.949374] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 20 15:22:19 zed kernel: [ 40.949375] usb 1-1: Product: E1659Fwu
Feb 20 15:22:19 zed kernel: [ 40.949376] usb 1-1: Manufacturer: DisplayLink
Feb 20 15:22:19 zed kernel: [ 40.949377] usb 1-1: SerialNumber: GFKE1JA000408
Feb 20 15:22:19 zed mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Feb 20 15:22:19 zed mtp-probe: bus: 1, device: 7 was not an MTP device
Feb 20 15:22:19 zed gnome-session[2734]: (gnome-software:2893): Gs-WARNING **: failed to call gs_plugin_add_updates_historical on fwupd: failed to start fwupd: Error calling StartServiceByName for org.freedesktop.fwupd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.fwupd': timed out
Feb 20 15:22:19 zed gnome-session[2734]: (gnome-software:2893): Gs-WARNING **: failed to call gs_plugin_refine on appstream: cannot process file of type text/plain
Feb 20 15:22:20 zed systemd[1]: Starting DisplayLink Manager Service...
Feb 20 15:22:20 zed sh[3454]: modprobe: ERROR: could not insert 'evdi': Invalid argument
Feb 20 15:22:20 zed sh[3454]: Module evdi/1.3.52 already installed on kernel 4.4.0-59-generic/x86_64
Feb 20 15:22:20 zed sh[3454]: modprobe: ERROR: could not insert 'evdi': Invalid argument
Feb 20 15:22:20 zed systemd[1]: dlm.service: Control process exited, code=exited status=1
Feb 20 15:22:20 zed systemd[1]: Failed to start DisplayLink Manager Service.
Feb 20 15:22:20 zed systemd[1]: dlm.service: Unit entered failed state.
Feb 20 15:22:20 zed systemd[1]: dlm.service: Failed with result 'exit-code'.
Feb 20 15:22:20 zed systemd-udevd[3429]: Process '/opt/displaylink/udev.sh /dev usb-001-007-DisplayLink_E1659Fwu_GFKE1JA000408 /dev/bus/usb/001/007' failed with exit code 1.

Feb 20 15:22:25 zed systemd[1]: dlm.service: Service hold-off time over, scheduling restart.
Feb 20 15:22:25 zed systemd[1]: Stopped DisplayLink Manager Service.
Feb 20 15:22:25 zed systemd[1]: Starting DisplayLink Manager Service...
Feb 20 15:22:25 zed sh[3578]: modprobe: ERROR: could not insert 'evdi': Invalid argument
Feb 20 15:22:25 zed sh[3578]: Module evdi/1.3.52 already installed on kernel 4.4.0-59-generic/x86_64
Feb 20 15:22:25 zed sh[3578]: modprobe: ERROR: could not insert 'evdi': Invalid argument
Feb 20 15:22:25 zed systemd[1]: dlm.service: Control process exited, code=exited status=1
Feb 20 15:22:25 zed systemd[1]: Failed to start DisplayLink Manager Service.
Feb 20 15:22:25 zed systemd[1]: dlm.service: Unit entered failed state.
Feb 20 15:22:25 zed systemd[1]: dlm.service: Failed with result 'exit-code'.

There's a problem with loading evdi module. Might it be out of date in your dkms tree for any reason?
Can you try to rebuild it?

Cheers,
Michal

I don't think so :

root@zed:~# dkms --verbose autoinstall
root@zed:~# dkms --verbose status
bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed
evdi, 1.3.52, 4.4.0-21-generic, x86_64: installed
evdi, 1.3.52, 4.4.0-59-generic, x86_64: installed
root@zed:~# uname -r
4.4.0-59-generic

This would indicate a problem however :

root@zed:~# file /lib/modules/4.4.0-59-generic/updates/dkms/evdi.ko
/lib/modules/4.4.0-59-generic/updates/dkms/evdi.ko: empty
root@zed:~# ls -l /lib/modules/4.4.0-59-generic/updates/dkms/evdi.ko
-rw-r--r-- 1 root root 0 Feb 20 15:08 /lib/modules/4.4.0-59-generic/updates/dkms/evdi.ko

root@zed:~# mv /lib/modules/4.4.0-59-generic/updates/dkms/evdi.ko /lib/modules/4.4.0-59-generic/updates/dkms/evdi.ko.empty
root@zed:~# ~pev/Downloads/displaylink-driver-1.3.52.run
Verifying archive integrity... All good.
Uncompressing DisplayLink Linux Driver 1.3.52 100%
DisplayLink Linux Software 1.3.52 install script called: install
Distribution discovered: Ubuntu 16.04.2 LTS
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-ubuntu-1604/DisplayLinkManager
Installing libraries
Installing firmware packages
Installing license file
Adding udev rule for DisplayLink DL-3xxx/5xxx devices
root@zed:~# find /lib/modules/$(uname -r) | grep evdi
/lib/modules/4.4.0-59-generic/updates/dkms/evdi.ko.empty

Trying manually :

root@zed:~/displaylink-1.3.52# dkms build evdi/1.3.52

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area....(bad exit status: 2)
make KERNELRELEASE=4.4.0-59-generic all INCLUDEDIR=/lib/modules/4.4.0-59-generic/build/include KVERSION=4.4.0-59-generic DKMS_BUILD=1.....
cleaning build area....(bad exit status: 2)

DKMS: build completed.
root@zed:~/displaylink-1.3.52# echo $?
0

Finally - it looks like dkms doesnt set KERNELRELEASE for make and for whatever reason this doesn't get picked up on by displaylink-installer.sh.

root@zed:/usr/src# dkms remove evdi/1.3.52 --all

-------- Uninstall Beginning --------
Module: evdi
Version: 1.3.52
Kernel: 4.4.0-59-generic (x86_64)
-------------------------------------

Status: This module version was INACTIVE for this kernel.
depmod....

DKMS: uninstall completed.

------------------------------
Deleting module version: 1.3.52
completely from the DKMS tree.
------------------------------
Done.
root@zed:/usr/src# dkms --verbose build evdi/1.3.52

Creating symlink /var/lib/dkms/evdi/1.3.52/source ->
/usr/src/evdi-1.3.52

DKMS: add completed.

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
make clean DKMS_BUILD=1
/lib/modules//build
make KBUILD_VERBOSE=1 SUBDIRS=/var/lib/dkms/evdi/1.3.52/build SRCROOT=/var/lib/dkms/evdi/1.3.52/build -C /lib/modules//build clean
make[1]: *** /lib/modules//build: No such file or directory. Stop.
Makefile:25: recipe for target 'clean' failed
make: *** [clean] Error 2
(bad exit status: 2)
{ make KERNELRELEASE=4.4.0-59-generic all INCLUDEDIR=/lib/modules/4.4.0-59-generic/build/include KVERSION=4.4.0-59-generic DKMS_BUILD=1; } >> /var/lib/dkms/evdi/1.3.52/build/make.log 2>&1

make clean DKMS_BUILD=1
/lib/modules//build
make KBUILD_VERBOSE=1 SUBDIRS=/var/lib/dkms/evdi/1.3.52/build SRCROOT=/var/lib/dkms/evdi/1.3.52/build -C /lib/modules//build clean
make[1]: *** /lib/modules//build: No such file or directory. Stop.
Makefile:25: recipe for target 'clean' failed
make: *** [clean] Error 2
(bad exit status: 2)

DKMS: build completed.
root@zed:/usr/src# echo $?
0

Changing the head of /usr/src/evdi-1.3.52/Makefile to the following fixes the dmks build :

ifneq ($(DKMS_BUILD),)

# DKMS

ifeq ($(KERNELRELEASE),)
KERNELRELEASE := $(shell uname -r)
endif



After that I can load up the module and the monitor starts working. Anecdotally it feels a lot less laggy than 1.1.65. However If I move the monitor arrangement from default I get the same old problem where it's not re-drawing the screen properly...