"Damien Bergamini" <[EMAIL PROTECTED]> writes: > But the wpi(4) driver should reassociate immediately.
And it does, most of the time. For one reason or another, at semi-random intervals I get Jul 23 08:06:49 thingy /bsd: wpi0: fatal firmware error Jul 23 08:06:50 thingy /bsd: wpi0: timeout waiting for adapter to initialize Jul 23 08:06:50 thingy /bsd: wpi0: could not load firmware Less often now (I tend to run latest snapshots, too lazy to do real -current most times), but it still happens, and sometimes AFAICS this leads to loss of link if not complete deassociation. Usually fixable with a new ifconfig wpi0 up (mumble) && dhclient wpi0, though. I've seen this on all revs since I got the machine (Thinkpad R60) in October last. If I can help debug this I'd be more than happy to. - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
