[uClinux-dev] NFS rooting issues

Allon Stern allon.stern at argonst.com
Wed Feb 6 15:15:34 EST 2008


With the original uClinux-dist-20070130 2.6.19-uc1 kernel I could  
root on an NFS volume.

After applying the uClinux-dist-20070130-20080131 patch, to bring the  
kernel to 2.6.24-uc0, I cannot.

Note: this is on an nommu system - M5282LITE

What I did was add a "root=/dev/nfs ip=dhcp" argument to the kernel 
(s), and, after building the images, I copied the files from uClinux- 
dist/romfs to a directory that I have exported via NFS and set to be  
the root filesystem. I then created device nodes in that root's /dev  
directory for console and null.

Netbooting with 2.6.19 works. Booting from the image.bin (romfs) works.
Netbooting with 2.6.24 fails. Booting from the image.bin (romfs) works.
I can netboot the 2.6.19 from the filesystem I built for 2.6.24.

The error I get with 2.6.24 is:
Unable to mmap process text, errno 12
Unable to mmap process text, errno 12
Kernel panic - not syncing: No init found. Try passing init= option  
to kernel.

The root filesystem has a /bin/init, which is a BFLT executable -  
version 4 gotpic

Reading through fs/binfmt_flat.c I can see where the failure is  
occuring, but I don't know why. I'm not too familiar with the mmaping  
implementation in uClinux. Also, it is puzzling why it would succeed  
with similar code in 2.6.19; the kernel configurations are close. Am  
I missing something in the kernel config?

Again, /bin/init is on an NFS volume.

Any clues?

Thanks.
-
allon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.uclinux.org/pipermail/uclinux-dev/attachments/20080206/52326a98/attachment.html


More information about the uClinux-dev mailing list