BeagleXm Rev C vs. BeagleXm Rev A


I thought I sent a post a few minutes ago; but I could not find it in
the discussion posts, so I send it again.

I am facing a problem to mount root filesystem from uSD card on
BeagleXm Rev C board. On bXm-C board, the message is like below. The
SD card is mounted as 'ro' (readonly). But with the original SD card
comes in the DigiKey shipping package, there is no problem.

[ 4.599700] mmc0: new high speed SDHC card at address 1234
[ 4.608551] mmcblk0: mmc0:1234 SA04G 3.67 GiB (ro)
[ 4.620666] mmcblk0: p1 p2
[ 17.093261] VFS: Cannot open root device "mmcblk0p2" or unknown-
[ 17.100677] Please append a correct "root=" boot option; here are
the available partitions:
[ 17.109527] b300 3858432 mmcblk0 driver: mmcblk
[ 17.115142] b301 72261 mmcblk0p1
[ 17.123535] b302 3783307 mmcblk0p2
[ 17.131927] Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(179,2)

While on BeagleXm RevA board, the SD card is mounted as 'r+w'. rootfs
can be mounted without problem. below is the log from bXm-A board.

[ 4.510986] mmc0: host does not support reading read-only switch.
assuming write-enable.
[ 4.531707] mmc0: new high speed SD card at address 0001
[ 4.540405] mmcblk0: mmc0:0001 00000 1.89 GiB
[ 4.551330] mmcblk0: p1 p2
[ 4.797637] usb 1-2.1: new high speed USB device using ehci-omap
and address 3
[ 4.923278] usb 1-2.1: New USB device found, idVendor=0424,
[ 4.930480] usb 1-2.1: New USB device strings: Mfr=0, Product=0,
[ 17.064392] EXT3-fs: barriers not enabled
[ 19.405639] kjournald starting. Commit interval 5 seconds
[ 19.411773] EXT3-fs (mmcblk0p2): warning: mounting unchecked fs,
running e2fsck is recommended
[ 19.590576] EXT3-fs (mmcblk0p2): using internal journal
[ 19.596099] EXT3-fs (mmcblk0p2): recovery complete
[ 19.666961] EXT3-fs (mmcblk0p2): mounted filesystem with ordered
data mode
[ 19.674713] VFS: Mounted root (ext3 filesystem) on device 179:2.

Does anybody know what is the cause? How to fix the problem?


Your kernel is missing the new "xM C" detection patches..

Almost all the current "demo images" have this fixed and patches have
been posted to l-o..