-
Notifications
You must be signed in to change notification settings - Fork 186
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
EVDI kernel 5.11/5.12 support #275
Comments
Thanks for the update! I noticed that the changes have been pushed to the |
does this update bring better support/performance for AMD Ryzen 4650? |
Looking forward to this! I was wondering why my SideTrak stopped working, though I assumed it was a system update. Kernel update makes perfect sense. Hopefully the upcoming update will fix it! |
Can't wait for the update! For now I just set my default kernel in grubby to 5.10.23 |
Sounds great! DisplayLink 5.4 is on the website, but we still need a evdi release, which supports 5.11/5.12. The 1.9.0 and 1.9.1 tagged versions are too old and so is the current commit in the master branch. |
@bnavigator are you using Wayland or X? It's not working for me on Xorg unfortunately, 5.11, testing 5.12 though EDIT: I see the package you're referring to on the site. Let me try it with the DL pkgbuild |
I hope that it solve my problems with evdi :) |
X11 on Archlinux with my displaylink package from AUR and evdi-git from AUR. Kernel 5.11.11-arch1-1 |
It's worth noting that on Archlinux I'm affected by #274 , downgrading |
It's also worth noting that DisplayLink 5.4.0-55.153 comes with a bundled evdi.tar.gz from 0f1ad21 Just found out and I am considering changing the AUR and openSUSE package to not require a separate evdi at all... |
As DLM and evdi are two separate projects, with separate releases and separate versions, I would prefer keeping them as separate AUR packages. In my opinion, that is the least confusing w.r.t. what is actually installed on your system. |
It is totally confusing with all the different old and recent AUR packages for evdi. Some work, some don't and it's always a new situation for every new release (or lack of it). |
That's a very good point. However, all those different AUR packages are necessary because every new kernel update breaks evdi in someway and evdi requires a patch. As DisplayLink does not add these patches into the DLM releases (as far as I am aware), you would need some other way to patch the bundled evdi. How would you deal with such a scenario without a separate evdi package that can be patched and updated regardless of DLM releases? |
Add a patchfile and patch inside the PKGBUILD. This would avoid what happened with DisplayLink 5.3 and evdi >=1.8. People were trying to use this combination very often, which did of course not work. |
After installing current dev (f703808) and DLM 5.4, I can finally detect displays :) But when trying to assign the display, I get the below in my Xorg log. I will wait for new evdi release or devel updates as @bnavigator stated above. Thanks
|
@nckrse did you try to inspect reported modes and assing a valid mode with xrandr? Did 3840x1080 work with DL 5.3 and evdi 1.7? |
That's not a commit in current dev |
Perhaps someone can help me out. Using Pop!_OS 20.10 with GNOME 3.38.3 on Xorg. I installed the new Ubuntu driver version 5.4 from the DisplayLink site and rebooted. The service is running, seemingly without error:
I have evdi 1.9.1 installed from this PPA because the regular repos only have 1.7:
GNOME detects that there is a second monitor plugged in: However, it won't let me switch away from "single display". If I select "mirror" or "join displays" and click apply, it automatically goes back to "single display". |
@bnavigator , sorry, i was trying separate forks a few days ago. I re-installed on dev b0b3d13 and run into the same issue. I have tried different xrandr modes also. My issue is the same exact as @echosa , but I had tailed the logs during doing so. |
You should move your questions to the displaylink support forum. This is out of scope for "EVDI kernel 5.11/5.12 support" |
Same issue for me on my external monitors, detected but no way to display and get it working with DLM 5.4, think it's mainly mesa 21 problems... Downgrading on popos is very dangerous but if it's the only way ... i will try as soon as i'll have time and get back here to give you feedback. |
@Nillu I find myself in the same situation, Pop!_OS 20.04 and kernel 5.11.0-7612-generic. After upgrading kernel, one of my screens became completely useless. I was thinking of downgrading kernel but I don't want to break my install at this point as it is my work PC. If you are able to get it working let me know! :) |
Note that the PPA says "evdi 1.9.1+master". master does not have the fixes for kernel >=5.11. DisplayLink 2.4 comes with evdi bundled. Did you try to uninstall the PPA evdi and reinstall DisplayLink from the official installer? |
I know it was recommended to go to the displaylink support, but when I contacted them, they only support Ubuntu. So, to update here since it was mentioned: I used Timeshift to rollback to before kernel 5.11. Then I used the previous driver installer to completely remove the old version of the driver and its evdi. (I was having issues with not being able to remove evdi completely). Once that was uninstalled and all clean again, I upgraded back to 5.11 again. I then installed the latest displaylink driver that was just released, including its bundled evdi, without having evdi installed via apt (whether PPA or not). Same issue. Everything seems fine. Service is running. Display is detected by GNOME. Still can't get it to actually display. Just wanted to update, since "Did you try to uninstall the PPA evdi and reinstall DisplayLink from the official installer?" didn't work. |
When you say PPA, I suspect Pop!_OS is close enough to Ubuntu. The "official" support might not be willing to help, but the forums are probably a better place to discuss this issue with the DisplayLink Manager than the GitHub issue tracker for evdi: |
Thank you for that link. I've reached back out to the official support, but having access to that forums is nice too. I'll avoid cluttering this GitHub issue anymore. |
Just to reiterate, DLM 5.4 has since been released. 😇 It works with the current devel, at last. No updates for AMD-specific bugs yet. We're aware of the issues on Pop!_OS and we'll be promptly investigating what has happened over there. 😉 |
Thanks, @displaylink-emajewsk! Regarding:
Is there somewhere we can track progress of that other than just watching for messages here? |
@displaylink-emajewsk Thank you for the updates. I can confirm that it is working on Fedora 33. Question: Are there any plans to re-tag 1.9.1 from the current devel branch? This would be helpful for packaging. Otherwise, we need to make changes over on https://github.com/displaylink-rpm/displaylink-rpm Thanks again for keeping us updated. |
I try to get 5.4 in running on devuan chimaera But inserting fails with: dmesg | grep evdi[ 85.702974] evdi: [I] Initialising logging on level 5 Any ideas? |
I found another error myself. This should be the same kernel as in bullseye. |
Hi, it works with Ubuntu Hirsute (5.11.0) and Displaylink 5.4 (displaylink-driver-5.4.0-55.153.run) NAME="Ubuntu"
dmesg
But i don't have evdi package installed on my system:
|
If you use the official standalone installer from DisplayLink, it comes with evdi bundled. It won't install any package into the dpkg database. Once again, please: The title of this page is "EVDI kernel 5.11/5.12 support". For anything else, please either use the displaylink support forum, or if it is specific to the evdi driver, open a new issue. |
I have Arch Linux with Kernel 5.11.12 on a Cinnamon Desktop and latest evdi & Displaylink commit. So every change of resolution or master screen ends up on a freeze also zoom isn‘t possible. |
Just following up on this question. Thanks |
@displaylink-emajewsk @displaylink-dkurek Sorry to ask once more. Can we expect to get a proper EVDI release that works with Kernel 5.11/5.12? The current 1.9.1 tag is not compatible with those kernels. You are bundling with the DisplayLink 5.4 drivers an unreleased version of EVDI. Thank you for your help and support. |
FYI for Pop!_OS users having issues, follow this thread instead: #279 |
How about we create a downstream repo of this EVDI devel branch on https://github.com/displaylink-rpm/ and then tag it ourselves. That way we not dependent on any tags here. |
I'm back from holiday. Thanks for the patience. 😇 @elguero The release has been retagged. Someone must've tagged the version incorrectly before pushing and we did not notice. I'll be more vigilant in the future. 😅 |
@displaylink-emajewsk Thank you! One thing that would be helpful is to have support for newer kernels done at a quicker pace. I know it all comes down to resources. Some in the community are quick to help test the release candidates and they point out when changes are needed for upcoming kernel releases. If those items could be taken care of before the official release or at least before the distros start to use the newer kernel that causes issues, that would be helpful. This is probably a no go as far as being resolved but the DisplayLink manager binary complicates being able to put something up on Fedora copr or even considered for inclusion in Fedora, if we are understanding things correctly (displaylink-rpm/displaylink-rpm#125). There was a request to add it to Fedora copr but we think that the DisplayLink manager binary prevents this from being done according to the current policies. Work is being done by contributors to try and get the displaylink-rpm project included in RPMFusion. One contributor has submitted a PR to help work towards this (displaylink-rpm/displaylink-rpm#97). Thank you for asking and for your responses. |
It might be even more out of scope, but IMHO the best solution would be to commit the opensource kernel module into the official linux kernel tree. It's the recommended way to keep all the drivers in sync with kernel development as it draws on the resources of kernel developers. See amdgpu vs nvidia drivers and how their approaches are received within the Linux community. |
You should probably also update your Releases page to indicate that v1.9.1 is the latest release, it's still showing v1.9.0 as being the latest release. |
@elguero Unfortunately, we only officially support Ubuntu LTS releases. Other Linux releases are being put in the "nice to have if there's time" category as of now. 😢 @bnavigator This is out of my hands, sorry. @ztoufie Ah, thanks! 😇 |
@displaylink-emajewsk 5.11 will the default kernel of ubuntu 20.04 within the next 3 months (about 3 months after 21.04 release). |
Dumb (noob) question: Does EVDI module come packaged within the DisplayLink Driver? I'm assuming so, because when I list the DKMS modules, EVDI shows up, but it's not listed in SYNAPTIC. On Ubuntu 20.04, running on a System76 Galago Pro (galp3-c) laptop, DL is broken for me.
Does that mean (a) that the patched EVDI 1.9.1 module hasn't been updated, or (b) that the System76 specific kernel(s) have issues? TIA |
If you installed from the official installer, yes.
What do you mean by that?
No.
Probably not to do with the kernel itself. Check lsmod if the evdi module is actually loaded. Check your Xserver logs if you got errors. Any more questions about usage: --> Displaylink support forum. |
EVDI module is loaded; No errors in XOrg.log.0 I guess if EVDI is included in DLM, it doesn't get listed as a separate package in SYNAPTIC. Okay - then it's something else. |
Fix in Xserver is done! Needs to built for Ubuntu from master: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1931547 |
Discussion on this issue deviated from 5.12 kernel to that Pop!_OS issue: If there is any 5.11/5.12 kernel issue please raise new issue. |
Hello, everyone. Again, sorry for the wait.
Current evdi has been pushed to Github. It is however, NOT a complete driver and will require new DLM in order to work correctly. It should be up on our website in a couple of days (it may vary because of the holidays).
I will update this thread when it goes up.
I'll also be closely monitoring our Github, so if you'll be having any issues with the new kernels, I hope we'll be able to resolve them in a more timely manner. 😇
Thank you for your patience.
The text was updated successfully, but these errors were encountered: