Re: [shr-u] wifi timeout with mokonnect
On Thu, Aug 20, 2009 at 12:16:02AM +0200, Bernhard Reiter wrote: Am Sonntag, den 16.08.2009, 21:00 +0200 schrieb Rask Ingemann Lambertsen: Someone needs to sit down with the firmware interface specification (i.e. from the existing driver?) and match it up with the Linux network device API (make htmldocs) and then write a new driver. any takers? at least for a detailed bug report? rask, what about yourself? I will not have the time at least until the gta02-core is out. It's something that won't have basic functionality after a weekend because - The firmware is said to be a pain to work with, - I'm unfamiliar with the SDIO stack for communication with the card, - I'm unfamiliar with the IEEE 802.11 network layer, - I'm not yet using WLAN, but at least the 802.11 card that was collecting dust on a table for a few months has now found its way into a PCI slot. -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
Am Sonntag, den 16.08.2009, 21:00 +0200 schrieb Rask Ingemann Lambertsen: What little I've seen of that code does not look promising. The author didn't understand the netif_stop_queue()/netif_wake_queue() calls, so who knows what else might have gone wrong? Someone needs to sit down with the firmware interface specification (i.e. from the existing driver?) and match it up with the Linux network device API (make htmldocs) and then write a new driver. any takers? at least for a detailed bug report? rask, what about yourself? bernhard ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Sat, Aug 15, 2009 at 01:14:37AM +0400, Paul Fertser wrote: I really hoped Werner would take care of that but he's too busy with gta02-core project currently and we lack another expert in Wifi in general and Atheros's crappy code in particular :( What little I've seen of that code does not look promising. The author didn't understand the netif_stop_queue()/netif_wake_queue() calls, so who knows what else might have gone wrong? Someone needs to sit down with the firmware interface specification (i.e. from the existing driver?) and match it up with the Linux network device API (make htmldocs) and then write a new driver. -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
arne anka openm...@ginguppin.de writes: and the fr is shock frozen. not really convincing a performance. Reproduced it. Thanks for the bugreport, will try to investigate. Sorry for misinformation, i guess i did something slightly different before so it didn't result in kernel panic. Sorry :( -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
Sorry for misinformation, i don't think misinformation is the right word here -- at least it helped me to understnad, what is supposed to be done and to happen. and it looks like that instigated other people as well to try again. if you or someone else can make something from the output, i'd be more than happy. btw: what bothers me, with the preinstalled 2007.X wifi worked and did so with kernel 2.6.24, what broke that in 2.6.2[89]? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
The way I got around this is to use two scripts - the first just handles spawning wpa_suppliocant and stops at a read statement - then hitting a return key exits the script. The various rm and kill commands are to cleanup before and after - needed for reliable and repeatable connections! This works with AP's wpa2, wep and no encryption at all (I use kernel 2.6.28 on shr-u, but it works with 2.6.29 as well) The second script just calls the first using fsoraw - I use a desktop icon calling script2 using xterm -e script2 script1: #!/bin/sh killall -9 wpa_supplicant udhcpc sleep 1 rm /var/run/wpa_supplicant/eth0 echo wifi starting! /usr/sbin/wpa_supplicant -B -t -i eth0 -Dwext -c /etc/wpa_supplicant/wpa_supplicant.conf sleep 8 ifup eth0 route del default gw 192.168.0.200 read ifdown eth0 killall -9 wpa_supplicant udhcpc echo WiFi off script2: #!/bin/sh export USER=root export HOME=/home/root cd /home/root ifdown eth0 sleep 1 /usr/bin/fsoraw -s -r WiFi,CPU -- /home/root/mefiles/wifi echo Done! On Fri, 2009-08-14 at 20:46 +0200, arne anka wrote: well, i did right now # fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf which resulted in ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported CTRL-EVENT-SCAN-RESULTS Trying to associate with XX:XX:.. (SSID='myssid' freq=2422 MHz) Association request to the driver failed Associated with XX:XX... WPA: Key negotiation completed with XX:XX:... [PTK=TKIP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to XX:XX:XX:... completed (auth) [id=2 id_str=] ok, dhclient eth0 opbtained an ip. but so fra i got vene without fsoraw the last time. let's see, what happens in a second attempt. killing 'fsoraw ...' with CTRL+C ... CTRL-EVENT-TERMINATING - signal 2 received ioctl[SIOCSIWESSID]: Invalid argument ioctl[SIOCSIWMLME]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported hmm. ok, # fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf and ... ioctl[SIOCGIWRANGE]: Input/output error ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCGIWSCAN]: Input/output error ioctl[SIOCSIWSCAN]: Input/output error Failed to initiate AP scan. ioctl[SIOCGIWSCAN]: Input/output error ioctl[SIOCSIWSCAN]: Input/output error Failed to initiate AP scan. ioctl[SIOCGIWSCAN]: Input/output error ioctl[SIOCSIWSCAN]: Input/output error Failed to initiate AP scan. ioctl[SIOCGIWSCAN]: Input/output error ioctl[SIOCSIWSCAN]: Input/output error Failed to initiate AP scan. ioctl[SIOCGIWSCAN]: Input/output error ioctl[SIOCSIWSCAN]: Input/output error ioctl[SIOCGIWSCAN]: Input/output error ... indefinitely. # killall wpa_suplicant and the fr is shock frozen. not really convincing a performance. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- William Kenworthy bi...@iinet.net.au Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
well, i did right now # fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf which resulted in ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported CTRL-EVENT-SCAN-RESULTS Trying to associate with XX:XX:.. (SSID='myssid' freq=2422 MHz) Association request to the driver failed Associated with XX:XX... WPA: Key negotiation completed with XX:XX:... [PTK=TKIP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to XX:XX:XX:... completed (auth) [id=2 id_str=] ok, dhclient eth0 opbtained an ip. but so fra i got vene without fsoraw the last time. let's see, what happens in a second attempt. killing 'fsoraw ...' with CTRL+C ... CTRL-EVENT-TERMINATING - signal 2 received ioctl[SIOCSIWESSID]: Invalid argument ioctl[SIOCSIWMLME]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported hmm. ok, # fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf and ... ioctl[SIOCGIWRANGE]: Input/output error ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCGIWSCAN]: Input/output error ioctl[SIOCSIWSCAN]: Input/output error Failed to initiate AP scan. ioctl[SIOCGIWSCAN]: Input/output error ioctl[SIOCSIWSCAN]: Input/output error Failed to initiate AP scan. ioctl[SIOCGIWSCAN]: Input/output error ioctl[SIOCSIWSCAN]: Input/output error Failed to initiate AP scan. ioctl[SIOCGIWSCAN]: Input/output error ioctl[SIOCSIWSCAN]: Input/output error Failed to initiate AP scan. ioctl[SIOCGIWSCAN]: Input/output error ioctl[SIOCSIWSCAN]: Input/output error ioctl[SIOCGIWSCAN]: Input/output error ... indefinitely. # killall wpa_suplicant and the fr is shock frozen. not really convincing a performance. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: [shr-u] wifi timeout with mokonnect
arne anka wrote: well, i did right now # fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf which resulted in [snip a lot] indefinitely. I get excatly the same. Only once have I managed to get a DHCP lease, but the network failed just after that. What has gone wrong with WiFi during the summer? In april, I had an almost working phone with almost stable WiFi - at least the first connect after boot was never a problem. Now I got it buzz-fixed, moved to the other end of the country and had holiday and when I return WiFi is broken and I have to use slow USB net. Some one must know what has changed? New kernel? /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
Peter Mogensen a...@bigendian.dk writes: Some one must know what has changed? New kernel? Well, i must admit i collected several reports that despite huge gains from moving to upstream SDIO stack there're some regressions. Several people reported they can't connect to the networks they were able to use before no matter what they try. I really hoped Werner would take care of that but he's too busy with gta02-core project currently and we lack another expert in Wifi in general and Atheros's crappy code in particular :( Life is unfair :-/ -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Wednesday 12 August 2009 11:19:55 am you wrote: Adam, i can't see a decent reason for you to omit the list from CC. On Wed, Aug 12, 2009 at 11:09:35AM -0400, Adam Jimerson wrote: On Wednesday 12 August 2009 04:57:48 am you wrote: Adam Jimerson vend...@gmail.com writes: On Tuesday 11 August 2009 02:41:53 am Paul Fertser wrote: Please try wpa_supplicant method as described on FSO_Resources wikipage and report the results. I know wpa_supplicant stopped working for me, I don't know what went wrong but when I started using mokonnect/connman it worked with no hassles with the .29 kernel with out the test patches installed. AFAIK either you're not using any WPA networks or you use wpa_supplicant, connman can't affect that. That is right all the networks I use, or try to use, are just MAC filtered which wpa_supplicant use to work fine for but it stopped getting DHCP for some reason and the same goes for Mokonnect/connman wpa_supplicant never gets DHCP, that's something a dhcp client should be used for. Also you don't say if you tried the maxperf trick or not. I know that wpa_supplicant doesn't handle DHCP but when I was using it then the ifup command would say that it connected, didn't return an error, but DHCP would always fail but it never did this before. Then I switched to mokonnect after learning about it and it worked right after install until it got updated from the one in the SHR feeds which I'm guessing something broke. -- We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure. Karl Popper signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
Adam Jimerson vend...@gmail.com writes: wpa_supplicant never gets DHCP, that's something a dhcp client should be used for. Also you don't say if you tried the maxperf trick or not. I know that wpa_supplicant doesn't handle DHCP but when I was using it then the ifup command would say that it connected, didn't return an error, but DHCP would always fail but it never did this before. ifup command is unnecessary here and quite possibly messes something up. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
I know that wpa_supplicant doesn't handle DHCP but when I was using it then the ifup command would say that it connected, didn't return an error, but DHCP would always fail but it never did this before. ifup command is unnecessary here and quite possibly messes something up. ok, i bite. _how_ is it supposed to be done? enabling wifi manually is not advised ifup is not necessary and might be messing up. please, paul, give me (and probably others too) a plain working example how to get up and down wifi repeatedly and reliable. i don't have mokoconnect available, connman does not work for me on debian and the two or three other managers mentioned here and there are not available to me. the most basic way would probably be /etc/network/interfaces so, how should that file loook like, how (if ifup is not advisable) is the iface to get up and down? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Thursday 13 August 2009 10:55:38 am arne anka wrote: I know that wpa_supplicant doesn't handle DHCP but when I was using it then the ifup command would say that it connected, didn't return an error, but DHCP would always fail but it never did this before. ifup command is unnecessary here and quite possibly messes something up. ok, i bite. _how_ is it supposed to be done? enabling wifi manually is not advised ifup is not necessary and might be messing up. please, paul, give me (and probably others too) a plain working example how to get up and down wifi repeatedly and reliable. i don't have mokoconnect available, connman does not work for me on debian and the two or three other managers mentioned here and there are not available to me. the most basic way would probably be /etc/network/interfaces so, how should that file loook like, how (if ifup is not advisable) is the iface to get up and down? Same here I would like to know how to connect to a network without using the ifconfig commands -- We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure. Karl Popper signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
Adam Jimerson vend...@gmail.com writes: On Thursday 13 August 2009 10:55:38 am arne anka wrote: I know that wpa_supplicant doesn't handle DHCP but when I was using it then the ifup command would say that it connected, didn't return an error, but DHCP would always fail but it never did this before. ifup command is unnecessary here and quite possibly messes something up. _how_ is it supposed to be done? Same here I would like to know how to connect to a network without using the ifconfig commands 0. So, clean boot, you didn't touch resource policies in any way (SHR settings/mdbus/whatever). 1. Then ``vim /etc/wpa_supplicant/wpa_supplicant.conf'' and configure the way you need. 2. Then ``fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf'' and wait for it to associate. 3. ``dhclient eth0'' (or whatever your favourite client is) 4. enjoy If the step 2 or 3 fails, then 2.5 ``wmiconfig -i eth0 --power=maxperf'' HTH -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: [shr-u] wifi timeout with mokonnect
Paul Fertser wrote: Adam Jimerson vend...@gmail.com writes: Same here I would like to know how to connect to a network without using the ifconfig commands 0. So, clean boot, you didn't touch resource policies in any way (SHR settings/mdbus/whatever). 1. Then ``vim /etc/wpa_supplicant/wpa_supplicant.conf'' and configure the way you need. 2. Then ``fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf'' and wait for it to associate. 3. ``dhclient eth0'' (or whatever your favourite client is) 4. enjoy If the step 2 or 3 fails, then 2.5 ``wmiconfig -i eth0 --power=maxperf'' No luck... If I omit doing step 2.5 as step 1.5 eth0 just disappears after using step 2 (fsoraw). If I do step 2.5 just before fsoraw it just goes quoted below. I'm curious. WiFi used to be easy to get going. I just edited my wpa_supplicant.conf, added the wpa-conf to /etc/network/interfaces and did an ifup eth0. What went wrong? $ ./fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
Peter Mogensen a...@bigendian.dk writes: Paul Fertser wrote: Adam Jimerson vend...@gmail.com writes: Same here I would like to know how to connect to a network without using the ifconfig commands 0. So, clean boot, you didn't touch resource policies in any way (SHR settings/mdbus/whatever). 1. Then ``vim /etc/wpa_supplicant/wpa_supplicant.conf'' and configure the way you need. 2. Then ``fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf'' and wait for it to associate. 3. ``dhclient eth0'' (or whatever your favourite client is) 4. enjoy If the step 2 or 3 fails, then 2.5 ``wmiconfig -i eth0 --power=maxperf'' No luck... If I omit doing step 2.5 as step 1.5 eth0 just disappears after using step 2 (fsoraw). That's expected. Step 2.5 is to be done while wpa_supplicant is running. And step 3 too. So you just leave it running and do you stuff. From your output it looks like wpa_supplicant can't see any wireless network specified in your config... If I do step 2.5 just before fsoraw it just goes quoted below. No sense in trying it before fsoraw... I'm curious. WiFi used to be easy to get going. I just edited my wpa_supplicant.conf, added the wpa-conf to /etc/network/interfaces and did an ifup eth0. If you want to integrate fsoraw in networking scripts properly, it'd be cool. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
Bernhard Reiter ock...@raz.or.at writes: Am Dienstag, den 11.08.2009, 10:41 +0400 schrieb Paul Fertser: Please try wpa_supplicant method as described on FSO_Resources wikipage and report the results. ok, using fsoraw it seems to connect to the router (only the important part given here): CTRL-EVENT-SCAN-RESULTS Trying to associate with mac address (SSID='SSID' freq=2437 MHz) Associated with mac address WPA: Key negotiation completed with mac address [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to mac address completed (auth) [id=0 id_str=] But unfortunately, I still can't ping my router, nor can I ping the FreeRunner from my laptop either. You're supposed to somehow set IP for eth0 after that (usually with the help of DHCP client). I really wonder why it's not obvious :S Also some APs require wmiconfig -ieth0 --power=maxperf trick to work. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
Adam Jimerson vend...@gmail.com writes: On Tuesday 11 August 2009 02:41:53 am Paul Fertser wrote: Please try wpa_supplicant method as described on FSO_Resources wikipage and report the results. I know wpa_supplicant stopped working for me, I don't know what went wrong but when I started using mokonnect/connman it worked with no hassles with the .29 kernel with out the test patches installed. AFAIK either you're not using any WPA networks or you use wpa_supplicant, connman can't affect that. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Wed, Aug 12, 2009 at 12:56:26PM +0400, Paul Fertser wrote: Bernhard Reiter ock...@raz.or.at writes: Am Dienstag, den 11.08.2009, 10:41 +0400 schrieb Paul Fertser: Please try wpa_supplicant method as described on FSO_Resources wikipage and report the results. ok, using fsoraw it seems to connect to the router (only the important part given here): CTRL-EVENT-SCAN-RESULTS Trying to associate with mac address (SSID='SSID' freq=2437 MHz) Associated with mac address WPA: Key negotiation completed with mac address [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to mac address completed (auth) [id=0 id_str=] But unfortunately, I still can't ping my router, nor can I ping the FreeRunner from my laptop either. You're supposed to somehow set IP for eth0 after that (usually with the help of DHCP client). I really wonder why it's not obvious :S You're also supposed to have an SSID setup before using a DHCP client. At least for me that NEVER happens :| Also some APs require wmiconfig -ieth0 --power=maxperf trick to work. I always run that. Rui -- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Wed, Aug 12, 2009 at 11:39:18AM +0100, Rui Miguel Silva Seabra wrote: On Wed, Aug 12, 2009 at 12:56:26PM +0400, Paul Fertser wrote: Bernhard Reiter ock...@raz.or.at writes: Am Dienstag, den 11.08.2009, 10:41 +0400 schrieb Paul Fertser: Please try wpa_supplicant method as described on FSO_Resources wikipage and report the results. ok, using fsoraw it seems to connect to the router (only the important part given here): CTRL-EVENT-SCAN-RESULTS Trying to associate with mac address (SSID='SSID' freq=2437 MHz) Associated with mac address WPA: Key negotiation completed with mac address [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to mac address completed (auth) [id=0 id_str=] But unfortunately, I still can't ping my router, nor can I ping the FreeRunner from my laptop either. You're supposed to somehow set IP for eth0 after that (usually with the help of DHCP client). I really wonder why it's not obvious :S You're also supposed to have an SSID setup before using a DHCP client. At least for me that NEVER happens :| And before someone blames the wifi driver, mofi has no problem connecting (but mokonnect is what I wish). Rui -- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
i don't think i've ever got wifi to work I feel your pain :( ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
Adolph J. Vogel ajvo...@tuks.co.za writes: i don't think i've ever got wifi to work I feel your pain :( Try to do what's written on FSO_Resources wiki page and report the results. The wlan chip _is_ compatible with most APs and the proposed method of using it _does_ in fact work. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Mon, Aug 10, 2009 at 2:43 PM, Bernhard Reiterock...@raz.or.at wrote: hi, using shr-u and mokonnect, i get a timeout when trying to connect to my managed wpa-secured home wlan router (while it is trying to setup dhcp, though things work fine with my laptop). is this some well-known issue or do i have to investigate my setup? (any debugging hints?) and what is the rsn encryption option that i get by default after a network scan but can't select in the list of encryption ways? Hi Bernard, I'm try to address all wlan problems together and coding a wifi manager prototype, that at some point may evolve in a freerunner dedicated network manager with a splitted gui. Please try it and report if it solves your problem, if possible use a kernel with no wifi bugs. http://wiki.openmoko.org/wiki/NWA Regards Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
Adolph J. Vogel ajvo...@tuks.co.za writes: Im sorry if this is an obvious question, but what kernel is wifi bug free? There's no such kernel in existance. And wifi firmware is not bugfree and most probably will never be. Blame Canada^W Atheros. Or buy a decent usb wifi dongle. :( -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Wednesday 12 August 2009, Paul Fertser wrote: Adolph J. Vogel ajvo...@tuks.co.za writes: Im sorry if this is an obvious question, but what kernel is wifi bug free? There's no such kernel in existance. And wifi firmware is not bugfree and most probably will never be. Blame Canada^W Atheros. Or buy a decent usb wifi dongle. :( Given that 2.6.28/9 has had at least one kernel bug with wifi support on the FR it isn't unreasonable to ask whether the currently distributed kernels have all the known bug fixes applied. It wouldn't be the first time that known bug fixes haven't been applied in the shipping kernel. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Wed, Aug 12, 2009 at 03:04:26PM +0400, Paul Fertser wrote: Rui Miguel Silva Seabra r...@1407.org writes: On Wed, Aug 12, 2009 at 12:56:26PM +0400, Paul Fertser wrote: Bernhard Reiter ock...@raz.or.at writes: CTRL-EVENT-SCAN-RESULTS Trying to associate with mac address (SSID='SSID' freq=2437 MHz) Associated with mac address WPA: Key negotiation completed with mac address [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to mac address completed (auth) [id=0 id_str=] But unfortunately, I still can't ping my router, nor can I ping the FreeRunner from my laptop either. You're supposed to somehow set IP for eth0 after that (usually with the help of DHCP client). I really wonder why it's not obvious :S You're also supposed to have an SSID setup before using a DHCP client. At least for me that NEVER happens :| wpa_supplicant does that for you. I'm yet to see a single case when it couldn't. Somehow people keep missing the point... With Mokonnect that NEVER happens. Wifi works just fine, Mofi sets it up without a problem. I'm quite sure wpa_supplicat hand made config will work as well. Also some APs require wmiconfig -ieth0 --power=maxperf trick to work. I always run that. Eats battery like mad. I suggest using this only as a last resort. I know, it lasted two hours last I tried, but at least it's reliable :) Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Wed, Aug 12, 2009 at 03:09:44PM +0200, Adolph J. Vogel wrote: Rui, what kernel are you using? r...@om-gta02 ~ $ uname -a Linux om-gta02 2.6.29-rc3 #1 PREEMPT Sun Aug 2 12:17:54 CEST 2009 armv4tl unknown (which I think is the most recent uImage available on 2009/08/08). With the shr-image and uImage from 2009/07/21 it was the same. Rui -- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
2009/8/11 Rui Miguel Silva Seabra r...@1407.org: To me it has never worked, but never means in images 20090721 and 20090808 of shr-u It doesn't even bother to set the SSID, but I don't know who's really at fault here, mokonnect or connman. Anyway, connman is a real piece of crap (but NetworkManager is just marginally lesser crap) sprout from people with NIH sindrome who don't understand NM. does wifi work yet with newer kernels? i heard some time back that .29 had issues. i don't think i've ever got wifi to work ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
Robin Paulson robin.paul...@gmail.com writes: 2009/8/11 Rui Miguel Silva Seabra r...@1407.org: Anyway, connman is a real piece of crap (but NetworkManager is just marginally lesser crap) sprout from people with NIH sindrome who don't understand NM. does wifi work yet with newer kernels? i heard some time back that .29 had issues. i don't think i've ever got wifi to work .29 has issues but those in kernel are workaroundable. Those in firmware are independent from the kernel and are unlikely to be ever solved. Luckily they don't affect the majority of users. Please try wpa_supplicant method as described on FSO_Resources wikipage and report the results. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Tue, Aug 11, 2009 at 06:37:03PM +1200, Robin Paulson wrote: 2009/8/11 Rui Miguel Silva Seabra r...@1407.org: To me it has never worked, but never means in images 20090721 and 20090808 of shr-u It doesn't even bother to set the SSID, but I don't know who's really at fault here, mokonnect or connman. Anyway, connman is a real piece of crap (but NetworkManager is just marginally lesser crap) sprout from people with NIH sindrome who don't understand NM. does wifi work yet with newer kernels? i heard some time back that .29 had issues. i don't think i've ever got wifi to work I don't have any problems connecting with mofi. Sure after, connecting I do wmiconfig -i eth0 --power maxperf and then keep a ping running just to know if the connection is alive, but mofi establishes the wifi connection and then it works. With connman+mokonnect I have had ZERO success, so if it works for someone, either that person has made some undocumented adjustment he can't remember or the current versions don't work and he's not running them. Rui -- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Tuesday 11 August 2009 02:41:53 am Paul Fertser wrote: Robin Paulson robin.paul...@gmail.com writes: 2009/8/11 Rui Miguel Silva Seabra r...@1407.org: Anyway, connman is a real piece of crap (but NetworkManager is just marginally lesser crap) sprout from people with NIH sindrome who don't understand NM. does wifi work yet with newer kernels? i heard some time back that .29 had issues. i don't think i've ever got wifi to work .29 has issues but those in kernel are workaroundable. Those in firmware are independent from the kernel and are unlikely to be ever solved. Luckily they don't affect the majority of users. Please try wpa_supplicant method as described on FSO_Resources wikipage and report the results. I know wpa_supplicant stopped working for me, I don't know what went wrong but when I started using mokonnect/connman it worked with no hassles with the .29 kernel with out the test patches installed. -- We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure. Karl Popper signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
Am Dienstag, den 11.08.2009, 10:41 +0400 schrieb Paul Fertser: Please try wpa_supplicant method as described on FSO_Resources wikipage and report the results. ok, using fsoraw it seems to connect to the router (only the important part given here): CTRL-EVENT-SCAN-RESULTS Trying to associate with mac address (SSID='SSID' freq=2437 MHz) Associated with mac address WPA: Key negotiation completed with mac address [PTK=CCMP GTK=TKIP] CTRL-EVENT-CONNECTED - Connection to mac address completed (auth) [id=0 id_str=] But unfortunately, I still can't ping my router, nor can I ping the FreeRunner from my laptop either. Bernhard ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[shr-u] wifi timeout with mokonnect
hi, using shr-u and mokonnect, i get a timeout when trying to connect to my managed wpa-secured home wlan router (while it is trying to setup dhcp, though things work fine with my laptop). is this some well-known issue or do i have to investigate my setup? (any debugging hints?) and what is the rsn encryption option that i get by default after a network scan but can't select in the list of encryption ways? regards bernhard ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Monday 10 August 2009 08:43:40 am Bernhard Reiter wrote: hi, using shr-u and mokonnect, i get a timeout when trying to connect to my managed wpa-secured home wlan router (while it is trying to setup dhcp, though things work fine with my laptop). is this some well-known issue or do i have to investigate my setup? (any debugging hints?) and what is the rsn encryption option that i get by default after a network scan but can't select in the list of encryption ways? regards bernhard I sent an email about this earlier, mokonnect timesout connect, scanning, and/or tryinig to get DHCP, and it no longer reconnects to the AP on resume. The older versions worked flawlessly and made me like it because ever sense the wifi kernel bug it was the first program that just worked short of my having to restart connman to first use it (minor problem). Sadly my post must have been ether lost, ate by some server, or just plan ignored. -- We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure. Karl Popper signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-u] wifi timeout with mokonnect
On Mon, Aug 10, 2009 at 11:11:54AM -0400, Adam Jimerson wrote: On Monday 10 August 2009 08:43:40 am Bernhard Reiter wrote: hi, using shr-u and mokonnect, i get a timeout when trying to connect to my managed wpa-secured home wlan router (while it is trying to setup dhcp, though things work fine with my laptop). is this some well-known issue or do i have to investigate my setup? (any debugging hints?) and what is the rsn encryption option that i get by default after a network scan but can't select in the list of encryption ways? regards bernhard I sent an email about this earlier, mokonnect timesout connect, scanning, and/or tryinig to get DHCP, and it no longer reconnects to the AP on resume. The older versions worked flawlessly and made me like it because ever sense the wifi kernel bug it was the first program that just worked short of my having to restart connman to first use it (minor problem). Sadly my post must have been ether lost, ate by some server, or just plan ignored. To me it has never worked, but never means in images 20090721 and 20090808 of shr-u It doesn't even bother to set the SSID, but I don't know who's really at fault here, mokonnect or connman. Anyway, connman is a real piece of crap (but NetworkManager is just marginally lesser crap) sprout from people with NIH sindrome who don't understand NM. Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
