public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Schroeder <mls@suse.de>
To: Tim Kelsey <mn@midnet.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test9-mm3 initrd strangeness
Date: Thu, 13 Nov 2003 15:47:38 +0100	[thread overview]
Message-ID: <20031113144738.GA18329@suse.de> (raw)
In-Reply-To: <20031113135245.128ec5e0.mn@midnet.co.uk>

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@suse.de
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}

  reply	other threads:[~2003-11-13 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-13 13:52 2.6.0-test9-mm3 initrd strangeness Tim Kelsey
2003-11-13 14:47 ` Michael Schroeder [this message]
2003-11-13 15:43   ` Tim Kelsey

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=20031113144738.GA18329@suse.de \
    --to=mls@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mn@midnet.co.uk \
    /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