How can I completely remove the LTS kernel?

Hello.

I am wondering if anyone knows how to entirely remove the LTS kernel and all traces or files associated with it? I only want to keep the mainline kernel. Thanks in advance.

sudo pacman -Rs linux-lts linux-lts-headers

in -Rs R for removal, s to remove dependencies provided that they are not required by other packages.
-Rc would remove dependencies even if they were needed by others.

After running

# pacman -Rs

Finish it off with

sudo grub-mkconfig -o /boot/grub/grub.cfg

This rebuilds the grub configuration so that you won’t see the LTS option anymore.

That isn’t quite right.

-Rs packagename removes packages that packagename has a dependency on.

-Rc packagename removes packages that depend on packagename.

The difference is the direction of the dependency, not if the packages are needed or not.

Also, -Rs will remove optional dependencies of other packages.

1 Like

How about just installing EndeavourOS’ own akm

yay -S akm

and use GUI to manage kernels?

The EnOS team may have made this ISO and a few tools to make installing and maintaining Arch easier/convenient, but it’s still a terminal-centric distro. Learning how to do things (with actual commands) is encouraged.

But yes, this is an option for the OP. :+1:

3 Likes

I agree. But learning should be done in small steps. Messing with Kernels manually is not something that should be done at first grade (especially when it’s learning from the community and not from a verified Wiki).

My very first distro required me to recompile the kernel to get a CDROM to work. The same CDROM I installed the OS from. I learned then that Linux isn’t First Grade its College and more importantly its your lab class.

Obviously We have come a long way since those early days but Linux is not for the faint of heart.

I should mention I never was successful in recompiling the Kernel as I didn’t understand what that meant back then and I’m not a programmer.

Thanks for explanation. But in Arch Wiki it’s seems incomplete https://wiki.archlinux.org/title/Pacman/Rosetta

Thanks. Seems I have misunderstood notion on Pacman manpage about these two, with -Rs "(A) they are not required by other packages; and (B) they were not explicitly installed by the user. " and -Rc "Remove all target packages, as well as all packages that depend on one or more target packages. This operation is recursive and must be used with care, since it can remove many potentially needed packages. "

So, what you’re saying is the Arch wiki is easier to follow than this forum? Because it’s not.

Often times I’ll be reading the wiki and just think, “These people really don’t want newbies to use Arch.”. But when I do a general web search for the same thing and find some forum, the explanation is often times plain as day.

As you said, we’ve come a long way, and only certain distros aren’t for the faint of heart. Linux, in general, is for everyone now.

That was never the problem the problem is Everyone is not ready for Linux

1 Like

I am not sure if you think “Linux is not for the faint of heart” and “Everyone is not ready for Linux” is vastly different. It’s the same thing in different words and a different focus.


“Linux is not for the faint of heart”
→ Linux isn’t for people who like it easy.


“Everyone is not ready for Linux”
→ Regular people are not ready to use Linux. (You may substitute “regular people” for “the general public” if that floats your boat)


Not sure about anyone else, but when I think of people who like things to be easy, I think of regular people. IMHO, that is the majority of the world. So again, both your statements are essentially the same.

It’s similar to personality tests that ask, “Would you agree that you like partying?”, then 20 questions later it asks, “Partying is fun, isn’t it?”.

The Rosetta page is for understanding how other package managers compare to pacman. Is isn’t a full reference for pacman.

On the topic though: @Valerian Has Dalto’s suggestions worked?

I feel Linux is like the ultimate lego set. If you know what you want to build (e.g a car). And if you develop the use cases you can build a car as you see it. There is no one stopping you from putting a jet engine on that car. But then when you try to steer that car, well you might have performance problems.

The same car made by Apple … pick 1 of 5 colours, heres your key, drive the car with this user manual. We tell you what you need.

1 Like

It’s a completely unnecessary tool.

Why not? It’s the same for any other package. What’s the worst that could happen?

And while I would generally advise against following random online guides, you will see that on this forum, people are very quick to correct any inaccuracies, so you probably won’t get better or safer online help regarding maintaining your Linux OS. It’s exceptionally rare that bad advice is posted here and there is nobody to correct it.

I second that, literally first thing i’ve done once moving to Linux - compiling Kernel! :rofl:
It was great.

And here you just install / remove it, it’ll be fine.

3 Likes

Here lies the problem some don’t really know what they want and even worse some cannot build/develop.

If it was designed by the ɢɴᴏᴍᴇ project, the only colour offered would be the most inoffensive and dull beige. :rofl: