Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Fedora 17/18 > Using Fedora
FedoraForum Search

Forgot Password? Join Us!

Using Fedora General support for current versions. Ask questions about Fedora and it's software that do not belong in any other forum.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 23rd December 2011, 07:50 PM
muhammad ammar Offline
Registered User
 
Join Date: Feb 2010
Posts: 42
linuxfirefox
Unhappy Fedora 16 Wireless Connection Problem

I have Dell Inpiron N5010 with Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller.

My OS is Fedora 16 64-bit. I have installed the following drivers for my wireless controller, everything is working great until yesterday. Now whenever i try to connect to wirless connection, it failed.

http://download1.rpmfusion.org/nonfr...oadcom-wl.html

I haven't installed anything that can cause this problem.

Following are log messages from /var/log/messages when i try to connect to connection. I have double checked connection settings and everything is correct.

Quote:
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Activation (eth1) starting connection 'Auto Communication Gallery'
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> (eth1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Activation (eth1) starting connection 'Auto Communication Gallery'
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> (eth1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> (eth1): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> (eth1): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Activation (eth1/wireless): connection 'Auto Communication Gallery' has security, and secrets exist. No new secrets needed.
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Activation (eth1/wireless): connection 'Auto Communication Gallery' has security, and secrets exist. No new secrets needed.
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Config: added 'ssid' value 'Communication Gallery'
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Config: added 'ssid' value 'Communication Gallery'
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Config: added 'scan_ssid' value '1'
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Config: added 'key_mgmt' value 'NONE'
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Config: added 'wep_key0' value '<omitted>'
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Config: added 'wep_tx_keyidx' value '0'
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Config: added 'scan_ssid' value '1'
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Config: added 'key_mgmt' value 'NONE'
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Config: added 'wep_key0' value '<omitted>'
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Config: added 'wep_tx_keyidx' value '0'
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: <info> Config: set interface ap_scan to 1
Dec 24 00:46:15 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> Config: set interface ap_scan to 1
Dec 24 00:46:16 ma-laptop NetworkManager[1039]: <info> (eth1): supplicant interface state: inactive -> scanning
Dec 24 00:46:16 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> (eth1): supplicant interface state: inactive -> scanning
Dec 24 00:46:41 ma-laptop NetworkManager[1039]: <warn> Activation (eth1/wireless): association took too long.
Dec 24 00:46:41 ma-laptop NetworkManager[1039]: <info> (eth1): device state change: config -> need-auth (reason 'none') [50 60 0]
Dec 24 00:46:41 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <warn> Activation (eth1/wireless): association took too long.
Dec 24 00:46:41 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> (eth1): device state change: config -> need-auth (reason 'none') [50 60 0]
Dec 24 00:46:41 ma-laptop NetworkManager[1039]: <warn> Activation (eth1/wireless): asking for new secrets
Dec 24 00:46:41 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <warn> Activation (eth1/wireless): asking for new secrets
Dec 24 00:46:41 ma-laptop NetworkManager[1039]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Dec 24 00:46:41 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Dec 24 00:46:41 ma-laptop NetworkManager[1039]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Dec 24 00:46:41 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Dec 24 00:46:43 ma-laptop NetworkManager[1039]: <info> (eth1): supplicant interface state: scanning -> inactive
Dec 24 00:46:43 ma-laptop NetworkManager[1039]: NetworkManager[1039]: <info> (eth1): supplicant interface state: scanning -> inactive
Dec 24 00:46:52 ma-laptop NetworkManager[1039]: <warn> No agents were available for this request.

Can anyone help me?

Thanks
Reply With Quote
  #2  
Old 23rd December 2011, 08:41 PM
stoat Offline
Registered User
 
Join Date: Jun 2006
Posts: 7,551
linuxfirefox
Re: Fedora 16 Wireless Connection Problem

According to linuxwireless.org, the BCM4313 chipset is supported by the new brcmsmac driver. That driver now is included with Fedora kernels as a kernel module. But I think it became available after the release of Fedora 16. So you may only need to update your system via a wired connection and reboot. I would try that now.
Reply With Quote
  #3  
Old 24th December 2011, 11:40 AM
muhammad ammar Offline
Registered User
 
Join Date: Feb 2010
Posts: 42
linuxfirefox
Re: Fedora 16 Wireless Connection Problem

Quote:
Originally Posted by stoat View Post
According to linuxwireless.org, the BCM4313 chipset is supported by the new brcmsmac driver. That driver now is included with Fedora kernels as a kernel module. But I think it became available after the release of Fedora 16. So you may only need to update your system via a wired connection and reboot. I would try that now.
Great Great Thanks stoat.

PROBLEM SOLVED.

I just updated the system and wireless is working great again.

But i really didn't understand what happened. How the wireless stopped working? In the last 5 days i haven't installed anything, nothing.
Reply With Quote
  #4  
Old 24th December 2011, 01:37 PM
pacific0 Offline
Registered User
 
Join Date: Dec 2011
Location: Canada
Posts: 16
macossafari
Re: Fedora 16 Wireless Connection Problem

This happened already on my acer aspire 4520 when the battery drained and bios configuration was lost, some how when this happens the wifi cards get dissabled.

Regards
Reply With Quote
  #5  
Old 24th December 2011, 02:59 PM
JEO Offline
Registered User
 
Join Date: Jan 2006
Posts: 2,769
linuxfirefox
Re: Fedora 16 Wireless Connection Problem

The wireless was failing to associate. Sometimes the wireless access point can get in a bad "state" and cause this problem. Waiting for a period of time and the problem goes away.
Reply With Quote
Reply

Tags
broadcom, connection, fedora, fedora16 x86_64, problem, wireless

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

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 connection problem d0ubty Servers & Networking 5 7th October 2009 05:23 AM
Ping (and connection) problem between 2 wireless in Fedora 10 itisspeedy Servers & Networking 0 8th January 2009 01:52 PM
Fedora 8 Wireless Network Connection Problem sudeep1 Servers & Networking 10 13th February 2008 03:29 AM
Wireless Connection Problem on Fedora marlonmin Servers & Networking 1 18th November 2007 11:35 PM
Fedora 7, wireless connection problem goodwin57 Servers & Networking 0 24th October 2007 04:11 PM


Current GMT-time: 16:51 (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