sigmoid.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A social space for people researching, working with, or just interested in AI!

Server stats:

596
active users

#kernel

14 posts11 participants0 posts today
AskUbuntu<p>dkms autoinstall on 6.14.0-24-generic/x86_64 failed for amdgpu(10) <a href="https://ubuntu.social/tags/apt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>apt</span></a> <a href="https://ubuntu.social/tags/packagemanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>packagemanagement</span></a> <a href="https://ubuntu.social/tags/upgrade" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>upgrade</span></a> <a href="https://ubuntu.social/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> <a href="https://ubuntu.social/tags/dpkg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dpkg</span></a></p><p><a href="https://askubuntu.com/q/1553515/612" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">askubuntu.com/q/1553515/612</span><span class="invisible"></span></a></p>

🐧The Linux Kernel Seeing Rare Code Activity Around SPARC64 • Phoronix

「 SPARC64 was the last architecture not using the generic vDSO library code that in turn prevented some necessary code clean-ups. With this patch series transitioning the SPARC code to the generic vDSO infrastructure saves several hundred lines of code and slightly reducing the SPARC maintenance burden 」

phoronix.com/news/Linux-SPARC6

www.phoronix.comThe Linux Kernel Seeing Rare Code Activity Around SPARC64One of the CPU architectures continuing to be supported by the mainline Linux kernel but rarely ever seeing any code activity is the SPARC64 architecture port for the once-interesting processors from Sun Microsystems.
Replied in thread

@edboythinks personally I'm in the process of.migrating from #Ubuntu fonts to #B612 because they are superior yet more permissively licensed.

Continued thread

2/ Another article about a feature recently added to the #XFS filesystem that is not considered experimental any more since #Linux 6.16-rc1 (the text was also written by the responsible developers):

""In this blog post, we discuss a new XFS feature [with] the ability to exchange arbitrary file contents atomically. […]

What Problems Does This Solve?

The first problem is that the Linux file I/O interface does not specify that writes to multiple ranges of a file must be persisted in an all or nothing fashion, which means that file contents can be inconsistent after a crash. […]

The second problem is that some external readers of a structured file must never see an update in progress.

A third problem in this space concerns software defined storage. […]""

blogs.oracle.com/linux/post/xf

#XFS Directory Parent Pointers since #Linux 6.16-rc1 are not considered experimental in the #kernel any more[1]. They allow constructing a file path from a file descriptor or a file handle, which should result in better redundancy and reporting.

In case your want to know more about it, checkout the recently published text "#XFS - Directory Parent Pointers in UEK8"[2], which was written by Allison Henderson and Darrick Wong, who developed and upstreamed the feature.

[1] Just like online fsck and the exchange-range syscall: git.kernel.org/linus/ca43b74ac

[2] just ignoring the Oracle/UEK specific bits

It's looking like #linux #kernel 6.14+ will contain the driver I need for an intel AX201 on a #Debian 12, which doesn't work on my #thinkpad right now (no wifi! agh!).

I'm telling you all that for the context behind this question:

Is it bad/dangerous/unstable to run Debian 12 on kernel 6.14?

Further, should I use the Ubuntu kernel or get the "raw" kernel?

Opinionated posts are welcome and helpful. Please do dump your thoughts at me.

#Linux users who have #Secure Boot enabled on their systems knowingly or unknowingly rely on a key from #Microsoft that is set to expire in September. After that point, Microsoft will no longer use that key to sign the shim first-stage #UEFI #bootloader that is used by Linux distributions to boot the #kernel with Secure Boot.

But the replacement key, which has been available since 2023, may not be installed on many systems; worse yet, it may require the #hardware vendor to issue an update for the system #firmware, which may or may not happen. It seems that the vast majority of systems will not be lost in the shuffle, but it may require extra work from distributors and users.

lwn.net/SubscriberLink/1029767

LWN.netLinux and Secure Boot certificate expirationLinux users who have Secure Boot enabled on their systems knowingly or unknowingly rely on a ke [...]