After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 618264 - Wireless LAN disconnects frequently # Chipset Intel 3945ABG @ AP with WPA
Wireless LAN disconnects frequently # Chipset Intel 3945ABG @ AP with WPA
Status: RESOLVED NOTGNOME
Product: NetworkManager
Classification: Platform
Component: general
0.8.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2010-05-10 12:45 UTC by Angel Abad
Modified: 2010-05-22 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
wpa_supplicant debug log (625.70 KB, text/plain)
2010-05-12 17:24 UTC, Pawel
Details

Description Angel Abad 2010-05-10 12:45:31 UTC
In Ubuntu Karmic Ungolianth reported:

Error occurs at Karmic Koala Alpha5:

Everything's working fine, when using the WEP-Encryption.

But when using a WPA-Encryption, the device looses connection after about 10-15 seconds. In that short time I'm able to use the Internet...

--------------------------------------------------------
$ lspci |grep -i net
02:08.0 Ethernet controller: Intel Corporation 82562ET/EZ/GT/GZ - PRO/100 VE (LOM) Ethernet Controller Mobile (rev 01)
10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
---------------------------------------------------------

If more data is needed contact me.

Launchpad ref: https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/425455
Comment 1 Dan Williams 2010-05-10 23:39:34 UTC
Can you grab the output of 'dmesg'?  There should be a number of items related to 'iwl3945' or 'iwlagn' in there that could help.  Also, some additional debugging tips are here:

http://live.gnome.org/NetworkManager/Debugging

in the "Debugging WiFi Connections" section; the supplicant log can be very useful in determining the problem.  The log bits linked in that Launchpad bug aren't quite enough to determine the issue.
Comment 2 Pawel 2010-05-12 17:24:50 UTC
Created attachment 160919 [details]
wpa_supplicant debug log

In attachment there is a log from wpa_supplicant in debug mode (ran with "-dddt").
Comment 3 Pawel 2010-05-12 17:31:33 UTC
dmesg | grep -e iwl3945 -e iwlagn
[   11.186223] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
[   11.186226] iwl3945: Copyright(c) 2003-2009 Intel Corporation
[   11.186334] iwl3945 0000:05:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[   11.186349] iwl3945 0000:05:00.0: setting latency timer to 64
[   11.242577] iwl3945 0000:05:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
[   11.242580] iwl3945 0000:05:00.0: Detected Intel Wireless WiFi Link 3945ABG
[   11.242732] iwl3945 0000:05:00.0: irq 28 for MSI/MSI-X
[   16.057115] iwl3945 0000:05:00.0: firmware: requesting iwlwifi-3945-2.ucode
[   16.449238] iwl3945 0000:05:00.0: loaded firmware version 15.32.2.9
Comment 4 Dan Williams 2010-05-22 16:34:29 UTC
Unfortunately this appears to be a driver error.  It simply isn't able to connect to the AP using the settings you've given it.  The logs show a lot of half-completed connections that then fail because the driver sends the "disconnect" event.  I think at this point you shoudl file a bug in your distributions' bugzilla against the kernel with these logs and follow it up there.  They'll likely ask you to enable debug logging of the driver so that they can see why the driver is failing to connect to the AP.
Comment 5 Pawel 2010-05-22 18:40:41 UTC
(In reply to comment #4)
> Unfortunately this appears to be a driver error.  It simply isn't able to
> connect to the AP using the settings you've given it.  The logs show a lot of
> half-completed connections that then fail because the driver sends the
> "disconnect" event.  I think at this point you shoudl file a bug in your
> distributions' bugzilla against the kernel with these logs and follow it up
> there.  They'll likely ask you to enable debug logging of the driver so that
> they can see why the driver is failing to connect to the AP.

Hmmm.. it works with Wicd Network Manager.