Re: Dual Monitor on tumbleweed
On Wed, 2021-12-08 at 18:52 -0300, Christian Schmitz wrote:
On Wednesday 08 December 2021 15:31:58 you wrote:
On Wed, Dec 8, 2021, 13:03 Christian Schmitz
wrote:
Helo everyone: Thanks for all. The working option was:
xrandr --output VGA-0 --auto --primary --output DVI-0 --mode 1024x768 --right-of VGA-0
I add --mode because i dont know why the system try to use a out of specifications resolution on small ( and secondary monitor)
Also --primary because the TDE use the small monitor as primary
The result is that the system start mirrored on boot, when X start for 0 seconds still mirrored and after that switch to the alright screen
.
These days the screen resolution info comes from edit monitor data, as supposed to more/less elaborate guess in the past.
Your vga screen has no way of communicating that data over vga, even if it would support it over hdmi/DP. The same is most likely true for your DVI connected screen. VGA still have DDC detection of monitor model, resolution and H/V data.
That is why X picks some sort of safe options. I think in same way
You probably would have correct resolution, refresh rates, etc. set correctly with modern monitors connected over DP/USB-C/hdmi
-T Thanks you for your answer. I am on Argentine, so the hardware is some old, but working hehehe.
--
By no means I wanted to suggest that people should use the latest and greatest - just wanted to reason about the possibility that the screen maybe unable to share its info. If you install read-edid and then run: sudo get-edid to find if you get any screen info on any I2C buses. If you do see info - decode it and see what the monitors are reporting. It works like this:
sudo get-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 4 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 2 potential busses found: 8 10 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. 128-byte EDID successfully retrieved from i2c bus 8 ??????????????-Z??x??TL??&PT??7????p8>@:*5%?? ??AUO ??B133HAN05.A Looks like i2c was successful. Have a good day.
sudo get-edid -b 8 | parse-edid 8 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 8 as per your request. 128-byte EDID successfully retrieved from i2c bus 8 Looks like i2c was successful. Have a good day. Checksum Correct
Section "Monitor" Identifier "" ModelName "" VendorName "AUO" # Monitor Manufactured week 0 of 2018 # EDID version 1.4 # Digital Display DisplaySize 290 170 Gamma 2.20 Option "DPMS" "false" Modeline "Mode 0" 142.60 1920 1978 2020 2080 1080 1083 1088 1142 -hsync -vsync EndSection
sudo get-edid -b 10 | parse-edid 1 0 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 10 as per your request. 256-byte EDID successfully retrieved from i2c bus 10 Looks like i2c was successful. Have a good day. Checksum Correct
Section "Monitor" Identifier "DELL U3011" ModelName "DELL U3011" VendorName "DEL" # Monitor Manufactured week 41 of 2012 # EDID version 1.3 # Digital Display DisplaySize 640 400 Gamma 2.20 Option "DPMS" "true" Horizsync 29-94 VertRefresh 49-86 # Maximum pixel clock is 180MHz #Not giving standard mode: 1152x864, 75Hz #Not giving standard mode: 1280x800, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1920x1200, 60Hz #Not giving standard mode: 1600x1200, 60Hz #Extension block found. Parsing... Modeline "Mode 17" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 0" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync Modeline "Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 2" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace Modeline "Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline "Mode 4" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline "Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline "Mode 6" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace Modeline "Mode 7" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace Modeline "Mode 8" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline "Mode 9" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace Modeline "Mode 10" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline "Mode 11" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline "Mode 12" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace Modeline "Mode 13" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline "Mode 14" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace Modeline "Mode 15" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 16" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 18" 74.25 1920 2008 2052 2200 540 542 547 562 +hsync +vsync interlace Modeline "Mode 19" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync Modeline "Mode 20" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync Option "PreferredMode" "Mode 17" EndSection
TomasK composed on 2021-12-08 21:28 (UTC-0500):
By no means I wanted to suggest that people should use the latest and greatest - just wanted to reason about the possibility that the screen maybe unable to share its info.
If you install read-edid and then run: sudo get-edid to find if you get any screen info on any I2C buses. If you do see info - decode it and see what the monitors are reporting.
It works like this:
sudo get-edid ... sudo get-edid -b 8 | parse-edid 8 ... Section "Monitor" ... # inxi -Sy System: Host: ab250 Kernel: 5.14.14-3-default x86_64 bits: 64 Desktop: Trinity R14.0.11 Distro: openSUSE Tumbleweed 20211207 # whoami root # get-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Looks like no busses have an EDID. Sorry! Attempting to use the classical VBE interface Illegal instruction (core dumped)
Have you ever found an material difference between your method, and output from: hwinfo --gfxcard ??? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
typo fixed: TomasK composed on 2021-12-08 21:28 (UTC-0500):
By no means I wanted to suggest that people should use the latest and greatest - just wanted to reason about the possibility that the screen maybe unable to share its info.
If you install read-edid and then run: sudo get-edid to find if you get any screen info on any I2C buses. If you do see info - decode it and see what the monitors are reporting.
It works like this:
sudo get-edid ... sudo get-edid -b 8 | parse-edid 8 ... Section "Monitor" ... # inxi -Sy System: Host: ab250 Kernel: 5.14.14-3-default x86_64 bits: 64 Desktop: Trinity R14.0.11 Distro: openSUSE Tumbleweed 20211207 # whoami root # get-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Looks like no busses have an EDID. Sorry! Attempting to use the classical VBE interface Illegal instruction (core dumped)
Have you ever found an material difference between your method, and output from: hwinfo --monitor ??? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
participants (2)
-
Felix Miata
-
TomasK