USB screen (ASUS MB168B+) no longer detected after latest Ubuntu update

[fishjh2]

Hi,

I downloaded the latest Ubuntu updates today, and the asus screen is no longer being detected by ubuntu (it works fine when I boot into Windows still).

Reports are attached. Any help would be greatly appreciated, as really value the use of the screen.

Many thanks.

[neovin]

Hello,

I have the same issue after Ubuntu 14.04.1 updates of yesterday, the screen plugged on display link device is not working anymore with precedent (1.0.335) or new driver (1.1.62).

The updates applied in my case are the following in /var/log/apt/history.log:

Start-Date: 2016-07-19  18:05:13
Commandline: aptdaemon role='role-commit-packages' sender=':1.88'
Install: linux-headers-3.19.0-65:amd64 (3.19.0-65.73~14.04.1), libefivar0:amd64 (0.21-1~14.04.2), linux-headers-3.16.0-77:amd64 (3.16.0-77.99~14.04.1), linux-image-extra-3.19.0-65-generic:amd64 (3.19.0-65.73~14.04.1), linux-image-3.19.0-65-generic:amd64 (3.19.0-65.73~14.04.1), linux-image-3.16.0-77-generic:amd64 (3.16.0-77.99~14.04.1), linux-headers-3.19.0-65-generic:amd64 (3.19.0-65.73~14.04.1), mokutil:amd64 (0.3.0-0ubuntu3~14.04.1), linux-headers-3.16.0-77-generic:amd64 (3.16.0-77.99~14.04.1), linux-signed-image-3.19.0-65-generic:amd64 (3.19.0-65.73~14.04.1), linux-image-extra-3.16.0-77-generic:amd64 (3.16.0-77.99~14.04.1), linux-signed-image-3.16.0-77-generic:amd64 (3.16.0-77.99~14.04.1)
Upgrade: shim-signed:amd64 (1.9+0.8-0ubuntu2,1.17~14.04.1+0.8-0ubuntu2), linux-signed-image-generic-lts-utopic:amd64 (3.16.0.76.67, 3.16.0.77.68), grub-efi-amd64-bin:amd64 (2.02~beta2-9ubuntu1.8, 2.02~beta2-9ubuntu1.11), oxideqt-codecs-extra:amd64 (1.15.7-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1), grub-efi-amd64:amd64 (2.02~beta2-9ubuntu1.8, 2.02~beta2-9ubuntu1.11), dkms:amd64 (2.2.0.3-1.1ubuntu5.14.04.5, 2.2.0.3-1.1ubuntu5.14.04.6), libarchive13:amd64 (3.1.2-7ubuntu2.2, 3.1.2-7ubuntu2.3), thunderbird-locale-en-us:amd64 (38.8.0+build1-0ubuntu0.14.04.1,45.2.0+build1-0ubuntu0.14.04.3), gimp:amd64 (2.8.10-0ubuntu1, 2.8.10-0ubuntu1.1), p7zip-full:amd64 (9.20.1~dfsg.1-4+deb7u1build0.14.04.1,9.20.1~dfsg.1-4+deb7u2build0.14.04.1), thunderbird:amd64 (38.8.0+build1-0ubuntu0.14.04.1,45.2.0+build1-0ubuntu0.14.04.3), linux-image-generic-lts-utopic:amd64 (3.16.0.76.67, 3.16.0.77.68), p7zip:amd64 (9.20.1~dfsg.1-4+deb7u1build0.14.04.1, 9.20.1~dfsg.1-4+deb7u2build0.14.04.1), libgimp2.0:amd64 (2.8.10-0ubuntu1, 2.8.10-0ubuntu1.1), tzdata-java:amd64 (2016d-0ubuntu0.14.04, 2016f-0ubuntu0.14.04), grub-common:amd64 (2.02~beta2-9ubuntu1.8, 2.02~beta2-9ubuntu1.11), chromium-codecs-ffmpeg-extra:amd64 (50.0.2661.102-0ubuntu0.14.04.1.1117, 51.0.2704.79-0ubuntu0.14.04.1.1121), libnspr4:amd64 (4.10.10-0ubuntu0.14.04.1, 4.12-0ubuntu0.14.04.1), flashplugin-installer:amd64 (11.2.202.626ubuntu0.14.04.1, 11.2.202.632ubuntu0.14.04.1), linux-image-generic-lts-vivid:amd64 (3.19.0.64.46, 3.19.0.65.47), libimobiledevice4:amd64 (1.1.5+git20140313.bafe6a9e-0ubuntu1, 1.1.5+git20140313.bafe6a9e-0ubuntu1.1), libgd3:amd64 (2.1.0-3ubuntu0.1, 2.1.0-3ubuntu0.2), libgd3:i386 (2.1.0-3ubuntu0.1, 2.1.0-3ubuntu0.2), grub2-common:amd64 (2.02~beta2-9ubuntu1.8, 2.02~beta2-9ubuntu1.11), libldap-2.4-2:amd64 (2.4.31-1+nmu2ubuntu8.2, 2.4.31-1+nmu2ubuntu8.3), libldap-2.4-2:i386 (2.4.31-1+nmu2ubuntu8.2, 2.4.31-1+nmu2ubuntu8.3), chromium-browser-l10n:amd64 (50.0.2661.102-0ubuntu0.14.04.1.1117, 51.0.2704.79-0ubuntu0.14.04.1.1121), libnss3-nssdb:amd64 (3.21-0ubuntu0.14.04.2, 3.23-0ubuntu0.14.04.1), thunderbird-locale-en:amd64 (38.8.0+build1-0ubuntu0.14.04.1, 45.2.0+build1-0ubuntu0.14.04.3), gimp-data:amd64 (2.8.10-0ubuntu1, 2.8.10-0ubuntu1.1), liboxideqtcore0:amd64 (1.15.7-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1), linux-signed-generic-lts-utopic:amd64 (3.16.0.76.67, 3.16.0.77.68), linux-headers-generic-lts-vivid:amd64 (3.19.0.64.46, 3.19.0.65.47), libpurple0:amd64 (2.10.9-0ubuntu3.2, 2.10.9-0ubuntu3.3), grub-efi-amd64-signed:amd64 (1.34.9+2.02~beta2-9ubuntu1.8, 1.34.13+2.02~beta2-9ubuntu1.11), thunderbird-gnome-support:amd64 (38.8.0+build1-0ubuntu0.14.04.1, 45.2.0+build1-0ubuntu0.14.04.3), libnss3:amd64 (3.21-0ubuntu0.14.04.2, 3.23-0ubuntu0.14.04.1), linux-generic-lts-vivid:amd64 (3.19.0.64.46, 3.19.0.65.47), sbsigntool:amd64 (0.6-0ubuntu7.1, 0.6-0ubuntu7.2), libpurple-bin:amd64 (2.10.9-0ubuntu3.2, 2.10.9-0ubuntu3.3), liboxideqtquick0:amd64 (1.15.7-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1), linux-signed-image-generic-lts-vivid:amd64 (3.19.0.64.46, 3.19.0.65.47), linux-signed-generic-lts-vivid:amd64 (3.19.0.64.46, 3.19.0.65.47), liboxideqt-qmlplugin:amd64 (1.15.7-0ubuntu0.14.04.1, 1.15.8-0ubuntu0.14.04.1), tzdata:amd64 (2016d-0ubuntu0.14.04, 2016f-0ubuntu0.14.04), linux-generic-lts-utopic:amd64 (3.16.0.76.67, 3.16.0.77.68), linux-libc-dev:amd64 (3.13.0-91.138, 3.13.0-92.139), chromium-browser:amd64 (50.0.2661.102-0ubuntu0.14.04.1.1117, 51.0.2704.79-0ubuntu0.14.04.1.1121), linux-headers-generic-lts-utopic:amd64 (3.16.0.76.67, 3.16.0.77.68)

