Display Link adapter not working

[catalyst]

Hello,
I have a Librem 13v4 with Qubes 4.1 installed. I have a second monitor and a mouse and keyboard working with it connected via a KVM switch. I have a third monitor that I am trying to connect via a USB to HDMI DIsplay Link adapter. I have managed to install the display link driver in dom0 and the display link adapter shows in the list of USB devices from the Qubes devices on the taskbar. However, the monitor still does not display anything. Am I missing something? Am I supposed to attach the display link adapter to dom0 in some way?

Many Thanks!

[tzwcfq]

@catalyst

Am I supposed to attach the display link adapter to dom0 in some way?

I don’t know if it possible to attach USB device from sys-usb to dom0.
If you attach one PCI USB controller to dom0 then you can use the USB devices connected to it in dom0.
Another option may be to create sys-gui and attach USB device from sys-usb to it but sys-gui for now is highly experimental:

How to install/use sys-gui (collecting all related information)

First, if you don’t know what sys-gui is, you need to read this first: Qubes Architecture Next Steps: The GUI Domain | Qubes OS Objective of this document: Currently (2021-10-01) the best documentation for on how to install/use sys-gui appears to be here. When 4.1 is formally released this information should be all that’s needed. However, If you attempt this at the current time (before the formal release), it’s easy to run into issues, so I’m going to document one install process that did wo…

[catalyst]

@tzwcfq

I don’t know if it possible to attach USB device from sys-usb to dom0.
If you attach one PCI USB controller to dom0 then you can use the USB devices connected to it in dom0.
Another option may be to create sys-gui and attach USB device from sys-usb to it but sys-gui for now is highly experimental:

I had issues with sys-gui. But apparently my display link adapter works without it. Weirdly enough I found that if I just logged off and then logged back in, the screen would then get detected. Not sure why this is and how to get it to become detected when the system starts up.