Displaylink Others Driver

23-04-2021
 |  [RAND-100] - Comments



The Wiki has moved to new hardware, and the old server died.
Book Creator
Remove this page from your book

DisplayLink is a driver that is installed on your Mac that allows you to display over USB 3.0 when you install DisplayLink manager. DisplayLink’s technology uses CPU and GPU in your computer to. Download DHs / Sabrent DisplayLink Display Adapter (0352) other device drivers or install DriverPack Solution software for driver update.

Table of Contents

Displaylink others driver support

DisplayLink 3.0 Devices

This HOWTO covers how to configure and install the DisplayLink driver (evdi) for USB 3.0 devices, and has been tested under Slackware 14.1 and newer. For older devices (e.g. USB 2.0), the udl driver should work with minimal configuration needed.

Older versions of the DisplayLink driver installed themselves in /usr/lib/displaylink instead of the path /opt/displaylink which is used in the instructions below

Preparation

In order to install the evdi driver, you will need to install dkms, which can be grabbed from SlackBuilds.org using your favorite method. To install it manually:

After installing dkms, reboot your system.

Installing evdi

Grab the current DisplayLink USB Graphics Driver for Ubuntu here: http://www.displaylink.com/downloads/ubuntu.

After downloading, you'll need to extract the driver and run the installer script (adjust for the current version number and make sure to run the script as root):

The WARNING messages are simply due to Slackware not being a “supported” distribution, and should not cause issue. Likewise, you might see a warning about the lsb-release command, which can also safely be ignoring. Once complete, the evdi module should be available. Restarting once more is recommended.

Starting DisplayLinkManager

In order to manually start the evdi module and DisplayLinkManager, run the following:

In testing, DisplayLinkManager did not seem to run properly unless executed by root and from the /opt/displaylink directory. Keep that in mind when manually, or automatically, calling the program.

Once running, you should be able to identify your new display(s) in xrandr:

Your native display (if on a laptop), will be Provider 0, with any connected monitors showing as 1, 2, etc. Assuming they are shown properly, enable them:

Replace 1 with the number of your external display(s). Once active, they should show in xrandr or your chosen display settings, and can be configured properly.

Automatically Loading on Boot

Since DisplayLink support is still pretty finicky, you might have to get creative with loading the module and starting DisplayLinkManager on boot. You should be able to add the following to /etc/rc.d/rc.modules.local to load evdi:

In order to start DisplayLinkManager, you can add the following to /etc/rc.d/rc.local:

From there, you'll only need to run (or script) the xrandr command to activate monitors on boot. One example is to add them to a script, like this:

DisplayLink 2.0 Devices

For devices and docks using USB 2.0, the built-in udl module should be sufficient to enable external monitors.

See Also