-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module evdi not found in directory. #492
Comments
Can confirm. Happens to me too. |
Same here.
The mentioned file contains a lot of errors like this, referring to a missing
|
Same thing happens to me 👍 |
I've taken more of a look into the issue. Due to the added tests, the However that only shifts the problem it seems. DKMS can then build the module, however it cannot be loaded:
However Same behavior if we build from source tarball in package |
Another one around here who has had the same problem in archlinux. So far I have solved it by changing the The current |
Confirmed, reverting to the 1.14.6-0 version has restored functionality, this issue seems to be limited to the 1.14.7 version. I'm not sure which version I chose to downgrade initially where this did not work. |
Also confirming that reverting to |
The I also first had issues when downgrading, but that might have been because I tried the For now I'm not updating to 6.11 then until |
I'm not sure if this is just a matter of it not being compatible, but after updating my system, the displaylink service no longer starts. After digging through logs, we eventually get:
modprobe[105853]: modprobe: FATAL: Module evdi not found in directory /lib/modules/6.10.10-zen1-1-zen
This looks like it may have started after updating to 1.14.7.r3.g59a3a86-1, but I have not been able to get this working again using an older version. This looks like it may be linked to #481 but it looks like that should have been fixed in the version I am currently on.
The text was updated successfully, but these errors were encountered: