(SOLVED) Occasional screen flicker and black square around windows

[redpinkoZ1917]

Did you see these warning lines from the log file:

Code: Select all

[  1937.578] (WW) NVIDIA(0): Unable to use EDID file '/home/redpinko/edid.bin,
[ 1937.578] (WW) NVIDIA(0): DP-1:/home/redpinko/edid2.bin': No such file or directory

I've switched the directory twice now, and I cannot seem to get it to read those files. They are definitely in there

[roblm]

This line should have a semicolon between the two EDID files, but yours has a comma:

Code: Select all

Option "CustomEDID" "DP-0:/home/redpinko/edid.bin; DP-1:/home/redpinko/edid2.bin"

[redpinkoZ1917]

This line should have a semicolon between the two EDID files, but yours has a comma:

Code: Select all

Option "CustomEDID" "DP-0:/home/redpinko/edid.bin; DP-1:/home/redpinko/edid2.bin"

It still can't find it, even after fixing that.

[roblm]

This is the exact same problem when you attempted to use an EDID file in your other post.

Code: Select all

[    71.882] (WW) NVIDIA(GPU-0): Unable to use EDID file '/home/redpinko/.edid.bin': No such
[    71.882] (WW) NVIDIA(GPU-0):     file or directory

I told you to switch the location to the Downloads folder and to try changing DP-1 to DFP-1. DP-0 would be changed to DFP-0.

DP-1 was the LG monitor in your other post, but with two monitors now connected, it is called DP-0. The EDID files may not be representing the correct monitors, so try switching them:

Code: Select all

[  1937.590] (II) NVIDIA(0): Display (LG Electronics LG ULTRAWIDE (DFP-0)) does not support
[  1937.590] (II) NVIDIA(0):     NVIDIA 3D Vision stereo.
[  1937.604] (II) NVIDIA(0): Display (Tech Concepts TCL (DFP-1)) does not support NVIDIA 3D
[ 1937.604] (II) NVIDIA(0): Vision stereo.

[redpinkoZ1917]

The EDID files have been found, but I am still unable to switch resolutions. I was reccomended to add NoMaxPClkCheck to the mode validation string, and it did give me the option to select 2560x1080 as a resolution. One I selected it, however, my computer gave me another black screen freeze, and I could not boot into the system unless I deleted that new setting from the mode validation string.

[roblm]

I suggest removing the EDID for the TCL monitor in the xorg.conf file because it probably won’t be needed. Then post the output of xrandr --prop and the Xorg.0.log file.

[redpinkoZ1917]

I suggest removing the EDID for the TCL monitor in the xorg.conf file because it probably won’t be needed. Then post the output of xrandr --prop and the Xorg.0.log file.

Edid removed from xorg.conf:

Here is Xorg.0.log

xrandr --prop:

Code: Select all

xrandr --prop
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 16384 x 16384
DP-0 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 798mm x 334mm
	EDID: 
		00ffffffffffff001e6df1599f970000
		031b010380502278eaca95a6554ea126
		0f5054a54b80714f818081c0a9c0b300
		0101010101017e4800e0a0381f404040
		3a001e4e31000018023a801871382d40
		582c45001e4e3100001e000000fc004c
		4720554c545241574944450a000000fd
		00384b1e5a18000a20202020202001d0
		02031df14a900403221412051f011323
		0907078301000065030c002000023a80
		1871382d40582c450056512100001e01
		1d8018711c1620582c25005651210000
		9e011d007251d01e206e285500565121
		00001e8c0ad08a20e02d10103e960056
		51210000180000000000000000000000
		00000000000000000000000000000068
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: TMDS 
		supported: TMDS
	ConnectorType: DisplayPort 
	ConnectorNumber: 0 
	_ConnectorLocation: 1 
   1920x1080     60.00*+  59.94    50.00    29.97    60.05    60.00    50.04  
   1680x1050     59.95  
   1600x900      60.00  
   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-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 800mm x 450mm
	EDID: 
		00ffffffffffff00506c000001010101
		031b0103805932780a0dc9a057479827
		12484ca14b008180d1c0590f01010101
		010101010101023a801871382d40582c
		450020c23100001e011d007251d01e20
		6e28550044402100001e000000fc0054
		434c0a202020202020202020000000fd
		0032550e4610000a20202020202001f1
		02032d70521413121116150504030207
		06011f102021228301000067030c0020
		00b82d29097f01157f50570700011d80
		d0721c1620102c258044402100009e01
		1d8018711c1620582c25004440210000
		98011d00bc52d01e20b8285540444021
		00001e011d007251d01e206e28550044
		4021001e000000000000000000000032
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: TMDS 
		supported: TMDS
	ConnectorType: DisplayPort 
	ConnectorNumber: 1 
	_ConnectorLocation: 2 
   1920x1080     60.00*+  59.94    50.00    29.97    25.00    23.97    60.05    60.00    50.04  
   1280x1024     75.02    60.02  
   1280x720      60.00    59.94    50.00  
   1280x660      60.00  
   1024x768      75.03    60.00  
   960x600       75.00  
   800x600       75.00    60.32  
   720x576       50.00    50.08  
   720x480       59.94    60.05  
   640x480       59.94    59.93  
