Havint trouble to trying out om2009 on sD card

[Jose Luis Perez Diez]

El Wednesday, 6 de May de 2009 09:22:28 Laszlo KREKACS va escriure:
> On Wed, May 6, 2009 at 8:51 AM, David Reyes Samblas Martinez
>
> <david at tuxbrain.com> wrote:
> > try to add "rw" in the options of the append file,
>
> root at om-gta02 /media/mmcblk0p2/boot $ cat append-GTA02
> rw
> loglevel = 8

The append-GTA02 file should is append to the end of the kernel parameter so 
no vertical whitespace should be used.

In a recent Qi /proc/cmdline for a kernel on the first partion of uSD is:

loglevel=4 console=tty0 console=ttySAC2,115200 init=/sbin/init ro \
mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(qi),\
0x00040000(depr-ub-env),0x00800000(kernel),0x000a0000(depr),\
0x00040000(identity-ext2),0x0f6a0000(rootfs) \
g_ether.host_addr=00:1F:11:01:1F:C2 g_ether.dev_addr=00:1F:11:01:1F:C2 \
root=/dev/mmcblk0p1 rootdelay=1

If the freeruner is booted holding the powerbutton Qi boots with loglevel=8
>
> root at om-gta02 /media/mmcblk0p2/boot $ exit
>
> But no luck so far:
> [   0.0000] Uknown boot option `g_ether.host_addr=00:1F:11:01:5D:38`:
> ignoring [   0.0000] Uknown boot option

this warning series only  mean that the kernel has g_ether as a module

> ....
> Please wait: booting...
> [21474566.875000] regulator: Unable to get requested regulator: SD_3V3
> [21474566.875000] s3c2440-sdi s3c2440: Regulator for SD_3V3 unavilable
> {cursor blinking}
>
> > btw no need of fat partition if you are using Qi
>
> The wiki wasnt clear enough
> (http://wiki.openmoko.org/wiki/Booting_from_SD), and wanted to
> stay on the safe side.

In fact Qi ignores fat partitions

> If I partitions right now, i would simply create three ext2
> partitions, as Qi can boot up to 3 partitions from SD
> card.
>
> Is there somewhere a ready-made .tar.gz for Qi, which I simply need to
> unzip to an ext2 partition and no further editing?
> Just to be sure, that Qi can boot, and works as expected. (so rule out
> one source of problem)

I don't think that build system makes the symbolic link from /boot/uImage 
to /boot/uImage-GTA02.bin and I don't know what OE recipe is responsible for 
that change.