From: "Norman Diamond" <ndiamond@wta.att.ne.jp>
To: <linux-kernel@vger.kernel.org>
Subject: 2.6.0-test7 vs. vga= boot parameter
Date: Mon, 13 Oct 2003 14:03:05 +0900 [thread overview]
Message-ID: <316c01c39147$8e019600$5cee4ca5@DIAMONDLX60> (raw)
On a machine with unknown graphics chip and a 1024x768 screen,
2.4.18 and 2.6.0-test1 through test7 can all be booted with
vga=791 and have no problem.
On a machine with a Neomagic 128XD chip and an 800x600 screen,
2.4.19 and 2.4.20 can be booted with vga=788 and have no problem.
But booting 2.6.0-test1 through test7 with vga=788 yields a
black screen during boot and disables all text mode displays
in VT consoles. After X11 starts up, switching to a VT just
displays whatever was last put in graphics memory by X11 and
does not change until I switch back to X11.
Booting 2.6.0-test1 through test7 without any vga option has
no problem displaying boot messages, and after X11 starts up,
it has no problem switching between X11 and VT consoles.
This part of dmesg might be relevant to the vga problem in test7.
vesafb seems to say it aborted and then succeeded, but maybe it
aborted and went crazy instead?
neofb: mapped io at c6800000
Autodetected internal display
Panel is a 800x600 color TFT display
neofb: mapped framebuffer at c6a01000
neofb v0.4.1: 2048kB VRAM, using 800x600, 37.878kHz, 60Hz
fb0: MagicGraph 128XD frame buffer device
vesafb: abort, cannot reserve video memory at 0x43000000
vesafb: framebuffer at 0x43000000, mapped to 0xc6c02000, size 1984k
vesafb: mode is 800x600x16, linelength=1600, pages=1
vesafb: protected mode interface info at c000:8cb0
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
fb1: VESA VGA frame buffer device
next reply other threads:[~2003-10-13 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 5:03 Norman Diamond [this message]
2003-10-13 6:04 ` M. Lucas
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='316c01c39147$8e019600$5cee4ca5@DIAMONDLX60' \
--to=ndiamond@wta.att.ne.jp \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®