We all have felt the frustration of evdi being out of tree for years now, with constant breakage between the DRM subsystem and the evdi.ko kernel module.
The best outcome would be to mainline the driver. There's a lot of history behind it here: https://github.com/DisplayLink/evdi/issues/25 The short answer is no one wants to do the refactoring work to make it palatable to upstream. You can still install evdi-dkms to get secureboot support, as long as you generate your own MOK key and enroll it. The real issue is that there is no open source userspace implementation, which makes it hard to justify inclusion of the open source kernel driver to mainline. I don't really think this will ever be addressed. I recently stopped using DisplayLink, as I finally gave up on it, after using it for years. I was over using 100% CPU on the manager to push packets over USB to make screens work. Honestly, I now recommend people move away from it, and use DP-alt mode instead. ** Bug watch added: github.com/DisplayLink/evdi/issues #25 https://github.com/DisplayLink/evdi/issues/25 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2110634 Title: Include support of Synaptics display link Status in linux package in Ubuntu: Incomplete Bug description: Synaptics display link (https://www.synaptics.com/products/displaylink-graphics) kernel drivers has been packaged into Ubuntu archive as https://launchpad.net/ubuntu/+source/evdi since Focal, and we may need to package it as linux-modules-evdi for installation on secureboot enabled platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2110634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
