(Solved) 2nd monitor is incorrectly recognized after a start up

Questions about hardware and drivers
Forum rules
Before you post please read how to get help
Post Reply
User avatar
David Chiang
Level 1
Level 1
Posts: 45
Joined: Sun Jul 01, 2007 4:42 am
Location: Morioka, Japan

(Solved) 2nd monitor is incorrectly recognized after a start up

Post by David Chiang »

The manufacturer (LG) is recognized correctly, but 52" are assigned instead of 32". How can I change this without constant re-setting, so that the selected resolution remains permanently assigned? I think that once the monitor is recognized correctly, the settings should remain stable afterwards.
Last edited by David Chiang on Tue Jul 27, 2021 8:10 am, edited 4 times in total.
LMDE 4 Debbie (64-bit), Linux Kernel 4.19, Cinnamon 5.0.5;
HTPC: ASUS TUF B450M-Pro Gaming, 3.6 GHz AMD Ryzen 7 3700X (8 cores), 2 × 4 TiB Seagate BarraCuda ES.3, 64 GiB HyperX Predator DDR4;
User avatar
Kadaitcha Man
Level 15
Level 15
Posts: 5679
Joined: Mon Aug 27, 2012 10:17 pm

Re: Second monitor is incorrectly recognized

Post by Kadaitcha Man »

David Chiang wrote:
Wed Jul 21, 2021 6:56 am
The manufacturer (LG) is recognized correctly, but 52" are assigned instead of 32". How can I change this without constant re-setting, so that the selected resolution remains permanently assigned? I think that once the monitor is recognized correctly, the settings should remain stable afterwards.
Please post the output of inxi -Fxz from a terminal and enclose it in code tags [code]output.here[/code]. You'll see the code tags icon </> when you reply.
[*] All kadaitcha men are liars
User avatar
David Chiang
Level 1
Level 1
Posts: 45
Joined: Sun Jul 01, 2007 4:42 am
Location: Morioka, Japan

Re: Second monitor is incorrectly recognized

Post by David Chiang »

The relevant section looks like this:

Code: Select all

Graphics:
  Device-1: AMD Ellesmere [Radeon Pro WX 7100] driver: amdgpu v: kernel 
  bus ID: 06:00.0 
  Display: x11 server: X.Org 1.20.4 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa resolution: 1280x800~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: AMD Radeon Pro WX 7100 Graphics (POLARIS10 DRM 3.27.0 
  4.19.0-17-amd64 LLVM 7.0.1) 
  v: 4.5 Mesa 18.3.6 direct render: Yes 
The second resolution is the wrong one!
LMDE 4 Debbie (64-bit), Linux Kernel 4.19, Cinnamon 5.0.5;
HTPC: ASUS TUF B450M-Pro Gaming, 3.6 GHz AMD Ryzen 7 3700X (8 cores), 2 × 4 TiB Seagate BarraCuda ES.3, 64 GiB HyperX Predator DDR4;
User avatar
Kadaitcha Man
Level 15
Level 15
Posts: 5679
Joined: Mon Aug 27, 2012 10:17 pm

Re: Second monitor is incorrectly recognized

Post by Kadaitcha Man »

David Chiang wrote:
Wed Jul 21, 2021 7:07 am
The relevant section looks like this:
I specifically asked for the output of inxi -Fxz, not what you consider the "relevant section". Given that you can't solve the problem, you are not in a position to determine what I might consider to be relevant.
[*] All kadaitcha men are liars
User avatar
David Chiang
Level 1
Level 1
Posts: 45
Joined: Sun Jul 01, 2007 4:42 am
Location: Morioka, Japan

Re: Second monitor is incorrectly recognized

Post by David Chiang »

It is extremely unlikely that you will need all of the information it contains. If you need any further specific information, please let me know what exactly. By the way, you are in no position to ask anything of me that you actually don't need! :roll:
LMDE 4 Debbie (64-bit), Linux Kernel 4.19, Cinnamon 5.0.5;
HTPC: ASUS TUF B450M-Pro Gaming, 3.6 GHz AMD Ryzen 7 3700X (8 cores), 2 × 4 TiB Seagate BarraCuda ES.3, 64 GiB HyperX Predator DDR4;
User avatar
Kadaitcha Man
Level 15
Level 15
Posts: 5679
Joined: Mon Aug 27, 2012 10:17 pm

Re: Second monitor is incorrectly recognized

Post by Kadaitcha Man »

David Chiang wrote:
Wed Jul 21, 2021 7:25 am
It is extremely unlikely that you will ...
It's even more unlikely you'll get any more help.
[*] All kadaitcha men are liars
User avatar
David Chiang
Level 1
Level 1
Posts: 45
Joined: Sun Jul 01, 2007 4:42 am
Location: Morioka, Japan

Re: Second monitor is incorrectly recognized

Post by David Chiang »

Kadaitcha Man wrote:
Wed Jul 21, 2021 7:28 am
It's even more unlikely you'll get any more help.
That wasn't to be expected from you anyway! :lol:
LMDE 4 Debbie (64-bit), Linux Kernel 4.19, Cinnamon 5.0.5;
HTPC: ASUS TUF B450M-Pro Gaming, 3.6 GHz AMD Ryzen 7 3700X (8 cores), 2 × 4 TiB Seagate BarraCuda ES.3, 64 GiB HyperX Predator DDR4;
User avatar
SMG
Level 16
Level 16
Posts: 6275
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Second monitor is incorrectly recognized

Post by SMG »

David Chiang wrote:
Wed Jul 21, 2021 7:25 am
It is extremely unlikely that you will need all of the information it contains. If you need any further specific information, please let me know what exactly. By the way, you are in no position to ask anything of me that you actually don't need! :roll:
If you would have read Section 5 of READ: How To Get Help! you would know we need more than the one section you provided. That information does not include any personally identifying information so you just prolong your ability to get help when you do not provide what was asked.

Some people run into issues with LMDE because it uses an older kernel. That is relevant to your situation because AMD graphics drivers come from the kernel. To know if you might benefit from running a newer kernel through backports, we would need to see your hardware info and how Mint views that hardware info. That is why the full output of inxi -Fxxxrz is requested.
David Chiang wrote:
Wed Jul 21, 2021 6:56 am
I think that once the monitor is recognized correctly, the settings should remain stable afterwards.
And you saved the settings in the Display app after they were recognized correctly? By the way, those settings are saved in a Cinnamon file, but you didn't supply the requested inxi info so we do not know what version of Cinnamon you are using.

Please supply the info requested.
A woman typing on a laptop with LM20.2 Cinnamon.
User avatar
Kadaitcha Man
Level 15
Level 15
Posts: 5679
Joined: Mon Aug 27, 2012 10:17 pm

Re: Second monitor is incorrectly recognized

Post by Kadaitcha Man »

