Hi.
I have an interesting problem here.
My intel pro wireless 2200 NIC doesn't work anymore. Yesterday it did, but not today (I didn't do anything special, so that it could go wrong).
When I boot up the following message comes: I'm using Debian Lenny on an i686 machine.
I tried to reinstall all the firmwares and kernel but still no luck.
I did run depmod and then try to reload the ipw2200 module, but the same message comes all the time.

Oh, one more thing. lspci does list the card, but not hwinfo --network.

What is ucode and -62? Any ideas? I already checked the forums and found that ipw doesn't work when ndiswrapper is loaded. Well, I don't have it loaded. What happend?

Thanks.

The only thing i can think of is to try downloading the firmware from http://ipw2200.sourceforge.net/firmware.php (probably 3.0 or 3.1 is what you'd want), extract the contents of the file to /var/firmware and reboot the system and see if that works...

As far as I know, the package "firmware-ipw2x00" was recently updated. Is it installed on your system? Try removing it and follow camh instructions, that should work...

Yes, I'm using the firmware-ipw2x00 package. If camh's method works, than I think I'll check if there are any bug reports for this updated firmware. I'll post back if the firmware upgrade did work or not.
Thanks for your suggestions.

One thing to look at...usually when hardware works one day and not the next, was any new software or updates to software done? I had a game update that knocked out a USB harddrive and had no clue how to fix it until the next update came out which corrected it.
Alan

Well, I actually did make an update on the previous day. I updated my wine packages from lenny version to wine-repo version. Nothing else on that day. Could it be that wine messes up firmware (sounds a bit wierd to me)?

Hi.
You won't believe it!!! The problem just disappeared! All by itself! I just started up my computer to fix the problem, but there was no problem anymore! Now, I'm really confused. How is it possible that one day, a really weird and unexplainable problem just pops up from nowhere and the very next day it just disappears? Was it a joke of some programmer? Or the firmware just decided not to work on august 2? Who knows... I guess this will remain a mystery...

EDIT: I don't know if I should mark this thread solved, because I have no idea if the problem was really solved. If it was solved (it seems), than I don't know how (I didn't do anything. Really. Nothing.), thus marking this thread solved could confuse people looking for solutions.

I have the same card I believe. And I have seen it fail (with some firmware error) - but that was some time ago.
A newer version would not work but the older did. Now the most recent version (3.1) works o.k.
And I have only seen it fail when I had a connection to an ad-hoc network. Shutting down the card, unloading and reloading the module would fix the situation, as well as a reboot..., but only temporarily.
Since then I try not to use ad-hoc mode since it appears to be still problematic. No real known reason or solution...sorry.

Hello again!
I answer to your question, I do not think it was a hardware failure but could have been something in the software update. As for now, if it is working, I would say don't mess with it, but just keep that update in mind for future reference. And I would not recommend listing this problem as solved unless there is a definite fix that repaired the problem...glitches do happen and the original problem may have just been a "hick-up" in the system.

Alan