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: Fri, 12 Jan 2001 14:04:11 -0800 [thread overview]
Message-ID: <20010112140411.B5625@draco.foogod.com> (raw)
In-Reply-To: <3A5F7BA7.B2FF852B@pcc.net>
In-Reply-To: <3A5F7BA7.B2FF852B@pcc.net>
On Fri, Jan 12, 2001 at 03:48:23PM -0600, Jordan wrote:
> 1st, the Sony Vaio Z505HS appears to be an example of a machine which
> will not boot a bzImage correctly, compaining about the compression
> format.
I can say from experience that this is not the case. In fact, the kernel
binaries (RPM) I provide on my Z505 page (http://www.foogod.com/z505_linux) are
bzImages (currently those are still test5, though I have used later ones on my
own machine as well, and will probably be upgrading the page to 2.4.0 final
eventually). I will admit that I haven't tried booting them from a floppy..
perhaps this is where the problem lies.
The Z505HS does have a USB floppy drive, which is the only thing I can think
of that's different from most other machines which might affect this, but I do
know that that doesn't stop a 2.2 kernel from booting off of it (though there
are problems accessing the floppy after the initial boot without USB drivers,
of course)
I will look into building a 2.4.0 floppy-bootable kernel on my Z505 and see if
I can reproduce the problems you're having.
-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/
next prev parent reply other threads:[~2001-01-12 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 21:48 can't build small enough zImage for floppy Jordan
2001-01-12 22:04 ` alex [this message]
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
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=20010112140411.B5625@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