From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] vgadb woes
Date: Wed, 15 Apr 2009 22:16:33 -0400 [thread overview]
Message-ID: <4d8f702bb4309f9ac9a89e6266b81fea@quanstro.net> (raw)
In-Reply-To: <9ab217670904151630u70220a0ah59a156c4033fb107@mail.gmail.com>
On Wed Apr 15 19:32:57 EDT 2009, devon.odell@gmail.com wrote:
> Well, that ends up getting my screen to have a bunch of lines through
> it, staggered -- so I'm not much better off than I was before. I'm
> guessing that's an nVidia driver issue or something. If I had any idea
> about video devices, I'd try to fix it, but I don't. I'll just live
> with a bit low-res VESA for now (all of the VESA modes don't seem to
> work), unless someone has ideas.
>
> Thanks!
>
> --dho
i'll put my terrible, awful, reprehensible, reprobate, disgusting nvidia
driver that sort-of works if you squint and set the mode incorrectly
up on sources (/n/sources/contrib/quanstro/src/vga). you may need to
have a monitor fairly resistant to misset frequencies. i had to hack my
vgadb. the commented-out line is correct for my montior. clearly i
don't have the frequency calculations right at all.
213t=1600x1200 # 60 Hz
clock=150
# shb=1664 ehb=1856 ht=2160
shb=1664 ehb=1856 ht=2058
vrs=1201 vre=1204 vt=1250
hsync=+ vsync=+
i really need to write a driver for integratede modern intel or ati
graphics.
- erik
next prev parent reply other threads:[~2009-04-16 2:16 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
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 [this message]
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=4d8f702bb4309f9ac9a89e6266b81fea@quanstro.net \
--to=quanstro@quanstro.net \
--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).