Glomation
 
Advanced Search
Welcome, Guest. Please login or register.

Login with username, password and session length
May 20, 2012, 02:53:39 AM
News: Welcome to GLomation peer support forum
Pages: [1]
Topic Tools  
Read November 11, 2009, 11:06:55 AM #0
slonko

boot via nfs

Hi,

I am trying to boot a 9g20 to use a root file system from my server with NFS.
I have a root file system that works great with a 9302 which uses RedBoot with the following commands:
fis load zImage
exec -c "root=/dev/nfs nfsroot=192.168.1.70:/home/dan/9302 ip=dhcp console=ttyAM0"


So Im trying to boot the 9g20 from the same NFS share (this may not be possible?)
so in U-Boot I am using:
set bootargs 'console=ttyS0,115200 root=/dev/nfs rw nfsroot=192.168.1.70:/home/dan/9302,nolock'
set ip 192.168.1.5:192.168.1.70:192.168.1.1:255.255.255.0:f175::off
boot


and I get:

ÿRomBOOT


U-Boot 1.3.4 (Jul 24 2009 - 17:50:12)

DRAM:  64 MB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   macb0
macb0: Starting autonegotiation...
macb0: Autonegotiation complete
macb0: link up, 100Mbps full-duplex (lpa: 0x4de1)
Hit any key to stop autoboot:  0
U-Boot> <INTERRUPT>
U-Boot> set bootargs 'console=ttyS0,115200 root=/dev/nfs rw nfsroot=192.168.1.70:/home/dan/9302,nolock'
U-Boot> set ip 192.168.1.5:192.168.1.70:192.168.1.1:255.255.255.0:f175::off
U-Boot> boot

NAND read: device 0 offset 0x100000, size 0x1a7a38
 1735224 bytes read: OK
## Booting kernel from Legacy Image at 21000000 ...
   Image Name:   Linux-2.6.27.4
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1735160 Bytes =  1.7 MB
   Load Address: 20008000
   Entry Point:  20008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.27.4 (user1@Atlas) (gcc version 4.2.3) #4 Sat Jun 27 16:17:54 EDT 2009
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Atmel AT91SAM9G20-EK
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 396 MHz, master 132 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: console=ttyS0,115200 root=/dev/nfs rw nfsroot=192.168.1.70:/home/dan/9302,nolock
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61248KB available (3228K code, 250K data, 132K init)
Calibrating delay loop... 197.83 BogoMIPS (lpj=989184)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 288 bytes
NET: Registered protocol family 16
AT91: Power Management
AT91: Starting after general reset
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
msgmni has been set to 119
io scheduler noop registered
io scheduler anticipatory registered (default)
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL
brd: module loaded
loop: module loaded
ssc ssc.0: Atmel SSC device at 0xc4870000 (irq 14)
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (3a:1f:34:08:54:54)
eth0: attached PHY driver [Davicom DM9161A] (mii_bus:phy_addr=ffffffff:00, irq=-1)
Linux video capture interface: v2.00
Driver 'sd' needs updating - please use bus_type methods
NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
AT91 NAND: 8-bit, Software ECC
Scanning device for bad blocks
Bad eraseblock 118 at 0x00ec0000
Creating 3 MTD partitions on "atmel_nand":
0x00000000-0x00400000 : "Bootstrap"
0x00400000-0x04000000 : "Partition 1"
0x04000000-0x10000000 : "Partition 2"
usbmon: debugfs is not available
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 20, io mem 0x00500000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
udc: at91_udc version 3 May 2006
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC 62:86:dc:30:cc:1d
usb0: HOST MAC 7e:3e:e9:cd:8f:2e
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
mice: PS/2 mouse device common for all mice
input: gpio-keys as /class/input/input0
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
rtc-at91sam9 at91_rtt.0: rtc0: SET TIME!
i2c /dev entries driver
i2c-gpio i2c-gpio: using pins 55 (SDA) and 56 (SCL)
Driver for 1-wire Dallas network protocol.
at91sam9_wdt: invalid timeout (must be between 1 and 16)
Registered led device: ds5
Registered led device: ds1
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock
Looking up port of RPC 100003/2 on 192.168.1.70 <<--Long pause here
rpcbind: server 192.168.1.70 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.1.70
rpcbind: server 192.168.1.70 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
Root-NFS: Server returned error -5 while mounting /home/dan/9302
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00       4096 mtdblock0 (driver?)
1f01      61440 mtdblock1 (driver?)
1f02     196608 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)


Any ideas? thanks for any help.

p.s I my final target is really a 9260S but it has no ethernet so I am assuming the 9g20 I have with ethernet will be the same (re ADC and GPIO)??
 
Read November 11, 2009, 01:47:09 PM #1
admin

Re: boot via nfs

The NFS root problems usually are software related.  You should check the kernel configuration to make sure it has NFS root enabled and other NFS root related TCP/IP settings correctly set.
 
Pages: [1]
Jump to:  

Theme Update by Runic Warrior Originally created by m3talc0re