Hi Sergio,
I've seen the exact same thing happen, when I used the
linux-omap v2.6.35 tag for a beagleboard based device. It gives me the same
kernel panic.
> [ 2.097320] Waiting for root device /dev/mmcblk0p2...
> [ 2.235595] mmc0: new SD card at address b874
> [ 2.243530] mmcblk0: mmc0:b874 SU02G 1.87 GiB (ro)
> [ 2.250213] mmcblk0: p1 p2
> [ 2.323638] VFS: Cannot open root device "mmcblk0p2" or
> unknown-block(179,2)
> [ 2.330871] Please append a correct "root=" boot option; here are the
> available partitions:
> [ 2.339477] b300 1971712 mmcblk0 driver: mmcblk
> [ 2.344848] b301 40131 mmcblk0p1
> [ 2.349182] b302 514080 mmcblk0p2
> [ 2.353973] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(179,2)
In my case, I found that using v2.6.35 and using the
omap3_beagleboard_defconfig worked.
This must an artifact from the defconfig clean up that happened for v2.6.35,
breakages due to defective or untested defconfigs.
Why don't you try a defconfig from a previous kernel version that works?
Best regards,
Elvis Dowson
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
