void-linux / void-linux/void-packages

DisplayLink GPU's (udl driver) broken because udlfb (CONFIG_FB_UDL) driver is enabled

Open
#39,076 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-testing
Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the linux5.18 package configuration and the CONFIG_FB_UDL setting. Compare the package's enabled options with the reported udlfb and udl behavior, then verify that disabling CONFIG_FB_UDL allows a DisplayLink GPU to be detected in a GNOME/Wayland session.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.