From: "Haven Skys" <hskys@frontbridge.com>
To: "'Matthias-Christian Ott'" <matthias.christian@tiscali.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Help: kernel option root=/dev/nfs failing 2.6.10
Date: Wed, 16 Feb 2005 12:02:08 -0800 [thread overview]
Message-ID: <005c01c51462$656c8b10$2401a8c0@internal.bigfish.com> (raw)
In-Reply-To: <42139A3D.2020202@tiscali.de>
Thanks. Yes I have.
Here are a couple configuration options I have set:
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_ROOT_NFS=y
Everything is textbook really. I followed several different examples and
still nothing works.
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Matthias-Christian
Ott
Sent: Wednesday, February 16, 2005 11:09 AM
To: Haven Skys
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help: kernel option root=/dev/nfs failing 2.6.10
Haven Skys wrote:
>I am attempting to create network bootable system with 2.6.10 and nfs and
am
>having trouble.
>
>I am using grub and the boot goes without a hitch until the kernel attempts
>to use the commands I've sent.
>
><SNIP from grub.conf>
>bootp
>root (nd)
>kernel (nd)/redhat-2.6.10/kernel root=/dev/nfs ip=bootp
>nfsroot=10.0.120.1:/diskless/redhat-2.6.10/
>baseos
></SNIP>
>
>Network booting machine X does fine until. It attempts to open the root
>device.
>
><SNIP>
>VFS: Cannot open root device "nfs" or unknown-block(0,255) Please append a
>correct "root=" boot option Kernel panic - not syncing: VFS: Unable to
mount
>root fs on unknown-block(0,255) </SNIP>
>
>It looks like the kernel isn't recognizing the virtual device /dev/nfs but
>I've enabled all the NFS options and everything is compiled into the
kernel.
>
>Any ideas?
>
>
>Thanks
>Haven
>
>
>
>
>
>
>FrontBridge introduces Message Archive and Secure Email. Get leading
Enterprise Message Security services from FrontBridge. www.frontbridge.com.
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
>
>
>
Hi!
I did you follow the "tutorial" in Documentation/nfsroot.txt?
Matthias-Christian Ott
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
FrontBridge introduces Message Archive and Secure Email. Get leading Enterprise Message Security services from FrontBridge. www.frontbridge.com.
next prev parent reply other threads:[~2005-02-16 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 18:05 Help: kernel option root=/dev/nfs failing 2.6.10 Haven Skys
2005-02-16 19:08 ` Matthias-Christian Ott
2005-02-16 20:02 ` Haven Skys [this message]
2005-02-16 20:43 ` Matthias-Christian Ott
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='005c01c51462$656c8b10$2401a8c0@internal.bigfish.com' \
--to=hskys@frontbridge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.christian@tiscali.de \
/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