Re: [FSO] Milestone 5, uBoot and SD, any success?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Wed, Feb 11, 2009 at 12:11 AM, Marc Bantle openm...@rcie.de wrote: | | Until current rootfs' get fixed, I dropped the 'ro' option in | the boot options. | | Thanks to all of you for you help. But I tried something else : Marek | Lindner just provided the steps for fixing the image. Here it is: | | Not sure whether somebody was able to properly fix it or not. We (Chris and me) | just ran into this issue and created a fix for the mount script. | The /etc/init.d/checkroot.sh file in line 24 is the reason for the problem. It | complains about a wrong file descriptor here: exec 90 /etc/fstab | I removed the 2 exec lines (line 24 and line 85) and added a /etc/fstab | at the end of line 84. | | It worked for me. It'd be great if we can get that change or something like it in the upstream that these images come from. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmSpuEACgkQOjLpvpq7dMrjcwCfRjc484sHPqQw0BoCUyL5NkUS lsAAn0J7duvLyNFWrKAu/HiepQTYE8iD =Hv7T -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Milestone 5, uBoot and SD, any success?
Andy Green wrote: Somebody in the thread at some point said: | On Wed, Feb 11, 2009 at 12:11 AM, Marc Bantle openm...@rcie.de wrote: | | Until current rootfs' get fixed, I dropped the 'ro' option in | the boot options. | | Thanks to all of you for you help. But I tried something else : Marek | Lindner just provided the steps for fixing the image. Here it is: | | Not sure whether somebody was able to properly fix it or not. We (Chris and me) | just ran into this issue and created a fix for the mount script. | The /etc/init.d/checkroot.sh file in line 24 is the reason for the problem. It | complains about a wrong file descriptor here: exec 90 /etc/fstab | I removed the 2 exec lines (line 24 and line 85) and added a /etc/fstab | at the end of line 84. | | It worked for me. It'd be great if we can get that change or something like it in the upstream that these images come from. Rename the file from checkroot.sh to checkroot, and it achieves the same effect (it is run in a shell instead of being sourced). As I said previously, this was an upstream OE bug which made it's way into FSO MS5 and has since been fixed upstream on OE.dev -- Rod ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Milestone 5, uBoot and SD, any success?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Rename the file from checkroot.sh to checkroot, and it achieves the same | effect (it is run in a shell instead of being sourced). | | As I said previously, this was an upstream OE bug which made it's way | into FSO MS5 and has since been fixed upstream on OE.dev Great, I'll just tell people to update their rootfs then. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmTpcYACgkQOjLpvpq7dMq6nQCdEQwX0IIuRj259bxXAGush6ku 3pwAn0gZkNznoAVxwV8OIkjPg3jGvuII =WCx/ -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Milestone 5, uBoot and SD, any success?
On Thu, 2009-02-12 at 09:59 +0530, Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Rename the file from checkroot.sh to checkroot, and it achieves the same | effect (it is run in a shell instead of being sourced). | | As I said previously, this was an upstream OE bug which made it's way | into FSO MS5 and has since been fixed upstream on OE.dev Great, I'll just tell people to update their rootfs then. - -Andy I think Mickey checked this into the milestone 5 branch tonight so hopefully it should hit the autobuilders and feeds tomorrow. http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/h=fso/milestone5 Angus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[FSO] Milestone 5, uBoot and SD, any success?
Hello ev'ryone. It's been a while since Freesmartphone's latest milestone (the so-called milestone 5) is out. However, and as willing as I am to test it, I still didn't manage to get past the root not remouted read-write as it should problem. I saw a lot of discussion about how to fix this with Qi. As I'm still too cautious to test Qi yet (after all, this is my main phone we're talking about... testing one piece of potentially unstable software at a time is well enough for me), I'm wondering whether anybody had success with that milestone and the following setup (or something close): - GTA02 - images (.tar.gz and .bin) from the fso-stable tree. - basic uBoot (no update whatsoever since purchase) - and of course, booting on the SD card (once again, I don't want to break every part at once) If, by any chance, somebody succeeded in something similar, would he mind explaining how he did? And if anybody from the FSO team passes by : is there some kind of milestone 5.1 expected (fixing that kind of problem, for instance), or should we wait for milestone 6? Thanks a lot. Regards, -- Olivier ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Milestone 5, uBoot and SD, any success?
Olivier Migeot escribió:
Hello ev'ryone.
It's been a while since Freesmartphone's latest milestone (the
so-called milestone 5) is out. However, and as willing as I am to
test it, I still didn't manage to get past the root not remouted
read-write as it should problem.
I saw a lot of discussion about how to fix this with Qi. As I'm still
too cautious to test Qi yet (after all, this is my main phone we're
talking about... testing one piece of potentially unstable software at
a time is well enough for me), I'm wondering whether anybody had
success with that milestone and the following setup (or something
close):
- GTA02
- images (.tar.gz and .bin) from the fso-stable tree.
- basic uBoot (no update whatsoever since purchase)
- and of course, booting on the SD card (once again, I don't want to
break every part at once)
If, by any chance, somebody succeeded in something similar, would he
mind explaining how he did?
And if anybody from the FSO team passes by : is there some kind of
milestone 5.1 expected (fixing that kind of problem, for instance), or
should we wait for milestone 6?
Thanks a lot.
Regards,
This is my first try on FSO and I like it so far. I had the same
problem with u-boot (didn't try Qi yet) but after some reading
and testing I made it work as follows:
I downloaded and installed neocon from here [1]:
The I ran
u...@x ~/freerunner/$ ./neocon -t 30 /dev/ttyACM0
wich took me to the nand interface. It lloks something like this:
u...@x:~/freerunner/neocon$ ./neocon -t 30 /dev/ttyACM0
[Open /dev/ttyACM0]
In:usbtty
Out: usbtty
Err: usbtty
PCB rev: 0x000
Power: 0mA
GTA02v5 #
Then
GTA02v5 # printenv (which prints all of the entrys in nand boot menu)
I the next command you set the name and menu_X entry as you wush, but
be aware of what you get from #printenv output. I mean, if you already
have an menu_1 entry, using that will overwrite the existing one, so
I suggest you use a none existing number to test it.
Well, next:
GTA02v5 # setenv menu_10 Boot for FSO V: setenv bootargs
${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5
${mtdparts} rw\; mmcinit\; fatload mmc 1 0x3200 ${sd_image_name}\;
bootm 0x3200
Note I'm using menu_10, couse I have several microsd running different
distros, and some of them have even more than one distro.
Also note it expects rootfs to be and ext2 partition, and it is on the
second partition on the microsd. (the first one is for the kernel). I
think the most important part, the one wich makes the difference, is the
rw option.
Then you save the entry to nand:
GTA02v5 # seveenv
Then you power the neo off and get into nand by pressing power + aux.
It is a lillte bit tricky to start neocon, but it does work. If it does
not connect you will get an [closed] message insted of the one I mention
before, but then you can just unplug the neo, get out from neocon by
taping ~. and try again. What I do is first get into nand, then plug the
neo and finnaly start neocon.
Look at the neocon's wiki page for more options[2]
Hope it helps.
Kosa
- Un mundo mejor es posible -
[1] http://svn.openmoko.org/developers/werner/neocon/
[2] http://wiki.openmoko.org/wiki/NeoCon
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Milestone 5, uBoot and SD, any success?
Kosa wrote:
GTA02v5 # setenv menu_10 Boot for FSO V: setenv bootargs
${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5
${mtdparts} rw\; mmcinit\; fatload mmc 1 0x3200 ${sd_image_name}\;
bootm 0x3200
A quick remark: You probably want to escape the dollar signs as well.
Otherwise, you expand the variables at the moment you enter the
command and if you want to change bootargs_base or sd_image_name
later, you have to remember to redo the menu line as well.
- Werner
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Milestone 5, uBoot and SD, any success?
Werner Almesberger escribió:
Kosa wrote:
GTA02v5 # setenv menu_10 Boot for FSO V: setenv bootargs
${bootargs_base} rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5
${mtdparts} rw\; mmcinit\; fatload mmc 1 0x3200 ${sd_image_name}\;
bootm 0x3200
A quick remark: You probably want to escape the dollar signs as well.
Otherwise, you expand the variables at the moment you enter the
command and if you want to change bootargs_base or sd_image_name
later, you have to remember to redo the menu line as well.
- Werner
Another quick remark: i wrote #seveenv, but it's #saveenv :-P
Kosa
- Un mundo mejor es posible -
Another
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Milestone 5, uBoot and SD, any success?
Olivier Migeot schrieb:
- GTA02
- images (.tar.gz and .bin) from the fso-stable tree.
- basic uBoot (no update whatsoever since purchase)
- and of course, booting on the SD card (once again, I don't want to
break every part at once)
I succesfully use
openmoko-fso-image-glibc-ipk--20090202-om-gta02.rootfs.tar.gz
and
uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin
with an u-boot environment, that can be create like this:
GTA02v6 #setenv menu_1 Boot from SD 2: setenv bootargs \${bootargs_base}
rootfstype=ext2 root=/dev/mmcblk0p2 \${mtdparts} \; mmcinit\; sleep
2\; ext2load mmc 0:1 0x3200 /boot/uImage-mmc2\; bootm 0x3200
where bootargs_base is create by
GTA02v6 #setenv bootargs_base glamo_mci.sd_idleclk=1
glamo_mci.sd_max_clk=1250 rootfstype=jffs2 root=/dev/mtdblock6
console=ttySAC2,115200 console=tty0 loglevel=5 rootdelay=5 regular_boot
Generally I don't change my boot environment.
All I do is copy the kernel into partition1/boot directory
and create symlink to it (e.g. /boot/uImage-mmc2).
The rootfs is placed into the according partition (e.g. /dev/mmcblk0p2).
Note: I use a SanDisk 16G card, which needs reduction of
glamo_mci.sd_max_clk.
Until current rootfs' get fixed, I dropped the 'ro' option in
the boot options.
I hope this helps a bit.
Cheers, Marc
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
