I’m a new EOS user, so I’m unfamiliar with the EOS repo release structure timings. So forgive me if this has been answered before (yes, I did search).
Linux mainline kernel 6.15 released five days ago (5/25). https://kernel.org/
But this variant is not available via the Arch/EOS repos at all.
Kernel 6.14.9 was in the “testing” repo the day after it released, then moved to the “stable” repo soon after (though it’s now flagged “out-of-date” as of yesterday). Do the devs wait for the first point-release (6.15.1) before adding to “testing”?
The reason I ask is because the 6.15 version specifically adds fixes to crashes for my AMD “Strix-Point” chipset.
Should I just compile my own 6.15 kernel from source now, or is the Arch/EOS 6.15 just around the corner and better to wait?
It depends. Often a new mainline kernel release is pushed to core-testing or core when the first pointrelease is available.
On EndeavourOS pacman fetches kernels from the Arch repos. So the Arch devs decide when they think the latest kernel version is good enough to be released.
Often they release a new kernel after the first .1 release (e.g. 6.5.1). First the kernel will be in the testing repos, and a bit later in the stable repos. Usually this process takes a few days, sometimes a bit more.
There have been issues with kmods, like virtual box module being properly ported. That’s probably why the lag time.
That’s what I figured, but thought I’d ask first. Thanks!
I think it is wise to wait for a pointrelease:
I’ve been running linux-cachyos 6.15.0-1 for the past several days without issue. So… so far, so good on my machine.
Not in [core] or [extra] or the other officially maintained repos, but linux-mainline is available in the AUR. And as @UncleSpellbinder pointed out, other kernel builds, which should be in the AUR as well, are a bit faster to adapt to the latest kernel releases. But I’m not certain if you’ll run into compilation hell if your choose to fetch another kernel build. Which could be addressed by including Chaotic-AUR eventually.
Even released x.y.0 kernels aren’t necessarily considered stable, but mainline, as is the case for e.g. 6.15.0 at the moment (https://kernel.org/).
Usually the next release - currently 6.16.0-rc1 (release candidate 1), and 6.15.1 in the same timeframe - triggers the whole chain moving to the next notch, which then will be picked up downstream in the Arch repos or linux-zen.
Arch is of portrayed as bleeding edge, but in reality that’s more blunt than you would assume, even in testing.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.