Re: [FSO] Wifi in M5 no longer functioning
2009/2/4 Oleg Sadov sa...@linux-ink.ru: ... # iwconfig eth0 essid my-wifi After that system hangs up and blinking by red LED in AUX button. Seems like restricted key is key point for this situation -- with open key all works good. Can someone try to reproduce this situation? May be something wrong with my hardware... I have the same except that the LED is not flashing. The system hangs, I had to remove the battery. Back to the original problem: I started wpa_supplicant in debug-mode, it goes thru various states up to 4way-handwake, but shortly thereafter to disconnected again: State: DISCONNECTED - SCANNING State: SCANNING - ASSOCIATED State: ASSOCIATED - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - ASSOCIATED State: ASSOCIATED - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - ASSOCIATING State: ASSOCIATING - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - ASSOCIATED State: ASSOCIATED - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - ASSOCIATED State: ASSOCIATED - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - 4WAY_HANDSHAKE State: 4WAY_HANDSHAKE - DISCONNECTED State: DISCONNECTED - SCANNING State: SCANNING - DISCONNECTED ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
[ Copying devel because that's where most of the WLAN-related discussions are taking place. ] Joachim Ott wrote: I have the same except that the LED is not flashing. The system hangs, I had to remove the battery. I've attached a patch with a work-around to https://docs.openmoko.org/trac/ticket/2227 Here's a direct link: https://docs.openmoko.org/trac/raw-attachment/ticket/2227/ar6k-dodge-locking-bug.patch This will avoid the crash and let the driver peacefully set the keys. I suspect that this leaves a race condition, though, but this race condition would have a broader effect than just this particular breakage. I'm still investigating if that supposed race is for real or just a figment of my imagination, though. - Werner ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: [4.965000] AR6000 connected event on freq 2437 with bssid my AP MAC address listenInterval=100, beaconInterval = 100, beaconIeLen = 22 assocReqLen=59 assocRespLen =59 [4.965000] Network: Infrastructure looks OK | eth0 AR6000 802.11g ESSID:my ESSID | Mode:Managed Frequency:2.437 GHz Access Point: my AP MAC | address | Bit Rate=65.535 Mb/s Tx-Power=0 dBm Sensitivity=0/3 Bitrate is broken. | eth0 Link encap:Ethernet HWaddr 00:12:CF:8F:33:91 | inet6 addr: fe80::212:cfff:fe8f:3391/64 Scope:Link | UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 | RX packets:125 errors:0 dropped:0 overruns:0 frame:0 | TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 | collisions:0 txqueuelen:1000 | RX bytes:144316 (140.9 KiB) TX bytes:4497 (4.3 KiB) | | eth0:avah Link encap:Ethernet HWaddr 00:12:CF:8F:33:91 | inet addr:169.254.6.255 Bcast:169.254.255.255 Mask:255.255.0.0 | UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Wow that's new, avahi secondary network interface. This has a link-local address only. | loLink encap:Local Loopback | inet addr:127.0.0.1 Mask:255.0.0.0 | inet6 addr: ::1/128 Scope:Host | UP LOOPBACK RUNNING MTU:16436 Metric:1 | RX packets:1 errors:0 dropped:0 overruns:0 frame:0 | TX packets:1 errors:0 dropped:0 overruns:0 carrier:0 | collisions:0 txqueuelen:0 | RX bytes:104 (104.0 B) TX bytes:104 (104.0 B) | | pan0 Link encap:Ethernet HWaddr AA:92:6C:B1:E1:A9 | BROADCAST MULTICAST MTU:1500 Metric:1 | RX packets:0 errors:0 dropped:0 overruns:0 frame:0 | TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 | collisions:0 txqueuelen:0 | RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) | | usb0 Link encap:Ethernet HWaddr 6E:F1:73:29:F6:4E | inet addr:192.168.0.202 Bcast:192.168.0.255 Mask:255.255.255.0 | inet6 addr: fe80::6cf1:73ff:fe29:f64e/64 Scope:Link | UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 | RX packets:638 errors:0 dropped:0 overruns:0 frame:0 | TX packets:510 errors:0 dropped:0 overruns:0 carrier:0 | collisions:0 txqueuelen:1000 | RX bytes:46204 (45.1 KiB) TX bytes:154823 (151.1 KiB) | | | It seems to look like it's connected, but I still can't ping google, the | AP, or access the internet. usb0 is up too. But, the missing info is your routing table route -n Will the PC you are connected to act as gateway on the USB Ethernet connection? Or is the only way out to the Internet through WLAN? Can you ping even if you don't try to use DNS? What network range does the AP subnet use... 192.168.0.x again? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmKrMsACgkQOjLpvpq7dMrSxQCfZE1Zs7aIQkBDtSKdbc+AY4iN dq0AnRDVEFltfudhVKA59eIoXMhDV1pD =Alfv -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Thursday 05 February 2009, Dylan Semler wrote: On Wed, Feb 4, 2009 at 7:47 AM, Al Johnson openm...@mazikeen.demon.co.ukwrote: I often get the above even with a working wpa_supplicant.conf because the dhcp discover starts being sent immediately, not after association, so dhcp times out before association is complete. Bringing the interface down then immediately up again will often get association faster, so the last dhcp request succeeds. Do you mean, after SetResourcePolicy WiFi enabled, you can do ifdown eth0, ifup eth0, and it works? Or do you cycle the SetResourcePolicy WiFi? Neither seems to work for me. I've been looking at this on recent SHR which I think is largely similar to MS5, but it's possible there are differences in this area. 'SetResourcePolicy WiFi enabled' tells FSO to power up the WiFi irrespective of whether any apps have issued 'RequestResource WiFi'. Before I do this I have no eth0 available. To get dhcp working I would often have to do: ifup eth0 ifdown eth0 ifup eth0 On the second ifup the association often completes a little quicker so dhcp has a chance of completing before timeout. Another method is to manually start dhcp after the first ifup using something like: udhcpc -i eth0 This assumes wpa_supplicant is making the association fine. You can check that with wpa_cli which accepts a 'help' command to tell you what other options it has. This has worked for me on everything I've tried since 2007.2, but I've not tried it on the recent SHR or MS5 yet. SHR, and probably MS5, have the added complication of connman running. This tries to manage the network connections, but at least for usb0 it is overridden by the ifup and ifdown commands. Assuming connman actually works, the other option would be to use the connman dbus interface to set the network parameters. Don't ask me how though ;-) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
eth0:avah Link encap:Ethernet HWaddr 00:12:CF:8F:33:91 inet addr:169.254.6.255 Bcast:169.254.255.255 It seems to look like it's connected nope. it's not. the ip address shown is a generic one, assigned by avahi in absence of a real one. i don't know, what you did to obtain an association with tha ap and an ip subsequnetly, but iwlist scan is not giong to o that. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Thu, Feb 5, 2009 at 3:09 AM, Andy Green a...@openmoko.com wrote: Somebody in the thread at some point said: | It seems to look like it's connected, but I still can't ping google, the | AP, or access the internet. usb0 is up too. I use usb to ssh into the phone. But, the missing info is your routing table route -n r...@om-gta02:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 00 usb0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 00 eth0 0.0.0.0 192.168.0.200 0.0.0.0 UG0 00 usb0 Will the PC you are connected to act as gateway on the USB Ethernet connection? Or is the only way out to the Internet through WLAN? I haven't done anything to setup access to the internet via usb (just ssh) so I imagine right now there's only WLAN. Unless GPRS gets configured automatically in M5. Can you ping even if you don't try to use DNS? No. No luck with 192.168.1.1 What network range does the AP subnet use... 192.168.0.x again? 192.168.1.x So I'm unclear whether you're supposed to ifup eth0 after SetResourcePolicy WiFi enabled. When I try right away it says r...@om-gta02:~# ifup eth0 ifup: interface eth0 already configured r...@om-gta02:~# ifdown eth0 cat: can't open '/var/run/udhcpc.eth0.pid': No such file or directory ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Thu, Feb 5, 2009 at 5:56 AM, Al Johnson openm...@mazikeen.demon.co.ukwrote: 'SetResourcePolicy WiFi enabled' tells FSO to power up the WiFi irrespective of whether any apps have issued 'RequestResource WiFi'. Before I do this I have no eth0 available. Yeah, but it seems to also configure eth0 because after I SetResourcePolicy, If I do ifup eth0 right away I get ifup: interface eth0 already configured To get dhcp working I would often have to do: ifup eth0 ifdown eth0 ifup eth0 I know what you're talking about, I definitely had to do this with past images as well. However, with M5, there's still no luck with the second ifup eth0. On the second ifup the association often completes a little quicker so dhcp has a chance of completing before timeout. Another method is to manually start dhcp after the first ifup using something like: udhcpc -i eth0 Yeah, this suffers the same fate is ifup, ifdown, ifup. It's good to know if I revert to an older image. This assumes wpa_supplicant is making the association fine. You can check that with wpa_cli which accepts a 'help' command to tell you what other options it has. This has worked for me on everything I've tried since 2007.2, but I've not tried it on the recent SHR or MS5 yet. SHR, and probably MS5, have the added complication of connman running. This tries to manage the network connections, but at least for usb0 it is overridden by the ifup and ifdown commands. Assuming connman actually works, the other option would be to use the connman dbus interface to set the network parameters. Don't ask me how though ;-) I'll poke at this when I have more time after the weekend. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
What about eth0? inet6 addr: fe80::212:cfff:fe8f:3391/64 same thing basically, though probably not assigned by avahi but something random (do you use ipv6 at home? does the fr kernel support ipv6 at all?) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Thu, Feb 5, 2009 at 11:10 AM, arne anka openm...@ginguppin.de wrote: What about eth0? inet6 addr: fe80::212:cfff:fe8f:3391/64 same thing basically, though probably not assigned by avahi but something random (do you use ipv6 at home? does the fr kernel support ipv6 at all?) I just checked. I'm running dd-wrt v24 rc5 which doesn't seem to have working IPv6.[1] [1]http://www.dd-wrt.com/wiki/index.php/IPv6 ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Wed, Feb 4, 2009 at 1:40 AM, Michael 'Mickey' Lauer mic...@openmoko.orgwrote: That's correct behaviour due to auto-release. Please read the usage introduction at http://docs.freesmartphone.org/usage-intro.html If you can't stay on the bus, use SetResourcePolicy. My bad, I hadn't read far enough before to catch the note about mdbus at the bottom. I've set the policy to enabled, but still having troubles r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy WiFi enabled r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.GetResourceState WiFi True r...@om-gta02:~# ifup eth0 WPA: Configuring Interface ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported udhcpc (v1.13.2) started run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 Sending discover... Sending discover... Sending discover... No lease, failing I don't _think_ it's a configuration issue, as my setup hasn't changed since M4 and I'm using the same config files. Really all I'm wanting to do is enable wifi so I can opkg some packages from the command line, etc. Am I going at this the wrong way? Dylan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
2009/2/4 Dylan Semler dylan.sem...@gmail.com: ... r...@om-gta02:~# ifup eth0 WPA: Configuring Interface ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported udhcpc (v1.13.2) started run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 Sending discover... Sending discover... Sending discover... No lease, failing Can you see scan data with iwlist eth0 scan? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
Am Wednesday 04 February 2009 10:08:37 schrieb Dylan Semler: mic...@openmoko.orgwrote: That's correct behaviour due to auto-release. Please read the usage introduction at http://docs.freesmartphone.org/usage-intro.html If you can't stay on the bus, use SetResourcePolicy. My bad, I hadn't read far enough before to catch the note about mdbus at the bottom. I've set the policy to enabled, but still having troubles r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy WiFi enabled r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.GetResourceState WiFi True Good so far. The framework itself does its job then. r...@om-gta02:~# ifup eth0 WPA: Configuring Interface ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported udhcpc (v1.13.2) started run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 Sending discover... Sending discover... Sending discover... No lease, failing I don't _think_ it's a configuration issue, as my setup hasn't changed since M4 and I'm using the same config files. I'm afraid the new kernel broke something then. Can you try an older one to make sure? -- :M: ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Wednesday 04 February 2009, Dylan Semler wrote: On Wed, Feb 4, 2009 at 1:40 AM, Michael 'Mickey' Lauer mic...@openmoko.orgwrote: That's correct behaviour due to auto-release. Please read the usage introduction at http://docs.freesmartphone.org/usage-intro.html If you can't stay on the bus, use SetResourcePolicy. My bad, I hadn't read far enough before to catch the note about mdbus at the bottom. I've set the policy to enabled, but still having troubles r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy WiFi enabled r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.GetResourceState WiFi True r...@om-gta02:~# ifup eth0 WPA: Configuring Interface ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported udhcpc (v1.13.2) started run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 Sending discover... Sending discover... Sending discover... No lease, failing I don't _think_ it's a configuration issue, as my setup hasn't changed since M4 and I'm using the same config files. I often get the above even with a working wpa_supplicant.conf because the dhcp discover starts being sent immediately, not after association, so dhcp times out before association is complete. Bringing the interface down then immediately up again will often get association faster, so the last dhcp request succeeds. Really all I'm wanting to do is enable wifi so I can opkg some packages from the command line, etc. Am I going at this the wrong way? Dylan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
04/02/2009 10:51 +, Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | r...@om-gta02:~# ifup eth0 | WPA: Configuring Interface | ioctl[SIOCSIWENCODEEXT]: Operation not supported | ioctl[SIOCSIWENCODEEXT]: Operation not supported | ioctl[SIOCSIWENCODEEXT]: Operation not supported | ioctl[SIOCSIWENCODEEXT]: Operation not supported | udhcpc (v1.13.2) started | run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 | Sending discover... | Sending discover... | Sending discover... | No lease, failing | | I don't _think_ it's a configuration issue, as my setup hasn't changed | since M4 and I'm using the same config files. | | I'm afraid the new kernel broke something then. Can you try an older one to | make sure? What's dmesg have to say about all this excitement? # iwconfig # iwlist eth0 scan In my FSO M5-equiped FR eth0 visible by iwconfig and my WiFi points successfully scaned by iwlist. Since the previous Jan 5th basis I understood the kernel had, there are relatively few patches. The main change is WLAN driver is now in modules. But, seems like I found another unpleasant bug :( I tryed setting up direct WiFi network access (without hardware Access Points) for FR by hands (I successfully used such scenario for configuring wireless-networking for some OLPCs traditional notebooks): # iwconfig eth0 mode ad-hoc # iwconfig eth0 essid my-wifi # iwconfig eth0 eth0 AR6000 802.11g ESSID:my-wifi Mode:Ad-Hoc Frequency:2.457 GHz Cell: 4E:72:EC:8E:38:88 Bit Rate=1 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:off Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 # iwconfig eth0 channel 1 # iwconfig eth0 key restricted 1234567890 # iwconfig eth0 eth0 AR6000 802.11g ESSID: Mode:Ad-Hoc Frequency:2.457 GHz Cell: 4E:72:EC:8E:38:88 Bit Rate=1 Mb/s Tx-Power=15 dBm Sensitivity=0/3 Retry:on Encryption key:1234-5678-90 Security mode:restricted Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-97 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 I lost my ESSID at this step and try setting up this one once again: # iwconfig eth0 essid my-wifi After that system hangs up and blinking by red LED in AUX button. Seems like restricted key is key point for this situation -- with open key all works good. Can someone try to reproduce this situation? May be something wrong with my hardware... --Oleg # lsmod I guess check eth0 is still assigned to WLAN with # ifconfig -a as well. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmJc00ACgkQOjLpvpq7dMpX+gCfTgXFLwakVt0dVmIt1hf1n2yZ LrkAn1Co5KbBV/xyBFANa8Ts9xT2jYaB =B4zW -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | In my FSO M5-equiped FR eth0 visible by iwconfig and my WiFi points | successfully scaned by iwlist. | | Since the previous Jan 5th basis I understood the kernel had, there are | relatively few patches. The main change is WLAN driver is now in modules. | | But, seems like I found another unpleasant bug :( I never met a pleasant one :-) | I tryed setting up direct WiFi network access (without hardware Access | Points) for FR by hands (I successfully used such scenario for | configuring wireless-networking for some OLPCs traditional notebooks): | | # iwconfig eth0 mode ad-hoc | # iwconfig eth0 essid my-wifi | # iwconfig eth0 | eth0 AR6000 802.11g ESSID:my-wifi | Mode:Ad-Hoc Frequency:2.457 GHz Cell: 4E:72:EC:8E:38:88 | Bit Rate=1 Mb/s Tx-Power=15 dBm Sensitivity=0/3 | Retry:on | Encryption key:off | Power Management:off | Link Quality:0/94 Signal level:-95 dBm Noise level:-96 dBm | Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 | Tx excessive retries:0 Invalid misc:0 Missed beacon:0 | | # iwconfig eth0 channel 1 | # iwconfig eth0 key restricted 1234567890 | # iwconfig eth0 | eth0 AR6000 802.11g ESSID: | Mode:Ad-Hoc Frequency:2.457 GHz Cell: 4E:72:EC:8E:38:88 | Bit Rate=1 Mb/s Tx-Power=15 dBm Sensitivity=0/3 | Retry:on | Encryption key:1234-5678-90 Security mode:restricted | Power Management:off | Link Quality:0/94 Signal level:-95 dBm Noise level:-97 dBm | Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 | Tx excessive retries:0 Invalid misc:0 Missed beacon:0 | | I lost my ESSID at this step and try setting up this one once again: | | # iwconfig eth0 essid my-wifi | | After that system hangs up and blinking by red LED in AUX button. Right, panicked. | Seems like restricted key is key point for this situation -- with open | key all works good. | | Can someone try to reproduce this situation? May be something wrong with | my hardware... No it shouldn't panic anyway. Can you open a Trac bug about this, just cut and paste your description here is fine. If we can reproduce it with a debug board it's probably not too hard to make the panic go away anyway. Ad-hoc is relatively uncommon so it makes sense it's going to show more bugs. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmJutYACgkQOjLpvpq7dMpb/gCfZHfm8QsObsaVshBJM8UNosUb kPwAn2TW7us9Iv5i7Yj3ug8apUFs7/PH =m9Cl -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | r...@om-gta02:~# ifup eth0 | WPA: Configuring Interface | ioctl[SIOCSIWENCODEEXT]: Operation not supported | ioctl[SIOCSIWENCODEEXT]: Operation not supported | ioctl[SIOCSIWENCODEEXT]: Operation not supported | ioctl[SIOCSIWENCODEEXT]: Operation not supported | udhcpc (v1.13.2) started | run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 | Sending discover... | Sending discover... | Sending discover... | No lease, failing | | I don't _think_ it's a configuration issue, as my setup hasn't changed | since M4 and I'm using the same config files. | | I'm afraid the new kernel broke something then. Can you try an older one to | make sure? What's dmesg have to say about all this excitement? # iwconfig # iwlist eth0 scan Since the previous Jan 5th basis I understood the kernel had, there are relatively few patches. The main change is WLAN driver is now in modules. # lsmod I guess check eth0 is still assigned to WLAN with # ifconfig -a as well. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmJc00ACgkQOjLpvpq7dMpX+gCfTgXFLwakVt0dVmIt1hf1n2yZ LrkAn1Co5KbBV/xyBFANa8Ts9xT2jYaB =B4zW -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
В Срд, 04/02/2009 в 15:57 +, Andy Green пишет: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | In my FSO M5-equiped FR eth0 visible by iwconfig and my WiFi points | successfully scaned by iwlist. | | Since the previous Jan 5th basis I understood the kernel had, there are | relatively few patches. The main change is WLAN driver is now in modules. | | But, seems like I found another unpleasant bug :( I never met a pleasant one :-) | I tryed setting up direct WiFi network access (without hardware Access | Points) for FR by hands (I successfully used such scenario for | configuring wireless-networking for some OLPCs traditional notebooks): | | # iwconfig eth0 mode ad-hoc | # iwconfig eth0 essid my-wifi | # iwconfig eth0 | eth0 AR6000 802.11g ESSID:my-wifi | Mode:Ad-Hoc Frequency:2.457 GHz Cell: 4E:72:EC:8E:38:88 | Bit Rate=1 Mb/s Tx-Power=15 dBm Sensitivity=0/3 | Retry:on | Encryption key:off | Power Management:off | Link Quality:0/94 Signal level:-95 dBm Noise level:-96 dBm | Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 | Tx excessive retries:0 Invalid misc:0 Missed beacon:0 | | # iwconfig eth0 channel 1 | # iwconfig eth0 key restricted 1234567890 | # iwconfig eth0 | eth0 AR6000 802.11g ESSID: | Mode:Ad-Hoc Frequency:2.457 GHz Cell: 4E:72:EC:8E:38:88 | Bit Rate=1 Mb/s Tx-Power=15 dBm Sensitivity=0/3 | Retry:on | Encryption key:1234-5678-90 Security mode:restricted | Power Management:off | Link Quality:0/94 Signal level:-95 dBm Noise level:-97 dBm | Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 | Tx excessive retries:0 Invalid misc:0 Missed beacon:0 | | I lost my ESSID at this step and try setting up this one once again: | | # iwconfig eth0 essid my-wifi | | After that system hangs up and blinking by red LED in AUX button. Right, panicked. | Seems like restricted key is key point for this situation -- with open | key all works good. | | Can someone try to reproduce this situation? May be something wrong with | my hardware... No it shouldn't panic anyway. Can you open a Trac bug about this, just cut and paste your description here is fine. Unfortunately, my account (linux-ink) don't have permissions for publishing bugs at: https://docs.openmoko.org/trac/newticket I got: Error: Forbidden TICKET_CREATE privileges are required to perform this operation This bug published at http://trac.freesmartphone.org on Ticket #344 If we can reproduce it with a debug board it's probably not too hard to make the panic go away anyway. Ad-hoc is relatively uncommon so it makes sense it's going to show more bugs. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmJutYACgkQOjLpvpq7dMpb/gCfZHfm8QsObsaVshBJM8UNosUb kPwAn2TW7us9Iv5i7Yj3ug8apUFs7/PH =m9Cl -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Wed, Feb 4, 2009 at 4:51 AM, Andy Green a...@openmoko.com wrote: What's dmesg have to say about all this excitement? After SetResourcePolicy Wifi enable I get the following new lines in dmesg: [21474827.275000] s3c2440-sdi s3c2440-sdi: host detect has no irq available [21474827.275000] mapped channel 0 to 0 [21474827.295000] s3c2440-sdi s3c2440-sdi: powered down. [21474827.295000] s3c2440-sdi s3c2440-sdi: initialisation done. [21474827.51] s3c2440-sdi s3c2440-sdi: running at 0kHz (requested: 0kHz). [21474827.51] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz). [21474827.51] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz). [21474827.52] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz). [21474827.52] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz). [21474827.545000] s3c2440-sdi s3c2440-sdi: running at 196kHz (requested: 195kHz). [21474827.56] mmc0: queuing CIS tuple 0x01 length 3 [21474827.58] mmc0: queuing CIS tuple 0x1a length 5 [21474827.595000] mmc0: queuing CIS tuple 0x1b length 8 [21474827.595000] s3c2440-sdi s3c2440-sdi: running at 25000kHz (requested: 25000kHz). [21474827.595000] s3c2440-sdi s3c2440-sdi: running at 25000kHz (requested: 25000kHz). [21474827.605000] mmc0: queuing CIS tuple 0x80 length 1 [21474827.605000] mmc0: queuing CIS tuple 0x81 length 1 [21474827.605000] mmc0: queuing CIS tuple 0x82 length 1 [21474827.605000] mmc0: new SDIO card at address 0001 [21474828.65] BMI Get Target Info: Exit (ver: 0x2059 type: 0x1) [21474828.725000] AR6000 Reg Code = 0x4060 [21474833.405000] ar6000_ioctl_giwscan(): data length 0 [21474836.36] AR6000 Reg Code = 0x8348 [4.585000] eth0: no IPv6 routers present [4.89] channel hint set to 2437 [4.905000] AR6000 disconnected [4.965000] AR6000 connected event on freq 2437 with bssid my AP MAC address listenInterval=100, beaconInterval = 100, beaconIeLen = 22 assocReqLen=59 assocRespLen =59 [4.965000] Network: Infrastructure # iwconfig r...@om-gta02:~# iwconfig lono wireless extensions. usb0 no wireless extensions. pan0 no wireless extensions. eth0 AR6000 802.11g ESSID:my ESSID Mode:Managed Frequency:2.437 GHz Access Point: my AP MAC address Bit Rate=65.535 Mb/s Tx-Power=0 dBm Sensitivity=0/3 Retry:on Encryption key:off Power Management:off Link Quality:0/94 Signal level:-95 dBm Noise level:-96 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 # iwlist eth0 scan r...@om-gta02:~# iwlist eth0 scan eth0 Scan completed : Cell 01 - Address: my AP MAC address ESSID:my ESSID Mode:Master Frequency:2.437 GHz (Channel 0) Quality=42/94 Signal level=-53 dBm Noise level=-95 dBm Encryption key:on Extra:bcn_int=100 Extra:rsn_ie=3014010fac02010fac02010fac020c00 Extra:wmm_ie=dd180050f202010183a427a442435e0062322f00 Since the previous Jan 5th basis I understood the kernel had, there are relatively few patches. The main change is WLAN driver is now in modules. # lsmod r...@om-gta02:~# lsmod Module Size Used by bnep 12800 2 sco10444 2 snd_soc_neo1973_gta02_wm8753 8552 0 snd_soc_s3c24xx_i2s 3896 1 snd_soc_neo1973_gta02_wm8753 snd_soc_s3c24xx 4424 1 snd_soc_neo1973_gta02_wm8753 snd_soc_wm8753 33384 1 snd_soc_neo1973_gta02_wm8753 snd_soc_core 34360 3 snd_soc_neo1973_gta02_wm8753,snd_soc_s3c24xx,snd_soc_wm8753 snd_pcm76364 2 snd_soc_s3c24xx,snd_soc_core snd_timer 21052 1 snd_pcm snd_page_alloc 6504 1 snd_pcm snd50788 5 snd_soc_neo1973_gta02_wm8753,snd_soc_wm8753,snd_soc_core,snd_pcm,snd_timer rfcomm 37320 4 ipv6 265884 14 hidp 14664 0 l2cap 21456 13 bnep,rfcomm,hidp g_ether39604 0 btusb 11952 0 bluetooth 60408 10 bnep,sco,rfcomm,hidp,l2cap,btusb ohci_hcd 28564 0 s3c2410_wdt 8984 0 I guess check eth0 is still assigned to WLAN with # ifconfig -a r...@om-gta02:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:12:CF:8F:33:91 inet6 addr: fe80::212:cfff:fe8f:3391/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:125 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:144316 (140.9 KiB) TX bytes:4497 (4.3 KiB) eth0:avah Link encap:Ethernet HWaddr 00:12:CF:8F:33:91 inet addr:169.254.6.255
Re: [FSO] Wifi in M5 no longer functioning
On Wed, Feb 4, 2009 at 4:38 AM, Michael 'Mickey' Lauer mic...@openmoko.orgwrote: Am Wednesday 04 February 2009 10:08:37 schrieb Dylan Semler: I don't _think_ it's a configuration issue, as my setup hasn't changed since M4 and I'm using the same config files. I'm afraid the new kernel broke something then. Can you try an older one to make sure? Using the kernel from M4.1 (2.6.24+r10 from Nov 18th), I can access the internet with SetResourcePolicy WiFi enabled and then ifup eth0. The next kernel image available in the testing and unstable repositories is 2.5.28-oe1 from Jan 12th. This kernel exhibits the same problems as the M5 kernel. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Wed, Feb 4, 2009 at 7:47 AM, Al Johnson openm...@mazikeen.demon.co.ukwrote: I often get the above even with a working wpa_supplicant.conf because the dhcp discover starts being sent immediately, not after association, so dhcp times out before association is complete. Bringing the interface down then immediately up again will often get association faster, so the last dhcp request succeeds. Do you mean, after SetResourcePolicy WiFi enabled, you can do ifdown eth0, ifup eth0, and it works? Or do you cycle the SetResourcePolicy WiFi? Neither seems to work for me. Dylan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[FSO] Wifi in M5 no longer functioning
It seems that my prior FSO wifi configuration no longer works with M5.
r...@om-gta02:~# ifup eth0
WPA: Configuring Interface
ioctl[SIOCGIFFLAGS]: No such device
Could not get interface 'eth0' flags
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: No such device
ioctl[SIOCGIFINDEX]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 7 value 0x0 - Failed to disable WPA in the driver.
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
wpa_supplicant: /usr/sbin/wpa_supplicant daemon failed to start
FAILED
ifconfig: SIOCGIFFLAGS: No such device
eth0 No such device
ifconfig: SIOCGIFFLAGS: No such device
I'm using WPA2 configured as follows:
# cat /etc/wpa_supplicant/cat wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid=private
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk=private
priority=50
}
And I've added the line: wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
beneith the line iface eth0 inet dhcp in /etc/network/interfaces.
This configuration has worked for all other distributions thus far. Is
something different this time around?
Dylan
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
Am Wednesday 04 February 2009 02:55:25 schrieb Dylan Semler: It seems that my prior FSO wifi configuration no longer works with M5. Did you request WiFi with the Usage API? -- :M: ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
I'm having the same problem.
Dylan Semler wrote:
It seems that my prior FSO wifi configuration no longer works with M5.
r...@om-gta02:~# ifup eth0
WPA: Configuring Interface
ioctl[SIOCGIFFLAGS]: No such device
Could not get interface 'eth0' flags
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: No such device
ioctl[SIOCGIFINDEX]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 7 value 0x0 - Failed to disable WPA in the driver.
ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: No such device
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
wpa_supplicant: /usr/sbin/wpa_supplicant daemon failed to start
FAILED
ifconfig: SIOCGIFFLAGS: No such device
eth0 No such device
ifconfig: SIOCGIFFLAGS: No such device
I'm using WPA2 configured as follows:
# cat /etc/wpa_supplicant/cat wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# WPA2:
network={
ssid=private
scan_ssid=1
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=TKIP CCMP
psk=private
priority=50
}
And I've added the line: wpa-conf
/etc/wpa_supplicant/wpa_supplicant.conf beneith the line iface eth0
inet dhcp in /etc/network/interfaces.
This configuration has worked for all other distributions thus far.
Is something different this time around?
Dylan
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
On Tue, Feb 3, 2009 at 8:20 PM, Michael 'Mickey' Lauer mic...@openmoko.orgwrote: Am Wednesday 04 February 2009 02:55:25 schrieb Dylan Semler: It seems that my prior FSO wifi configuration no longer works with M5. Did you request WiFi with the Usage API? I guess I did not. Now I run r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.RequestResource WiFi r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.GetResourceState WiFi False r...@om-gta02:~# After RequestResource WiFi, the freerunner shows up on my router's list of connected wifi devices. Does RequestResource not only turn on the radio, but also try to connect (and thus, ifup eth0 would not be necessary)? If it does it must be failing in my case. Dylan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Wifi in M5 no longer functioning
Am Dienstag, den 03.02.2009, 22:13 -0600 schrieb Dylan Semler: On Tue, Feb 3, 2009 at 8:20 PM, Michael 'Mickey' Lauer mic...@openmoko.org wrote: Am Wednesday 04 February 2009 02:55:25 schrieb Dylan Semler: It seems that my prior FSO wifi configuration no longer works with M5. Did you request WiFi with the Usage API? I guess I did not. Now I run r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.RequestResource WiFi r...@om-gta02:~# mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.GetResourceState WiFi False r...@om-gta02:~# That's correct behaviour due to auto-release. Please read the usage introduction at http://docs.freesmartphone.org/usage-intro.html If you can't stay on the bus, use SetResourcePolicy. :M: ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
