Hi, On 07/30/2014 04:49 PM, Luc Verhaegen wrote: > Hi, > > On my cubietruck with 3.16.0-rc7-00007-g31dab71, my rootfs is not being > mounted rw, so my ubuntu complains. Manually remounting works. > > Here is the relevant section of dmesg: > > sunxi-mmc 1c12000.mmc: No vqmmc regulator found > sunxi-mmc 1c12000.mmc: base:0xf00f6000 irq:67 > vcc3v0: disabling > sunxi-mmc 1c12000.mmc: smc 1 err, cmd 8, RTO !! > mmc1: queuing unknown CIS tuple 0x80 (2 bytes) > EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature incompatibilities > EXT4-fs (mmcblk0p2): couldn't mount as ext2 due to feature incompatibilities > mmc1: queuing unknown CIS tuple 0x80 (3 bytes) > mmc1: queuing unknown CIS tuple 0x80 (3 bytes) > EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) > VFS: Mounted root (ext4 filesystem) readonly on device 179:2. > mmc1: queuing unknown CIS tuple 0x80 (7 bytes) > mmc1: new high speed SDIO card at address 0001 > > Any ideas on what the smc 1 err, and CIS tuple 0x80 errors are?
"smc 1" means the errors are on mmc1 not mmc0, or iow these are errors from the sdio probing of the sdio wifi chip. These are "normal" sdio probing errors (some sdio probing commands are expected to fail), and can safely be ignored. > Are they really responsible for the RO mount, No. > or is there something my 14.04 ubuntu should be aware about with newer > kernels? If you want to have your rootfs mounted rw right away by the kernel, rather then having it remounted later on by init scripts, you need to specify "rw" on the kernel commandline. Regards, Hans -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
