Query re Bug #1048919 and kernels 2.6.32-x, now considered a duplicate of this one:
It'swonderful to hear that this problem is likely to disappear for the 3.2.x kernels. Should one hope that the fix will back-propagate to the 2.6.32-x kernels?
Also, as a result of this problem, I'm currently stuck having to manually select and boot from an older kernel. I managed to "patch up" my system for a while by manually running 'update-initramfs -u -k ' following each kernel update. That no longer works.
Can anyone suggest a "patch up" workaround for kernels 2.6.32-42and later?
Presumably which will need to be re-applied each time Update Manager installs a new kernel, at least until the fix for the installation makes it intoproduction.
Query re Bug #1048919 and kernels 2.6.32-x, now considered a duplicate of this one:
It'swonderful to hear that this problem is likely to disappear for the 3.2.x kernels. Should one hope that the fix will back-propagate to the 2.6.32-x kernels?
Also, as a result of this problem, I'm currently stuck having to manually select and boot from an older kernel. I managed to "patch up" my system for a while by manually running 'update-initramfs -u -k ' following each kernel update. That no longer works.
Can anyone suggest a "patch up" workaround for kernels 2.6.32-42and later?
Presumably which will need to be re-applied each time Update Manager installs a new kernel, at least until the fix for the installation makes it intoproduction.
Thanks...
Frank McKenney