From: Roy Hills <linux-kernel-l@nta-monitor.com>
To: linux-kernel@vger.kernel.org
Subject: zImage not supported for 2.2.20?
Date: Fri, 28 Dec 2001 10:18:20 +0000 [thread overview]
Message-ID: <4.3.2.7.2.20011228101818.00aaa2c0@192.168.124.1> (raw)
I'm using linux kernel 2.2.20 on my systems. This works fine as a
bzImage which most of my systems use, however one of my systems
(a Toshiba Tecra laptop) needs to use zImage, and I find that 2.2.20
does not work in this case, although previous versions e.g. 2.2.17 do.
When I look at the kernels with "file", I notice that the 2.2.20 kernel doesn't
report zImage/bzImage like the older kernels did. 2.2.20 also omits the
system that it was built on and the build date. E.g:
$ file /boot/vmlinuz-2.2.*
/boot/vmlinuz-2.2.19: Linux kernel x86 boot executable bzImage, version
2.2.19
(root@mercury) #7 Fri No, RO-rootFS, root_dev=0x301, Normal VGA
/boot/vmlinuz-2.2.20: Linux kernel x86 boot executable RO-rootFS,
root_dev=0x3
01, Normal VGA
$ file --version
file-3.27
magic data from /etc/magic:/usr/share/misc/magic
I'm running Debian GNU/Linux 2.2r4 (potato) using monolithic kernels compiled
from source.
Is this the end of zImage support, or is there something else different
about the
2.2.20 boot loading process that might be tickling the buggy hardware in my
Tecra?
Regards,
Roy Hills
--
Roy Hills Tel: +44 1634 721855
NTA Monitor Ltd FAX: +44 1634 721844
14 Ashford House, Beaufort Court,
Medway City Estate, Email: Roy.Hills@nta-monitor.com
Rochester, Kent ME2 4FA, UK WWW: http://www.nta-monitor.com/
next reply other threads:[~2001-12-28 10:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 10:18 Roy Hills [this message]
2001-12-28 12:12 ` Matthias Andree
2001-12-28 12:26 ` bug reports for CML2? rpjday
2001-12-28 12:39 ` André Dahlqvist
2001-12-28 17:44 ` zImage not supported for 2.2.20? Roy Hills
2001-12-28 18:19 ` Alan Cox
2001-12-28 20:36 ` Petri Kaukasoina
2001-12-29 2:25 ` H. Peter Anvin
2001-12-29 2:58 ` Alan Cox
2001-12-29 11:01 ` Petri Kaukasoina
2001-12-28 18:36 ` H. Peter Anvin
2001-12-28 19:04 ` Alan Cox
2001-12-28 18:42 ` H. Peter Anvin
2001-12-31 12:16 ` Roy Hills
2001-12-31 13:06 ` Petri Kaukasoina
2001-12-28 13:11 ` Roy Hills
2001-12-28 13:35 ` Matthias Andree
2001-12-28 14:32 ` Petri Kaukasoina
2001-12-28 20:13 ` Wolfgang Erig
2001-12-29 2:23 ` H. Peter Anvin
2002-01-01 15:16 ` Wolfgang Erig
2001-12-31 9:12 ` Roy Hills
2002-01-02 0:54 ` H. Peter Anvin
2001-12-28 21:06 Andries.Brouwer
2001-12-28 21:55 ` H. Peter Anvin
2001-12-28 23:57 ` Alan Cox
2001-12-29 0:01 Andries.Brouwer
2001-12-29 0:17 ` H. Peter Anvin
2001-12-29 0:20 ` 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=4.3.2.7.2.20011228101818.00aaa2c0@192.168.124.1 \
--to=linux-kernel-l@nta-monitor.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
all inboxes | Powered by JetHome®