[Nouveau] Strange monitor behavior on forced DVI-D output
Ilia Mirkin
imirkin at alum.mit.edu
Sun Sep 23 18:05:12 UTC 2018
On Sun, Sep 23, 2018 at 1:48 PM, Wolfgang Rißler <wolle321 at freenet.de> wrote:
> Am Sonntag, den 23.09.2018, 12:55 -0400 schrieb Ilia Mirkin:
>> On Sun, Sep 23, 2018 at 12:26 PM, Wolfgang Rißler
>> <wolle321 at freenet.de> wrote:
> [snip]
>>
>> That's not extremely surprising ... force-enabling an output I think
>> might kill the resolution detection, and 1024x768 is the default. Why
>> are you force-enabling/disabling video outputs? That should not
>> generally be necessary.
>
> Ok, I would not force enabling/disabling an output, if it would be
> switched on automatically, but it doesnt.
> The system normally ()without forcing anything) starts with the LVDS-1
> on an the (connected) DVI-D-1 off:
>
> [ 17.636] (II) NOUVEAU(0): EDID for output LVDS-1
> [ 17.636] (II) NOUVEAU(0): Manufacturer: SEC Model: 3448 Serial#: 0
> [ 17.636] (II) NOUVEAU(0): Year: 2005 Week: 0
> [ 17.636] (II) NOUVEAU(0): EDID Version: 1.3
> [ 17.636] (II) NOUVEAU(0): Digital Display Input
> [ 17.636] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 37 vert.: 23
> [ 17.636] (II) NOUVEAU(0): Gamma: 2.20
> [ 17.636] (II) NOUVEAU(0): No DPMS capabilities specified
> [ 17.636] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
> [ 17.636] (II) NOUVEAU(0): First detailed timing is preferred mode
> [ 17.636] (II) NOUVEAU(0): redX: 0.580 redY: 0.340 greenX: 0.310 greenY: 0.550
> [ 17.636] (II) NOUVEAU(0): blueX: 0.155 blueY: 0.155 whiteX: 0.313 whiteY: 0.329
> [ 17.636] (II) NOUVEAU(0): Manufacturer's mask: 0
> [ 17.636] (II) NOUVEAU(0): Supported detailed timing:
> [ 17.636] (II) NOUVEAU(0): clock: 161.6 MHz Image Size: 367 x 230 mm
> [ 17.636] (II) NOUVEAU(0): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2208 h_border: 0
> [ 17.636] (II) NOUVEAU(0): v_active: 1200 v_sync: 1202 v_sync_end 1208 v_blanking: 1220 v_border: 0
> [ 17.636] (II) NOUVEAU(0): Unknown vendor-specific block f
> [ 17.636] (II) NOUVEAU(0): SAMSUNG
> [ 17.636] (II) NOUVEAU(0): 170CT02-001
> [ 17.636] (II) NOUVEAU(0): EDID (in hex):
> [ 17.636] (II) NOUVEAU(0): 00ffffffffffff004ca3483400000000
> [ 17.636] (II) NOUVEAU(0): 000f0103802517780a87f594574f8c27
> [ 17.636] (II) NOUVEAU(0): 27505400000001010101010101010101
> [ 17.636] (II) NOUVEAU(0): 010101010101233f802071b014403020
> [ 17.636] (II) NOUVEAU(0): 26006fe6100000190000000f00000000
> [ 17.636] (II) NOUVEAU(0): 000000000046d2026400000000fe0053
> [ 17.636] (II) NOUVEAU(0): 414d53554e470a2020202020000000fe
> [ 17.636] (II) NOUVEAU(0): 00313730435430322d3030310a2000d1
> [ 17.636] (II) NOUVEAU(0): Printing probed modes for output LVDS-1
> [ 17.636] (II) NOUVEAU(0): Modeline "1920x1200"x60.0 161.63 1920 1968 2000 2208 1200 1202 1208 1220 -hsync -vsync (73.2 kHz eP)
> [ 17.636] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 173.11 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync (67.2 kHz)
> [ 17.636] (II) NOUVEAU(0): Modeline "1600x1200"x60.0 161.23 1600 1712 1880 2160 1200 1203 1207 1245 -hsync +vsync (74.6 kHz)
> [ 17.636] (II) NOUVEAU(0): Modeline "1680x1050"x60.0 146.36 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz)
> [ 17.636] (II) NOUVEAU(0): Modeline "1400x1050"x60.0 121.79 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz)
> [ 17.636] (II) NOUVEAU(0): Modeline "1280x1024"x59.9 109.10 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync (63.7 kHz)
> [ 17.636] (II) NOUVEAU(0): Modeline "1280x960"x60.0 101.34 1280 1360 1488 1696 960 963 967 996 -hsync +vsync (59.8 kHz)
> [ 17.636] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.77 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz)
> [ 17.636] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.53 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz)
> [ 17.636] (II) NOUVEAU(0): Modeline "800x600"x60.0 38.31 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz)
> [ 17.636] (II) NOUVEAU(0): Modeline "640x480"x59.9 23.98 640 664 720 800 480 483 487 500 -hsync +vsync (30.0 kHz)
> [ 17.636] (II) NOUVEAU(0): Modeline "720x400"x60.0 22.41 720 744 808 896 400 403 413 417 -hsync +vsync (25.0 kHz)
> [ 17.636] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz)
> [ 17.636] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.52 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz)
> [ 17.637] (II) NOUVEAU(0): EDID for output DVI-D-1
> [ 17.638] (II) NOUVEAU(0): EDID for output DVI-D-2
> [ 17.649] (II) NOUVEAU(0): EDID for output VGA-1
> [ 17.649] (II) NOUVEAU(0): Output LVDS-1 connected
> [ 17.649] (II) NOUVEAU(0): Output DVI-D-1 disconnected
> [ 17.649] (II) NOUVEAU(0): Output DVI-D-2 disconnected
> [ 17.649] (II) NOUVEAU(0): Output VGA-1 disconnected
> [ 17.649] (II) NOUVEAU(0): Using exact sizes for initial modes
> [ 17.649] (II) NOUVEAU(0): Output LVDS-1 using initial mode 1920x1200 +0+0
> [ 17.649] (==) NOUVEAU(0): Using gamma correction (1.0, 1.0, 1.0)
>
> But I might like to have a multiscreen setting or a single screen DVI.
OK, well this is already bad. It's not detecting DVI-D-1 as connected.
I notice in your dmesg earlier, there's a message
[ 1.680769] nouveau 0000:01:00.0: mxm: unmatched output device
0103010201010100
which is probably the harbinger of the later failure. I don't know
anything offhand about how the mxm hookups work, but I'm pretty sure
we'd need to see a vbios to figure out what's off. Please include it
in the bug you file (/sys/kernel/debug/dri/0/vbios.rom).
Cheers,
-ilia
More information about the Nouveau
mailing list