Fedora Linux Support Community & Resources Center

Home Forums Posting Rules Linux Help Fedora Set-Up Guides Ask Fedora Fedora Project
Go Back   FedoraForum.org > Fedora 17/18 > Servers & Networking
Reload this Page fc11: broadcom BCM4322 can't authenticate
FedoraForum Search
Forgot Password? Join Us!
Register All Albums FAQ Search Today's Posts Mark Forums Read

Servers & Networking Discuss any Fedora server problems and Networking issues such as dhcp, IP numbers, wlan, modems, etc.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 15th July 2009, 12:22 AM
mike.slass Offline
Registered User
  
Join Date: Jul 2009
Posts: 1
fc11: broadcom BCM4322 can't authenticate
I can't get my Broadcoam BCM4322 to connect to a protected access point.
I've tried the drivers from rpmfusion, and tried to build the module with the source+binary package from Broadcom, all with no luck. The failure seems to happen during the WPA negotiation.

I haven't tried connecting to an unsecured WiFi access point.

When booting this same laptop to Kubuntu 9.04, it can connect to secured, so it is possible under linux.

Here's output from lspci, and the tail of the log while KNetworkManager is trying to connect the device.

Help appreciated.

lspci | grep -i network
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
0c:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)

tail -F /var/log/messages
Jul 14 15:59:12 laptop NetworkManager: <info> Activation (eth1) starting connection 'SeattleHQ'
Jul 14 15:59:12 laptop NetworkManager: <info> (eth1): device state change: 3 -> 4
Jul 14 15:59:12 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jul 14 15:59:12 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jul 14 15:59:12 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jul 14 15:59:12 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jul 14 15:59:12 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jul 14 15:59:12 laptop NetworkManager: <info> (eth1): device state change: 4 -> 5
Jul 14 15:59:12 laptop NetworkManager: <info> Activation (eth1/wireless): access point 'SeattleHQ' has security, but secrets are required.
Jul 14 15:59:12 laptop NetworkManager: <info> (eth1): device state change: 5 -> 6
Jul 14 15:59:12 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jul 14 15:59:18 laptop NetworkManager: <info> (eth1): supplicant connection state: scanning -> inactive
Jul 14 15:59:20 laptop NetworkManager: <WARN> update_one_setting(): Failed to update connection secrets: 1 802-1x
Jul 14 15:59:20 laptop NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.
Jul 14 15:59:20 laptop NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.
Jul 14 15:59:20 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jul 14 15:59:20 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jul 14 15:59:20 laptop NetworkManager: <info> (eth1): device state change: 6 -> 4
Jul 14 15:59:20 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jul 14 15:59:20 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jul 14 15:59:20 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jul 14 15:59:20 laptop NetworkManager: <info> (eth1): device state change: 4 -> 5
Jul 14 15:59:20 laptop NetworkManager: <info> Activation (eth1/wireless): connection 'SeattleHQ' has security, and secrets exist. No new secrets needed.
Jul 14 15:59:20 laptop NetworkManager: <info> Config: added 'ssid' value 'SeattleHQ'
Jul 14 15:59:20 laptop NetworkManager: <info> Config: added 'scan_ssid' value '1'
Jul 14 15:59:20 laptop NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Jul 14 15:59:20 laptop NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Jul 14 15:59:20 laptop NetworkManager: <info> Config: added 'psk' value '<omitted>'
Jul 14 15:59:20 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jul 14 15:59:20 laptop NetworkManager: <info> Config: set interface ap_scan to 1
Jul 14 15:59:20 laptop NetworkManager: <info> (eth1): supplicant connection state: inactive -> scanning
Jul 14 15:59:25 laptop NetworkManager: <info> (eth1): supplicant connection state: scanning -> associating
Jul 14 15:59:28 laptop NetworkManager: <info> (eth1): supplicant connection state: associating -> 4-way handshake
Jul 14 15:59:28 laptop NetworkManager: <info> (eth1): supplicant connection state: 4-way handshake -> associated
Jul 14 15:59:29 laptop NetworkManager: <info> (eth1): supplicant connection state: associated -> 4-way handshake
Jul 14 15:59:32 laptop NetworkManager: <info> (eth1): supplicant connection state: 4-way handshake -> disconnected
Jul 14 15:59:32 laptop NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
Jul 14 15:59:39 laptop NetworkManager: <info> (eth1): supplicant connection state: scanning -> disconnected
Jul 14 15:59:39 laptop NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
Jul 14 15:59:45 laptop NetworkManager: <info> (eth1): supplicant connection state: scanning -> associated
Jul 14 15:59:45 laptop NetworkManager: <info> (eth1): supplicant connection state: associated -> 4-way handshake
Jul 14 15:59:46 laptop NetworkManager: <info> Activation (eth1/wireless): association took too long.
Jul 14 15:59:46 laptop NetworkManager: <info> (eth1): device state change: 5 -> 6
Jul 14 15:59:46 laptop NetworkManager: <info> Activation (eth1/wireless): asking for new secrets
Jul 14 15:59:46 laptop NetworkManager: <info> (eth1): supplicant connection state: 4-way handshake -> disconnected
Jul 14 15:59:57 laptop NetworkManager: <WARN> update_one_setting(): Failed to update connection secrets: 1 802-1x
Jul 14 15:59:57 laptop NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.
Jul 14 15:59:57 laptop NetworkManager: <WARN> real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.
Jul 14 15:59:57 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Jul 14 15:59:57 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Jul 14 15:59:57 laptop NetworkManager: <info> (eth1): device state change: 6 -> 4
Jul 14 15:59:57 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Jul 14 15:59:57 laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Jul 14 15:59:57 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Jul 14 15:59:57 laptop NetworkManager: <info> (eth1): device state change: 4 -> 5
Jul 14 15:59:57 laptop NetworkManager: <info> Activation (eth1/wireless): connection 'SeattleHQ' has security, and secrets exist. No new secrets needed.
Jul 14 15:59:57 laptop NetworkManager: <info> Config: added 'ssid' value 'SeattleHQ'
Jul 14 15:59:57 laptop NetworkManager: <info> Config: added 'scan_ssid' value '1'
Jul 14 15:59:57 laptop NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Jul 14 15:59:57 laptop NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Jul 14 15:59:57 laptop NetworkManager: <info> Config: added 'psk' value '<omitted>'
Jul 14 15:59:57 laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Jul 14 15:59:57 laptop NetworkManager: <info> Config: set interface ap_scan to 1
Jul 14 15:59:57 laptop NetworkManager: <info> (eth1): supplicant connection state: disconnected -> scanning
Reply With Quote
  #2  
