Bug 695959 - F15 can't detect wireless networks with ath5k
Summary: F15 can't detect wireless networks with ath5k
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-12 23:20 UTC by Ranferi Meza
Modified: 2012-08-07 15:57 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 15:57:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
screenshot of NM not displaying networks (141.08 KB, image/png)
2011-04-12 23:40 UTC, Ranferi Meza
no flags Details
nm-applet tooltip showing connection to a wireless network (143.05 KB, image/png)
2011-04-13 00:06 UTC, Ranferi Meza
no flags Details
/var/log/messages (115.47 KB, text/plain)
2011-04-16 22:50 UTC, Ranferi Meza
no flags Details
dangets /var/log/messages (295.05 KB, text/plain)
2011-04-20 17:50 UTC, Danny George
no flags Details

Description Ranferi Meza 2011-04-12 23:20:07 UTC
Description of problem:

Fedora 15 loads the ath5k module correctly, but NetworkManager does not list any available wireless network, eventhough in F14 I can connect correctly to my home wireless.

Version-Release number of selected component (if applicable):

Version shipped with F15 beta x86_64 (April 8th 2011)
How reproducible:


Steps to Reproduce:
1.Use the live image to run F15 or install it
2.Click on networkmanager icon on taskbar
3.
  
Actual results:
No wireless network available to connect.

Expected results:
At least in my case, 1 wireless network should be listed (my home network)

Additional info:

lspci results:

[liveuser@localhost ~]$ lspci
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 10)
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:05.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:06.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:07.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:12.0 IDE interface: ATI Technologies Inc IXP SB400 Serial ATA Controller (rev 80)
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller (rev 80)
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 83)
00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller (rev 80)
00:14.2 Audio device: ATI Technologies Inc IXP SB4x0 High Definition Audio Controller (rev 01)
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80)
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200M]
08:01.0 CardBus bridge: ENE Technology Inc CB-712/4 Cardbus Controller (rev 10)
08:01.1 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller (rev 01)
08:01.2 SD Host controller: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller (rev 01)
08:01.3 FLASH memory: ENE Technology Inc FLASH memory: ENE Technology Inc: (rev 01)
08:01.4 FLASH memory: ENE Technology Inc SD/MMC Card Reader Controller (rev 01)
08:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
08:04.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)

dmesg stuff related to ath5k):

[   10.910090] ath5k 0000:08:04.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[   10.910174] ath5k 0000:08:04.0: registered as 'phy0'
[   11.642101] ath: EEPROM regdomain: 0x63
[   11.642104] ath: EEPROM indicates we should expect a direct regpair map
[   11.642108] ath: Country alpha2 being used: 00
[   11.642110] ath: Regpair used: 0x63
[   11.672550] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45)

ifconfig:

