DisplayLink Feature Suggestions
- Vote for an existing idea (60)
- or
-
Linux wayland support
Displaylink does not seem to work with wayland yet, which is starting to be the standard, replacing Xorg, on linux soon:
https://fedoraproject.org/wiki/Changes/WaylandByDefault
https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)Would be great if you could also support wayland!
197 votesTo work with Wayland, EVDI lacks GBM. For anyone that would be willing to have a go and develop a GBM backend, here’s how it was already implemented for Chrome OS in their minigbm: https://chromium.googlesource.com/chromiumos/platform/minigbm/+/master/evdi.c
-
Better linux support
Better linux support, updated drivers, Fedora support (that means distributing an RPM)
Fix the issue where closing X for the first time means that the devices are no longer recognized by xrandr
Fix the slowness disparity between running it in linux and running it in windows
windows = no lag
linux = lagImprove your linux drivers.
96 votesThanks for the feedback. The Ubuntu release is provided to give the tools to be able to port to other Linux flavours.
An RPM has already been created and available here: http://nothen.com.ar/en/support-for-displaylink-adapters-on-linux/
We would be happy for the community to maintain packages for other Linux variants, based off the DisplayLink Ubuntu package.
The issues you are seeing with stability and performance are more due to the X system. DisplayLink do not intend to start changing the Linux OS to address these issues.
The performance is slower than Windows due to the way we get screen update changes. A change on any screen makes all pixels update on all screens, giving us many pixels to encode and send over USB. If the Linux graphics subsystem just notified of the areas of the screen which had changed, this would minimise the changes needed to be encoded by DisplayLink and remove the…
-
Linux Driver Management integration
Integrate Solus' Linux Driver Management (https://solus-project.com/2018/01/26/linux-driver-management-1-0-released/) to better support Linux distros.
1 vote -
Support linux on ALL your devices
I just purchased a displaylink USB 3 based device; reading the forums I didn't pickup the difference between USB 2.0 being supported and USB 3.0 not being supported. This is nonsense. Content protection on the monitor, I don't care about being able to use protected content; I'd like to just be able to use the monitor I paid for. But no.
I think you should support Linux with USB 3.0 devices to use non-DRM content.
576 votesUbuntu is now supported by DisplayLink and can be downloaded from here:
http://www.displaylink.com/downloads/ubuntu
The Ubuntu driver is designed with open source components and packaging which enables it to be ported and distributed for other linux distros. DisplayLink does not intend to officially support more than Ubuntu. For more information, see our article here:
http://support.displaylink.com/knowledgebase/articles/679060
If you have further suggestions about Linux support, please raise separate specific feature requests.
If you have any problems or need support, please use the Linux forum here:
http://www.displaylink.org/forum/forumdisplay.php?f=29Please DO NOT use the comments thread to report problems. We have no way of following up on problem reports here. Use the forum instead.
-
Linux: reach Windows feature parity (mirroring, scaling, and rotating)
Currently unsupported / broken in DisplayLink on Linux:
- Display mirroring
- Display scaling
- Display rotationThis really limits what you can actually do with DisplayLink on Linux - i.e. you can only currently have an extended display activated with no scaling or rotation. You can't even use only the DisplayLink connected display on its own.
188 votes -
ARM linux support
Better Linux support, a direct driver for X11 and support ARM devices and not crypted logs.
120 votesI’ve updated this to be for ARM Linux support. EVDI is designed as an open source component to be adapted for different graphics architectures.
The logs from the DisplayLink binary component are encrypted to protect IP. This is the same on all OSes for DisplayLink binary components.
-
Support linux with nvidia/amd drivers
support displaylink with proprietary drivers from nvidia and amd
196 votesThis is on the backlog of Linux work, but is possible to be addressed by the community.
It is possible the issue could be fixed with changes to the EVDI driver, which is an open source component available on github here:
-
Fix linux driver scaling
Scaling doesn't work with the linux DisplayLink driver. This makes it impossible to use displays of different DPI together. By scaling I mean, for example:
xrandr --output DVI-I-1 --auto --scale 2x2
56 votes -
Linux kernel version 4 unsupported.
Just tried building the displaylink driver using the displaylink-installer.sh on my Fedora Rawhide machine and look at the results!
./displaylink-installer.sh -?
DisplayLink Linux Software 1.0.68 install script called: -?
Distribution discovered: "Fedora release 24 (Rawhide)"
Unsatisfied dependencies. Missing component: Kernel version 4.2.0-0.rc5.git3.1.fc24.x86_64 is too old. At least 3.14 is required.
This is a fatal error, cannot install DisplayLink Linux Software.Hmm, 4 is older than 3!?!? Who Knew?!?! Need to fix the script.
4 votesThis should now be fixed in the latest Ubuntu release
-
Linux driver update to support Kernel 4.9.*
Displaylink stopped working on the new 4.9 kernel because the EVDI kernel module does not compile.
There is a new release that supports kernel 4.9 and 4.10 of the EVDI library https://github.com/DisplayLink/evdi/releases/tag/v1.3.43.
Please also update the install file.9 votes -
16.04 LTS is comming ... And Displaylink, are you ready ?
16.04 LTS release comming next month, The display link drivers for linux is ready for?
The latest drivers support 14.04 LTS24 votesV1.1 of the Ubuntu driver is now available, which supports 16.04.
-
Make the Linux driver open source and get it into the kernel
If the DisplayLink driver existed in the kernel, it would be SO much easier for the users to get it working. In my role as Chief Digital Officer for a large company (of 8000 people), I would probably have bought 500 of these devices IF the driver were just upstream (you know, how Linux devices normally "just work" without the aggro common in the Windows world). However, the annoyance of a manual driver install, especially when it's broken on updates to newer kernels, is just something I wouldn't want to invest in. Please consider that proprietary drivers are serious impediment…
163 votes -
Add upgrade logic to the Linux installation scripts
I had version 1.1.62 of the Ubuntu driver installed. When I tried to install the new driver, I got errors saying the EVDI module was running and I needed to reboot to continue the installation. After reboot, I got the same error again.
After looking into the running DisplayLinkManager process, I ended up dropping into /usr/lib/displaylink and running the install script there with the uninstall option:
me@mine:/usr/lib/displaylink$ sudo ./displaylink-installer.sh uninstall
DisplayLink Linux Software 1.1.62 install script called: uninstall
Distribution discovered: Ubuntu 16.04.2 LTS
Uninstalling
Removing EVDI from kernel tree, DKMS, and removing sources.
Stopping DLM systemd service
Removed symlink /etc/systemd/system/graphical.target.wants/displaylink.service. …10 votes -
Ubuntu drivers eating a lot of CPU. Not always but at least 50% of the times
I have actually a very slow PC because of this:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1541 root 20 0 2343424 51804 2624 S 111.9 1.4 198:49.14 DisplayLinkMana
in other words, DisplayLinkMana(ger) eats a lot of CPU. from 50 to more than 100%sometimes not.
I think this is an issue, that should be fixed.
Thank you.
alfonso
41 votes -
tell me how to send you the Support Files I collected with your Support Tool
tell me how to send you the Support Files I collected with your Support Tool
2 votesThe artciles describing how to collect the log files have now been updated with a contact email address to send the files to.
-
Netflix support on Android device
Netflix support from Android device
12 votes -
Better Mac OS X support
Better Mac OS X support
19 votesThis needs a better description as to specific issues on Mac that need addressing. Some issues are already documented and being worked on by DisplayLink. as documented in knowledgebase articles.
-
3 Monitor Support on Chrome OS
As DisplayLink support is not embedded in the ChromeOS 51 build and later, you should add 3+ monitor support for ChromeOS. At this point someone would only be able to run it off of a Chromebook/Chromebox with higher ram (8-16GB+). But adding this support would mean A LOT more business use cases being satisfied.
1 voteDisplayLink imposes no limit on the number of DisplayLink enabled displays that can be connected on Chrome OS from R51 onwards.
Any limitations found will be OS restrictions rather than something added by DisplayLink.
-
Add support for VMware USB passthrough so guest OS can have dedicated display output
For DL-3xxx and DL-5xxx devices especially.
This is already working for MacOS but not working for Windows (as mentioned in DisplayLink KB 544870) and Linux.
This will allow multiple DisplayLinks to be used on single VM hosts behaving like thin clients, which is an enormous user base and thus market potential.
61 votes -
Sales Support improvements
Get better customer service and sales support at Display Link. Dealing with voice mails and forms is a waste if time. Do any humans work for this company!
4 votesDisplayLink does NOT design, manufacture, distribute or sell any end product. DisplayLink is a semiconductor company. We are delighted to provide email support as debugging graphics issues are impossible by phone as we need data for a diagnosis.
The assistance for installation, and sales support, is coming from the product manufacturer and the seller as they know best the product they decided to build.
- Don't see your idea?