DP-2 disconnected (normal left inverted right x axis y axis)
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: DisplayPort 
		supported: DisplayPort
	ConnectorType: DisplayPort 
	ConnectorNumber: 0 
	_ConnectorLocation: 1 
DP-3 disconnected (normal left inverted right x axis y axis)
	BorderDimensions: 4 
		supported: 4
	Border: 0 0 0 0 
		range: (0, 65535)
	SignalFormat: DisplayPort 
		supported: DisplayPort
	ConnectorType: DisplayPort 
	ConnectorNumber: 1 
	_ConnectorLocation: 2 

[roblm]

The nvidia-340 driver appears to have no problem reading the EDID file and this info is from it: max dotclock 240MHz

Would you restart your system with the TLC monitor disconnected. Post the Xorg.0.log.

[redpinkoZ1917]

The nvidia-340 driver appears to have no problem reading the EDID file and this info is from it: max dotclock 240MHz

Would you restart your system with the TLC monitor disconnected. Post the Xorg.0.log.

Here you go

[roblm]

The same warning message:

Code: Select all

[    69.517] (WW) NVIDIA(GPU-0):     Mode is rejected: PixelClock (185.6 MHz) too high for
[ 69.517] (WW) NVIDIA(GPU-0): Display Device (Max: 165.0 MHz).

So with everything set identical to your previous topic, the obvious conflict is coming from the older nvidia-340 driver.

I know you have been seeking help at the same time on the Nvidia Linux Graphics forum. Next to Aaron Plattner, the moderator, user generix is probably the most knowledgeable person who contributes to that forum. I know he already asked you to try the attributes NoMaxPClkCheck and NoEdidMaxPClkCheck, but can you try them again along with AllowNonEdidModes in these two lines:

Code: Select all

Option "ModeValidation" "NoMaxPClkCheck, AllowNonEdidModes, NoExtendedGpuCapabilitiesCheck"
Option "ModeValidation" "NoEdidMaxPClkCheck, AllowNonEdidModes, NoExtendedGpuCapabilitiesCheck"

[redpinkoZ1917]

The same warning message:

Code: Select all

[    69.517] (WW) NVIDIA(GPU-0):     Mode is rejected: PixelClock (185.6 MHz) too high for
[ 69.517] (WW) NVIDIA(GPU-0): Display Device (Max: 165.0 MHz).

So with everything set identical to your previous topic, the obvious conflict is coming from the older nvidia-340 driver.

I know you have been seeking help at the same time on the Nvidia Linux Graphics forum. Next to Aaron Plattner, the moderator, user generix is probably the most knowledgeable person who contributes to that forum. I know he already asked you to try the attributes NoMaxPClkCheck and NoEdidMaxPClkCheck, but can you try them again along with AllowNonEdidModes in these two lines:

Code: Select all

Option "ModeValidation" "NoMaxPClkCheck, AllowNonEdidModes, NoExtendedGpuCapabilitiesCheck"
Option "ModeValidation" "NoEdidMaxPClkCheck, AllowNonEdidModes, NoExtendedGpuCapabilitiesCheck"

