James G. Sack (jim) wrote:
Ralph Shumaker wrote:
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.)
Did packet counts go down without unload/reload of any wireless modules
or rebooting?
Well, obviously rebooting will reset the numbers, so I don't think
that's what you're asking.
I've been watching via:
$ while true; do (dmesg | grep ipw | wc ; dmesg | grep Failed | wc ;
dmesg | grep Restarting | wc ; iwconfig eth1 ; ifconfig eth1 ; uptime ;
sleep 60); done
Every time a new "Failed" error message appears, RX and TX packet counts
reset back to 0. So far, no other changes have appeared, but neither
have any error messages about a firmware failure. Presently, the uptime
is 2:21, with 79 "Failed ..." messages and 0 "... Restarting." messages.
Ummm, that doesn't seem right at all (I would say it SB impossible, but..)
SB? (Should Be?)
Do you have a live-CD that you could try running the laptop from, to see
if that makes any difference?
Yeah, I have Knoppix DVD fixated 2008-03-26. I'm currently using it to
perform a memtest on another laptop which came to me complaining of
freezing up (WhenDoze). Fortunately, memtest is not selfish and
promptly surrendered the DVD upon request.
On googling your error message I did run across suggestions of putting
WIRELESS_AP_SCANMODE='2'
in your etc/sysconfig/network-scrips/ifcfg-eth1
$ ls /etc/sysconfig/network-scripts/ifcfg-* gives ifcfg-eth0 and ifcfg-lo.
Should I copy ifcfg-eth0 to ifcfg-eth1 and just drop the first line
(which looks like a commented-out description of eth0) and adjust the
DEVICE line and the HWADDR line to fit? Then add that line?
$ cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=xx:xx:xx:xx:xx:xx
ONBOOT=yes
DHCP_HOSTNAME=localhost.localdomain
NM_CONTROLLED=
And another suggestion to turn off hardware crypto via a file (create if
necessary), etc/modprobe.d/ipw2200, as follows:
options ipw2200 hwcrypto=0
(If there are already other options in a line like this, just append the
hwcrypto=0 part.
The file did not exist. I made it as directed. How do I make it take
effect without rebooting?
I started with your second suggestion (since it seemed easier), but did
the first one also, making guesses. So far, the last error occurred
about 10 minutes after creating the file in the modprobe.d directory.
But that was about the time I was playing with the modprobe command to
try to invoke the change. Shortly afterward, I created the ifcfg-eth1
file with best-guess changes. So I don't really know what caused the
error messages to stop (or even if they have indeed stopped). But
scrolling back up, there was one place where no new error messages
occurred for at least 20 minutes that had absolutely nothing to do with
me. From 22:58 to now (23:25) and counting, there have been no new
error messages. I created /etc/modprobe.d/ipw2200 at 22:43 and
/etc/sysconfig/network-scripts/ifcfg-eth1 at about 23:03 or so, with
modifications saved by 23:13.
By 01:18, more of the error appears. :(
So I rebooted. :)
Immediately, the error starts occurring. ~x(
I really don't understand what the messages really mean, so I'm just
guessing. Scan mode has something(?) to do with APs that don't broadcast
(or ..), so conceivably that might fit your environment.
Hey, sometimes I make guesses too. No worries. Besides, this is a
fresh install. He had no problem with me wiping XP away from the laptop
he bought from someone. The XP was useless to him because the password
was unknown. So I can mess it up and just blow it away and install again.
--
The refusal of King George III to allow the colonies to operate an
honest money system, which freed the ordinary man from the clutches of
the money manipulators was probably the prime cause of the revolution.
--Benjamin Franklin
--
KPLUG-List@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