[liveuser@localhost ~]$ ifconfig
em1       Link encap:Ethernet  HWaddr 00:16:36:BF:B1:D3  
          inet addr:192.168.1.70  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::216:36ff:febf:b1d3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6454 errors:58 dropped:0 overruns:0 frame:0
          TX packets:5281 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:5547091 (5.2 MiB)  TX bytes:825626 (806.2 KiB)
          Interrupt:20 Base address:0x2c00 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:204 errors:0 dropped:0 overruns:0 frame:0
          TX packets:204 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:18048 (17.6 KiB)  TX bytes:18048 (17.6 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:19:7D:2A:BF:0C  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Comment 1 Ranferi Meza 2011-04-12 23:37:58 UTC
version for NM:

evolution-NetworkManager-2.91.92-2.fc15.x86_64
NetworkManager-openvpn-0.8.995-1.fc15.x86_64
NetworkManager-gnome-0.8.998-2.git20110406.fc15.x86_64
NetworkManager-openconnect-0.8.1-7.git20110326.fc15.x86_64
NetworkManager-vpnc-0.8.996-2.fc15.x86_64
NetworkManager-glib-0.8.998-2.git20110406.fc15.x86_64
NetworkManager-pptp-0.8.995-1.fc15.x86_64
NetworkManager-0.8.998-2.git20110406.fc15.x86_64

Comment 2 Ranferi Meza 2011-04-12 23:40:22 UTC
Created attachment 491616 [details]
screenshot of NM not displaying networks

This is a screenshot showing how in F15 I can not see any wireless networks eventhough wireless card is on.

Comment 3 Ranferi Meza 2011-04-12 23:45:10 UTC
If I try to manually connect to my wireless network entering the SSID in Network Settings -> Wireless, right after I type in the WPA2 key, the nm-applet dies.
NetworkManager keeps running.

Comment 4 Ranferi Meza 2011-04-13 00:02:22 UTC
The same laptop running F14:

[remiks@jackal ~]$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:36:BF:B1:D3  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:20 Base address:0x4c00 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:214 errors:0 dropped:0 overruns:0 frame:0
          TX packets:214 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:17266 (16.8 KiB)  TX bytes:17266 (16.8 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:19:7D:2A:BF:0C  
          inet addr:192.168.1.64  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:804 errors:0 dropped:0 overruns:0 frame:0
          TX packets:878 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:304772 (297.6 KiB)  TX bytes:166215 (162.3 KiB)

lspci:

00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 10)
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:05.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:06.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:07.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:12.0 IDE interface: ATI Technologies Inc IXP SB400 Serial ATA Controller (rev 80)
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller (rev 80)
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 83)
00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller (rev 80)
00:14.2 Audio device: ATI Technologies Inc IXP SB4x0 High Definition Audio Controller (rev 01)
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80)
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200M]
08:01.0 CardBus bridge: ENE Technology Inc CB-712/4 Cardbus Controller (rev 10)
08:01.1 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller (rev 01)
08:01.2 SD Host controller: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller (rev 01)
08:01.3 FLASH memory: ENE Technology Inc FLASH memory: ENE Technology Inc: (rev 01)
08:01.4 FLASH memory: ENE Technology Inc SD/MMC Card Reader Controller (rev 01)
08:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
08:04.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)

dmesg:

[    8.564430] ath5k 0000:08:04.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[    8.564503] ath5k 0000:08:04.0: registered as 'phy0'
[    9.280333] ath: EEPROM regdomain: 0x63
[    9.280338] ath: EEPROM indicates we should expect a direct regpair map
[    9.280343] ath: Country alpha2 being used: 00
[    9.280345] ath: Regpair used: 0x63
[    9.384724] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45)

Comment 5 Ranferi Meza 2011-04-13 00:06:17 UTC
Created attachment 491617 [details]
nm-applet tooltip showing connection to a wireless network

The screenshot shows that, in F14 with the same hardware, I can connect to my home wireless network.

Comment 6 Jirka Klimes 2011-04-13 08:17:48 UTC
Could you run in terminal
$ nm-tool
which would show us if NM can see some WiFI networks?

Comment 7 Ranferi Meza 2011-04-14 00:44:11 UTC
This is from F14 working and connected:

[remiks@jackal ~]$ nm-tool

NetworkManager Tool

State: connected

- Device: eth0 -----------------------------------------------------------------
  Type:              Wired
  Driver:            8139too
  State:             unavailable
  Default:           no
  HW Address:        00:16:36:BF:B1:D3

  Capabilities:
    Carrier Detect:  yes
    Speed:           10 Mb/s

  Wired Properties
    Carrier:         off


