I'm attempting to get 0.21.0-62b5 booting via NFS. I've had minimyth booting via NFS on another frontend before, so somewhat familiar with the setup process.
The PXE process goes fine, initial dhcp works, kernel loads but during the second DHCP process something goes wrong with messages as below;
INIT: version 2.86 booting
usbcore: registered blah...
usbcore: registered blah...
nfs: server 192.168.5.12 not responding, still trying
nfs: server 192.168.5.12 not responding, still trying
And it stops there. The NFS/BOOTP/DHCP server is on the 192.168.5.0/24 subnet and the client is on the 192.168.1.0/24 subnet. I've got the router forwarding DHCP request from the .1 to the .5 network correctly. Here is what I know and have tried;
- PXE works fine, I've got another LTSP client booting off the same sever from the .1 network;
- NFS server/exports are correct as I can mount the /export/minimyth-0.21.0-62b5 roofs correctly from another linux machine on the .1 network;
- I can change pxelinux.cfg/default file to load the ramdisk image version with 0.21.0-62b5 and this boots correctly (but takes a much longer time, hence nfs preference);
- I can get minimyth-0.21.0-58 nfs booting correctly with exactly two changes to the current config with the same setup, the pxelinux.cfg/default preference and the DHCP "root disk path" to point to /export/minimyth-0.21.0-58 instead;
- with 0.21.0-62b5 nfs, the client is pingable from the .1 network once its stuck but not from the .5 network(hence why it can't reach the nfs server to contonue), which leads me to believe the default gw/netmask is not being set correctly during the second DHCP, but I have no way to verify this on the client once it's stuck (can't telnet etc), but DHCP logs don't indicate anything unusual.
So why am I doing all this if -58 works properly? The client is using a brand new ASUS M3N78-VM motherboards with built in Nvidia GeForce 8200, which needs the latest beta Nvidia drivers. -58 boots but but does not load X11 due to the driver issue. Plus I want to leverage VDPAU once I get past this point with the 186.xx drivers.
The fact -58 nfs boots correctly leads me to suspect an issue with 62b5 and the interaction with the dhcp relay on my router (Cisco 7500) perhaps. Had the same issue with 62b3 build as well btw.
Any ideas?

Thanks
Tony