Old 15th July 2009, 02:08 AM
Hlingler's Avatar
Hlingler Offline
Administrator
  
Join Date: Sep 2006
Location: Connellsville, PA, USA
Posts: 11,289
Greetings mike.slass:

You may have noticed that the above post was automatically moderated (removed from public view) by our vBulletin software. I do not know why, but I have reviewed and approved the post.

Good Luck,
V
Reply With Quote
  #3  
Old 15th July 2009, 10:01 PM
David Becker Offline
Registered User
  
Join Date: Feb 2006
Posts: 780
Quote:
Originally Posted by mike.slass View Post
I can't get my Broadcoam BCM4322 to connect to a protected access point.
I've tried the drivers from rpmfusion, and tried to build the module with the source+binary package from Broadcom, all with no luck. The failure seems to happen during the WPA negotiation.

I haven't tried connecting to an unsecured WiFi access point.

When booting this same laptop to Kubuntu 9.04, it can connect to secured, so it is possible under linux.

Here's output from lspci, and the tail of the log while KNetworkManager is trying to connect the device.
...
It's unclear which driver kubuntu is using. Maybe you'll have better luck with this driver, although it may deprive you of 'n' capability.

David
Reply With Quote
  #4  
Old 15th July 2009, 11:26 PM
bbfuller Offline
Registered User
  
Join Date: Jun 2005
Location: UK
Posts: 4,345
Hello mike.slass

Welcome to the forum.

That's an awful lot of output there. I assume you are using the broadcom-wl driver for your card also known on the broadcom website as the Linux STA driver. It's also the one David Becker is pointing you to.

Of the two wireless drivers available for broadcom wireless cards that is the only one that is listed as working with your 4322 card.

I've had a couple of conversations with people who had problems getting their broadcoms to connect/authenticate recently and though I can't offer them as working solutions you may want to consider:

1. Some of the Linux wireless drivers don't like, or understand, the "n" parts of the wireless specification. Turning of the "n" parts in the access point can make a difference.

2. Not all drivers work with all channels. Here in Europe for example, we can use wireless channels 12 and 13, which are not available in other parts of the world. Not all drivers support 12 and 13.

Just one other experiment you might try. Will your setup connect to an access point with no security. I'm not suggesting that you leave it that way, just try it. It may help narrow the cause of the problem down.
Reply With Quote
Reply

Tags
bcm4322, broadcom, wpa, wpa_supplicant

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
wireless download too slow consistently - BCM4322 ngupta94 Hardware & Laptops 2 1st December 2009 06:50 AM
HP MiniNote 2133 FC11 and Broadcom Wifi jtmoon07 Installation and Live Media 8 25th August 2009 09:57 AM
PIL-1.1.6-9.fc11.i586 conflicts with file from package python-imaging-1.1.6-14.fc11.i toddbailey Using Fedora 0 14th August 2009 06:49 AM
BCM4322 Broadcom card can't use WEP dmyersturnbull Servers & Networking 6 12th July 2009 10:12 AM
Fedora 11 preview. WiFi driver for BCM4322 alexbour Alpha, Beta & Snapshots Discussions (Fedora 11 Only) 2 11th June 2009 10:45 AM


Current GMT-time: 01:17 (Saturday, 25-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.
Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

 FedoraForum is Powered by RedHat