NOTICE: What I thought were -20 kernel problems may not be. Today I discovered that the new 4GB RAM card I bought on 3/11 went belly up after an increasing number of severe problems. I am now back to the original 4GB (another chip coming from Amazon Friday!) and things are working well again.
The most recent kernel "-20", was a disaster for my installation. My average temperature rose by 10F and once while playing Minecraft it was shut down by a "temperature overrun" to 140F, even though this CPU has a max temp of 194F.
Also, I was noticing an accumulation of linux kernels and headers and such in /boot, starting with the "-8" right up to the latest, "-20". I decided to clean my kernel house.
The usual was is to run Synaptic and search on "linux-headers", then click on the little square above the first column to move all the green boxes (installed headers and kernels) to the top of the list. Then select the kernels and headers you want to remove. (In the past all one had to do was select the kernel and Synaptic would select the appropriate header, but not now). Click the apply button. Synaptic would remove the selected kernels and headers and then run "update-grub".
Not any more. My /boot/grub.cfg file still showed the now missing kernels as options to choose from. When I ran "sudo update-grup" the new grub.cfg file STILL contained them. I checked the /boot directory and the ones Synaptic told me were removed were actually all still there!
So, I manually removed them using Dolphin. I had to remove
abi-3,2,0-XX-generic
config-3.2.0-XX-generic
initrd.img-3.2.0-XX-generic
System.map-3.2.0-XX-generic
vmlinuz-3.2.0-XX-generic
for all of the kernels from XX=8 to XX=16, and XX=20.
THEN I ran "update-grub" and got a good grub file.
There was a time in the past, before grub and during the first grub incarnation, when all one had to do was manually edit a single file in /boot and arrange the kernels in the order you wanted them to appear. Grub "1" had "menu.lst". Grub-2 has, IMO, gone in the wrong direction. About the only way for Joe or Sally Sixpack to use it is to let the kernels pile up in /boot and let grub.cfg be controlled automatically, forcing them to manually select any but the latest automatically installed kernel. Removing old and/or unused kernels is not a job for Joe or Sally, and updating /etc/default/grub.cfg is almost too much to ask of Joe or Sally.
It's about time an app was created which listed all the kernels in /boot and allowed the user to re-arrange them, or mark the default boot kernel, or to remove stale kernels, and then have the app do all the work in the back ground with apt-get and update-grub.
The most recent kernel "-20", was a disaster for my installation. My average temperature rose by 10F and once while playing Minecraft it was shut down by a "temperature overrun" to 140F, even though this CPU has a max temp of 194F.
Also, I was noticing an accumulation of linux kernels and headers and such in /boot, starting with the "-8" right up to the latest, "-20". I decided to clean my kernel house.
The usual was is to run Synaptic and search on "linux-headers", then click on the little square above the first column to move all the green boxes (installed headers and kernels) to the top of the list. Then select the kernels and headers you want to remove. (In the past all one had to do was select the kernel and Synaptic would select the appropriate header, but not now). Click the apply button. Synaptic would remove the selected kernels and headers and then run "update-grub".
Not any more. My /boot/grub.cfg file still showed the now missing kernels as options to choose from. When I ran "sudo update-grup" the new grub.cfg file STILL contained them. I checked the /boot directory and the ones Synaptic told me were removed were actually all still there!
So, I manually removed them using Dolphin. I had to remove
abi-3,2,0-XX-generic
config-3.2.0-XX-generic
initrd.img-3.2.0-XX-generic
System.map-3.2.0-XX-generic
vmlinuz-3.2.0-XX-generic
for all of the kernels from XX=8 to XX=16, and XX=20.
THEN I ran "update-grub" and got a good grub file.
There was a time in the past, before grub and during the first grub incarnation, when all one had to do was manually edit a single file in /boot and arrange the kernels in the order you wanted them to appear. Grub "1" had "menu.lst". Grub-2 has, IMO, gone in the wrong direction. About the only way for Joe or Sally Sixpack to use it is to let the kernels pile up in /boot and let grub.cfg be controlled automatically, forcing them to manually select any but the latest automatically installed kernel. Removing old and/or unused kernels is not a job for Joe or Sally, and updating /etc/default/grub.cfg is almost too much to ask of Joe or Sally.
It's about time an app was created which listed all the kernels in /boot and allowed the user to re-arrange them, or mark the default boot kernel, or to remove stale kernels, and then have the app do all the work in the back ground with apt-get and update-grub.
Comment