All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: zImage not supported for 2.2.20?
Date: 28 Dec 2001 18:25:06 -0800	[thread overview]
Message-ID: <a0j9i2$tkr$1@cesium.transmeta.com> (raw)
In-Reply-To: <4.3.2.7.2.20011228124704.00abba70@192.168.124.1> <4.3.2.7.2.20011228173505.00aa3da0@192.168.124.1> <E16K1bW-0001K0-00@the-village.bc.nu> <20011228223604.A370@elektroni.ee.tut.fi>

Followup to:  <20011228223604.A370@elektroni.ee.tut.fi>
By author:    Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi>
In newsgroup: linux.dev.kernel
> 
> Hi, I was one that reported the problem that zImage doesn't work. I don't
> personally care whether it works or not because bzImages are fine for my
> machines. Anyway, 2.2.20pre3 was ok but 2.2.20pre5 was not. I just rechecked
> with 2.2.20 final. I compiled 2.2.20 'make zImage; make bzImage' for one old
> 486 and for one pentium. Both print Out of memory and System halted for the
> zImages and work fine with bzImages.
> 
> 486:
> 
> Memory: 47176k/49152k available (796k kernel code, 408k reserved, 728k data, 44k init)
>    text    data     bss     dec     hex filename
>  853655   90740  125288 1069683  105273 vmlinux
> -rwxr-xr-x    1 kaukasoi users     1111776 Dec 28 21:46 vmlinux
> -rw-r--r--    1 kaukasoi users      458880 Dec 28 21:46 bzImage
> -rw-r--r--    1 kaukasoi users      458877 Dec 28 21:46 zImage
> 
> pentium:
> 
> Memory: 63516k/65536k available (736k kernel code, 416k reserved, 828k data, 40k init)
>    text    data     bss     dec     hex filename
>  788441   90140  105768  984349   f051d vmlinux
> -rwxr-xr-x    1 kaukasoi users     1098107 Dec 28 22:04 vmlinux
> -rw-r--r--    1 kaukasoi users      442277 Dec 28 22:04 bzImage
> -rw-r--r--    1 kaukasoi users      442277 Dec 28 22:04 zImage
> 
> I compiled them with gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2
> release) and binutils 2.11.90.0.19 (tehy are the versions that come with
> Slackware 8.0). The pentium uses LILO version 19 and the 486 uses version
> 21.7-5.
> 
> If you think those are too large kernels for zImage, e.g. this 2.2.19 works
> ok on the 486:
> -rw-r--r--    1 root     root       476269 Aug 11 23:32 zImage
> Memory: 47136k/49152k available (832k kernel code, 412k reserved, 728k data, 44k init)
> -

Machine/motherboard/chipset/BIOS info?

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

  reply	other threads:[~2001-12-29  2:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-28 10:18 zImage not supported for 2.2.20? Roy Hills
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 13:11 ` zImage not supported for 2.2.20? 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-28 17:44   ` Roy Hills
2001-12-28 18:19     ` Alan Cox
2001-12-28 20:36       ` Petri Kaukasoina
2001-12-29  2:25         ` H. Peter Anvin [this message]
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  9:12     ` Roy Hills
2002-01-02  0:54       ` H. Peter Anvin
2001-12-31 12:16     ` Roy Hills
2001-12-31 13:06       ` Petri Kaukasoina
  -- strict thread matches above, loose matches on Subject: below --
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='a0j9i2$tkr$1@cesium.transmeta.com' \
    --to=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.