Matthew Saltzman wrote:
On Wed, 1 Mar 2006, Charles Curley wrote:
I can't explain it, but I may have a less drastic work-around. I had a
similar glitch yesterday. I rmmoded the ipw2200 driver, and modprobed
it. It's been fine since.
I do have a lot of this:
Mar 1 20:25:51 dragon kernel: ipw2200: Firmware error detected.
Restarting.
Mar 1 20:25:51 dragon kernel: ipw2200: Sysfs 'error' log already
exists.
Mar 1 20:44:22 dragon kernel: ipw2200: Firmware error detected.
Restarting.
Mar 1 20:44:22 dragon kernel: ipw2200: Sysfs 'error' log already
exists.
I wonder if it's related to suspending to memory a lot.
I don't think so. It appears to be a driver or firmware issue. As a
workaround, try adding
options ipw2200 hwcrypto=0
to /etc/modprobe.conf. It seems to drastically reduce the number of
these errors.
If you are bold and want to try the latest drivers (which may fix the
porblem), see http://www.ces.clemson.edu/linux/fc2-ipw2200.shtml.
[quote]
* Wed Mar 1 2006 Dave Jones <davej@xxxxxxxxxx> [2.6.15-1.1833_FC4]
- 2.6.15.5
* Tue Feb 21 2006 Dave Jones <davej@xxxxxxxxxx>
- Add boot delay debug patch.
* Mon Feb 20 2006 Dave Jones <davej@xxxxxxxxxx>
- Make monitor mode work for ipw2200
- Add another mp3 player to the usb unusual device list. (#176584)
* Sun Feb 19 2006 Dave Jones <davej@xxxxxxxxxx>
- Bump minimum requirements for module-init-tools & udev
- Make 16C950 UARTs work.
* Thu Feb 16 2006 Dave Jones <davej@xxxxxxxxxx>
- Fix PMTU NAT bug.
* Thu Feb 16 2006 John W. Linville <linville@xxxxxxxxxx>
- Set ipw2200 hwcrypto option to 0 to avoid firmware restarts.
[/quote]
Some fixes in the latest stable kernel update for ipw2200 (including the hwcrypto=0). Try it out.
