The evdi package (evdi 1.12.0-1) failed to load by dkms on my system: what instantaneously addressed the problem for me was to install evdi-git.
displaylink 5.6.1-3, evdi-git 1.12.0.r6.gbdc258b-1, Linux 6.0.5-arch1-1.
Search Criteria
Package Details: evdi 1.12.0-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/evdi.git (read-only, click to copy) |
|---|---|
| Package Base: | evdi |
| Description: | A Linux® kernel module that enables management of multiple screens. |
| Upstream URL: | https://github.com/DisplayLink/evdi |
| Keywords: | display displaylink dp evdi screens |
| Licenses: | GPL |
| Submitter: | PlusMinus |
| Maintainer: | francoism90 |
| Last Packager: | francoism90 |
| Votes: | 51 |
| Popularity: | 0.24 |
| First Submitted: | 2016-09-16 07:44 (UTC) |
| Last Updated: | 2022-07-24 19:46 (UTC) |
Dependencies (3)
Required by (3)
Sources (1)
olof commented on 2022-10-30 10:06 (UTC)
mcardillo55 commented on 2022-10-13 19:24 (UTC)
@direc85's workaround works for me. Thank you!
direc85 commented on 2022-10-11 08:06 (UTC) (edited on 2022-10-14 07:17 (UTC) by direc85)
Edit: The fix was mainlained, so evdi-git works now as-is.
As kernel 6.0 compatibility isn't yet released, the simplest way is adding this to /usr/src/evdi-1.12.0/evdi_drm_drv.h and running dkms autoinstall:
#if KERNEL_VERSION(6, 0, 0) <= LINUX_VERSION_CODE
#include <drm/drm_framebuffer.h>
#endif
rbeucher commented on 2022-08-25 02:14 (UTC)
Same issue as @stefanbankow. I can't add evdi to 5.19.3-arch1-1. Same error messages...
stefanbankow commented on 2022-08-24 15:18 (UTC)
Trying to load evdi/1.12.0 on 5.19.3-arch1-1 returns "modprobe: could not insert 'evdi': Invalid argument". Journalctl cotains the error "Invalid btf_info kind_flag, failed to validate module [evdi] BTF: -22". The same happens when trying to load v1.11.0. I tried to install v1.10.1 as well, but dkms failed to build the module.
direc85 commented on 2022-08-24 08:01 (UTC) (edited on 2022-08-24 08:01 (UTC) by direc85)
Note that at the time of writing, AUR displaylink package is still at 5.6.
If you actually have displaylink 5.6.1 and evdi 1.12, try running sudo mkinitcpio -P and rebooting. I've had to do it a few times after upgrade, I don't know what really causes it.
rbeucher commented on 2022-08-24 06:08 (UTC)
Does not work anymore for me... I tried all configurations I think. 1.12 and 5.6.1 1.11 and 5.6.0-1
The_Loko commented on 2022-08-24 05:48 (UTC)
5.19-3-arch1-1 only works with evdi 1.10 or 1.11, 1.12 doesn't seem to work. I'm using it with displaylink 5.6
rbeucher commented on 2022-08-24 04:26 (UTC)
I am having issues with Kernel v5.19-3-arch1-1. I can't start the displaylink service. I was running evdi 1.10.0, I upgraded to 1.12 and also tried evdi-git but no luck... Anyone else?
wero14 commented on 2022-07-29 15:28 (UTC)
version 1.12.0 is not working with 5.15 as well. had to roll back to 1.11.0-2
Pinned Comments
HavasiK commented on 2022-07-28 12:47 (UTC)
I had the issue also with Kernel v5.10.131. A manual downgrade to evdi v1.11.0 was needed to get my displays back.
julian.poidevin commented on 2022-07-25 07:52 (UTC)
For those having the issue with evdi v1.12 and kernel 5.18.14. This is a known issue, please checkout https://github.com/DisplayLink/evdi/issues/373