From: Nicholas Knight <tegeran@home.com>
To: linux-kernel@vger.kernel.org
Subject: K7/Athlon optimizations again. (The sacrifices worked??) (VIA KT133A chipset)
Date: Thu, 6 Sep 2001 13:55:31 -0700 [thread overview]
Message-ID: <01090613553103.00465@c779218-a> (raw)
Thanks to Charles Cazabon, I now have a new theory.
to quote, I'm the one he quoted here:
----Begin Quote---
> And I CAN nail it down to a particular chipset. It only occurs on VIA
> KT133A chipsets so far, unfortunitely it doesn't occur 100% of the time
> on that chipset.
I'd be curious if it's an issue with only one brand or release of BIOS
then.
----End Quote----
And thus begins a new round, I started by slapping myself.
I've seen two instances so far of someone mentioning that one BIOS
release caused problems while another did not. One was mentioned on the
list, one was part of the reports sent to me. I completely passed over
this information and I have no idea why.
Everyone having problems, here's what you could try:
Upgrade to the latest BIOS version for your board.
If you are at the latest BIOS version, go back a version or two.
For those NOT having problems, and who would like to help test/live
dangerously, could you also try the previously mentioned upgrades or
downgrades?
And be sure to have a non-K7 optimized kernel installed as a backup
incase you forget to make TWO diskettes for upgrading your BIOS and it's
your only system :)
This problem doesn't even affect me, I'm not a developer, and any system
I buy in the future will be long after the KT133A is "outdated", I don't
know why I'm hammering at this so much.
next reply other threads:[~2001-09-06 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 20:55 Nicholas Knight [this message]
2001-09-06 21:51 ` K7/Athlon optimizations again. (The sacrifices worked??) (VIA KT133A chipset) Gerbrand van der Zouw
2001-09-06 22:01 ` Luigi Genoni
2001-09-06 23:55 ` Re[2]: " victor
2001-09-07 0:15 ` brian
2001-09-07 0:57 ` Jonathan Morton
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=01090613553103.00465@c779218-a \
--to=tegeran@home.com \
--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