ETH0 wifi on FSO not working

[alex at nanocom.co.il]

hi

i have problem on the last FSO Milestone  i cnot get the wifi to work

i dont have the eth0 on iwconfig and

and all the application like "i/o and tele"not working i get error

how can i fix it ?



----- Original Message ----- 
From: <support-request at lists.openmoko.org>
To: <support at lists.openmoko.org>
Sent: Wednesday, February 11, 2009 1:00 PM
Subject: support Digest, Vol 8, Issue 21


> Send support mailing list submissions to
> support at lists.openmoko.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.openmoko.org/mailman/listinfo/support
> or, via email, send a message with subject or body 'help' to
> support-request at lists.openmoko.org
>
> You can reach the person managing the list at
> support-owner at lists.openmoko.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of support digest..."
>
>
> Today's Topics:
>
>   1. [FSO] Milestone 5, uBoot and SD, any success? (Olivier Migeot)
>   2. Re: [FSO] Milestone 5, uBoot and SD, any success? (Kosa)
>   3. Re: [FSO] Milestone 5, uBoot and SD, any success?
>      (Werner Almesberger)
>   4. Re: [FSO] Milestone 5, uBoot and SD, any success? (Kosa)
>   5. Re: [FSO] Milestone 5, uBoot and SD, any success? (Marc Bantle)
>   6. Re: Power Adaptor. (Craig Woodward)
>   7. Freerunner still for sale (me too) (Craig Woodward)
>   8. Re: [FSO] Milestone 5, uBoot and SD, any success? (Olivier Migeot)
>   9. Re: [FSO] Milestone 5, uBoot and SD, any success? (Andy Green)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 10 Feb 2009 16:49:50 +0100
> From: Olivier Migeot <larrycow at gmail.com>
> Subject: [FSO] Milestone 5, uBoot and SD, any success?
> To: Support for Openmoko Device Owners <support at lists.openmoko.org>
> Message-ID:
> <389eeb980902100749j752e8814ka66ce6496f2f7685 at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> 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
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 10 Feb 2009 11:41:40 -0600
> From: Kosa <kosa at piradio.org>
> Subject: Re: [FSO] Milestone 5, uBoot and SD, any success?
> To: Support for Openmoko Device Owners <support at lists.openmoko.org>
> Message-ID: <4991BC54.4070400 at piradio.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
>
> 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
> user at XXXXX ~/freerunner/$ ./neocon -t 30 /dev/ttyACM0
> wich took me to the nand interface. It lloks something like this:
>
>
> user at XXXXX:~/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 0x32000000 ${sd_image_name}\;
> bootm 0x32000000
>
> 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
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 10 Feb 2009 17:12:38 -0200
> From: Werner Almesberger <werner at openmoko.org>
> Subject: Re: [FSO] Milestone 5, uBoot and SD, any success?
> To: Support for Openmoko Device Owners <support at lists.openmoko.org>
> Message-ID: <20090210191238.GW18025 at almesberger.net>
> Content-Type: text/plain; charset=us-ascii
>
> 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 0x32000000 ${sd_image_name}\;
>> bootm 0x32000000
>
> 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
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 10 Feb 2009 14:58:33 -0600
> From: Kosa <kosa at piradio.org>
> Subject: Re: [FSO] Milestone 5, uBoot and SD, any success?
> To: Support for Openmoko Device Owners <support at lists.openmoko.org>
> Message-ID: <4991EA79.8000307 at piradio.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
>
> 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 0x32000000 ${sd_image_name}\;
>>> bootm 0x32000000
>>
>> 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
>
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 11 Feb 2009 00:11:54 +0100
> From: Marc Bantle <openmoko at rcie.de>
> Subject: Re: [FSO] Milestone 5, uBoot and SD, any success?
> To: Support for Openmoko Device Owners <support at lists.openmoko.org>
> Message-ID: <499209BA.5080800 at rcie.de>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> 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 0x32000000 /boot/uImage-mmc2\; bootm 0x32000000
> where bootargs_base is create by
> GTA02v6 #setenv bootargs_base glamo_mci.sd_idleclk=1
> glamo_mci.sd_max_clk=12500000 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
>
>
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Tue, 10 Feb 2009 19:08:34 -0500
> From: Craig Woodward <woody at rochester.rr.com>
> Subject: Re: Power Adaptor.
> To: Support for Openmoko Device Owners <support at lists.openmoko.org>
> Message-ID: <20090211000834.WGGI5.73428.root at hrndva-web07-z01>
> Content-Type: text/plain; charset=utf-8
>
> I'm sure the charger has a cap or two in it.  Most transformers do in 
> order to help rectify the AC current down to DC.  If you touch them 
> shortly after unplugging you may get a minor shock.  This is true of 
> almost all AC to DC converter bricks.
>
> ---- Chris Syntichakis <chris at c-64.mobi> wrote:
>
> =============
>
> Hi,
>
> I had a nice experience with the power adaptor. I just charged the FR and
> after this, I took of the adaptor from the mains. Then accidentally, I
> touched both the pins of the plug (of the adaptor) and guess that.. I felt 
> a
> small shock!
>
> Now, what's this? Bad construction? of they forgot to put a some 
> diodes...?
>
> chris
> -- 
> View this message in context: 
> http://n2.nabble.com/Power-Adaptor.-tp2285864p2285864.html
> Sent from the Openmoko Support mailing list archive at Nabble.com.
>
>
> _______________________________________________
> support mailing list
> support at lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 11 Feb 2009 0:18:18 +0000
> From: Craig Woodward <woody at rochester.rr.com>
> Subject: Freerunner still for sale (me too)
> To: Support for Openmoko Device Owners <support at lists.openmoko.org>
> Message-ID: <20090211001818.1Z14T.73515.root at hrndva-web07-z01>
> Content-Type: text/plain; charset=utf-8
>
>
> Looks like I'm selling too.
>
> Here's the deal you get with me:
>
> o Full box kit (box/foam, stylus, 512k uSD, power block/adapters, etc)
> o GTA02v5 - great condition, no bounce or major gsm hum found.
> o External battery charger, not the best but works, just in case.
> o GPS external antenna (FR plug, 3' cord, 1"x1"x?" antenna).
> o 2Gb uSD card w/ SD converter & USB reader.
>
> Phone currently has Andriod Koolu Beta 3 installed and running.
> 2Gb uSD card had Debain installed, bootable from NAND menu.
>
> I'd love to get $350 for the whole kit shipped, but will consider 
> reasonable offers.
> US/Canada only please, prefer paypal for funds transfer.
>
>
>
> ------------------------------
>
> Message: 8
> Date: Wed, 11 Feb 2009 11:02:33 +0100
> From: Olivier Migeot <larrycow at gmail.com>
> Subject: Re: [FSO] Milestone 5, uBoot and SD, any success?
> To: Support for Openmoko Device Owners <support at lists.openmoko.org>
> Message-ID:
> <389eeb980902110202x1b2f20e0kee8fe1663c81cc13 at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Wed, Feb 11, 2009 at 12:11 AM, Marc Bantle <openmoko at 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 9>&0 </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.
>
> -- 
> Olivier
>
>
>
> ------------------------------
>
> Message: 9
> Date: Wed, 11 Feb 2009 15:52:26 +0530
> From: Andy Green <andy at openmoko.com>
> Subject: Re: [FSO] Milestone 5, uBoot and SD, any success?
> To: Support for Openmoko Device Owners <support at lists.openmoko.org>,
> Angus Ainslie <nytowl at openmoko.org>
> Message-ID: <4992A6E2.1070509 at openmoko.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> -----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 <openmoko at 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 9>&0 </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 at lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>
>
> End of support Digest, Vol 8, Issue 21
> **************************************
>