All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Kelsey <mn@midnet.co.uk>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test9-mm3 initrd strangeness
Date: Thu, 13 Nov 2003 13:52:45 +0000	[thread overview]
Message-ID: <20031113135245.128ec5e0.mn@midnet.co.uk> (raw)

This is my first mailing list post so Sorry for any breach of etiquette.

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 

Many Thanx,

Tim Kelsey
Systems Admin, Midland Internet

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-13 13:52 Tim Kelsey [this message]
2003-11-13 14:47 ` 2.6.0-test9-mm3 initrd strangeness Michael Schroeder
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=20031113135245.128ec5e0.mn@midnet.co.uk \
    --to=mn@midnet.co.uk \
    --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.