Lost 4K resolution detection with 455.23.04

Graphics / Linux Linux
1

Hi,
I updated my Archlinux system from 450.66 to 455.23.04. Monitor is a Samsung TV Q7FN 55" from 2018.

With 450.66 xrandr returns:

$ xrandr -q
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 1210mm x 680mm
   3840x2160     30.00 +  59.94    50.00    29.97    25.00    23.98    23.98  
   4096x2160     59.94    50.00    29.97    25.00    24.00    23.98  
   1920x1080    119.88*  100.00    60.00    59.94    50.00    29.97    25.00    23.98  
   1680x1050     59.95  
   1600x900      60.00  
   1440x900      59.89  
   1366x768      59.79  
   1280x1024     75.02    60.02  
   1280x800      59.81  
   1280x720      60.00    59.94    50.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)

With 455.23.04:

$ xrandr -q
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 1872mm x 1053mm
   1920x1080     60.00*+  59.94    50.00    29.97    25.00    23.98  
   1680x1050     59.95  
   1600x900      60.00  
   1440x900      59.89  
   1366x768      59.79  
   1280x1024     75.02    60.02  
   1280x800      59.81  
   1280x720      60.00    59.94    50.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)

Has anyone observed this too?

2

I have sent the nvidia bug log to the linux-bugs email address, but please find it attached here also.
nvidia-bug-report.log.gz (876.9 KB)

3

I have now produced bug reports in logverbose 6, for both versions of the driver:
nvidia-bug-report-455.log.gz (1.1 MB)
nvidia-bug-report-450.log.gz (1.1 MB)

4

Same resolution loss happens in ubuntu 20.04. It ends up in 640x320.

However to get back (in case you need to do some work you can do

Today Sept 28th, 2020 I did an update via the ubunu update tool. Once done the graphics no longer works properly the resolution I get is 640x320.

The solution that works is to go to the NVIDIA Web page and download the 450 driver. Than you need to install that driver with sudo sh FILNAME_OF_THE_RUN_FILE.run

After the next reboot, your screen will be good again. I checked on also the 32 bit option and recreated the X settings.

It would be nice to work with ubuntu to make sure this does not happen.

wget https://us.download.nvidia.com/XFree86/Linux-x86_64/450.66/NVIDIA-Linux-x86_64-450.66.run
sudo sh NVIDIA-Linux-x86_64-450.66.run
sudo restart -h now
5

Well indeed reverting to 450.66 fixes the issue, but that is not a solution as far as 455.23.04 is concerned. That said, it is unadvised to use the run file on a distribution like Ubuntu or Archlinux. Prefer downgrading the packages instead.

6

I had a look at my bug report files and found out something from the Xorg.0.log files:

  • For 450.66:
    [ 5.036] (–) NVIDIA(GPU-0): SAMSUNG (DFP-1): connected
    [ 5.036] (–) NVIDIA(GPU-0): SAMSUNG (DFP-1): Internal TMDS
    [ 5.036] (–) NVIDIA(GPU-0): SAMSUNG (DFP-1): 600.0 MHz maximum pixel clock
    …
    [ 5.101] (==) NVIDIA(0): No modes were requested; the default mode “nvidia-auto-select”
    [ 5.101] (==) NVIDIA(0): will be used as the requested mode.
    [ 5.102] (==) NVIDIA(0):
    [ 5.103] (II) NVIDIA(0): Validated MetaModes:
    [ 5.103] (II) NVIDIA(0): “DFP-1:nvidia-auto-select”
    [ 5.103] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 2160

  • For 455.23.04:
    [ 5.308] (–) NVIDIA(GPU-0): SAMSUNG (DFP-1): connected
    [ 5.308] (–) NVIDIA(GPU-0): SAMSUNG (DFP-1): Internal TMDS
    [ 5.308] (–) NVIDIA(GPU-0): SAMSUNG (DFP-1): 165.0 MHz maximum pixel clock
    …
    [ 5.358] (==) NVIDIA(0): No modes were requested; the default mode “nvidia-auto-select”
    [ 5.358] (==) NVIDIA(0): will be used as the requested mode.
    [ 5.358] (==) NVIDIA(0):
    [ 5.360] (II) NVIDIA(0): Validated MetaModes:
    [ 5.360] (II) NVIDIA(0): “DFP-1:nvidia-auto-select”
    [ 5.360] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080

There is a discrepancy between the maximum pixel clock values (165 vs 600 MHz), and am wondering if this in the end affects the virtual screen size as determined by nvidia-auto-select.

7

Also, xrandr --verbose (line 8285 and 8378 of the bug reports for 455 and 450, repectively) shows that both versions read the same EDID information, however the computed modes are different, maxing out at 1920 for 455, and with different maximum clock frequencies.