networkmanager prevents wifi to work

Bug #367543 reported by David Jobet on 2009-04-26
2
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: network-manager

I have 2 pcs under linux (k)ubuntu that were running fine under intrepid.
After upgrade to jaunty both wifi stopped working.

My first workstation uses the ath5k with a manual configuration (networkmanager should not be used at all).
However, till I killed networkmanager (sudo /etc/init.d/NetworkManager stop) my wifi connection would not start.
No strange things in /var/log/messages, some warnings in the console when restarting the connection as usual (sudo /etc/init.d/networking restart), but dhcp would never get a lease.
After having killed NetworkManager, I get a lease immediatly.

Second pc is a sony vaio laptop using driver iwl3945.
Browsing the ubuntu forums, I had both to
- add a new file /etc/modprobe.d/iwl3945.conf containing the following line :
  options iwl3945 disable_hw_scan=1
- kill networkmanager (and create a manual configuration)
to make the connection works.

doing rmmod iwl3945 would kernel panic.

If I only add the module option, without killing networkmanager, iwl3945 seems to write a lot of debug messages in /var/log/messages (iwl3945: Tuning to channel XXX, iwl3945: check TGG and auto detect 1 | 1, iwl3945: check anteena 2 1, ...) but both iwconfig and ifconfig shows that the connection is not up, and the configuration ignored !
killing networkmanager fixes the issue (well, I have the network up, but networkmanager is not working for me)

Release : Ubuntu 9.04
Package : network-manager 0.7.1~rc4.1cf199a964-0ubuntu2

David Jobet (david-jobet) wrote :

Read elsewhere it could be a kwallet issue and/or a kde plasma applet issue.
I do not have the plasma applet running. I have knetworkmanager running.

I tried the applet. It seems to be handling better the kwallet (e.g. : asking for permission to access it), and it even seems like scanning and connecting to my network. However the connection is not stable : it constantly loses it and have to re-acquire it. It's not usable at all.

With regular knetworkmanager, it may be a kwallet issue, because kwallet never gets fired.
Trying to activate a connection seems to have no effect, and I regularly see my active iwconfig ssid to be the one of a random existing network, but never the one I asked for !

Manually configuring the network (and killing networkmanager) is ok for me and the connection is rock stable.
=> does not seem to be a module/kernel problem

Well, at least for my iwl3945 module.
My ath5k module on my other box is so slow I cannot do anything with it. I found other bug reports for the ath5k, so I guess this whole entry is a big duplicate.
Sorry for the noise.

Pedro Villavicencio (pedro) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please open a terminal and execute: apport-collect 367543 ? It will attach the necessary information to this report. Also you can submit more information for it by looking to https://wiki.ubuntu.com/DebuggingNetworkManager , Thanks in advance.

Changed in network-manager (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
David Jobet (david-jobet) wrote :

appport wants "change anything" privileges.
No way I'm going to give that kind of privileges to a program.

As for this bug, I've stopped using NetworkManager and now use the kde4 plasma network manager which work even better than the old knetworkmanager and is more user friendly.

This bug report is nearly 5 months old : better close it, I've moved on.

Launchpad Janitor (janitor) wrote :

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

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers