Comment 16 for bug 288148

I always read the change log for the Kernel at least before I apply an update and thus I knew my ATH5K support would disappear. But I've long felt that update-manager or some other tool should preserve the last few changelogs locally so that when you applied an update and something suddenly stopped working you had a way to go back through your locally kept logs to try to determine the root cause.

I think the note here should have been much more explanatory. Something to the effect of "You WILL lose wireless connectivity and must take the following steps to restore it"

For my personal situation, merely installing the LBM package did not instantly restore connectivity. While I'm still troubleshooting and expect I'll eventually get either that module, MadWiFi or NdisWrapper to work, I can see that for many people, especially who only have wireless connectivity on their laptop/netbook that this could be terribly frustrating.

That said, all of you should be mindful that you are currently running a pre-release version of Intrepid, that this is not GA software and that you have put yourself in a unique situation by electing to use this distribution. The goal for everybody is to have stable software in six more days. I've experienced the performance problems with the ATH5K module that this thread are addressing and agree that stability for release must be a paramount goal.