Intel 3945ABG wifi can't connect at all if 802.11a and 802.11n are both available

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Natty Narwhal. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

I tried the Natty Beta 2 live CD just now.

No difference — exact same misbehaviour as with Maverick — a connection attempt with my home access point configured for both A and N modes still fails with exactly the same error message that I originally reported — but I can connect just fine if the access point is configured only for 802.11a.

I see there's no syslog attachment to this bug report. Could you please try to reproduce the problem again and attach /var/log/syslog so that we can see all of the messages happening as you try to connect?

Thanks.

My original report included what I assumed were all the relevant lines from syslog — nine lines that were repeated over and over.

If you really, really insist you can't or won't investigate the bug without my laptop's entire syslog file, I'll see what I can do — but in that case, can you possibly make do with the syslog from the laptop's production (Maverick) system, since it's cumbersome for me to reconfigure the access point back and forth in order to capture the information and then restore my home's wireless infrastructure to a fully working condition?

Any logs will be fine, we just need to be able to check more than just wpasupplicant, since it could be a driver or NM issue.

OK, I'm attaching a (hopefully substantial) portion of the laptop's syslog. Please let me know if this is enough.

When this syslog excerpt shows a successful connection at the end, please note that this was after I configured my access point back to "A-only" mode on its 5-GHz radio.

Thanks.

I think we probably have enough information now. I suspect a driver issue with mixed-mode itself:

Apr 9 00:25:09 rde-richw-2 wpa_supplicant[1490]: Trying to associate with 00:1f:33:b6:cd:82 (SSID='Wales276Mosher-A' freq=5260 MHz)
Apr 9 00:25:09 rde-richw-2 NetworkManager[1321]: <info> (wlan0): supplicant connection state: scanning -> associating
Apr 9 00:25:09 rde-richw-2 kernel: [169127.033183] wlan0: authenticate with 00:1f:33:b6:cd:82 (try 1)
Apr 9 00:25:09 rde-richw-2 kernel: [169127.033844] wlan0: authenticated
Apr 9 00:25:09 rde-richw-2 kernel: [169127.033912] wlan0: associate with 00:1f:33:b6:cd:82 (try 1)
Apr 9 00:25:09 rde-richw-2 kernel: [169127.034470] wlan0: RX AssocResp from 00:1f:33:b6:cd:82 (capab=0x11 status=18 aid=0)
Apr 9 00:25:09 rde-richw-2 kernel: [169127.034475] wlan0: 00:1f:33:b6:cd:82 denied association (code=18)
Apr 9 00:25:09 rde-richw-2 kernel: [169127.034490] wlan0: deauthenticating from 00:1f:33:b6:cd:82 by local choice (reason=3)
Apr 9 00:25:19 rde-richw-2 wpa_supplicant[1490]: Authentication with 00:1f:33:b6:cd:82 timed out.

I think this is sufficient to assign it to the 'linux' package for further investigation at the kernel level.

Setting back to New so the bug can be properly triaged.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 759051

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

confirmed per duplicate
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: kernel-bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Rich Wales, thank you for reporting this bug and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It is understood your laptop is a production machine. However, it will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]