No that's not it.
xrandr --listproviders does actually show me the providers
but xrandr --listproviders --verbose does not show me the dvi ports they should provide
starting/restarting the systemd daemon does not help...
this is what xrandr shows me:
# xrandr --listproviders
Providers: number : 3
Provider 0: id: 0x45 cap: 0x2, Sink Output crtcs: 3 outputs: 3 associated providers: 0 name:modesetting
Provider 1: id: 0x137 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
Provider 2: id: 0x10b cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
# xrandr --setprovideroutputsource 1 0
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 35 (RRSetProviderOutputSource)
Value in failed request: 0x45
Serial number of failed request: 17
Current serial number in output stream: 18
log files for both my monitors are created under /var/log/displaylink/, though the content are not human readable.
I see the udev file makes mention of the plugdev group that does not exist on my machine though...
Search Criteria
Package Details: displaylink 6.0-0
Package Actions
| Git Clone URL: | https://aur.archlinux.org/displaylink.git (read-only, click to copy) |
|---|---|
| Package Base: | displaylink |
| Description: | Linux driver for DisplayLink devices |
| Upstream URL: | https://www.synaptics.com/products/displaylink-graphics |
| Keywords: | dock gpu graphics usb |
| Licenses: | GPL2, custom, LGPL2.1 |
| Submitter: | Hideaki |
| Maintainer: | endorfina |
| Last Packager: | endorfina |
| Votes: | 99 |
| Popularity: | 0.151362 |
| First Submitted: | 2015-08-04 23:24 (UTC) |
| Last Updated: | 2024-05-06 08:33 (UTC) |
Dependencies (5)
- evdiAUR (evdi-amd-vmap-textureAUR, evdi-compat-gitAUR, evdi-gitAUR)
- libusb (libusb-gitAUR)
- gawk (gawk-gitAUR, busybox-coreutilsAUR) (make)
- grep (grep-gitAUR, busybox-coreutilsAUR) (make)
- wget (wget-gitAUR) (make)
Required by (1)
Sources (7)
yah00ka commented on 2015-08-07 06:52 (UTC)
Hideaki commented on 2015-08-07 06:36 (UTC)
Oh yeah, you also have to enable the systemd service.
sudo systemctl start displaylink
I'm updating the DisplayLink wiki page to make mention of how to use the new driver.
yah00ka commented on 2015-08-07 06:19 (UTC)
unfortunately xrandr didn't do anything for me.
xrandr --listproviders does not even list the displaylink device.
Hideaki commented on 2015-08-06 17:06 (UTC)
Ubuntu does some magic to prevent you from needing to manually tell xrandr to link your main gpu to your displaylink device. xrandr --listproviders should show the displaylink device as modesetting, xrandr --setprovideroutputsource 1 0 should get your up and running.
yah00ka commented on 2015-08-06 16:08 (UTC)
Awesome work!
unfortunately, the driver isn't working for me in Arch. I have tested it with Ubuntu, so I know it can work.
journalctl is showing me the info for my external monitors on connection of the docking, but they never show up in gnome's display configuration...
Hideaki commented on 2015-08-06 01:01 (UTC)
This is an initial release of the new driver that DisplayLink has released for their USB 3.0 devices. The PKGBUILD is based on their official installer with a ton of crud removed. I've added an Install section to the systemd service that was missing from their installer, so you can set the service to load on boot. Look at the Upstream URL for all the limitations of the current version.
Pinned Comments