AW: [Netboot-general] Probs with netboot/NFS

[Gero K. <ge...@gk...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

> -----Urspr=FCngliche Nachricht-----
> [...]
> Kernel command line: auto rw root=3D/dev/nfs nfsroot=3D/nfsroot
> ip=3D192.168.1.18:192.168.1.2:192.168.1.1:255.255.255.0:
> <etc>
> devfs: boot_options: 0x1
> <etc>
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> eepro100.c:v1.09j-t 9/29/99 Donald Becker <url>
> eepro100.c: $Revision: 1.36 $ 2000/11/17 <etc>
> <etc>
> IP-Config: Complete:
> device=3Deth0, addr=3D192.168.1.18, mask=3D255.255.255.0, gw=3D192.168.=
1.1,
> host=3D192.168.1.18, domain=3D, nis-domain=3D(none),
> bootserver=3D192.168.1.2, rootserver=3D192.168.1.2, rootpath=3D
> <etc>
> RAMDISK: cramfs filesystem found at block 0
> RAMDISK: loading 1156 blocks [1 disk] into ram disk... done
> <etc>
> Kernel panic: VFS: Unable to mount root fs on 00:ff
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> (note nothing set after "rootpath" in the IP-Config bit)

Automounting a root-NFS file system is a two-step process: first the
kernel has to configure the network interface, and then it has to call
the NFS code to actually mount the root directory. Configuration of the
network interface is done using the "ip=3D" command line option. If this
option is missing, the kernel sends out its own DHCP/BOOTP/RARP requests
to configure the interface, and it then sets the "rootpath" using the
information it got from the server. In your case, the bootrom already
did all that BOOTP thing, and passed a valid "ip=3D" option to the kernel.
The kernel therefore had no need to start DHCP itself, and therefore the
"rootpath" value in the debugging output is empty. This is OK, and your
network interface has been setup correctly.
The second step involves mounting the NFS root directory. The name of
the directory is taken from the "nfsroot=3D" command line option, which
has also been passed correctly by the bootrom process. Unfortunately, you
did not give us any kernel output which relates to the NFS step. I there-
fore assume that you did not compile your kernel using nfsroot support.
Please check for the CONFIG_ROOT_NFS variable being set in your kernel
configuration file (/usr/src/linux/.config). Set this to "y" and recompil=
e
the kernel.

> [...]
> The command I used to make the .nbi file is:
>
> mknbi-linux -x -d /nfsroot -i rom -r initrd.img-2.4.32.img -k bzImage -=
o
> bootImage.nbi

With this command line you specify the root directory explicitely. You
can also use "-d rom" to the let the bootrom set the root directory
according to the information in the BOOTP/DHCP response.

Please let me know if this answer did not solve your problem.

gero.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFDq9hA8f/CfZ6W4egRAlprAJ9rJ1YOgRQGe9qSsJOT/KXPSDkkFQCgjbvx
XhhiYhHkK5XQlVF5L8Y2rvk=3D
=3D7qXe
-----END PGP SIGNATURE-----