@steadfasterX I'm also sometimes experiencing high CPU usage on the DisplayLink process. I don't know either if that's normal or not.
Search Criteria
Package Details: displaylink 5.8-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: | 99 |
| Popularity: | 0.189301 |
| First Submitted: | 2015-08-04 23:24 (UTC) |
| Last Updated: | 2023-11-12 15:52 (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)
julian.poidevin commented on 2023-06-15 07:45 (UTC)
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.
bnavigator commented on 2023-03-23 10:11 (UTC) (edited on 2023-04-07 19:01 (UTC) by bnavigator)
Note: You need the kernel module evdi in a version which is both compatbile with displaylink as well as with the current kernel.
Displaylink is not ready for evdi-1.13.0 yet because of a changed API.
Use evdi-compat-git or a similar patched evdi to make it work with the current kernel. The displaylink package itself does not need to be changed.
Do NOT flag displaylink out of date unless a new Displaylink version is released.
mrTsjolder commented on 2023-03-23 10:03 (UTC)
@Mithras The workaround is to build evdi 1.13 as 1.12.1 (see https://github.com/DisplayLink/evdi/issues/406#issuecomment-1471872488)
Mithras commented on 2023-03-10 20:06 (UTC)
Is there a workaround to make it work with evdi-git 1.13? I can install it by removing version constraint but it doesn't work.
MaKaNu commented on 2023-03-06 13:43 (UTC) (edited on 2023-03-06 13:43 (UTC) by MaKaNu)
I stumbled about this also today. At the end the fix @apoc139 together with freshest kernel worked for my setup. I still wondering where the pkgver() was used in the PACKAGEBUILD.
Pinned Comments