I’m also able to run DisplayLink stack at home with another DisplayLink
supporting device OWC USB-C Dual HDMI Display Adapter. So far the tasks
to be done to enable displaylink:
* Ubuntu side
1. To port 1.14.10 into Ubuntu because latest displaylink-driver
(versioned 6.1.1-17) depends on evdi >= 1.14.9, and we have 1.14.8 for
Questing/Plucky, 1.14.6 for Oracular, and 1.14.2 for Noble. This will be
LP: #2110682.
2. To determine the right version of displaylink-driver to be
installed. Then that means backport of evdi packages from a later series
to Noble.
* Synaptics side
1. Update displaylink-driver debian/control field Depends as Depends:
evdi-modules | evdi-dkms, libc6 ( >= 2.31)`
evdi-modules and evdi-dkms will be provided by linux-modules-evdi,
and the version will be ubuntu kernel version. There is still a package
named evdi-dkms, and its version follows Synaptics' version. However
that means there are two different version schemes, and therefore
version upper/lower bounds for Depends control field become invalid.
There might be a better way to restrict driver version dependencies.
2. /opt/displaylink/DisplayLinkManager should dlopen libevdi.so.1 ,
rather than libevdi.so. The former is provided by Ubuntu package
libevdi1, and the latter is by libevdi-dev. displaylink-driver depends
on neither, but it should really depend on libevdi1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2110634
Title:
Include support of Synaptics display link
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2110634/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
