From: frank@inua.be
To: 9fans@9fans.net
Subject: Re: [9fans] [frank@inua.be: Re: no frame buffer]
Date: Thu, 27 May 2010 23:02:41 +0200 [thread overview]
Message-ID: <20100527210241.GA4382@chiron.galaxy> (raw)
In-Reply-To: <ee1e8b12012be4a0a0a69ec1731e1881@kw.quanstro.net>
On Wed, May 26, 2010 at 08:00:59PM -0400, erik quanstrom wrote:
> On Wed May 26 12:33:49 EDT 2010, frank@inua.be wrote:
> > I don't see a follow-up on this topic... I hope someone still has an
> > idea.
>
> not really. you may wish to double-check the vga register
I used aux/vga -ip with some different resolutions. The only strange
thing I see is that under "dbdumpmode" "frequency=100" always comes
back.
> settings. not sure about crt[13].
What do you mean with "crt[13]"?
> sometimes aux/vga -l text works when nothing else
> does.
I had already tried that, but it doesn't work either.
It seems I can stop searching. I have an identical box running Linux
and used lspci, which gave me some more info compared to the pci -v
output on Plan 9:
...
00:01.1 VGA compatible controller [0300]: National Semiconductor Corporation Geode GX2 Graphics Processor [100b:0030] (prog-if 00 [VGA controller])
Subsystem: National Semiconductor Corporation Geode GX2 Graphics Processor [100b:0030]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Region 0: Memory at 41000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at 40ffc000 (32-bit, non-prefetchable) [size=16K]
Region 2: Memory at 40ff8000 (32-bit, non-prefetchable) [size=16K]
Region 3: Memory at 40ff4000 (32-bit, non-prefetchable) [size=16K]
Kernel modules: gxfb
...
I googled for AMD GX2 graphics processor and the first result led to:
http://plan9.bell-labs.com/wiki/plan9/Supported_PC_hardware/index.html
...
The following cards are known not to work with VESA:
...snip...
* AMD Geode GX2. Blank screen. Bug identified by Russ Cox, but hard to solve.
...
Too bad, but at least, I learned something. I'll use a Via Epia box as
terminal to start learning the rest;-)
> - erik
--
Frank Lenaerts ---------------------------------------- frank@inua.be
next prev parent reply other threads:[~2010-05-27 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 16:32 frank
2010-05-27 0:00 ` erik quanstrom
2010-05-27 21:02 ` frank [this message]
2010-06-06 20:13 ` David du Colombier
2010-06-06 21:26 ` 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=20100527210241.GA4382@chiron.galaxy \
--to=frank@inua.be \
--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).