- Device: wlan0  [Auto PENNY2] -------------------------------------------------
  Type:              802.11 WiFi
  Driver:            ath5k
  State:             connected
  Default:           yes
  HW Address:        00:19:7D:2A:BF:0C

  Capabilities:
    Speed:           54 Mb/s

  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points (* = current AP)
    INFINITUM0145:   Infra, 00:1D:5A:23:BD:99, Freq 2412 MHz, Rate 54 Mb/s, Strength 34 WEP
    INFINITUM5127:   Infra, 5C:4C:A9:E9:8B:A8, Freq 2427 MHz, Rate 54 Mb/s, Strength 31 WEP
    *PENNY2:         Infra, 00:1A:C4:60:CB:E9, Freq 2412 MHz, Rate 54 Mb/s, Strength 100 WPA

  IPv4 Settings:
    Address:         192.168.1.64
    Prefix:          24 (255.255.255.0)
    Gateway:         192.168.1.254

    DNS:             127.0.0.1
    DNS:             8.8.8.8
    DNS:             8.8.4.4

Comment 8 Ranferi Meza 2011-04-14 00:50:21 UTC
And this is from F15 live:

[liveuser@localhost ~]$ nm-tool 

NetworkManager Tool

State: connected (global)

- Device: em1  [Wired connection 1] --------------------------------------------
  Type:              Wired
  Driver:            8139too
  State:             connected
  Default:           yes
  HW Address:        00:16:36:BF:B1:D3

  Capabilities:
    Carrier Detect:  yes
    Speed:           100 Mb/s

  Wired Properties
    Carrier:         on

  IPv4 Settings:
    Address:         192.168.1.70
    Prefix:          24 (255.255.255.0)
    Gateway:         192.168.1.254

    DNS:             192.168.1.254


- Device: wlan0 ----------------------------------------------------------------
  Type:              802.11 WiFi
  Driver:            ath5k
  State:             disconnected
  Default:           no
  HW Address:        00:19:7D:2A:BF:0C

  Capabilities:

  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points 

I am seated in the very same spot, no walls, AP is at like 1.5 mts from the laptop...

Comment 9 Jirka Klimes 2011-04-15 08:01:43 UTC
It doesn't show any networks because it's disconnected.

Please try to scan with:
sudo ifconfig wlan0 up
iwlist wlan0 scan

And grab /var/log/message so we can look at NetworkManager logs.

In comment #3 you say that applet dies. Do you see any crash in abrt or something in .xsession-errors or whatever?

Comment 10 Ranferi Meza 2011-04-16 22:45:48 UTC
Well, the card is up, but here it goes anyway,,,

[liveuser@localhost ~]$ su -
[root@localhost ~]# ifconfig wlan0 up
[root@localhost ~]# iwlist wlan0 scan
wlan0     No scan results

Comment 11 Ranferi Meza 2011-04-16 22:50:09 UTC
Created attachment 492652 [details]
/var/log/messages

/var/log/messages

Comment 12 Ranferi Meza 2011-04-16 22:53:09 UTC
funny... now it sees the network... I will try to connect and get back to you.

Curious: is it necessary to do all that ifconfig/iwlist stuff to get it working?

Comment 13 Ranferi Meza 2011-04-16 22:56:23 UTC
It can not connect: asks for WPA pswd, and then, it asks it again, and again, and again...

here is the dmesg:

