Ralph Shumaker wrote:
Ralph Shumaker 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.
As suggested, I got the latest firmware for the ipw2200, only to
discover that the newest firmware files are identical to the ones
installed.
What should I check next?
# ifconfig
eth0 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet6 addr: xxxx::xxx:xxxx:xxxx:xxxx/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 METRIC:1
RX packets:1104477 errors:0 dropped:0 overruns:0 frame:0
TX packets:816177 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1597740002 (1.4 GiB) TX bytes:61188242 (58.3 MiB)
Interrupt:16
eth1 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx
inet6 addr: xxxx::xxx:xxxx:xxxx:xxxx/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 METRIC:1
RX packets:0 errors:10 dropped:10 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:56 (56.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Base address:0xe000 Memory:dfcff000-dfcfffff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 METRIC:1
RX packets:5586 errors:0 dropped:0 overruns:0 frame:0
TX packets:5586 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:0
RX bytes:292504 (285.6 KiB) TX bytes:292504 (285.6 KiB)
# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 unassociated ESSID:off/any
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
pan0 no wireless extensions.
I'm hoping to catch it as it starts. I rebooted, and at a virtual
terminal, entered this (after searching thru old emails for the pieces
needed for the formula):
$ while true; do (dmesg | grep ipw ; /sbin/iwconfig eth1 ;
/sbin/ifconfig eth1 ; uptime ; sleep 60); done
So far, nothing is changing except the RX and TX packet numbers on
ifconfig. RX jumped up 566 and TX jumped up 55 from the previous
minute. And now, 670 and 56, respectively. Now, 644 and 55. Now,
604 and 55.
I don't have wireless, so there must be something in the vicinity.
The error messages have begun at uptime between 54 and 55 minutes. RX
packets went from 35201 to 26 and TX from 2962 to 2 during which 2 error
messages appeared.
The next minute gave one more error message and RX and TX went to 0 and 1.
The next minute gave no more error messages and RX and TX went to 698 and 5.
Next, no error message, RX and TX are 1463 and 105.
Still no new error message, RX and TX are 4529 and 326. All else
appears to remain the same.
Between uptime 1:04 and 1:05, got 2 new error messages. RX and TX got
dropped back down to low levels. But nothing else appears to have changed.
Got 3 more errors. uptime 1:06
I know that uptime has little to do with anything. But I wanted to pay
attention to that since last night it was up for several hours before
even a single error appeared.
Every time a new error message appears, RX and TX get reset on eth1.
But so far, still no errors being reported by ifconfig. And still none
of the error claiming a firmware failure. (I modified the script some.)
--
We shall have World Government, whether or not we like it. The only
question is whether World Government will be achieved by conquest or
consent.
--Paul Warburg CFR (Council on Foreign Relations) and architect of the
Federal Reserve System in an address to the US Senate. 1950-02-17
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
