For convenience I've pushed a patch with the changes suggested by julian.poidevin to https://github.com/seb-sky/aur-displaylink
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.21 |
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 2 3 4 5 6 7 8 9 10 11 12 .. 44 Next › Last »
sebdotv commented on 2023-08-15 07:29 (UTC)
julian.poidevin commented on 2023-08-10 13:18 (UTC) (edited on 2023-08-10 13:23 (UTC) by julian.poidevin)
This is broken for me when using the latest evdi release 1.14.1-0
version. Needs to be updated to displaylink v5.8.
I did that manually using :
pkgver=5.8
_releasedate=2023-08
_pkgfullver=5.8.0-63.33
And it works as intended.
steadfasterX commented on 2023-06-15 08:13 (UTC)
ok, thx for clarifying ! :)
bnavigator commented on 2023-06-15 08:06 (UTC)
Yes it is normal. It is due to the way displaylink works and a reason why there is never a long-term maintainer. We move away from using the hardware quickly.
julian.poidevin commented on 2023-06-15 07:45 (UTC)
@steadfasterX I'm also sometimes experiencing high CPU usage on the DisplayLink process. I don't know either if that's normal or not.
steadfasterX commented on 2023-06-15 07:13 (UTC)
anyone else experiencing high CPU usage for /usr/lib/displaylink/DisplayLinkManager or is just me / my setup? Just bought a displaylink device and don't know if I miss anything here..
running on Kernel 6.1 and all is working fine just that the CPU usage is jumping between 20-100% all the time.. nothing wild connected but I have no idea how to debug (or if its normal or not)
LinaM commented on 2023-06-02 21:02 (UTC)
5.7.1-version works fine with evdi-compat-git (Manjaro kernel 6.3.5) Thx.
PaddiM8 commented on 2023-04-20 22:16 (UTC)
It seems like there's a new version of DisplayLink with "preliminary support" for kernel 6.2.
Release: 5.7 | Apr 20, 2023
bnavigator commented on 2023-04-07 19:03 (UTC)
@zertyz: The current PKGBUILD of displaylink is compatible with evdi-compat-git. There is nothing to be changed. This package is not out of date.
zertyz commented on 2023-04-07 00:17 (UTC) (edited on 2023-04-07 15:31 (UTC) by zertyz)
A better workaround than recompiling evdi 1.13 as 1.12.1 is to install the package evdi-compat-git instead. I just did that and I was able to fully update my system. Displaylink is working as it should.
IMHO, the mainteiner of this package should make it, temporarily, depend on that one and save all his users all this unnecessary trouble.
This, alone, would suffice (again, IMHO), for users to legitmately flag this package as outdated -- since the environment changed, breaking the building of this package, which could be fixed by a PKGFILE edit (even if no upstream code had changed).
So, even if a new Displaylink version isn't released, the update would bring version 5.6.1-3 to 5.6.1-4 and solve all issues.
Pinned Comments