public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Cengiz Akinli <cengiz@drtalus.aoe.vt.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x kernels hang before uncompressing
Date: Tue, 11 Jun 2002 17:17:24 +0200	[thread overview]
Message-ID: <3D061484.3030903@loewe-komp.de> (raw)
In-Reply-To: <200206111436.g5BEa4Z17577@drtalus.aoe.vt.edu>

Cengiz Akinli wrote:
> Hello all,
> 
>    We have a Tri-M PC-104 system with a Cyrix ZF486 processor that (in
> addition to being painfully slow building kernels) refuses to boot any
> 2.4.x kernels.  It has a M-Systems Disk-On-Chip 2000 (which ironically,
> I got to work just fine with the 2.2.x kernel that I had to patch, but
> NOT with the 2.4 kernel that comes with a driver), but I don't think that's
> the problem, because the 2.4.x kernel is not even uncompressing, to say
> nothing of booting and trying to mount the root fs.
> 
>   It DOES appear to finish loading, because it outputs a linefeed after
> the line of dots in 'Loading linux....'
> 
[..]
>   The lilo used to install the boot sector on this Disk On Chip is
> a custom-patched one provided by the vendor.  It works fine on 2.2.x
> kernels.  Should I suspect it?
> 

Perhaps the patched lilo can't cope with bzImage - only zImage?
only a cheap guess

Did you try to compile the kernel as i386?


  reply	other threads:[~2002-06-11 15:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-11 14:36 2.4.x kernels hang before uncompressing Cengiz Akinli
2002-06-11 15:17 ` Peter Wächtler [this message]
2002-06-11 17:31 ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2002-06-12 10:13 Jon Burgess

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=3D061484.3030903@loewe-komp.de \
    --to=pwaechtler@loewe-komp.de \
    --cc=cengiz@drtalus.aoe.vt.edu \
    --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