From: frank@inua.be
To: 9fans@9fans.net
Subject: Re: [9fans] no frame buffer
Date: Sun, 23 May 2010 23:41:39 +0200 [thread overview]
Message-ID: <20100523214139.GA25735@chiron.galaxy> (raw)
In-Reply-To: <a789e80fc25704103187023a1ead8c04@kw.quanstro.net>
On Sat, May 22, 2010 at 08:01:40PM -0400, erik quanstrom wrote:
> > However, when this box boots via PXE, it has the same issue... Any
> > idea what might be wrong?
>
> perhaps vgasize or monitor is unset. try
>
> vgasize=1280x1024x16 # adjust as appropriate. cf. vga(8)
> monitor=vesa
> aux/vga -l $vgasize
Since the issue is solved on the Via Epia system, I turned back to the
AMD Geode system but for some reason, I can't get that box in
graphical mode. Whatever I use for monitor (vesa, vga) or vgasize, the
screen just turns black and the led of the monitor is blinking.
This is what pci -v shows about the VGA controller:
0.1.1: vid 03.00.00 100b/0030 0 0:41000000 16777216 1:40ffc000 16384 2:40ff8000 16384 3:40ff4000 16384
National Semiconductors NSC Geode VGA Compatible Device
This is what aux/vga -m vesa -p displays about the modes:
vesa mode 0x101 640x480x8 m8 packed
vesa mode 0x103 800x600x8 m8 packed
vesa mode 0x105 1024x768x8 m8 packed
vesa mode 0x107 1280x1024x8 m8 packed
vesa mode 0x110 640x480x15 r5g5b5 direct
vesa mode 0x111 640x480x16 r5g6b5 direct
vesa mode 0x112 640x480x32 r8g8b8 direct
vesa mode 0x113 800x600x15 r5g5b5 direct
vesa mode 0x114 800x600x16 r5g6b5 direct
vesa mode 0x115 800x600x32 r8g8b8 direct
vesa mode 0x116 1024x768x15 r5g5b5 direct
vesa mode 0x117 1024x768x16 r5g6b5 direct
vesa mode 0x118 1024x768x32 r8g8b8 direct
vesa mode 0x119 1280x1024x15 r5g5b5 direct
vesa mode 0x11a 1280x1024x16 r5g6b5 direct
vesa mode 0x11b 1280x1024x32 r8g8b8 direct
vesa mode 0x125 1152x864x8 m8 packed
vesa mode 0x126 1152x864x15 r5g5b5 direct
vesa mode 0x127 1152x864x16 r5g6b5 direct
vesa mode 0x128 1152x864x32 r8g8b8 direct
vesa mode 0x131 1600x1200x8 m8 packed
vesa mode 0x132 1600x1200x15 r5g5b5 direct
vesa mode 0x133 1600x1200x16 r5g6b5 direct
I would expect to at least get something like 640x480x8 working...
> - erik
--
Frank Lenaerts ---------------------------------------- frank@inua.be
next prev parent reply other threads:[~2010-05-23 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 22:55 frank
2010-05-23 0:01 ` erik quanstrom
2010-05-23 10:08 ` frank
2010-05-23 11:26 ` Richard Miller
2010-05-23 13:55 ` frank
2010-05-23 21:41 ` frank [this message]
2010-05-23 23:00 ` Ethan Grammatikidis
2010-05-24 19:45 ` frank
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=20100523214139.GA25735@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).