linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Amit D Chaudhary <amitc@brocade.com>
To: "'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: root=/dev/ram0
Date: Fri, 27 Jul 2001 12:53:14 -0700	[thread overview]
Message-ID: <3B61C6AA.9030400@brocade.com> (raw)
In-Reply-To: 3B616383.E539C269@seranoa.com


Interesting, try the following,
Don't specify root= anywhere including kernel cmdline

in your initrd, ensure thet there is a symlink /linuxrc to /bin/sh(or
equivalent).

Amit

Andrew Dixon wrote:

> Amit D Chaudhary wrote:
>
>>Hi,
>>
>>Can you give the following details,
>>Are you trying to load it as initrd? Not I assume, else confirm that
>>CONFIG_BLK_DEV_INITRD=y
>>
>
> I am trying to load it as initrd.
>
> andrew.dixon@pig2:/usr/src/linux$ cat .config |grep
> CONFIG_BLK_DEV_INITRD
> CONFIG_BLK_DEV_INITRD=y
>
> And this is set up correctly in the kernel.  Just to make sure that my
> configuration was a workable solution I recompiled everything for an i86
> architecture and I tried it out on my laptop.  I put my compressed
> ramdisk image and kernel onto a floppy and used ldlinux.sys as a boot
> loader passing it the command:
>
> 	root=/dev/ram0 initrd=fs.gz
>
> and it works fine.  This prompted me to do a little searching through
> the ramdisk source (/usr/src/linux/drivers/block/rd.c) and I found that
> the ramdisk expects to find the ramdisk image on the floppy drive:
>
> 	if (MAJOR(ROOT_DEV) != FLOPPY_MAJOR
> #ifdef CONFIG_BLK_DEV_INITRD
> 		&& MAJOR(real_root_dev) != FLOPPY_MAJOR
> #endif
> 	)
> 	  //ADD
> 	  //we don't want to return here because our real_root_dev is not the
> 	  //floppy but the disk or flash device.  Right?  Right!
> 	  //		return;
>
>
> It still doesn't work but I've got that feeling that I'm getting
> closer.  I'm going to make sure that the hard disk is detected before
> the ramdisk tries to load the image
>
> later,
> Andy
>
> P.S. Do people on the list like to be cc'd on responses or should I keep
> all mail to the list only?
>
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-07-27 19:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-26 20:02 root=/dev/ram0 Andrew Dixon
2001-07-26 20:45 ` root=/dev/ram0 Paul Ruhland
2001-07-26 21:33   ` root=/dev/ram0 Andrew Dixon
2001-07-26 22:13     ` root=/dev/ram0 Rey Estrada
2001-07-27  3:01     ` root=/dev/ram0 Amit D Chaudhary
2001-07-27 12:50       ` root=/dev/ram0 Andrew Dixon
2001-07-27 19:53         ` Amit D Chaudhary [this message]
2001-07-27  6:52 ` root=/dev/ram0 Peter Ryser

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=3B61C6AA.9030400@brocade.com \
    --to=amitc@brocade.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).