Comment 12 for bug 311485
Revision history for this message
| clubsoda (clubsoda) wrote Re: Logix Monitor: Default Resolution Not Valid | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
>The resolution is probably another story.
Yes. I'm regretting the title of this bug report now because I'm no longer worried about the resolution at all. The screen is quite happy at 1400x1050 and even did 1680x1050 when I added these as per your suggestion:-
HorizSync 30.0-70.0
VertRefresh 50.0-120.0
DisplaySize 320 240
Of course, the monitor doesn't have that many physical pixels and thinks those higher modes are 1280x1024 but it's not as if smoke is billowing out the back or anything terrible.
[Those timings were sourced from a Korean page which lists many other Logix monitors too.
http://
In case of a 404 error, Google-> LG-1731D ModeLine <- and click on "View as HTML" to see Google's cache.]
So the real problem is the oversized panel font.
- Option "DDC" "false" works but with limited modes, starting up at only 1152x864.
- Quirks are a good idea but only for monitors we know about.
Moreover, neither of those solutions is available from the kernel boot line (as far as I know), for others who experience this kind of problem.
The VESA document suggests that EDID v1.0, v1.1 and v1.2 should not be trusted with respect to the "detailed timing descriptions" field. If there was a way for the driver to be skeptical about early version EDID but still allow X to come up with exotic timings (which even the manufacturers weren't aware were possible), then that could be ideal.
Thanking you again for your time on this,
Regards.