From: S.R. M. <srm...@gm...> - 2012-04-19 10:21:40
|
Hey all, So, this issue has come up before and in troubleshooting it iv'e been trying different prebuilt kernels, compiling my own kernel and modules, etc... and im running into the following problem in almost every situation where the libertas_sdio or libertas modules load: root@overo:~# iwconfig wlan1 essid maddox ap 14:D6:4D:24:D8:1C channel 6 root@overo:~# cfg80211: Calling CRDA to update world regulatory domain iwconfig lo no wireless extensions. wlan1 IEEE 802.11bg ESSID:off/any Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on root@overo:~# iwconfig wlan1 essid maddox ap 14:D6:4D:24:D8:1C channel 6 root@overo:~# cfg80211: Calling CRDA to update world regulatory domain iwlist wlan1 scan wlan1 Scan completed : Cell 01 - Address: 14:D6:4D:24:D8:1C Channel:6 Frequency:2.437 GHz (Channel 6) Quality=46/70 Signal level=-64 dBm Encryption key:off ESSID:"maddox" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=0000008736e16f2c Extra: Last beacon: 601ms ago IE: Unknown: 00066D6164646F78 IE: Unknown: 010882848B960C121824 IE: Unknown: 030106 IE: Unknown: 2A0100 IE: Unknown: 32043048606C IE: Unknown: DD180050F2020101820003A4000027A4000042435E0062322F00 IE: Unknown: DD1E00904C334E101BFFFF000000000000000000000000000000000000000000 IE: Unknown: 2D1A4E101BFFFF000000000000000000000000000000000000000000 IE: Unknown: DD1A00904C3406001B00000000000000000000000000000000000000 IE: Unknown: 3D1606001B00000000000000000000000000000000000000 IE: Unknown: 4A0E14000A002C01C800140005001900 IE: Unknown: 7F0101 IE: Unknown: DD0900037F01010000FF7F IE: Unknown: DD0A00037F04010000004000 root@overo:~# In the latest development kernel and rootfs, libertas loads about 5 minutes after boot, and constantly outputs errors to the console BUT i can associate with the AP using iwconfig wlan1 essid maddox. So I'm wondering what's going on here - it looks like it's a driver issue, since the only things that changes the behavior of whether or not I can associate is the particular driver/kernel version loaded... Any ideas? I've gotten the kernel modules/kernel compiled that I'd like to use, with the 3.2.0+ image. No wifi would be a project killer though. I've tried moving the device closer to the AP to eliminate signal issues to no avail. |