Comment 6 for bug 182473

Confirmed with the stock Gutsy kernel ( 2.6.22-14-generic ) on the same motherboard using the same driver. However I'm using WPA2.

Modprobing the driver in and out does seem to fix it for me, at least at the moment.

I don't get anything printed to dmesg except "wlan0: deauthenticate(reason=3)"; and this is sometimes up to 5 minutes after the connection has dropped. As with the original bug reporter, the system still thinks it's connected.

I have included my current dmesg. Some time before 9987, the connection went down. At 10578 I reloaded the correct driver.