Missing Resolution after Monitor Power Cycle

[anubis]

Hello,

First post here. Running Linux 5.4.0-89-generic with a Samsung 1920x1200 60hz Monitor.

Code: Select all

 username:~$ cvt 1920 1200
# 1920x1200 59.88 Hz (CVT 2.30MA) hsync: 74.56 kHz; pclk: 193.25 MHz
Modeline "1920x1200_60.00"  193.25  1920 2056 2256 2592  1200 1203 1209 1245 -hsync +vsync

When I boot my computer everything is fine.
When I reboot my computer everything is fine.
When I power off my monitor I lose the resolution setting for 1920x1200 and it is not listed in the Display options.

I can only get the display back after reboot.
I've found a few articles that involve manually configuring a permanent display setting, but I've been unable to get this to work. viewtopic.php?t=274540

Here are the results from xrandr before monitor power turns off:

Code: Select all

Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200     59.95*+
   1920x1080     60.00    59.94  
   1680x1050     59.95  
   1600x900      60.00  
   1280x1024     60.02  
   1440x900      59.89  
   1280x800      59.81  
   1280x720      60.00    59.94  
   1024x768      60.00  
   800x600       60.32    56.25  
   640x480       60.00    59.94  

and here are the results after powering the monitor back on:

Code: Select all

Screen 0: minimum 320 x 200, current 1600 x 900, maximum 8192 x 8192
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 connected primary 1600x900+0+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1600x900      60.00* 
   1280x1024     60.02  
   1440x900      59.89  
   1280x800      59.81  
   1280x720      60.00    59.94  
   1024x768      60.00  
   800x600       60.32    56.25  
   640x480       60.00    59.94  

Any advice?

[SMG]

First post here. Running Linux 5.4.0-89-generic with a Samsung 1920x1200 60hz Monitor.

Welcome to the forum, anubis.

You have not given us the information Section 5 of READ: How To Get Help! so we do not know what desktop version of Mint you are running, but I believe all of them give an option to Apply or Save the current monitor resolution. Have you tried doing that? I do not see where you mentioned that.

Do you have your monitor connected directly to your computer (and not through a KVM or other switch)?

[anubis]

Hello,

I'm running Linux Mint 20.2 Cinnamon version 5.0.6.
My monitor is connected directly to the Display port on the back of my computer.
I have tried 'Apply' in the display settings.
- To be clear the problem only occurs when I power cycle my monitor, not when I boot the OS.

Is there a way to permanently set this resolution option in settings without having the OS detect it for availability?

[SMG]

I'm running Linux Mint 20.2 Cinnamon version 5.0.6.

Please open Update Manager and run the updates. That is not the latest version of Cinnamon (and -89 is not the latest kernel available either).

I have tried 'Apply' in the display settings.
Is there a way to permanently set this resolution option in settings without having the OS detect it for availability?

That is what the Apply button is supposed to do. However, when clicking that button it also saves the monitor information. What I think may be happening is the monitor information changes when you power cycle it and thus Mint is no longer recognizing the monitor to know to use the saved setting. I think that may be why the xrandr changes you tried did not work.

There is some hard-coded EDID information that could be passed using a kernel parameter, but 1920x1200 is not one of the options. 1920x1080 is the closest available option.

[anubis]

Hello,

I apologize for the delay on this. I believe you are correct, it seems when I power cycle the monitor, the monitor changes the resolution from 1920x1200 to the following:

1. 1600x900 on the first power cycle.
2. 1024x768 on the second power cycle.
3. 1920x1200 on the third power cycle.

It appears to be cycling through resolutions for no reason. Power cycling the monitor with the computer on enough times eventually leads me back to my desired resolution of 1920x1200.

What makes this more strange is I have 2 other monitors of the same make and model that don't have this issue with other PCs.
I have switched this computer over to those monitors for testing and I experience the same issue.

This leads me to believe that both of the following are true.
1. The monitors are changing the resolution when power cycled as a means of formatting and quick booting the display when powered on.
2. Because of this behavior the OS can only properly detect the actual resolution of the screen a fraction of the time.

Questions:
Is it possible the OS is detecting the monitor faster than it has time to retrieve the optimal resolution setting of 1920x1200?
Is there a way to delay resolution detection by half a second to grant the monitor more time to reach it's maximum resolution before attempting screen detection?

[SMG]

What makes this more strange is I have 2 other monitors of the same make and model that don't have this issue with other PCs.
I have switched this computer over to those monitors for testing and I experience the same issue.

