Wey, As far as I can tell the config is setup properly for iwlagn but here is a link to my complete config: http://pastebin.com/yrynheyx Router information: Model: Buffalo WZR-HP-G300NH Firmware: DD-WRT v24SP2 (Buffalo official version) Band: 2.4ghz Channel: 9 Channel Width: 40mhz Mode: NG-Mixed While my laptop does have bluetooth I don't believe the module for it is loaded. Also, I've not been able to connect any other AP that I've tried. Thanks, Erik On Sat, Jun 18, 2011 at 6:12 AM, wwguy <wey-yi.w.guy@xxxxxxxxx> wrote: > Hi Erik, > > n Thu, 2011-06-16 at 23:14 -0700, Erik Hardesty wrote: >> Having trouble with iwlagn in kernels newer than 2.6.38. >> I've tried 2.6.39 and 3.0rc3 and both give me the same problem. >> I have the latest intel firmware installed on the system. Both >> iwlwifi-1000-3.ucode >> and iwlwifi-1000-5.ucode are in /lib/firmware >> >> Note: 2.6.38 does not exhibit the same issue and works fine. >> >> Symptom: Able to scan for access points but unable to connect. >> I am unable to connect to any router regardless of it being open, WEP, or WPAx. >> >> lspci -v | grep -i wifi: >> >> 03:00.0 Network controller: Intel Corporation WiFi Link 1000 Series >> Subsystem: Intel Corporation WiFi Link 1000 Series 1000BGN >> >> dmesg: >> >> myhost kernel: wlan0: direct probe to <ap> (try 1) >> myhost kernel: wlan0: direct probe to <ap> (try 2) >> myhost kernel: wlan0: direct probe to <ap> (try 3) >> myhost kernel: wlan0: direct probe to <ap> timed out >> myhost kernel: iwlagn 0000:03:00.0: fail to flush all tx fifo queues >> > There were a driver split happen to iwlagn between .38 and .39. Could > you please check your .config to make sure all the configuration set > correctly. > > I will also need more information on your setup, such as band and > channel, AP model... > > One more thing, do you have bluetooth in your system? is it on by > default? > > Thanks > Wey > > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
