Talk:DisplayLink

TODO

• Single X server layouts with a normal monitor and a DL monitor are notably quite difficult to get working. Elaborate on this, provide external links to the related broken packages and what people are doing to fix this.
• Write a section for multi-X server layouts and include ways to combine them. Even if we can't move windows between monitors, this is better than nothing.

DisplayLink driver does not work with Intel GPUs after recent X upgrades

This seems to work again with the DisplayLink driver version 5. After more people have it working again, we might want to add this to the wiki.

Hanckmann (talk) 09:05, 6 March 2019 (UTC)

fb_defio=1

fb_defio=1 module option was removed from this page, since commit 9f811b72c669e29f8c01e258d912254065e58f11 to linux-stable has added it by default.

If this breaks anything, please go ahead and re-add it, but let me know because I'm pretty convinced it's not required.

Ndt (talk) 06:38, 2 June 2013 (UTC)

DELL displayLink model DA100 now working...

With kernel 4.1 or higher , and after installing the USB drivers of the wiki. Start the service ( sytemctl start displaylink.service ) that with the DA100 adapter ( 4 in 1 - VGA ,HDMI,Ethernet and USB 2.0 ) works.

DisplayLink USB 3.0 w/DL-3x00 Suspend/Resume Issues

Just to note there are some resume issues when a system goes into suspend (in my case, Lenovo Thinkpad USB 3.0 Dock w/2 DVI monitors). On resume, xrandr --listproviders shows the providers, and enabling them doesn't seem to do anything: Gnome doesn't see the monitors. Also, the NIC and Audio devices are not found. Unplugging/replugging the USB doesn't change either. I have to Power Off the USB 3.0 Dock and power it back on. Haven't had that issue under Windows across multiple notebooks before.

Eduncan911 (talk) 15:25, 21 January 2016 (UTC)

Not showing in --listproviders until a screen is plugged in

Maybe there should be a note about this? I thought it would show up as a provider even if nothing was plugged in.

xrandr --listproviders isn't showing all my displays

Install evdi from AUR repositories. If that gives error like "logpipe: unbound variable", then install linux-headers with pacman. Restart. Ref: this discussion here https://aur.archlinux.org/packages/evdi-git/

Random Disconnects and Reconnects

Installing and using the DisplayLink software worked without problems following the instructions in this post. However, when using it, I kept getting the problem that the connection to the screens was interrupted and then restored after a few seconds, resulting in a momentary black screen.

After some research I think I found a possible problem. I think the problem is with the USB autosuspend. After the installation the file /etc/udev/rules.d/99-displaylink.rules is created. Here I disabled the USB autosuspend by adding "ATTR{power/autosuspend}="-1"".

Example:

ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb", ATTRS{idVendor}=="17e9", ATTR{power/autosuspend}="-1", ATTR{bInterfaceClass}=="ff", ATTR{bInterfaceProtocol}=="03", ENV{ID_DISPLAYLINK_DEVICE}="1", RUN+="/opt/displaylink/udev.sh START"

After a reboot, the problem has resolved.

Maybe someone can confirm me this solution? Brend (talk) 13:27, 9 October 2023 (UTC)

Wayland ("no configuration is needed" is BS)

Under 1.2 it says "For Wayland, no configuration is needed".

Given that, and that there is a "setting up X displays" section but no section about setting up anything on Wayland, the only possible conclusion is that after following 1.1 and 1.2, I should be able to just plug in the monitors and it should just work, but that is not the case.

EDIT: turns out the device I was trying was not DL. Tried with an actual DL one and it does work out of the box, although with glitches.

Php4fan (talk) 14:40, 24 May 2025 (UTC)

Agreed, there are multiple reported issues and discussions with some Wayland environments such as Sway (Gnome and KDE seem to do better), and patches have been made with varying degrees of success to get DL to work on Wayland. This page should be considered a stub when it comes to DL support on Wayland.

EDIT: Fair enough that Wayland seems to support DL in a broad range of environments. The page could still use improvements covering more edge cases and older hardware on Wayland, though the demand and resources for such edits will likely decrease as Wayland and associated environments mature and modern hardware is phased in.

LJwrites (talk) 21:14, 5 June 2025 (UTC)

troubleshooting: udl loading first may cause issues

I found that udl loading ahead of evdi/displaylink could cause issues on some screens, such as a monitor in vertical orientation cutting off at the bottom in a black band. Blacklisting udl and getting the setting to stick by rebuilding initramfs can get the monitor working correctly again by letting evdi and displaylink handle the connection. I think this relationship is worth clarifying in Installation and the issue would be useful to add to Troubleshooting, as there is essentially no clear information online. LJwrites (talk) 21:25, 5 June 2025 (UTC)