From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
To: DragonK <dragon_krome@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel 2.4.x Bug
Date: Wed, 25 Sep 2002 10:04:05 -0200 [thread overview]
Message-ID: <200209250709.g8P79ip29724@Port.imtp.ilyichevsk.odessa.ua> (raw)
In-Reply-To: <20020924213421.22776.qmail@web20307.mail.yahoo.com>
On 24 September 2002 19:34, DragonK wrote:
> I'm sorry if I'm sending this to the wrong persons,
> but I really don't know whom I should send this to.
>
> My problem involves ALL linux kernels 2.4.x. All
> versions I've tried on my machine lock up at boot time
> (no panic, no oops, just plain old dead), just after
> writing "Uncompressing linux kernel...Ok, now booting
> the kernel...". The kernel banner DOES NOT appear. I
> compiled every kernel with a minimal set of options
> (and CPU=386) but nothing; I've even installed the
> latest Lilo.
I'd compile 2.2 and 2.4 kernels with most conservative settings,
put them on a diskettes and try at several PCs.
No, not a full Linux, just a kernel.
That way you can collect some data as to which PCs do
not like 2.4
Also you can stick debugging in the early boot stages
and investigate.
<shameless plug>
If you have/can install DOS, you may use this bootloader
for debugging. It is small and source is easy to understand
(I hope)
http://www.imtp.ilyichevsk.odessa.ua/linux/vda/linld/
You need *devel.tar* file only if you don't have Borland C,
otherwise take much smaller linld095.tar.bz2
</shameless plug>
--
vda
next prev parent reply other threads:[~2002-09-25 7:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 21:34 Linux Kernel 2.4.x Bug DragonK
2002-09-25 12:04 ` Denis Vlasenko [this message]
2002-09-25 13:07 ` Phil Auld
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=200209250709.g8P79ip29724@Port.imtp.ilyichevsk.odessa.ua \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=dragon_krome@yahoo.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 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).