From: Gerbrand van der Zouw <g.vanderzouw@chello.nl>
To: Patrick Chase <pchase2@pacbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Status of the VIA KT133a and 2.4.x debacle?
Date: Wed, 05 Sep 2001 00:14:12 +0200 [thread overview]
Message-ID: <3B955234.2040204@chello.nl> (raw)
In-Reply-To: <999493106.15509.33.camel@homebase.localdomain>
Patrick Chase wrote:
> Are you enabling or disabling bank interleaving with the new BIOS?
As it turned out, the oopses are not correlated with the bank
interleaving. I can turn the feature on and off and system stability
remains the same (which is good enough to write this mail under X and
compile a kernel).
The other features that this BIOS upgrade (Award v. 2.9) includes are
(from the MSI site):
-Add Bank Interleave item in the BIOS Chipset setup
-Adjust Vcore Voltage Sensitivity on Hardware Monitor
-Show CPU L1 and L2 cache size
-Don't Display Ghz for AMD K7 CPU
-Fixed that WD WD400BB-00AUA1 HDD fail in FDISK with nVidia Geforce2 AGP Card
In fact I do have a nVidia Geforce2 card. Another hypothesis is that the
last fix, also fixes the oopses.
Tomorrow I will flash the BIOS back to 2.7 and see if I get the system
back to the previous, unstable state.
Regards,
Gerbrand van der Zouw
next prev parent reply other threads:[~2001-09-04 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 4:58 Status of the VIA KT133a and 2.4.x debacle? Patrick Chase
2001-09-04 22:14 ` Gerbrand van der Zouw [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-01 14:19 Simen Thoresen
2001-09-01 17:05 ` Simen Thoresen
2001-09-01 17:11 ` Nicholas Knight
2001-09-02 22:53 ` Gerbrand van der Zouw
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=3B955234.2040204@chello.nl \
--to=g.vanderzouw@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=pchase2@pacbell.net \
/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.