-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said: | Most of time i have this error, but sometimes as this morning all works fine! | This morning i have boot the moko and it sees the SD: | Rebooting the problem comes back again! Strange behavior!
| [ 3.430000] usbcore: registered new interface driver hci_usb | [ 3.435000] mmcblk0: mmc0:0002 SD4GB 4018176KiB | [ 3.440000] mmcblk0: p1 p2 p3 p4 < > Well normally at this point, negotiations are completed and you can use the card without trouble. All of the important aspects of the card communication have been exercised. | [ 35.795000] FAT: invalid media value (0x00) | [ 35.800000] VFS: Can't find a valid FAT filesystem on dev mmcblk0. | [ 35.810000] FAT: invalid media value (0x00) | [ 35.815000] VFS: Can't find a valid FAT filesystem on dev mmcblk0. | [ 37.890000] EXT2-fs warning: mounting unchecked fs, running e2fsck is | recommended | [ 38.155000] EXT2-fs warning: mounting unchecked fs, running e2fsck is | recommended | [ 38.380000] EXT2-fs warning: mounting unchecked fs, running e2fsck is | recommended | [ 38.620000] FAT: bogus number of reserved sectors | [ 38.625000] VFS: Can't find a valid FAT filesystem on dev mmcblk0p4. | [ 38.635000] FAT: bogus number of reserved sectors | [ 38.640000] VFS: Can't find a valid FAT filesystem on dev mmcblk0p4. I think these errors can be OK, it's the userspace trying to mount things various ways, including the block device directly as FAT which is seen on Windows formatted stuff sometimes. Otherwise there are no real errors in this dmesg it seems. Is it always changing whether it will show problems or not every boot? So every second boot works? - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkl0TRkACgkQOjLpvpq7dMoZDwCdED6HAWE3tyJzKcCKdRqXReM7 rKgAn09ISf9MCMnlMNLYbgmyWz3hXC6W =fXBC -----END PGP SIGNATURE-----