[  851.280390] wlan0: direct probe to 00:1a:c4:60:cb:e9 (try 1/3)
[  851.480069] wlan0: direct probe to 00:1a:c4:60:cb:e9 (try 2/3)
[  851.680071] wlan0: direct probe to 00:1a:c4:60:cb:e9 (try 3/3)
[  851.682141] wlan0: direct probe responded
[  851.682170] wlan0: authenticate with 00:1a:c4:60:cb:e9 (try 1)
[  851.882048] wlan0: authenticate with 00:1a:c4:60:cb:e9 (try 2)
[  852.082069] wlan0: authenticate with 00:1a:c4:60:cb:e9 (try 3)
[  852.083997] wlan0: authenticated
[  852.085073] wlan0: associate with 00:1a:c4:60:cb:e9 (try 1)
[  852.091535] wlan0: RX AssocResp from 00:1a:c4:60:cb:e9 (capab=0x431 status=0 aid=1)
[  852.091546] wlan0: associated
[  852.095858] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  852.096229] cfg80211: Calling CRDA for country: US
[  852.261341] cfg80211: Regulatory domain changed to country: US
[  852.261345] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[  852.261350] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[  852.261354] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[  852.261357] cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  852.261360] cfg80211:     (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  852.261364] cfg80211:     (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  852.261367] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[  855.174561] wlan0: deauthenticated from 00:1a:c4:60:cb:e9 (Reason: 2)
[  855.177283] cfg80211: Calling CRDA to update world regulatory domain
[  855.225766] cfg80211: World regulatory domain updated:
[  855.225776] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[  855.225787] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  855.225796] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[  855.225804] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[  855.225813] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  855.225821] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  856.143782] wlan0: authenticate with 00:1a:c4:60:cb:e9 (try 1)
[  856.343069] wlan0: authenticate with 00:1a:c4:60:cb:e9 (try 2)
[  856.346864] wlan0: authenticated
[  856.347441] wlan0: associate with 00:1a:c4:60:cb:e9 (try 1)
[  856.547048] wlan0: associate with 00:1a:c4:60:cb:e9 (try 2)
[  856.747092] wlan0: associate with 00:1a:c4:60:cb:e9 (try 3)
[  856.947064] wlan0: association with 00:1a:c4:60:cb:e9 timed out
[  862.274034] wlan0: no IPv6 routers present
[  862.784197] wlan0: direct probe to 00:1a:c4:60:cb:e9 (try 1/3)
[  862.984093] wlan0: direct probe to 00:1a:c4:60:cb:e9 (try 2/3)
[  863.184069] wlan0: direct probe to 00:1a:c4:60:cb:e9 (try 3/3)
[  863.384065] wlan0: direct probe to 00:1a:c4:60:cb:e9 timed out
[  869.192189] wlan0: direct probe to 00:1a:c4:60:cb:e9 (try 1/3)
[  869.392062] wlan0: direct probe to 00:1a:c4:60:cb:e9 (try 2/3)
[  869.592068] wlan0: direct probe to 00:1a:c4:60:cb:e9 (try 3/3)
[  869.792065] wlan0: direct probe to 00:1a:c4:60:cb:e9 timed out
[  885.754525] wlan0: direct probe to 00:1a:c4:60:cb:e9 (try 1/3)
[  885.954070] wlan0: direct probe to 00:1a:c4:60:cb:e9 (try 2/3)
[  886.154079] wlan0: direct probe to 00:1a:c4:60:cb:e9 (try 3/3)
[  886.354072] wlan0: direct probe to 00:1a:c4:60:cb:e9 timed out

Comment 14 Ranferi Meza 2011-04-16 22:58:47 UTC
regarding the nm-applet crash... nope, no logs... tried that last time and it did not yield any result...

Comment 15 Ranferi Meza 2011-04-16 23:39:17 UTC
regarding the nm-applet crash... nope, no logs... tried that last time and it did not yield any result...

Comment 16 Timo Sorvoja 2011-04-20 12:36:16 UTC
I'm having the same issue with my Acer 3100 laptop (with AR2413 chip).

Comment 17 Danny George 2011-04-20 17:49:28 UTC
Same issue here with Dell M1330, Intel 4965 AG wireless card. F15 Live Beta

'nm-tool' shows nothing under Wireless Access Points
'iwlist wlan0 scanning' shows many networks detected

Also, if I click on the NetworkManager icon and just leave it up, the Wireless section will intermittently switch between the On/Off slider and "unavailable".

Also attaching my /var/log/messages

Comment 18 Danny George 2011-04-20 17:50:28 UTC
Created attachment 493563 [details]
dangets /var/log/messages

