From: Miles Lane <miles@megapathdsl.net>
To: rob@sysgo.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Anybody got 2.4.0 running on a 386 ?
Date: Tue, 09 Jan 2001 17:48:10 -0800 [thread overview]
Message-ID: <3A5BBF5A.7030103@megapathdsl.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0101100527220.23018-100000@bee.lk> <01011000420402.03050@rob>
Hi Rob,
Just out of curiosity, did you use a 2.2 series
.config file and then run make oldconfig or did
you build a new .config file from scratch?
I have periodically built kernels that crashed
immediately at the point you mention. Usually this
was due to me choose configuration options that
were incompatible with my machine's hardware.
Another time, the machine wouldn't boot because
I needed a new version of LILO. I also have seen
at least one machine where I needed to specify
"linear" as one of the options in lilo.conf.
If you aren't specifying "linear" now, give it
a try.
IIRC, here's my litany of goofed configurations:
Building support for multiple framebuffer
devices. Apparently, the kernel would
hang in the chip detection process.
Wrong CPU architecture.
Wrong IDE chipset specified.
Built EXT2 as a module, but / was on
an EXT2 partition.
I may have hit some other bogus configurations
over the last two years, but these are ones that
come to mind.
Miles
-
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 prev parent reply other threads:[~2001-01-10 1:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 20:53 Robert Kaiser
2001-01-09 21:15 ` Brian Gerst
2001-01-09 21:17 ` Robert Kaiser
2001-01-09 21:46 ` Brian Gerst
2001-01-09 22:17 ` Robert Kaiser
2001-01-09 22:57 ` Ingo Molnar
2001-01-09 23:44 ` Robert Kaiser
2001-01-10 0:19 ` Alex Buell
2001-01-10 0:20 ` Ingo Molnar
2001-01-10 0:24 ` Ingo Molnar
2001-01-10 16:00 ` Robert Kaiser
2001-01-10 21:29 ` Tom G. Christensen
2001-01-10 22:04 ` X performance on 2.4.0 v.s. 2.4.0-test12 Alan Olsen
2001-01-09 23:03 ` Anybody got 2.4.0 running on a 386 ? Brian Gerst
2001-01-09 23:04 ` Robert Kaiser
2001-01-09 23:28 ` Anuradha Ratnaweera
2001-01-09 23:42 ` Robert Kaiser
2001-01-10 1:48 ` Miles Lane [this message]
2001-01-10 15:25 ` Robert Kaiser
2001-01-10 21:04 ` Miles Lane
2001-01-10 16:28 ` Paul Gortmaker
2001-01-15 18:38 ` [SOLVED + PATCH] " Robert Kaiser
2001-01-15 19:11 ` Linus Torvalds
2001-01-09 22:44 ` Timur Tabi
2001-01-09 21:59 ` Brian Gerst
2001-01-10 19:51 ` mo6
2001-01-10 20:18 ` Brian Gerst
2001-01-10 21:53 ` mo6
2001-01-11 12:20 ` mo6
2001-01-10 3:53 ` Tom Leete
2001-01-10 9:25 richardj_moore
2001-01-10 14:19 ` Alan Cox
2001-01-10 15:04 ` Robert Kaiser
2001-01-10 15:49 ` Alan Cox
2001-01-10 16:02 ` Robert Kaiser
[not found] <Pine.LNX.4.04.10101101000130.27018-100000@hantana.pdn.ac.lk>
2001-01-10 15:37 ` Robert Kaiser
2001-01-10 17:16 Petr Vandrovec
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=3A5BBF5A.7030103@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@sysgo.de \
/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
Powered by JetHome