Broadcom 4312(b43) with opensuse 11.3 wont work :(

Sandel-UA · August 23, 2010, 4:46pm

Greetings!

Well I see there is a lot of people which have problems with BCM4312

I read that topics but my problem kind of different…

I installed 11.3 few day ago at my job. Everything was just fine…

First of all I’m installed firmware

install_bcm43xx_firmware

Wireless worked fine…

When i come back home, I could’t make it work…
I mean my laptop WiFi bcm4312 with my home WiFi point (router Linksys WRT54GL with DD-WRT firmware)

Other devices (such as phone, other laptop(Windows)) work fine with Linksys.

My laptop Dell Vostro 1310

# /sbin/lspci -nnv | grep -i broadcom
06:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
# uname -a
Linux orion.somewhere 2.6.34-12-default #1 SMP 2010-06-29 02:39:08 +0200 i686 i686 i386 GNU/Linux
# dmesg | grep -i broad
   12.698446] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
   12.876192] Broadcom 43xx driver loaded  Features: PMLS, Firmware-ID: FW13 ]

Encryption on Linksys is WPA2 Personal Mixed TKIP+AES…

So I click to NetworkManager icon and choose my wireless connection (my home WiFi point)
Logs below:

/var/log/NetworkManager

Aug 23 17:20:32 orion NetworkManager: <info>  Activation (wlan0) starting connection 'ho'
Aug 23 17:20:32 orion NetworkManager: <info>  (wlan0): device state change: 3 -> 4 (reason 0)
Aug 23 17:20:32 orion NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Aug 23 17:20:32 orion NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Aug 23 17:20:32 orion NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Aug 23 17:20:32 orion NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Aug 23 17:20:32 orion NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Aug 23 17:20:32 orion NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Aug 23 17:20:32 orion NetworkManager: <info>  Activation (wlan0/wireless): connection 'ho' has security, and secrets exist.  No new secrets needed.
Aug 23 17:20:32 orion NetworkManager: <info>  Config: added 'ssid' value 'nk002g'
Aug 23 17:20:32 orion NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Aug 23 17:20:32 orion NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Aug 23 17:20:32 orion NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Aug 23 17:20:32 orion NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Aug 23 17:20:32 orion NetworkManager: <info>  Config: set interface ap_scan to 1
Aug 23 17:20:32 orion NetworkManager: <info>  (wlan0): supplicant connection state:  inactive -> scanning
Aug 23 17:20:33 orion NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating

/var/log/wpa_supplicant.log

Trying to associate with 00:1d:7e:bd:4a:46 (SSID='nk002g' freq=2437 MHz)

so… that ok… right? And after few seconds:

/var/log/NetworkManager

Aug 23 17:20:43 orion NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Aug 23 17:20:43 orion NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning

Authentication with 00:1d:7e:bd:4a:46 timed out.

