From: Scott Wood <scottwood@freescale.com>
To: Andre Haupt <haupt.andre@gmx.de>
Cc: kernelnewbies@nl.linux.org, linuxppc-embedded@ozlabs.org,
Manjunath AM <Manjunath.AM@Lntemsys.com>
Subject: Re: nfs mounting problem
Date: Tue, 23 Jan 2007 09:32:55 -0600 [thread overview]
Message-ID: <45B62AA7.4020306@freescale.com> (raw)
In-Reply-To: <45B61459.1030507@gmx.de>
Andre Haupt wrote:
> Also what seems a bit odd to me is that your dmesg shows no rootpath
>
> IP-Config: Complete:
> device=eth1, addr=192.168.178.234, mask=255.255.255.0,
> gw=192.168.178.47,
> host=cashel, domain=, nis-domain=(none),
> bootserver=192.168.178.110, rootserver=192.168.178.110, rootpath=
>
> On my system the complete root path is printed here.
I don't think I've ever seen the root path printed there (with nfsroot
otherwise working), so I don't think that's the problem... From looking
at the code, it seems that the root path received from BOOTP is stored
in a different variable than the path from the nfsroot boot option, and
it's the former that gets printed there.
To Manjunath AM: does the ethernet work from U-Boot? Can you verify
that packets are being successfully sent and received under Linux? If
the only variable is the board, then the problem is probably not with
NFS itself; there's probably something different in how the ethernet is
hooked up on your board, or in how the board is being initialized.
-Scott
next prev parent reply other threads:[~2007-01-23 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 12:33 nfs mounting problem Manjunath AM
2007-01-23 12:59 ` Andre Haupt
2007-01-23 13:23 ` Manjunath AM
2007-01-23 13:57 ` Andre Haupt
2007-01-23 15:32 ` Scott Wood [this message]
2007-01-24 8:10 ` Andre Haupt
2007-01-30 18:41 ` Manjunath AM
2007-10-12 9:13 ` Abhijit Naik
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=45B62AA7.4020306@freescale.com \
--to=scottwood@freescale.com \
--cc=Manjunath.AM@Lntemsys.com \
--cc=haupt.andre@gmx.de \
--cc=kernelnewbies@nl.linux.org \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.