From: Kurt Roeckx <Q@ping.be>
To: linux-kernel@vger.kernel.org
Subject: Problem with framebuffer in 2.6.0-test3
Date: Fri, 15 Aug 2003 16:20:08 +0200 [thread overview]
Message-ID: <20030815142008.GA22123@ping.be> (raw)
If I compile with framebuffer I get weird results during boot.
When I use "vga=normal", I get this weird screen during boot.
It doesn't show any text. It just lots of coloured pixels.
When I use "vga=0x301" I just get a blank screen during boot.
In the init scripts I call fbset to set the proper resolution,
which work in both cases.
Here is part of my .config:
CONFIG_FB=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=y
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
CONFIG_FB_3DFX=y
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_VIRTUAL is not set
>From dmesg (with vga=0x301)
Linux version 2.6.0-test3 (root@Q) (gcc version 2.95.3 20010315
(release)) #6 Mon Aug 11 19:47:08 CEST 2003
Video mode to be used for restore is 301
...
Console: colour dummy device 80x25
...
fb: 3Dfx Banshee memory = 16384K
vesafb: abort, cannot reserve video memory at 0xe6000000
vesafb: framebuffer at 0xe6000000, mapped to 0xcf802000, size
16384k
vesafb: mode is 640x480x8, linelength=640, pages=53
vesafb: protected mode interface info at c000:7e95
vesafb: scrolling: redraw
fb1: VESA VGA frame buffer device
vga16fb: initializing
vga16fb: mapped to 0xc00a0000
fb2: VGA16 VGA frame buffer device
Console: switching to colour frame buffer device 80x30
With vga=normal
Linux version 2.6.0-test3 (root@Q) (gcc version 2.95.3 20010315
(release)) #6 Mon Aug 11 19:47:08 CEST 2003
Aug 11 20:13:45 Q kernel: Video mode to be used for restore is f00
...
Console: colour VGA+ 80x25
...
fb: 3Dfx Banshee memory = 16384K
vga16fb: mapped to 0xc00a0000
fb1: VGA16 VGA frame buffer device
Console: switching to colour frame buffer device 80x30
Kurt
next reply other threads:[~2003-08-15 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 14:20 Kurt Roeckx [this message]
[not found] ` <20030815141846.083f3d2d.akpm@osdl.org>
2003-08-15 21:59 ` Problem with framebuffer in 2.6.0-test3 Kurt Roeckx
2003-08-15 22:04 ` James Simmons
2003-08-15 22:03 ` James Simmons
2003-08-15 22:46 ` Kurt Roeckx
2003-08-15 22:59 ` James Simmons
2003-08-16 15:09 ` Kurt Roeckx
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=20030815142008.GA22123@ping.be \
--to=q@ping.be \
--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