bcmwl doesn't handle powermanagement on/off properly, turns device on or off

[Dave Morley]

Binary package hint: network-manager

Network-manager on une desktop doesn't connect, however if I log out and log back in but on normal desktop it connects without fault. I'm making a huge assumption that there is something conflicting on in the une desktop version.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: network-manager 0.8.1+git.20100810t184654.ab580f4-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: wl
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Mon Sep 27 22:47:48 2010
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
IpRoute:
 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.6 metric 2
 169.254.0.0/16 dev eth1 scope link metric 1000
 default via 192.168.1.1 dev eth1 proto static
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
RfKill:
 0: hp-wifi: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager

[Dave Morley (davmor2)]

output from /var/log/daemon.log

Sep 29 12:00:23 bilbo NetworkManager[822]: <info> (eth1): DHCPv4 state changed nbi -> preinit
Sep 29 12:00:23 bilbo dhclient: Listening on LPF/eth1/00:26:5e:58:bf:21
Sep 29 12:00:23 bilbo dhclient: Sending on LPF/eth1/00:26:5e:58:bf:21
Sep 29 12:00:23 bilbo dhclient: Sending on Socket/fallback
Sep 29 12:00:23 bilbo dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
Sep 29 12:00:26 bilbo dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
Sep 29 12:00:27 bilbo dhclient: DHCPOFFER of 192.168.1.6 from 192.168.1.1
Sep 29 12:00:27 bilbo dhclient: DHCPREQUEST of 192.168.1.6 on eth1 to 255.255.255.255 port 67
Sep 29 12:00:53 bilbo dhclient: last message repeated 2 times
Sep 29 12:00:53 bilbo dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
Sep 29 12:00:56 bilbo dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
Sep 29 12:01:00 bilbo dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
Sep 29 12:01:09 bilbo NetworkManager[822]: <warn> (eth1): DHCPv4 request timed out.
Sep 29 12:01:09 bilbo NetworkManager[822]: <info> (eth1): canceled DHCP transaction, DHCP client pid 1599
Sep 29 12:01:09 bilbo NetworkManager[822]: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Timeout) scheduled...
Sep 29 12:01:09 bilbo NetworkManager[822]: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Timeout) started...
Sep 29 12:01:09 bilbo NetworkManager[822]: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
Sep 29 12:01:09 bilbo NetworkManager[822]: <info> Activation (eth1) Stage 4 of 5 (IP4 Configure Timeout) complete.
Sep 29 12:01:09 bilbo NetworkManager[822]: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
Sep 29 12:01:09 bilbo NetworkManager[822]: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) failed (no IP configuration found)
Sep 29 12:01:09 bilbo NetworkManager[822]: <info> (eth1): device state change: 7 -> 9 (reason 5)
Sep 29 12:01:09 bilbo NetworkManager[822]: <warn> Activation (eth1) failed for access point (davmor2)
Sep 29 12:01:09 bilbo NetworkManager[822]: <info> Marking connection 'Auto davmor2' invalid.
Sep 29 12:01:09 bilbo NetworkManager[822]: <warn> Activation (eth1) failed.
Sep 29 12:01:09 bilbo NetworkManager[822]: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
Sep 29 12:01:09 bilbo NetworkManager[822]: <info> (eth1): device state change: 9 -> 3 (reason 0)
Sep 29 12:01:09 bilbo NetworkManager[822]: <info> (eth1): deactivating device (reason: 0).
Sep 29 12:01:09 bilbo wpa_supplicant[828]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

[Dave Morley (davmor2)]

This was working flawlessly on this machine till the last Linux update. I assumed there was an issue with one of the upgrades so today I tried a fresh install and got the same issue. The wifi see the router and just fails to connect to it. This is using the Broadcom STA driver.

[Mathieu Trudel-Lapierre (cyphermox)]

Dave,

Could you tell us what kind of system this is? I'd like to test on two netbooks to see if I can reproduce the issue (since I didn't see this on my own netbook, but maybe I wasn't quite up to date). So I'd test with a system similar to yours if I can put my hands on one, and another without broadcom wifi.

[Mathieu Trudel-Lapierre (cyphermox)]

I'm unable to reproduce this on a clean install of Maverick netbook with image 20100928.2; on a very similar Compaq Mini which has the same wireless chip (checked PCI IDs). I will test an upgrade from Lucid netbook edition.

[Dave Morley (davmor2)]

This now turns out to be a likely PM issue. If I unplug the laptop from the power the wifi cannot connect, if I plug the netbook back into the power it connects first time.

[Dave Morley (davmor2)]

This is on a compaq mini 110

[Dave Morley (davmor2)]

Following advice on #ubuntu-desktop I unplugged the power supply and tried to connect with no joy. I then ran "sudo pm-powersave false" and tried to connect once more this time successfully leading me to believe that this is definitely an issue within pm-utils not n-m

[Mathieu Trudel-Lapierre (cyphermox)]

I've been digging deeper into the wireless script in pm-utils and it looks like the wireless driver might be at fault, this seems to be an issue with it handling the "power on" and "power off" iwconfig commands (turning power-management on or off).

Reassigning to bcmwl.