mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: alex@foogod.com
To: Jordan <jordang@pcc.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: can't build small enough zImage for floppy
Date: Sun, 14 Jan 2001 21:34:27 -0800	[thread overview]
Message-ID: <20010114213427.A10734@draco.foogod.com> (raw)
In-Reply-To: <3A5F7BA7.B2FF852B@pcc.net> <20010112152032.C5625@draco.foogod.com> <3A604FF7.EF3D9D51@pcc.net>
In-Reply-To: <3A604FF7.EF3D9D51@pcc.net>

On Sat, Jan 13, 2001 at 06:54:15AM -0600, Jordan wrote:
> alex@foogod.com wrote:
> 
> > I forgot to ask.. when attempting to boot from a floppy, are you using
> > SYSLINUX, or something else?  What version?
> 
> unsure.  I have booted floppies on my machine before which displayed SYSLINUX on
> boot, but the 2.4.0 kernel I compiled (on my Red Hat 6.2 with 2.2.14-5.0 Vaio
> Desktop) and used "make bzdisk" to make the disk, does not display SYSLINUX while
> booting.  It displays
> 
> Loading.........................................
> Uncompressing Linux...
> 
> invalid compressed format (err=21)
> 
> -- System Halted

Ah, this explains it.. the basic bootloader built into the kernel images is 
apparently not compatible with the Z505 (possibly because it doesn't like the 
BIOS emulation done to make the USB floppy look like a traditional floppy 
drive during boot).  I've never attempted this form of booting a kernel 
before, so I hadn't seen this behavior (of course this method also seems to 
have different problems booting on my desktop system, too, so..).  Had you 
managed to make a small enough zImage you would have had the same results.

My advice is to try using SYSLINUX 
(http://www.kernel.org/pub/linux/utils/boot/syslinux/) to load the kernel 
instead of writing it straight to the floppy, as this is known to work on the 
Z505 and is more flexible anyway.

-alex
-
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/

      parent reply	other threads:[~2001-01-15  5:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12 21:48 Jordan
2001-01-12 22:04 ` alex
2001-01-12 22:39 ` Manfred Bartz
2001-01-13  2:04 ` Jens Axboe
     [not found] ` <20010112152032.C5625@draco.foogod.com>
     [not found]   ` <3A604FF7.EF3D9D51@pcc.net>
2001-01-15  5:34     ` alex [this message]

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=20010114213427.A10734@draco.foogod.com \
    --to=alex@foogod.com \
    --cc=jordang@pcc.net \
    --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

all inboxes | Powered by JetHome®