Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5 chipset

Bug #141620 reported by nynexman4464
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Alexander Sack

Bug Description

Binary package hint: network-manager

I have an IBM Thinkpad T23 with a IBM High Rate Wireless LAN Mini-PCI Adapter with Modem (Prism 2.5 chipset).

When I have WPA security enabled on my wireless network, I cannot connect to it with NetworkManager. It is listed under the wireless networks, and has a security icon next to it. When I click on it I am asked for a key, but the only options listed are for WEP and LEAP. If I don't enable security, or use WEP I am able to connect to the network.

I also tried manually specifying the network essid, selecting the WPA option and entering the passcode. This resulted in network-manager attempting to connect and eventually crashing.

I can connect to the network manually using wpasupplicant, which is why I think the bug is in NetworkManager.

This is on ubunti 7.10 gutsy with the latest updates. uname -a:
Linux conrad 2.6.22-12-generic #1 SMP Thu Sep 20 18:51:18 GMT 2007 i686 GNU/Linux

Revision history for this message
nynexman4464 (alex-alexrock) wrote : lspci -vvnn
Revision history for this message
nynexman4464 (alex-alexrock) wrote : Contents of dmesg
Revision history for this message
nynexman4464 (alex-alexrock) wrote : tail -n 50 /var/syslog after network-manager crash
Revision history for this message
Alexander Sack (asac) wrote :

please get a backtrace as documented in the debugging crashes section on https://wiki.ubuntu.com/DebuggingNetworkManager

Thanks,
 - Alexander

Changed in network-manager:
assignee: nobody → asac
status: New → Incomplete
Revision history for this message
nynexman4464 (alex-alexrock) wrote :

I assume that the wiki page meant tail -f -n0 /var/log/syslog > /tmp/syslog, rather than tail -n0 /var/log/syslog > /tmp/syslog, which outputs nothing.

Happily (or I guess unfortunately, depending on how you look at it) I wasn't able to replicate the crash. However there is still a bug. When I first tried to connect to the network, I was asked for a WEP key like before. I hit cancel and it didn't connect. So I selected manual connection, specified the essid and the WPA key. Network manager connected, but then disconnected a few seconds later. I then tried selecting the network again (from the list, not manually). This time I wasn't asked the key, but it did connect to the network and seems to be staying connected.

I tried rebooting to see if it would connect again after I logged in and it did. So it seems the problem is rather that I'm not given the option to select WPA encryption when I fist connect, but then if I manually specify it I am able to connect, on the second try.

I tried to mark out in the log where I tried to connect, like requested in the wiki.

Changed in network-manager:
status: Incomplete → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :

do you still see this in latest hardy? If so, please attach your _complete_ /Var/log/syslog taken _after_ you reproduced this problem. Thanks!

Changed in network-manager:
status: Confirmed → Incomplete
Revision history for this message
nynexman4464 (alex-alexrock) wrote :

Yes, it still happens on the first connections. I have to manually enter the network information, and even then, it only connects after several reattempts.

Here is the syslog as requested.

Revision history for this message
nynexman4464 (alex-alexrock) wrote :

Sorry, that log has other information from boot (in order to reproduce the problem, I have to delete the connection from gconf as it only happens on the first connection attempts). This log contains only the boot where the config info wasn't present and I had to enter manually.

Revision history for this message
Alexander Sack (asac) wrote :

do you still have problems with prism chipset with intrepid kernel?

Revision history for this message
nynexman4464 (alex-alexrock) wrote :

I'm not sure, I've retired that laptop. I still have it though so I will dig it out of storage and give it a try later in the week.

Revision history for this message
nynexman4464 (alex-alexrock) wrote :

Yes, now the option for WPA is not given anywhere, even under the manual setup. I don't have a network cable handy at the moment to see if there are any updates available. I don't know what logs might be useful in this case either.

Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. I noticed that the version of Ubuntu your using is in End of Life status. More information may be found at: https://wiki.ubuntu.com/Releases As well, the package version your bugging is updated in Maverick. Please update via www.ubuntu.com repost a detailed error report, and update the bug status. Thanks!

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
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.