From: joy <gracecott@sancharnet.in>
To: linux-newbie@vger.kernel.org
Subject: kernel error?
Date: Mon, 29 Dec 2003 22:01:40 +0530 [thread overview]
Message-ID: <3FF056EC.6020002@sancharnet.in> (raw)
Hi,
I just compiled my new 2.6 kernel and when I boot thru it, I get an
error saying:
VFS : cannot open root device "345" or unknown-block (3,69)
OK.so I give an argument roo=/dev/hdb5 (that's my root partiton, I get
the message
VFS : cannot open root device "hdb5" or unknown-block (0,0)
anyone with an answer?
My old kernel worked fine w/o any lilo args.
and used to refer to my hdd as (03:05) when I had it as hda.
Thanks in advance,
deadhead.
--------------------------------------------------------------------------------------------------------
A life without purpose is like a bird that never learnt to fly.......
I am the bird that regularly flies Lufthansa
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next reply other threads:[~2003-12-29 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 16:31 joy [this message]
2004-01-01 21:59 ` kernel error? Eric
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=3FF056EC.6020002@sancharnet.in \
--to=gracecott@sancharnet.in \
--cc=linux-newbie@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