So the issue seems to be a combination of this particular computer (and or the operating system) and those monitor models. What model Samsung is it?

Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz
Click </> from the mini toolbar above the textbox where you type your reply and then place your cursor between the code tags and paste the results of the command between the code tags [code]Results[/code]. This will let us know how Mint sees your hardware.

[anubis]

So the issue seems to be a combination of this particular computer (and or the operating system) and those monitor models. What model Samsung is it?

Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz

Hi SMG,

Yes, that is what it seems.

I am using the following Samsung model: LS24E65UDWG/ZA
Here is my system info.

Code: Select all

System:
  Kernel: 5.4.0-104-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 5.0.7 wm: muffin 5.0.2 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: Dell product: Precision T1600 v: 01 serial: <filter> 
  Chassis: type: 6 serial: <filter> 
  Mobo: Dell model: 06NWYK v: A00 serial: <filter> UEFI: Dell v: A21 
  date: 07/05/2018 
CPU:
  Topology: Quad Core model: Intel Xeon E31245 bits: 64 type: MT MCP 
  arch: Sandy Bridge rev: 7 L2 cache: 8192 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 52680 
  Speed: 1596 MHz min/max: 1600/3700 MHz Core speeds (MHz): 1: 1596 2: 1596 
  3: 1595 4: 1596 5: 1596 6: 1596 7: 1596 8: 1597 
Graphics:
  Device-1: Intel Xeon E3-1200 Processor Family Integrated Graphics 
  vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:010a 
  Display: x11 server: X.Org 1.20.13 driver: modesetting 
  unloaded: fbdev,vesa resolution: 1920x1200~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1) 
  v: 3.3 Mesa 21.2.6 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
  vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  chip ID: 8086:1c20 
  Sound Server: ALSA v: k5.4.0-104-generic 
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Dell driver: e1000e 
  v: 3.2.6-k port: 3080 bus ID: 00:19.0 chip ID: 8086:1502 
  IF: eno1 state: down mac: <filter> 
  Device-2: ASUSTek type: USB driver: rtl88x2bu bus ID: 2-1.8:4 
  chip ID: 0b05:184c serial: <filter> 
  IF: wlxf02f7465f6f4 state: up mac: <filter> 
  IF-ID-1: docker0 state: down mac: <filter> 
Drives:
  Local Storage: total: 931.52 GiB used: 341.58 GiB (36.7%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 4B6Q scheme: GPT 
  ID-2: /dev/sdb vendor: Western Digital model: WDBNCE5000PNC 
  size: 465.76 GiB speed: 6.0 Gb/s serial: <filter> rev: 40RL scheme: GPT 
Partition:
  ID-1: / size: 456.96 GiB used: 341.57 GiB (74.7%) fs: ext4 dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 48.0 C mobo: 21.0 C 
  Fan Speeds (RPM): cpu: 1748 mobo: 1516 
Info:
  Processes: 309 Uptime: 13d 18h 31m Memory: 23.15 GiB 
  used: 15.63 GiB (67.5%) Init: systemd v: 245 runlevel: 5 Compilers: 
  gcc: 9.4.0 alt: 9 Shell: bash v: 5.0.17 running in: gnome-terminal 
  inxi: 3.0.38 

[SMG]

It appears to be cycling through resolutions for no reason. Power cycling the monitor with the computer on enough times eventually leads me back to my desired resolution of 1920x1200.

The operating system handles new monitors being connected to the computer as a hot-plug event. So each time you power cycle the monitor, it is completely disconnected from the computer, and then it is re-connected as a new connection. Whenever there is a new connection, the EDID data from the monitor is passed to the computer and the computer uses that information to determine what resolutions are available.

I give you that background because I do not understand how your questions (below) relate to what is happening. Each disconnect and reconnect (which is essentially what you are doing by power-cycling the monitor) is a fresh connection. The only way to delay the computer from getting the information from the monitor is to not have the cable connected. There is no "timer" which handles the connection that you can adjust to delay one part of the connection.

Questions:
Is it possible the OS is detecting the monitor faster than it has time to retrieve the optimal resolution setting of 1920x1200?
Is there a way to delay resolution detection by half a second to grant the monitor more time to reach it's maximum resolution before attempting screen detection?

I have searched all through the monitor manual and the Dell computer manual. I have no guesses at all what might be happening unless there is something squirrelly happening at the physical DP port on the computer?

What makes this more strange is I have 2 other monitors of the same make and model that don't have this issue with other PCs.
I have switched this computer over to those monitors for testing and I experience the same issue.

Were you using the same monitor cable when you did these tests or were you using different cables?