On Sat, Feb 27, 2016 at 9:03 AM, Fabio Estevam <[email protected]> wrote: > On Sat, Feb 27, 2016 at 8:13 AM, Otavio Salvador > <[email protected]> wrote: > >> http://ci.ossystems.com.br/public/fsl-community-bsp/master-next/imx6qsabresd/framebuffer/1040/images > > Thanks for providing the pre-built images. They are very helpful.
You are welcome. We are doing some massive changes on our autobuilder infrastructure and we had some issues last days due those changes. > I tried it and booted fine for the first time on my mx6qsabresd. I > could reach the prompt successfully. > > However in the second boot it failed to found the rootfs, which seems > to match what Matt reported: > > ALSA device list: > #0: wm8962-audio > #1: imx-hdmi-soc > EXT3-fs (mmcblk2p2): error: couldn't mount because of unsupported > optional features (2c0) > EXT2-fs (mmcblk2p2): error: couldn't mount because of unsupported > optional features (2c4) > JBD2: recovery failed > EXT4-fs (mmcblk2p2): error loading journal ... > "Unable to mount 780 MB Volume > Error mounting /dev/mmcblk0p2 at > /media/fabio/167af0df-63c6-426f-8461-763d24a0b678: Command-line `mount > -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/mmcblk0p2" > "/media/fabio/167af0df-63c6-426f-8461-763d24a0b678"' exited with > non-zero exit status 32: mount: wrong fs type, bad option, bad > superblock on /dev/mmcblk0p2, > missing codepage or helper program, or other error > In some cases useful info is found in syslog - try > dmesg | tail or so" > > All subsequent boots failed as well. I think I know what is going on; instead of plugging out the power cable, issue a reboot in the first time. It will work afterwards it seems. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
