From: "Barry K. Nathan" <barryn@cx518206-b.irvn1.occa.home.com>
To: linux-kernel@vger.kernel.org
Subject: [BUG?] AMD K5 and 2.4 (was Re: Updated 2.4 TODO List)
Date: Tue, 14 Nov 2000 20:35:31 -0800 (PST) [thread overview]
Message-ID: <200011150435.UAA05562@cx518206-b.irvn1.occa.home.com> (raw)
In-Reply-To: <200010112210.e9BMAe002775@trampoline.thunk.org> from "tytso@mit.edu" at Oct 11, 2000 06:10:40 PM
(I'm replying to a message from about a month ago, but it's relevant to a
problem I'm having now.)
tytso@mit.edu wrote:
> Date: Mon, 09 Oct 2000 20:13:35 +0200
> From: Thomas Sailer <sailer@ife.ee.ethz.ch>
>
[snip]
> My Asus P55TP4 (i430FX)/AMD K5 PC also crashes after "Booting the
> kernel..."
> and before printing anything else
>
> Are you sure it was compiled with the correct CPU? If you configure the
> CPU incorrectly (686 when you only have a 586, etc.) the kernel *will*
> refuse to boot.
I have a Compaq Presario 425 here, with a K5 upgrade (by Evergreen
Technologies) in it. It reboots immediately after "Booting the kernel..."
with Linux 2.4.0test10 (I haven't tried test11preX on this machine) if the
kernel is compiled for 586/K5/etc. If I compile for 486, then it boots. If
I compile for 586/K5/etc. with 2.2.17, it boots. (This is all with egcs
1.1.2.)
Is this a real bug or just a documentation bug?
-Barry K. Nathan <barryn@pobox.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2000-11-15 5:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200010112210.e9BMAe002775@trampoline.thunk.org>
2000-11-15 4:35 ` Barry K. Nathan [this message]
2000-11-15 19:58 ` [BUG?] AMD 5x86 and 2.4 (was Re: [BUG?] AMD K5 and 2.4) Barry K. Nathan
2000-11-16 11:00 ` Vojtech Pavlik
2000-11-27 1:25 ` Andreas Eibach
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=200011150435.UAA05562@cx518206-b.irvn1.occa.home.com \
--to=barryn@cx518206-b.irvn1.occa.home.com \
--cc=barryn@pobox.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 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.