lkml.org 
[lkml]   [2001]   [Aug]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.2.20pre series and booting problem
On Fri, Aug 17, 2001 at 08:16:29AM +0300, Petri Kaukasoina wrote:
> On Thu, Aug 16, 2001 at 04:35:23PM -0700, Tim Moore wrote:
> > Petri Kaukasoina wrote:
> > >
> > > 2.2.20pre3 boots ok but pre5-pre9 do not:
> > >
> > > Uncompressing Linux...
> > >
> > > Out of memory
> > >
> > > -- System halted
> > >
>
> > make bzimage?
>
> Yes, both zImage and bzImage gave the same error. (I should have mentioned
> that, sorry.)

I was wrong. I must have made a mistake when I tried bzImage because now it
works.

Up to 2.2.20pre3 zImage works ok. After that it doesn't work any longer, but
bzImage does.

For example this is a 2.2.19 zImage

-rw-r--r-- 1 root root 476269 Aug 11 23:32 vmlinuz-2.2.19

which reports its size like this

Memory: 47136k/49152k available (832k kernel code, 412k reserved, 728k data, 44k init)

A 2.2.20pre9 built from the same .config doesn't boot from a zImage (tells
Out of memory) but boots up ok from a bzImage. Its size is the same as above:

Memory: 47136k/49152k available (832k kernel code, 412k reserved, 728k data, 44k init)

When I leave almost everything out of .config, I get this minimal kernel:

-rw-r--r-- 1 kaukasoi users 261818 Aug 17 20:01 zImage

which reports this

Memory: 47612k/49152k available (428k kernel code, 412k reserved, 668k data, 32k init)

Even then zImage tells 'Out of memory' but bzImage boots up ok. So it seems
that zImages don't work any longer.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:57    [W:0.047 / U:5.676 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site