[U-Boot-Users] NFS booting problem
Hi,
I'm using a FSForth NS9750 developer's kit and I got into some problems booting from NFS. My server ip stated in u-boot is 167.116.150.102 but when linux is looking up RPC 100003/2 and 100005/1, it's trying ip address 167.116.183.37. Failing to find it, it goes into kernel panic.
Any idea why the server's ip address is changed?? I tried another kit to boot from 167.116.150.102 and it worked fine but there are no differences in the u-boot environment parameters.
Any hints??
Thanks, Terence Soh.
My u-boot environment is
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
baudrate=38400 ethaddr=00:04:f3:00:23:b1 fssize=500000 bootdelay=3 v=oetenv bootargs bootfile=uImage rootpath=/opt/fs filesize=10f674 fileaddr=10000 netmask=255.255.255.0 device=eth0 ipaddr=167.116.150.101 serverip=167.116.150.102 gatewayip=167.116.150.1 bootargs=console=ttyS0 root=/dev/nfs nfsroot=167.116.150.102:/opt/fs ip=167.116.150.101:167.116.150.102:167.116.150.1:255.255.255.0:darkstar:eth0:off stdin=serial stdout=serial stderr=serial
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Starting kernel ...
Uncompressing Linux................................................................................ done, booting the kernel. Linux version 2.6.8ABTest (root@darkstar) (gcc version 3.3.3) #6 Thu Mar 31 14:34:18 SGT 2005 CPU: ARM926EJ-Sid(wb) [41069264] revision 4 (ARMv5TEJ) CPU: D VIPT write-back cache CPU: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets CPU: D cache: 4096 bytes, associativity 4, 32 byte lines, 32 sets Machine: NS9750 Memory policy: ECC disabled, Data cache writeback NS9750 Rev. 0, running at 398 MHz On node 0 totalpages: 4096 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 0 pages, LIFO batch:1 HighMem zone: 0 pages, LIFO batch:1 Built 1 zonelists Kernel command line: console=ttyS0 root=/dev/nfs nfsroot=167.116.150.102:/opt/fs ip=167.116.150.101:167.116.150.102:167.116.150.1:255.255.255.0:darkstar:eth0:off PID hash table entries: 128 (order 7: 1024 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) Memory: 16MB = 16MB total Memory: 13620KB available (1941K code, 504K data, 96K init) Calibrating delay loop... 99.32 BogoMIPS Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub i2c_ns: I2C ns9750 driver $Revision: 1.1 $ initializing ns9750fb: Using LCD display sharp_lq57 fb0: ns9750fb frame buffer device NetWinder Floating Point Emulator V0.97 (double precision) devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au) devfs: boot_options: 0x0 JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc. Console: switching to colour frame buffer device 40x15 Serial: 8250/16550 driver $Revision: 1.2 $ 1 ports, IRQ sharing disabled ttyS0 at MMIO 0x0 (irq = 30) is a ST16654 Serial: JTAG driver $Revision: 1.2 $ ttyJ0 at MMIO 0x0 (irq = 0) is a JTAGCOMM RAMDISK driver initialized: 16 RAM disks of 6128K size 1024 blocksize Ethernet: NS9750 driver $Revision: 1.6 $ Using anticipatory io scheduler NAND Flash memory mapped to virtual c1851000 NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bit) Scanning device for bad blocks Using static partition definition Creating 1 MTD partitions on "a9m9750": 0x00000000-0x02000000 : "(whole)" ns9750-ohci ns9750-ohci0: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.0:USB HID core driver mice: PS/2 mouse device common for all mice ns9750ts NS9750 touchscreen initialization 24c64: EEPROM driver $Revision: 1.1 $ initializing NET: Registered protocol family 2 IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 1024 bind 2048) NET: Registered protocol family 1 NET: Registered protocol family 17 ns_eth: PHY (0x13, 0x78e2) = LXT971A detected at 0x1 ns_eth: link mode 100 Mbps full duplex (auto) IP-Config: Gateway not on directly connected network. Looking up port of RPC 100003/2 on 167.116.183.37 RPC: sendmsg returned error 101 portmap: RPC call returned error 101 Root-NFS: Unable to get nfsd port number from server, using default Looking up port of RPC 100005/1 on 167.116.183.37 RPC: sendmsg returned error 101 portmap: RPC call returned error 101 Root-NFS: Unable to get mountd port number from server, using default RPC: sendmsg returned error 101 mount: RPC call returned error 101 Root-NFS: Server returned error -101 while mounting 167.116.150.102:/opt/fs 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 Kernel panic: VFS: Unable to mount root fs on unknown-block(2,0)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
In message OF28F58C91.E63A1264-ON48256FD5.0024B11F-48256FD5.0025BC5D@applera.com you wrote:
I'm using a FSForth NS9750 developer's kit and I got into some problems booting from NFS. My server ip stated in u-boot is 167.116.150.102 but when linux is looking up RPC 100003/2 and 100005/1, it's trying ip address 167.116.183.37. Failing to find it, it goes into kernel panic.
Any idea why the server's ip address is changed?? I tried another kit to
bootargs=console=ttyS0 root=/dev/nfs nfsroot=167.116.150.102:/opt/fs ip=167.116.150.101:167.116.150.102:167.116.150.1:255.255.255.0:darkstar:eth0:off
--------------------------------------------------------------------------^^^^
In your bootmessages I can see a "ns_eth" device, but no "eth0". Is there any "eth0" device on your board?
Best regards,
Wolfgang Denk
In your bootmessages I can see a "ns_eth" device, but no "eth0". Is there any "eth0" device on your board?
Yes, there is a eth0 device on board. It used to work until I was meddling with the u-boot environment because my nfs server got a new ip. It's wierd because I'm sure I set the serverip to 167.116.150.160 but the kernel keeps going to 167.116.191.205(some arbitary ip) to look up RPC 10000X.
I even tried using cross cables hooking the target system to the nfs server. Still it's doing the wrong thing.
I checked on another board and the way it's done is that the RPC is looked up on the serverip(167.116.150.160).
Terence Soh.
In message OF8F84690F.EA2B187E-ON48256FD6.0002C9F8-48256FD6.0003B706@applera.com you wrote:
Yes, there is a eth0 device on board. It used to work until I was meddling
I don't see it in your boot messages. Please check.
Best regards,
Wolfgang Denk
Any chance you ran dhcp and it got a new <wrong> serverip from your dhcp server? Happens to me all the time ;-) BTW, is there a way to prevent dhcp server from updating serverip?
Sergei Sharonov
In message loom.20050331T175833-546@post.gmane.org you wrote:
Any chance you ran dhcp and it got a new <wrong> serverip from your dhcp server? Happens to me all the time ;-)
It should not have happened here as the <autoconf> part of the "ip=" boot argument was set to "off" which means "means no autoconfiguration."
BTW, is there a way to prevent dhcp server from updating serverip?
Yes. Don't ask the DHCP server.
Best regards,
Wolfgang Denk
Wolfgang Denk <wd <at> denx.de> writes:
In message <loom.20050331T175833-546 <at> post.gmane.org> you wrote:
Any chance you ran dhcp and it got a new <wrong> serverip from your dhcp server? Happens to me all the time
It should not have happened here as the <autoconf> part of the "ip=" boot argument was set to "off" which means "means no autoconfiguration."
Oups. Should have read the whole message ;-)
BTW, is there a way to prevent dhcp server from updating serverip?
Yes. Don't ask the DHCP server.
Errr.. Was talking about u-boot. How do I prevent u-boot from updating serverip when I run dhcp command? Sorry if that's FAQ.
Best regards,
Sergei Sharonov
In message loom.20050331T211027-298@post.gmane.org you wrote:
Yes. Don't ask the DHCP server.
Errr.. Was talking about u-boot. How do I prevent u-boot from updating serverip when I run dhcp command? Sorry if that's FAQ.
Don't ask the DHCP server if you don't need the configuration from it.
Alternatively, save any values you wanna keep. Something like that:
=> set old $ipaddr;dhcp;set ipaddr $old
Viele Grüße,
Wolfgang Denk
participants (3)
-
Sergei Sharonov -
Terence Soh -
Wolfgang Denk