SMG wrote:
Wed Jul 21, 2021 9:21 am
Please supply the info requested.
Don't count on it. I expect that the avoidance is deliberate. Not that I place any weight whatsoever on signatures, but it does lead me to suspect that we may not be dealing with either LMDE or Linux Mint at all, and that the poster is under the misapprehension that we are stupid.
[*] All kadaitcha men are liars
User avatar
David Chiang
Level 1
Level 1
Posts: 45
Joined: Sun Jul 01, 2007 4:42 am
Location: Morioka, Japan

Re: Second monitor is incorrectly recognized

Post by David Chiang »

SMG wrote:
Wed Jul 21, 2021 9:21 am
If you would have read Section 5 of READ: "How To Get Help", you would know we need more than the one section you provided. That information does not include any personally identifying information ...
That's not true, the list contains several pieces of information that are not in the least related to the problem, such as the host name etc.
SMG wrote:
Wed Jul 21, 2021 9:21 am
Some people run into issues with LMDE because it uses an older kernel. That is relevant to your situation because AMD graphics drivers come from the kernel. To know if you might benefit from running a newer kernel through backports, we would need to see your hardware info and how Mint views that hardware info. That is why the full output of inxi -Fxxxrz is requested.
I don't think you need all the sections of the list to do this, although you need more than one.
SMG wrote:
Wed Jul 21, 2021 9:21 am
And you saved the settings in the Display app after they were recognized correctly?
Of course, how could I forget? I don't use the monitors at the same time, only individually, that means I switch one off and the other one on. Only the settings of the correctly recognized monitor are retained, those of the other one are automatically reset to the recommended value and that's not usable for me. An annoying side effect is also that the icons on the desktop are repeatedly deranged and then put back into order. By the way, the correctly recognized monitor is much newer than the other one from LG, so I find it quite unusual that the older device is not clearly recognized.

Wherever the cause may lie, I don't think the kernel is causing the problem!
Last edited by David Chiang on Mon Jul 26, 2021 5:20 am, edited 1 time in total.
LMDE 4 Debbie (64-bit), Linux Kernel 4.19, Cinnamon 5.0.5;
HTPC: ASUS TUF B450M-Pro Gaming, 3.6 GHz AMD Ryzen 7 3700X (8 cores), 2 × 4 TiB Seagate BarraCuda ES.3, 64 GiB HyperX Predator DDR4;
User avatar
AndyMH
Level 17
Level 17
Posts: 7364
Joined: Fri Mar 04, 2016 5:23 pm
Location: Wiltshire

Re: Second monitor is incorrectly recognized

Post by AndyMH »

LG monitors can be troublesome, I've got one, what model and what is the native resolution?

With the monitor plugged in post the output from xrandr --verbose.

How is it connected, vga, DP, HDMI?
Homebrew i5-8400+GTX1080 Cinnamon 19.0, 4 x Thinkpad T430 Cinnamon 20.1, 2 x i7-3632 , i5-3320, i5-3210, Thinkpad T60 19.0 Mate
User avatar
SMG
Level 16
Level 16
Posts: 6275
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Second monitor is incorrectly recognized

Post by SMG »

David Chiang wrote:
Thu Jul 22, 2021 3:57 am
That's not true, the list contains several pieces of information that are not in the least related to the problem, such as the host name etc.
Host name does not show in the version of inxi I currently have, but when it did in past versions I just substituted my forum username. I've seen others put xxx for the host name.
David Chiang wrote:
Thu Jul 22, 2021 3:57 am
I don't use the monitors at the same time, only individually, that means I switch one off and the other one on.
There is a ~/.config/cinnamon-monitors.xml file which is supposed to retain saved information. Does it appear that file is being updated when you save in the Display app?

X Server re-polls the ports on the GPU periodically and if the monitor is turned off then it is removed from the server. When turned back on, the GPU sends what it detects. That is a factor of the GPU hardware and the graphics driver as well as the Mint code.

I am not able to tell from your description whether the identifier for the monitor is not correct and that may be why the wrong info is being used. There might be information in the Xorg log (/var/log/Xorg.0.log) which may give some clues as to how the monitor is being recognized. Unfortunately, not all monitors are correctly labeled by the manufacturer.
David Chiang wrote:
Thu Jul 22, 2021 3:57 am
Wherever the cause may lie, I don't think the kernel is causing the problem!
Your computer's graphics drivers are loaded from the kernel. That is what the v. kernel means. If the graphics driver is the issue, then, in effect, the kernel is "causing" the problem.

Device-1: AMD Ellesmere [Radeon Pro WX 7100] driver: amdgpu v: kernel

That amdgpu driver does interact with your GPU and the ports on it which transmit the information to and from the monitor. That is one reason we ask what type of connection to your monitor you are using. Sometimes there are issues with the driver, but they only affect one type of port on the GPU. The specs I found for your GPU indicate it only had DisplayPorts.

TUF B450M-PRO GAMING: BIOS & FIRMWARE lists the latest version as 3202. I mention that because I see some of listed items affecting port and GPU issue. There is also an update for Ryzen 3000 Series Processors.

Machine:
Type: Desktop Mobo: ASUSTeK model: TUF B450M-PRO GAMING v: Rev X.0x
serial: <filter> UEFI: American Megatrends v: 2006 date: 11/13/2019
A woman typing on a laptop with LM20.2 Cinnamon.
User avatar
David Chiang
Level 1
Level 1
Posts: 45
Joined: Sun Jul 01, 2007 4:42 am
Location: Morioka, Japan

Re: Second monitor is incorrectly recognized

Post by David Chiang »

AndyMH wrote:
Thu Jul 22, 2021 4:13 am
LG monitors can be troublesome, I've got one, what model and what is the native resolution?
The Model is LG 32LH4900 and its maximum resolution for HDMI is 1920×1080 (HSync: 67.5 kHz, VSync: 60.0 Hz).
AndyMH wrote:
Thu Jul 22, 2021 4:13 am
With the monitor plugged in post the output from xrandr --verbose.
Both monitors are permanently connected to the HTPC, they are only used alternatively, but never at the same time! The system can also distinguish between the main monitor and the secondary monitor depending on the respective setting. The sections for DP2 and DP3 are excluded here as they are not connected. It should also be mentioned that both devices are switched on at this point and the LG only shows the wallpaper, as it's not the "active" monitor at the moment. In addition, DP1 currently shows the last values I set that are normally to be used!

Code: Select all

