mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: zImage not supported for 2.2.20?
Date: Fri, 28 Dec 2001 16:32:50 +0200	[thread overview]
Message-ID: <20011228163250.A31791@elektroni.ee.tut.fi> (raw)
In-Reply-To: <4.3.2.7.2.20011228101818.00aaa2c0@192.168.124.1> <4.3.2.7.2.20011228101818.00aaa2c0@192.168.124.1> <20011228121228.GA9920@emma1.emma.line.org> <4.3.2.7.2.20011228124704.00abba70@192.168.124.1>
In-Reply-To: <4.3.2.7.2.20011228124704.00abba70@192.168.124.1>; from linux-kernel-l@nta-monitor.com on Fri, Dec 28, 2001 at 01:11:42PM +0000

On Fri, Dec 28, 2001 at 01:11:42PM +0000, Roy Hills wrote:
> The old 2.2.17 zImage kernel that runs fine has a filesize of 462060 bytes and
> reports 784k kernel code, 412k reserved, 1168k data, 36k init.
> 
> The new 2.2.20 zImage kernel that fails has a filesize of 482795 bytes.
> Note that the actual problem with Toshiba tecra laptops and bzImage files is
> a known hardware problem (something to do with the A20 line).  I'm not trying
> to address this problem, just why the normal workaround (use zImage rather
> than bzImage to keep in conventional memory) doesn't work any more with
> 2.2.20.

Hi, I used to make zImages, but for no specific reason. The last working
version was 2.2.20pre3. 2.2.20pre5 gave Out of memory -- System halted. I
reported it a few months ago:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0108.2/0363.html

This was the only change then that looks like it:

o       Add support for the 2.4 boot extensions to 2.2  (H Peter Anvin)

  parent reply	other threads:[~2001-12-28 14:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-28 10:18 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 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 [this message]
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=20011228163250.A31791@elektroni.ee.tut.fi \
    --to=kaukasoi@elektroni.ee.tut.fi \
    --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®