From: Tom Felker <tcfelker@mtco.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: root= needs hex in 2.6.0-test1-mm2
Date: Wed, 23 Jul 2003 13:52:54 -0500 [thread overview]
Message-ID: <200307231352.54208.tcfelker@mtco.com> (raw)
In-Reply-To: <200307240133.36646.kernel@kolivas.org>
On Wednesday 23 July 2003 10:33 am, Con Kolivas wrote:
> On Wed, 23 Jul 2003 23:43, Christoph Hellwig wrote:
> > On Wed, Jul 23, 2003 at 01:56:40AM -0500, Tom Felker wrote:
> > > I finally booted 2.6.0-test1-mm2, after reading somebody else who
> > > needed to use hex in the root= argument. root=/dev/hdb1 and root=hdb2
> > > would panic ("VFS: Cannot open root device hdb1 or
> > > unknown-block(0,0)"), but root=0341 worked. Devfs is compiled in,
> > > devfs=nomount and devfs=mount make no difference. Is this intentional?
> >
> > Yes. If you use devfs you have to use devfs names for root=. It's
> > pretty simple. Best option of course is to avoid devfs.
>From the perspective of an ignorant user, I kinda like the idea of devfs.
> ie use
>
> root=/dev/ide/host0/bus0/target1/lun0/part1
>
> or equivalent
Yes, this worked. I guess now my question is, why does /dev/hdb1 work for
2.6.0-test1, but not 2.6.0-test1-mm2?
Also, I just started getting oopses during startup and shutdown with
test1-mm2, EIP at ext3_journaling_dirty_data or something similar, followed
by a bunch of file not found errors. I'm getting scared, I have valuable
data on ext3. I'll be looking into some way to capture this.
--
Tom Felker
Hack user friendliness onto a pure and simple system, because
you can't hack purity and simplicity onto a user friendly system.
prev parent reply other threads:[~2003-07-23 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 6:56 root= needs hex in 2.6.0-test1-mm2 Tom Felker
2003-07-23 12:20 ` Felipe Alfaro Solana
2003-07-23 15:06 ` Florian Huber
2003-07-23 15:48 ` Charles Lepple
2003-07-23 13:43 ` Christoph Hellwig
2003-07-23 15:08 ` Felipe Alfaro Solana
2003-07-23 18:17 ` Diego Calleja García
2003-07-23 19:30 ` Steven Cole
2003-07-23 15:33 ` Con Kolivas
2003-07-23 18:52 ` Tom Felker [this message]
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=200307231352.54208.tcfelker@mtco.com \
--to=tcfelker@mtco.com \
--cc=kernel@kolivas.org \
--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;
as well as URLs for NNTP newsgroup(s).