From: john@csplan9.rit.edu
To: 9fans@9fans.net
Subject: Re: [9fans] vgadb woes
Date: Wed, 15 Apr 2009 15:18:48 -0400 [thread overview]
Message-ID: <def333318eb99b2e3027bb46fef85cb5@csplan9.rit.edu> (raw)
In-Reply-To: <9ab217670904151211rb880e2fy1f25fa41dbbedb95@mail.gmail.com>
> I've got a laptop that I (for shits and giggles) decided to put Plan 9
> on. Lo and behold, it worked fine (Compal EL80, Core 2 Duo, 2GB RAM,
> nVidia video).
>
> So, I'm running at 1280x1024x32 right now in VESA, which is
> reasonable, but I'd like to run at my maximum native resolution, which
> is 1680x1050 (I believe). After tooling around with Xorg configs, I've
> found a horiz/vert refresh rate that should work for me...
>
> ...except that I have no idea how to convert that into vgadb lingo.
> I've read all the comments in vgadb, and the manpage, which helpfully
> suggests that I purchase a rather dated book. I suppose it's at least
> available, but in the interest of ``I want it now,'' are there any
> hints on translating eg.
>
> Option "DPMS"
> HorizSync 28-84
> VertRefresh 43-60
>
> into vgadb(6) lingo?
>
> Only other bit of potentially relevant information I have is that Xorg
> reports the monitor as having a ``330.0 MHz pixel clock''.
>
> Thanks,
>
> --dho
I got something working for me, so I wrote a wiki page:
http://www.plan9.bell-labs.com/wiki/plan9/Adding_a_monitor_to_vgadb/index.html
Hope that helps; I've tried something similar with a different monitor
and managed to get a setup that causes the screen to jiggle and hurt
my eyes, so your mileage may vary.
John
next prev parent reply other threads:[~2009-04-15 19:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 19:11 Devon H. O'Dell
2009-04-15 18:43 ` Eris Discordia
2009-04-15 19:18 ` john [this message]
2009-04-15 19:26 ` blstuart
2009-04-15 19:44 ` erik quanstrom
2009-04-15 19:45 ` Steve Simon
2009-04-15 20:13 ` Devon H. O'Dell
2009-04-15 23:30 ` Devon H. O'Dell
2009-04-16 2:16 ` erik quanstrom
2009-04-16 3:55 ` Venkatesh Srinivas
2009-04-16 12:33 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=def333318eb99b2e3027bb46fef85cb5@csplan9.rit.edu \
--to=john@csplan9.rit.edu \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).