Comment 19 Jirka Klimes 2011-04-21 07:46:11 UTC
(In reply to comment #17)
> Same issue here with Dell M1330, Intel 4965 AG wireless card. F15 Live Beta
> 
> 'nm-tool' shows nothing under Wireless Access Points
> 'iwlist wlan0 scanning' shows many networks detected
> 
> Also, if I click on the NetworkManager icon and just leave it up, the Wireless
> section will intermittently switch between the On/Off slider and "unavailable".
> 
> Also attaching my /var/log/messages

Danny, in your case there is a problem with wpa_supplicant. It crashes continuously. abrt has caught the crash. Would you mind running 'abrt-gui' as root and file the bug?

What version of wpa_supplicant do you have?

Apr 20 17:47:37 localhost NetworkManager[981]: <info> (wlan0): supplicant interface state: starting -> ready
Apr 20 17:47:37 localhost NetworkManager[981]: <info> (wlan0): device state change: 20 -> 30 (reason 42)
Apr 20 17:47:37 localhost NetworkManager[981]: <info> (wlan0): supplicant interface state: ready -> inactive
Apr 20 17:47:39 localhost kernel: [  816.111276] scsi 6:0:0:0: Direct-Access     SMI      USB DISK         3000 PQ: 0 ANSI: 0 CCS
Apr 20 17:47:39 localhost kernel: [  816.116793] sd 6:0:0:0: Attached scsi generic sg3 type 0
Apr 20 15:47:40 localhost abrt[2374]: saved core dump of pid 2370 (/usr/sbin/wpa_supplicant) to /var/spool/abrt/ccpp-1303336060-2370.new/coredump (995328 bytes)
Apr 20 17:47:40 localhost abrtd: Directory 'ccpp-1303336060-2370' creation detected
Apr 20 17:47:40 localhost NetworkManager[981]: <info> wpa_supplicant stopped
Apr 20 17:47:40 localhost NetworkManager[981]: <info> (wlan0): supplicant interface state: inactive -> down
Apr 20 17:47:40 localhost NetworkManager[981]: <info> (wlan0): device state change: 30 -> 20 (reason 10)
Apr 20 17:47:40 localhost NetworkManager[981]: <info> (wlan0): deactivating device (reason: 10).
Apr 20 17:47:40 localhost NetworkManager[981]: <info> wpa_supplicant die count 3; ignoring for 10 seconds

Comment 20 Danny George 2011-04-21 14:34:01 UTC
Sorry for this bug-jacking... I added my comments to a different bug which looks similar.  https://bugzilla.redhat.com/show_bug.cgi?id=697946

wpa_supplicant version v0.7.3 (using LiveCD)

I was also asked to run abrt-gui to report the bug, but unless I'm missing
something, no application crashes are being captured - even though I can still
watch the wireless go back and forth between slider and unavailable.

Comment 21 arctos 2011-04-26 05:46:56 UTC
I am having same problem.  Acer Travelmate 2423WXCi with Atheros wireless card.  Does not show any networks in Fedora 15.  When attempting to manually add the wireless network, the applet crashed.  The wireless worked fine in F14 and works fine in Ubuntu 11.04.

Comment 22 arctos 2011-04-26 05:48:25 UTC
(In reply to comment #21)
> I am having same problem.  Acer Travelmate 2423WXCi with Atheros wireless card.
>  Does not show any networks in Fedora 15.  When attempting to manually add the
> wireless network, the applet crashed.  The wireless worked fine in F14 and
> works fine in Ubuntu 11.04.

Forgot to include, my wireless card is the same as everyone else with this issue in this report so far... AR2413

06:05.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)

Comment 23 Jirka Klimes 2011-05-02 11:29:32 UTC
Does anybody see 
"ath5k phy0: gain calibration timeout .." in dmesg?
That would indicate the issue described in bug 672778.

(In reply to comment #21)
> I am having same problem.  Acer Travelmate 2423WXCi with Atheros wireless card.
>  Does not show any networks in Fedora 15.  When attempting to manually add the
> wireless network, the applet crashed.  The wireless worked fine in F14 and
> works fine in Ubuntu 11.04.

If you say that applet crashed, can you see/report that from abrt-gui. Any interesting logs in /var/log/messages and ~/.xsession-errors ?

Comment 24 Timo Sorvoja 2011-05-26 04:44:16 UTC
Hi,
"ath5k phy0: gain calibration timeout .." is not in /var/log/messages.

I can not confirm that the applet crashes. For me it seems that this is a kernel or NetworkManager issue since in Ubuntu 11.04 BETA this did not work either. I'll download the latest Ubuntu 11.04 iso-image and see if this works not there.

In my messages-logs it says that device is disconnected (grep NetworkManager):
May 26 07:29:06 F15 NetworkManager[867]: <info> NetworkManager (version 0.8.999-2.git20110509.fc15) is starting...
May 26 07:29:06 F15 NetworkManager[867]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
May 26 07:29:07 F15 NetworkManager[867]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc
May 26 07:29:07 F15 NetworkManager[867]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
May 26 07:29:07 F15 NetworkManager[867]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
May 26 07:29:07 F15 NetworkManager[867]: <info> VPN: loaded org.freedesktop.NetworkManager.openconnect
May 26 07:29:08 F15 NetworkManager[867]: <error> [1306384148.534356] [nm-session-monitor.c:349] nm_session_monitor_init(): Error loading /var/run/ConsoleKit/database: Error statting file /var/run/ConsoleKit/database: No such file or directory
May 26 07:29:08 F15 NetworkManager[867]:    ifcfg-rh: Acquired D-Bus service com.redhat.ifcfgrh1
May 26 07:29:08 F15 NetworkManager[867]: <info> Loaded plugin ifcfg-rh: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
May 26 07:29:08 F15 NetworkManager[867]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
May 26 07:29:08 F15 NetworkManager[867]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... 
May 26 07:29:08 F15 NetworkManager[867]:    ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-XXX-WLAN ... 
May 26 07:29:08 F15 NetworkManager[867]:    ifcfg-rh:     read connection 'Auto XXX-WLAN'
May 26 07:29:08 F15 NetworkManager[867]: <info> trying to start the modem manager...
May 26 07:29:08 F15 NetworkManager[867]: <info> monitoring kernel firmware directory '/lib/firmware'.
May 26 07:29:08 F15 NetworkManager[867]: <info> found WiFi radio killswitch rfkill0 (at /sys/devices/pci0000:00/0000:00:14.4/0000:06:02.0/ieee80211/phy0/rfkill0) (driver (unknown))
May 26 07:29:08 F15 NetworkManager[867]: <info> WiFi enabled by radio killswitch; enabled by state file
May 26 07:29:08 F15 NetworkManager[867]: <info> WWAN enabled by radio killswitch; enabled by state file
May 26 07:29:08 F15 NetworkManager[867]: <info> WiMAX enabled by radio killswitch; enabled by state file
May 26 07:29:08 F15 NetworkManager[867]: <info> Networking is enabled by state file
May 26 07:29:08 F15 NetworkManager[867]: <info> (eth0): carrier is OFF
May 26 07:29:08 F15 NetworkManager[867]: <info> (eth0): new Ethernet device (driver: '8139too' ifindex: 2)
May 26 07:29:08 F15 NetworkManager[867]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
May 26 07:29:08 F15 NetworkManager[867]: <info> (eth0): now managed
May 26 07:29:08 F15 NetworkManager[867]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 26 07:29:08 F15 NetworkManager[867]: <info> (eth0): bringing up device.
May 26 07:29:08 F15 NetworkManager[867]: <info> (eth0): preparing device.
May 26 07:29:08 F15 NetworkManager[867]: <info> (eth0): deactivating device (reason: 2).
May 26 07:29:08 F15 NetworkManager[867]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:14.4/0000:06:01.0/net/eth0
May 26 07:29:08 F15 NetworkManager[867]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
May 26 07:29:08 F15 NetworkManager[867]: <info> (wlan0): new 802.11 WiFi device (driver: 'ath5k' ifindex: 3)
May 26 07:29:08 F15 NetworkManager[867]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
May 26 07:29:08 F15 NetworkManager[867]: <info> (wlan0): now managed
May 26 07:29:08 F15 NetworkManager[867]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 26 07:29:08 F15 NetworkManager[867]: <info> (wlan0): bringing up device.
May 26 07:29:08 F15 NetworkManager[867]: <info> (wlan0): preparing device.
May 26 07:29:08 F15 NetworkManager[867]: <info> (wlan0): deactivating device (reason: 2).
May 26 07:29:09 F15 NetworkManager[867]: <info> modem-manager is now available
May 26 07:29:09 F15 NetworkManager[867]: <warn> bluez error getting default adapter: No such adapter
May 26 07:29:09 F15 NetworkManager[867]: <warn> bluez error getting default adapter: No such adapter
May 26 07:29:09 F15 NetworkManager[867]: <info> wpa_supplicant started
May 26 07:29:09 F15 NetworkManager[867]: <info> (wlan0): supplicant interface state: starting -> ready
May 26 07:29:09 F15 NetworkManager[867]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 26 07:29:09 F15 NetworkManager[867]: <info> (wlan0): supplicant interface state: ready -> inactive

Comment 25 Timo Sorvoja 2011-05-26 17:55:41 UTC
Additional info: Ubuntu 11.04 and Mint11 are the same. Wireless not working with this wireless chipset.

Comment 26 john5342 2011-06-03 12:43:59 UTC
This bug looks a lot like: https://bugzilla.kernel.org/show_bug.cgi?id=34992

Comment 27 Maurice Pijpers 2011-06-05 14:35:46 UTC
Same thing happens on a lenovo S12 with Broadcom BCM4312 card:
07:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

Jun  5 16:33:52 donald NetworkManager[882]: <info> (wlan0): bringing up device.
Jun  5 16:33:52 donald kernel: [ 1296.728133] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Jun  5 16:33:54 donald kernel: [ 1298.130820] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun  5 16:33:54 donald NetworkManager[882]: <info> WiFi hardware radio set enabled
Jun  5 16:33:54 donald NetworkManager[882]: <info> WiFi now enabled by radio killswitch
Jun  5 16:33:54 donald NetworkManager[882]: <info> (wlan0): supplicant interface state: starting -> ready
Jun  5 16:33:54 donald NetworkManager[882]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jun  5 16:33:54 donald NetworkManager[882]: <info> (wlan0): supplicant interface state: ready -> inactive
Jun  5 16:33:55 donald NetworkManager[882]: <info> WiFi now disabled by radio killswitch
Jun  5 16:33:55 donald NetworkManager[882]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0]
Jun  5 16:33:55 donald NetworkManager[882]: <info> (wlan0): deactivating device (reason: 0).

Comment 28 Jirka Klimes 2011-06-06 07:19:41 UTC
Maurice, in your case WiFi is disabled. Please check with
$ rfkill list

And try enabling with
$ rfkill unblock all
And be sure, you don't have WiFi blocked by a hardware switch.

The problem in this bug is probably driver. All who has a problem, please experiment with different kernel versions.

Comment 29 Denis110 2011-06-10 01:17:46 UTC
(In reply to comment #28)
> Maurice, in your case WiFi is disabled. Please check with
> $ rfkill list
> 
> And try enabling with
> $ rfkill unblock all
> And be sure, you don't have WiFi blocked by a hardware switch.

Jirka, I just got to thank you for this suggestion, it solved my nagging problem.

Really appreciate your help,

Did I say thank you?

Thanks

Denis Milette

Comment 30 Fedora End Of Life 2012-08-07 15:57:50 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.