Re: iwi0 firmware error on Dell Inspiron 6000 w/ Intel PRO/Wireless 2200BG

On Thursday 25 October 2007 19:54:17 Sam Leffler wrote:
> Stefan Ehmann wrote:
> > On Thursday 25 October 2007 18:28:47 pluknet wrote:
> >> On 25/10/2007, Guy Helmer <ghelmer_at_palisadesys.com> wrote:
> >>> I just upgraded a laptop to FreeBSD RELENG_7 checked out on 20071016.
> >>> Previously, iwi0 had worked OK under FreeBSD 6.2.  After updating to 7,
> >>> though, iwi0 reports "firmware error" and nothing more happens.  I have
> >>> set legal.intel_iwi.license_ack=1 in /boot/loader.conf.  wpa_supplicant
> >>> and dhclient are running with the same configurations that worked under
> >>> FreeBSD 6.  I'm using the GENERIC kernel with SCHED_ULE instead of
> >>> SCHED_4BSD, and the loaded modules are:
> >>>
> >>> Id Refs Address    Size     Name
> >>>  1   23 0xc0400000 8d0750   kernel
> >>>  2    1 0xc0cd1000 111b8    geom_eli.ko
> >>>  3    2 0xc0ce3000 25ff8    crypto.ko
> >>>  4    2 0xc0d09000 ab40     zlib.ko
> >>>  5    1 0xc0d14000 6e48     snd_ich.ko
> >>>  6    2 0xc0d1b000 4a52c    sound.ko
> >>>  7    1 0xc0d66000 69164    acpi.ko
> >>> 10    1 0xc32fb000 22000    linux.ko
> >>> 11    1 0xc3595000 21000    radeon.ko
> >>> 12    1 0xc35b6000 f000     drm.ko
> >>> 13    1 0xc31ff000 f000     if_iwi.ko
> >>> 14    1 0xc3e4f000 30000    iwi_bss.ko
> >>>
> >>> ifconfig iwi0 reports:
> >>>
> >>> iwi0: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
> >>>         ether 00:12:f0:12:1c:24
> >>>         inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
> >>>         media: IEEE 802.11 Wireless Ethernet autoselect
> >>>         status: no carrier
> >>>         ssid "" channel 8 (2447 Mhz 11g)
> >>>         authmode WPA1+WPA2/802.11i privacy ON deftxkey 1 txpowmax 100
> >>>         bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250
> >>>         roam:rssi11g 14 roam:rate11g 5 protmode CTS roaming MANUAL
> >>> bintval 100
> >>>
> >>> I've tried setting debug.iwi=1, and the kernel messages regarding iwi0
> >>> are:
> >>>
> >>> Oct 25 08:09:11 aquarius kernel: iwi0: <Intel(R) PRO/Wireless 2200BG>
> >>> mem 0xdfcfd000-0xdfcfdfff irq 17 at device 3.0 on pci3 Oct 25 08:09:11
> >>> aquarius kernel: iwi0: Ethernet address: 00:12:f0:12:1c:24 Oct 25
> >>> 08:09:11 aquarius kernel: iwi0: [ITHREAD]
> >>> Oct 25 08:09:14 aquarius kernel: iwi0: firmware error
> >>> Oct 25 08:10:17 aquarius kernel: iwi_newstate: SCAN -> INIT flags 0x0
> >>> Oct 25 08:10:31 aquarius kernel: iwi_newstate: INIT -> INIT flags 0x0
> >>> Oct 25 08:10:31 aquarius kernel: iwi_newstate: INIT -> SCAN flags 0x1
> >>> Oct 25 08:10:57 aquarius kernel: iwi_newstate: SCAN -> SCAN flags 0x1
> >>> Oct 25 08:10:57 aquarius kernel: iwi_newstate: SCAN -> SCAN flags 0x1
> >>>
> >>> Any ideas?
> >>>
> >>> Guy
> >>>
> >>> --
> >>> Guy Helmer, Ph.D.
> >>> Chief System Architect
> >>> Palisade Systems, Inc.
> >>
> >> Me too.
> >> (It works in authmode OPEN though, see my case on
> >> http://lists.freebsd.org/pipermail/freebsd-current/2007-August/076397.ht
> >>ml)
> >
> > On my notebook, I get similar errors most of the time. The problems
> > started some months ago.
> >
> > If I don't configure iwi0 via /etc/rc.conf, I can get WPA working
> > something like this:
> >
> > ifconfig iwi0 up
> > wpa_supplicant -d -i iwi0 -c /etc/wpa_supplicant.conf
> > dhclient iwi0
> >
> > IIRC it worked most of the time via /etc/rc.conf if I disabled
> > WITNESS/INVARIANTS. Haven't been using the notebook too much lately, so
> > I'm not sure if this is still true.
>
> 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.

I upgraded to a fresh CURRENT.

Most of the time it works during startup. I couldn't reproduce the firmware 
error message with debug.iwi enabled.

What used to work and now causes the firmware error message is when I 
kldunload if_iwi. This used to work some time ago, e.g. iwi was automatically 
reloaded and successfully associated. (I use this for suspend/resume)

I only get wpa_supplicant to work again if I do ifconfig iwi down/up.

Here's the log
http://stud4.tuwien.ac.at/~e0125637/fbsd/iwi.log