============================================================================= ============================================================================= DisplayLink Ubuntu Software Release Note Build: 4.4.24 (99511) Date: 10 Oct 2018 Extensible Virtual Display Interface version included: 1.5.1 (0e4b7f3) ============================================================================= ============================================================================= A. Introduction =============== This is DisplayLink Driver Software v4.4.0 for Ubuntu. It provides production quality support for DisplayLink USB 3.0 devices on specific variants of desktop Ubuntu Linux. This release adds support for Ubuntu 18.04. The driver enables video support for products using DisplayLink USB 3.0 technology. Standard native Ubuntu drivers provide support for DisplayLink audio and Ethernet interfaces. This driver delivers ARM binaries (32 bit) that enable DisplayLink devices on Raspberry Pi. They are delivered for evaluation purposes and are not officially supported at this time. B. Contents =========== A. Introduction B. Contents C. Issues fixed D. Supported O/S variants E. Release components F. How to install G. Supported features & hardware H. Limitations & known issues I. Future development C. Issues fixed =============== Issues fixed since DisplayLink Driver Software v4.2.0 for Ubuntu (4.2.29) ------------------------------------------------------------------------- DisplayLink screen can sometimes remain blank after resume from sleep if monitor connected over DisplayPort (28120) Cannot login with DisplayLink display plugged in on Ubuntu 18.04 with NVIDIA GPUs (27905) D. Supported O/S variants ========================= This release has been prepared to be compatible with Ubuntu 18.04 and Ubuntu 16.04. Other variants and editions may be compatible if they meet minimum O/S requirements, but are not supported by DisplayLink. The Software contains binaries which work on Intel x86 platform (32 bit and 64 bit). Supported Linux Kernel version between 3.16 and 4.15. Supported Xorg version between 1.16 and 1.19. E. Release components ===================== The Software consists of an open-source kernel mode driver (EVDI) with an accompanying library (libevdi), and a supporting binary application compatible with Intel x86 platform. Source code for the open-source components can be found at DisplayLink's GitHub, https://github.com/DisplayLink F. How to install ================= To install the release, from a terminal window, with root permissions use the command: sudo ./displaylink-driver-XXXX.run Where displaylink-driver-XXXX.run is the name of the extracted DisplayLink driver. The dkms framework is required for installation of DisplayLink. This can be installed with the command: sudo apt-get install dkms More detailed information on installation can be found at http://support.displaylink.com/knowledgebase/articles/615714#ubuntu G. Supported features & hardware ================================ This driver will support up to 2 displays connected to DisplayLink devices. More than 2 DisplayLink displays may work, but not supported or tested by DisplayLink. Resolutions up to 4K are supported on the appropriate DisplayLink hardware. Device families supported: - DL-6xxx - DL-5xxx - DL-41xx - DL-3xxx DL-1x5 and DL-1x0 devices use the open source udl driver, which is not developed or maintained by DisplayLink. H. Limitations & known issues ============================= A list of limitations and known issues can be found here: http://support.displaylink.com/knowledgebase/articles/641668 I. Future development ===================== DisplayLink are open to suggestions and feedback on improving the proposed architecture and will gladly review patches or proposals from the developer community. Please find a current list of areas we identify as requiring attention below. - In this release, the user mode driver service is running with root permissions. In future versions, we would like to reduce the privilege level required for this process – e.g. by using a separate low-privileged user and a separate group, to ensure the permissions needed for driving DisplayLink screens are as low as possible. - The communication between the EVDI kernel module and the wrapper libevdi library is not access-controlled or authenticated. This could be improved in future releases, making it harder to compromise the data EVDI is sending and receiving. - EVDI kernel module driver is currently a platform_driver, for multiple reasons; most importantly because virtual displays are not discoverable, i.e. cannot be enumerated at the hardware level. EVDI is also a generic device, not tied to any particular kind of device, transport layer or a bus.