On 27 Jan, Terry Collins wrote:
> [EMAIL PROTECTED] wrote:
>
>
> > Ah. Yes, I remember the problem I had, now: not enough knowledge. :-)
>
> Umm, {:-), have you read the Video-Timings(?)-HowTO (or RTFM politely).
> It is a bit head turning.
I tried - but some of the variables aren't defined - they're assumed
knowledge I think (I had the same problem with Peter Chubb's attempt to
explain to me).
> My 2c, can your video card handle these modes?
Ah. Excellent question. It's an Nvidia Riva TNT2. I found a random
web page discussing the Riva TNT2 M64 and that it supports 2048x1536.
I'll continue to check.
> > Sorry for being so thick.
>
> Naah, just don't try the readings or calcs after a party in the week
> prior. {:-).
:-) You can say *that* again.
Geoff Reidy uses gtf - I'll see if I can find the source for that (or
try it on one of my newer Linux distros) and see how that works out
(it's not part of my old but continuously updated RH7.2).
Mike McCanna wrote:
> The solutions in the thread so far seem a little labor intensive: are
> y'all aware it should be possible to get exact modelines from your
> Windows monitor.inf file?
>
> I think there's even tools to put them into the format you'd use in
> xorg.conf (or XF86ConFiGrANdoMCAPS.CONFOMGWTFBBQ for those so inclined).
I did have a look at that file originally, but couldn't find any meaty
looking numbers in it. In fact I got the impression that Windows must
do its own calculations after querying the monitor, there was so little
info in the .inf file. But I'll look again - perhaps I only looked at
XP's one.
Thanks, guys, for all the leads.
luke
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
