Skip to contentSkip to conversation

bootm problem

U-Boot-Users Chung Pham 3 participants 3 messages Sep 6, 2004

lore
Share & tools
lore

Chung Pham

author
#0 lore raw

Hi,

I have just started with U-boot. Can you help me
this problem:

First I used TFTP command to load uImage for bootm, it's OK.
Second, I used "bootm" for boot Linux, but when it ran to these lines:

[WRS]> bootm 100000
## Booting image at 00100000 ...
Image Name: Linux-2.4.25
Image Type: PowerPC Linux Kernel Image (gzip
compressed)
Data Size: 704727 Bytes = 688.2 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Linux version 2.4.25 (root at linux) (gcc version 3.2.2 20030217 (Yellow Dog Linux 3.0 3.2.2-2a_1)) #1 Mon Sep 6 16:35:49 KST 2004
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/nfs rw nfsroot=192.168.1.245:/opt/eldk/ppc_8xx ip=192.168.1.248:192.168.1.245:192.168.1.1:255.255.255.0 Decrementer Frequency = 187500000/60 Calibrating delay loop... 49.76 BogoMIPS
Memory: 30684k available (1216k kernel code, 416k data, 56k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc. CPM UART driver version 0.04
ttyS0 at 0x0280 is on SMC1 using BRG1
pty: 256 Unix98 ptys configured
eth0: CPM ENET Version 0.2 on SCC1, 00:d0:93:00:05:b5 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision:
7.00beta4-2.4
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
IP-Config: Complete:

      device=eth0, addr=192.168.1.248,
mask=255.255.255.0, gw=192.168.1.1,
     host=192.168.1.248, domain=, nis-domain=(none),
     bootserver=192.168.1.245,

rootserver=192.168.1.245, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Looking up port of RPC 100003/2 on 192.168.1.245

And it hang not continue.

Could you please tell me what is this problem?

Thank you for you help.

Chung Pham.

_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush

#1 lore raw
Quoted 3 lines · In message <[email protected]> you wrote:

I have just started with U-boot. Can you help me
this problem:

Why are you sending the same question twice within half an hour, and with a different subject???

DON'T DO THAT!

Wolfgang Denk

Signature · 4 lines
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
Question: How does one get fresh air into a Russian church?
Answer:   One clicks on an icon, and a window opens!
#2 lore raw
In reply to Chung Pham
Quoted 4 lines

Kernel command line: root=/dev/nfs rw nfsroot=192.168.1.245:/opt/eldk/ppc_8xx ip=192.168.1.248:192.168.1.245:192.168.1.1:255.255.255.0

...

Quoted 10 lines

NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
IP-Config: Complete:

      device=eth0, addr=192.168.1.248,
mask=255.255.255.0, gw=192.168.1.1,
     host=192.168.1.248, domain=, nis-domain=(none),
     bootserver=192.168.1.245,
Quoted 8 lines

rootserver=192.168.1.245, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Looking up port of RPC 100003/2 on 192.168.1.245

And it hang not continue.

I would bet that NFS is not running on 192.168.1.248. Your kernel command line is trying to point the newly booted kernel to access its root filesystem through an NFS mount point on 192.168.1.248, specifically, th directory: /opt/eldk/ppc_8xx.

1) make sure NFS is running,
on RHL, try, e.g., '/etc/init.d/nfs status'
2) make sure you have a well-formed /etc/exports file
try, e.g., '/opt/eldk/ppc_8xx *(rw,no_root_squash,no_all_squash)'
3) make sure the mount point '/opt/eldk/ppc_8xx' exists and contains an image of the ELDK PPC/8xx root filesystem
4) run 'exportfs -ra' after starting NFS the first time, to synchronize info
5) boot your target again

Cheers,
T.mike