From: "Tom Eastep" <teastep@shorewall.net>
To: <bernat@free.fr>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: VIA Northbridge Workaround in 2.4.18 Causing Video Problems
Date: Wed, 27 Feb 2002 07:12:09 -0800 [thread overview]
Message-ID: <000001c1bfa1$20759060$0501a8c0@ursa> (raw)
In-Reply-To: <m3u1s4asb4.fsf@neo.loria>
Vincent,
> -----Original Message-----
> From: bernat@free.fr [mailto:bernat@free.fr]
> Sent: Tuesday, February 26, 2002 12:42 PM
> To: Tom Eastep
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: VIA Northbridge Workaround in 2.4.18 Causing
> Video Problems
>
> Tom Eastep <teastep@shorewall.net> disait:
>
>
> > I'm currently getting around the problem with the following hack:
>
> You may use the "setpci" command instead to fix this in "userland".
>
Thanks for the suggestion -- unfortunately, it is only a partial
solution.
During boot with an 80x25 VGA console, the console video is getting
trashed even before the first init script runs. In that case, correcting
the root cause (setting bit 5 in byte 0x55 of the Northbridge config)
does nothing to restore console video (although it does allow X to run
properly).
So long as I am running a kernel that includes my hack, there's no
problem. My main concern is that the next time that people with a system
like mine want to upgrade their distribution, the distribution's kernel
will include this workaround; those people (myself included) will then
have a miserable time doing the upgrade.
-Tom
--
Tom Eastep \ Shorewall -- iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
next prev parent reply other threads:[~2002-02-27 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 19:57 Tom Eastep
2002-02-26 20:42 ` Vincent Bernat
2002-02-26 21:19 ` Mark Cooke
2002-02-27 15:12 ` Tom Eastep [this message]
2002-02-27 16:29 ` Vincent Bernat
2002-02-27 2:27 ` Steven Walter
2002-02-27 22:33 ` James Cassidy
2002-02-27 22:45 ` Tom Eastep
2002-02-27 18:01 Alex Davis
2002-02-27 21:26 ` Mark Cooke
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='000001c1bfa1$20759060$0501a8c0@ursa' \
--to=teastep@shorewall.net \
--cc=bernat@free.fr \
--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®