Description of problem: Wireless connection does not work on a Dell Precision M6400 with an Intel Wireless WiFi Link 5100. It worked very well previously, though not with the latest two kernels. It worked very well too under F11. This is a clean install of F12. I don't have control over the access point (I'm in a school), but the setting for Wireless security they ask you to set it to "none". Version-Release number of selected component (if applicable): kernel-2.6.31.12-174.2.3.fc12.x86_64 other: NetworkManager-0.7.997-2.git20091214.fc12.x86_64 wpa_supplicant-0.6.8-8.fc12.x86_64 iwl5000-firmware-8.24.2.12-2.noarch How reproducible: Steps to Reproduce: 1. boot PC 2. try to connect to internet 3. Actual results: see Additional info below Expected results: connect to internet Additional info: message on the wpa_supplicant.log --- Failed to initiate AP scan. Trying to associate with 00:14:f2:70:d8:b0 (SSID='bgsu' freq=2412 MHz) CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Authentication with 00:00:00:00:00:00 timed out. --- messages from the messages system log --- NetworkManager: <info> wlan0: link timed out. NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected NetworkManager: <info> Activation (wlan0/wireless): association took too long, failing activation. NetworkManager: <info> (wlan0): device state change: 5 -> 9 (reason 11) NetworkManager: <info> Activation (wlan0) failed for access point (bgsu) NetworkManager: <info> Marking connection 'Wireless connection 1' invalid. NetworkManager: <info> Activation (wlan0) failed. NetworkManager: <info> (wlan0): device state change: 9 -> 3 (reason 0) NetworkManager: <info> (wlan0): deactivating device (reason: 0). --- output from lspci -vnn --- 0c:00.0 Network controller [0280]: Intel Corporation Wireless WiFi Link 5100 [8086:4232] Subsystem: Intel Corporation Wireless WiFi Link 5100 [8086:1321] Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at f1ffe000 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [e0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 00-22-fb-ff-ff-9f-1e-08 Kernel driver in use: iwlagn Kernel modules: iwlagn --- output from nm-tool NetworkManager Tool State: connected - Device: wlan0 ---------------------------------------------------------------- Type: 802.11 WiFi Driver: iwlagn State: disconnected Default: no HW Address: 00:22:FB:9F:1E:08 Capabilities: Wireless Properties WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes Wireless Access Points bgsu: Infra, 00:14:F2:70:D3:A0, Freq 2437 MHz, Rate 0 Mb/s, Strength 52 ---
Hi (In reply to comment #0) > Wireless connection does not work on a Dell Precision M6400 with an Intel > Wireless WiFi Link 5100. It worked very well previously, though not with the > latest two kernels. It worked very well too under F11. This is a clean install > of F12. Looks like regression between 2.6.30 and 2.6.31 kernel, hmm. Seams the same thing as we have in bug 539878, with difference of wifi device type. Enrique, Could you post the output of running iwevent during the association attempts? Also, could you include the output of dmesg from the same period? Addionally could you test 2.6.32 based kernel (using command 'yum --enablerepo="rawhide" update kernel') ?
Hi, Below is the info from iwevent and the messages log. Thanks. iwevent: Waiting for Wireless Events from interfaces... 16:15:32.154932 wlan0 Scan request completed 16:15:32.155112 wlan0 Set Mode:Managed 16:15:32.155126 wlan0 Set Frequency:2.412 GHz (Channel 1) 16:15:32.758277 wlan0 New Access Point/Cell address:Not-Associated 16:15:54.887941 wlan0 Scan request completed messages log: NetworkManager: <info> Activation (wlan0) starting connection 'Wireless connection 1' NetworkManager: <info> (wlan0): device state change: 3 -> 4 (reason 0) NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0) NetworkManager: <info> Activation (wlan0/wireless): connection 'Wireless connection 1' requires no security. No secrets needed. NetworkManager: <info> Config: added 'ssid' value 'bgsu' NetworkManager: <info> Config: added 'scan_ssid' value '1' NetworkManager: <info> Config: added 'key_mgmt' value 'NONE' NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. NetworkManager: <info> Config: set interface ap_scan to 1 NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected NetworkManager: <info> wlan0: link timed out. NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning NetworkManager: <info> Activation (wlan0/wireless): association took too long, failing activation. NetworkManager: <info> (wlan0): device state change: 5 -> 9 (reason 11) NetworkManager: <info> Activation (wlan0) failed for access point (bgsu) NetworkManager: <info> Marking connection 'Wirelessconnection 1' invalid. NetworkManager: <info> Activation (wlan0) failed. NetworkManager: <info> (wlan0): device state change: 9 -> 3 (reason 0) NetworkManager: <info> (wlan0): deactivating device (reason: 0).
Hi Enrique Could you please provide 'dmesg' output from association attempts period? Please also test swcrypto=1 option (see https://bugzilla.redhat.com/show_bug.cgi?id=539878#c6). Optionally could you downgrade the kernel to version that we have in f11 and provide us logs (messages,iwevent,dmesg) from successfully association? To downgrade kernel you can use following commands: > [root@yellow /]# cd / >[root@yellow /]# wget http://ultra.linux.cz/MIRRORS/fedora.redhat.com/linux/updates/11/x86_64/kernel-2.6.30.10-105.2.4.fc11.x86_64.rpm >[root@yellow /]# rpm2cpio kernel-2.6.30.10-105.2.4.fc11.x86_64.rpm | cpio --extract --make-directories >[root@yellow /]# /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod --install 2.6.30.10-105.2.4.fc11.x86_64 Please note the graphics may not work due to Xwindow/kernel incompatibility (nomodeset kernel parameter may help), if it works we have workaround for your bug ;-). If graphics not work, install cnetworkmanager to initialize wifi from text console (hint1: use Alt+Fx or Alt+Ctrl+Fx keys to switch to and between virtual text consoles).
Created attachment 387135 [details] output of dmesg output of dmesg while trying to associate wireless.
Hi, There is no output to dmesg from the association attempt. See attachment. I'll try the swcrypto=1 option later on today. Thanks! Enrique
Hi, When I try the swcrypto=1 option following the bug report indicated I get this back: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. WARNING: All config files need .conf: /etc/modprobe.d/iwlagn, it will be ignored in a future release. WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. WARNING: All config files need .conf: /etc/modprobe.d/iwlagn, it will be ignored in a future release. WARNING: Error inserting mac80211 (/lib/modules/2.6.31.12-174.2.3.fc12.x86_64/kernel/net/mac80211/mac80211.ko): Operation not permitted WARNING: Error inserting iwlcore (/lib/modules/2.6.31.12-174.2.3.fc12.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlcore.ko): Operation not permitted FATAL: Error inserting iwlagn (/lib/modules/2.6.31.12-174.2.3.fc12.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko): Operation not permitted
Hello (In reply to comment #6) > WARNING: Deprecated config file /etc/modprobe.conf, all config files belong > into /etc/modprobe.d/. > WARNING: All config files need .conf: /etc/modprobe.d/iwlagn, it will be > ignored in a future release. These warnings can be ignored. > FATAL: Error inserting iwlagn >(/lib/modules/2.6.31.12-174.2.3.fc12.x86_64/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko): > Operation not permitted I didn't tell that you have to perform these commands as root. If you have modified /etc/modprobe.d/iwlagn file then when you reboot swcrypto=1 option will be used. (In reply to comment #5) > There is no output to dmesg from the association attempt. See attachment. Association information in dmesg are the most interesting. It's looks like below: wlan0: direct probe to AP 00:23:69:35:d1:3e (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:23:69:35:d1:3e (try 1) wlan0: authenticated wlan0: associate with AP 00:23:69:35:d1:3e (try 1) wlan0: RX AssocResp from 00:23:69:35:d1:3e (capab=0x411 status=0 aid=1) wlan0: associated
Hi, Here are the messages from dmesg. The system log viewer does not update dmesg, so that is why I was not seeing the output (that may be another different bug altogether!). -Enrique iwlagn 0000:0c:00.0: firmware: requesting iwlwifi-5000-2.ucode iwlagn 0000:0c:00.0: loaded firmware version 8.24.2.12 Registered led device: iwl-phy0::radio Registered led device: iwl-phy0::assoc Registered led device: iwl-phy0::RX Registered led device: iwl-phy0::TX ADDRCONF(NETDEV_UP): wlan0: link is not ready . . . wlan0: authenticate with AP 00:14:f2:70:d8:60 wlan0: authenticated wlan0: associate with AP 00:14:f2:70:d8:60 wlan0: RX AssocResp from 00:14:f2:70:d8:60 (capab=0x21 status=18 aid=0) wlan0: AP denied association (code=18) wlan0: associate with AP 00:14:f2:70:d8:60 wlan0: RX AssocResp from 00:14:f2:70:d8:60 (capab=0x21 status=18 aid=0) wlan0: AP denied association (code=18) wlan0: associate with AP 00:14:f2:70:d8:60 wlan0: RX AssocResp from 00:14:f2:70:d8:60 (capab=0x21 status=18 aid=0) wlan0: AP denied association (code=18) wlan0: association with AP 00:14:f2:70:d8:60 timed out eth0: no IPv6 routers present type=1305 audit(1264790023.909:43387): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=system_u:system_r:readahead_t:s0 res=1 wlan0: authenticate with AP 00:14:1c:15:f6:90 wlan0: authenticated wlan0: associate with AP 00:14:1c:15:f6:90 wlan0: RX AssocResp from 00:14:1c:15:f6:90 (capab=0x421 status=0 aid=31) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready cfg80211: Calling CRDA for country: US cfg80211: Current regulatory domain updated by AP to: US (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) wlan0: no IPv6 routers present wlan0: deauthenticated (Reason: 1) wlan0: direct probe to AP 00:14:1c:15:f6:90 try 1 wlan0 direct probe responded wlan0: authenticate with AP 00:14:1c:15:f6:90 wlan0: authenticated wlan0: associate with AP 00:14:1c:15:f6:90 wlan0: RX ReassocResp from 00:14:1c:15:f6:90 (capab=0x421 status=0 aid=34) wlan0: associated wlan0: deauthenticated (Reason: 1) wlan0: direct probe to AP 00:14:1c:15:f6:90 try 1 wlan0 direct probe responded wlan0: authenticate with AP 00:14:1c:15:f6:90 wlan0: authenticated wlan0: associate with AP 00:14:1c:15:f6:90 wlan0: RX ReassocResp from 00:14:1c:15:f6:90 (capab=0x421 status=0 aid=37) wlan0: associated CE: hpet increasing min_delta_ns to 15000 nsec wlan0: authenticate with AP 00:14:f2:70:d3:a0 wlan0: authenticated wlan0: associate with AP 00:14:f2:70:d3:a0 wlan0: RX ReassocResp from 00:14:f2:70:d3:a0 (capab=0x21 status=18 aid=37) wlan0: AP denied association (code=18) wlan0: associate with AP 00:14:f2:70:d3:a0 wlan0: RX AssocResp from 00:14:f2:70:d3:a0 (capab=0x21 status=18 aid=37) wlan0: AP denied association (code=18) wlan0: associate with AP 00:14:f2:70:d3:a0 wlan0: RX AssocResp from 00:14:f2:70:d3:a0 (capab=0x21 status=18 aid=37) wlan0: AP denied association (code=18) wlan0: association with AP 00:14:f2:70:d3:a0 timed out
(In reply to comment #8) > Here are the messages from dmesg. The system log viewer does not update dmesg, > so that is why I was not seeing the output (that may be another different bug > altogether!). Default setting of system logger not log kernel debug information to /var/log/messages. You can edit /etc/rsyslog.conf to change that. > wlan0: associate with AP 00:14:f2:70:d3:a0 > wlan0: RX AssocResp from 00:14:f2:70:d3:a0 (capab=0x21 status=18 aid=37) > wlan0: AP denied association (code=18) We have few AP in your network, to most of them we fail to associate because of code 18. To some of them we successfully associate but after that AP deauthenticated us for unknown reason. code 18 mean we (station) do not support transmit rates that AP requires. I do some code revision and suspect that in some circumstances linux mac80211 stack can send corrupted Supported Rates information element. I'm going to prepare patch with fix and with more verbose messages about bit rates to help diagnose problem.
Hi Enrique, Could you please run kernel from http://koji.fedoraproject.org/koji/taskinfo?taskID=1960573 There is small chance that it can fix the issue. If not, please provide dmesg as new kernel will print some extra debug information.
Hi, Just to be sure. I need to install: kernel-2.6.31.9-174.sgtest2.fc12.x86_64.rpm kernel-debug-2.6.31.9-174.sgtest2.fc12.x86_64.rpm kernel-headers-2.6.31.9-174.sgtest2.fc12.x86_64.rpm Do I need to install these? kernel-debug-debuginfo-2.6.31.9-174.sgtest2.fc12.x86_64.rpm kernel-debuginfo-2.6.31.9-174.sgtest2.fc12.x86_64.rpm kernel-debuginfo-common-x86_64-2.6.31.9-174.sgtest2.fc12.x86_64.rpm kernel-debug-devel-2.6.31.9-174.sgtest2.fc12.x86_64.rpm kernel-devel-2.6.31.9-174.sgtest2.fc12.x86_64.rpm Don't I need also kernel-firmware-2.6.31.9.174? Thanks, Enrique
Ah, sorry I didn't inform you before. You have to install firmware and kernel (as root): rpm -ivh kernel-firmware-2.6.31.9-174.sgtest2.fc12.noarch.rpm rpm -ivh kernel-2.6.31.9-174.sgtest2.fc12.x86_64.rpm Firmware package is in "buildArch (kernel-2.6.31.9-174.sgtest2.fc12.src.rpm, noarch" subdirectory: http://koji.fedoraproject.org/koji/taskinfo?taskID=1960576 Please test it as soon as possible, because this is "scratch" build - that's mean packages are removed after a week or so. Thanks.
Hi, The modified kernel did not fix the issue. Below are the dmesg relevant parts. Thanks, Enrique eth0: Tigon3 [partno(BCM95761e) rev 5761100] (PCI Express) MAC address 00:26:b9:00:e3:21 eth0: attached PHY is 5761 (10/100/1000Base-T Ethernet) (WireSpeed[1]) eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] eth0: dma_rwctrl[76180000] dma_mask[64-bit] iTCO_vendor_support: vendor-support=0 dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19 iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27kds iwlagn: Copyright(c) 2003-2009 Intel Corporation iwlagn 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwlagn 0000:0c:00.0: setting latency timer to 64 iwlagn 0000:0c:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54 iwlagn 0000:0c:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels alloc irq_desc for 32 on node 0 alloc kstat_irqs on node 0 iwlagn 0000:0c:00.0: irq 32 for MSI/MSI-X ----- NET: Registered protocol family 10 lo: Disabled Privacy Extensions ip6_tables: (C) 2000-2006 Netfilter Core Team iwlagn 0000:0c:00.0: firmware: requesting iwlwifi-5000-2.ucode iwlagn 0000:0c:00.0: loaded firmware version 8.24.2.12 Registered led device: iwl-phy0::radio Registered led device: iwl-phy0::assoc Registered led device: iwl-phy0::RX Registered led device: iwl-phy0::TX ADDRCONF(NETDEV_UP): wlan0: link is not ready tg3 0000:09:00.0: PME# disabled alloc irq_desc for 33 on node 0 alloc kstat_irqs on node 0 tg3 0000:09:00.0: irq 33 for MSI/MSI-X ADDRCONF(NETDEV_UP): eth0: link is not ready ---- tg3: eth0: Link is up at 100 Mbps, full duplex. tg3: eth0: Flow control is off for TX and off for RX. ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready wlan0: authenticate with AP 00:14:f2:70:d8:b0 wlan0: authenticated wlan0: associate with AP 00:14:f2:70:d8:b0 ieee80211_send_assoc supported rates IE: 0100 wlan0: RX AssocResp from 00:14:f2:70:d8:b0 (capab=0x21 status=18 aid=0) ieee80211_rx_mgmt_assoc_resp supported rates: 82848b96 ieee80211_rx_mgmt_assoc_resp extended supported rates: 3048606c wlan0: AP denied association (code=18) wlan0: associate with AP 00:14:f2:70:d8:b0 ieee80211_send_assoc supported rates IE: 0100 wlan0: RX AssocResp from 00:14:f2:70:d8:b0 (capab=0x21 status=18 aid=0) ieee80211_rx_mgmt_assoc_resp supported rates: 82848b96 ieee80211_rx_mgmt_assoc_resp extended supported rates: 3048606c wlan0: AP denied association (code=18) wlan0: associate with AP 00:14:f2:70:d8:b0 ieee80211_send_assoc supported rates IE: 0100 wlan0: RX AssocResp from 00:14:f2:70:d8:b0 (capab=0x21 status=18 aid=0) ieee80211_rx_mgmt_assoc_resp supported rates: 82848b96 ieee80211_rx_mgmt_assoc_resp extended supported rates: 3048606c wlan0: AP denied association (code=18) wlan0: association with AP 00:14:f2:70:d8:b0 timed out eth0: no IPv6 routers present fuse init (API version 7.12) SELinux: initialized (dev fuse, type fuse), uses genfs_contexts
(In reply to comment #13) > wlan0: AP denied association (code=18) > wlan0: associate with AP 00:14:f2:70:d8:b0 > ieee80211_send_assoc supported rates IE: > 0100 This is completely wrong, but I do not figure out where the bug can be. I probably prepare new kernel with more verbose debug to find out problem. Since then, please try new 2.6.32 based kernel from fedora updates testing repository: yum --enablerepo="updates-testing" update kernel
Hi, Tried the new kernel (kernel-2.6.32.7-37.fc12.x86_64), same problem. See dmesg below. Thanks, Enrique iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27kds iwlagn: Copyright(c) 2003-2009 Intel Corporation iwlagn 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwlagn 0000:0c:00.0: setting latency timer to 64 iwlagn 0000:0c:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54 iwlagn 0000:0c:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels alloc irq_desc for 32 on node -1 alloc kstat_irqs on node -1 iwlagn 0000:0c:00.0: irq 32 for MSI/MSI-X name_count maxed, losing inode data: dev=00:07, inode=11511 --- iwlagn 0000:0c:00.0: firmware: requesting iwlwifi-5000-2.ucode iwlagn 0000:0c:00.0: loaded firmware version 8.24.2.12 Registered led device: iwl-phy0::radio Registered led device: iwl-phy0::assoc Registered led device: iwl-phy0::RX Registered led device: iwl-phy0::TX ADDRCONF(NETDEV_UP): wlan0: link is not ready alloc irq_desc for 33 on node -1 alloc kstat_irqs on node -1 tg3 0000:09:00.0: irq 33 for MSI/MSI-X --- tg3: eth0: Link is up at 100 Mbps, full duplex. tg3: eth0: Flow control is off for TX and off for RX. ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready wlan0: deauthenticating from 00:14:f2:70:d8:60 by local choice (reason=3) wlan0: direct probe to AP 00:14:f2:70:d8:60 (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:14:f2:70:d8:60 (try 1) wlan0: authenticated wlan0: associate with AP 00:14:f2:70:d8:60 (try 1) wlan0: RX AssocResp from 00:14:f2:70:d8:60 (capab=0x21 status=18 aid=0) wlan0: AP denied association (code=18) wlan0: deauthenticating from 00:14:f2:70:d8:60 by local choice (reason=3) btusb_intr_complete: hci0 urb ffff88020fbf8f00 failed to resubmit (1) btusb_bulk_complete: hci0 urb ffff88020fbf80c0 failed to resubmit (1) btusb_bulk_complete: hci0 urb ffff88020fbf8000 failed to resubmit (1) eth0: no IPv6 routers present btusb_intr_complete: hci0 urb ffff8801fd5269c0 failed to resubmit (1) btusb_bulk_complete: hci0 urb ffff8801fd526900 failed to resubmit (1) btusb_bulk_complete: hci0 urb ffff8801fd526a80 failed to resubmit (1) wlan0: direct probe to AP 00:14:f2:70:d8:60 (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:14:f2:70:d8:60 (try 1) wlan0: authenticated wlan0: associate with AP 00:14:f2:70:d8:60 (try 1) wlan0: RX AssocResp from 00:14:f2:70:d8:60 (capab=0x21 status=18 aid=0) wlan0: AP denied association (code=18) wlan0: deauthenticating from 00:14:f2:70:d8:60 by local choice (reason=3) wlan0: direct probe to AP 00:14:f2:70:d8:60 (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:14:f2:70:d8:60 (try 1) wlan0: authenticated wlan0: associate with AP 00:14:f2:70:d8:60 (try 1) wlan0: RX AssocResp from 00:14:f2:70:d8:60 (capab=0x21 status=18 aid=0) wlan0: AP denied association (code=18) wlan0: deauthenticating from 00:14:f2:70:d8:60 by local choice (reason=3) -------------------------------------------------------------------------- wpa_supplicant log is a little bit different than before: Trying to associate with 00:14:f2:70:d8:60 (SSID='bgsu' freq=2412 MHz) Association request to the driver failed Authentication with 00:14:f2:70:d8:60 timed out. Trying to associate with 00:14:f2:70:d8:60 (SSID='bgsu' freq=2412 MHz) Association request to the driver failed Authentication with 00:14:f2:70:d8:60 timed out. Trying to associate with 00:14:f2:70:d8:60 (SSID='bgsu' freq=2412 MHz) Association request to the driver failed Authentication with 00:14:f2:70:d8:60 timed out. Trying to associate with 00:14:f2:70:d8:60 (SSID='bgsu' freq=2412 MHz) Association request to the driver failed Authentication with 00:00:00:00:00:00 timed out.
Hi Enrique Please run below kernel and provide two dmesg's outputs. First running kernel as is second with additional debug50=0x00100000 option. You can add option to /etc/modprobe/iwlagn and reload modules or pass it as command line parameter like here: "rmmod iwlagn iwlcore ; modprobe iwlagn debug50=0x00100000 ". Attach full dmesg so I could also see messages when module starts. Here is the kernel: http://koji.fedoraproject.org/koji/taskinfo?taskID=1988628
Created attachment 394790 [details] dmesg log for kernel-2.6.31.9-174.sgtest3.fc12.x86_64 Attachment of full dmesg running kernel as is. -Enrique
Hi, Please explain how to add the option for additional debugging debug50=0x00100000. When I add the line (debug50=0x00100000) to file iwlagn.conf and reboot I get WARNING: /etc/modprobe.d/iwlagn.conf line 1: ignoring bad line starting with 'debug50=0x00100000' Thanks, Enrique
Created attachment 394793 [details] dmesg log for kernel-2.6.31.9-174.sgtest3.fc12.x86_64 and debug50=0x00100000 dmesg output for kernel 2.6.31.9-174.sgtest3.fc12.x86_64 using debug50=0x00100000 in iwlagn.
(In reply to comment #18) > WARNING: /etc/modprobe.d/iwlagn.conf line 1: ignoring bad line starting with > 'debug50=0x00100000' You need to have "options" keyword like: options iwlagn debug50=0x00100000
Enrique, I believe this kernel include fix for your problem, please test. If not I will have to think again about whole issue and prepare next debug kernel. However I hope this one is ok. http://koji.fedoraproject.org/koji/taskinfo?taskID=1998566
Created attachment 395189 [details] output from dmesg for kernel-2.6.31.9-174.sgtest4.fc12.x86_64 Hi, Unfortunately, the new kernel does not fix the problem either. See the attached dmesg for more information. Thanks, Enrique
Ok, next kernel with another potencial fix: http://koji.fedoraproject.org/koji/taskinfo?taskID=2004655 I also add some additional verbose debug prints when module mac80211 is loaded with mdebug=1 option. If kernel will not work, provide dmesg logs as previous and /var/log/messages with mdebug=1 (add "option mac80211 mdebug=1" line in modprobe config file). These messages are quite frequent so pure dmesg size will not be enough to contains them all.
Hi Enrique Any test result of above kernel?
Created attachment 396419 [details] output from dmesg for kernel-2.6.31.9-174.sgtest5.fc12.x86_64 Hi, Unfortunately kernel-2.6.31.9-174.sgtest5.fc12.x86_64 does not fix the problem. Attached is the dmesg log. I will test it with the debug option tomorrow. Thanks. Enrique
Created attachment 396669 [details] dmesg log for kernel-2.6.31.9-174.sgtest5.fc12.x86_64 and mac80211 mdebug=1 Here is the output from dmesg for kernel-2.6.31.9-174.sgtest5.fc12.x86_64 with the option mac80211 mdebug=1.
Created attachment 396670 [details] messages log for kernel-2.6.31.9-174.sgtest5.fc12.x86_64 and mac80211 mdebug=1 Here is the log from messages for kernel-2.6.31.9-174.sgtest5.fc12.x86_64 with the options mac80211 mdebug=1. Thanks, Enrique
Enrique Could you check out new kernel from here: http://koji.fedoraproject.org/koji/taskinfo?taskID=2044352 It contains QoS fix, maybe this is also fix for your issue.
Hi Enrique Please test or at least download kernel before it expire on koji server. Thanks.
Hi! Great, that did it! kernel-2.6.32.8-48.rc2.sg_test1.fc12.x86_64 fixed the problem. I now have a working wireless. Thanks! Enrique
Hi, Where can I download a test kernel to test if this solve my problem too? thanks in advance dmesg with latest F12 kernel (2.6.32.11-99.fc12.i686.PAE) wlan0: deauthenticating from 00:08:54:8a:c5:50 by local choice (reason=3) wlan0: direct probe to AP 00:08:54:8a:c5:50 (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:08:54:8a:c5:50 (try 1) wlan0: authenticated wlan0: associate with AP 00:08:54:8a:c5:50 (try 1) wlan0: RX AssocResp from 00:08:54:8a:c5:50 (capab=0x411 status=0 aid=193) wlan0: invalid aid value 193; bits 15:14 not set wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: no IPv6 routers present wlan0: disassociated from 00:08:54:8a:c5:50 (Reason: 14) wlan0: deauthenticating from 00:08:54:8a:c5:50 by local choice (reason=3) wlan0: direct probe to AP 00:08:54:8a:c5:50 (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:08:54:8a:c5:50 (try 1) wlan0: authenticated wlan0: associate with AP 00:08:54:8a:c5:50 (try 1) wlan0: RX AssocResp from 00:08:54:8a:c5:50 (capab=0x411 status=12 aid=193) wlan0: AP denied association (code=12) wlan0: deauthenticating from 00:08:54:8a:c5:50 by local choice (reason=3) wlan0: direct probe to AP 00:08:54:8a:c5:50 (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:08:54:8a:c5:50 (try 1) wlan0: authenticated wlan0: associate with AP 00:08:54:8a:c5:50 (try 1) wlan0: RX AssocResp from 00:08:54:8a:c5:50 (capab=0x411 status=12 aid=193) wlan0: AP denied association (code=12) wlan0: deauthenticating from 00:08:54:8a:c5:50 by local choice (reason=3) wlan0: direct probe to AP 00:08:54:8a:c5:50 (try 1) wlan0: direct probe responded wlan0: authenticate with AP 00:08:54:8a:c5:50 (try 1) wlan0: authenticated wlan0: associate with AP 00:08:54:8a:c5:50 (try 1) wlan0: RX AssocResp from 00:08:54:8a:c5:50 (capab=0x411 status=12 aid=193) wlan0: AP denied association (code=12) wlan0: deauthenticating from 00:08:54:8a:c5:50 by local choice (reason=3)
Ricardo, Enrique, Upstream mac80211 maintainer do not like QoS fix I proposed and I had to rework on in. Finally fix get in into wireless-next tree a two weeks ago, but unfortunately we do not have them in Fedora yet. Please test flowing kernel: http://koji.fedoraproject.org/koji/taskinfo?taskID=2119725 It include new upstream QoS fix backported to fedora. It not include previous "Supported rates" fix proposed in this bugzilla before. kernel-2.6.32.8-48.rc2.sg_test1 which works included both QoS and "Supported rates" fixes. Enrique, please test the new kernel, to see if "Supported rates" fix is really needed. Thanks.
Hi Stanislaw, Unfortunately, the kernel including only the QoS fix breaks the wifi in my computer just as before. So, the "Supported rates" fix is really needed for the wifi of my DELL Precision M6400 to work. Thanks, Enrique
Here is build with both fixes, please test: http://koji.fedoraproject.org/koji/taskinfo?taskID=2132358
Hi Stanislaw, With both fixes the wifi is working again. kernel-2.6.32.11-103.sg3.fc12.x86_64 kernel-firmware-2.6.32.11-103.sg3.fc12.noarch Thanks! Enrique
Hi, Would this fix ever move upstream? The latest kernel, kernel-2.6.32.12-115.fc12.x86_64 still breaks wifi in a Dell Precision M6400 laptop. Thanks, Enrique
Hi Enrique I'm sorry, I was quite busy. Fixes are now available in upstream 2.6.35-rc1 kernel. Now we can put them in fedora, but this again will take some time. I will take care of that in this or next week.
Finally fixed after half a year :) http://koji.fedoraproject.org/koji/buildinfo?buildID=177949
Hi Stanislaw, I thought you may find this interesting. I'm currently running kernel-2.6.32.14-127.fc12.x86_64, which is not the one that has the fixes. But I noticed a couple of days ago that the wireless is working fine with this kernel. I wonder if the bug was in some other package that I updated recently. Would you like to send you the list of updated packages from yumex? Cheers, Enrique
Hi Enrique (In reply to comment #39) > Would you like to send you the list of updated packages from yumex? Well, I'm happy that it works, it is or at least it should be normal sytuation, so I will not investigate why it works :-) Closing bug.
kernel-2.6.33.6-147.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/kernel-2.6.33.6-147.fc13
kernel-2.6.32.16-141.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/kernel-2.6.32.16-141.fc12
kernel-2.6.33.6-147.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
kernel-2.6.32.16-141.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
Hi Stanislaw, I just installed the latest kernel (2.6.32.16-150.fc12.x86_64) and the wireless is broken once again. It worked fine with 2.6.32.16-141.fc12.x86_64. Thanks, Enrique
Hi, That's strange. According logs there was no changes in wireless between -141 and -150 kernel. There was some change in crypto code, I will look more closely at it, but at first glance it was unrelated ... Looking at Comment 39 I'm starting to suspect problem can be not in kernel. Or perhaps now there is different kernel problem that is not 100% reproducible, and showed up randomly. Anyway we need more debug. What shows logs when kernel is not able to connect? Please also try up-to-dake kernel from koji to see if it make any difference.
Hi Stanislaw, Here are some log reports: iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27kds iwlagn: Copyright(c) 2003-2009 Intel Corporation iwlagn 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 iwlagn 0000:0c:00.0: setting latency timer to 64 iwlagn 0000:0c:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54 iwlagn 0000:0c:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels alloc irq_desc for 32 on node -1 alloc kstat_irqs on node -1 iwlagn 0000:0c:00.0: irq 32 for MSI/MSI-X and when I try to connect: Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> Activation (wlan0) starting connection 'Wireless connection 1' Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> (wlan0): device state change: 3 -> 4 (reason 0) Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> (wlan0): device state change: 4 -> 5 (reason 0) Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> Activation (wlan0/wireless): connection 'Wireless connection 1' requires no security. No secrets needed. Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> Config: added 'ssid' value 'bgsu' Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> Config: added 'scan_ssid' value '1' Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> Config: added 'key_mgmt' value 'NONE' Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> Config: set interface ap_scan to 1 Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> (wlan0): supplicant connection state: scanning -> disconnected Aug 25 12:20:21 papaloapan NetworkManager[2201]: <info> (wlan0): supplicant connection state: disconnected -> scanning Aug 25 12:20:24 papaloapan NetworkManager[2201]: <info> (wlan0): supplicant connection state: scanning -> associating Aug 25 12:20:34 papaloapan NetworkManager[2201]: <info> (wlan0): supplicant connection state: associating -> disconnected Aug 25 12:20:34 papaloapan NetworkManager[2201]: <info> (wlan0): supplicant connection state: disconnected -> scanning Aug 25 12:20:37 papaloapan NetworkManager[2201]: <warn> (wlan0): link timed out. Aug 25 12:20:37 papaloapan NetworkManager[2201]: <info> (wlan0): supplicant connection state: scanning -> associating Aug 25 12:20:47 papaloapan NetworkManager[2201]: <warn> Activation (wlan0/wireless): association took too long, failing activation. Aug 25 12:20:47 papaloapan NetworkManager[2201]: <info> (wlan0): device state change: 5 -> 9 (reason 11) Aug 25 12:20:47 papaloapan NetworkManager[2201]: <warn> Activation (wlan0) failed for access point (bgsu) Aug 25 12:20:47 papaloapan NetworkManager[2201]: <info> Marking connection 'Wireless connection 1' invalid. Aug 25 12:20:47 papaloapan NetworkManager[2201]: <warn> Activation (wlan0) failed. Aug 25 12:20:47 papaloapan NetworkManager[2201]: <info> (wlan0): device state change: 9 -> 3 (reason 0) Aug 25 12:20:47 papaloapan NetworkManager[2201]: <info> (wlan0): deactivating device (reason: 0). I am currently running kernel 2.6.32.19-163.fc12.x86_64. These are all the packages that were updated when the wireless broke again. True-Install kernel-2.6.32.16.150.fc12.x86_64 kernel-devel-2.6.32.16.150.fc12.x86_64 Update SDL-1.2.13.12.fc12.x86_64 VirtualBox-3.2-3.2.8_64453_fedora12.1.x86_64 cryptsetup-luks-1.1.3.1.fc12.x86_64 cryptsetup-luks-libs-1.1.3.1.fc12.x86_64 dhclient-12:4.1.1.18.P1.fc12.x86_64 doxygen-1:1.7.1.1.fc12.x86_64 eject-2.1.5.18.fc12.x86_64 emacs-common-ess-5.11.1.fc12.noarch emacs-ess-5.11.1.fc12.noarch git-1.7.2.1.2.fc12.x86_64 git-email-1.7.2.1.2.fc12.noarch gnome-settings-daemon-2.28.2.2.fc12.x86_64 indent-2.2.11.1.fc12.x86_64 java-1.6.0-openjdk-1:1.6.0.0.40.b18.fc12.x86_64 java-1.6.0-openjdk-plugin-1:1.6.0.0.40.b18.fc12.x86_64 kernel-firmware-2.6.32.16.150.fc12.noarch kernel-headers-2.6.32.16.150.fc12.x86_64 kmod-nvidia-1:195.36.31.1.fc12.2.x86_64 libass-0.9.9.1.fc12.x86_64 mysql-libs-5.1.47.2.fc12.x86_64 perf-2.6.32.16.150.fc12.noarch perl-4:5.10.0.91.fc12.x86_64 perl-Archive-Extract-1:0.30.91.fc12.x86_64 perl-Archive-Tar-1.62.91.fc12.x86_64 perl-CPAN-1.9205.91.fc12.x86_64 perl-CPANPLUS-0.84.91.fc12.x86_64 perl-Compress-Zlib-2.008.91.fc12.x86_64 perl-Digest-SHA-1:5.47.91.fc12.x86_64 perl-ExtUtils-CBuilder-1:0.24.91.fc12.x86_64 perl-ExtUtils-Embed-1.28.91.fc12.x86_64 perl-ExtUtils-MakeMaker-6.36.91.fc12.x86_64 perl-ExtUtils-ParseXS-1:2.18.91.fc12.x86_64 perl-File-Fetch-0.18.91.fc12.x86_64 perl-Git-1.7.2.1.2.fc12.noarch perl-IO-Compress-Base-2.015.91.fc12.x86_64 perl-IO-Compress-Zlib-2.015.91.fc12.x86_64 perl-IO-Zlib-1:1.07.91.fc12.x86_64 perl-IPC-Cmd-1:0.42.91.fc12.x86_64 perl-Locale-Maketext-Simple-1:0.18.91.fc12.x86_64 perl-Log-Message-1:0.01.91.fc12.x86_64 perl-Log-Message-Simple-0.04.91.fc12.x86_64 perl-Module-Build-1:0.3200.91.fc12.x86_64 perl-Module-CoreList-2.17.91.fc12.x86_64 perl-Module-Load-1:0.12.91.fc12.x86_64 perl-Module-Load-Conditional-0.30.91.fc12.x86_64 perl-Module-Loaded-1:0.01.91.fc12.x86_64 perl-Module-Pluggable-1:3.90.91.fc12.x86_64 perl-Object-Accessor-1:0.32.91.fc12.x86_64 perl-Package-Constants-1:0.01.91.fc12.x86_64 perl-Params-Check-1:0.26.91.fc12.x86_64 perl-Pod-Escapes-1:1.04.91.fc12.x86_64 perl-Pod-Simple-1:3.07.91.fc12.x86_64 perl-Term-UI-0.18.91.fc12.x86_64 perl-Test-Harness-3.16.91.fc12.x86_64 perl-Test-Simple-0.92.91.fc12.x86_64 perl-Time-Piece-1.12.91.fc12.x86_64 perl-core-5.10.0.91.fc12.x86_64 perl-devel-4:5.10.0.91.fc12.x86_64 perl-libs-4:5.10.0.91.fc12.x86_64 perl-suidperl-4:5.10.0.91.fc12.x86_64 poppler-0.12.4.4.fc12.x86_64 poppler-glib-0.12.4.4.fc12.x86_64 poppler-utils-0.12.4.4.fc12.x86_64 python-lxml-2.2.5.1.fc12.x86_64 qgis-1.5.0.3.fc12.x86_64 qgis-grass-1.5.0.3.fc12.x86_64 qgis-python-1.5.0.3.fc12.x86_64 systemtap-1.3.2.fc12.x86_64 systemtap-runtime-1.3.2.fc12.x86_64 tzdata-2010k.1.fc12.noarch tzdata-java-2010k.1.fc12.noarch vorbis-tools-1:1.2.0.8.fc12.x86_64 xorg-x11-xinit-1.0.9.16.fc12.x86_64 xsane-0.997.10.fc12.x86_64 xsane-common-0.997.10.fc12.x86_64 xsane-gimp-0.997.10.fc12.x86_64 Erase kernel-2.6.32.12.115.fc12.x86_64 kernel-devel-2.6.32.12.115.fc12.x86_64 Dep-Install gdal-python-1.6.1.2.fc12.x86_64 kmod-nvidia-2.6.32.16-150.fc12.x86_64-1:195.36.31.1.fc12.2.x86_64 Updated SDL-1.2.13.11.fc12.x86_64 VirtualBox-3.2-3.2.6_63112_fedora12.1.x86_64 cryptsetup-luks-1.1.0.0.4.fc12.x86_64 cryptsetup-luks-libs-1.1.0.0.4.fc12.x86_64 dhclient-12:4.1.1.17.P1.fc12.x86_64 doxygen-1:1.6.1.1.fc12.x86_64 eject-2.1.5.17.fc12.x86_64 emacs-common-ess-5.8.1.fc12.noarch emacs-ess-5.8.1.fc12.noarch git-1.7.2.1.fc12.x86_64 git-email-1.7.2.1.fc12.noarch gnome-settings-daemon-2.28.2.1.fc12.x86_64 indent-2.2.10.5.fc12.x86_64 java-1.6.0-openjdk-1:1.6.0.0.39.b18.fc12.x86_64 java-1.6.0-openjdk-plugin-1:1.6.0.0.39.b18.fc12.x86_64 kernel-firmware-2.6.32.16.141.fc12.noarch kernel-headers-2.6.32.16.141.fc12.x86_64 kmod-nvidia-1:195.36.31.1.fc12.1.x86_64 libass-0.9.7.1.fc12.x86_64 mysql-libs-5.1.47.1.fc12.x86_64 perf-2.6.32.16.141.fc12.noarch perl-4:5.10.0.90.fc12.x86_64 perl-Archive-Extract-1:0.30.90.fc12.x86_64 perl-Archive-Tar-1.62.90.fc12.x86_64 perl-CPAN-1.9205.90.fc12.x86_64 perl-CPANPLUS-0.84.90.fc12.x86_64 perl-Compress-Zlib-2.008.90.fc12.x86_64 perl-Digest-SHA-1:5.47.90.fc12.x86_64 perl-ExtUtils-CBuilder-1:0.24.90.fc12.x86_64 perl-ExtUtils-Embed-1.28.90.fc12.x86_64 perl-ExtUtils-MakeMaker-6.36.90.fc12.x86_64 perl-ExtUtils-ParseXS-1:2.18.90.fc12.x86_64 perl-File-Fetch-0.18.90.fc12.x86_64 perl-Git-1.7.2.1.fc12.noarch perl-IO-Compress-Base-2.015.90.fc12.x86_64 perl-IO-Compress-Zlib-2.015.90.fc12.x86_64 perl-IO-Zlib-1:1.07.90.fc12.x86_64 perl-IPC-Cmd-1:0.42.90.fc12.x86_64 perl-Locale-Maketext-Simple-1:0.18.90.fc12.x86_64 perl-Log-Message-1:0.01.90.fc12.x86_64 perl-Log-Message-Simple-0.04.90.fc12.x86_64 perl-Module-Build-1:0.3200.90.fc12.x86_64 perl-Module-CoreList-2.17.90.fc12.x86_64 perl-Module-Load-1:0.12.90.fc12.x86_64 perl-Module-Load-Conditional-0.30.90.fc12.x86_64 perl-Module-Loaded-1:0.01.90.fc12.x86_64 perl-Module-Pluggable-1:3.90.90.fc12.x86_64 perl-Object-Accessor-1:0.32.90.fc12.x86_64 perl-Package-Constants-1:0.01.90.fc12.x86_64 perl-Params-Check-1:0.26.90.fc12.x86_64 perl-Pod-Escapes-1:1.04.90.fc12.x86_64 perl-Pod-Simple-1:3.07.90.fc12.x86_64 perl-Term-UI-0.18.90.fc12.x86_64 perl-Test-Harness-3.16.90.fc12.x86_64 perl-Test-Simple-0.92.90.fc12.x86_64 perl-Time-Piece-1.12.90.fc12.x86_64 perl-core-5.10.0.90.fc12.x86_64 perl-devel-4:5.10.0.90.fc12.x86_64 perl-libs-4:5.10.0.90.fc12.x86_64 perl-suidperl-4:5.10.0.90.fc12.x86_64 poppler-0.12.4.2.fc12.x86_64 poppler-glib-0.12.4.2.fc12.x86_64 poppler-utils-0.12.4.2.fc12.x86_64 python-lxml-2.2.3.1.fc12.x86_64 qgis-1.0.2.6.fc12.x86_64 qgis-grass-1.0.2.6.fc12.x86_64 qgis-python-1.0.2.6.fc12.x86_64 systemtap-1.2.1.fc12.x86_64 systemtap-runtime-1.2.1.fc12.x86_64 tzdata-2010j.1.fc12.noarch tzdata-java-2010j.1.fc12.noarch vorbis-tools-1:1.2.0.6.fc12.x86_64 xorg-x11-xinit-1.0.9.14.fc12.x86_64 xsane-0.997.8.fc12.x86_64 xsane-common-0.997.8.fc12.x86_64 xsane-gimp-0.997.8.fc12.x86_64 Thanks! Enrique
Hi. Could you not load proprietary kmod-nvidia driver and check if that helps? When attempt to connect do you have similar dmesg messages like in comment 8?
Hi, Now, it gets interesting. With kernel 2.6.32.19-163.fc12.x86_64 it is working again. I know it is not the wireless node because there is a WinXP PC next to mine that has not lost any connectivity. The proprietary kmod-nvidia driver was not the problem either. After the kernel update the only updates that I installed were: NetworkManager-openvpn-1:0.8.1.0.1.git20100609.fc12.x86_64 git-1.7.2.2.1.fc12.x86_64 git-email-1.7.2.2.1.fc12.noarch perl-Git-1.7.2.2.1.fc12.noarch python-ethtool-0.5.1.fc12.x86_64 selinux-policy-3.6.32.121.fc12.noarch selinux-policy-targeted-3.6.32.121.fc12.noarch Go figure! Thanks, Enrique
Hi. I have no idea what is going on. So 2.6.32.19-163 does not work in first (comment 48), and start works now (comment 50), it that correct. > NetworkManager-openvpn-1:0.8.1.0.1.git20100609.fc12.x86_64 > git-1.7.2.2.1.fc12.x86_64 > git-email-1.7.2.2.1.fc12.noarch > perl-Git-1.7.2.2.1.fc12.noarch > python-ethtool-0.5.1.fc12.x86_64 > selinux-policy-3.6.32.121.fc12.noarch > selinux-policy-targeted-3.6.32.121.fc12.noarch Well, any of these packages are not related with wireless. NetworkManager update is for openvpn, selinux is suspicious but it almost sure is also unrelated. I suspect we still have some problem, but it is not 100% reproducible, so sometimes kernel work sometimes not.
Hi Enrique Issue that you reported at the beginning (supported rates and QoS bugs) is for sure fixed. So I'm closing this bug. For further issues that you have, please open a new bug report and assign it to me. To allow to see where possibly the problem can be, configure wpa_supplicant and rsyslog as described in "Configure for basic debug" in https://fedoraproject.org/wiki/DebugWireless. Then if problem happens again, open new bug and provide reasonable part of /var/log/messages. Thanks.