I had some problems with the update, which I solved myself. I am surprised that the linux-meta package still indicates kernel 6.15 as current.
The -meta packages are maintained; it is just that many members don’t seem to know the actual purpose of them.
They aren’t meant to force you on to the newest kernel; they are meant to stop you from continuing to run an unsupported EOL kernel that has been removed from the repos.
When linux615 is completely removed from Manjaro’s repos, the linux-meta package will be updated to automatically install linux616 and remove the no-longer-available linux615 from the user’s machine.
7 Likes
It seems like a good strategy if the dev team has the time to update it, but considering 6.15 has been EOL for a month it seems strange that it hasn’t moved to 6.16 yet. Right now its coaxing users to stay on a EOL kernel as opposed to moving to the new bleeding edge kernel.
Is there a reason linux-meta hasn’t moved to 6.16 yet? Why lag behind a month on what would be more closely associated with the unstable repo’s strategy of bleeding edge? I could see the argument that this is the stable branch so it should stay off for a bit. However, leaving the unsupported kernel installed seems wrong as it would incentivize people to use an out of date kernel.
Maybe my argument fails considering design philosophy of Manjaro vs Arch or stable vs unstable. I do hold that when a user specifically installs a non-LTS kernel it should be incentivized to stay away from ones that have fallen out of support.
1 Like
Linux-meta is not supposed to update you to the latest kernel as in some other distros. It is a safety net if do not update yourself and link to the oldest possible kernel and will only move up when that gets removed.
That is the current concept.
5 Likes
You do realise that you can still install other kernels when you have linux-meta installed? For example, I have 3 kernels installed:
pamac search -i linux
...
linux617 6.17.0rc7-1 core
The Linux 6.17 kernel and modules
linux616 6.16.9-1 core
The Linux 6.16 kernel and modules
linux612 6.12.49-1 core
The Linux 6.12 kernel and modules
linux-meta 6.16-1 core
Manjaro stable kernel meta package
...
I install new kernels when they become available, but don’t bother manually removing them anymore when they disappear from the repos. linux-meta handles removal of no-longer-available kernels on my system, as happened yesterday with the removal of linux615 from the Testing repos:
[2025-09-27T19:25:28+1000] [ALPM] removed linux615 (6.15.11-2)
[2025-09-27T19:25:35+1000] [ALPM] upgraded linux-meta (6.15-1 -> 6.16-1)
One thing I would recommend for users running only 1 kernel & using linux-meta to manage things is that they also install the kernel-modules-hook package to ensure that their system remains operational until they reboot if their currently running kernel is removed by linux-meta during an update. Of course, after any major update, a reboot should be done ASAP.
5 Likes
Yeah I understand I can install newer ones just fine. Just seems weird/bad practice that if you do follow the ‘recommended’ path you would end up on a EOL kernel for a month+.
I am one to follow the release cadences closely, but a user that doesn’t probably won’t look to install a newer one and will be stuck (I understand not stuck, but not everyone looks for kernel releases and will blindly follow linux-meta) on a EOL kernel.
The point I am making is someone who doesn’t follow too closely will end up on a kernel they shouldn’t be using anymore. This is anti-Manjaro philosophy to some degree, but in this case the user decided to go with bleeding edge kernels and should be kept to the bleeding edge that are still under support.
Ultimately I disagree with the concept I guess. In my opinion the safety net should be a little bigger 
As previously stated, it’s updated when the package is removed from the repo. That’s when it’s truly EOL. linux615 is still in the stable repo, so linux-meta still points to linux615.
It’s been removed from the unstable repo and linux-meta has been updated accordingly. You’ll have to wait until the updates get pushed to stable, or if you can’t wait then you can switch to the unstable branch.
Alternatively you could make and maintain your own version.
Not really, it’s the result of having a stable branch.
1 Like
Isn’t the stable branch one of the major points to have Manjaro over Arch/other derivatives?
Exactly. And you get bonus points if you use LTS kernel 
6 Likes
Abandoned topic (60+ days)