I suppose you didn't need to patch the SDG bootloader as you put the needed parameters in the "boot options" compiled in the kernel, and told it to override any parameter passed by the bootloader. Can you confirm?
I'd be defintely interested in having a look at your kernel .config and extra kernel boot parameters, if you were willing to share them :-) I didn't even think the hx4700 could handle SD-HC CARDS.. that would be good news for me! Enrico James A. Langbridge wrote: > Hi, > > Yes, I did this a while ago. I have an hx4700 that can boot from internal > NAND, SD (GPE) and SD (Opie). I did this by adding a CompactFlash card, > only for the bootloader, and the main partitions were on a 4Gb SD-HC card. > With this technique, I didn't need to patch the SDG bootloader. Do you want > me to root through my files? > > > James A. Langbridge > Packetfury.net > -- The urgent is done, the impossible ongoing. For miracles, expect a small > delay. > > > On 29 June 2012 16:19, wiseLYNX <wiselynx.na...@fastwebnet.it> wrote: > >> hello everybody, >> >> my struggle to get my hx4700 in shape still goes on.. >> >> now I'd want to have its root filesystem on an SD card, while booting >> from SDG bootloader, for two reasons: >> - most images are quite bigger that what the internal NAND could store >> - while I'm experimenting, I'm reflashing the image over and over, and >> it's a long, boring task; moreover, I'd really want to spare some write >> cycles on the NAND, while an external SD card is expendable >> >> to do achieve that, I "hex-patched" the sdg bootloader so that it >> assumes the root filesystem on /dev/mmcblk0p1 (ext2 formatted SD) >> instead of /dev/mtdxxxx (can't remember the name, it's not important >> now). This works quite well, but I get a kernel panic when it does try >> to mount the root filesystem and it doesn't find it. >> >> I already tried adding the "rootwait" parameter to kernel, only to have >> a nice message about waiting the root device to show up, which never >> happens. >> >> I compiled everything I think is needed statically, which includes "MMC >> block device driver" and "Toshiba Mobile IO controller (TMIO)" (if >> helpful, I can send the kernel .config I'm using, I'm not sending it now >> as I'm not sure it's ok with the mailing list policy). I can see in logs: >> >> mmc0: mmc_try_rescan_freq: trying to init card at 400000 Hz >> mmc0 at 0xc4834800 irq 162 >> >> but it doesn't seem to "see" the partitions. >> >> Any hint? Anyone already did something similar? Is it even possible to >> do what I'm trying to do? >> >> thank you very much everybody >> >> Enrico >> >> _______________________________________________ >> Angstrom-distro-users mailing list >> Angstrom-distro-users@linuxtogo.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users >> >> > _______________________________________________ > Angstrom-distro-users mailing list > Angstrom-distro-users@linuxtogo.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users > _______________________________________________ Angstrom-distro-users mailing list Angstrom-distro-users@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
