Re: ipw2200 sometimes works, mostly not
Digby Tarvin wrote:
> I am using Etch and the built in version of the ipw2200 driver on my
> Fujitsu Lifebook with mixed success. It usally works immediately
> after boot, but I get frequent console error messages and after a few
> hours (about 1-24) it stops working altogether and I reboot to restore
> things.
Weird. FWIW, I'm using ipw2200, ieee80211, ieee80211_crypt, from binary
kernel 2.6.18 (specifically, linux-image-2.6.18-1-686 from sid---though
I'm sure 2.6.17 also worked). I mean, I didn't build anything from
source. This on a Thinkpad T42, Intel PRO/Wireless 2200BG. I believe
this is very similar to the hardware of Johannes, the original poster.
I see similar log messages:
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2kmq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels)
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation
<jketreno@linux.intel.com>
I even see the "receive_packet failed on wifi: Network is down",
sometimes (I renamed the interface as "wifi", rather than "eth*").
My setup works perfectly, though. I even have monitor mode.
The firmware is from http://ipw2200.sourceforge.net/ , of course. I'm
afraid I don't remember precisely which version I have, but I believe
it's the latest available, v3.0. Here are the md5sums:
f0216818744e31f769098c7310688e97 /lib/firmware/ipw2200-bss.fw
8bd8a347b63aa732eb36d6b00ab660b4 /lib/firmware/ipw2200-ibss.fw
d57c836007d5245522ddbb030e21749c /lib/firmware/ipw2200-sniffer.fw
> I have also noticed that if my boot is delayed for any reason (such
> as a disk check being forced) the driver frequently fails to work
> at all when booting finishes.
I do recall having a similar issue, some time ago, back when I had to
build the modules from source. It was infrequent, though. Unloading
and reloading the modules fixed that.
Anyway, hope this helps.
--
César Rincón
Enlaces Tecnológicos
Guadalajara, México
Reply to: