• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Can't get NFS boot to work (solved)  (Read 1914 times)
DanielQuinn
Newbie
*

Karma: 0
Posts: 9


View Profile
« on: May 01, 2009, 10:05:30 PM »

This is causing me so much pain, please someone help me :-(

So here's the deal: I tried writing a .jffs2 file to /dev/mtdblock2 and it blew up with a bunch of errors so now I'm trying to fix everything by starting an NFS boot with the following:

Code:
set ipaddr 192.168.1.15
set serverip 192.168.1.65
set rootpath '/sheevaplug/home'
set image_name uImage.sheeva.040309
set console 'console=ttyS0,115200 mtdparts=:0x100000@0x000000(u-boot),0x300000@0x100000(uImage),0x1fc00000@0x400000(rootfs)rw'
set bootargs_root 'root=/dev/nfs rw'
set bootcmd 'tftpboot 0x2000000 $(image_name);setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x2000000'
saveenv
reset

Now the server (192.168.1.65) is running NFS and I mounted it just to check but here's what's in there:

Code:
# cat /etc/exports
/sheevaplug/home      *(rw,no_root_squash,sync,subtree_check)

# mount -t nfs 192.168.1.65:/sheevaplug/home /mnt/tmp
# ls -l /mnt/tmp
total 112K
drwxr-xr-x  2 root root 4.0K Feb 26  2008 bin
drwxr-xr-x  4 root root  16K Feb 26  2008 dev
drwxr-xr-x  3 root root   72 Feb 26  2008 etc
drwxr-xr-x  2 root root 4.0K Feb 26  2008 lib
lrwxrwxrwx  1 root root   11 May  2 03:59 linuxrc -> bin/busybox
drwxr-xr-x  2 root root    1 Feb 25 04:45 mnt
drwxr-xr-x  2 root root    1 Feb 26  2008 proc
drwxr-xr-x  2 root root 4.0K Feb 26  2008 sbin
drwxr-xr-x 10 root root   64 Feb 26  2008 usr

However, when I start up the plug, it hangs with:

Code:
USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
Using egiga0 device
TFTP from server 192.168.1.65; our IP address is 192.168.1.15
Filename 'uImage.sheeva.040309'.
Load address: 0x2000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###############
done
Bytes transferred = 2070316 (1f972c hex)
## Booting image at 02000000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-04-04   1:49:44 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2070252 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux...

I don't know what's wrong, but the sad part is that this is only the first hurdle.  All I want to do is install a custom kernel on the stock Linux that came pre-installed and is now gone.  Every custom kernel I've built has failed in one way or another to boot, but at the very least I'd like to fix this one issue tonight.
« Last Edit: May 02, 2009, 12:49:22 AM by DanielQuinn » Logged

tmk
Newbie
*

Karma: 1
Posts: 40


View Profile
« Reply #1 on: May 02, 2009, 12:02:32 AM »

Did you 'set mainlineLinux yes' or whatever the syntax is? You have to set it correctly.. If using the kernel packaged with sheevaplug, then mainlineLinux=no, if you compiled your own, mainlineLinux=yes.

It's documented somewhere, probably in the kernel config section.

Also you'll probably have to set the arcnum to 2097 or whatever it is.

-tmk

Logged

DanielQuinn
Newbie
*

Karma: 0
Posts: 9


View Profile
« Reply #2 on: May 02, 2009, 12:07:18 AM »

That's exactly it.  I figured it out on my own about 10 min ago and just popped back here to just delete the evidence of my stupidity :-)  Thanks for the quick reply!
Logged

Pages: [1]
Print
Jump to: