-
-
Notifications
You must be signed in to change notification settings - Fork 227
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
Broken after update to 4.19 kernel #191
Comments
@toddsnider-epc thanks for the heads up. Since this is a problem with source driver, I'm not sure what can be done on Except monitor what changes they make on their side so we can act if any additional changes will need to be done. In meantime, I'm open to any suggestions you may have. |
Same problem here... Thanks for your feedback, let's hope this issue is quickly fixed on their side. |
Problem was also mentioned by @adangel as part of #68 (comment) |
It is apparently fixed with evdi 1.5.1, but upstream displaylink 4.4 still includes only 1.5.0. |
I've just made changes which are ought to fix problems with >= 4.19 linux kernel, I didn't merge the changes with master yet (changes are in So if any of you could run Once in displaylink-debian directory oneliner which will do everything for you:
|
No luck yet ...
|
@toddsnider-epc okay problem is fixed, pull the latest changes and run re-install again. If problem persists please re-open the issue. |
As of 1533409, displaylink-debian now works for me with both 4.18 and 4.19 kernels. Many thanks @AdnanHodzic and @adangel ! |
Hello, I am now on kernel 4.20, and I still see the code 3 error :
I tried both with master and next-gen branch, even though I guess this one was merged. Any idea what's going on here? |
@GingoO I have an idea what the problem is. Can you also include output of:
|
Here is the output of --debug:
|
It seems, that for kernel 4.20, the evdi module needs to be adjusted as well: DisplayLink/evdi#145 |
Thanks to the both of you. Yes, may try downgrading. |
As part of b57cea8 commit udl/udlf will be added to blacklist.conf automatically if >= 4.14.9 is detected. I'm not sure if this will fix your problem, but I'd definitely advise you to pull the latest changes and perform reinstall and report back if there any changes. Of course changes should still only be done on <= 4.20 kernel. |
I'm closing this issue due to inactivity. Feel free re-open the issue If you're still experiencing same problem after pulling latest updates and running reinstall. |
I've just merged Regardless, please pull latest ( If the issue still persists, re-open the issue and include output of |
This isn't an issue with the script but rather the driver source lagging changes to the 4.19 kernel API. I'm hoping that this can be fixed by patching the files in this commit. before building evdi.
The text was updated successfully, but these errors were encountered: