[valtam]

Is anyone else having issues where the Kernel Removal tool in Lite Tweaks fails to see existing kernels for removal?

[penglezos]

Dear Jerry,

I have the same error!

Kind regards,
Panagiotis Englezos

[ralphy]

penglezos, do you have multiple (older kernels) listed under /usr/src  ??

Are you running a 32 bit or 64 bit version? Is it in a virtual machine?

[valtam]

Dear Jerry,

I have the same error!

Kind regards,
Panagiotis Englezos

Please open a terminal and paste here the output of:

Code:

dpkg --list | grep linux-image

and:

Code:

uname -a

[trinidad]

I have been faithfully updating and removing old kernels without any issues at all on several machines both 32bit and 64bit. None are VMs. Perhaps the VM keeps logging you into old kernels, or grub retains them in VM thus the error. I still use gnome boxes for VM's, but do not run it in LL, and have never run LL as a g-box or VM from deb.

TC

[ralphy]

Perhaps it has to do with the fact that a new kernel is been installed but the machine hasn't been rebooted, hence it can't list the kernel that is in use.

I cannot replicate this issue in either version x32 or x64. I've added a check in Install Updates to recommend users to restart when/if needed (such as in the case of a new kernel install)

[valtam]

Perhaps it has to do with the fact that a new kernel is been installed but the machine hasn't been rebooted, hence it can't list the kernel that is in use.

I cannot replicate this issue in either version x32 or x64. I've added a check in Install Updates to recommend users to restart when/if needed (such as in the case of a new kernel install)

That is tasty :)

I reboot my machines, so that's not the issue here.

Sent from my Phone using Tapatalk

[trinidad]

Obvious praxis would be install updates, reboot, then use the tweaks kernel remover. I wonder if the physical system and the VM both have to reboot; say for instance, if the physical system is running on an older kernel, and perhaps the VM software itself has dependencies that would break with the newer kernel even though the VM can run the new kernel just fine. PCI cards are an instance that used to cause problems between physical and virtualized hardware running different kernels. It has to be a VM software thing. Kernel remover works flawlessly on the six physical systems I have had at hand here. The only other thing it could be is an underrun problem of some kind that causes a default boot to the old kernel, but that is highly unlikely on your big machine, the thing is when things don't change after updates it can be because of underruns during bootup.

TC

[firenice03]

So I went a lil crazy and checked both LL machines - some differences but I ran the gamut and posted current listed then tried a removal...

Heres the 32-bit Mini - It started with 3.0 and upgraded to 3.2...
Lite Tweaks/Kernel Cleaner shows extra kernels?? /src shows 21, 51 and 53 (in use); cleaner shows additional 34,45 and 47..??
I think I have removed these in past and have rebooted several times for sure..

Code:

dad@TRCD-LLMini:~$ uname -a
Linux TRCD-LLMini 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:58:04 UTC 2016 i686 i686 i686 GNU/Linux

 

I'll remove to see if any errors..
*Removed the .34 kernel, cleared informed removed...



The Boys 64-bit shows one to one...
Boys 64-bit 3.2 installed..

Code:

boys@TRCD-LL_Boys:~$ uname -a
Linux TRCD-LL_Boys 4.8.0-linuxlite #1 SMP Mon Oct 3 13:28:39 NZDT 2016 x86_64 x86_64 x86_64 GNU/Linux

Upon removing the older 4.4 kernels - cleaner reported error..

 


After reboot it does show those kernels removed:

 

[valtam]

@trinidad - interesting hypothesis's, I'll look into those.