From: Steven Walter <srwalter@hapablap.dyn.dhs.org>
To: linux-kernel@vger.kernel.org
Subject: VIA Northing workaround /causing/ problems
Date: Sat, 2 Feb 2002 22:40:32 -0600 [thread overview]
Message-ID: <20020202224032.A8010@hapablap.dyn.dhs.org> (raw)
I recently upgraded my kernel from 2.4.10-pre6 to 2.4.18-pre2. After
doing so, X acted extremely weird; whenever just about anything
happened, lines would appear across the screen, almost like static.
After playing around with a few config options that I'd changed, with no
results, I noticed the message about the VIA northbridge bug in dmesg.
I commented out the line listing this chipset in pci-pc.c, recompiled,
and sure enough that fixed the problem!
This board is based on the KT33 chipset. If anyone would like more
information, email me.
--
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
-- George Orwell
He's alive. He's alive! Oh, that fellow at RadioShack said I was mad!
Well, who's mad now?
-- Montgomery C. Burns
next reply other threads:[~2002-02-03 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-03 4:40 Steven Walter [this message]
2002-02-04 16:47 ` VIA Northing workaround /causing/ problems Denis Vlasenko
2002-02-04 15:11 ` Calin A. Culianu
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=20020202224032.A8010@hapablap.dyn.dhs.org \
--to=srwalter@hapablap.dyn.dhs.org \
--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