Screen 0: minimum 320 x 200, current 2640 x 840, maximum 16384 x 16384
DisplayPort-0 connected primary 1280x800+0+0 (0x68) normal (normal left inverted right x axis y axis) 518mm x 324mm
	Identifier: 0x55
	Timestamp:  6459118
	Subpixel:   unknown
	Gamma:      1.0:1.0:1.0
	Brightness: 1.0
	Clones:    
	CRTC:       0
	CRTCs:      0 1 2 3 4 5
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	EDID: 
		00ffffffffffff0038a30f6900000000
		1b190104b5342078e2ef95a35435b526
		0f5054bfef8081c0814081808bc09500
		9040b300a940283c80a070b023403020
		360006442100001c000000fd0031551f
		7811000a202020202020000000fc0050
		41323432570a202020202020000000ff
		00353733303736323554570a20200175
		1001050000e43eb0a04080377030203a
		0044061200001a5320c0a030b0254030
		205a0003441100001a721fb0a040c01c
		303020370044031100001a023a801871
		382d40942c450006242100001e023a80
		d072382d40102c458006232100001e00
		00000000000000000000000000000000
		00000000000000000000000000000053
	GAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	DEGAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	GAMMA_LUT: 0 
		range: (0, 65535)
	CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
		0 1 
	DEGAMMA_LUT: 0 
		range: (0, 65535)
	TearFree: auto 
		supported: off, on, auto
	max bpc: 8 
		range: (8, 16)
	underscan vborder: 0 
		range: (0, 128)
	underscan hborder: 0 
		range: (0, 128)
	underscan: off 
		supported: off, on, auto
	scaling mode: None 
		supported: None, Full, Center, Full aspect
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 56 
		supported: 56
	non-desktop: 0 
		range: (0, 1)
  1920x1200 (0x5a) 154.000MHz -HSync +VSync +preferred
        h: width  1920 start 1968 end 2000 total 2080 skew    0 clock  74.04KHz
        v: height 1200 start 1203 end 1209 total 1235           clock  59.95Hz
  1200x1920 (0x5b) 161.000MHz +HSync -VSync
        h: width  1200 start 1248 end 1280 total 1360 skew    0 clock 118.38KHz
        v: height 1920 start 1923 end 1933 total 1975           clock  59.94Hz
  1920x1080 (0x5c) 148.500MHz +HSync +VSync
        h: width  1920 start 2068 end 2112 total 2200 skew    0 clock  67.50KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  60.00Hz
  1920x1080 (0x5d) 148.500MHz +HSync +VSync
        h: width  1920 start 2448 end 2492 total 2640 skew    0 clock  56.25KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  50.00Hz
  1600x1200 (0x5e) 162.000MHz +HSync +VSync
        h: width  1600 start 1664 end 1856 total 2160 skew    0 clock  75.00KHz
        v: height 1200 start 1201 end 1204 total 1250           clock  60.00Hz
  1680x1050 (0x5f) 146.250MHz -HSync +VSync
        h: width  1680 start 1784 end 1960 total 2240 skew    0 clock  65.29KHz
        v: height 1050 start 1053 end 1059 total 1089           clock  59.95Hz
  1400x1050 (0x60) 121.750MHz -HSync +VSync
        h: width  1400 start 1488 end 1632 total 1864 skew    0 clock  65.32KHz
        v: height 1050 start 1053 end 1057 total 1089           clock  59.98Hz
  1280x1024 (0x61) 135.000MHz +HSync +VSync
        h: width  1280 start 1296 end 1440 total 1688 skew    0 clock  79.98KHz
        v: height 1024 start 1025 end 1028 total 1066           clock  75.02Hz
  1280x1024 (0x62) 108.000MHz +HSync +VSync
        h: width  1280 start 1328 end 1440 total 1688 skew    0 clock  63.98KHz
        v: height 1024 start 1025 end 1028 total 1066           clock  60.02Hz
  1440x900 (0x63) 106.500MHz -HSync +VSync
        h: width  1440 start 1520 end 1672 total 1904 skew    0 clock  55.93KHz
        v: height  900 start  903 end  909 total  934           clock  59.89Hz
  1280x960 (0x64) 108.000MHz +HSync +VSync
        h: width  1280 start 1376 end 1488 total 1800 skew    0 clock  60.00KHz
        v: height  960 start  961 end  964 total 1000           clock  60.00Hz
  960x1200 (0x65) 82.750MHz +HSync -VSync
        h: width   960 start 1008 end 1040 total 1120 skew    0 clock  73.88KHz
        v: height 1200 start 1205 end 1215 total 1237           clock  59.73Hz
  1200x960 (0x66) 80.500MHz +HSync -VSync
        h: width  1200 start 1248 end 1280 total 1360 skew    0 clock  59.19KHz
        v: height  960 start  963 end  970 total  988           clock  59.91Hz
  1360x768 (0x67) 84.963MHz -HSync +VSync
        h: width  1366 start 1431 end 1567 total 1776 skew    0 clock  47.84KHz
        v: height  768 start  771 end  781 total  798           clock  59.95Hz
  1280x800 (0x68) 154.000MHz -HSync +VSync *current
        h: width  1280 start 1968 end 2000 total 2080 skew    0 clock  74.04KHz
        v: height  800 start 1203 end 1209 total 1235           clock  59.95Hz
  1152x864 (0x69) 108.000MHz +HSync +VSync
        h: width  1152 start 1216 end 1344 total 1600 skew    0 clock  67.50KHz
        v: height  864 start  865 end  868 total  900           clock  75.00Hz
  1280x720 (0x6a) 74.250MHz +HSync +VSync
        h: width  1280 start 1390 end 1430 total 1650 skew    0 clock  45.00KHz
        v: height  720 start  725 end  730 total  750           clock  60.00Hz
  1024x768 (0x6b) 78.750MHz +HSync +VSync
        h: width  1024 start 1040 end 1136 total 1312 skew    0 clock  60.02KHz
        v: height  768 start  769 end  772 total  800           clock  75.03Hz
  1024x768 (0x6c) 75.000MHz -HSync -VSync
        h: width  1024 start 1048 end 1184 total 1328 skew    0 clock  56.48KHz
        v: height  768 start  771 end  777 total  806           clock  70.07Hz
  1024x768 (0x6d) 65.000MHz -HSync -VSync
        h: width  1024 start 1048 end 1184 total 1344 skew    0 clock  48.36KHz
        v: height  768 start  771 end  777 total  806           clock  60.00Hz
  832x624 (0x6e) 57.284MHz -HSync -VSync
        h: width   832 start  864 end  928 total 1152 skew    0 clock  49.73KHz
        v: height  624 start  625 end  628 total  667           clock  74.55Hz
  800x600 (0x6f) 50.000MHz +HSync +VSync
        h: width   800 start  856 end  976 total 1040 skew    0 clock  48.08KHz
        v: height  600 start  637 end  643 total  666           clock  72.19Hz
  800x600 (0x70) 49.500MHz +HSync +VSync
        h: width   800 start  816 end  896 total 1056 skew    0 clock  46.88KHz
        v: height  600 start  601 end  604 total  625           clock  75.00Hz
  800x600 (0x71) 40.000MHz +HSync +VSync
        h: width   800 start  840 end  968 total 1056 skew    0 clock  37.88KHz
        v: height  600 start  601 end  605 total  628           clock  60.32Hz
  800x600 (0x72) 36.000MHz +HSync +VSync
        h: width   800 start  824 end  896 total 1024 skew    0 clock  35.16KHz
        v: height  600 start  601 end  603 total  625           clock  56.25Hz
  640x480 (0x73) 31.500MHz -HSync -VSync
        h: width   640 start  656 end  720 total  840 skew    0 clock  37.50KHz
        v: height  480 start  481 end  484 total  500           clock  75.00Hz
  640x480 (0x74) 31.500MHz -HSync -VSync
        h: width   640 start  664 end  704 total  832 skew    0 clock  37.86KHz
        v: height  480 start  489 end  492 total  520           clock  72.81Hz
  640x480 (0x75) 30.240MHz -HSync -VSync
        h: width   640 start  704 end  768 total  864 skew    0 clock  35.00KHz
        v: height  480 start  483 end  486 total  525           clock  66.67Hz
  640x480 (0x76) 25.175MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.47KHz
        v: height  480 start  490 end  492 total  525           clock  59.94Hz
  720x400 (0x77) 28.320MHz -HSync +VSync
        h: width   720 start  738 end  846 total  900 skew    0 clock  31.47KHz
        v: height  400 start  412 end  414 total  449           clock  70.08Hz
