Comment 108 for bug 346691

As one of the regular users who's been KO'ed by this bug (and who's pretty much frothing that this bug was *known* prior to the final release and nobody bothered to put out a huge general HEADS UP about it ... but that's another whole issue) --

could somebody post easy instructions on how to install the kernel that seems to solve the problem? At least then us poor schmoes could get some use out of our jaunty installs. I'll be glad to put the workaround in the "known jaunty bugs and workarounds" sticky on ubuntuforums.

For instance, would something along these lines be right:
[CODE]wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.29.3/
sudo dpkg -i linux-image-2.6.29-and-then-what-goes-here??.deb
sudo dpkg -i linux-headers-2.6.29-and-then-what-goes-here??.deb linux-headers-2.6.29-and-then-what-goes-here??_all.deb[/CODE]

(I gather the 29 kernel would be the preferred solution? Yes? No?)

Which commands -- or which further commands -- would one need?

I understand that this is not is not standard practice, yadda, yadda, yadda. Having constant filesystem corruption is worse, though, so please give us a fix!