From: John Bradford <john@grabjohn.com>
To: fkosa@eposta.hu (Kósa Ferenc)
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM
Date: Sun, 9 Mar 2003 12:55:02 +0000 (GMT) [thread overview]
Message-ID: <200303091255.h29Ct2aF001120@81-2-122-30.bradfords.org.uk> (raw)
In-Reply-To: <1047210594.13821.37.camel@daisy> from "=?ISO-8859-1?Q?K=F3sa?= Ferenc" at Mar 09, 2003 12:49:55 PM
> 1. Newer kernels do not boot on 386
>
> 2. I use linux successfully since 1997. A year ago I've tried to use
> linux on an AMD 5x86, and I realized that newer kernels (>2.4.13) do no=
> t
> boot. It starts: "loading linux........" and then after a while it
> reboots the computer, before "Ok, booting the kernel". I found the same
> problem on a Cyrix 486SLC2 too. I tried compile kernels by myself, but
> they did the same too, except for 2.4.13. The official Debian
> kernel-images failed too. I use lilo-2.2, with debian 3.0 stable
> (woody).
I've used 2.4.18 extensively on an Intel 486 SX-25, without problems.
I did notice the immediate rebooting problem using a few old 2.5.x
trees, but that was months ago, around the 2.5.40 timeframe, more
recent 2.5.x trees worked fine.
Incidently, I haven't had time to do my usual testing on low spec
machines recently, but intend restart that at the earliest
opportunity.
John.
next prev parent reply other threads:[~2003-03-09 12:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 11:49 PROBLEM Kósa Ferenc
2003-03-09 12:55 ` John Bradford [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-27 1:35 PROBLEM Thomas Kayser
2006-02-03 12:02 PROBLEM Badri Pillai
2004-12-24 4:22 PROBLEM Scott Mollica
2004-12-27 3:28 ` PROBLEM Adrian Bunk
2003-12-19 18:10 PROBLEM Federico Freire
2003-12-19 18:25 ` PROBLEM Jean-Philippe Woot de Trixhe
2003-12-19 19:29 ` PROBLEM Jose Luis Domingo Lopez
2003-11-30 4:07 PROBLEM Mike Morrell
2003-11-30 6:05 ` PROBLEM Chris Ernst
2003-10-21 13:39 PROBLEM laurent.miaille
2003-03-13 21:40 Problem Smiler
2002-12-31 16:19 Problem Amar Lior
2002-12-31 17:38 ` Problem Hugh Dickins
2002-12-31 16:18 PROBLEM Amar Lior
2002-08-29 19:55 Problem Ryan White
2002-08-14 14:20 PROBLEM Bob Kruger
2001-09-11 23:16 Problem George Lloyd
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=200303091255.h29Ct2aF001120@81-2-122-30.bradfords.org.uk \
--to=john@grabjohn.com \
--cc=fkosa@eposta.hu \
--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;
as well as URLs for NNTP newsgroup(s).