Kingston SDC4 don't work with OM2008.9's kernel
acd.capobianco at gmail.com
Mon Jan 19 11:45:38 CET 2009
The SD is partioned in this way:
Disco /dev/sdf: 4114 MB, 4114612224 byte
127 testine, 62 settori/tracce, 1020 cilindri
Unità = cilindri di 7874 * 512 = 4031488 byte
Identificativo disco: 0x00069e13
Dispositivo Boot Start End Blocks Id System
/dev/sdf1 1 4 15717 83 Linux
/dev/sdf2 5 271 1051179 83 Linux
/dev/sdf3 272 402 515747 83 Linux
/dev/sdf4 403 1020 2433066 5 Esteso
/dev/sdf5 403 669 1051148 83 Linux
/dev/sdf6 670 800 515716 83 Linux
/dev/sdf7 801 931 515716 83 Linux
/dev/sdf8 932 1020 350362 83 Linux
/dev/sdf4 is an extended partition, maybe the kernel can't read this kind of
I'm booting form NAND, if i try to boot from /dev/sdf3 i have kernel panic,
but it succeed in loading the kernel from the firt partition of the SD.
GTA02v6 # mmcinit
Card Type: SD 2.0 SDHC
Manufacturer: 0x41, OEM "42"
Product name: "SD4GB", revision 2.0
Serial number: 8914688
Manufacturing date: 7/2008
MMC/SD size: 3MiB
GTA02v6 # ext2load mmc 1 0x32c00000 uImageStable.bin
1912444 bytes read
GTA02v6 # bootm 0x32000000
## Booting kernel from Legacy Image at 32000000 ...
Image Name: Openmoko Freerunner Kernel
Created: 2009-01-16 23:22:46 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1912380 Bytes = 1.8 MB
Load Address: 30008000
Entry Point: 30008000
Verifying Checksum ... OK
This is the error when i try to boot from SD:
| b301 15717 mmcblk0p1
| b302 1051179 mmcblk0p2
| b303 515747 mmcblk0p3
| b304 1 mmcblk0p4
| No filesystem could mount root, tried ext2
| Kernel panic - not syncing: VFS: Unable to mount root fs on
Andy Green wrote:
> -----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
> -----END PGP SIGNATURE-----
View this message in context: http://n2.nabble.com/Kingston-SDC4-don%27t-work-with-OM2008.9%27s-kernel-tp2109232p2180755.html
Sent from the Openmoko Kernel mailing list archive at Nabble.com.
More information about the openmoko-kernel