On Tuesday 07 September 2010, jeremy jozwik wrote: > On Tue, Sep 7, 2010 at 10:17 AM, jeremy jozwik <[email protected]> wrote: > > On Tue, Sep 7, 2010 at 9:18 AM, Davide Scaini <[email protected]> wrote: > >> really no idea... .29 kernel series should work flawlessy. > >> two hints (maybe idiot): > >> - install modules that come with your selected kernel > > dont know anything about these kernel modules. i should not need to do > that with a fresh kernel right? like old stable kernels saved locally > on my machine that were working should still work right?
The kernel should have everything it needs to access the SD as without it booting with rootfs on SD would be rather tricky. Same goes for ext3. Having mismatched kernel and modules will lead to other things not working properly, but shouldn't prevent you accessing the SD. If you have an old known-stable kernel that used to be able to access SD but no longer can then I would guess it's a hardware problem. I usually boot from SD, but I do have an old shr-testing installed in NAND, and it can access my SD just fine. It looks like the images are still available in too: http://build.shr-project.org/shr-testing/images/om-gta02/ shr-lite-eglibc-ipk--20100415-om-gta02.rootfs.jffs2 uImage-2.6.29-oe11+gitr119861+a15608f241a40b41fed5bffe511355c2067c4e88-r8-om- gta02.bin You could also try opening a terminal connection to u-boot and seeing what the result of the mmcinit command is, and whether it can list files in your ext3 partition. _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
