RE: Problem with booting linux

[Sai Saravana <sai.sy@xxxxxxxxxxx>]

Hi All,

I have fixed all the syntax issues. But still linux is not coming up.
It stops by saying "append a correct boot option". Log is attached.

Can anyone send me the binaries of u-boot, linux and cramfs for ARM VP
board.
The exact details are ARM 926EJS PB Real View versatile Platform base board.

Thanks in advance

Thanks and Regards,
-Sai.
________________________________
RAM Configuration:
Bank #0: 00000000  0 kB
Flash: 64 MB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
VersatilePB # printenv
bootdelay=2
baudrate=38400
bootfile="/tftpboot/uImage"
bootargs=root=/dev/mtdblock0 mtdparts=armflash.0:0x65D000k@0x2C0000(cramfs)
cons
ole=ttyAMA0 mem=128M
bootcmd=cp 0x34080000 0x7FC0 0x81000
stdin=serial
stdout=serial
stderr=serial
verify=n

Environment size: 243/65532 bytes
VersatilePB # bootm
## Booting image at 00007fc0 ...
Bad Magic Number
VersatilePB # cp 0x34080000 0x7FC0 0x81000
VersatilePB # bootm
## Booting image at 00007fc0 ...
   Image Name:   uzImage
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1122216 Bytes =  1.1 MB
   Load Address: 00007fc0
   Entry Point:  00008000
   XIP Kernel Image ... OK

Starting kernel ...

Uncompressing
Linux.............................................................
.............. done, booting the kernel.
Linux version 2.6.12-arm1 (cmarinas@pc1117) (gcc version 3.4.3 (release)
(CodeSo
urcery ARM Q1B 2005)) #7 Fri Jun 24 15:35:43 BST 2005
CPU: ARM926EJ-Sid(wb) [41069263] revision 3 (ARMv5TEJ)
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
Machine: ARM-Versatile PB
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists
Kernel command line: root=/dev/mtdblock0
mtdparts=armflash.0:0x65D000k@0x2C0000(
cramfs) console=ttyAMA0 mem=128M
PID hash table entries: 1024 (order: 10, 16384 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB = 128MB total
Memory: 127360KB available (1931K code, 401K data, 84K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
CLCD: Versatile hardware, VGA display
Clock CLCDCLK: setting VCO reg params: S=1 R=99 V=98
Console: switching to colour frame buffer device 80x30
Serial: AMBA PL011 UART driver
ttyAMA0 at MMIO 0x101f1000 (irq = 12) is a AMBA/PL011
ttyAMA1 at MMIO 0x101f2000 (irq = 13) is a AMBA/PL011
ttyAMA2 at MMIO 0x101f3000 (irq = 14) is a AMBA/PL011
ttyAMA3 at MMIO 0x10009000 (irq = 38) is a AMBA/PL011
io scheduler noop registered
io scheduler deadline registered
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@xxxxxxx>
eth0: SMC91C11xFD (rev 1) at c886c000 IRQ 25 [nowait]
eth0: Ethernet addr: 00:02:f7:00:11:9f
armflash.0: Found 2 x16 devices at 0x0 in 32-bit bank
 Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
mtd: armflash.0: partitioning exceeds flash size, truncating
RedBoot partition parsing not available
afs partition parsing not available
mice: PS/2 mouse device common for all mice
mmc0: MMCI rev 0 cfg 00 at 0x10005000 irq 22,33
mmc1: MMCI rev 0 cfg 00 at 0x1000b000 irq 23,34
Advanced Linux Sound Architecture Driver Version 1.0.9rc2  (Thu Mar 24
10:33:39
2005 UTC).
ALSA device list:
  #0: ARM AC'97 Interface at 0x10004000, irq 24
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 1 part 10 variant 9 rev 1
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "mtdblock0" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(2,0)
________________________________

-----Original Message-----
From: Catalin Marinas [mailto:catalin.marinas@xxxxxxx] 
Sent: Monday, July 25, 2005 3:38 PM
To: Sai Saravana
Cc: linux-arm@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Problem with booting linux


Sai Saravana <sai.sy@xxxxxxxxxxx> wrote:
> While the linux is booting on the arm board, the boot process stops by 
> givign the following error..
>
> VFS: Cannot open root device
> "mtdblock0=mtdparts=armflash0:19232k@2C0000(cramfs)
            ^
That's wrong. The problem is in setting the command line in U-Boot.

> I am following the exact syntax as you have told. Please let me know 
> How to proceed further. Is the cramfs file system not matching by any 
> chance???

In U-Boot:

setenv bootargs root=/dev/mtdblock0 mtdparts=armflash0:19232k@2C0000(cramfs)

and printenv will show the proper command line (without the '=' between
mtdblock0 and mtdparts).

Also change 'armflash0' with 'armflash.0' if you use a 2.6.12 kernel.

-- 
Catalin




-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php