iwi0 firmware error on Dell Inspiron 6000 w/ Intel PRO/Wireless
2200BG
Rainer Duffner
rainer at ultra-secure.de
Sun Oct 28 16:14:27 PDT 2007
Sam Leffler wrote:
> I just tested this on a t42 w/ 2200 card and it worked for me. Try
> setting debug.iwi to something like 2 or 5 and collect a log. The
> firmware is very finnicky and getting it to integrate w/ wpa_supplicant
> was a challenge.
Hi,
I also have this problem now, with 7-BETA1.
none4 at pci0:1:13:0: class=0x028000 card=0x27028086 chip=0x42208086
rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = 'PRO/Wireless 2200BG Network Connection'
class = network
Enabling these debug-options make iwi produce lots of these messages:
sending command idx=6 type=8 len=8
Scan request: index 2275 dwell 200/200/200
Scan 1 2.4GHz channels: 3/BDIR
sending command idx=7 type=26 len=96
received frame len=109 chan=3 rssi=20 rssi_dbm=47
Scan of channel 2422 complete (3)
Scan completed (1, 1)
exit FW state 4
enter FW state 4
sending command idx=8 type=8 len=8
Scan request: index 2276 dwell 200/200/200
Scan 1 2.4GHz channels: 4/BDIR
sending command idx=9 type=26 len=96
Scan of channel 2427 complete (4)
Scan completed (1, 1)
exit FW state 4
enter FW state 4
sending command idx=10 type=8 len=8
Scan request: index 2277 dwell 200/200/200
Scan 1 2.4GHz channels: 5/BDIR
sending command idx=11 type=26 len=96
received frame len=103 chan=5 rssi=23 rssi_dbm=61
Scan of channel 2432 complete (5)
Scan completed (1, 1)
exit FW state 4
enter FW state 4
sending command idx=12 type=8 len=8
Scan request: index 2278 dwell 200/200/200
Scan 1 2.4GHz channels: 8/BDIR
sending command idx=13 type=26 len=96
received frame len=103 chan=8 rssi=24 rssi_dbm=81
received frame len=122 chan=8 rssi=20 rssi_dbm=44
received frame len=109 chan=8 rssi=24 rssi_dbm=85
received frame len=122 chan=8 rssi=20 rssi_dbm=44
received frame len=109 chan=8 rssi=24 rssi_dbm=85
Scan of channel 2447 complete (8)
Scan completed (1, 1)
exit FW state 4
enter FW state 4
sending command idx=14 type=8 len=8
Scan request: index 2279 dwell 200/200/200
Scan 1 2.4GHz channels: 9/BDIR
sending command idx=15 type=26 len=96
received frame len=103 chan=9 rssi=24 rssi_dbm=85
received frame len=109 chan=9 rssi=24 rssi_dbm=81
received frame len=109 chan=9 rssi=24 rssi_dbm=85
Scan of channel 2452 complete (9)
Scan completed (1, 1)
exit FW state 4
enter FW state 4
sending command idx=0 type=8 len=8
Scan request: index 2280 dwell 200/200/200
Scan 1 2.4GHz channels: 10/BDIR
sending command idx=1 type=26 len=96
received frame len=103 chan=10 rssi=24 rssi_dbm=85
received frame len=109 chan=10 rssi=24 rssi_dbm=81
received frame len=109 chan=10 rssi=24 rssi_dbm=85
Scan of channel 2457 complete (10)
Scan completed (1, 1)
exit FW state 4
enter FW state 4
sending command idx=2 type=8 len=8
Scan request: index 2281 dwell 200/200/200
Scan 1 2.4GHz channels: 12/BDIR
sending command idx=3 type=26 len=96
received frame len=103 chan=12 rssi=24 rssi_dbm=79
received frame len=109 chan=12 rssi=24 rssi_dbm=79
Scan of channel 2467 complete (12)
Scan completed (1, 1)
exit FW state 4
enter FW state 4
sending command idx=4 type=8 len=8
received frame len=109 chan=12 rssi=24 rssi_dbm=79
Scan request: index 2282 dwell 200/200/200
Scan 1 2.4GHz channels: 14/BDIR
sending command idx=5 type=26 len=96
Scan of channel 2484 complete (14)
Scan completed (1, 1)
exit FW state 4
enter FW state 4
sending command idx=6 type=8 len=8
Scan request: index 2283 dwell 200/200/200
Scan 1 2.4GHz channels: 1/BDIR
sending command idx=7 type=26 len=96
Scan of channel 2412 complete (1)
Scan completed (1, 1)
exit FW state 4
enter FW state 4
sending command idx=8 type=8 len=8
Scan request: index 2284 dwell 200/200/200
Scan 1 2.4GHz channels: 6/BDIR
sending command idx=9 type=26 len=96
received frame len=103 chan=6 rssi=23 rssi_dbm=80
received frame len=122 chan=6 rssi=21 rssi_dbm=44
received frame len=109 chan=6 rssi=24 rssi_dbm=79
iwi_newstate: SCAN -> INIT flags 0x20
iwi_newstate: INIT -> INIT flags 0x0
WPA supplicant seems to start automatically, when I unload and load if_iwi.
This did work with 6.2 very nicely.
What else can I do?
Best Regards,
Rainer
More information about the freebsd-current
mailing list