med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

370
active users

#linuxkernel

9 posts8 participants3 posts today

A bunch of new stable kernels is out. With them, the #Linux 6.14.y stable series is now EOL – right after the merge window closed.

This is a bit earlier then we are used to, but will be the new normal. To quote @gregkh from lore.kernel.org/all/2025061030:

'"Note this is the LAST 6.14.y release. This kernel branch is now end-of-life. Please move to the 6.15.y kernel branch at this time.

If you notice, this has happened a bit more "early" than previous end-of-life announcements. Normally, after -rc1 is out there is a TON of stable patches happening due to the changes that come into the merge-window that were marked for stable backports but didn't get into Linus's release before -final. As some people have objected to this large influx being added to a stable kernel that is just about to go end-of-life, let's try marking this end-of-life a bit earlier to see how it goes.

It might also spur maintainers/developers to get fixes into -final a bit more as well :)"'

very long shot: do i know anyone who knows anything about linux's schedutil CPU governor?
i have this old microserver and the clock never leaves the lowest frequency (unless i tell it to manually). i have checked A Lot of things and everything looks correct, it just does not do anything even under high load.
it's a basic nixos install, but from everything i have checked i would be surprised if it's a disto specific issue.
#linux #kernel #linuxkernel #nixos

This week's Linux and FOSS news:

LINUX NEWS

Linux kernel 6.15 released with Rust support for hrtimer and ARMv7, a new setcpuid= boot parameter for x86 CPUs, support for sched_ext to count and report internal events, x86 Intel and AMD PMU enhancements, nested virtualization support for VGICv3 on ARM, support for emulating FEAT_PMUv3 on Apple Silicon, new API to receive information about mount and unmount events of filesystems, support for hardware-wrapped encryption keys in the block layer, support for 48-bit block addressing in the EROFS file system, etc:
9to5linux.com/linux-kernel-6-1

Linux-libre kernel 6.15 released with Nova Core GPU, Qualcomm iris v4l2, Airoha NPU, Tehuti Networks TN40xx 10G Ethernet, Realtek 8814A Wi-Fi, Apple Silicon SoC touchscreen, Renesas UFS hooks, Spider 1Gb Ethernet,aw88166 audio drivers removed:
9to5linux.com/gnu-linux-libre-

Archinstall 3.0.7 released with option to configure Btrfs snapshot type (Snapper or Timeshift), disk encryption configuration moved into the disk config menu, various bug fixes and improvements:
9to5linux.com/archinstall-3-0-

Alpine Linux 3.22 released with Linux kernel 6.12 LTS, GNOME 48, KDE Plasma 6.3, LXQt 2.2, gummiboot (systemd-boot) replaced with systemd-efistub, updated packages:
9to5linux.com/alpine-linux-3-2

Ubuntu 20.04 LTS reached EOL on May 31, upgrade to newer version is recommended, or Ubuntu Pro subscription to get patches until 2030:
news.itsfoss.com/ubuntu-20-04-
(Canonical doin the Microsoft thing: charging to keep getting patches)

Canonical to release monthly Ubuntu snapshots:
phoronix.com/news/Monthly-Ubun

NVIDIA driver 575 released with NVIDIA Smooth Motion support, support for GLX front buffer rendering on Xwayland, support for the __NV_DISABLE_EXPLICIT_SYNC environment variable to also apply to GLX and Vulkan apps etc:
9to5linux.com/nvidia-575-linux

(more Linux and FOSS news in comments)

Media even without AI manages to deliberately or accidentally misinform us all the time[1]. The screenshotted article below is an example of this, as #Linux (the #Kernel) as of now still supports 486-style CPUs.

So let me repeat[2]:

Patches to remove 486-style CPUs support were discussed[3], but were not merged for #LinuxKernel 6.15. They are not even yet queued for 6.16, the version currently in development. But a developer likely will submit them[4] – then it's up to Linus if he will merge them immediately for 6.16 or let them wait till 6.17 to ensure they are tested in -next for a while, as bigger kernel changes are supposed to.

[1] See also: en.wikipedia.org/wiki/Gell-Man

[2] hachyderm.io/@kernellogger/114

[3] lore.kernel.org/lkml/202505150

[4] lore.kernel.org/lkml/aCX9iN5Bx

A option to optimize the code for the local CPU was merged for #Linux 6.16:

git.kernel.org/torvalds/c/ea1d

To quote: '"Add a 'native' option that allows users to build an optimized kernel for their local machine (i.e. the machine which is used to build the kernel) by passing '-march=native' to CFLAGS.

The idea comes from Linus' reply to Arnd's initial proposal:

lore.kernel.org/all/CAHk-=wji1

Here are some numbers comparing 'generic' to 'native' on a Skylake dual-core laptop (generic --> native) […]
There is little difference both in terms of size and of performance, however
the native build comes out on top ever so slightly [3 % in some cases]."'

Note, the author tried in on a different machine later, and there it made no real difference:

lore.kernel.org/all/b67fad41-3

Highlights from the main #bcachefs merge for #Linux 6.16: git.kernel.org/torvalds/c/5225

- Incompatible features may now be enabled at runtime, via "opts/version_upgrade" in sysfs.

- Various changes to support deployable disk images

- Major error message improvements for btree node reads, data reads, and elsewhere.

- New option, 'rebalance_on_ac_only'.

- Repair/self healing:

- We can now kick off recovery passes and run them in the background if we detect errors.

- Performance:

- Faster snapshot deletion

- Faster device removal

- We're now coalescing redundant accounting updates prior to transaction commit, taking some pressure off the journal.

- Stack usage improvements: All allocator state has been moved off the stack

git.kernel.orgMaking sure you're not a bot!