Tomas Frydrych
2012-04-04 10:14:55 UTC
Hi,
I am trying to get Yocto image built from yesterday's master
(Linux-3.0.23-yocto-standard) to boot on the NAND-less version of
BeagleBoard xM, but the kernel panics with:
----------------- console log start ------------
Waiting for root device /dev/mmcblk0p2...
mmc0: new SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.67 GiB (ro)
mmcblk0: p1 p2
VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)
Please append a correct "root=" boot option; here are the available
partitions:
b300 3858432 mmcblk0 driver: mmcblk
b301 120456 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1
b302 3445942 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
VFS: Unable to mount root fs on unknown-block(179,2)
User configuration error - no valid root filesystem found
Kernel panic - not syncing: Invalid configuration from end user prevents
continuing
-------------- console log end ------------------------------------
My guess would be the problem is the card being detected as 'ro' (line
3), but I do not know why that is (there is no lock switch on mmc cards).
The card itself is fine, it's the original card that came with the
board, the original Angstrom demo boots fine from it, and yocto kernel
2.6.37 also used to boot.
Tomas
I am trying to get Yocto image built from yesterday's master
(Linux-3.0.23-yocto-standard) to boot on the NAND-less version of
BeagleBoard xM, but the kernel panics with:
----------------- console log start ------------
Waiting for root device /dev/mmcblk0p2...
mmc0: new SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.67 GiB (ro)
mmcblk0: p1 p2
VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)
Please append a correct "root=" boot option; here are the available
partitions:
b300 3858432 mmcblk0 driver: mmcblk
b301 120456 mmcblk0p1 00000000-0000-0000-0000-000000000mmcblk0p1
b302 3445942 mmcblk0p2 00000000-0000-0000-0000-000000000mmcblk0p2
VFS: Unable to mount root fs on unknown-block(179,2)
User configuration error - no valid root filesystem found
Kernel panic - not syncing: Invalid configuration from end user prevents
continuing
-------------- console log end ------------------------------------
My guess would be the problem is the card being detected as 'ro' (line
3), but I do not know why that is (there is no lock switch on mmc cards).
The card itself is fine, it's the original card that came with the
board, the original Angstrom demo boots fine from it, and yocto kernel
2.6.37 also used to boot.
Tomas