From: Miles Lane <miles@megapathdsl.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.2-pre2 -- vesafb gives broken virtual terminals.
Date: Fri, 09 Feb 2001 02:41:39 -0800 [thread overview]
Message-ID: <3A83C963.4070602@megapathdsl.net> (raw)
I just gave 2.4.2-pre2 a spin on my laptop. This machine
has a Neomagic MagicGraph 128XD (2160) video chip.
My .config included:
#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
#
# Frame-buffer support
#
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
Notice that "CONFIG_VIDEO_SELECT=y" is defined twice
(not that this has anything to do with my VTs not
working).
This config fails to give usable VTs. When I try to
switch virtual terminals, all I get is an underscore
in the top left part of the screen. Also, XFree86
won't load. It keeps giving me an error about
being unable to use VT number 2.
The broken config gives this log output:
Feb 9 01:16:36 agate kernel: Console: colour dummy device 80x25
Feb 9 01:16:49 agate kernel: vesafb: framebuffer at 0xfd000000, mapped
to 0xc5800000, size 1984k
Feb 9 01:16:49 agate kernel: vesafb: mode is 1024x768x16,
linelength=2048, pages=0
Feb 9 01:16:50 agate kernel: vesafb: protected mode interface info at
c000:8d50
Feb 9 01:16:50 agate kernel: vesafb: scrolling: redraw
Feb 9 01:16:50 agate kernel: vesafb: directcolor: size=0:5:6:5,
shift=0:11:5:0
Feb 9 01:16:50 agate kernel: Console: switching to colour frame buffer
device 128x48
Feb 9 01:16:51 agate kernel: fb0: VESA VGA frame buffer device
If I turn off the framebuffer stuff, I can boot fine and
the virtual terminals work.
Ciao,
Miles
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2001-02-09 10:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A83C963.4070602@megapathdsl.net \
--to=miles@megapathdsl.net \
--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