maemo.org Bugzilla – Bug 2926
"Network connection error." upon associating with network
Last modified: 2008-07-28 00:05:33 UTC
You need to log in before you can comment on or make changes to this bug.
SOFTWARE VERSION: RX-34_2008SE_2.2007.50-2 STEPS TO REPRODUCE THE PROBLEM: Try to associate with a wireless network EXPECTED OUTCOME: Success ACTUAL OUTCOME: "Network connection error." REPRODUCIBILITY: always, rebooting helps most of the time, until I want to associate with another network Nothing suspicious in dmesg, closed source wifi drivers suck. EXTRA SOFTWARE INSTALLED: OTHER COMMENTS: User-Agent: Mozilla/5.0 (X11; A; Linux x86_64; en; rv:1.9b3pre) Gecko/2008020300 (Gentoo) Firefox/3.0b3pre
Please update lastest OS2008 version and try again. And if possible give some more info about your Wlan access point, what software have you installed to your device.
astro, can you please answer Jake's questions? Thanks in advance.
Situation seems to have worsened with RX-34_2008SE_2.2007.51-3. However, I do now see the following line alot in the dmesg: cx3110x: WARNING sm_drv_transmit: prism_softmac_frame_tx() returned error -9. Access Points are diverse. One is unencrypted madwifi, others are unknown with WPA-EAP.
OK, but "diverse" does not help us - Please come up with at least one exact name and its settings, otherwise it's hard to reproduce. Thanks in advance :)
The one I can access is a Fon Fonera running OpenWRT with kernel 2.6.23.17 and Madwifi trunk r3314 as single VAP. Settings below. This one works most of the time, but not always. WPA networks are much more troublesome. ath0 IEEE 802.11g ESSID:"air.sin" Nickname:"" Mode:Master Frequency:2.462 GHz Access Point: 00:xx:xx:xx:xx:xx Bit Rate:0 kb/s Tx-Power:17 dBm Sensitivity=1/1 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=0/70 Signal level=-96 dBm Noise level=-96 dBm Rx invalid nwid:4873 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Hmm, having one that never works would be an even better testcase. :-D
With Diablo Wifi is almost dead. I'm not seeing networks anymore, but nothing in dmesg.
(In reply to comment #7) > With Diablo Wifi is almost dead. I'm not seeing networks anymore, but nothing > in dmesg. What does "almost" mean? Connection manager does not show *any* networks? Network itself is running, I assume? Does running "/etc/init.d/networking restart" as root change anything?
Does not show *any*. restart networking didn't change anything, as chroot /mnt/initfs /usr/bin/wlan-cal doesn't either. I'm going to reflash with OS2007 to check if it's not defective H/W.
Looks like it's working with reflashed Diablo. What I did differently this time was: don't restore backup on first boot but later.
Hmm, so the issue is "fixed" for you now? If so I'd close this but will try to keep it in mind if duplicates get submitted, so this would be handled correctly (yes, I prefer to have reproducibility before forwarding issues).
ping :)
Thanks for your care. It's not glitch-free (DNS & UI issues), but it working Ok right now.
Strange and not really satisfying, but closing as FIXED. Please feel free to file bug reports about the other issues you face. Thanks!
*Might* be related to http://tabletschool.blogspot.com/2008/07/nokia-n810-n800-how-to-use-tablets-with.html