No boot from SD-Card in rw mode

[csotoalonso]

Hi,

I'm having a strange problem booting my board from SD-Card

When mounting rootfs as read-only, it boots fine. But as long as I try to boot in read-write mode, the kernel panics.

I'm using a Seco Q7 board iMX6Q based, kernel 3.10.17ga-1.0.1

That's my kernel bootargs which works fine:

Kernel command line: console=ttymxc1,115200 root=/dev/mmcblk0p1 rootdelay=1 ro mem=1024M arm_freq=792

And that's the problematic one:

Kernel command line: console=ttymxc1,115200 root=/dev/mmcblk0p1 rootdelay=1 rw mem=1024M arm_freq=792

That's the message I get from console:

VFS: Cannot open root device "mmcblk0p1" or unknown-block(179,1): error -30

Please append a correct "root=" boot option; here are the available partitions:

b300        15212544 mmcblk0  driver: mmcblk

  b301         1048576 mmcblk0p1 a89529c2-01

  b302        14162944 mmcblk0p2 a89529c2-02

b308         3866624 mmcblk1  driver: mmcblk

  b309         3865600 mmcblk1p1 af9f8377-01

b320             512 mmcblk1rpmb  (driver?)

b318            2048 mmcblk1boot1  (driver?)

b310            2048 mmcblk1boot0  (driver?)

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1)

I've also tried putting the sd-card in a USB adapter, loading the kernel from TFTP and the rootfs from the USB adapter, and it also works fine. So nothing wrong with the card and the FS.

Any thoughts?

[igorpadykov]

Hi Carlos

FSL BSP has kernel parameters as in attached document

Table 8. Kernel Boot Parameters, seems linux ignore bootargs

if encounters invalid argument. I think you can post this problem

to Seco Q7 forum or add source modifications so this parameter

become valid.

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

[csotoalonso · Accepted solution]

There are no invalid arguments. As you can see, the only modification in bootargs is the change from ro to rw, and those seem to be pretty standard ones.

Anyway, I've upgraded uboot to the latest version (2015.04) and now it works fine.