DisplayPort-1 connected 1360x768+1280+72 (0x81) normal (normal left inverted right x axis y axis) 1150mm x 650mm
	Identifier: 0x56
	Timestamp:  6459118
	Subpixel:   unknown
	Gamma:      1.0:1.0:1.0
	Brightness: 1.0
	Clones:    
	CRTC:       1
	CRTCs:      0 1 2 3 4 5
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	EDID: 
		00ffffffffffff001e6d010001010101
		02130103807341780acf74a3574cb023
		09484ca1080081806140454031400101
		010101010101023a801871382d40582c
		45007e8a4200001e011d007251d01e20
		6e2855007e8a4200001e000000fd003a
		3e1e5310000a202020202020000000fc
		004c472054560a202020202020200104
		020326f14e101f841305140302122021
		2215012615075009570767030c001000
		b82de3050301011d8018711c1620582c
		25007e8a4200009e011d008051d00c20
		408035007e8a4200001e023a80187138
		2d40582c45007e8a4200001e662150b0
		51001b30407036007e8a4200001e0000
		000000000000000000000000000000f9
	GAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	DEGAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	GAMMA_LUT: 0 
		range: (0, 65535)
	CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
		0 1 
	DEGAMMA_LUT: 0 
		range: (0, 65535)
	TearFree: auto 
		supported: off, on, auto
	max bpc: 8 
		range: (8, 16)
	underscan vborder: 0 
		range: (0, 128)
	underscan hborder: 0 
		range: (0, 128)
	underscan: off 
		supported: off, on, auto
	scaling mode: None 
		supported: None, Full, Center, Full aspect
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 59 
		supported: 59
	non-desktop: 0 
		range: (0, 1)
  1920x1080 (0x78) 148.500MHz +HSync +VSync +preferred
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.50KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  60.00Hz
  1920x1080 (0x5d) 148.500MHz +HSync +VSync
        h: width  1920 start 2448 end 2492 total 2640 skew    0 clock  56.25KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  50.00Hz
  1920x1080 (0x79) 148.352MHz +HSync +VSync
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.43KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  59.94Hz
  1920x1080 (0x7a) 74.250MHz +HSync +VSync
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.75KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  30.00Hz
  1920x1080 (0x7b) 74.250MHz +HSync +VSync
        h: width  1920 start 2448 end 2492 total 2640 skew    0 clock  28.12KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  25.00Hz
  1920x1080 (0x7c) 74.250MHz +HSync +VSync
        h: width  1920 start 2558 end 2602 total 2750 skew    0 clock  27.00KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  24.00Hz
  1920x1080 (0x7d) 74.176MHz +HSync +VSync
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.72KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  29.97Hz
  1920x1080 (0x7e) 74.176MHz +HSync +VSync
        h: width  1920 start 2558 end 2602 total 2750 skew    0 clock  26.97KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  23.98Hz
  1680x1050 (0x7f) 148.500MHz +HSync +VSync
        h: width  1680 start 2008 end 2052 total 2200 skew    0 clock  67.50KHz
        v: height 1050 start 1084 end 1089 total 1125           clock  60.00Hz
  1280x1024 (0x62) 108.000MHz +HSync +VSync
        h: width  1280 start 1328 end 1440 total 1688 skew    0 clock  63.98KHz
        v: height 1024 start 1025 end 1028 total 1066           clock  60.02Hz
  1440x900 (0x80) 148.500MHz +HSync +VSync
        h: width  1440 start 2008 end 2052 total 2200 skew    0 clock  67.50KHz
        v: height  900 start 1084 end 1089 total 1125           clock  60.00Hz
  1360x768 (0x81) 85.500MHz +HSync +VSync *current
        h: width  1360 start 1424 end 1536 total 1792 skew    0 clock  47.71KHz
        v: height  768 start  771 end  777 total  795           clock  60.02Hz
  1280x800 (0x82) 148.500MHz +HSync +VSync
        h: width  1280 start 2008 end 2052 total 2200 skew    0 clock  67.50KHz
        v: height  800 start 1084 end 1089 total 1125           clock  60.00Hz
  1280x720 (0x83) 74.250MHz +HSync +VSync
        h: width  1280 start 1344 end 1472 total 1664 skew    0 clock  44.62KHz
        v: height  720 start  723 end  728 total  732           clock  60.96Hz
  1280x720 (0x6a) 74.250MHz +HSync +VSync
        h: width  1280 start 1390 end 1430 total 1650 skew    0 clock  45.00KHz
        v: height  720 start  725 end  730 total  750           clock  60.00Hz
  1280x720 (0x84) 74.250MHz +HSync +VSync
        h: width  1280 start 1720 end 1760 total 1980 skew    0 clock  37.50KHz
        v: height  720 start  725 end  730 total  750           clock  50.00Hz
  1280x720 (0x85) 74.176MHz +HSync +VSync
        h: width  1280 start 1390 end 1430 total 1650 skew    0 clock  44.96KHz
        v: height  720 start  725 end  730 total  750           clock  59.94Hz
  1024x768 (0x6d) 65.000MHz -HSync -VSync
        h: width  1024 start 1048 end 1184 total 1344 skew    0 clock  48.36KHz
        v: height  768 start  771 end  777 total  806           clock  60.00Hz
  800x600 (0x71) 40.000MHz +HSync +VSync
        h: width   800 start  840 end  968 total 1056 skew    0 clock  37.88KHz
        v: height  600 start  601 end  605 total  628           clock  60.32Hz
  720x576 (0x86) 27.000MHz -HSync -VSync
        h: width   720 start  732 end  796 total  864 skew    0 clock  31.25KHz
        v: height  576 start  581 end  586 total  625           clock  50.00Hz
  720x480 (0x87) 27.027MHz -HSync -VSync
        h: width   720 start  736 end  798 total  858 skew    0 clock  31.50KHz
        v: height  480 start  489 end  495 total  525           clock  60.00Hz
  720x480 (0x88) 27.000MHz -HSync -VSync
        h: width   720 start  736 end  798 total  858 skew    0 clock  31.47KHz
        v: height  480 start  489 end  495 total  525           clock  59.94Hz
  640x480 (0x89) 25.200MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.50KHz
        v: height  480 start  490 end  492 total  525           clock  60.00Hz
  640x480 (0x76) 25.175MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.47KHz
        v: height  480 start  490 end  492 total  525           clock  59.94Hz
  720x400 (0x77) 28.320MHz -HSync +VSync
        h: width   720 start  738 end  846 total  900 skew    0 clock  31.47KHz
        v: height  400 start  412 end  414 total  449           clock  70.08Hz
