DJA wrote:
Ralph Shumaker wrote:
What can I do about this error message?
ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command.

I just now freshly installed Fedora 9 onto a laptop for someone.

It concerns me that dmesg is getting a repeating message approximately 6 times each minute. The message appeared 54 times over 10 minutes, then 68 times over the next 10 minutes, and most recently 59 times over the final 10 minutes. So it is not consistent with precision, but generally.

The ipw2200 messages have 4 lines before all the incessant repeats:
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection
ipw2200: Detected geography ZZA (11.802.11bg channels, 13 802.11a channels)

And *now* when I run 'dmesg | grep -i "ipw" | grep -v "Failed to send ", I also get 6 of these messages:
ipw2200: Firmware error detected.  Restarting.

The 6 lines are interspersed among the 539 lines of the "Failed to send " message, tho in a very inconsistent manner.

First appears the 4 ipw2200 lines about the interface.
Then come about 426 of "Failed to send" followed by 1 line of "Restarting". Then come about 124 of "Failed to send" followed by 2 lines of "Restarting".
Then 1 and 1.
Then 1 and 2.
Then 76 and 1.
Then 1 and 2.
Then 2 and 1.
Then 1 and 1.
Then 18 and 1.
Then 1 and 3.
Then 15 and 4.
Then 1 and 1.
Then 8.

Very inconsistent.

I don't know what to do about the laptop wireless interface beyond this point.

I'm considering pulling my dsl ethernet line from my PC to plug into the laptop eth0 to verify that it can access the internet that way. But if the laptop owner has a wireless AP, he should be able to go that way. With these 2 error messages repeating this way, something is obviously amiss, and I have *zero* experience in wireless troubleshooting.

I don't have a wireless AP here. The wireless on the laptop is eth1. It also has eth0, which I'm sure is the ethernet plug in the back.

You need to download and install firmware for the IPW2200 from here:

http://ipw2200.sourceforge.net/firmware.php or

directly from Intel's site.

Also make sure you have wpa_supplicant installed (which should be in the default installation).

How do I check for that? Something by that name seems present. I type "wpa" and hit TAB+TAB, and wpa_supplicant is one of three things that appear.

As for downloading, I guess I'm going to have to try to connect my internet to it. I'll try that now. ... Immediate recognition! Kewl!



Long story short:
The latest files I downloaded are identical to the ones already installed.



Short story long:
The download page has multiple selections according to which version of ipw2200 driver is being used. dmesg no longer has that info in its history and I wanted to be sure I didn't make a typo above when I recreated the messages, so I rebooted. But since rebooting, the error messages haven't come back. It's been back up for about 21 minutes now (according to uptime).

I went ahead and downloaded the appropriate package, and unpacked it. I didn't see the README or INSTALL instruction files that the license told me to look for. But I'm not sure I'm going to need it. I don't know how long it was up the first time before it started getting the error, but so far the error is not occurring this time, even after several hours. I guess I'll just keep checking back.

Next morning, the error message has returned, at the rate of about 3 per minute (about half as much as before).

I poked around on the website and found a link for INSTALL. After reading through the mountain of things it says to do, I finally read that the .fw files I downloaded must be copied (after doing all the other things) into /lib/firmware. Just for reference, I ls that directory and notice that the dates (2006-03-07) and sizes of the downloaded .fw files are identical. Just for good measure, I diff each of the three files (even though the INSTALL webpage says there are supposed to be three others) and no differences are reported back.

While I was doing all that, I had yum update bringing the system up to date. I doubt that yum did any updates using files that are 30 months old. When yum finished (late last night), I checked and found no ipw error messages, so went to bed.

This morning, the ipw error messages were back. Well, not "message*s*". Just "ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command." was back. The "ipw2200: Firmware error detected. Restarting." message has not appeared.

Any ideas?



--
Recent events have proved that the paper-money system of this country may be used as an engine and that those who desire to engross all power in the hands of the few and to govern by corruption or force are aware of its power and are prepared to employ it. Your banks now furnish your only circulating medium and money is plenty or scarce according to the quantity of notes issued by them.
--Andrew Jackson


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to