GeForce GTX 1060 GPU with Nvidia-driver-525 Resolutions Problem

[mark bower]

System: Ubuntu-Mate 20.04, ;Samsung 40” TV, native resolution 3840 x 2160 HDMI 2.0; GTX 1060, HDMI 2.0; cable “high speed”.

Ubuntu will not display 2560 x 1600 or 2560 x 1440 pixels on my TV monitor with Nvidia “nvidia-driver 525-distro non-free recommended” installed. Software & Updates show this to be the correct driver to install. I need to be able to switch between resolutions 3840 x 2160 and 2560 x 1600.

xrandr shows the resolutions are not available. some other diagnostics:

mark@senior:~$ sudo lshw -c video
[sudo] password for mark: 
  *-display                 
       description: VGA compatible controller
       product: GP106 [GeForce GTX 1060 6GB]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nvidia latency=0
       resources: irq:136 memory:de000000-deffffff memory:c0000000-cfffffff memory:d0000000-d1ffffff ioport:e000(size=128) memory:c0000-dffff

mark@senior:~$ sudo ubuntu-drivers devices
== /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 ==
modalias : pci:v000010DEd00001C03sv00003842sd00006267bc03sc00i00
vendor   : NVIDIA Corporation
model    : GP106 [GeForce GTX 1060 6GB]
driver   : nvidia-driver-515 - distro non-free
driver   : nvidia-driver-525 - distro non-free recommended
driver   : nvidia-driver-515-server - distro non-free
driver   : nvidia-driver-525-server - distro non-free
driver   : nvidia-driver-418-server - distro non-free
driver   : nvidia-driver-390 - distro non-free
driver   : nvidia-driver-470-server - distro non-free
driver   : nvidia-driver-470 - distro non-free
driver   : nvidia-driver-450-server - distro non-free
driver   : nvidia-driver-510 - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

When I boot to Win10 or Win7 on the same PC, the 2560 x 1600 or 2560 x 1440 resolutions are available.

Is there a way to get Linux to display the "missing resolutions" which Win10 and Win7 display?

[TheFu]

X/Windows
or
Wayland?

Which DE - desktop environment - ah Mate. Most DEs have a User's Guide which explains how to control the screen resolution. Of course, if the TV doesn't work at the resolution + update speed, then it won't work. Both are important. The GPU shouldn't throw 2560 x 1600 @ 120Mhz to a TV that only supports 2560 x 1600 @ 30Mhz or 60Mhz. I didn't look it up, but that's my best guess.

BTW, 'lxrandr' is a simple GUI to control what xrandr does. I think you'll like it, but it only works for X/Windows, not Wayland.
For Wayland, I don't know.

[TheFu]

If the TV isn't telling the GPU the resolutions are available, probably not a good idea to force it. Is there any HDMI switch being used? Sometimes those block the EDID information from the monitor getting to the GPU.

There are some edid* commands on Linux so show what the GPU is being told. The data in the output from those commands can be used to create an xorg.conf modeline.

[mark bower]

I will check tomorrow on Xorg vs Wayland - does it make a difference? Mate: System>Control Center>Displays is where I can see available resolutions as well as the command line cmds. I have not set any HDMI switch as I do not know what/where it is. I can only reiterate that Win10 and Win7 have no problem.

[mark bower]

The PC is using X11. lxrandr is neat and shows the missing desired resolution: 2560 x 1600. Any suggestions for a fix?

[TheFu]

The PC is using X11. lxrandr is neat and shows the missing desired resolution: 2560 x 1600. Any suggestions for a fix?

Select the resolution you want and "Apply" then "Save".
Does that not work?

You can force the resolution to whatever you like using the automatic program running for your DE at login with something like this:

xrandr  --output VGA-1 --mode  1920x1200
xrandr  --output HDMI-1 --mode  1920x1080

You'll need to look up the specific output device and set the mode to match what 'xrandr' or 'lxrandr' sees to create the correct xrandr command.
There are all sorts of names, so don't expect yours to be like mine. If lxrandr fixed it, then xrandr can too.

[mark bower]

Select the resolution you want and "Apply" then "Save"

I am not clear re your suggestion: lxrandr does not show the needed resolution? So desired resolution is not available to select and save?

You can force the resolution to whatever you like using the automatic program running for your DE at login with something like this:

Are you saying that I can make an added resolution, which will be permanently available (not lost on reboot), via cmd line such as,

"xrandr --output HDMI-1 --mode 2560x1600" (the HDMI on the PC is in fact on HDMI-1)

[TheFu]

You said:

lxrandr is neat and shows the missing desired resolution: 2560 x 1600.

So I took that to mean that the desired resolution was being showed, so it could be selected. If that isn't the situation, you'll need to get the monitor to provide the available resolutions to your GPU. That should happen automatically for VGA, HDMI, DP connections.

$ get-edid

will get the information from the monitor in a machine format.

$ parse-edid