AndyMH wrote:
Thu Jul 22, 2021 4:13 am
How is it connected, VGA, DP, HDMI?
The graphics card Radeon PRO WX 7100 has 4 DP connectors (DP0 - DP3).
The NEC MultiSync PA242W is directly connected from port DP0 to its DP-in connector and is always recognized without any problems,
the LG 32LH4900 is connected from port DP1 to a DP/HDMI adapter and from there to its HDMI-1 input, it doesn't have a DisplayPort input.
LMDE 4 Debbie (64-bit), Linux Kernel 4.19, Cinnamon 5.0.5;
HTPC: ASUS TUF B450M-Pro Gaming, 3.6 GHz AMD Ryzen 7 3700X (8 cores), 2 × 4 TiB Seagate BarraCuda ES.3, 64 GiB HyperX Predator DDR4;
User avatar
David Chiang
Level 1
Level 1
Posts: 45
Joined: Sun Jul 01, 2007 4:42 am
Location: Morioka, Japan

Re: Second monitor is incorrectly recognized

Post by David Chiang »

SMG wrote:
Thu Jul 22, 2021 6:45 pm
Host name does not show in the version of inxi I currently have, but when it did in past versions I just substituted my forum username. I've seen others put xxx for the host name.
I can only talk about my version and here is this information included which I had to cancel manually.
SMG wrote:
Thu Jul 22, 2021 6:45 pm
There is a ~/.config/cinnamon-monitors.xml file which is supposed to retain saved information. Does it appear that file is being updated when you save in the Display app?
Yes it's always updated, last time was yesterday, take a look:

Code: Select all

<monitors version="1">
  <configuration>
      <clone>no</clone>
      <base_scale>1</base_scale>
      <output name="DisplayPort-0">
      </output>
      <output name="DisplayPort-1">
          <vendor>GSM</vendor>
          <product>0x0001</product>
          <serial>0x01010101</serial>
          <width>1360</width>
          <height>768</height>
          <rate>60,015000</rate>
          <x>0</x>
          <y>0</y>
          <scale>1,000000</scale>
          <rotation>normal</rotation>
          <reflect_x>no</reflect_x>
          <reflect_y>no</reflect_y>
          <primary>yes</primary>
      </output>
      <output name="DisplayPort-2">
      </output>
      <output name="DisplayPort-3">
      </output>
  </configuration>
  <configuration>
      <clone>no</clone>
      <base_scale>1</base_scale>
      <output name="DisplayPort-0">
          <vendor>NEC</vendor>
          <product>0x690f</product>
          <serial>0x00000000</serial>
          <width>1280</width>
          <height>800</height>
          <rate>59,950000</rate>
          <x>0</x>
          <y>0</y>
          <scale>1,000000</scale>
          <rotation>normal</rotation>
          <reflect_x>no</reflect_x>
          <reflect_y>no</reflect_y>
          <primary>yes</primary>
      </output>
      <output name="DisplayPort-1">
          <vendor>GSM</vendor>
          <product>0x0001</product>
          <serial>0x01010101</serial>
          <width>1360</width>
          <height>768</height>
          <rate>60,015000</rate>
          <x>1280</x>
          <y>72</y>
          <scale>1,000000</scale>
          <rotation>normal</rotation>
          <reflect_x>no</reflect_x>
          <reflect_y>no</reflect_y>
          <primary>no</primary>
      </output>
      <output name="DisplayPort-2">
      </output>
      <output name="DisplayPort-3">
      </output>
  </configuration>
</monitors>
SMG wrote:
Thu Jul 22, 2021 6:45 pm
There might be information in the Xorg log (/var/log/Xorg.0.log) which may give some clues as to how the monitor is being recognized. Unfortunately, not all monitors are correctly labeled by the manufacturer.
I have already thought about this, since the LG is a comparatively quite old device, it can not be ruled out that it does not identify itself completely. But since we don't really know that at the moment, it's too early for this diagnosis. :wink:
Here is an interesting excerpt from the log file, it even shows the serial number of the LG monitor (cancelled):

Code: Select all

