UNSOLVED

felagund

updated

1 year ago

F

felagund

1 Rookie

•

17 Posts

•

2 Points

0

41

August 19th, 2025 08:29

U4320Q, USB-C Prioritization set to "High Data Speed" makes USB3 devices invisible

I have a U4320Q monitor connected through USB-C to my computer running Fedora 42. When I set the monitor's "USB-C Prioritization" to "High Data Speed", the monitor indeed reports that it is connected through HBR3 and the reported quality of the connection is USB3.1. However, the USB-C port of the monitor then stops recognizing any USB3+ devices like a SSD hard drive or a 1gbit ethernet cable connected through a USB-C<>ethernet connector . It always reliably picks up my USB-C mouse or Android phone, which only use USB2. When I set USB-C prioritization to "High Resolution", I lose HBR3 and only get USB2 speeds. This applies to all the USB ports on the monitor, wherever they are positioned and whether they are type A or C.

 

I am positive this is not a cable problem, as I am using a cables that have no problems supporting USB3 speeds when connecting directly to my laptop.

Any ideas what is wrong and how can I fix that? I will try to get a hang of a Windows computer to see if it is a OS thing. By the way I can see in my router's log that when I connect the ethernet cable through the USB-C convertor, the router puts the link up, so there is some signals flowing in between them, just nothing ever seems to reach my computer, the USB hub in the monitors just eats everything and never seems to spit anything out.

There is a forum thread, now closed, which suggests this might be expected. I am not sure how to interpret it. The table there seems to suggest this is the expected behaviour, however the manual says otherwise and a user there claims the table is wrong. I am also able to get HBR3 reported by the monitor, but then in practice it does not seem to work.

I tried to post this question yesterday, I got an e-mail that the post was altered, but now I cannot find it. I do not understand what is happening there. I edited the question as compared to the version from yesterday as I was able to get more precise about the problem.

No Responses