You are not logged in.
Hi,
I've used a USBC-to-HDMI cable previously to connect to an external monitor with no issue (1600x900). I just bought a used Alienware monitor from a friend who doesn't want it (1920x1080) and it's not working. I'm on kernel 4.14 with my hardware all completely updated. When I initially plug in the monitor, the screen flashes and I can see the monitor in the gnome display settings as well as this output in xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 294mm x 165mm
1920x1080 59.93*+
1400x1050 59.98
1280x1024 60.02
1280x960 60.00
1024x768 60.04 60.00
960x720 60.00
928x696 60.05
896x672 60.01
800x600 60.00 60.32 56.25
700x525 59.98
640x512 60.02
640x480 60.00 59.94
512x384 60.00
400x300 60.32 56.34
320x240 60.05
DP-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 477mm x 268mm
1920x1080 60.00*+ 50.00 59.94
1920x1080i 60.00 50.00 59.94
1280x1024 75.02 60.02
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 60.00
800x600 75.00 60.32
720x576 50.00
720x480 60.00 59.94
640x480 75.00 60.00 59.94
720x400 70.08
DP-2 disconnected (normal left inverted right x axis y axis)After about 2 sec, the screen flashes again and xrandr/gnome settings no longer sees the monitor.
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 294mm x 165mm
1920x1080 59.93*+
1400x1050 59.98
1280x1024 60.02
1280x960 60.00
1024x768 60.04 60.00
960x720 60.00
928x696 60.05
896x672 60.01
800x600 60.00 60.32 56.25
700x525 59.98
640x512 60.02
640x480 60.00 59.94
512x384 60.00
400x300 60.32 56.34
320x240 60.05
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)The monitor gives me the error message "There is no signal coming from your computer".
Journalctl gives
Jan 08 10:50:11 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): EDID vendor "SHP", prod id 5193
Jan 08 10:50:11 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): Printing DDC gathered Modelines:
Jan 08 10:50:11 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 -hsync -vsync (66.6 kHz eP)
Jan 08 10:50:11 ryan /usr/lib/gdm/gdm-x-session[3881]: (WW) EDID timing clock 148.50 exceeds claimed max 85MHz, fixing
Jan 08 10:50:11 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): Allocate new frame buffer 3200x1080 stride
Jan 08 10:50:11 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): EDID vendor "SHP", prod id 5193
Jan 08 10:50:11 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): Printing DDC gathered Modelines:
Jan 08 10:50:11 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 -hsync -vsync (66.6 kHz eP)
Jan 08 10:50:11 ryan /usr/lib/gdm/gdm-x-session[3881]: (WW) EDID timing clock 148.50 exceeds claimed max 85MHz, fixing
Jan 08 10:50:11 ryan gsd-color[3592]: no xrandr-LONTIUM-2533359616 device found: Failed to find output xrandr-LONTIUM-2533359616
Jan 08 10:50:14 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): EDID vendor "SHP", prod id 5193
Jan 08 10:50:14 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): Printing DDC gathered Modelines:
Jan 08 10:50:14 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 -hsync -vsync (66.6 kHz eP)
Jan 08 10:50:15 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): Allocate new frame buffer 1920x1080 stride
Jan 08 10:50:15 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): EDID vendor "SHP", prod id 5193
Jan 08 10:50:15 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): Printing DDC gathered Modelines:
Jan 08 10:50:15 ryan /usr/lib/gdm/gdm-x-session[3881]: (II) modeset(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 -hsync -vsync (66.6 kHz eP)The monitor does not work when using the same cable on windows but using a HDMI-DVI or HDMI-HDMI cable from windows (on a desktop machine) works perfectly fine. I would guess it's the cable then, but the same cable has worked with another monitor and the fact that it sees the monitor for a split second doesn't make sense to me.
Offline
It might well be the cable. Some hardware is more tolerant than others to a bad cable that transmits bad signal. It may well be that your other monitor is more tolerant of bad signal. The fact that xrandr (or Gnome) see the monitor for a split of a second is entirely consistent to that. The signal is just at the threshold of what the monitor can detect. I think also the higher resolution of this monitor requires a better quality signal (I am not completely sure, being not a specialist in HDMI signal). I remember having similar issues with a long (10m) low-quality HDMI cable:
The fact that it does not work in Windows shows that it is not likely a configuration/driver problem. The fact that your monitor works with another connection shows that the monitor is OK. I would try to connect a better cable but it is impossible to know for sure in advance. Instead of the cable, it may well be some sort of internal connexion that is bad.
Last edited by olive (2018-01-09 15:48:28)
Offline
So I bought a new USBC-HDMI cable that was specified up to a 4k resolution. Now when I plugged in, I got 0 response from the higher resolution monitor (it just says that there is no cable - xrandr/gnome show nothing) while it works perfectly fine with the lower res monitor. Does the USBC not support the 1920x1080 resoultion??
Offline
FWIK USBC is just the shape of the plug and says nothing about what is really supported. Anyway, I don't think any recent material can support HDMI without supporting 1920x1080 which is pretty standard.
Offline
Ok, so I bought a USBC-HDMI (female instead of male) adapter and now the monitor works with a normal HDMI cable.
Offline