* [ISSUE] DisplayLink GPU's (udl driver) broken because udlfb (CONFIG_FB_UDL) driver is enabled
@ 2022-09-02 23:58 JeremyRand
0 siblings, 0 replies; only message in thread
From: JeremyRand @ 2022-09-02 23:58 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
New issue by JeremyRand on void-packages repository
https://github.com/void-linux/void-packages/issues/39076
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.19_1 ppc64 pSeries uptodate FF
### Package(s) Affected
linux5.18-5.18.19_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://bugs.archlinux.org/task/56817
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011986
### Expected behaviour
The DisplayLink GPU should be automatically detected by GNOME/Wayland; my desktop should be displayed on it.
### Actual behaviour
The DisplayLink GPU is not detected by GNOME/Wayland; my desktop is not displayed on it. It can be fixed manually by blacklisting the `udlfb` Linux driver and rebooting. This happens because the `udlfb` driver is deprecated and interferes with the correct driver, `udl`. I believe Void should disable the `CONFIG_FB_UDL` option in Linux to fix this properly.
### Steps to reproduce
1. Install GNOME with Wayland.
2. Launch a GNOME/Wayland session.
3. Plug in a DisplayLink USB 2.0 GPU, such as a [StarTech USB2DVIPRO2](https://www.startech.com/en-us/audio-video-products/usb2dvipro2).
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-09-02 23:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-02 23:58 [ISSUE] DisplayLink GPU's (udl driver) broken because udlfb (CONFIG_FB_UDL) driver is enabled JeremyRand
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).