On Wed, Aug 25, 2010 at 7:57 AM, Paul Hartman > wrote: > On Wed, Aug 25, 2010 at 9:44 AM, Mick wrote: > > On 25 August 2010 15:38, Paul Hartman > > wrote: > >> On Wed, Aug 25, 2010 at 9:25 AM, Mick > wrote: > >>> On 25 August 2010 15:17, Paul Hartman > > wrote: > >>>> On Tue, Aug 24, 2010 at 7:03 PM, Kevin O'Gorman > 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. > > Of course, and I agree completely, but what I was going for was at > least he can get blurry 16:9 that fills the whole screen rather than > 4:3 that is either stretched or leaves gaps on the sides. :) > > Precisely my goal when I started this thread. In my case, native appears to be 1920x1080. With no xorg.conf, X finds 1280x1024, which is usable either stretched, or with the gaps. There is no discernable flicker, blur or distortion, just capacity that is not being used. There are some confusing things about this. - The log contains 1920x1080 modelines, but is not using them or clearly stating the reason. - The log contains the lines (!!) MACH64(0): Virtual resolutions will be limited to 8191 kB due to linear aperture size and/or placement of hardware cursor image area. I have no idea how to reconcile that with the fact that the resolution being used results in 1310720 (1.3 million) pixels, at 3 bytes (24 bits) per pixel, which sounds to me like over 3 megabytes. The desired resolution would have 2073600 (2 million) pixels and about 6 megabytes. They sound too big, but the first one actually works. I don't understand this at all. - (--) MACH64(0): Internal programmable clock generator detected. (--) MACH64(0): Reference clock 157.5/11 (14.318) MHz. (II) MACH64(0): : Using hsync range of 30.00-85.00 kHz (II) MACH64(0): : Using vrefresh range of 55.00-75.00 Hz (II) MACH64(0): : Using maximum pixel clock of 160.00 MHz (II) MACH64(0): Estimated virtual size for aspect ratio 1.7931 is 1920x1080 (this bothers me because, 1920/1080 is more like 1.7777) (II) MACH64(0): Maximum clock: 120.00 MHz So it's still contemplating 1920x1080, but mentions both 120MHz and 160MHz as the max for pixel clock. Anyway, for 2 million pixels, 120MHz is not going to cover any overhead at 60 Hz, and 55Hz might not make it either. Maybe the MACH64 cannot actually get above 120 MHz. How to find out if that's what the log is trying to say? - it complains about memory for 2048x1536, but not for anything smaller (I don't think the monitor has that many pixels anyway.) So I guess there's memory enough for all the others. Instead it complains about many modelines in this fashion (but showing just the last 2 lines) (II) MACH64(0): Not using driver mode "1920x1080" (bad mode clock/interlace/doublescan) (WW) MACH64(0): Shrinking virtual size estimate from 1920x1080 to 1280x1024 -- Kevin O'Gorman, PhD