This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Issue with OMAP MUX flag while building android rowboat kernel.



  • Hi Pawan,

     

    Could you elaborate your issue ?

     

    -

    satish

  • Hi Satish,

     

    Hi Satish,
    Ofcourse, I am building android rowboat 2.3.4 along with DSP. while booting I am having error of

    VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)
    Please append a correct "root=" boot option; here are the available partitions:
    1f00             512 mtdblock0 (driver?)
    1f01            1792 mtdblock1 (driver?)
    1f02             256 mtdblock2 (driver?)
    1f03            5120 mtdblock3 (driver?)
    1f04          516608 mtdblock4 (driver?)
    b300         3872256 mmcblk0 driver: mmcblk
      b301           72261 mmcblk0p1
      b302         1935832 mmcblk0p2
      b303         1863540 mmcblk0p3
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)

    After applying lots of diiferent boot arguments I came to know that by disabling OMAP MUX resolves the issue. Nothing wrong with boot arguments because they are already working fine while using prebuilt image provided by Varisicte.
    So now if I disable OMAP MUX using make menuconfig of kernel, then while booting it detects rootfs and "VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)" error gone, But now there is nothing on LCD it is totally blank.
    And on command prompt it I use logcat command then everything seems to be working properly.

     

    Apologies for blank post, don't Know why this forum page is not working in Internet explorer

     

    Pawan

  • Since you are using a different board from omap3evm, it may not be possible to use the sources provided with the DevKit directly. You probably need to incorporate the changes needed for your board in the kernel source for it to work correctly.

    If you have the sources for the working kernel image, you may be able to port the changes to the DevKit kernel.