Re: 2.6.0-test9-mm3 initrd strangeness

[Tim Kelsey]

Thanx,

My image was too big, i have now changed the initrd size in the kernel config as you said and it works perfectly now.

Thanx very much for your help

Tim Kelsey

On Thu, 13 Nov 2003 15:47:38 +0100
Michael Schroeder <mls@xxxxxxx> wrote:

> On Thu, Nov 13, 2003 at 01:52:45PM +0000, Tim Kelsey wrote:
> > I am experiencing problems with 2.6.0-test9-mm3 and initrd ramdisks
> > I have support for ramdisks and initrd compiled directly into the kernel and have an initrd image gzipped and placed in /boot called initrd-crypt.gz
> > 
> > When booting off a 2.4.22 kernel the image is loaded and linuxrc is executed perfectly but with a 2.6.0-test9-mm3 kernel i get the following msg at boot time
> > 
> > 	RAMDISK: Compressed image found at block 0
> > 	RAMDISK: incomplete Write (-1 != 32768) 4194304
> > 
> > Any comments, advice, opinions greatly appreciated also if someone could explain what those numbers actually mean i would be very grateful 
> 
> Seems like your ramdisk is full, the default size is 4096k.
> Change the CONFIG_BLK_DEV_RAM_SIZE parameter or boot with
> ramdisk_size=<value>.
> 
> Cheers,
>   Michael.
> 
> -- 
> Michael Schroeder                                   mls@xxxxxxx
> main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/