On 25 August 2010 15:38, Paul Hartman <paul.hartman+gen...@gmail.com> wrote: > On Wed, Aug 25, 2010 at 9:25 AM, Mick <michaelkintz...@gmail.com> wrote: >> On 25 August 2010 15:17, Paul Hartman <paul.hartman+gen...@gmail.com> wrote: >>> On Tue, Aug 24, 2010 at 7:03 PM, Kevin O'Gorman <kogor...@gmail.com> wrote: >>>> I found the specs with Hsync and VSync limits, but they don't mention the >>>> clock speed. I guess I'll just have to fool with it until it works or >>>> catches fire. >>> >>> That basically describes the way I've done my X monitor settings for >>> the past 10 years or so. I just made up a bunch of numbers and hope >>> they accidentally work. :) Now I'm thankful for EDID in monitors and >>> smarter video drivers. >> >> I think that if xrandr -q does not show the resolution you are >> seeking, then the video card or driver in question cannot provide it. >> I'm not sure that feeding xorg any odd modeline will change things, >> plus unlike a CRT monitor, LCDs only provide a clear image at their >> native resolution (denoted by '+' in the xrandr list of resolutions) > > I've been able to generate modelines in the past for all kinds of > crazy non-standard resolutions. I think the ones listed may be the > ones defined in the card's BIOS. > > I just remembered about CVT, I think it's what I used to generate the > modelines I posted earlier. It is part of the x11-base/xorg-server > package and will generate the frequencies and everything for you based > on VESA standards. You simply give it X and Y resolution and it does > the rest. For example: > > $ cvt 1280 720 > # 1280x720 59.86 Hz (CVT 0.92M9) hsync: 44.77 kHz; pclk: 74.50 MHz > Modeline "1280x720_60.00" 74.50 1280 1344 1472 1664 720 723 728 > 748 -hsync +vsync
Fair enough, but anything other than the native resolution on an LCD monitor will end looking distorted or blurred. -- Regards, Mick
