View Single Post
terrencegf's Avatar
Posts: 221 | Thanked: 182 times | Joined on Jul 2007 @ Central Illinois
#192
Originally Posted by fanoush View Post
This is strange. It shouldn't be related to the card size at all. If you can mount the card and see the data, it should be same at boot time. Which partition you used for ext2, /dev/mmcblk0p2 or something higher like p4,p5..?
I did two partitions, /dev/mmcblk0p1 as FAT16 or FAT32 (depending on the size I chose) and /dev/mmcblk0p2 as ext2.

Originally Posted by fanoush View Post
You can edit/create bootmenu.conf (not .sh) and add
Code:
dmesg >/tmp/dmesg.out
as a last line and after boot see if there is anything suspicious in kernel log early at boot time. You can also see kernel log after it failed and booted from flash but the beginning is cut off.
The resulting /tmp/dmesg.out file doesn't seem to show any errors. But I have noticed something I didn't see before. It tried to boot from mmc, failed and booted from flash; I then mounted /dev/mmcblk0p2 on /opt and did "ls", which gave me an "input/output" error on /opt/bin. So it looks like it tried to read from the mmc card's bin directory but failed, which created something bad in the filesystem. Doing "fsck /dev/mmcblk0p2" would fix any errors, but the errors would return upon next reboot.

Originally Posted by fanoush View Post
You may also try to test if it is some limitation/bug of uclibc system in initfs. As root you may run
Code:
chroot /mnt/initfs
this will switch to the system used at early boot time so you can try mounting the card there and see if everything works too.
Doing this seems to generate zero errors. I'm thinking more and more it's a compatibility problem with the card itself. I'm going to order a different brand of 8gb SDHC card and see if it makes any difference.