James G. Sack (jim) wrote:
Ralph Shumaker wrote:
James G. Sack (jim) wrote:
Ralph Shumaker wrote:
..
<my funny tbird behavior volunteers information, once again>
Eh, *I* did not write that. :)
..
Whoops. I made the changes I thought necessary from ifcfg-eth0 to make
it somewhat more fit for the eth1 interface, but then forgot to include
the suggested addition. Making adjustments now. I left in the HWADDR=
line since I knew the address to plug in. But to no avail. After
adjusting, then rebooting, it comes back up and promptly has 12 of the
Failed error messages within the first 3 minutes. Perhaps I should
remove the HWADDR after all?
I believe the HWADDR line should cause no problem whether absent or
present (and correct).
Knoppix currently has uptime 11:40 with 0 ipw errors. Tho I do find it
a bit odd that in nearly 12 hours, there have only been 6 RX packets and
3 TX packets with 394448 RX bytes and 5883 TX bytes. Oops, scratch
that, now only 0 RX packets with 1 TX packets (while bytes RX and TX are
unchanged).
Apparently, there are ipw2200 problems that are not being reported under
dmesg in Knoppix.
Well, now Knoppix has an uptime of , 12 occurrences of "ipw2200:
Firmware error detected. Restarting." and has since at least as far
back as about 45 minutes ago (where scrolling hits its limit). It still
has 0 occurrences of "ipw2200: Failed to send ..." Maybe the "Firmware
error occurred when I grabbed a web page. Momentarily, eth1 has an
ESSID:off/any, so it may be that the signal is currently too weak (or
off, which is a subset of too weak).
--
There is no security without privacy. And liberty requires both security
and privacy.
--Bruce Schneier
--
KPLUG-List@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