[    21.673] (II) AMDGPU(0): EDID for output DisplayPort-1
[    21.673] (II) AMDGPU(0): Manufacturer: GSM  Model: 1  Serial#: xxxxxxxxxx
[    21.673] (II) AMDGPU(0): Year: 2009  Week: 2
[    21.673] (II) AMDGPU(0): EDID Version: 1.3
[    21.673] (II) AMDGPU(0): Digital Display Input
[    21.673] (II) AMDGPU(0): Max Image Size [cm]: horiz.: 115  vert.: 65
[    21.673] (II) AMDGPU(0): Gamma: 2.20
[    21.673] (II) AMDGPU(0): No DPMS capabilities specified
[    21.673] (II) AMDGPU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 
[    21.673] (II) AMDGPU(0): First detailed timing is preferred mode
[    21.673] (II) AMDGPU(0): redX: 0.640 redY: 0.340   greenX: 0.300 greenY: 0.690
[    21.673] (II) AMDGPU(0): blueX: 0.138 blueY: 0.038   whiteX: 0.282 whiteY: 0.297
[    21.673] (II) AMDGPU(0): Supported established timings:
[    21.673] (II) AMDGPU(0): 720x400@70Hz
[    21.673] (II) AMDGPU(0): 640x480@60Hz
[    21.673] (II) AMDGPU(0): 800x600@60Hz
[    21.673] (II) AMDGPU(0): 1024x768@60Hz
[    21.673] (II) AMDGPU(0): Manufacturer's mask: 0
[    21.673] (II) AMDGPU(0): Supported standard timings:
[    21.673] (II) AMDGPU(0): #0: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
[    21.673] (II) AMDGPU(0): #1: hsize: 1024  vsize 768  refresh: 60  vid: 16481
[    21.673] (II) AMDGPU(0): #2: hsize: 800  vsize 600  refresh: 60  vid: 16453
[    21.673] (II) AMDGPU(0): #3: hsize: 640  vsize 480  refresh: 60  vid: 16433
[    21.673] (II) AMDGPU(0): Supported detailed timing:
[    21.673] (II) AMDGPU(0): clock: 148.5 MHz   Image Size:  1150 x 650 mm
[    21.673] (II) AMDGPU(0): h_active: 1920  h_sync: 2008  h_sync_end 2052 h_blank_end 2200 h_border: 0
[    21.673] (II) AMDGPU(0): v_active: 1080  v_sync: 1084  v_sync_end 1089 v_blanking: 1125 v_border: 0
[    21.673] (II) AMDGPU(0): Supported detailed timing:
[    21.673] (II) AMDGPU(0): clock: 74.2 MHz   Image Size:  1150 x 650 mm
[    21.673] (II) AMDGPU(0): h_active: 1280  h_sync: 1390  h_sync_end 1430 h_blank_end 1650 h_border: 0
[    21.673] (II) AMDGPU(0): v_active: 720  v_sync: 725  v_sync_end 730 v_blanking: 750 v_border: 0
[    21.673] (II) AMDGPU(0): Ranges: V min: 58 V max: 62 Hz, H min: 30 H max: 83 kHz, PixClock max 165 MHz
[    21.673] (II) AMDGPU(0): Monitor name: LG TV
[    21.673] (II) AMDGPU(0): Supported detailed timing:
[    21.673] (II) AMDGPU(0): clock: 74.2 MHz   Image Size:  1150 x 650 mm
[    21.673] (II) AMDGPU(0): h_active: 1920  h_sync: 2008  h_sync_end 2052 h_blank_end 2200 h_border: 0
[    21.673] (II) AMDGPU(0): v_active: 540  v_sync: 542  v_sync_end 547 v_blanking: 562 v_border: 0
[    21.673] (II) AMDGPU(0): Supported detailed timing:
[    21.673] (II) AMDGPU(0): clock: 74.2 MHz   Image Size:  1150 x 650 mm
[    21.673] (II) AMDGPU(0): h_active: 1280  h_sync: 1344  h_sync_end 1472 h_blank_end 1664 h_border: 0
[    21.673] (II) AMDGPU(0): v_active: 720  v_sync: 723  v_sync_end 728 v_blanking: 732 v_border: 0
[    21.673] (II) AMDGPU(0): Supported detailed timing:
[    21.673] (II) AMDGPU(0): clock: 148.5 MHz   Image Size:  1150 x 650 mm
[    21.673] (II) AMDGPU(0): h_active: 1920  h_sync: 2008  h_sync_end 2052 h_blank_end 2200 h_border: 0
[    21.673] (II) AMDGPU(0): v_active: 1080  v_sync: 1084  v_sync_end 1089 v_blanking: 1125 v_border: 0
[    21.673] (II) AMDGPU(0): Supported detailed timing:
[    21.673] (II) AMDGPU(0): clock: 85.5 MHz   Image Size:  1150 x 650 mm
[    21.673] (II) AMDGPU(0): h_active: 1360  h_sync: 1424  h_sync_end 1536 h_blank_end 1792 h_border: 0
[    21.673] (II) AMDGPU(0): v_active: 768  v_sync: 771  v_sync_end 777 v_blanking: 795 v_border: 0
[    21.673] (II) AMDGPU(0): Number of EDID sections to follow: 1
[    21.673] (II) AMDGPU(0): EDID (in hex):
[    21.673] (II) AMDGPU(0): 	00ffffffffffff001e6d010001010101
[    21.673] (II) AMDGPU(0): 	02130103807341780acf74a3574cb023
[    21.673] (II) AMDGPU(0): 	09484ca1080081806140454031400101
[    21.673] (II) AMDGPU(0): 	010101010101023a801871382d40582c
[    21.673] (II) AMDGPU(0): 	45007e8a4200001e011d007251d01e20
[    21.673] (II) AMDGPU(0): 	6e2855007e8a4200001e000000fd003a
[    21.673] (II) AMDGPU(0): 	3e1e5310000a202020202020000000fc
[    21.673] (II) AMDGPU(0): 	004c472054560a202020202020200104
[    21.673] (II) AMDGPU(0): 	020326f14e101f841305140302122021
[    21.673] (II) AMDGPU(0): 	2215012615075009570767030c001000
[    21.673] (II) AMDGPU(0): 	b82de3050301011d8018711c1620582c
[    21.673] (II) AMDGPU(0): 	25007e8a4200009e011d008051d00c20
[    21.673] (II) AMDGPU(0): 	408035007e8a4200001e023a80187138
[    21.673] (II) AMDGPU(0): 	2d40582c45007e8a4200001e662150b0
[    21.673] (II) AMDGPU(0): 	51001b30407036007e8a4200001e0000
[    21.673] (II) AMDGPU(0): 	000000000000000000000000000000f9
[    21.673] (--) AMDGPU(0): HDMI max TMDS frequency 225000KHz
[    21.673] (II) AMDGPU(0): Printing probed modes for output DisplayPort-1
[    21.673] (II) AMDGPU(0): Modeline "1920x1080"x60.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[    21.673] (II) AMDGPU(0): Modeline "1920x1080"x50.0  148.50  1920 2448 2492 2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1920x1080"x59.9  148.35  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1920x1080"x30.0   74.25  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (33.8 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1920x1080"x25.0   74.25  1920 2448 2492 2640  1080 1084 1089 1125 +hsync +vsync (28.1 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1920x1080"x24.0   74.25  1920 2558 2602 2750  1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1920x1080"x30.0   74.18  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (33.7 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1920x1080"x24.0   74.18  1920 2558 2602 2750  1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1680x1050"x60.0  148.50  1680 2008 2052 2200  1050 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1440x900"x60.0  148.50  1440 2008 2052 2200  900 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1360x768"x60.0   85.50  1360 1424 1536 1792  768 771 777 795 +hsync +vsync (47.7 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1280x800"x60.0  148.50  1280 2008 2052 2200  800 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1280x720"x61.0   74.25  1280 1344 1472 1664  720 723 728 732 +hsync +vsync (44.6 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1280x720"x60.0   74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1280x720"x50.0   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1280x720"x59.9   74.18  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "720x576"x50.0   27.00  720 732 796 864  576 581 586 625 -hsync -vsync (31.2 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "720x480"x60.0   27.03  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "720x480"x59.9   27.00  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "640x480"x60.0   25.20  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    21.673] (II) AMDGPU(0): Modeline "720x400"x70.1   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
SMG wrote:
Thu Jul 22, 2021 6:45 pm
TUF B450M-PRO GAMING: BIOS & FIRMWARE lists the latest version as 3202. I mention that because I see some of listed items affecting port and GPU issue. There is also an update for Ryzen 3000 Series Processors.
I know that, but as long as there is no decisive reason, I will run my hardware as it is. I have already spent enough time in advance with almost endless research, just to make sure that all components are compatible with each other without restrictions, that should be enough for the time being. As far as I could tell, there have also been consumers who couldn't use a whole bunch of processors without an immediate BIOS upgrade. Fortunately, I am not affected by this! In addition, there is also a Linux driver from AMD for the graphics card, but despite its comprehensive functions it hasn't yet been installed, as it isn't yet needed. :lol:

One more word to the BIOS version: 2006 is from November 2019, so the version is new enough to recognise 99% of all devices from the last 20 years and as you can probably see, both of my monitors falls into this period. An update wouldn't change anything, because the problem exists with an older device and not with the very latest hardware as so often. Not to forget, my LMDE 4 system is still completely up-to-date (including the kernel), I hope that's enough for the moment!
LMDE 4 Debbie (64-bit), Linux Kernel 4.19, Cinnamon 5.0.5;
HTPC: ASUS TUF B450M-Pro Gaming, 3.6 GHz AMD Ryzen 7 3700X (8 cores), 2 × 4 TiB Seagate BarraCuda ES.3, 64 GiB HyperX Predator DDR4;
User avatar
SMG
Level 16
Level 16
Posts: 6275
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Second monitor is incorrectly recognized

Post by SMG »

Most people have complaints about monitor resolution because the native resolution is not showing. My understanding of what you have presented so far is that is not the case here. You have a personal preference you want for each monitor and Mint is only remembering to use that personal preference for the NEC MultiSync attached to DP-0. You are not using the native resolution (designated by the + preferred) for either monitor. You are using what is listed as * current.

Code: Select all

DisplayPort-0 connected primary 1280x800+0+0 (0x68) normal (normal left inverted right x axis y axis) 518mm x 324mm
  1920x1200 (0x5a) 154.000MHz -HSync +VSync +preferred
        h: width  1920 start 1968 end 2000 total 2080 skew    0 clock  74.04KHz
        v: height 1200 start 1203 end 1209 total 1235           clock  59.95Hz
  1280x800 (0x68) 154.000MHz -HSync +VSync *current
        h: width  1280 start 1968 end 2000 total 2080 skew    0 clock  74.04KHz
        v: height  800 start 1203 end 1209 total 1235           clock  59.95Hz
DisplayPort-1 connected 1360x768+1280+72 (0x81) normal (normal left inverted right x axis y axis) 1150mm x 650mm
  1920x1080 (0x78) 148.500MHz +HSync +VSync +preferred
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.50KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  60.00Hz
  1360x768 (0x81) 85.500MHz +HSync +VSync *current
        h: width  1360 start 1424 end 1536 total 1792 skew    0 clock  47.71KHz
        v: height  768 start  771 end  777 total  795           clock  60.02Hz
David Chiang wrote:
Fri Jul 23, 2021 4:53 am
The system can also distinguish between the main monitor and the secondary monitor depending on the respective setting.
For clarity, what "respective setting"? Does this just mean the correct resolution is showing when the NEC is in use?
David Chiang wrote:
Fri Jul 23, 2021 6:14 am
Yes it's always updated, last time was yesterday, take a look:
I'm going to make an observation strictly based on what I see in the code (because I do not have much experience with this particular file).

You indicated, "Both monitors are permanently connected to the HTPC, they are only used alternatively, but never at the same time!" I would think that would mean there would be two configurations and each one would only have one monitor in them. That is not what I see. There is one configuration with just DP1 and another configuration with DP0 and DP1 and that second configuration has a different offset for x,y for DP1 as if both monitors are being used. To me, that would seem something other than what you wanted is what was saved?
David Chiang wrote:
Fri Jul 23, 2021 6:14 am
Here is an interesting excerpt from the log file, it even shows the serial number of the LG monitor (cancelled):
Which I take to mean that is the correct serial number, especially since the driver is picking up what appears to be the correct options for resolutions. (Sometimes different values show up in Xorg that do not show up in xrandr which is why I make that comment.)

It also indicates:

Code: Select all

[    21.673] (II) AMDGPU(0): First detailed timing is preferred mode
...
[    21.673] (II) AMDGPU(0): Supported detailed timing:
[    21.673] (II) AMDGPU(0): clock: 148.5 MHz   Image Size:  1150 x 650 mm
[    21.673] (II) AMDGPU(0): h_active: 1920  h_sync: 2008  h_sync_end 2052 h_blank_end 2200 h_border: 0
[    21.673] (II) AMDGPU(0): v_active: 1080  v_sync: 1084  v_sync_end 1089 v_blanking: 1125 v_border: 0
so it appears to be reading the monitor correctly.

And it does pick up your preferred resolution as an option.

Code: Select all

[    21.673] (II) AMDGPU(0): Monitor name: LG TV
...
[    21.673] (II) AMDGPU(0): h_active: 1360  h_sync: 1424  h_sync_end 1536 h_blank_end 1792 h_border: 0
[    21.673] (II) AMDGPU(0): v_active: 768  v_sync: 771  v_sync_end 777 v_blanking: 795 v_border: 0
David Chiang wrote:
Fri Jul 23, 2021 6:14 am
In addition, there is also a Linux driver from AMD for the graphics card, but despite its comprehensive functions it hasn't yet been installed, as it isn't yet needed.
While there is a closed-source component to that driver archive, the bulk of the files are the same files are the same open-source files one can get from the kernel (depending upon which version of the kernel is used).

I was not able to find the specific driver which would work with your LMDE kernel, but the Release Notes for a newer version indicate a known issue "Display resolution resets to default for displays connected through multi display hub.". That is not the issue you are seeing, but it is an issue related to the GPU/driver regardless of the monitor. Such issues do exist which is why I mentioned that type of possibility.
David Chiang wrote:
Fri Jul 23, 2021 6:14 am
One more word to the BIOS version: 2006 is from November 2019, so the version is new enough to recognise 99% of all devices from the last 20 years and as you can probably see, both of my monitors falls into this period. An update wouldn't change anything, because the problem exists with an older device and not with the very latest hardware as so often.
Your monitors are not connected to the mobo. I looked at the listed changes which indicate they would affect your GPU and your CPU which is why I let you know the updates are available. I only mention BIOS updates when I think they have applicability to the issue in the thread.

It appears to me that issues with the Display app are part of linuxmint / cinnamon-control-center because I found some issues posted related to the app.

In this older issue Display Module: Displays not detected? #241 I see a comment from the developer, "The new monitors.xml file (cinnamon-monitors.xml actually now) will only be created when you 'apply' changes. If you deleted your existing one, it's just autodetecting everything."

If you have two monitors and only one is ever used at a time, is the system seeing one as primary and the other as secondary or do they both show up as primary when they are in use? I wonder if that might be why both monitors are in the second configuration in the cinnamon-monitors.xml you posted.
A woman typing on a laptop with LM20.2 Cinnamon.
User avatar
David Chiang
Level 1
Level 1
Posts: 45
Joined: Sun Jul 01, 2007 4:42 am
Location: Morioka, Japan

Re: Second monitor is incorrectly recognized

Post by David Chiang »

SMG wrote:
Fri Jul 23, 2021 4:17 pm
For clarity, what "respective setting"? Does this just mean the correct resolution is showing when the NEC is in use?
The user has the possibility to determine which of his monitors is considered the main monitor and which is the secondary monitor. This setting is then also decisive for the further behaviour in the setup.
SMG wrote:
Fri Jul 23, 2021 4:17 pm
You indicated, "Both monitors are permanently connected to the HTPC, they are only used alternatively, but never at the same time!" I would think that would mean there would be two configurations and each one would only have one monitor in them.
You have observed this correctly so far, this is also where part of the problem has arisen. :D
SMG wrote:
Fri Jul 23, 2021 4:17 pm
There is one configuration with just DP1 and another configuration with DP0 and DP1 and that second configuration has a different offset for x,y for DP1 as if both monitors are being used. To me, that would seem something other than what you wanted is what was saved?
Correct, but why this could happen I will tell you below.
SMG wrote:
Fri Jul 23, 2021 4:17 pm
While there is a closed-source component to that driver archive, the bulk of the files are the same files are the same open-source files one can get from the kernel (depending upon which version of the kernel is used).
No, they are never the same, too many changes in the further development take place at AMD. Don't be misled here!
SMG wrote:
Fri Jul 23, 2021 4:17 pm
Your monitors are not connected to the mobo. I looked at the listed changes which indicate they would affect your GPU and your CPU which is why I let you know the updates are available. I only mention BIOS updates when I think they have applicability to the issue in the thread.
It no longer plays a major role where and how a component or device is connected to the hardware, the detection takes place via all bus systems, since most devices already communicate with each other. Moreover, with the best of intentions, I cannot imagine that someone without a reason will perform 5 BIOS upgrades in a period of 20 months just because they happen to be available. That would be an upgrade on average every 4 months and I don't know anyone who would update their BIOS just because of a vague suspicion. Forget it, you're totally wrong here!
SMG wrote:
Fri Jul 23, 2021 4:17 pm
It appears to me that issues with the Display app are part of linuxmint / cinnamon-control-center because I found some issues posted related to the app.
This software is certainly underdeveloped and poorly documented, but definitely not the cause.
SMG wrote:
Fri Jul 23, 2021 4:17 pm
In this older issue Display Module: Displays not detected? #241 I see a comment from the developer, "The new monitors.xml file (cinnamon-monitors.xml actually now) will only be created when you 'apply' changes. If you deleted your existing one, it's just autodetecting everything."
Ok, here you are on the right track, this is probably part of two causes that led to the problem.
SMG wrote:
Fri Jul 23, 2021 4:17 pm
If you have two monitors and only one is ever used at a time, is the system seeing one as primary and the other as secondary or do they both show up as primary when they are in use? I wonder if that might be why both monitors are in the second configuration in the cinnamon-monitors.xml you posted.
Just read what's next and you'll be amazed! :lol:
LMDE 4 Debbie (64-bit), Linux Kernel 4.19, Cinnamon 5.0.5;
HTPC: ASUS TUF B450M-Pro Gaming, 3.6 GHz AMD Ryzen 7 3700X (8 cores), 2 × 4 TiB Seagate BarraCuda ES.3, 64 GiB HyperX Predator DDR4;
User avatar
David Chiang
Level 1
Level 1
Posts: 45
Joined: Sun Jul 01, 2007 4:42 am
Location: Morioka, Japan

Re: 2nd monitor is incorrectly recognized when I start up with it

Post by David Chiang »

First of all, I would like to state what was demonstrably not the cause of the problem:
the BIOS, the graphics card and its generic driver software, the CPU, the GPU, the kernel, the operating system as a whole, the distribution and its update status, the hardware equipment of the HTPC, the topological arrangement of the respective devices, the type of connections and their underlying standards and a lot of things more.

And now let's get to the hard facts:
  1. For whatever reason, the LG monitor suppresses its type designation (32LH4900) in the EDID code, which means that the resolution recommended by the system is always the highest possible, because the monitor is not recognized well and therefore the wrong size (52" instead of 32") is assumed by the system. This fact was clear from the beginning and at the same time the cause for everything else.
  2. By considering only using one of the two monitors at a time, I let myself be carried away to configure them separately, which turned out to be an error that led to an unstable state in the configuration. This means that switching back and forth between the two monitors meant that the settings for the secondary monitor (LG) were lost each time and were reset by the system. Only after assigning the recognized NEC monitor as the main monitor and subsequently setting both resolutions from there, the situation has changed radically. It follows that it is absolutely necessary to first define the main monitor in order to then set both resolutions from there. Shouldn't this be possible from both monitors? Yes, with a high probability, but only if both monitors are recognized perfectly! At the same time, however, this is also an indicator that the configuration software is faulty, as it shouldn't actually allow any incorrect operation in this circumstances.
The main clues to solve my problem came from these two files: cinnamon-monitors.xml and Xorg.0.log, the latter clearly showing the core of the problem. By the way, thank you SMG for this hint, only then was it possible to circle the real causes. Everything else was unfortunately more or less useless, but this is just normal, as remote diagnosis is always difficult. :wink:
LMDE 4 Debbie (64-bit), Linux Kernel 4.19, Cinnamon 5.0.5;
HTPC: ASUS TUF B450M-Pro Gaming, 3.6 GHz AMD Ryzen 7 3700X (8 cores), 2 × 4 TiB Seagate BarraCuda ES.3, 64 GiB HyperX Predator DDR4;
User avatar
AndyMH
Level 17
Level 17
Posts: 7364
Joined: Fri Mar 04, 2016 5:23 pm
Location: Wiltshire

Re: (Solved) 2nd monitor is incorrectly recognized when I start up with it

Post by AndyMH »

It sounds like you have fixed the problem. Can you state exactly what you did to solve it. This is for the benefit of others who may have the same problem.
You can also go back to your first post and edit it so you can added [solved] into the title.
Homebrew i5-8400+GTX1080 Cinnamon 19.0, 4 x Thinkpad T430 Cinnamon 20.1, 2 x i7-3632 , i5-3320, i5-3210, Thinkpad T60 19.0 Mate
User avatar
David Chiang
Level 1
Level 1
Posts: 45
Joined: Sun Jul 01, 2007 4:42 am
Location: Morioka, Japan

Re: (Solved) 2nd monitor is incorrectly recognized when I start up with it

Post by David Chiang »

To explain it as simply as possible, as long as the system believes that there is only one setup, the configuration file cinnamon-monitors.xml is constantly updated by the system with only a single configuration, which leads to the fact that the entered monitor, no matter which of the two, is constantly re-entered. This wouldn't be a problem under normal circumstances if both are properly recognized by the system. In my particular case, however, it is unfortunately so that only one is fully recognized, but the other one is not, which led to the fact that the settings for the resolution of the latter were lost each time and reset by the system.

Only when both devices were switched on at the same time and set up from the main monitor as they are needed was the problem solved. As a result, the entry in the cinnamon-monitors.xml file now consists of two configurations, one with only one monitor and a second with now two monitors. The settings made are now retained, as the system believes there are apparently two setups and therefore now switches back and forth between these two without changing anything. That was the solution! 8)
LMDE 4 Debbie (64-bit), Linux Kernel 4.19, Cinnamon 5.0.5;
HTPC: ASUS TUF B450M-Pro Gaming, 3.6 GHz AMD Ryzen 7 3700X (8 cores), 2 × 4 TiB Seagate BarraCuda ES.3, 64 GiB HyperX Predator DDR4;
Post Reply