Reports are attached,
Thank you.

[neovin]

Hello,

I found out that it is Ubuntu activation of validation of modules signature linked to secure boot (UEFI) that caused the driver to stop.
I had the same issue with VirtualBox for my virtual machines which was not working anymore but when reinstalling the virtualbox drivers (sudo apt-get install --reinstall virtualbox-dkms), a final step proposed to deactivate the secure boot by inserting a password and then typing it again on restart (UEFI menu appeared on BIOS step and asks some password characters to validate deactivation).

It then solved my display link and virtual box issues !

I don't know how to activate this step independently of the virtual box installation but it should be possible to deactivate the secure boot from the BIOS whereas it seems different on each machine. Here are some tutorials for some machines (sorry only in french): https://doc.ubuntu-fr.org/desactiver_secure_boot

I hope it can help if you don't mind deactivating secure boot.

Regards,

[neovin]

Hello,

It seems that the command line used for disabling the secure boot mode was the following:
sudo mokutil --disable-validation
-asked for a password
- restart and during BIOS step ask to type any key for modification
- choose change secure boot state
- enter some characters of the password

On my machine it was sufficient to deactivate secure boot and nothing was necessary inside the BIOS parameters but it seems to be the case for others machines.

Moreover, if you do not want to deactivate the secure boot it should be possible to manually sign the display link drivers and add the signing key in the secure boot keys. Here are some hints on how it is possible:
http://gorka.eguileor.com/vbox-vmwar...x-2016-update/
http://www.rodsbooks.com/efi-bootloa...olling-sb.html

Regards.