OpenWrt Forum Archive

Topic: Problem with buildroot in openwrt Kamikaze - cant build nfsroot image

The content of this topic has been archived on 6 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi All,

To speed up my work on the final OpenWRT image for my Asus WL500Gp v2 (and to avoid continuous reflashing ;-) ), I need to prepare a system capable to boot from the network and to operate on a NFS mounted root filesystem.

The procedure is quite easy:
* Connect the UART cable
* Press the RESTORE button
* Power up (while holding the RESTORE buton)
* kill the TFPT client (by CTRL+C from terminal)
* Configure the NIC: CFE> ifconfig eth0 -addr=172.17.1.6
* Boot the kernel via TFTP: CFE> boot -elf 172.17.1.1:vmlinux.elf

However the problem is, that I'm not able to compile the NFS-enabled kernel.

I need to compile the NFS support into the kernel, and to modify the CONFIG_CMDLINE to
CONFIG_CMDLINE="root=/dev/nfs nfsroot=172.17.1.1:/usr/local/nfs/asus init=/etc/preinit noinitrd console=ttyS0,115200 ip=dhcp"

I have tried to follow the instructions found in http://wiki.openwrt.org/BuildRoot , section "Customizing the kernel options".
When I do "make ARCH=mips menuconfig" in trunk/build_dir/linux-brcm47xx/linux-2.6.25.17 everything seems to be OK in the .config file.

However, when I run the "make" in the top ("trunk") directory, the previous contents of the .config is somehow magically restored...
(at least the "CONFIG_NFS_FS=y" gets replaced with "# CONFIG_NFS_FS is not set").

What do I wrong?
--
TIA, WZab

(Last edited by wzab on 13 Oct 2008, 00:16)

Oooops, I think I've found the solution.
I've generated the docs in the trunk, and in openwrt.pdf I've found the following:

If you want, you can also modify the kernel config for the selected target sys-
tem. simply run "make kernel_menuconfig" and the build system will unpack
the kernel sources (if necessary), run menuconfig inside of the kernel tree, and
then copy the kernel config to target/linux/<platform> /config so that it is
preserved over "make clean" calls.

So, sorry for confusion...

The discussion might have continued from here.