I’ve been running Manjaro for not long, so it might be a case of pointing me to the proper Arch wiki page
I have a Dell Latitude 5510 laptop connected to a WD19 dock (the base USB-C version, not the S nor the thunderbolt one) and the monitor connected to the HDMI port of the latter stays black, despite being registered properly.
- It all works on the Windows partition. It also works in Manjaro with the HDMI cable in the laptop port, so it has to be an issue with the dock.
- BIOS and dock firmware are up-to-date :
# fwupdmgr get-updates
Devices with the latest available firmware version:
• PC SN530 NVMe WDC 512GB
• System Firmware
(confirmed in the windows partition)
- And the second monitor is detected:
# xrandr --current
Screen 0: minimum 320 x 200, current 1921 x 2160, maximum 16384 x 16384
eDP-1 connected primary 1920x1080+1+1080 (normal left inverted right x axis y axis) 344mm x 194mm
[... Laptop monitor ...]
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
DP-1-1 disconnected (normal left inverted right x axis y axis)
DP-1-2 disconnected (normal left inverted right x axis y axis)
DP-1-3 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 476mm x 268mm
1920x1080 60.00*+ 50.00 59.94
1280x720 60.00 50.00 59.94
720x480 60.00 59.94
640x480 60.00 59.94
It properly shows in display settings and get my cursor “through it”.
- I tried fiddling with the relevant BIOS options with no success. (I can’t put my hands back on a post suggesting that an option to “always allow Dell dock” or something like that needed to be deactivated, but couldn’t find such option.)
There is a similar issue on the forum, that got closed with no solution.
See if this discussion might give you some hints:
Thanks for the answer! Yes, I saw that thread earlier, however, it is not of much help, sadly. I don’t own the thunderbolt version of the dock, so most of the troubleshooting steps he does won’t work, and I merely have an Intel iGPU, so forget about the bumblebee workaround (which he abandoned in the end, anyway).
Could it be that the HDMI signal is somehow recognised as a DisplayPort one? The USB-C cable indeed is a DP one, and it appears to not be an issue for others though…
# xrandr --verbose
DP-1-3 connected 1920x1080+0+0 (0x99) normal (normal left inverted right x axis y axis) 476mm x 268mm
CRTCs: 0 1 2
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
max bpc: 12
range: (6, 12)
HDCP Content Type: HDCP Type0
supported: HDCP Type0, HDCP Type1
Content Protection: Undesired
supported: Undesired, Desired, Enabled
Broadcast RGB: Automatic
supported: Automatic, Full, Limited 16:235
supported: force-dvi, off, auto, on
supported: Good, Bad
CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0
range: (0, 1)
1920x1080 (0x99) 148.500MHz +HSync +VSync *current +preferred
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.50KHz
v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz
A little update (and bump ).
I have tried with a Sitecom CN-389 USB-C hub and got the same result : the monitor is detected properly, and can be activated, itself detects something is connected, but doesn’t display anything, i.e. it stays idle. Edit : tried with a simple usb-c to hdmi adapter and got the same result.
As a reminder, it works properly on a windows partition (with both hubs) and when I plug the HDMI cable directly into the laptop, so the hardware and firmware are not at fault.
inxi outputs unchanged. I just note, once again, that the monitor is listed as a DP output, as far as I understand it, while it is connected as
HDMI-2 when directly plug :
0: +*eDP-1 1920/344x1080/194+1+1080 eDP-1
1: +DP-1-8 1920/476x1080/268+0+0 DP-1-8
I may speak nonsense, but could it be that X sends “DP formatted data” instead of “HDMI data” to the monitor and that would be the cause of the issue? If so, is there a way to fiddle with xrandr and change that ?
Note : I was persuaded DisplayLink driver wasn’t needed, since my devices are not listed on their site as containing a relevant chip, so didn’t try until now. I gave it a go. It required building the git build of
edvi. Either way,
xrandr --listproviders only lists one provider :
modesetting, so it doesn’t seem to resolve my issue.