I've been using displaylink with an external USB for the last two months.
Downgraded the libmesa packages as suggested in the messages below.
Displaylink service has been broken since last week (~Jan 15). The displaylink.service is active. evdi module is loaded.
plugging in the extra monitor and running
xrandr --setprovideroutputsource 1 0
the monitor becomes activated however it is totally black. I can trace my mouse motion on the extra monitor, nothing else is visible.
EDIT;
It turns out pacman decided to upgrade the lib32-mesa, lib32-mesa-libgl, mesa, mesa-libgl packages to 13.0.1.
When I try to re-install the old ones, I get the following error
error: mesa: missing required signature
error: lib32-mesa: missing required signature
error: lib32-mesa-libgl: missing required signature
error: mesa-libgl: missing required signature
I tried upgrading evdi package from 1.2.64 to 1.3.43, but no luck! same problem persists
Search Criteria
Package Details: displaylink 6.1-1
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: | 105 |
Popularity: | 0.156961 |
First Submitted: | 2015-08-04 23:24 (UTC) |
Last Updated: | 2024-12-14 08:31 (UTC) |
Dependencies (5)
- evdiAUR (evdi-amd-vmap-textureAUR, evdi-gitAUR, evdi-dkms-gitAUR, evdi-dkmsAUR)
- libusb (libusb-gitAUR)
- gawk (gawk-gitAUR) (make)
- grep (grep-gitAUR, grep-compatAUR) (make)
- wget (wget-gitAUR, wurlAUR) (make)
Required by (1)
Sources (7)
Latest Comments
« First ‹ Previous 1 .. 33 34 35 36 37 38 39 40 41 42 43 44 Next › Last »
fethio commented on 2017-01-24 10:55 (UTC) (edited on 2017-01-24 12:00 (UTC) by fethio)
acidicX commented on 2016-11-21 09:05 (UTC)
I've tried to install this right now and it fails with the following output:
==> Starting package()...
./displaylink-driver-1.2.65.run: line 400: exec: -t: invalid option
Prutheus commented on 2016-11-12 23:57 (UTC)
I get a little screen freeze every ~~10 seconds. This needs to be related to displaylink. Coul you please check this?
project0 commented on 2016-11-11 19:31 (UTC)
@SmartSuka There is currently an issue with the new libmesa 13.x package. Downgrade to 12.x should fix this, see https://bbs.archlinux.org/viewtopic.php?pid=1666503#p1666503
SmartSuka commented on 2016-11-08 02:11 (UTC)
I'm also having problems with my displayLink configuration that I was not having previously. I've placed my relevant errors from dmesg into the same gist that project0 posted previously.
https://gist.github.com/Project0/3ff20cd550c4238523f11e7a4ec28d53
If there is another form where I should post instead, please point me in the right direction. I'm still new here.
PlusMinus commented on 2016-10-17 09:03 (UTC)
That is true, I already forgot that I switched back to X.
truongan commented on 2016-10-16 18:59 (UTC)
@project0: It's neither dislaylink or evdi problem for me. Since gnome 3.22 update, gnome default to start in Wayland instead of Xorg. And one can easy suppose that dislaylink have neither the interest nor the resource to make their driver work on wayland. Before type in my password in GDM, click the small gear icon and choose Gnome on Xorg, everything will work fine as before.
PlusMinus commented on 2016-10-14 09:17 (UTC)
But the displaylink driver didn't receive any changes. evdi got the actual update.
project0 commented on 2016-10-14 08:15 (UTC) (edited on 2016-10-19 09:01 (UTC) by project0)
since last system update, the displaylink service doesnt work for me anymore: https://gist.github.com/Project0/3ff20cd550c4238523f11e7a4ec28d53
update 17.10: I have fixed this errors by deleting /var/lib/gdm/.*, but displaylink does not found any provider
update 19.10: I had some custom configs for the intel device in /etc/X11/xorg.conf.d/ which breaks the displaylink devices with xrandr.
aguo commented on 2016-10-02 12:33 (UTC) (edited on 2016-10-02 12:34 (UTC) by aguo)
Can confirm this is working on kernel 4.7 using a D3100 dock. I didn't realise that this doesn't work automatically immediately after download & install. I referred to the steps on the wiki to get xrandr configured before it worked.
Big thanks @PlusMinus for maintaining the package! :)
Pinned Comments