From: brian@worldcontrol.com
To: Anton Altaparmakov <aia21@cus.cam.ac.uk>
Cc: David Hollister <david@digitalaudioresources.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Conquering the Athlon optimization troubles
Date: Fri, 14 Sep 2001 00:25:58 -0700 [thread overview]
Message-ID: <20010914002558.A2046@top.worldcontrol.com> (raw)
In-Reply-To: <3BA1472E.2000008@digitalaudioresources.org> <Pine.SOL.3.96.1010914012401.21012A-100000@virgo.cus.cam.ac.uk>
In-Reply-To: <Pine.SOL.3.96.1010914012401.21012A-100000@virgo.cus.cam.ac.uk>
> On Thu, 13 Sep 2001, David Hollister wrote:
> > My motherboard is the Epox 8KTA3+, and I'm running an Athlon 1.4GHz.
> > The point to all this is that with the newer BIOS, my machine is now
> > up and running absolutely fine with Athlon optimization turned on.
On Fri, Sep 14, 2001 at 01:28:45AM +0100, Anton Altaparmakov wrote:
> Maybe you meant 9/6/2001. That is the latest available version. From only
> 5 days ago. ...
> Congratulations! (-: I would recommend you to run a long memtest86 as well
> in particular tests 5 and 8. - They are the ones that used to fail for me
> with the inappropriate memmory settings...
I have an Epox 8KTA3+ Duron 900MHz system running linux 2.4.9ac5.
I oopses to death during boot of Athlon/Duron kernels, works fine
with K6 style kernels.
I flashed the BIOS with the 9/6/2001 BIOS upgrade, and the Athlon
optimized kernel dies in exactly the same way it did before.
--
Brian Litzinger <brian@worldcontrol.com>
Copyright (c) 2000 By Brian Litzinger, All Rights Reserved
prev parent reply other threads:[~2001-09-14 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 23:54 Conquering the Athlon optimization troubles David Hollister
2001-09-14 0:28 ` Anton Altaparmakov
2001-09-14 2:22 ` David Hollister
2001-09-14 7:25 ` brian [this message]
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=20010914002558.A2046@top.worldcontrol.com \
--to=brian@worldcontrol.com \
--cc=aia21@cus.cam.ac.uk \
--cc=david@digitalaudioresources.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 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.