can read the machine format and should output the supported resolutions and other technical information that can be used to create modelines for the xorg.conf file.

So, in theory, running

$ sudo get-edid |parse-edid

should show everything. That's the theory. https://askubuntu.com/questions/8137...from-a-monitor


Here's a modeline from one of my systems:

        Modeline        "Mode 0" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync

The output seems to create a full xorg.conf "Monitor" section, which is really nice. I don't have nvidia working in any of my systems, so that's from an AMD GPU. One of my AMD GPU systems is using VESA, not the proprietary driver. Only the proprietary driver is outputting useful information.

[mark bower]

"lxrandr is neat and shows the missing desired resolution: 2560 x 1600" - geez what terrible wording indeed - just the opposite of what I intended!!!!!!!!!!

So, following is the edid output.
1)What do the numbers on a ModeLine mean?
2)Given the output, what is the next step aiming for the 2560x1400 display?

mark@senior:~$ sudo get-edid |parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 5
No EDID on bus 6
No EDID on bus 7
1 potential busses found: 4
256-byte EDID successfully retrieved from i2c bus 4
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
	Identifier "SAMSUNG"
	ModelName "SAMSUNG"
	VendorName "SAM"
	# Monitor Manufactured week 1 of 2016
	# EDID version 1.3
	# Digital Display
	DisplaySize 890 500
	Gamma 2.20
	Option "DPMS" "false"
	Horizsync 15-81
	VertRefresh 24-75
	# Maximum pixel clock is 300MHz
	#Not giving standard mode: 1152x864, 75Hz
	#Not giving standard mode: 1280x720, 60Hz
	#Not giving standard mode: 1280x800, 60Hz
	#Not giving standard mode: 1280x1024, 60Hz
	#Not giving standard mode: 1440x900, 60Hz
	#Not giving standard mode: 1600x900, 60Hz
	#Not giving standard mode: 1680x1050, 60Hz

	#Extension block found. Parsing...
#WARNING: I may have missed a mode (CEA mode 95)
#DOUBLE WARNING: It's your first mode, too, so this may actually be important.
#WARNING: I may have missed a mode (CEA mode 93)
#WARNING: I may have missed a mode (CEA mode 94)
#WARNING: I may have missed a mode (CEA mode 98)
#WARNING: I may have missed a mode (CEA mode 99)
#WARNING: I may have missed a mode (CEA mode 100)
	Modeline 	"Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
	Modeline 	"Mode 0" 297.00 3840 4016 4104 4400 2160 2168 2178 2250 +hsync +vsync 
	Modeline 	"Mode 1" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync 
	Modeline 	"Mode 3" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
	Modeline 	"Mode 4" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
	Modeline 	"Mode 5" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
	Modeline 	"Mode 6" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
	Modeline 	"Mode 7" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
	Modeline 	"Mode 8" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
	Modeline 	"Mode 9" 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
	Modeline 	"Mode 10" 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
	Modeline 	"Mode 11" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
	Modeline 	"Mode 12" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
	Modeline 	"Mode 13" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
	Modeline 	"Mode 14" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
	Modeline 	"Mode 15" 74.25 1920 2448 2492 2640 540 542 547 562 +hsync +vsync interlace
	Modeline 	"Mode 16" 85.50 1366 1436 1579 1792 768 771 774 798 +hsync +vsync 
	Option "PreferredMode" "Mode 2"
EndSection

[TheFu]

"lxrandr is neat and shows the missing desired resolution: 2560 x 1600" - geez what terrible wording indeed - just the opposite of what I intended!!!!!!!!!!

So, following is the edid output.
1)What do the numbers on a ModeLine mean?
2)Given the output, what is the next step aiming for the 2560x1400 display?

They are what the monitor says it can support. There are 16 modes available. It is odd that the resolution isn't used vs "Mode 1". Seems like a mistake in the TV firmware to me. The fact that the exact TV model isn't listed in the EDID is odd too. I've never seen that either. You can replace those comments with anything you like. I'd put the resolutions into there.

BTW, the errors say some modes were missed, so perhaps running the command a few times to see if other, desired modes show up would be a good idea.

If it were me, I'd take the Monitor section information, create a text file with everything from Section ---> EndSection, including both of those lines. Then I'd move that file to /etc/X11/xorg.conf.d/ and 'chown root:root' on it with 644 permissions. Then I'd reboot.

BTW, the monitor is NOT reporting support for the resolution you want, so asking for it means some sort of scaling is happening.

1920x2008 at 148.500hz updates seems to be the native resolution based on the output above.

When you look in the monitor manual, it should list all the resolutions and update frequencies. That would be important. In theory, monitors since around 2000 have protections to prevent over driving them, but just a few months ago, I recall reading where some monitors were destroyed by a GPU driving it beyond the capabilities. The EDID should say correctly the capabilities of the connected monitor. If it doesn't, I'd suspect a bad/weak cable.