public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Edgar Toernig <froese@gmx.de>
To: DervishD <raul@pleyades.net>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Unable to boot a raw kernel image :??
Date: Fri, 06 Dec 2002 12:45:20 +0100	[thread overview]
Message-ID: <3DF08DD0.BA70DA62@gmx.de> (raw)
In-Reply-To: 20021129132126.GA102@DervishD

DervishD wrote:
> 
>     Hi all :))
> 
>     A time ago I was able to generate bootable Linux CD's just by
> dd'ing a floppy containing a raw kernel image:
> 
>     dd if=/dev/fd0 of=eltorito
> 
>     After that, mkisofsing, toasting and booting. But now, depending
> on the machine, I have 'invalid compressed format' errors, or even
> ye olde register dump when the image was damaged :(
> 
>     Booting directly from the floppy works, but booting with that
> same image from a CD does not :(( I now I can use LILO, or better
> yet, Syslinux or isolinux, but I'm just curious why I cannot boot raw
> image-based CD's anymore.
> 
>     Anyone knows what's happenning here?

I had this problem a while ago.  It turned out to be a (widespread)
BIOS bug triggered be the disk-size probe of the kernel's boot loader.

The crude fix which worked for me: disable the probing for 2.88MB disks
by changing the first byte of the disksizes table at the end of bootsect.S
from 36 to 18.

The long explanation: The BIOS allows bigger-than-track-size reads
in El-Torito mode which confuses the probe routine which then assumes
a 2.88MB disk when the BIOS is actually emulating a 1.44MB disk.
In LBA mode that would be no problem but in CHS mode (which is used
by the loader) it does not work.

Ciao, ET.

  parent reply	other threads:[~2002-12-06 11:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29 13:21 Unable to boot a raw kernel image :?? DervishD
2002-12-03 11:29 ` Denis Vlasenko
2002-12-08 10:33   ` DervishD
2002-12-06 11:45 ` Edgar Toernig [this message]
2002-12-08 10:36   ` DervishD
2003-03-05 15:00   ` H. Peter Anvin
2003-03-05 15:33     ` Mikael Pettersson
2003-03-05 15:47       ` H. Peter Anvin
2003-03-05 15:58         ` Mikael Pettersson
2003-03-05 16:02           ` H. Peter Anvin
2003-03-05 16:05             ` Mikael Pettersson
2003-03-06 10:16             ` Mikael Pettersson
2003-03-06 20:28               ` H. Peter Anvin
2003-03-09 10:31                 ` DervishD
2003-03-10 19:38                   ` H. Peter Anvin
2003-03-11  9:23                     ` DervishD
2003-03-05 16:12     ` DervishD
2003-03-05 16:33       ` John Bradford
2003-03-05 16:48         ` H. Peter Anvin
2003-03-05 16:55           ` John Bradford
2003-03-05 17:01         ` DervishD
2003-03-05 18:04           ` John Bradford
2003-03-05 16:51       ` H. Peter Anvin
2003-03-05 17:04         ` DervishD
2003-03-05 17:51           ` H. Peter Anvin
2003-03-06  1:08         ` Alan Cox
2003-03-06  0:30           ` H. Peter Anvin

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=3DF08DD0.BA70DA62@gmx.de \
    --to=froese@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raul@pleyades.net \
    /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