Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with NFS boot
Date: Mon, 3 Dec 2012 09:32:15 +0100	[thread overview]
Message-ID: <20121203093215.2b6d64c6@skate> (raw)
In-Reply-To: <CADKZYYLt90YY8rm4SCuqRN2SsAGqjXhQM7t5hQydpV9o7ZtT+A@mail.gmail.com>

Dear Santhosh Ramani,

On Sat, 1 Dec 2012 19:51:37 -0600, Santhosh Ramani wrote:

> Thank you for your reply, yes I did untar the rootfs.tar.bz2 into the
> folder that is exported as NFS using sudo.
> 
> Note:
> Linux kernel from TI SDK + buildroot rootfs = no nfs (only SD Card)
> Linux kernle from buildroot + buildroot rootfs = everything works fine.

What /dev management solution are you using? Static? Dynamic?

If you're using one of the dynamic solutions (devtmpfs, mdev or udev),
make sure that your kernel is built with CONFIG_DEVTMPFS and
CONFIG_DEVTMPFS_MOUNT. When the kernel is built by Buildroot, Buildroot
automatically enables those options. When your kernel is built
manually, you have to make sure those options are enabled.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2012-12-03  8:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-02  1:51 [Buildroot] Problem with NFS boot Santhosh Ramani
2012-12-02 10:42 ` Stephan Hoffmann
2012-12-03 20:28   ` Santhosh Ramani
2012-12-04  8:33     ` Stephan Hoffmann
2012-12-04 16:21       ` Santhosh Ramani
2012-12-03  8:32 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-12-01 16:38 Santhosh Ramani
2012-12-01 17:19 ` Stephan Hoffmann

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=20121203093215.2b6d64c6@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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