On 27 Jan, Peter Chubb wrote: > No, 370MHz. But you need to use a lower freq. to get the > characteristics you want [...] > lukekendall> By commenting out the Flags lines, I was able to get the > lukekendall> 2048x1536 mode to work, though the 1920x1440 mode looks > lukekendall> dangerous - the screen sort of folds back over itself and > lukekendall> looks dark. You can recognise where the windows (folded > lukekendall> horizontally) are. > > That implies the HSync pulse is wrong. Try running xvidtune, and > adjusting it.
I could actually see xvidtune enough to operate it, but couldn't find any combination of Hsync start and end (via left/right off the scale, and wider/narrower) that came anywhere near making a worthwhile improvement. :-( I also realised that I somehow fooled myself that I had 1920x1440 working - actually, it was being rejected by X: (II) NV(0): Not using mode "1920x1440" (hsync out of range) (II) NV(0): Not using mode "1920x1440" (no mode of this name) > lukekendall> Should I have left the DotClock at your 341.5, or perhaps > Yes. > lukekendall> tried 370? Does that affect the other numbers? > And yes. Interestingly, I tried both 341.5 and 370, and the results were a complete failure - for 341.5,X rejected the modelines as invalid for my monitor, and when I (foolishly?) tried 370 the monitor went instantly into power saving mode when I tried to switch resolutions - a safety feature, I assume. I think I simply don't understand the variables well enough to experiment properly. Thanks for your help, though! luke -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
