From: Christer Weinigel <wingel@acolyte.hack.org>
To: jfbeam@bluetronic.net
Cc: zwane@linux.realnet.co.sz, pwaechtler@loewe-komp.de,
alan@lxorguk.ukuu.org.uk, pierre.ficheux@openwide.fr,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.18 AND Geode GX1/200Mhz problem
Date: Sat, 13 Apr 2002 22:45:04 +0200 (CEST) [thread overview]
Message-ID: <20020413204504.6B104F5B@acolyte.hack.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0204111246400.29312-100000@sweetums.bluetronic.net> (message from Ricky Beam on Thu, 11 Apr 2002 12:51:29 -0400 (EDT))
Ricky Beam <jfbeam@bluetronic.net> wrote:
> On a side note, has anyone seen dd scrolling behavior with video chipse
> using shared memory? On the geode board I'm playing with, the screen
> never scrolls correctly. It's probablly something stupid in the 5530's
> setup that's at fault. (I have ever intention of turning the VGA port
> off entirely.)
The VSA CGA/EGA/VGA text emulation seems to be rather awful and has
lots of bugs. Compile in the VESA framebuffer support in your Linux
kernel and add vga=785 (see linux/Documentation/fb/vesafb.txt) to
your kernel command line. It's a choice of:
Linux kernel frobs the text console -> buggy VSA emulation -> framebuffer
or
Linux kernel frobs the framebuffer directly
Guess which works better? *grin*
/Christer
--
"Just how much can I get away with and still go to heaven?"
next prev parent reply other threads:[~2002-04-13 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-07 23:19 2.4.18 AND Geode GX1/200Mhz problem Pierre Ficheux
2002-04-07 23:41 ` Alan Cox
2002-04-08 9:30 ` Peter Wächtler
2002-04-08 11:12 ` Zwane Mwaikambo
2002-04-11 16:51 ` Ricky Beam
2002-04-13 19:08 ` Alan Cox
2002-04-13 20:45 ` Christer Weinigel [this message]
2002-04-08 12:58 ` Pierre Ficheux
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=20020413204504.6B104F5B@acolyte.hack.org \
--to=wingel@acolyte.hack.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jfbeam@bluetronic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre.ficheux@openwide.fr \
--cc=pwaechtler@loewe-komp.de \
--cc=zwane@linux.realnet.co.sz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.