displaylink-rpm VS evdi

For the driver, I download this rpm and installed it. While it froze at the end, after a reboot, it worked.

Now, it's much easier to enable the Fusion repository and Envycontrol makes it as easy as Ubuntu to switch GPUs! I also use DisplayLink for additional monitors and there is now a 3rd party rpm for that.

Doing a quick search for "displaylink Fedora" on brave. These are the first 2 results and look pretty simple:

https://github.com/displaylink-rpm/displaylink-rpm

https://kcore.org/2023/01/01/installing-evdi-fedora37/ (should work on the latest Fedora 38)

Hope you next time do some research before making any statement. https://github.com/displaylink-rpm/displaylink-rpm

Appears to be broken on 6.2.x kernels (github issue).

AFAIK this driver is not completely open source. But I assume this issue was created by you? Then I'm afraid you can't do any more besides going back to a 6.1.x kernel.

I'm losing wifi and all animations after installing the evdi display link drivers from the following link: https://github.com/displaylink-rpm/displaylink-rpm/releases

DisplayLink - you will need to get the DisplayLink RPM out-of-kernel driver; if you want to continue using SecureBoot then you'll need to enroll a MOK and get that all set up as part of the build. More details over there.

If you used another method, especially if you did this setup manually, consider building and installing the source rpm here instead: https://github.com/displaylink-rpm/displaylink-rpm

git clone https://github.com/DisplayLink/evdi.git

So I'm currently on Ubuntu 22.10 with Mesa and asahi-edge kernel. You need both to allow using primary GPU as source output. I'm using evdi 1.13.1 with the correction to set the module to the 1.12.0 to run the script displaylink from Synaptics for Ubuntu.

The RPM version never worked for me. It's only useful for getting the services installed. After that clone the repo from https://github.com/DisplayLink/evdi and change to the devel branch. Run make and sudo make install. If you use SecureBoot you also need to sign the resulting evdi.ko with your key. After that restart displaylink.service or reboot and it should work. At least it did for me. I's been a while since I had to use it.

Uninstallation steps complete. darren@pop-os:~/displaylinkfix$ ./displaylink-driver-5.6.1-59.184.run --noexec --keep Creating directory displaylink-driver-5.6.1-59.184 Verifying archive integrity... 100% MD5 checksums are OK. All good. Uncompressing DisplayLink Linux Driver 5.6.1-59.184 100% darren@pop-os:~/displaylinkfix$ cd ./displaylink-driver-5.6.1-59.184 darren@pop-os:~/displaylinkfix/displaylink-driver-5.6.1-59.184$ curl -L https://github.com/DisplayLink/evdi/archive/refs/heads/devel.tar.gz -o evdi.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 80603 0 80603 0 0 179k 0 --:--:-- --:--:-- --:--:-- 179k darren@pop-os:~/displaylinkfix/displaylink-driver-5.6.1-59.184$ nano darren@pop-os:~/displaylinkfix/displaylink-driver-5.6.1-59.184$ nano evdi.tar.gz darren@pop-os:~/displaylinkfix/displaylink-driver-5.6.1-59.184$

I'm afraid this might be a hardware issue, maybe with the cable. I don't have a second cable to swap out unfortunately. A new one won't be here until Saturday. And it seems like a hell of a coincidence for the cable to fail when there's other issues reported within the last few days that seem very similar.

https://github.com/DisplayLink/evdi states

Theres a bug in the 6.2 kernel right now with at least the evdi package (dont know about evdi-git) but can be fixed with a patch. Pr for it is already open but yet to be merged https://github.com/DisplayLink/evdi/pull/401