I recently found a german (sry) description of someone who manged to
get the WLan up and running:


As far as I understand he added:

ifdown usb0

to the start section and

ifup usb0

to the stop section of the shell script propagated by the openmoko wiki.

I'll give it a try ;o)


On Wed, Jul 16, 2008 at 8:03 PM, julien cubizolles <[EMAIL PROTECTED]> wrote:
> Le mercredi 16 juillet 2008 à 11:56 -0500, Stephen Shelton a écrit :
>> I've been beating my head against the wall trying to get my FR to connect to 
>> any
>> secured wireless AP. It has no trouble connecting if there is no encryption, 
>> but
>> I've had no luck otherwise.
>> If anyone has had a better experience than me, perhaps you could take a look 
>> at
>> the "GTA02 WLAN" page on the wiki (http://wiki.openmoko.org/wiki/GTA02_WLAN) 
>> and
>> contribute or clean up.
>> Most specifically, I keep getting messages such as "ioctl[SIOCSIWENCODEEXT]"
>> which would lead me to believe the kernel is unhappy...
> I could connect to my WPA2 protected wlan following the indications on
> the above page even though I was getting the same message.
> But it was just once, when I got the Freerunner. Now, after several opkg
> upgrades (don't know if it's related thoug), I can't get it to get a
> lease anymore.
> I tried running wpa_supplicant in foreground (ie without the -B swith)
> to catch additionnal error messages. I get :
> ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
> After that, udhcpc0 can't get a lease and goes
> Sending discover...
> Sending discover...
> Sending discover...
> run-parts: /etc/udhcpc.d/99avahi-autoipd exited with code 1
> forever...
> Julien.
> _______________________________________________
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community

spread the word ... see www.browsehappy.com ;o)

Calvin: Weekends don't count unless you spend them doing something
completely pointless.

Join the Greater IBM Connection (http://www.xing.com/premiumgroup-6291.d26b7d)

Openmoko community mailing list

Reply via email to