From: "Kósa Ferenc" <fkosa@eposta.hu>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM
Date: 09 Mar 2003 12:49:55 +0100 [thread overview]
Message-ID: <1047210594.13821.37.camel@daisy> (raw)
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 not
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).
3. Kernel
4. Kernel version: > 2.4.13
5. No Oops..
6. No shell script
7. AMD 5x86, Cyrix 486SLC2 - 4MB RAM 800MB ide hd, 200MB swap, no PCI,
no SCSI, 2 isa eexpress network adapters, 1 serial, 1 parallel ports,
lilo-2.2. boot loader, debian 3.0 stable woody linux
thanks for helping, regards
--
Kósa Ferenc <fkosa@eposta.hu>
next reply other threads:[~2003-03-09 11:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 11:49 Kósa Ferenc [this message]
2003-03-09 12:55 ` PROBLEM John Bradford
-- 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=1047210594.13821.37.camel@daisy \
--to=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