From: Gerbrand van der Zouw <g.vanderzouw@chello.nl>
To: tegeran@home.com, linux-kernel@vger.kernel.org
Subject: Re: K7/Athlon optimizations again. (The sacrifices worked??) (VIA KT133A chipset)
Date: Thu, 06 Sep 2001 23:51:28 +0200 [thread overview]
Message-ID: <3B97EFE0.30703@chello.nl> (raw)
In-Reply-To: <01090613553103.00465@c779218-a>
Nicholas Knight wrote:
> I'd be curious if it's an issue with only one brand or release of BIOS
> then.
Hi,
I am one of the person reporting success with some BIOS version over
another. I have been experimenting some more and found the following:
Sytem:
Board: MSI K7T Turbo (MS-6330)
CPU: Athlon 1.2 GHz
Video: NVidia GF2
Kernel: 2.4.6ac5 with the patch Kurt Garloff posted here some while ago
(can't find the right reference)
Ranking from very unstable to stable:
Very unstable: 2.4.6 plain, Award V2.7 Bios (i.e. without the
Southbridge bug solved the official VIA way)
Unstable: 2.4.6ac5 with or without Kurt's patch, Award V2.7 Bios
Stable (up to now): 2.4.6ac5 with Kurt's patch and Award V2.8 Bios.
The key factor seemed to be the BIOS. The MSI website says that the
following things changed between release 2.7 and 2.8:
- Fix STR Fail on MS-6330Lite.
- Fix 3Dmark 2001 sometimes halt
- Fix K7T Turbo Limited cannot adjust vcore
Only the second fix seems applicable to my mobo, but the description
does not give a clue.
I hope that someone can distill something useful out of this. I am of
course willing to try some other combination of parameters if this would
help finding the source of the problem.
Cheers,
Gerbrand van der Zouw
next prev parent reply other threads:[~2001-09-06 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 20:55 K7/Athlon optimizations again. (The sacrifices worked??) (VIA KT133A chipset) Nicholas Knight
2001-09-06 21:51 ` Gerbrand van der Zouw [this message]
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=3B97EFE0.30703@chello.nl \
--to=g.vanderzouw@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=tegeran@home.com \
/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.