BG2200 wifi card loses WPA abilities in 12.04b2

Bug #977688 reported by Mike Stucka
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Problems are with a Intel BG2200 wifi cards in 12.04b2.

Looks like the drivers are in ipw2200, which apparently comes with the kernel.

After installing 12.04b2 at least two people lost the ability to connect to WPA or WPA2 routers. In the network panel, the other networks still appear but are in a dark gray/grayed out. Only WEP routers appear to be options.

Other report:
http://ubuntuforums.org/showthread.php?p=11832068#post11832068

After upgrades from 11.04, I was using the wifi card successfully for some hours, but then noticed in the network panel that it didn't know what network I was on. I made the mistake of disconnecting, and was not able to reconnect.

I believe the BG2200 is a rather old card but was popular for a long time. There's probably a not insignificant usage base.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/977688/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → linux (Ubuntu)
tags: added: regression-release
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

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

apport-collect 977688

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.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
Revision history for this message
Mike Stucka (stucka) wrote :

None of the package search tools on the web site, nor on my computer, nor the IRC channel, nor Google told me what package the module came from. I'm sorry, I'm new at this, but went through all the instructions and nothing helped got me pointed in the right direction.

Running the apport command crashed the script. Error log attached.

I can try whatever else y'all want.

From a cold boot this morning I got a connect message to my WPA2 network.
Title: Wireless Network Authentication Required
Passwords or encryption keys are required to access the wireless network 'whitedoggies2'.

Options are cancel or connect. Connect is grayed out.

In the network selector are other WPA and WPA2 networks in my neighborhood that are also grayed out.

Revision history for this message
Mike Stucka (stucka) wrote :

apport was updated overnight, but I still get a similar crash.

Looks as if the BG2200 is now part of the kernel ... ? My kernel:
3.2.0-22-generic #35-Ubuntu SMP Tue Apr 3 18:32:42 UTC 2012 i686 i686 i386 GNU/Linux

I also found out several pointers to reporting a kernel bug. Naturally, the section is missing: https://wiki.ubuntu.com/Bugs/FindRightPackage#Kernel

I'm trying here, guys, I swear ...

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc2-precise/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Revision history for this message
Mike Stucka (stucka) wrote :

I don't have access to the tag editor, in the location it's in the help video here: https://help.launchpad.net/Videos?action=AttachFile&do=get&target=launchpad-in-line-bug-tag-editing.ogv

so needs-upstream-testing tag needs to go
kernel-bug-exists-upstream needs to be added

If indeed it's the kernel at fault.

I booted with the 3.4 kernel: Linux mikelight 3.4.0-030400rc2-generic #201204072235 SMP Sun Apr 8 02:43:03 UTC 2012 i686 i686 i386 GNU/Linux

Same results, but I don't know that that's changing the actual module itself (if indeed the module is at fault). I also booted with the 11.10's 3.0 kernel, which worked yesterday, and the 11.04's 2.6 kernel, which I'd used for a year.

Also using dpkg -r to remove the 3.4 kernel required an update-grub execution.

Anything else I can check here?

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Mike Stucka (stucka) wrote :

Will do. I appreciate all the help.

For what it's worth, WEP networks are not grayed out. However, when I set up my wife's cell phone as a WEP hotspot, I never got a connection and the network manager assumed it was an open connection. When I put in a WEP password, it never got a connection. When I switched the phone back to an open hot spot, it connected within a few seconds.

I don't know what this means, but I thought I should pass it along. =)

Revision history for this message
Mike Stucka (stucka) wrote :

@#*& Looks like this may have already been reported under the module name rather than the card name.

https://bugzilla.kernel.org/show_bug.cgi?id=43049
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/971628
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/973241

I'm afraid this bug report was a duplicate and I failed to find the duplicates. I am so very very sorry.

Revision history for this message
Mike Stucka (stucka) wrote :

OK, dumb question here -- does the patch do anything to address a related problem with WPA? Looks like these bugs are related to software improperly communicating whether the BG2200 can do WEP and WPA.

I couldn't get WEP to work, though, and even with no capabilities reported, network manager was still listing WEP routers as possible connections. It was only WPA/WPA2 routers that were grayed out.

Do I need to open up a bug report on that, or is WEP an assumed connection type?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.