Option "ModeValidation" "NoEdidMaxPClkCheck, AllowNonEdidModes, NoExtendedGpuCapabilitiesCheck"
^managed to bump the available options up to 2048x1152, but the other froze my system.

[roblm]

I forgot to tell you to post the Xorg.0.log for the ModeValidation line that allowed you to get to the desktop.

[roblm]

You haven't replied in a while so I’m posting the next step because I’m finished for today.

This method will try forcing the mode. With only the LG monitor connected, add this line to the first Monitor section:

Code: Select all

Modeline "2560x1080_60.00"  185.58  2560 2624 2688 2784  1080 1083 1093 1111  -HSync  -Vsync

Use this ModeValidation line:

Code: Select all

Option "ModeValidation" "NoXserverModes, NoVesaModes, NoEdidModes, AllowNonEdidModes, NoExtendedGpuCapabilitiesCheck"

Post the Xorg.0.log if that doesn’t work.

[redpinkoZ1917]

Here is the log Suggestions didn't work.

My kvm switch is definitely giving me the problems. I bought a 4k 60hz capable hdmi cable for kvm input and another one for output, and I got a 4k 60hz capable DP to HDMI converter, plugged it all in, and my monitor showed the HP logo for the bios then it cut out. After that, the signal would not be picked up at all by my monitor no matter how many times I rebooted. I then plugged the upgraded cable with upgraded dongle directly into my monitor, and the resolution was detected instantly. The GRUB splash even loaded at the correct resolution which was another problem altogether.

My KVM switch is 4k capable too, so this makes it all the more frustrating.

[roblm]

That log file was not the correct one. You had both monitors connected but I said to only connect the LG. This ModeValidation line which I said to test is not listed:

Code: Select all

Option "ModeValidation" "NoXserverModes, NoVesaModes, NoEdidModes, AllowNonEdidModes, NoExtendedGpuCapabilitiesCheck"

You must have generated a new xorg.conf file using Nvidia Settings because there are extra lines in it now.

[redpinkoZ1917]

Sorry about that. I believe this is the correct log with the single monitor attatched:
link
System will only allow me an 800x600 resolution now.

Here is my current xorg file just to make sure we're on the same page:

Code: Select all

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Option         "Xinerama" "0"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "LG Electronics LG ULTRAWIDE"
    HorizSync       30.0 - 90.0
    VertRefresh     56.0 - 75.0
    Modeline       "2560x1080_60.00"  185.58  2560 2624 2688 2784  1080 1083 1093 1111  -HSync  -Vsync
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    ModelName      "Tech Concepts TCL"
    HorizSync       14.0 - 70.0
    VertRefresh     50.0 - 85.0
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "NVS 310"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "ForceFullCompositionPipeline" "true"
    Option         "ModeValidation" "NoXserverModes, NoVesaModes, NoEdidModes, AllowNonEdidModes, NoExtendedGpuCapabilitiesCheck"
    Option         "ModeDebug" "true"
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-0"
    Option         "metamodes" "DP-0: 2560x1080_60.00 +1920+0, DP-1: nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

[roblm]

Add NoEdidMaxPClkCheck to the ModeValidation line. Use this line because DFP-0 has also been added:

Code: Select all

Option "ModeValidation" "DFP-0: NoXserverModes, NoVesaModes, NoEdidModes, AllowNonEdidModes, NoExtendedGpuCapabilitiesCheck, NoEdidMaxPClkCheck"

If that doesn't help, then add this line to the Device section: Option "UseEDID" "false"

Post the Xorg.0.log

[redpinkoZ1917]

its not workin

[roblm]

Unfortunately, the only option left is to add NoMaxPClkCheck to the ModeValidation line but this didn’t work previously. I can’t explain why the mode isn’t used. The monitor’s EDID shows max dotclock 240MHz. The only difference from your other topic and this one is using the nvidia-340 driver vs the 390. You could reinstall the 390 driver and see if the mode works like it did before. If it doesn’t, then there’s obviously some hardware limitation. If the mode works, then you could try installing the nvidia-384 driver from Nvidia’s website but I would need to give you detailed instructions.

[redpinkoZ1917]

I’ve ordered some new hardware that might do the trick, but if it doesn’t work then I’ll report back and try the 380 driver per your instructions.

Thanks for your help, and happy new year!