archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <>
To: "H. Peter Anvin" <>
Subject: Re: 2.6.23: does it supposed to work on an i486?
Date: Fri, 30 Nov 2007 21:43:34 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

H. Peter Anvin wrote:
> Michael Tokarev wrote:
[2.6.23 on an i486 machine]
>> The result is immediately machine reboot right
>> after bootloader (etherboot) passes control to
>> the kernel -- BEFORE "Uncompressing linux"
>> message.
>> 2.6.22 worked just fine.
> It looks like is missing checkin
> 7ed192906a2144ebc8ca2925a85d27b9c5355668 from Linus' tree (attached),
> which is necessary to work on 386 and 486.

Well, I applied the patch (in 2.6.23 it's
but that's minor) - still the same behavior, it still reboots
instantly right when bootloader gave control to the kernel.
So it must be something else.. ;)

I'll try other kernels tomorrow, given some time (I already
spent almost the whole day today with this "machine").  This
whole story prompted me to just throw those machines away and
replace them with tiny devices (a small print server in this
case).  There are still several 486-class machines out there...

By the way, this very machine I'm experimenting with is a
strange beast by itself.  For example, etherboot does not
work on it properly, anything since version 5.1.0 just
freezes right after displaying the "greeting" message.
5.0.11 works.  However till now, linux worked on it just
fine, -- unlike etherboot.



  reply	other threads:[~2007-11-30 18:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 17:32 2.6.23: does it supposed to work on an i486? Michael Tokarev
2007-11-30 18:08 ` H. Peter Anvin
2007-11-30 18:43   ` Michael Tokarev [this message]
2007-11-30 19:08     ` H. Peter Anvin
2007-11-30 19:20     ` Gerb Stralko

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).