PC sends data, no video output from GPU or iGPU via DP or HDMI, yet DVI outperforms HDMI
PC sends data, no video output from GPU or iGPU via DP or HDMI, yet DVI outperforms HDMI
Because it is DVI-D it verifies that the DDC wire (EDID data) is present.
If you start your system in the correct output with the DVI-D link and look at the available video modes, does it display all of the monitor's options? If only "standard" modes appear it could indicate a lack of self-reporting configuration information.
In Linux it's possible to install the package "mesa-utils" (you're unsure which distribution you're using), which includes the utility "glxinfo". Could you share the output of:
glxinfo | grep -i version
Also, the output of:
xrandr
If you want to save those results:
glxinfo | grep -i version 2>&1 | tee info.txt
xrandr 2>&1 | tee xrandr.txt
This will display more details. In the latter, you'll find a section labeled "EDID" for any monitor with that information. Whether this data exists or not is crucial. You can visit www.edidreader.com to view the specifications and see if the monitor self-reports.
Since you're using Linux, debugging might be simpler. If you connect a non-functional monitor (even after booting), and then run "xrandr --props" again, you can verify if EDID is available and matches the DVI-D version of EDID. The presence or absence of this data matters. For monitors that don't work, you may need to use SSH to check:
For the failing monitor, an SSH login might be necessary (avoid using "ssh -X" or "ssh -Y"; instead, run "export DISPLAY=:0" in your command line before debugging). This helps determine how the configuration is handling the session. It will show you whether the discrete GPU is NVIDIA or AMD, or another type.
Nvidia.
I should mention since getting DP/HDMI to output a signal after hours of troubleshooting the system has been working fine, just as it was before the incident. BIOS is back to the previous configuration (testing each change before making the next), displays and GPU setup too, using the discrete GPU output DP>mDP to display 1, then daisy chaining DP>DP from display 1 to display 2.
Code:
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
OpenGL core profile version string: 4.6.0 NVIDIA 580.95.05
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL version string: 4.6.0 NVIDIA 580.95.05
OpenGL shading language version string: 4.60 NVIDIA
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 580.95.05
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
GL_EXT_shader_group_vote, GL_EXT_shader_implicit_conversions,
(shorter version)
Code:
Screen 0: minimum 8 x 8, current 4480 x 1080, maximum 32767 x 32767
DP-0.8 connected primary 1920x1080+2560+0 (normal left inverted right x axis y axis) 527mm x 296mm
1920x1080 60.00*+ 60.00 59.94 50.00 23.98
1280x1024 75.02 60.02
1280x720 60.00 59.94 50.00
1152x864 75.00
1024x768 75.03 60.00
800x600 75.00 60.32
720x576 50.00
720x480 59.94
640x480 75.00 59.94 59.93
DP-0.1 connected 2560x1080+0+0 (normal left inverted right x axis y axis) 798mm x 334mm
2560x1080 59.98 + 74.99* 50.00
1920x1080 74.91 60.00 59.94 50.00
1680x1050 59.95
1600x900 60.00
1280x1024 75.02 60.02
1280x800 59.81
1280x720 60.00 59.94 50.00
1152x864 59.96
1024x768 75.03 60.00
800x600 75.00 60.32
720x576 50.00
720x480 59.94
640x480 75.00 59.94 59.93
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 disconnected (normal left inverted right x axis y axis)
DP-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-3 disconnected (normal left inverted right x axis y axis)
Small note about displays: The only issue I usually experience seems 100% software related. Sometimes display 2 won't be detected by the system after being put into stand by/power saving mode unless I manually turn it off and back on if the system is already up or poke the display 2 button to wake it before the system so it's actively seeking a signal.
It feels like the OS tries to re-detect displays and ignores it when the display 2 doesn't turn on quickly enough. I've tried to setup it in xorg.conf without luck (but at least the OS remembers position and resolution once detected) and have been just living with it for the time being. It's also unrelated to the no signal issue I experienced.
The issue didn't look like both displays failing to get a signal but the computer failing to send a signal. Here's the
xrand --props
EDID part:
Code:
s
Screen 0: minimum 8 x 8, current 4480 x 1080, maximum 32767 x 32767
DP-0.8 connected primary 1920x1080+2560+0 (normal left inverted right x axis y axis) 527mm x 296mm
_KDE_SCREEN_INDEX: 1
CTM: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
GUID: {10DE9070-0000-0000-00A2-55B4000000B0}
EDID:
00ffffffffffff0010ace74053595841
1a1b0104a5351e783aee95a3544c9926
0f5054a54b00714f8180a940d1c00101
010101010101023a801871382d40582c
45000f282100001e000000ff0058564e
4e54373651415859530a000000fc0044
454c4c205532343137480a20000000fd
00324b1e5311000a2020202020200123
02031df1509005040302071601061112
1513141f2023091f0783010000023a80
1871382d40582c25000f282100001e01
1d8018711c1620582c25000f28210000
9e011d007251d01e206e2855000f2821
00001e8c0ad08a20e02d10103e96000f
28210000180000000000000000000000
00000000000000000000000000000075
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: DisplayPort
supported: DisplayPort
ConnectorType: DisplayPort
ConnectorNumber: 4
_ConnectorLocation: 4
non-desktop: 0
supported: 0, 1
1920x1080 60.00*+ 60.00 59.94 50.00 23.98
1280x1024 75.02 60.02
1280x720 60.00 59.94 50.00
1152x864 75.00
1024x768 75.03 60.00
800x600 75.00 60.32
720x576 50.00
720x480 59.94
640x480 75.00 59.94 59.93
DP-0.1 connected 2560x1080+0+0 (normal left inverted right x axis y axis) 798mm x 334mm
GUID: {10DE9070-0000-0002-C07C-4E4400000056}
EDID:
00ffffffffffff001e6d157701010101
011c0104b55022789fca95a6554ea126
0f5054256b807140818081c0a9c0b300
d1c08100d1cfcd4600a0a0381f403020
3a001e4e3100001a023a801871382d40
582c45001e4e3100001e000000fd0028
4b5a5a18010a202020202020000000fc
004c472048445220574648440a2001f7
02031e712309070749100403011f1359
da1283010000e305c000e30605018c0a
d08a20e02d10103e96001e4e31000018
295900a0a038274030203a001e4e3100
001a0000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
000000000000000000000000000000d7
_KDE_SCREEN_INDEX: 2
CTM: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: DisplayPort
supported: DisplayPort
ConnectorType: DisplayPort
ConnectorNumber: 4
_ConnectorLocation: 4
non-desktop: 0
supported: 0, 1
2560x1080 59.98 + 74.99* 50.00
1920x1080 74.91 60.00 59.94 50.00
1680x1050 59.95
1600x900 60.00
1280x1024 75.02 60.02
1280x800 59.81
1280x720 60.00 59.94 50.00
1152x864 59.96
1024x768 75.03 60.00
800x600 75.00 60.32
720x576 50.00
720x480 59.94
640x480 75.00 59.94 59.93
Since it already works I'm just replying to explain some of the output for future use.
Your GPU driver from
glxinfo
shows it is an actual NVIDIA driver, at least for OpenGL. If you were to manually install the driver, then this is version 580.95.05.
The
xrandr
shows available modes. Technically, there are simple ways you could pass any of those modes to the GPU on the kernel command line right at the start of boot (which can help if you want to set modes before the GUI loads; some people don't use the GUI). Seeing those modes also says configuration is generally working. However, the display which sometimes does not detect, might make use of this. I'll say more below.
Your EDID cleans up as:
0x00 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0x00 0x10 0xAC 0xE7 0x40 0x53 0x59 0x58 0x41 0x1A 0x1B 0x01 0x04 0xA5 0x35 0x1E 0x78 0x3A 0xEE 0x95 0xA3 0x54 0x4C 0x99 0x26 0x0F 0x50 0x54 0xA5 0x4B 0x00 0x71 0x4F 0x81 0x80 0xA9 0x40 0xD1 0xC0 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x02 0x3A 0x80 0x18 0x71 0x38 0x2D 0x40 0x58 0x2C 0x45 0x00 0x0F 0x28 0x21 0x00 0x00 0x1E 0x00 0x00 0x00 0xFF 0x00 0x58 0x56 0x4E 0x4E 0x54 0x37 0x36 0x51 0x41 0x58 0x59 0x53 0x0A 0x00 0x00 0x00 0xFC 0x00 0x44 0x45 0x4C 0x4C 0x20 0x55 0x32 0x34 0x31 0x37 0x48 0x0A 0x20 0x00 0x00 0x00 0xFD 0x00 0x32 0x4B 0x1E 0x53 0x11 0x00 0x0A 0x20 0x20 0x20 0x20 0x20 0x20 0x01 0x23 0x02 0x03 0x1D 0xF1 0x50 0x90 0x05 0x04 0x03 0x02 0x07 0x16 0x01 0x06 0x11 0x12 0x15 0x13 0x14 0x1F 0x20 0x23 0x09 0x1F 0x07 0x83 0x01 0x00 0x00 0x02 0x3A 0x80 0x18 0x71 0x38 0x2D 0x40 0x58 0x2C 0x25 0x00 0x0F 0x28 0x21 0x00 0x00 0x1E 0x01 0x1D 0x80 0x18 0x71 0x1C 0x16 0x20 0x58 0x2C 0x25 0x00 0x0F 0x28 0x21 0x00 0x00 0x9E 0x01 0x1D 0x00 0x72 0x51 0xD0 0x1E 0x20 0x6E 0x28 0x55 0x00 0x0F 0x28 0x21 0x00 0x00 0x1E 0x8C 0x0A 0xD0 0x8A 0x20 0xE0 0x2D 0x10 0x10 0x3E 0x96 0x00 0x0F 0x28 0x21 0x00 0x00 0x18 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x75
You could copy and paste that into the
https://www.edidreader.com/
utility and see the exact specifications of your monitor such that this is what your PC sees. Available modes are the intersection of the shown monitor EDID modes and the NVIDIA driver capabilities (the
xrandr
).
About the monitor which is not reliably detected...
Setting a specific resolution on that port won't necessarily cause detection, but it will mean that details of the monitor will be set up before it is used. It might work more reliably.
There are other details, but the gist is that the kernel command line can be found in the GRUB2 configuration file, usually here:
/boot/grub/grub.cfg
This file is generated, and there are ways to set defaults via (I'm using Ubuntu, but this usually applies to Fedora and some others; details might change for distribution, but the kernel itself will be standard), but use a text editor and look at the
grub.cfg
. There is a lot to that file, but when you get to actual "
menuentry
" (there are usually several, but one is default), the line "
linux
" is the command line for when the kernel is loading. That line is a very long space-delimited value, so be sure not to fragment it into multiple lines (hopefully the editor uses word wrap which is visible only and doesn't actually insert newlines). With a space and then a token without spaces you can add parameters (this works until GRUB2 is updated; there is a second location to add this if you want it to remain during auto generation of GRUB2 parameters from default settings, e.g., upon GRUB2 update). The "
video
" token can name a particular screen from the "
xrandr
" along with the requested mode. I will give you an example, adjust this for the particular video port and mode you want (there is a leading space and this is appended to the "linux" line for a given boot entry):
DP-0.1:[email protected]
In some cases this might also work for the video framebuffer console in text mode prior to reaching the GUI (you'd have to check it to be sure, don't know). I find this is most useful with (A) multiple monitors, or (B) when using a KVM switch.
You can copy a given GRUB2 entry and make a second entry, but please research before you do that. The different entries can have different values. You can also try this
for a single boot
if your GRUB2 menu has enough delay to hit a key and stop boot in the GRUB2 menu. The "
e
" key allows editing. You can go to your boot entry, find the "
linux
" line, and append that same
[email protected]
; then use "
CTRL+x
" to execute (boot) that modified entry. This will only have an effect on one boot so it is easy to experiment without risk.
If you like that, then you can go to your "
/etc/default/grub
" file, and edit that. Things like timeout and
GRUB_CMDLINE_LINUX_DEFAULT
can be edited. I use a timeout of 20 seconds on machines without multiboot, and usually over 200 seconds if I multiboot. An example of setting that video parameter, with a leading space:
GRUB_CMDLINE_LINUX_DEFAULT=" video=DP-0.1:[email protected]"
If you want to do that, then the next time GRUB2 updates it will have that in the command line. Or you can manually run "
sudo update-grub
". Details change depending on which distribution you use, but GRUB2 itself tends to be standard, along with kernel parameters. It is possible this will make your monitor detection work better.