Problem of Redboot

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem of Redboot

685 Views
GeoffroyLETOUR1
Contributor I

Hello,

 

I have a problem on the IMX27PDK plateform I am trying to download a LINUX Kernel with the server nfs and tftp.

I am working on a virtual Machine Ubuntu 10.04 with VMware. First of all I have tested my NFS and TFTP server with the iMX27ADS plateform in order to see if the servers are correctly installed. So the ADS plateform works good and LINUX is downloaded with the servers.

 

Here is my /etc/exports file:

/tftpboot/rootfs/ *(rw,no_root_squash,no_subtree_check,async)

The servers are restart (TFTP and NFS)

 

In the LTIB I configure:

NFS only

the tagert networking:

-10.6.15.244 (IP gateway)

-10.6.15.227 (IP address of the PDK)

-10.6.15.244 (IP address of the server)

-255.255.255.0 (Netmask)

 

The FEC is disabled in the configure kernel menu.

 

And the redboot configuration is:

- Gateway IP address: 10.6.15.244
- Local IP address: 10.6.15.227
- Local IP address mask: 255.255.255.0
- Default server IP address: 10.6.15.244
- Board specifics: 0
- Console baud rate: 115200

- Set eth0 network hardware address [MAC]: true

This is the command send to reboot in order to boot on linux

load -r -b 0x100000 /tftpboot/zImage


exec -b 0x100000 -l 0x200000 -c "noinitrd console=ttymxc0,115200 root=/dev/nfs nfsroot=10.6.15.244:/tftpboot/rootfs init=/linuxrc ip=10.6.15.227:10.6.15.244"

But I have this error under redboot:
mma7450 0-001d: mma7450 device is probed successfully.

SSI module loaded successfully

PMIC Character device: successfully loaded

PMIC Audio driver loading...
PMIC Battery successfully probed

SEC: mxc_sec_mod_init() called

Sahara HW Version is 0x00000003
VPU initialized

MXC MMC/SD driver

mxcmci-0 found

usbcore: registered new interface driver usbhid

drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver

Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC).

Control ALSA component registered

ALSA device list:

  #0: MXC Freescale with PMIC

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

ieee80211: 802.11 data/management/control stack, git-1.1.13

ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>

input: mxc_ts as /class/input/input2

mxc input touchscreen loaded

mxc_rtc mxc_rtc.0: setting the system clock to 1970-01-01 01:12:58 (4378)

eth0: SMSC911x/921x identified at 0xc885c000, IRQ: 256

eth0: SMSC911x MAC Address: 00:04:9f:00:d3:1e

eth0: link down

IP-Config: Guessing netmask 255.0.0.0

IP-Config: Complete:

      device=eth0, addr=10.6.15.227, mask=255.0.0.0, gw=255.255.255.255,

     host=10.6.15.227, domain=, nis-domain=(none),

     bootserver=10.6.15.244, rootserver=10.6.15.244, rootpath=

Looking up port of RPC 100003/2 on 10.6.15.244

eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

rpcbind: server 10.6.15.244 not responding, timed out

Root-NFS: Unable to get nfsd port number from server, using default

Looking up port of RPC 100005/1 on 10.6.15.244

rpcbind: server 10.6.15.244 not responding, timed out

Root-NFS: Unable to get mountd port number from server, using default

mount: server 10.6.15.244 not responding, timed out

Root-NFS: Server returned error -5 while mounting /tftpboot/rootfs

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       1024 mtdblock0 (driver?)

1f01       5120 mtdblock1 (driver?)

1f02      98304 mtdblock2 (driver?)

1f03       8192 mtdblock3 (driver?)

1f04     149504 mtdblock4 (driver?)

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Could you help me??
Best regards
Tags (1)
0 Kudos
5 Replies

477 Views
PaulFertser
Contributor I
Link down on ethernet card init is perfectly normal, once it's ready, it should detect the carrier, bring the link up, etc. So your kernel log looks fine to me. How did you check your NFS server is properly running and accessible from the network you're connecting your board too?
0 Kudos

477 Views
GeoffroyLETOUR1
Contributor I
Just seven line before eth0: link up you will see the link down. Like you say i am using the debug board. What is the problemn on my configuration for you??
0 Kudos

477 Views
PaulFertser
Contributor I

I do not see any "eth0:link down" in redboot output. I see a line like that in your kernel output, but it later says "link up" shortly after, so that's normal.


FEC is an embedded MAC, and you seem to be using an external SMSC911x ethernet card for eth0 (located on the debug board, also requires some FPGA initialization to be useful, but that can be done in bootloader as well).

0 Kudos

477 Views
GeoffroyLETOUR1
Contributor I

For me the problem comes of the eth0:link down if you see in the error of the redboot. I have the ADS plateform too and the linux boot works good!!

When the ADS boot eth0 is eth0: using half-duplex 10Base-T (RJ-45).

In the menu configure the kernel the FEC would be disabled or enabled????

And there is another option to enable???

Moreover I don't know tcpdump, it is a tool to see the packet on the network???

Thank you in advance

0 Kudos

477 Views
PaulFertser
Contributor I
Why do you think this is related to RedBoot? You kernel seem to be booting all right but it can't connect to your server: "rpcbind: server 10.6.15.244 not responding, timed out". Probably tcpdump on your host would help; anyway, this looks like a network issue.
0 Kudos