Monitor mode not working for iwi(4) on 7.X

[Brandon Gooch]

2010/10/6 Alexey Dokuchaev <danfe at freebsd.org>:
> On Fri, Dec 14, 2007 at 11:19:25PM +0100, Jan Henrik Sylvester wrote:
>> In contrast to 6.2-RELEASE, monitor mode does not work. Kismet does
>> not receive anything, while it does with ath or ural (even at the same
>> time). dmesg with debug.iwi=2 is below -- anything unusual?
>>
>> Moreover, "ifconfig iwi0 scan" sometimes just hangs, which never
>> happened on 6.2-RELEASE.
>
> Just found this email sent to stable@ almost three years ago; sadly I
> have to confirm iwi(4) still exhibits these problems on fairly recent
> 7-STABLE (early Juneish).  Maybe I have better luck on net@ (I am
> particularly interested in working monitor mode).  Thanks.  Any debug
> information will be gladly provided.  Pointers where to look (revisions
> to try, patches, etc.) are greatly appreciated.
>
> ./danfe
>
>> iwi_newstate: INIT -> INIT flags 0x0
>> enter FW state 1
>> Setting MAC address to 00:0e:35:91:2b:0b
>> sending command idx=0 type=11 len=6
>> Configuring adapter
>> sending command idx=1 type=6 len=20
>> Setting power mode to 0
>> sending command idx=2 type=17 len=4
>> Setting RTS threshold to 2346
>> sending command idx=3 type=15 len=4
>> Setting fragmentation threshold to 2346
>> sending command idx=4 type=16 len=4
>> Setting .11bg supported rates (12)
>> sending command idx=5 type=22 len=16
>> Setting .11a supported rates (0)
>> sending command idx=6 type=22 len=16
>> Setting initialization vector to 3524349664
>> sending command idx=7 type=34 len=4
>> Setting wep key index 0 len 0
>> sending command idx=8 type=18 len=20
>> Setting wep key index 1 len 0
>> sending command idx=9 type=18 len=20
>> Setting wep key index 2 len 0
>> sending command idx=10 type=18 len=20
>> Setting wep key index 3 len 0
>> sending command idx=11 type=18 len=20
>> Enabling adapter
>> sending command idx=12 type=2 len=0
>> iwi_newstate: INIT -> RUN flags 0x1
>> iwi_newstate: RUN -> RUN flags 0x1
>> exit FW state 1
>> Setting WME parameters
>> sending command idx=13 type=25 len=96

I know this response isn't too helpful, but the whole Intel
PRO/Wireless 2200BG/2225BG/2915ABG open-source driver situation is not
too good.

Same goes for the Intel 3945ABG (wpi(4)); it's very easy in both Linux
and *BSDs to befuddle the Intel Wifi chips.

Having said that, Bernhard Schmidt has made outstanding progress with
the iwn(4) driver, supporting Intel Wireless WiFi Link
4965/1000/5000/5150/5300/6000/6050 series.

Is it possible in your situation to try another wireless card? I know
some notebook computers only whitelist a small set of PCI devices...

-Brandon