External Display connection through HP USB-C universal dock G2

Hello!

I have recently migrated to Fedora Linux 41 (Workstation Edition) from Windows 11. I am using an HP laptop - HP Laptop 14s-fq1xxx - with AMD Ryzen™ 5 5500U processor with Radeon™ Graphics × 12 integrated graphics. I am using a HP USB-C/A Universal Dock G2 to connect the laptop to my peripherals including a Lenovo monitor. The mouse and keyboard works fine via the dock but the system does not seem to detect the connected external monitor. This setup used to work okay on windows.

I tried downloading and installing Displaylink but with no luck. The monitor works fine when directly connected from the laptop via hdmi.

I could not find any threads on external display issues on Fedora 41 in the forum. I would really appreciate any inputs on the matter and let me know if any additional info is required.

Thanks in advance!

Where did you download the DisplayLink drivers from?

You need to check whether the kernel modules have been built successfully.
You can check with either sudo akmods or sudo dkms status.

If your system has Secure Boot enabled, then you also need to enroll the MOK key first, otherwise the kernel will refuse to load the kernel module.

A quick test would be to disable secure boot in UEFI/BIOS and boot Fedora and see if the drivers are loaded and work.

mokutil --sb-state will tell you if secure boot is enabled.

1 Like

Hello!

Thank you for taking the time to reply.

As you suggested, disabling SecureBoot fixed the issue. Now the external display works!
I am wondering if its okay to keep SecureBoot disabled.

Just posting the following info if it helps anyone else:

I downloaded display link from: Releases · displaylink-rpm/displaylink-rpm · GitHub

sudo dkms status returned:
evdi/1.14.7, 6.12.11-200.fc41.x86_64, x86_64: installed

As far as I understand MOK enrollment is required after installing Nvidia drivers and I am assuming I do not need Nvidia drivers since I am using an AMD processor with AMD Radeon integrated graphics (correct me if I’m wrong).

The active GPU driver is:
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon Graphics (radeonsi, renoir, LLVM 19.1.7, DRM 3.59, 6.12.11-200.fc41.x86_64)

[quote=“Jerry John, post:3, topic:144407, username:jerryjohn”]
I am wondering if its okay to keep SecureBoot disabled.
[/quote]y

That depends on your use case, but even if secure boot (SB) isn’t critical for your purposes, enabling it may reveal issues that might affect others in the linux community who do need the added layer of security it provides. If you find it creates problems or is too much extra work, it is not hard to disable it (but you should report the issues).

1 Like

the github page you linked to has the neccessary steps listed how to enroll the key

Every driver must be signed. All drivers / modules that are distributed with the kernel are already signed with a key that your system trusts.

Drivers not distributed with the kernel, are signed with a custom key, which is created on-the-fly by the host. This key is not known and not trustworthy unless it has been enrolled/imported.

Btw, it’s a DisplayLink framebuffer, the GPU is not really involved here. It may help the DisplayLink driver in mathematical computations. It’s basically a USB3toHDMI or USB3toDisplayPort adapter.

Real USB-C or Thunderbolt docks use native DisplayPort and do not require additional 3rd party drivers. But they require a host system that can provide video (DisplayPort) via an USB-C port.

1 Like

The issue persisted when I enabled SecureBoot again.

I tried following the steps to enroll the key as per the guidelines on github: how to enroll the key

Ended up with the issue that /var/lib/dkms/mok.pub file does not exist.

Removed and installed dkms. Still could not see the ‘mok.pub’ file and sudo dkms status returned empty.

Removed displayLink. Reinstalled it. This time by downloading and installing the rpm package from: Release v6.1.0-2 (re-released) · displaylink-rpm/displaylink-rpm · GitHub

The install completed with some non-critical error associated with evdi. But after this,
sudo dkms status returned:
evdi/1.14.7, 6.12.11-200.fc41.x86_64, x86_64: installed (Original modules exist)

and /var/lib/dkms/mok.pub key was generated. Now I was able to complete the steps: how to enroll the key

Now the external display is working with SecureBoot enabled.

Thank you so much for the help with this issue!

1 Like

I understand. I have added a reply on how I was able to solve the issue with SecureBoot enabled, by enrolling MOK. I’m not quite used to this forum so let me know if I have to post it somewhere else.

1 Like

Glad you got display via USB-C dock working. Others with similar issues should be able to find this topic and all the details are available, so good contribution to the community.

I wouldn’t call this a USB-C dock, because they also work on an USB-A port.
These docks are usually supplied with a USB-A to USB-C adapter.

Agree, but I assume HP marketing is responsible for the name. It is much better to have the full model number as there are several HP USB-C universal dock models.

I guess the hint is in the name USB-C/A and universal :slight_smile:

Lenovo sell a similar dock Hybrid USB-C with USB-A Dock.