Linux boot hint needed

We're gettting further in getting linux to run on our board. From the messages either: ethernet initialization completely failed or linux can't find a NFS mount point for the root file system. If the reason is the former are there debug switches available that would give more details? Thx.

4)) #14 Thu May 6 13:12:27 EDT 2004 CPU: XScale-IOP80321 [69052430] revision 0 (ARMv5TE) CPU: D undefined 5 cache CPU: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets CPU: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets Machine: LSI Logic 80321 Ignoring unrecognised tag 0x00000000 initrd (0xa0800000 - 0xa0c00000) extends beyond physical memory - disabling initrd MM: not creating mapping for 0x10081000 at 0x10081000 in user region On node 0 totalpages: 32768 zone(0): 32768 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: ip=boot root=/dev/nfs nfsroot=172.22.33.87:/opt/montavista/pro/devkit/arm/xscale_le/target/ console =ttyS0,38400 ****************Baud Base: 38400, Baud: 38400, quotient: 1Calibrating delay loop... 599.65 BogoMIPS Memory: 128MB = 128MB total Memory: 127628KB available (1442K code, 292K data, 256K init) XScale Cache/TLB Locking Copyright(c) 2001 MontaVista Software, Inc. XScale cache_lock_init called Calling consistent alloc low_level_page initialized low_level_page @ 0xc8800000 icache_lock_fn @ 0xc8800080 dcache_lock_fn @ 0xc88000a0 icache_unlock_fn @ 0xc8800098 dcache_unlock_fn @ 0xc88000f0 Initializing TLB locking TLB locking initialized Dentry cache hash table entries: 16384 (order: 5, 131072 bytes) Inode cache hash table entries: 8192 (order: 4, 65536 bytes) Mount-cache hash table entries: 2048 (order: 2, 16384 bytes) Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes) Page-cache hash table entries: 32768 (order: 5, 131072 bytes) POSIX conformance testing by UNIFIX PCI: bus0: Fast back to back transfers enabled Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket LSP Revision 1 ikconfig 0.5 with /proc/ikconfig Starting kswapd Disabling the Out Of Memory Killer devfs: v1.12c (20020818) Richard Gooch ( snipped-for-privacy@atnf.csiro.au) devfs: boot_options: 0x1 JFFS2 version 2.1. (C) 2001, 2002 Red Hat, Inc., designed by Axis Communications AB. pty: 256 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0x10081000 (irq = 28) is a 16550A Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize Intel(R) PRO/1000 Network Driver - version 5.0.43 Copyright (c) 1999-2003 Intel Corporation. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP IP: routing cache hash table of 1024 buckets, 8Kbytes TCP: Hash tables configured (established 8192 bind 16384) IP-Config: No network devices available. NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. NetWinder Floating Point Emulator V0.95 (c) 1998-1999 Rebel.com Looking up port of RPC 100003/2 on 172.22.33.87 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 172.22.33.87 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 /opt/montavista/pro/devkit/arm/xscale_le/target/ VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "nfs" or 02:00 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 02:00
Reply to
noone
Loading thread data ...

From the messages, looks like the ethernet init is ok. You could try mounting the nfs directory from another PC and see if it works (just to make sure that the host nfs server works ok).

-sid

Reply to
Siddharth Choudhuri

It appears that the Ethernet device was not found/initialized. Either the device did not match any loaded driver, or it wasn't enabled.

Is the ip=... setting right? When I have used it, it has a number of parameters separated by colons, e.g. ip=10.6.0.200:10.6.3.16::255.255.240.0::eth0:off This specifies the local IP address, boot server, default router, netmask, and host address. If I want to use bootp to get the address, I set the off at the end to on, and don't set the other parameters. For details, see

formatting link
and look for ip=

A network driver was loaded, presumably this matches the network hardware.

Right at this point, there should be some messages about the link status changes.

This doesn't look good - there should be a network device here to configure.

Also, is your hardware cache-coherent? At least for the e100 driver, coherent cache is required (requiring the processor and memory controller to snoop the DMA activity and invalidate cache lines when appropriate). You could try the eepro1000 driver, the eepro100 driver does not require coherent cache, if you don't have coherent cache.

Reply to
Haller

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.