From: JeremyRand <JeremyRand@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] DisplayLink GPU's (udl driver) broken because udlfb (CONFIG_FB_UDL) driver is enabled
Date: Sat, 03 Sep 2022 01:58:32 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39076@inbox.vuxu.org> (raw)
[-- 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).
reply other threads:[~2022-09-02 23:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39076@inbox.vuxu.org \
--to=jeremyrand@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).