-
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
Feature Request: Kernel 5.18 Support #361
Comments
I am running it on Arch Linux, which uses the Kernel 5.18 as of now. These are my build logs. It may help to track down the issue:
|
Smells like torvalds/linux@7938f42 which says "dma-buf-map: Rename to iosys-map" |
The build log from above suggests that the source code of version evdi 1.10.1 was used. https://github.com/DisplayLink/evdi/commits/v1.11.0 is the latest tag (which is not flagged as a release on github); that tag includes 7d7bad9 which most likely fixes the problem reported here. The real challenge here seems to be that an attempt is made to use evdi 1.10.1 on a newer kernel. I am aware of https://github.com/displaylink-rpm/displaylink-rpm and I am aware of that not making use of the latest DisplayLink components (yet - there is a PR). Disclaimer: the above is all based on reading source code and project metadata. So far I have only (successfully) installed the official DisplayLink 5.6 release onto the (supported) Ubuntu 22.04 LTS; my real target is Fedora 36, though, hence my digging. |
@shoffmeister v1.11.0 fixes the problem for me on Arch Linux with |
I can confirm, the new version works. Sorry for the inconvenience. |
Works, thanks |
How did you actually install 1.11? Did you just download the source and configure it yourself? https://github.com/DisplayLink/evdi/releases EDIT I followed this and my usb ports work and dock is seen, but my display port for my monitor doesn't seem to work. Working through that now. #367 |
Even when fedora is not a supported distribution it would be nice to get kernel 5.18 support which will be added soon.
The text was updated successfully, but these errors were encountered: