[opensuse] LG Flatron question
I'm currently using a LG Flatron LG1953T in 1280x1024@60Hz mode. It has a few other mods such as 1280x960 (a 4x3) as well. I've just picked up a wide-screen Flatron, a W1492TQ at a yard sale for C$15. While I can find Windows drivers for this my google-foo has not turned up specification and timing. OK, I could plug it in and hope for the nest, it is physically wider, so I wonder. Do I get more pixels or is this a compromise like some of the wide laptops I see, 1440 x 900 ? What would be nice is 2560X1600. Am I dreaming? What would be the modeline? https://www.cnet.com/products/lg-l1953s-lcd-monitor-19/ -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Thu, 04 Apr 2019, Anton Aylward wrote:
I'm currently using a LG Flatron LG1953T in 1280x1024@60Hz mode. It has a few other mods such as 1280x960 (a 4x3) as well.
I've just picked up a wide-screen Flatron, a W1492TQ at a yard sale for C$15. While I can find Windows drivers for this my google-foo has not turned up specification and timing.
First hit https://duckduckgo.com/html/?q=LG%20W1492TQ is: https://www.lg.com/ca_en/desktop-monitors/lg-W1942TQ-BF-lcd-monitor
OK, I could plug it in and hope for the nest, it is physically wider, so I wonder. Do I get more pixels or is this a compromise like some of the wide laptops I see, 1440 x 900 ?
Jep. Xorg should do the right thing automatically. -dnh -- To kick or not to kick... -- Somewhere on IRC, inspired by Shakespeare -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-04-04 5:47 p.m., David Haller wrote:
First hit https://duckduckgo.com/html/?q=LG%20W1492TQ is:
Hmmm. Maybe duckduckgo is getting better than google? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward composed on 2019-04-04 17:13 (UTC-0400):
I'm currently using a LG Flatron LG1953T in 1280x1024@60Hz mode. It has a few other mods such as 1280x960 (a 4x3) as well.
I've just picked up a wide-screen Flatron, a W1492TQ at a yard sale for C$15. While I can find Windows drivers for this my google-foo has not turned up specification and timing.
Xorg.0.log reports "Monitor Name", which is the model number, VertRefresh and HorizSync on the "Ranges:" line following, following that with raw EDID and modelines for probed modes. 1440x900 probably requires no hardware-specific display driver on Windows since Vista at least.
OK, I could plug it in and hope for the nest, it is physically wider, so I wonder. Do I get more pixels or is this a compromise like some of the wide laptops I see, 1440 x 900 ?
IMO this mode was made originally because 19" 1680x1050, 19" 1600x900 and 19" 1980x1080 displays were too much display density for many of the people in the market for 19" (aka low cost) widescreen. Other than with laptops, I've never seen 1440x900 as preferred mode in any size other than 19".
What would be nice is 2560X1600.
Those are seriously expensive. 2560x1440 can be had for half as much or less.
Am I dreaming? What would be the modeline?
Xorg has been smart enough to generate modelines on its own (and read them from EDID) for well over a decade. Last time I needed one manually configured was with XFree86 much too long ago to remember.
If your Optiplex 755 is using its onboard Intel GPU and, that's what you connected the 1492 to, it should automatically use 1440x900, if the 1492's EDID reports it, and if you don't have some manual config somewhere to override it. If your kernel cmdline has a video= option and your Xorg is using the Intel DDX driver rather than the default Xorg DDX driver (modesetting), then Xorg will use that cmdline video= mode, assuming the display actually supports it. If the modesetting DDX is in use, this won't happen, same as with AMD and NVidia GPUs. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-04-04 7:51 p.m., Felix Miata wrote:
What would be nice is 2560X1600. Those are seriously expensive. 2560x1440 can be had for half as much or less.
I'd settle for that. And a 24" monitor would also be nice. But like I say, this was a gift at the yard sale for C$15.
Am I dreaming? What would be the modeline?
Xorg has been smart enough to generate modelines on its own (and read them from EDID) for well over a decade. Last time I needed one manually configured was with XFree86 much too long ago to remember.
And you have a choice presented by lxrandr? IIR many LG models have problems with EDID being incompatible and not supply the information in a way the Xorg works with. I ran into this when I first got the old 1953 and I've seen it discussed many time more in my googling for a solution for the 1942. So CVT did a good job then and I'm hoping it can again now.
https://www.cnet.com/products/lg-l1953s-lcd-monitor-19/ If your Optiplex 755 is using its onboard Intel GPU and, that's what you connected the 1492 to, it should automatically use 1440x900,
OK, got the cvt: # cvt 1440 900 # 1440x900 59.89 Hz (CVT 1.30MA) hsync: 55.93 kHz; pclk: 106.50 MHz Modeline "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync
if the 1492's EDID reports it,
Ha ha ha. "is there a tool to determine that?" No the Xorg.0.log doens't tell me what EDID reports, only what 50-monitor.conf has.
and if you don't have some manual config somewhere to override it. If your kernel cmdline has a video= option and your Xorg is using the Intel DDX driver rather than the default Xorg DDX driver (modesetting), then Xorg will use that cmdline video= mode, assuming the display actually supports it. If the modesetting DDX is in use, this won't happen, same as with AMD and NVidia GPUs.
Just to. But what else can I set the 1942 to? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Thu, 04 Apr 2019, Anton Aylward wrote:
On 2019-04-04 7:51 p.m., Felix Miata wrote:
if the 1492's EDID reports it,
Ha ha ha. "is there a tool to determine that?"
https://software.opensuse.org/package/read-edid HTH, -dnh -- "...you might as well skip the Xmas celebration completely, and instead sit in front of your linux computer playing with the all-new-and-improved linux kernel version." (By Linus Torvalds) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-04-05 3:50 p.m., David Haller wrote:
Hello,
On Thu, 04 Apr 2019, Anton Aylward wrote:
On 2019-04-04 7:51 p.m., Felix Miata wrote:
if the 1492's EDID reports it,
Ha ha ha. "is there a tool to determine that?"
Thank you. This is what I got =================== # get-edid | parse-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 Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful VBE version 300 VBE string at 0x11100 "Intel(r)Q33/Q35/G33 Graphics Chip Accelerated VGA BIOS" VBE/DDC service about to be called Report DDC capabilities Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 Function supported Call successful Monitor and video card combination does not support DDC1 transfers Monitor and video card combination supports DDC2 transfers 0 seconds per 128 byte EDID block transfer Screen is not blanked during DDC transfer Reading next EDID block VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call failed =================== I don't know what to do about that. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Fri, 05 Apr 2019, Anton Aylward wrote:
This is what I got =================== # get-edid | parse-edid [..] VBE string at 0x11100 "Intel(r)Q33/Q35/G33 Graphics Chip Accelerated VGA BIOS" [..] I don't know what to do about that.
Looks like your monitor does not supply (valid) EDID/DDC data that get-edid/parse-edid support :( See also https://en.wikipedia.org/wiki/Display_Data_Channel https://en.wikipedia.org/wiki/Extended_Display_Identification_Data Well, have a look at the xrandr output, the Xorg.*.log etc... -dnh -- I didn't know it was impossible when I did it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David Haller composed on 2019-04-06 07:07 (UTC+0200):
Anton Aylward wrote:
This is what I got =================== # get-edid | parse-edid [..] VBE string at 0x11100 "Intel(r)Q33/Q35/G33 Graphics Chip Accelerated VGA BIOS" [..] I don't know what to do about that.
Looks like your monitor does not supply (valid) EDID/DDC data that get-edid/parse-edid support :(
See also https://en.wikipedia.org/wiki/Display_Data_Channel https://en.wikipedia.org/wiki/Extended_Display_Identification_Data I've never figured out how to make the read-edid package useful either, though sometimes I can make a monitor-edid package work:
# inxi -GxxSM System: Host: vizio Kernel: 5.0.5-1-default x86_64 bits: 64 compiler: gcc v: 8.3.1 Desktop: KDE Plasma 5.15.3 tk: Qt 5.12.2 wm: kwin_x11 dm: KDM Distro: openSUSE Tumbleweed 20190403 Machine: Type: Desktop System: Dell product: OptiPlex 760 v: N/A serial: FVVV4J1 Chassis: type: 15 serial: FVVV4J1 Mobo: Dell model: 0M863N v: A00 serial: ..CN7360494L006I. BIOS: Dell v: A16 date: 08/06/2013 Graphics: Device-1: Intel 4 Series Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2e12 Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa alternate: intel compositor: kwin_x11 resolution: 2560x1440~60Hz OpenGL: renderer: Mesa DRI Intel Q45/Q43 v: 2.1 Mesa 19.0.1 direct render: Yes # rpm -qi monitor-edid Name : monitor-edid Version : 3.0 Release : 14.1 Architecture: x86_64 Install Date: Fri Feb 6 16:46:04 2015 Group : Hardware/Other Size : 100399 License : GPL Signature : DSA/SHA1, Sun Dec 22 16:32:49 2013, Key ID 2f8734b2f5b125a2 Source RPM : monitor-edid-3.0-14.1.src.rpm Build Date : Sun Dec 22 16:32:36 2013 Build Host : build16 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/home:Strahlex URL : http://wiki.mandriva.com/en/Tools/monitor-edid Summary : Tool for probing and parsing monitor EDID Description : Monitor-edid is a tool for probing and parsing Extended display identification data (EDID) from monitors. For more information about EDID, see http://en.wikipedia.org/wiki/EDID Distribution: home:Strahlex / openSUSE_13.1 # monitor-edid -v probing EDID using VBE (port 0) probing EDID using VBE (port 1) probing EDID using VBE (port 2) parsing EDID from /sys/class/drm/card0-DP-1/edid Name: K272HUL EISA ID: ACR0524 EDID version: 1.4 EDID extension blocks: 1 Screen size: 59.8 cm x 33.6 cm (27.01 inches, aspect ratio 16/9 = 1.78) Gamma: 2.2 Digital signal Standard resolution: 640x480 @ 60 Hz (established timing) Standard resolution: 640x480 @ 67 Hz (established timing) Standard resolution: 640x480 @ 72 Hz (established timing) Standard resolution: 640x480 @ 75 Hz (established timing) Standard resolution: 720x400 @ 70 Hz (established timing) Standard resolution: 800x600 @ 56 Hz (established timing) Standard resolution: 800x600 @ 60 Hz (established timing) Standard resolution: 800x600 @ 72 Hz (established timing) Standard resolution: 800x600 @ 75 Hz (established timing) Standard resolution: 832x624 @ 75 Hz (established timing) Standard resolution: 1024x768 @ 60 Hz (established timing) Standard resolution: 1024x768 @ 70 Hz (established timing) Standard resolution: 1024x768 @ 75 Hz (established timing) Standard resolution: 1280x1024 @ 75 Hz (established timing) Standard resolution: 1152x864 @ 75 Hz, ratio 4/3 (!) Standard resolution: 1280x960 @ 60 Hz, ratio 4/3 (!) Standard resolution: 1280x1024 @ 60 Hz, ratio 5/4 (!) Standard resolution: 1280x720 @ 60 Hz, ratio 16/9 Standard resolution: 1280x800 @ 60 Hz, ratio 16/10 (!) Standard resolution: 1440x900 @ 60 Hz, ratio 16/10 (!) Standard resolution: 1680x1050 @ 60 Hz, ratio 16/10 (!) Standard resolution: 1920x1080 @ 60 Hz, ratio 16/9 Max video bandwidth: 300 MHz HorizSync 113-113 VertRefresh 40-75 # Monitor preferred modeline (60.0 Hz vsync, 88.8 kHz hsync, ratio 16/9, 108 dpi) ModeLine "2560x1440" 241.5 2560 2608 2640 2720 1440 1443 1448 1481 -hsync +vsync # Monitor supported CEA modeline (60.0 Hz vsync, 67.5 kHz hsync, ratio 16/9, 81 dpi) ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync # Monitor supported CEA modeline (59.9 Hz vsync, 31.5 kHz hsync, ratio 4/3, 27x36 dpi) (bad ratio) ModeLine "640x480" 25.175 640 656 752 800 480 490 492 525 -hsync -vsync # Monitor supported CEA modeline (59.9 Hz vsync, 31.5 kHz hsync, ratio 3/2, 30x36 dpi) (bad ratio) ModeLine "720x480" 27 720 736 798 858 480 489 495 525 -hsync -vsync # Monitor supported CEA modeline (59.9 Hz vsync, 31.5 kHz hsync, ratio 3/2, 30x36 dpi) (bad ratio) ModeLine "720x480" 27 720 736 798 858 480 489 495 525 -hsync -vsync # Monitor supported CEA modeline (60.0 Hz vsync, 45.0 kHz hsync, ratio 16/9, 54 dpi) ModeLine "1280x720" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync # Monitor supported CEA modeline (60.0 Hz vsync, 33.8 kHz hsync, interlaced, ratio 16/9, 81 dpi) ModeLine "1920x1080" 74.25 1920 2008 2052 2200 1080 1084 1094 1125 +hsync +vsync Interlace # Monitor supported CEA modeline (50.0 Hz vsync, 31.2 kHz hsync, ratio 5/4, 30x43 dpi) (bad ratio) ModeLine "720x576" 27 720 732 796 864 576 581 586 625 -hsync -vsync # Monitor supported CEA modeline (50.0 Hz vsync, 31.2 kHz hsync, ratio 5/4, 30x43 dpi) (bad ratio) ModeLine "720x576" 27 720 732 796 864 576 581 586 625 -hsync -vsync # Monitor supported CEA modeline (50.0 Hz vsync, 37.5 kHz hsync, ratio 16/9, 54 dpi) ModeLine "1280x720" 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync # Monitor supported CEA modeline (50.0 Hz vsync, 28.1 kHz hsync, interlaced, ratio 16/9, 81 dpi) ModeLine "1920x1080" 74.25 1920 2448 2492 2640 1080 1084 1094 1125 +hsync +vsync Interlace # Monitor supported CEA modeline (50.0 Hz vsync, 56.2 kHz hsync, ratio 16/9, 81 dpi) ModeLine "1920x1080" 148.5 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync # Monitor supported modeline (74.9 Hz vsync, 111.8 kHz hsync, ratio 16/9, 108 dpi) ModeLine "2560x1440" 298.47 2560 2583 2615 2670 1440 1478 1486 1492 -hsync +vsync # Monitor supported modeline (74.9 Hz vsync, 84.6 kHz hsync, ratio 16/9, 81 dpi) ModeLine "1920x1080" 220.75 1920 2056 2264 2608 1080 1083 1088 1130 -hsync +vsync # Monitor supported modeline (60.0 Hz vsync, 67.5 kHz hsync, ratio 16/9, 81 dpi) ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync # Monitor supported modeline (60.0 Hz vsync, 45.0 kHz hsync, ratio 16/9, 54 dpi) ModeLine "1280x720" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync # Monitor supported modeline (59.9 Hz vsync, 31.5 kHz hsync, ratio 3/2, 30x36 dpi) (bad ratio) ModeLine "720x480" 27 720 736 798 858 480 489 495 525 -hsync +vsync # hwinfo --display 14: PCI 02.1: 0380 Display controller [Created at pci.386] Unique ID: ruGf.gwnt_y2xiAE SysFS ID: /devices/pci0000:00/0000:00:02.1 SysFS BusID: 0000:00:02.1 Hardware Class: graphics card Model: "Intel 4 Series Chipset Integrated Graphics Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2e13 "4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x027f Revision: 0x03 Memory Range: 0xf7b00000-0xf7bfffff (rw,non-prefetchable) Module Alias: "pci:v00008086d00002E13sv00001028sd0000027Fbc03sc80i00" Config Status: cfg=new, avail=yes, need=no, active=unknown 28: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.9UQF57mGRZ8 SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Intel 4 Series Chipset Integrated Graphics Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2e12 "4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x027f Revision: 0x03 Driver: "i915" Driver Modules: "i915" Memory Range: 0xf7c00000-0xf7ffffff (rw,non-prefetchable) Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable) I/O Ports: 0xecb0-0xecb7 (rw) Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) IRQ: 16 (5503 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v00008086d00002E12sv00001028sd0000027Fbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown Primary display adapter: #28 # rpm -qi read-edid Name : read-edid Version : 3.0.2 Release : 2.2 Architecture: x86_64 Install Date: Sat Apr 6 01:24:21 2019 Group : System/X11/Utilities Size : 53446 License : BSD-3-Clause Signature : RSA/SHA256, Wed Jan 30 00:41:30 2019, Key ID b88b2fd43dbdc284 Source RPM : read-edid-3.0.2-2.2.src.rpm Build Date : Wed Jan 30 00:41:14 2019 Build Host : lamb16 Relocations : (not relocatable) Packager : https://bugs.opensuse.org Vendor : openSUSE URL : http://polypux.org/projects/read-edid/ Summary : Tool for reading EDID information Description : A pair of tools for reading the Extended Display Identification Data (EDID) from a monitor. Assuming the video card supports the standard read commands, the utilities should work with most monitors made since 1996. 256-byte EDIDs are not supported, though. - get-edid, which gets the raw edid information from the monitor. - parse-edid, which turns the raw binary information into an xorg-compatible monitor section. Distribution: openSUSE Tumbleweed # grep -A60 EDID /var/log/Xorg.0.log [ 214.832] (II) modeset(0): EDID for output VGA-1 [ 214.833] (II) modeset(0): EDID for output HDMI-1 [ 214.852] (II) modeset(0): EDID for output DP-1 [ 214.852] (II) modeset(0): Manufacturer: ACR Model: 524 Serial#: 2215657459 [ 214.852] (II) modeset(0): Year: 2018 Week: 41 [ 214.852] (II) modeset(0): EDID Version: 1.4 [ 214.852] (II) modeset(0): Digital Display Input [ 214.852] (II) modeset(0): 10 bits per channel [ 214.852] (II) modeset(0): Digital interface is DisplayPort [ 214.852] (II) modeset(0): Max Image Size [cm]: horiz.: 60 vert.: 34 [ 214.852] (II) modeset(0): Gamma: 2.20 [ 214.852] (II) modeset(0): DPMS capabilities: Off [ 214.852] (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 YCrCb 4:2:2 [ 214.852] (II) modeset(0): Default color space is primary color space [ 214.852] (II) modeset(0): First detailed timing is preferred mode [ 214.852] (II) modeset(0): Preferred mode is native pixel format and refresh rate [ 214.852] (II) modeset(0): Display is continuous-frequency [ 214.852] (II) modeset(0): redX: 0.650 redY: 0.339 greenX: 0.313 greenY: 0.626 [ 214.852] (II) modeset(0): blueX: 0.150 blueY: 0.052 whiteX: 0.313 whiteY: 0.329 [ 214.852] (II) modeset(0): Supported established timings: [ 214.852] (II) modeset(0): 720x400@70Hz [ 214.852] (II) modeset(0): 640x480@60Hz [ 214.852] (II) modeset(0): 640x480@67Hz [ 214.852] (II) modeset(0): 640x480@72Hz [ 214.852] (II) modeset(0): 640x480@75Hz [ 214.852] (II) modeset(0): 800x600@56Hz [ 214.852] (II) modeset(0): 800x600@60Hz [ 214.852] (II) modeset(0): 800x600@72Hz [ 214.852] (II) modeset(0): 800x600@75Hz [ 214.852] (II) modeset(0): 832x624@75Hz [ 214.852] (II) modeset(0): 1024x768@60Hz [ 214.852] (II) modeset(0): 1024x768@70Hz [ 214.852] (II) modeset(0): 1024x768@75Hz [ 214.852] (II) modeset(0): 1280x1024@75Hz [ 214.852] (II) modeset(0): 1152x864@75Hz [ 214.852] (II) modeset(0): Manufacturer's mask: 0 [ 214.852] (II) modeset(0): Supported standard timings: [ 214.852] (II) modeset(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337 [ 214.852] (II) modeset(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513 [ 214.852] (II) modeset(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897 [ 214.852] (II) modeset(0): #3: hsize: 1280 vsize 720 refresh: 60 vid: 49281 [ 214.852] (II) modeset(0): #4: hsize: 1280 vsize 800 refresh: 60 vid: 129 [ 214.852] (II) modeset(0): #5: hsize: 1440 vsize 900 refresh: 60 vid: 149 [ 214.852] (II) modeset(0): #6: hsize: 1680 vsize 1050 refresh: 60 vid: 179 [ 214.852] (II) modeset(0): #7: hsize: 1920 vsize 1080 refresh: 60 vid: 49361 [ 214.852] (II) modeset(0): Supported detailed timing: [ 214.852] (II) modeset(0): clock: 241.5 MHz Image Size: 598 x 336 mm [ 214.852] (II) modeset(0): h_active: 2560 h_sync: 2608 h_sync_end 2640 h_blank_end 2720 h_border: 0 [ 214.852] (II) modeset(0): v_active: 1440 v_sync: 1443 v_sync_end 1448 v_blanking: 1481 v_border: 0 [ 214.852] (II) modeset(0): Ranges: V min: 40 V max: 75 Hz, H min: 113 H max: 113 kHz, PixClock max 305 MHz [ 214.852] (II) modeset(0): Monitor name: K272HUL [ 214.852] (II) modeset(0): Serial No: T6AAA0018508 [ 214.852] (II) modeset(0): Supported detailed timing: [ 214.852] (II) modeset(0): clock: 298.5 MHz Image Size: 598 x 336 mm [ 214.852] (II) modeset(0): h_active: 2560 h_sync: 2583 h_sync_end 2615 h_blank_end 2670 h_border: 0 [ 214.852] (II) modeset(0): v_active: 1440 v_sync: 1478 v_sync_end 1486 v_blanking: 1492 v_border: 0 [ 214.852] (II) modeset(0): Supported detailed timing: [ 214.852] (II) modeset(0): clock: 220.8 MHz Image Size: 598 x 336 mm [ 214.852] (II) modeset(0): h_active: 1920 h_sync: 2056 h_sync_end 2264 h_blank_end 2608 h_border: 0 [ 214.852] (II) modeset(0): v_active: 1080 v_sync: 1083 v_sync_end 1088 v_blanking: 1130 v_border: 0 [ 214.852] (II) modeset(0): Supported detailed timing: [ 214.852] (II) modeset(0): clock: 148.5 MHz Image Size: 598 x 336 mm [ 214.852] (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0 [ 214.852] (II) modeset(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0 [ 214.853] (II) modeset(0): Supported detailed timing: [ 214.853] (II) modeset(0): clock: 74.2 MHz Image Size: 598 x 336 mm -- [ 214.853] (II) modeset(0): Number of EDID sections to follow: 1 [ 214.853] (II) modeset(0): EDID (in hex): [ 214.853] (II) modeset(0): 00ffffffffffff0004722405f33f1084 [ 214.853] (II) modeset(0): 291c0104b53c22783fb595a65650a026 [ 214.853] (II) modeset(0): 0d5054bfef80714f8140818081c08100 [ 214.853] (II) modeset(0): 9500b300d1c0565e00a0a0a029503020 [ 214.853] (II) modeset(0): 350056502100001a000000fd00284b71 [ 214.853] (II) modeset(0): 711e010a202020202020000000fc004b [ 214.853] (II) modeset(0): 32373248554c0a2020202020000000ff [ 214.853] (II) modeset(0): 005436414141303031383530380a0155 [ 214.853] (II) modeset(0): 020318f14b900102030405111213141f [ 214.853] (II) modeset(0): 23090707830100009774006ea0a03450 [ 214.853] (II) modeset(0): 1720680856502100001a3b5680b07238 [ 214.853] (II) modeset(0): 324088d0350056502100001a023a8018 [ 214.853] (II) modeset(0): 71382d40582c450056502100001e011d [ 214.853] (II) modeset(0): 007251d01e206e28550056502100001e [ 214.853] (II) modeset(0): 8c0ad08a20e02d10103e960056502100 [ 214.853] (II) modeset(0): 001a0000000000000000000000000088 [ 214.853] (II) modeset(0): Printing probed modes for output DP-1 [ 214.853] (II) modeset(0): Modeline "2560x1440"x60.0 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP) [ 214.853] (II) modeset(0): Modeline "2560x1440"x74.9 298.47 2560 2583 2615 2670 1440 1478 1486 1492 +hsync -vsync (111.8 kHz e) [ 214.853] (II) modeset(0): Modeline "1920x1440"x75.0 297.00 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync (112.5 kHz e) [ 214.853] (II) modeset(0): Modeline "1856x1392"x75.0 288.00 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync (112.5 kHz e) [ 214.853] (II) modeset(0): Modeline "1920x1080"x74.9 220.75 1920 2056 2264 2608 1080 1083 1088 1130 +hsync -vsync (84.6 kHz e) [ 214.853] (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) [ 214.853] (II) modeset(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) [ 214.853] (II) modeset(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e) [ 214.853] (II) modeset(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e) [ 214.853] (II) modeset(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) [ 214.853] (II) modeset(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [ 214.853] (II) modeset(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e) [ 214.853] (II) modeset(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e) [ 214.853] (II) modeset(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 -hsync +vsync (49.7 kHz e) [ 214.853] (II) modeset(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) [ 214.853] (II) modeset(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) [ 214.853] (II) modeset(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) [ 214.853] (II) modeset(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) [ 214.853] (II) modeset(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) [ 214.853] (II) modeset(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) [ 214.853] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 214.853] (II) modeset(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) [ 214.853] (II) modeset(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) [ 214.853] (II) modeset(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) [ 214.853] (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [ 214.853] (II) modeset(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) [ 214.853] (II) modeset(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) [ 214.853] (II) modeset(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) [ 214.853] (II) modeset(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 +hsync -vsync (31.5 kHz e) [ 214.853] (II) modeset(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) [ 214.853] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) [ 214.853] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) [ 214.853] (II) modeset(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) [ 214.853] (II) modeset(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [ 214.853] (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [ 214.853] (II) modeset(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) [ 214.853] (II) modeset(0): Output VGA-1 disconnected [ 214.854] (II) modeset(0): Output HDMI-1 disconnected [ 214.854] (II) modeset(0): Output DP-1 connected [ 214.854] (II) modeset(0): Using exact sizes for initial modes [ 214.854] (II) modeset(0): Output DP-1 using initial mode 2560x1440 +0+0 [ 214.854] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0) [ 214.854] (==) modeset(0): DPI set to (96, 96) # get-edid | parse-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 Partial Read... Try again -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-04-06 1:43 a.m., Felix Miata wrote:
# inxi -GxxSM System: Host: vizio Kernel: 5.0.5-1-default x86_64 bits: 64 compiler: gcc v: 8.3.1 Desktop: KDE Plasma 5.15.3 tk: Qt 5.12.2 wm: kwin_x11 dm: KDM Distro: openSUSE Tumbleweed 20190403 Machine: Type: Desktop System: Dell product: OptiPlex 760 v: N/A serial: FVVV4J1 Chassis: type: 15 serial: FVVV4J1 Mobo: Dell model: 0M863N v: A00 serial: ..CN7360494L006I. BIOS: Dell v: A16 date: 08/06/2013 Graphics: Device-1: Intel 4 Series Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2e12 Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa alternate: intel compositor: kwin_x11 resolution: 2560x1440~60Hz OpenGL: renderer: Mesa DRI Intel Q45/Q43 v: 2.1 Mesa 19.0.1 direct render: Yes
Hmm. And what physical monitor is doing the 2560x1440~60Hz? # inxi -GxxSM System: Host: main.HOME.SystemI.ca Kernel: 5.0.6-1.gdff56e4-default x86_64 bits: 64 compiler: gcc v: 8.3.1 Console: tty 3 wm: kwin_x11 dm: KDM Distro: openSUSE Leap 42.3 Machine: Type: Desktop System: Dell product: OptiPlex 755 v: N/A serial: CGMS3G1 Chassis: type: 6 serial: CGMS3G1 Mobo: Dell model: 0GM819 serial: ..CN1374081L011M. BIOS: Dell v: A09 date: 03/11/2008 Graphics: Device-1: Intel 82Q35 Express Integrated Graphics vendor: Dell OptiPlex 755 driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:29b2 Display: server: X.Org 1.18.3 driver: intel unloaded: fbdev,modesetting,vesa compositor: kwin_x11 resolution: 1440x900_60.00~60Hz OpenGL: renderer: Mesa DRI Intel Q35 v: 2.1 Mesa 17.0.5 direct render: Yes -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata composed on 2019-04-06 01:43 (UTC-0400):
# monitor-edid -v ... Name: K272HUL EISA ID: ACR0524 ... # grep -A60 EDID /var/log/Xorg.0.log ... [ 214.852] (II) modeset(0): Manufacturer: ACR Model: 524 Serial#: 2215657459 [ 214.852] (II) modeset(0): Year: 2018 Week: 41 ... [ 214.852] (II) modeset(0): Monitor name: K272HUL
Anton Aylward composed on 2019-04-06 10:15 (UTC-0400):
And what physical monitor is doing the 2560x1440~60Hz?
http://lmgtfy.com/?q=K272HUL cost $180USD last summer. Anton Aylward composed on 2019-04-06 10:25 (UTC-0400):
I've now go to the point where I'm now wondering about an entirely different set of questions such as:
-- should I try to plug in another video card and run the old and new monitors?
Is the 755 a SFF model? If it is, do you keep it running 24/7? If the answer to both is yes, consider doing so not. Lots of heat in a small space with nominal air flow. You might kill a decade+ old PS with questionably adequate reserve or tired old well heated capacitors. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-04-06 1:07 a.m., David Haller wrote:
Hello,
On Fri, 05 Apr 2019, Anton Aylward wrote:
This is what I got =================== # get-edid | parse-edid [..] VBE string at 0x11100 "Intel(r)Q33/Q35/G33 Graphics Chip Accelerated VGA BIOS" [..] I don't know what to do about that.
Looks like your monitor does not supply (valid) EDID/DDC data that get-edid/parse-edid support :(
Yes. Didn't I say that LG Flatron series was notorious for that?
Well, have a look at the xrandr output, the Xorg.*.log etc...
BTDT. The xrandr series bacically tells me what modelines I have set up manually. If I remove the xorg.conf.d altjogehter it gets weird. If I can get it to beeot, which is not most of the time, the lxrandr family tells me that it can display 1024x768 and smaller.
From the pointers i've been given I gather 'native mode' is 1440x900.
The "when" is that a lot of the time I get a message saying that t it can't sync. So I go back to using the xorg.conf.d and stuff various 60hz Modelines in there. Yes, 1440x900@60 works. So does 1280x960@60 and 1280x1024@60 Strangely 1400x1050@60 does but the applications and the KDF5 layout need a bit of juggling. I'm not entirely happy with it. The 1280 and 1440x900 are fine, though. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward composed on 2019-04-04 23:50 (UTC-0400):
Felix Miata wrote:
Xorg has been smart enough to generate modelines on its own (and read them from EDID) for well over a decade. Last time I needed one manually configured was with XFree86 much too long ago to remember.
And you have a choice presented by lxrandr?
I can't answer. I don't have lx anything installed anywhere. I do have xrandr....
IIR many LG models have problems with EDID being incompatible and not supply the information in a way the Xorg works with. I ran into this when I first got the old 1953 and I've seen it discussed many time more in my googling for a solution for the 1942.
So CVT did a good job then and I'm hoping it can again now.
https://www.cnet.com/products/lg-l1953s-lcd-monitor-19/ If your Optiplex 755 is using its onboard Intel GPU and, that's what you connected the 1492 to, it should automatically use 1440x900,
OK, got the cvt:
# cvt 1440 900 # 1440x900 59.89 Hz (CVT 1.30MA) hsync: 55.93 kHz; pclk: 106.50 MHz Modeline "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync
Almost identical to the 60Hz 1440x900 on my ancient 19" Polaroid widescreen NTSC TV....
if the 1492's EDID reports it,
Ha ha ha. "is there a tool to determine that?" No the Xorg.0.log doens't tell me what EDID reports, only what 50-monitor.conf has.
# inxi -GxxSM System: Host: vizio Kernel: 4.20.2-1-default x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: KDE Plasma 5.14.5 tk: Qt 5.12.0 wm: kwin_x11 dm: KDM Distro: openSUSE Tumbleweed 20190124 Machine: Type: Desktop System: Dell product: OptiPlex 760 v: N/A serial: FVVV4J1 Chassis: type: 15 serial: FVVV4J1 Mobo: Dell model: 0M863N v: A00 serial: ..CN7360494L006I. BIOS: Dell v: A16 date: 08/06/2013 Graphics: Device-1: Intel 4 Series Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2e12 Display: server: X.Org 1.20.3 driver: modesetting unloaded: fbdev,vesa alternate: intel compositor: kwin_x11 resolution: 1440x900~75Hz OpenGL: renderer: Mesa DRI Intel Q45/Q43 v: 2.1 Mesa 18.3.1 direct render: Yes # xrandr Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192 VGA-1 connected primary 1440x900+0+0 (normal left inverted right x axis y axis) 410mm x 260mm 1280x1024 59.91 + 75.02 1792x1344 60.00 1600x1200 75.00 70.00 65.00 60.00 1440x900 74.98* 59.89 1280x960 60.00 1152x864 75.00 1024x768 75.03 70.07 60.00 1024x768i 86.96 800x600 72.19 75.00 60.32 56.25 640x480 75.00 72.81 59.94 720x400 70.08 HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) # cat /etc/X11/xorg.conf cat: /etc/X11/xorg.conf: No such file or directory # cat /etc/X11/xorg.conf.d/50-monitor.conf # Having multiple "Monitor" sections is known to be problematic. Make # sure you don't have in use another one laying around e.g. in another # xorg.conf.d file or even a generic xorg.conf file. More details can # be found in https://bugs.freedesktop.org/show_bug.cgi?id=32430. # #Section "Monitor" # Identifier "Default Monitor" # # ## If your monitor doesn't support DDC you may override the # ## defaults here # #HorizSync 28-85 # #VertRefresh 50-100 # # ## Add your mode lines here, use e.g the cvt tool # #EndSection # monitor-edid Name: FLM-1911 EISA ID: PTS00c3 EDID version: 1.3 EDID extension blocks: 0 Screen size: 41.0 cm x 26.0 cm (19.11 inches, aspect ratio 16/10 = 1.58) Gamma: 2.4 Analog signal Max video bandwidth: 210 MHz HorizSync 30-100 VertRefresh 60-75 # Monitor preferred modeline (59.9 Hz vsync, 64.0 kHz hsync, ratio 5/4, 79x100 dpi) (bad ratio) ModeLine "1280x1024" 108 1280 1328 1440 1688 1024 1025 1028 1068 +hsync +vsync # grep -v ^\# /etc/X11/xinit/xinitrc.d/setup | grep xrandr xrandr --dpi 100 --output VGA-1 --mode 1440x900 # modeset or nouveau analog # grep Modeline /var/log/Xorg.0.log [ 214.568] (II) modeset(0): Modeline "1280x1024"x59.9 108.00 1280 1328 1440 1688 1024 1025 1028 1068 +hsync +vsync (64.0 kHz eP) [ 214.568] (II) modeset(0): Modeline "1792x1344"x60.0 204.75 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync (83.6 kHz e) [ 214.568] (II) modeset(0): Modeline "1600x1200"x75.0 202.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (93.8 kHz e) [ 214.568] (II) modeset(0): Modeline "1600x1200"x70.0 189.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (87.5 kHz e) [ 214.568] (II) modeset(0): Modeline "1600x1200"x65.0 175.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (81.2 kHz e) [ 214.568] (II) modeset(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e) [ 214.568] (II) modeset(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) [ 214.568] (II) modeset(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e) [ 214.568] (II) modeset(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e) [ 214.568] (II) modeset(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e) [ 214.568] (II) modeset(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) [ 214.568] (II) modeset(0): Modeline "1024x768"x75.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) [ 214.568] (II) modeset(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) [ 214.568] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [ 214.568] (II) modeset(0): Modeline "1024x768i"x87.0 44.90 1024 1032 1208 1264 768 768 776 817 interlace +hsync +vsync (35.5 kHz e) [ 214.568] (II) modeset(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) [ 214.568] (II) modeset(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) [ 214.568] (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [ 214.568] (II) modeset(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) [ 214.568] (II) modeset(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) [ 214.568] (II) modeset(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) [ 214.568] (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [ 214.568] (II) modeset(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Note the "preferred modeline" is obviously inappropriate for the ~16:10 (1.613:1; 413mm X 256mm) screen that this is. Obviously this is due to broken EDID. 1280x1024 is really stupid looking at this physical ratio. xrandr in startup script as you can see above corrects that here. Any of the GUI screen configuration tools should be able to do the same.
and if you don't have some manual config somewhere to override it. If your kernel cmdline has a video= option and your Xorg is using the Intel DDX driver rather than the default Xorg DDX driver (modesetting), then Xorg will use that cmdline video= mode, assuming the display actually supports it. If the modesetting DDX is in use, this won't happen, same as with AMD and NVidia GPUs.
Just to.
???
But what else can I set the 1942 to?
I don't know if I understand what this asks. xrandr will report available modes. Are you finding none in your Xorg.0.log, or from xrandr, or krandr/kscreen, or arandr? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-04-05 10:57 p.m., Felix Miata wrote:
And you have a choice presented by lxrandr? I can't answer. I don't have lx anything installed anywhere. I do have xrandr....
I run lxrandr under Plasma. It's the GUI version. xrandr returns text only. XRANDR(1) says: NAME xrandr - primitive command line interface to RandR extension while it is very capable, there is no mention of EDID -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward composed on 2019-04-05 23:41 (UTC-0400):
Felix Miata wrote:
And you have a choice presented by lxrandr?
I can't answer. I don't have lx anything installed anywhere. I do have xrandr....
I run lxrandr under Plasma. It's the GUI version. xrandr returns text only.
XRANDR(1) says:
NAME xrandr - primitive command line interface to RandR extension
while it is very capable, there is no mention of EDID
Reading EDID is anything but intuitive. Apps that need to read it generally manage to do what's really needed, though far from always. As long as its Windows drivers work, I doubt most display manufacturers care much about EDID correctness, except maybe for pricey models, not for a 19" 1440x900 from LG. Remember, LG started out in North America as Goldstar, precursor to today's marketplace's "made in China". Did you investigate my other suggestions? What exactly is it you want from it? https://software.opensuse.org/package/monitor-edid hwinfo --display --verbose and Xorg.0.log get it also. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-04-06 1:55 a.m., Felix Miata wrote:
Did you investigate my other suggestions? What exactly is it you want from it?
Yes, and there's a big BUT... Which is that I've been able to experiment, as other branches of this overall thread show, faster. I've now go to the point where I'm now wondering about an entirely different set of questions such as: -- should I try to plug in another video card and run the old and new monitors? -- should I put my my optiplex under the desk and get one of the multitude of mothballed machines from the basement as a terminal server front end for the applications running on the optiplex? Then there are the more important issues like clearing up the garden now the snow has gone, and all the horrific stuff around the house that is often termed 'spring cleaning' that I've been so diligently avoiding. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I dunno if it's a solution to the present problem, I try to read the thread but find it a bit confusing. But I had to "play" with xrandr to get what I wanted on several computers, summarized here: http://www.dodin.org/wiki/pmwiki.php?n=Doc.AddXResolution hope it may help jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/04/2019 01.51, Felix Miata wrote:
Anton Aylward composed on 2019-04-04 17:13 (UTC-0400):
What would be nice is 2560X1600.
Those are seriously expensive. 2560x1440 can be had for half as much or less.
I'm curious. Why a particular resolution not that different from another is that expensive? In any case, the resolution to use would be the native one of the monitor. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. composed on 2019-04-05 13:42 (UTC+0200):
Felix Miata wrote:
Anton Aylward composed on 2019-04-04 17:13 (UTC-0400):
What would be nice is 2560X1600.
Those are seriously expensive. 2560x1440 can be had for half as much or less.
I'm curious. Why a particular resolution not that different from another is that expensive?
Reasonable question. Try shopping for 2560x1600. They come in limited sizes, mostly 30", 13" & 10". https://www.newegg.com/Product/ProductList.aspx?Submit=ENE&IsNodeId=1&N=100161617%20600012686 2560x1440 can be had in 24" or 25". Mine is 27", thin framed, same height and only 2" wider than a much older 24" 1920x1200. I paid $180 new on sale: https://www.newegg.com/Product/Product.aspx?Item=N82E16824009969 -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 05.04.19 um 13:42 schrieb Carlos E. R.:
On 05/04/2019 01.51, Felix Miata wrote:
Anton Aylward composed on 2019-04-04 17:13 (UTC-0400):
What would be nice is 2560X1600.
Those are seriously expensive. 2560x1440 can be had for half as much or less.
I'm curious. Why a particular resolution not that different from another is that expensive?
because it's more or less a business resolution. (aspect ratio 16:10) not the home/gamer/movie aspect_ratio (16:9). i use 2 pices (16:10) 2560x1600 flatron w3000h as double screen at one computer. on all my others i use 1920x1200 (16:10) what is mostly more expensive than 1920x1080 (16:9). and some weeks in past i tried to buy 1920x1200 in 4 different big media shops, none of them had only one in stock, answer of all shops: its not a tv-resolution /aspect ratio, so only a small amount of people like it. for me for business i prefer clearly 16:10. https://de.wikipedia.org/wiki/Bildaufl%C3%B6sung (scroll down for the chart) https://en.wikipedia.org/wiki/Display_resolution (german side has more resolutions in the chart) ============ only for information: the flatron w3000h could bought with a little luck at ebay /second hand for about 100-150€ but these days its not a really good screen. it seems always a little to green and adjusting the colors could only done with software. and i was not able to adjust it that white will be white and all other colors would be nice also. simoN
In any case, the resolution to use would be the native one of the monitor.
-- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/04/2019 15.06, Simon Becherer wrote:
Am 05.04.19 um 13:42 schrieb Carlos E. R.:
On 05/04/2019 01.51, Felix Miata wrote:
Anton Aylward composed on 2019-04-04 17:13 (UTC-0400):
What would be nice is 2560X1600.
Those are seriously expensive. 2560x1440 can be had for half as much or less.
I'm curious. Why a particular resolution not that different from another is that expensive?
because it's more or less a business resolution. (aspect ratio 16:10) not the home/gamer/movie aspect_ratio (16:9).
Ah. Yes, a lot of us use displays that are also TV screens, designed mostly for multimedia. And they are cheaper than ever for sizes that years ago we could only dream about.
i use 2 pices (16:10) 2560x1600 flatron w3000h as double screen at one computer. on all my others i use 1920x1200 (16:10) what is mostly more expensive than 1920x1080 (16:9). and some weeks in past i tried to buy 1920x1200 in 4 different big media shops, none of them had only one in stock, answer of all shops: its not a tv-resolution /aspect ratio, so only a small amount of people like it. for me for business i prefer clearly 16:10.
But it is just a tiny bit bigger. Why not go for higher surface regardless of the aspect ratio? Or both things, more inches and more pixels?
https://de.wikipedia.org/wiki/Bildaufl%C3%B6sung (scroll down for the chart) https://en.wikipedia.org/wiki/Display_resolution (german side has more resolutions in the chart)
So many resolutions! :-o -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (6)
-
Anton Aylward -
Carlos E. R. -
David Haller -
Felix Miata -
jdd＠dodin.org -
Simon Becherer