mlukaszek
10-11-2016, 12:11 PM
Hi All,
We have just released a new version of the Ubuntu driver, v1.2.65.
You can download it from our download page (http://www.displaylink.com/downloads/ubuntu), as usual.
It delivers the following improvements:
Installer will now install correct binaries on Ubuntu 16.10
EVDI is compatible with kernel 4.8 again
As always, looking forward to feedback - please use separate threads if you encounter issues!
Please do attach logs for any reports - use our Linux support tool (http://support.displaylink.com/knowledgebase/articles/757047-how-can-i-report-ubuntu-issues-to-displaylink) to collect necessary diagnostic files.
IMPORTANT NOTE: The evdi kernel module has no signature, which means systems with Secure Boot enabled won't load it. In order for the driver to work, you need to either sign the kernel module (https://github.com/Canonical-kernel/Ubuntu-kernel/blob/master/Documentation/module-signing.txt) yourself, or disable Secure Boot. More help on AskUbuntu thread (https://askubuntu.com/questions/760671/could-not-load-vboxdrv-after-upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur) explaining similar solution for VirtualBox modules.
Thanks,
Michal
We have just released a new version of the Ubuntu driver, v1.2.65.
You can download it from our download page (http://www.displaylink.com/downloads/ubuntu), as usual.
It delivers the following improvements:
Installer will now install correct binaries on Ubuntu 16.10
EVDI is compatible with kernel 4.8 again
As always, looking forward to feedback - please use separate threads if you encounter issues!
Please do attach logs for any reports - use our Linux support tool (http://support.displaylink.com/knowledgebase/articles/757047-how-can-i-report-ubuntu-issues-to-displaylink) to collect necessary diagnostic files.
IMPORTANT NOTE: The evdi kernel module has no signature, which means systems with Secure Boot enabled won't load it. In order for the driver to work, you need to either sign the kernel module (https://github.com/Canonical-kernel/Ubuntu-kernel/blob/master/Documentation/module-signing.txt) yourself, or disable Secure Boot. More help on AskUbuntu thread (https://askubuntu.com/questions/760671/could-not-load-vboxdrv-after-upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur) explaining similar solution for VirtualBox modules.
Thanks,
Michal