On Sat, Sep 25, 2010 at 3:35 AM, Chen Dai <[email protected]> wrote:
> Hi,
> I try to apply the devkit8000 patch got form 2.6.35-devel on 2.6-stable.
> But the kernel stop booting at mount root fs, it seems that the
> kernel unable to mount root on mmc on devkit8000.
>>
>> Root-NFS: No NFS server available, giving up.
>>
>> VFS: Unable to mount root fs via NFS, trying floppy.
>>
>> VFS: Cannot open root device "mmcblk0p2" or unknown-block(2,0)
>>
>> Please append a correct "root" boot option;here are the available
>> partitions:
>>
>> Kernel panic - not syncing: VFS Unable to mount root fs on
>> unknown-block(2,0)
>>
>> ...........
>>
>> ..........
>
> I noticed that there is a similar bug in  2.6.35-devel Bug
> #607906 https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap/+bug/607906
> But the bug status is fix released. So, is the patch bring the bug back?

That bug came out of hiding after a proper change in the omap mmc
layer in 2.6.35.. It turned out that we had been using the wrong
gpio_wp lines on Cx and xM beagles for long time.  It's now fixed
hopefully for the 2.6.37 omap merge.

But take a look at the devkit8000 schematic.. is this the correct pin
mmc write protect pin?

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=arch/arm/mach-omap2/board-devkit8000.c;h=a07086d6a0b26b6cb7d7fbe7d810ea330bcdae28;hb=HEAD#l109


> Or it is the devkit8000 u-boot problem? Because  I use the u-boot.bin
> from http://ftp.linuxfoundation.org/pub/meego/MEEGO_GENIVI_BEAGLE_DEMO.img.xz from http://wiki.meego.com/ARM/Meego_on_the_Beagle,
> the kernel can boot successfully and I can login to the system.Only the LCD
> was black, didn't light on.
> How to resolve this problem? Does anybody have some ideas?
> Thanks in advance,
> Chen
>
>
> _______________________________________________
> MeeGo-dev mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-dev
>
>



-- 
Robert Nelson
http://www.rcn-ee.com/
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to