I've tried the current Jaunty, and the problem is not resolved. It's exactly the same as before.
As far as Sitsofe's report, for all we know he may not have seen the problem on Intrepid either. It's not really good evidence that anything has been resolved.
I believe the problem is related to the type of network I'm on, which has multiple access points on the same SSID (repeaters). The driver seems to get confused by the process of switching from one of the access points to another based on which one has the best signal. The madwifi and ndiswrapper drivers can handle this (and will switch properly from one access point to another), but the ath5k driver somehow gets bogged down and confused and leaves the network in a disconnected state for minutes at a time.
I've tried the current Jaunty, and the problem is not resolved. It's exactly the same as before.
As far as Sitsofe's report, for all we know he may not have seen the problem on Intrepid either. It's not really good evidence that anything has been resolved.
I believe the problem is related to the type of network I'm on, which has multiple access points on the same SSID (repeaters). The driver seems to get confused by the process of switching from one of the access points to another based on which one has the best signal. The madwifi and ndiswrapper drivers can handle this (and will switch properly from one access point to another), but the ath5k driver somehow gets bogged down and confused and leaves the network in a disconnected state for minutes at a time.