> On Sun, 2004-11-14 at 21:32 +0000, Simon Michelson wrote: > > > > The only way I've found to fix it so far is to rmmod prism54 && modprobe > > prism54. Note that just taking out and putting > > in the card doesn't work without doing the "rmmod prism54". Since writing that I've found that that does sometimes work and sometimes doesn't. Also rmmod'ing and modprobe'ing the module only sometimes works. On Sun, Nov 14, 2004 at 05:15:33PM -0600, Kevin Freeman wrote: > I do not use suspend/resume but occasionally run into the same bug. And > I "solve" it in the same manner that you posted. The bugzilla comment > below indicates a workaround - I have not encountered the bug since the > workaround has been posted. > > http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=56#c14 Thanks for the pointer, however, doing an arping actually made the situation worse because the system got into a state where you couldn't unload the prism54 module. (rmmod hangs in kernel space and can't be killed). When I tried to reboot, I had to give it a hard power down because it kept spewing the same message, something about eth1's usage count being 7. Does anyone know if using ndiswrapper with this card is likely to work any better than using the native linux drivers? The way I use this laptop is to wake it up for brief periods to quickly look up a bit of information. If I can't reliably suspend and resume it I won't bother using it at all, so this bug is quite annoying. Can anyone recommend a card that they know works with suspending and resuming under FC3? Preferably one with the firmware on board.. I was quite naive in my first attempt at buying a WLAN card, I just saw the 3Com brand and incorrectly assumed it would be a high quality product with good linux support. Simon.
