Siduction Forum

Siduction Forum => Software - Support => Topic started by: tranquil on 2022/11/28, 00:15:16

Title: [SOLVED] Old Kernel Not Marked for Removal...Why?
Post by: tranquil on 2022/11/28, 00:15:16
Note:  I'm using stock Debian Unstable, not Siduction.

I went to remove the prior two kernel versions today and I noticed that linux-image-5.14.0-3-amd is still on my system, but it's not marked for auto-removal.

Code: [Select]
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.0.0-4-amd64
Found initrd image: /boot/initrd.img-6.0.0-4-amd64
Found linux image: /boot/vmlinuz-6.0.0-3-amd64
Found initrd image: /boot/initrd.img-6.0.0-3-amd64
Found linux image: /boot/vmlinuz-5.14.0-3-amd64
Found initrd image: /boot/initrd.img-5.14.0-3-amd64

Is it okay to just remove it using:

Code: [Select]
sudo apt purge
Any idea why linux-image-5.14.0-3-amd is not being flagged for auto-removal?
Title: Re: Old Kernel Not Marked for Removal...Why?
Post by: unklarer on 2022/11/28, 09:22:48
This kernel you have

- not installed with apt
- installed by hand

Yes, you also have to uninstall it by hand.   ;)
Title: Re: Old Kernel Not Marked for Removal...Why?
Post by: Mister00X on 2022/11/28, 18:11:29
What does
Code: [Select]
apt-mark showhold and
Code: [Select]
apt-mark showmanual linux-image-5.14.0-3-amd64 say?


 btw linux-image-5.14.0-3-amd64 is not a siduction kernel but seems to be a debian one because its missing "siduction" in its name.
Title: Re: Old Kernel Not Marked for Removal...Why?
Post by: towo on 2022/11/28, 19:31:05
Quote
btw linux-image-5.14.0-3-amd64 is not a siduction kernel but seems to be a debian one because its missing "siduction" in its name.

Quote
Note:  I'm using stock Debian Unstable, not Siduction.
Title: Re: Old Kernel Not Marked for Removal...Why?
Post by: Mister00X on 2022/11/28, 19:44:07
Quote
btw linux-image-5.14.0-3-amd64 is not a siduction kernel but seems to be a debian one because its missing "siduction" in its name.

Quote
Note:  I'm using stock Debian Unstable, not Siduction.

Apparently I skipped that line. Mea culpa.
Title: Re: Old Kernel Not Marked for Removal...Why?
Post by: tranquil on 2022/11/29, 10:38:41
This kernel you have

- not installed with apt
- installed by hand

Yes, you also have to uninstall it by hand.   ;)

No, I don't install kernels by hand.
Title: Re: Old Kernel Not Marked for Removal...Why?
Post by: tranquil on 2022/11/29, 10:41:00
What does
Code: [Select]
apt-mark showhold and
Code: [Select]
apt-mark showmanual linux-image-5.14.0-3-amd64 say?
The kernel is not being held. I'll have to log into the Debian Unstable install on my laptop later today and try the
Code: [Select]
apt-mark showmanual command. However, I did not manually install the kernel. I never manually install kernels.

btw linux-image-5.14.0-3-amd64 is not a siduction kernel but seems to be a debian one because its missing "siduction" in its name.

Correct...I use the Siduction forums because I've learned a lot from the members about using Debian Unstable.

I also run Debian Unstable on my desktop and the kernel doesn't exist there; really weird. I'm going to attempt to purge the kernel from my laptop.
Title: Re: Old Kernel Not Marked for Removal...Why?
Post by: unklarer on 2022/11/29, 11:20:04


No, I don't install kernels by hand.

synaptic etc. ?
Title: Re: Old Kernel Not Marked for Removal...Why?
Post by: tranquil on 2022/11/30, 04:45:54


No, I don't install kernels by hand.

synaptic etc. ?
I never, ever use Synaptic to perform installs or removals. I learned about not doing that very long ago when I became interested in Ubuntu.
Title: Re: Old Kernel Not Marked for Removal...Why?
Post by: tranquil on 2022/11/30, 04:47:35
What does
Code: [Select]
apt-mark showhold and
Code: [Select]
apt-mark showmanual linux-image-5.14.0-3-amd64 say?

Output of apt-mark showmanual linux-image-5.14.0-3-amd64:

Code: [Select]
linux-image-5.14.0-3-amd64
So I guess that means it was manually installed. How, I have no idea. I successfully purged the kernel from my laptop. Thank you to everyone who contributed to this thread.