this is bad ((
and at last

/var/log/NetworkManager

Aug 23 17:20:44 orion NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug 23 17:20:54 orion NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Aug 23 17:20:54 orion NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug 23 17:20:56 orion NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug 23 17:20:58 orion NetworkManager: <info>  Activation (wlan0/wireless): association took too long.
Aug 23 17:20:58 orion NetworkManager: <info>  (wlan0): device state change: 5 -> 6 (reason 0)
Aug 23 17:20:58 orion NetworkManager: <info>  Activation (wlan0/wireless): asking for new secrets
Aug 23 17:20:58 orion NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected

/var/log/wpa_supplicant.log

Trying to associate with 00:1d:7e:bd:4a:46 (SSID='nk002g' freq=2437 MHz)
Authentication with 00:1d:7e:bd:4a:46 timed out.
Trying to associate with 00:1d:7e:bd:4a:46 (SSID='nk002g' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.

and here /var/log/messages log

Aug 23 17:20:33 orion kernel: [12902.749650] wlan0: authenticate with 00:1d:7e:bd:4a:46 (try 1)
Aug 23 17:20:33 orion kernel: [12902.767601] wlan0: 00:1d:7e:bd:4a:46 denied authentication (status 13)

after this appears KnetworkManager GUI with password form… even if I reenter password, it is wont work ((

On openSuSE 11.1 with wl driver it works.

Passphrase is 100% right… I rechecked it on other devices…

I don’t understand what I do wrong…

By the way… I don’t want to use wl driver because it’s buggy :(… I was very happy when saw that openSuSE 11.3 kernel support default b43 driver…

Sandel-UA · August 23, 2010, 5:06pm

aarrrgghhh >:(

even if i turn Wireless Security Mode from WPA2 to Disabled (non-password WiFi point) i’m still going to get something like

denied authentication

Logs with Wireless Security Mode Disabled

/var/log/NetworkManager

Aug 23 17:59:02 orion NetworkManager: <info>  Activation (wlan0) starting connection 'su'
Aug 23 17:59:02 orion NetworkManager: <info>  (wlan0): device state change: 3 -> 4 (reason 0)
Aug 23 17:59:02 orion NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Aug 23 17:59:02 orion NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Aug 23 17:59:02 orion NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Aug 23 17:59:02 orion NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Aug 23 17:59:02 orion NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Aug 23 17:59:02 orion NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Aug 23 17:59:02 orion NetworkManager: <info>  Activation (wlan0/wireless): connection 'su' requires no security.  No secrets needed.
Aug 23 17:59:02 orion NetworkManager: <info>  Config: added 'ssid' value 'nk002g'
Aug 23 17:59:02 orion NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Aug 23 17:59:02 orion NetworkManager: <info>  Config: added 'key_mgmt' value 'NONE'
Aug 23 17:59:02 orion NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Aug 23 17:59:02 orion NetworkManager: <info>  Config: set interface ap_scan to 1
Aug 23 17:59:02 orion NetworkManager: <info>  (wlan0): supplicant connection state:  inactive -> scanning
Aug 23 17:59:03 orion NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug 23 17:59:13 orion NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Aug 23 17:59:13 orion NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug 23 17:59:14 orion NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug 23 17:59:24 orion NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Aug 23 17:59:24 orion NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug 23 17:59:26 orion NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug 23 17:59:27 orion NetworkManager: <info>  Activation (wlan0/wireless): association took too long, failing activation.
Aug 23 17:59:27 orion NetworkManager: <info>  (wlan0): device state change: 5 -> 9 (reason 11)
Aug 23 17:59:27 orion NetworkManager: <info>  Activation (wlan0) failed for access point (nk002g)
Aug 23 17:59:27 orion NetworkManager: <info>  Marking connection 'su' invalid.
Aug 23 17:59:27 orion NetworkManager: <info>  Activation (wlan0) failed.
Aug 23 17:59:27 orion NetworkManager: <info>  (wlan0): device state change: 9 -> 3 (reason 0)
Aug 23 17:59:27 orion NetworkManager: <info>  (wlan0): deactivating device (reason: 0).

/var/log/wpa_supplicant.log

Trying to associate with 00:1d:7e:bd:4a:46 (SSID='nk002g' freq=2437 MHz)
Authentication with 00:1d:7e:bd:4a:46 timed out.
Trying to associate with 00:1d:7e:bd:4a:46 (SSID='nk002g' freq=2437 MHz)
Authentication with 00:1d:7e:bd:4a:46 timed out.
Trying to associate with 00:1d:7e:bd:4a:46 (SSID='nk002g' freq=2437 MHz)
Authentication with 00:00:00:00:00:00 timed out.

/var/log/messages

Aug 23 17:59:03 orion kernel: [15212.593111] wlan0: authenticate with 00:1d:7e:bd:4a:46 (try 1)
Aug 23 17:59:03 orion kernel: [15212.595053] wlan0: 00:1d:7e:bd:4a:46 denied authentication (status 13)
Aug 23 17:59:14 orion kernel: [15223.900701] wlan0: authenticate with 00:1d:7e:bd:4a:46 (try 1)
Aug 23 17:59:14 orion kernel: [15223.902624] wlan0: 00:1d:7e:bd:4a:46 denied authentication (status 13)
Aug 23 17:59:26 orion kernel: [15235.201105] wlan0: authenticate with 00:1d:7e:bd:4a:46 (try 1)
Aug 23 17:59:26 orion kernel: [15235.203494] wlan0: 00:1d:7e:bd:4a:46 denied authentication (status 13)

Sandel-UA · August 23, 2010, 5:37pm

oops sorry… i forgot change value “Authentication Type” from “Shared Key” to “Auto” at Linksys router… i did some tests with this and others values… but no result…

So below logs with “Wireless Security Mode Disable”

/var/log/NetworkManager

Aug 23 18:31:35 orion NetworkManager: <info>  Activation (wlan0) starting connection 'fuu'
Aug 23 18:31:35 orion NetworkManager: <info>  (wlan0): device state change: 3 -> 4 (reason 0)
Aug 23 18:31:35 orion NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Aug 23 18:31:35 orion NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Aug 23 18:31:35 orion NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Aug 23 18:31:35 orion NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Aug 23 18:31:35 orion NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Aug 23 18:31:35 orion NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Aug 23 18:31:35 orion NetworkManager: <info>  Activation (wlan0/wireless): connection 'fuu' requires no security.  No secrets needed.
Aug 23 18:31:35 orion NetworkManager: <info>  Config: added 'ssid' value 'nk002g'
Aug 23 18:31:35 orion NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Aug 23 18:31:35 orion NetworkManager: <info>  Config: added 'key_mgmt' value 'NONE'
Aug 23 18:31:35 orion NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Aug 23 18:31:35 orion NetworkManager: <info>  Config: set interface ap_scan to 1
Aug 23 18:31:35 orion NetworkManager: <info>  (wlan0): supplicant connection state:  inactive -> scanning
Aug 23 18:31:37 orion NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Aug 23 18:31:37 orion NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Aug 23 18:31:37 orion NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> completed
Aug 23 18:31:37 orion NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'nk002g'.
Aug 23 18:31:37 orion NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Aug 23 18:31:37 orion NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Aug 23 18:31:37 orion NetworkManager: <info>  (wlan0): device state change: 5 -> 7 (reason 0)
Aug 23 18:31:37 orion NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction (timeout in 45 seconds)
Aug 23 18:31:37 orion NetworkManager: <info>  dhclient started with pid 15100
Aug 23 18:31:37 orion NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) scheduled...
Aug 23 18:31:37 orion NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Aug 23 18:31:37 orion NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) started...
Aug 23 18:31:37 orion NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) complete.
Aug 23 18:31:37 orion NetworkManager: <info>  DHCP: device wlan0 state changed normal exit -> preinit

Aug 23 18:31:43 orion NetworkManager: <info>  DHCP: device wlan0 state changed preinit -> bound
Aug 23 18:31:43 orion NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Aug 23 18:31:43 orion NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Aug 23 18:31:43 orion NetworkManager: <info>    address 10.72.0.5
Aug 23 18:31:43 orion NetworkManager: <info>    prefix 28 (255.255.255.240)
Aug 23 18:31:43 orion NetworkManager: <info>    gateway 10.72.0.1
Aug 23 18:31:43 orion NetworkManager: <info>    nameserver '109.86.2.2'
Aug 23 18:31:43 orion NetworkManager: <info>    nameserver '109.86.2.21'
Aug 23 18:31:43 orion NetworkManager: <info>    domain name 'kievnet.com'
Aug 23 18:31:43 orion NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Aug 23 18:31:43 orion NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Aug 23 18:31:43 orion NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Aug 23 18:31:44 orion NetworkManager: <debug> [1282577504.033179] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
Aug 23 18:31:44 orion NetworkManager: <debug> [1282577504.036001] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'#012
Aug 23 18:31:44 orion NetworkManager: <debug> [1282577504.036378] write_to_netconfig(): Writing to netconfig: DNSSEARCH='kievnet.com kievnet.com'#012
Aug 23 18:31:44 orion NetworkManager: <debug> [1282577504.036624] write_to_netconfig(): Writing to netconfig: DNSSERVERS='109.86.2.2 109.86.2.21'#012
Aug 23 18:31:44 orion NetworkManager: <info>  Clearing nscd hosts cache.
Aug 23 18:31:44 orion NetworkManager: <info>  (wlan0): device state change: 7 -> 8 (reason 0)
Aug 23 18:31:44 orion NetworkManager: <debug> [1282577504.043536] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
Aug 23 18:31:44 orion NetworkManager: <debug> [1282577504.046370] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'#012
Aug 23 18:31:44 orion NetworkManager: <debug> [1282577504.046427] write_to_netconfig(): Writing to netconfig: DNSSEARCH='kievnet.com kievnet.com'#012
Aug 23 18:31:44 orion NetworkManager: <debug> [1282577504.046446] write_to_netconfig(): Writing to netconfig: DNSSERVERS='109.86.2.2 109.86.2.21'#012
Aug 23 18:31:44 orion NetworkManager: <info>  Clearing nscd hosts cache.
Aug 23 18:31:44 orion NetworkManager: <info>  Policy set 'fuu' (wlan0) as default for routing and DNS.
Aug 23 18:31:44 orion NetworkManager: <info>  Activation (wlan0) successful, device activated.
Aug 23 18:31:44 orion NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Aug 23 18:31:44 orion nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.


Aug 23 18:32:00 orion NetworkManager: <info>  (wlan0): supplicant connection state:  completed -> disconnected
Aug 23 18:32:00 orion NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Aug 23 18:32:01 orion NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating



Aug 23 18:32:05 orion NetworkManager: <debug> [1282577525.002536] periodic_update(): Roamed from BSSID 00:1D:7E:BD:4A:46 (nk002g) to (none) ((none))
Aug 23 18:32:11 orion NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected
Aug 23 18:32:11 orion NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
^[24;2~Aug 23 18:32:16 orion NetworkManager: <info>  (wlan0): device state change: 8 -> 3 (reason 11)
Aug 23 18:32:16 orion NetworkManager: <info>  (wlan0): deactivating device (reason: 11).
Aug 23 18:32:16 orion NetworkManager: <info>  (wlan0): canceled DHCP transaction, dhcp client pid 15100
Aug 23 18:32:16 orion NetworkManager: <WARN>  check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess#012
Aug 23 18:32:16 orion NetworkManager: <debug> [1282577536.204722] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
Aug 23 18:32:16 orion NetworkManager: <debug> [1282577536.209101] write_to_netconfig(): Writing to netconfig: INTERFACE='wlan0'#012
Aug 23 18:32:16 orion NetworkManager: <info>  Clearing nscd hosts cache.
Aug 23 18:32:16 orion nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.

/var/log/messages

Aug 23 18:31:37 orion kernel: [17166.201649] wlan0: authenticate with 00:1d:7e:bd:4a:46 (try 1)
Aug 23 18:31:37 orion kernel: [17166.204205] wlan0: authenticated
Aug 23 18:31:37 orion kernel: [17166.204635] wlan0: associate with 00:1d:7e:bd:4a:46 (try 1)
Aug 23 18:31:37 orion kernel: [17166.207049] wlan0: RX AssocResp from 00:1d:7e:bd:4a:46 (capab=0x401 status=0 aid=1)
Aug 23 18:31:37 orion kernel: [17166.207053] wlan0: associated
Aug 23 18:31:37 orion kernel: [17166.208330] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Aug 23 18:31:37 orion dhclient: Internet Systems Consortium DHCP Client 4.1.1-P1
Aug 23 18:31:37 orion dhclient: Copyright 2004-2010 Internet Systems Consortium.
Aug 23 18:31:37 orion dhclient: All rights reserved.
Aug 23 18:31:37 orion dhclient: For info, please visit https://www.isc.org/software/dhcp/
Aug 23 18:31:37 orion dhclient: 
Aug 23 18:31:37 orion dhclient: Listening on LPF/wlan0/00:22:5f:06:cb:c6
Aug 23 18:31:37 orion dhclient: Sending on   LPF/wlan0/00:22:5f:06:cb:c6
Aug 23 18:31:37 orion dhclient: Sending on   Socket/fallback
Aug 23 18:31:38 orion dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Aug 23 18:31:39 orion dhclient: DHCPOFFER from 10.72.0.1
Aug 23 18:31:39 orion kernel: [17168.175311] martian source 255.255.255.255 from 10.72.0.1, on dev wlan0
Aug 23 18:31:39 orion kernel: [17168.175318] ll header: ff:ff:ff:ff:ff:ff:00:1d:7e:bd:4a:44:08:00

Aug 23 18:31:43 orion dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Aug 23 18:31:43 orion dhclient: DHCPACK from 10.72.0.1
Aug 23 18:31:43 orion kernel: [17172.171295] martian source 255.255.255.255 from 10.72.0.1, on dev wlan0
Aug 23 18:31:43 orion kernel: [17172.171302] ll header: ff:ff:ff:ff:ff:ff:00:1d:7e:bd:4a:44:08:00
Aug 23 18:31:43 orion dhclient: bound to 10.72.0.5 -- renewal in 32725 seconds.
Aug 23 18:31:43 orion avahi-daemon[2125]: Joining mDNS multicast group on interface wlan0.IPv4 with address 10.72.0.5.
Aug 23 18:31:43 orion avahi-daemon[2125]: New relevant interface wlan0.IPv4 for mDNS.
Aug 23 18:31:43 orion avahi-daemon[2125]: Registering new address record for 10.72.0.5 on wlan0.IPv4.
Aug 23 18:31:44 orion if-up.d/21-dhcpcd-hook-samba: No dhcpcd info nor dhclient leases file found for wlan0.
Aug 23 18:31:44 orion SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Aug 23 18:31:44 orion SuSEfirewall2: using default zone 'ext' for interface pan0
Aug 23 18:31:44 orion SuSEfirewall2: batch committing...
Aug 23 18:31:44 orion SuSEfirewall2: Firewall rules successfully set
Aug 23 18:31:44 orion sm-notify[15367]: Already notifying clients; Exiting!


Aug 23 18:32:00 orion kernel: [17189.488181] No probe response from AP 00:1d:7e:bd:4a:46 after 500ms, disconnecting.
Aug 23 18:32:00 orion kernel: [17189.497704] cfg80211: Calling CRDA to update world regulatory domain
Aug 23 18:32:00 orion kernel: [17189.506473] cfg80211: World regulatory domain updated:
Aug 23 18:32:00 orion kernel: [17189.506480]     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Aug 23 18:32:00 orion kernel: [17189.506488]     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Aug 23 18:32:00 orion kernel: [17189.506495]     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Aug 23 18:32:00 orion kernel: [17189.506502]     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Aug 23 18:32:00 orion kernel: [17189.506508]     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Aug 23 18:32:00 orion kernel: [17189.506515]     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Aug 23 18:32:01 orion kernel: [17190.897040] wlan0: authenticate with 00:1d:7e:bd:4a:46 (try 1)
Aug 23 18:32:01 orion kernel: [17191.096112] wlan0: authenticate with 00:1d:7e:bd:4a:46 (try 2)
Aug 23 18:32:02 orion kernel: [17191.296172] wlan0: authenticate with 00:1d:7e:bd:4a:46 (try 3)
Aug 23 18:32:02 orion kernel: [17191.496176] wlan0: authentication with 00:1d:7e:bd:4a:46 timed out


Aug 23 18:32:16 orion avahi-daemon[2125]: Withdrawing address record for 10.72.0.5 on wlan0.
Aug 23 18:32:16 orion avahi-daemon[2125]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.72.0.5.
Aug 23 18:32:16 orion avahi-daemon[2125]: Interface wlan0.IPv4 no longer relevant for mDNS.

/var/log/wpa_supplicant.log

Trying to associate with 00:1d:7e:bd:4a:46 (SSID='nk002g' freq=2437 MHz)
Associated with 00:1d:7e:bd:4a:46
CTRL-EVENT-CONNECTED - Connection to 00:1d:7e:bd:4a:46 completed (auth) [id=0 id_str=]



CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:1d:7e:bd:4a:46 (SSID='nk002g' freq=2437 MHz)


Authentication with 00:1d:7e:bd:4a:46 timed out.

as you can see connections is success… also i getting dhcp
i can ping hosts, etc…
it appears at 18:31:44

but at 18:32:00 connection is goes down (((

lwfinger · August 23, 2010, 5:37pm

On 08/23/2010 10:06 AM, Sandel-UA wrote:
>
> I don’t understand what I do wrong…
>
> By the way… I don’t want to use wl driver because it’s buggy :(… I
> was very happy when saw that openSuSE 11.3 kernel support default b43
> driver…

I can assure you that b43 supports WPA/WPA2 with AES+TKIP. I’m using it as I
send this message.

Are you using KDE or Gnome? If KDE, click on the knetworkmanager applet, then on
“Manage Connections” and create your new connection there. If it already exists,
delete it and recreate it. Sometimes, the pop-up authentication screens do not
get the right info back to the database. If you are using Gnome, the procedure
should be similar.

Sandel-UA · August 23, 2010, 6:41pm

lwfinger, thanks for answer… i didn’t saw you post at first time…

yes, i’m using KDE…

create your new connection there. If it already exists,
delete it and recreate it.

I did it ~50 times… i did a lot of tests but no result (((

btw… if on Linksys i switch encrypt from WPA2 Personal Mixed TKIP+AES to WPA2 Personal TKIP
i’ll get same as in this topic.

No probe response from AP ... after 500ms, disconnecting.

taytong888 · August 25, 2010, 3:52am

Hi,

I thought I am the only person with the problem of authentication window popping up. I have the same messages in dmesg and /var/log/NetworkManager. The only difference is Atheros madwifi ath5k driver in a built-in miniPCI wireless adapter in my laptop. I am running openSUSE11.3 Gnome, kernel 2.6.34.12-default kernel.

joonR · August 26, 2010, 5:54pm

I’m using Gnome and Dell E6400. I found that bcm43xx_firmware does not work with my home router either. It does not work well with WEP passphrase. So I uninstalled it, and installed broadcom-wl, broadcom-wl-kmp-default, broadcom-wl-kmp-desktop and now it works fine.

lwfinger · August 26, 2010, 6:31pm

On 08/26/2010 11:06 AM, joonR wrote:
>
> I’m using Gnome and Dell E6400. I found that bcm43xx_firmware does not
> work with my home router either. It does not work well with WEP
> passphrase. So I uninstalled it, and installed broadcom-wl,
> broadcom-wl-kmp-default, broadcom-wl-kmp-desktop and now it works fine.

No mac80211 driver works with a WEP passphrase. You need to use the hex key.

Using wl is OK, but remember that it will break with every new kernel until you
load the packages for that new kernel.

Sandel-UA · August 27, 2010, 4:25pm

ok… I installed broadcom-wl, broadcom-wl-kmp-default, broadcom-wl-kmp-desktop few minutes ago…

# dmesg | grep -i broa
    5.875418] eth0: Broadcom BCM4315 802.11 Hybrid Wireless Controller 5.60.48.36

also did it:

# cat /etc/modprobe.d/49-b43.conf 
blacklist bcm43xx
blacklist b43

when i disable Wireless with NetworkManager GUI, LED on my laptop is light down…
and when i enable wireless it’s light up… so it’s works… but in “Select Wireless Network” window there are nothing… i can’t join to access points because the window is empty

any idea?

I already reboot laptop and delete all connections in NetworkManager GUI…

Sandel-UA · August 27, 2010, 5:20pm

Wait a minute… i’m use BCM4312, not BCM4315…

# lspci -nnk | grep -i broad
06:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)

eehhh… why dmesg tells me that i use BCM4315?

It’s strange :’(

btw

# sudo iwlist scan
lo        Interface doesn't support scanning.

eth1      No scan results

eth0      Interface doesn't support scanning.

pan0      Interface doesn't support scanning.

eth1 wireless tells me that no WiFi points in my area… but there are at least 3 points…

Sandel-UA · August 28, 2010, 12:14pm

any idea?
I tried to fix this problem about week :’(
don’t know what to do else…

lwfinger · August 28, 2010, 5:56pm

On 08/28/2010 05:36 AM, Sandel-UA wrote:
>
> any idea?
> I tried to fix this problem about week :’(
> don’t know what to do else…

Sorry. I do not help with wl for those devices that work with b43/ssb.

Sandel-UA · August 28, 2010, 11:19pm

I don’t know what to say…

I tried everything that I know to connect the wireless to the laptop with b43/ssb… really… I like b43/ssb
I even reinstalled the firmware on the router… but it (b43/ssb) doesn’t connect… all devices works fine, but my laptope with b43/ssb doesn’t connect…
I spend a lot of time “playing” with settings at router… it’s doesn’t work (((

Sandel-UA · August 29, 2010, 12:02am

Ok, now I really confused! I turned on laptop few minutes ago and Wireless with WL driver found points… I successfully connect to it… I rebooted laptop few times… tried “default” and “desktop” kernels and it’s still works… I turning off laptop now… Tomorrow I’ll check whether it will work or not

Sandel-UA · August 29, 2010, 2:21pm

heh… well, WL works now… don’t know what to say… thanks for help everyone rotfl!

joonR · August 30, 2010, 10:08pm

Glad to hear it. May I ask you are you using the firmware or the -wl stuff?

trueshanti · September 1, 2010, 9:07pm

wow … thats hard to read … i was glad to finally find a threat about that … it really s0cks … exactly the same behaviour on my side … :-p

i suspect NW to be an idiot … cant proove it … still waiting for a clue … br

rhasselbaum · September 20, 2010, 3:19pm

I am having the same problem. If I use the b43 driver with firmware, I get a timeout during connect (“No probe response from AP xxxx after 500ms, disconnecting” in /var/log/messages). When I switch to the **broadcom-wl ** driver, I don’t see any wireless networks at all. The strange thing is that the same hardware worked fine with broadcom-wl under 64-bit openSUSE 11.3. But since I switched to 32-bit (after frustrations with Flash), I can’t get the wireless card working. The lspci output is as follows:


0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
        Subsystem: Dell Wireless 1395 WLAN Mini-Card
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at f1ffc000 (64-bit, non-prefetchable) [size=16]
        Capabilities: [40] Power Management version 3
        Capabilities: [58] Vendor Specific Information: Len=78 <?>
        Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [d0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Virtual Channel
        Capabilities: [160] Device Serial Number c9-19-e1-ff-ff-c3-00-1f
        Capabilities: [16c] Power Budgeting <?>
        Kernel driver in use: b43-pci-bridge

Any other ideas?[/size]

knurpht · September 20, 2010, 3:33pm

For the 4312 you need the broadcom-wl driver. The package and the kernel module. Don’t forget to reboot. As you can see it’s still using the b43 driver.

If this worked on 64bit openSUSE, why did you switch to 32bit? I run 64bit with Flash, no issues at all. Changing to 32bit should not be a solution

rhasselbaum · September 20, 2010, 3:58pm

I had uninstalled the broadcom-wl driver when I ran lspci above. That’s why you see b43 listed. I guess I will experiment with broadcom-wl some more. One thing I can’t remember about when I had it working under 64-bit openSUSE is whether I was using the desktop or the default kernel. Right now, on 32-bit, I am using the desktop kernel. I suppose I could try switching kernels, but don’t know what other side-effects that will have.

I switched to 32-bit because Flash was very flaky under 64-bit with the wrapper on two different boxes. Fullscreen video performance (e.g. Hulu) was horrible. And when I had multuple Firefox tabs open with Flash content on each (e.g. Pandora plus one other), it was almost a certainty that Flash would crash or stop responding within minutes. All of these problems went away when I switched to 32-bit openSUSE on one of the boxes. On the remaining 64-bit box, I just installed the 64-bit prerelease of Flash that Adobe put out last week and it seems to be more stable. But all this is a story for another thread…