mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "John Z. Bohach" <jzb@aexorsyst.com>
To: linux-kernel@vger.kernel.org
Subject: root=/dev/sda1 fails but root=0x0801 works...
Date: Mon, 13 Feb 2006 23:16:15 -0800	[thread overview]
Message-ID: <200602132316.15992.jzb@aexorsyst.com> (raw)

This is probably a question with an obvious answer, but I haven't found it
elsewhere, so I hope its okay if I ask here...

As the subject says, if I have my kernel command line with
'...root=/dev/sda1...' then I get

VFS: Cannot open root device "sda1" or unknown-block(0,0)

however, everything else being the same, if I have
'...root=0x0801...', then it works fine.  Note that 

SCSI device sda: 2001888 512-byte hdwr sectors (1025 MB)
sda: Write Protect is off
sda: assuming drive cache: write through
 sda: sda1
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0

preceeds this in the console both for the failed case and the succeeding case
(as I already have the rootdelay=10 param. on the command line as well).

I've narrowed this down to another CONFIG_* option, but I can't find which
one in tractable time...

Does anybody know which CONFIG_* option might contribute to text string
root=/dev/sda1 failing while its root=0x0801 cousin works?  I've already tried the
CONFIG_KALLSYMS one, but no luck.  Would this possibly have to do with
CONFIG_NLS=m (et al),  as I have those as modules, and if so, is this intentional?

Thanks,
John


-- 
     ###  Any similarity between my views and the truth is completely ###
     ###  coincidental, except that they are endorsed by NO ONE       ###


             reply	other threads:[~2006-02-14  7:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-14  7:16 John Z. Bohach [this message]
2006-02-14 15:42 ` Phillip Susi
2006-02-14 16:24   ` Al Viro
2006-02-14 17:20     ` John Z. Bohach
2006-02-14 19:03       ` Phillip Susi
2006-02-15  6:59     ` Andrew Morton
2006-02-15  7:10       ` Al Viro
2006-02-15  7:32         ` Andrew Morton
2006-02-15  7:59           ` Al Viro

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=200602132316.15992.jzb@aexorsyst.com \
    --to=jzb@aexorsyst.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

Powered by JetHome