Probably your bootargs passed from uboot override it??
Check in your kernel bootup log, what exactly the bootargs that kernel
receives.. (will be shown as "Kernel command line: xxxxxxxxx"
-Deva

PS.
My sample log.,

Starting kernel ...

Uncompressing
Linux.........................................................................................................................................................................
done, booting the kernel.
Linux version 2.6.32.9 (d...@ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite
2009q1-203) ) #1 SMP PREEMPT Sat Jul 10 00:53:57 IST 2010
CPU: ARMv7 Processor [410fc091] revision 1 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP4430 4430SDP board
Memory policy: ECC disabled, Data cache writealloc
OMAP4430 ES1.0
SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0x100000
Reserving 14745600 bytes SDRAM for VRAM
PERCPU: Embedded 8 pages/cpu @c17a4000 s10080 r8192 d14496 u65536
pcpu-alloc: s10080 r8192 d14496 u65536 alloc=16*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 117602
*Kernel command line: console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw mem=463M
init=/init omapfb.vram=0:4M androidboot.console=ttyO2*
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)


On Mon, Jul 12, 2010 at 2:23 PM, yenchengwang <yenchengw...@gmail.com>wrote:

> hi all,
>     I always get the error message below while kernel booting~
>     CONFIG_CMDLINE="console=ttyS0, 115200 mem=128M uard_dma android"
>
>     VFS: Cannot open root device "<NULL>" or unknown-block(0,0)
>     please append a correct "root=" boot option; here are the available
> partitions:
>     1f00           1024 mtdblock0 (driver?)
>     1f01           3072 mtdblock1 (driver?)
>     1f02          65536 mtdblock2 (driver?)
>     1f03         177536 mtdblock3 (driver?)
>      ....
>     1f07              512 mtdblock7 (driver?)
>     kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0, 0)
>
>     I also tried
>     CONFIG_CMDLINE="root=/dev/mtdblock2 rw init=/init console=ttyS0, 115200
> mem=128M uard_dma android"
>     VFS: Cannot open root device "mtdblock2" or unknown-block(31,2)
>     please append a correct "root=" boot option; here are the available
> partitions:
>     1f00           1024 mtdblock0 (driver?)
>     1f01           3072 mtdblock1 (driver?)
>     1f02          65536 mtdblock2 (driver?)
>     1f03         177536 mtdblock3 (driver?)
>      ....
>     1f07              512 mtdblock7 (driver?)
>     kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(31, 2)
>
>     need some advance~~thanks !!
>
> --
> Regards
> Y-C Wang
>
> --
> unsubscribe: 
> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com>
> website: http://groups.google.com/group/android-porting
>

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

Reply via email to