You are not logged in.

#1 2009-06-16 12:01:45

elb
Member
From: France
Registered: 2006-03-17
Posts: 24
Website

[SOLVED] Broadcom bcm4318 cannot connect anymore

Hello,

I'm using arch on a HP Compaq nc6120 laptop with a Broadcom bcm4318 wifi chip. So far it worked correctly with the b43 driver. Now I have the biggest difficulties to connect to any ssid using NetworkManager, although surprisingly it happens to work from times to times. The networks are detected, but connection attempts fail.

I have browsed the forums and the web without success.

I suspect it started with kernel 2.6.29 but I'm not sure it is linked to it. The problem happens with WPA as well as unencrypted networks, so I guess wpa-supplicant is not to suspect.

Here are the relevant lines from /var/log/messages.log :

Jun 16 08:17:06 mamgoudig NetworkManager: <info>  (wlan0): device state change: 1 -> 2
Jun 16 08:17:06 mamgoudig NetworkManager: <info>  (wlan0): bringing up device.
Jun 16 08:17:06 mamgoudig kernel: input: b43-phy0 as /devices/virtual/input/input8
Jun 16 08:17:06 mamgoudig kernel: b43 ssb0:0: firmware: requesting b43/ucode5.fw
Jun 16 08:17:06 mamgoudig kernel: b43 ssb0:0: firmware: requesting b43/pcm5.fw
Jun 16 08:17:06 mamgoudig kernel: b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
Jun 16 08:17:06 mamgoudig kernel: b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
Jun 16 08:17:06 mamgoudig kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Jun 16 08:17:06 mamgoudig kernel: Registered led device: b43-phy0::radio
Jun 16 08:17:06 mamgoudig kernel: b43-phy0: Radio turned on by software
Jun 16 08:17:06 mamgoudig kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 16 08:17:06 mamgoudig NetworkManager: <info>  (wlan0): preparing device.
Jun 16 08:17:06 mamgoudig NetworkManager: <info>  (wlan0): deactivating device (reason: 2).
Jun 16 08:17:06 mamgoudig NetworkManager: <info>  (wlan0): device state change: 2 -> 3
Jun 16 08:17:07 mamgoudig NetworkManager: <info>  (wlan0): supplicant interface state:  starting -> ready
(...)
Jun 16 08:17:47 mamgoudig NetworkManager: <info>  Activation (wlan0) starting connection 'MyPlace'
Jun 16 08:17:47 mamgoudig NetworkManager: <info>  (wlan0): device state change: 3 -> 4
Jun 16 08:17:47 mamgoudig NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 16 08:17:47 mamgoudig NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jun 16 08:17:47 mamgoudig NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jun 16 08:17:47 mamgoudig NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jun 16 08:17:47 mamgoudig NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jun 16 08:17:47 mamgoudig NetworkManager: <info>  (wlan0): device state change: 4 -> 5
Jun 16 08:17:47 mamgoudig NetworkManager: <info>  Activation (wlan0/wireless): access point 'MyPlace' has security, but secrets are required.
Jun 16 08:17:47 mamgoudig NetworkManager: <info>  (wlan0): device state change: 5 -> 6
Jun 16 08:17:47 mamgoudig NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jun 16 08:17:48 mamgoudig NetworkManager: <WARN>  update_one_setting(): Failed to update connection secrets: 1 802-1x
Jun 16 08:17:48 mamgoudig NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.
Jun 16 08:17:48 mamgoudig NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  (wlan0): device state change: 6 -> 4
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  (wlan0): device state change: 4 -> 5
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Activation (wlan0/wireless): connection 'MyPlace' has security, and secrets exist.  No new secrets needed.
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Config: added 'ssid' value 'MyPlace'
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Config: added 'auth_alg' value 'OPEN'
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  Config: set interface ap_scan to 1
Jun 16 08:17:48 mamgoudig NetworkManager: <info>  (wlan0): supplicant connection state:  inactive -> scanning
Jun 16 08:17:49 mamgoudig NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Jun 16 08:17:59 mamgoudig NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Jun 16 08:17:59 mamgoudig NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Jun 16 08:18:00 mamgoudig NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Jun 16 08:18:01 mamgoudig NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected

Any help would be appreciated.

Last edited by elb (2009-06-19 07:42:29)

Offline

#2 2009-06-18 08:17:05

elb
Member
From: France
Registered: 2006-03-17
Posts: 24
Website

Re: [SOLVED] Broadcom bcm4318 cannot connect anymore

I probably found the cause of the problem : I had followed recommendations in the wiki (http://wiki.archlinux.org/index.php/Net … Kit_issues) and applied the first option (by modifying /etc/pam.d/kde).
I came into some authorizations problems : mounting usb devices with Dolphin became impossible, and I strongly suspect my wifi problems happened after that.
I rolled back the modification yesterday and since that I haven't encountered connection problems anymore.

Offline

Board footer

Powered by FluxBB