public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Shawn <core@enodev.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2-mm1: Can't mount root
Date: Mon, 28 Jul 2003 14:47:04 -0700	[thread overview]
Message-ID: <20030728144704.49c433bc.akpm@osdl.org> (raw)
In-Reply-To: <1059428584.6146.9.camel@localhost>

Shawn <core@enodev.com> wrote:
>
> I'm using ide=reverse, and my root is on hde5. 2.6.0-test1-mm2 finds my
> root fs fine using the init/do_mounts.c patch posted recently.
> 
> 2.6.0-test2-mm1 (in which said patch seems to have been included),
> however, fails on all of the following root= options:
>       * 2105
>       * /dev/ide/host2/bus0/target0/lun0/part5
>       * /dev/hde5
> 
> I don't know what to try next. Can someone enlighten me as to what has
> been happening lately?

Beats me.  Tried "/dev/hde/5" and "21:05"?

Can you see what this says?

 25-akpm/init/do_mounts.c |    1 +
 1 files changed, 1 insertion(+)

diff -puN init/do_mounts.c~a init/do_mounts.c
--- 25/init/do_mounts.c~a	Mon Jul 28 14:44:37 2003
+++ 25-akpm/init/do_mounts.c	Mon Jul 28 14:44:53 2003
@@ -74,6 +74,7 @@ static dev_t __init try_name(char *name,
 	/*
 	 * The format of dev is now %u:%u -- see print_dev_t()
 	 */
+	printk("scanning `%s'\n", buf);
 	if (sscanf(buf, "%u:%u", &maj, &min) == 2)
 		res = MKDEV(maj, min);
 	else

_

Also take a close look at the dmesg output, make sure that all the devices
and partitions are appearing in the expected places.



  reply	other threads:[~2003-07-28 21:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28 21:43 2.6.0-test2-mm1: Can't mount root Shawn
2003-07-28 21:47 ` Andrew Morton [this message]
2003-07-28 22:06   ` Shawn
2003-07-28 22:02     ` Andrew Morton
2003-07-28 22:39       ` Shawn
2003-07-29  2:04       ` Shawn
2003-07-29  2:36         ` Andrew Morton
2003-07-29  4:44           ` Shawn
2003-07-29  5:32           ` Shawn
2003-07-29  5:47             ` Andrew Morton
2003-07-29  6:14               ` Shawn

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=20030728144704.49c433bc.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=core@enodev.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox