From: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>
To: John R Lenton <john@grulic.org.ar>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Au-Ja <doelf@au-ja.de>, Yiping Chen <YipingChen@via.com.tw>,
support@msi.com.tw, info@msi-computer.de, support@via-cyrix.de
Subject: VIA's Southbridge bug (was: PATCH 2.4.5.1: Fix Via interrupt routing issues)
Date: Tue, 15 May 2001 11:34:53 +0200 [thread overview]
Message-ID: <20010515113453.A3539@pua.nirvana> (raw)
On Mon, May 14, 2001 at 02:07:53PM -0300, John R Lenton wrote:
> On Sun, May 13, 2001 at 01:28:06PM -0400, Jeff Garzik wrote:
> > For those of you with Via interrupting routing issues (or
> > interrupt-not-being-delivered issues, etc), please try out this patch
> > [...]
> Just to add a little noise: My box (msi 694d pro AI motherboard,
> revI, i.e. vt82c686a) been a *lot* stabler since I removed the
> Live! and dropped back to the onboard soundcard.
> [...]
> If I could put in words the difference between the Live! and the
> via, I would. Alas, I can't, so you're stuck with this inane
> rant:
>
> please please please fix it.
This has nothing to do with the routing issue, but is a bigger problem by
itself :(
The VIA chipset is buggy, and your Soundblaster Live! increases the likelyhood
of triggering that bug. This is a rather well documented problem, read an
english article about it on http://www.au-ja.de/review-kt133a-1-en.html and a
german article on the discussion of this on the lkml on
http://www.au-ja.de/review-kt133a-linux.html (if you don't read German this is
not a problem, as all links found there refer to english pages).
You seem to have bad luck, as the 686a should not be a buggy as the 686b.
Bottom line: Try to get a BIOS upgrade and hope that VIA will opensource and
contribute their Windows patch to linux...
Regards, Axel.
--
Axel.Thimm@physik.fu-berlin.de
reply other threads:[~2001-05-15 9:36 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=20010515113453.A3539@pua.nirvana \
--to=axel.thimm@physik.fu-berlin.de \
--cc=YipingChen@via.com.tw \
--cc=doelf@au-ja.de \
--cc=info@msi-computer.de \
--cc=john@grulic.org.ar \
--cc=linux-kernel@vger.kernel.org \
--cc=support@msi.com.tw \
--cc=support@via-cyrix.de \
/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