Ask us anything about Ubuntu Kernels!

Ok, so it’s official! Thank you for the pointers.

I already have Ubuntu Studio Installer, with these two packages enabled:

  • ubuntustudio-lowlatency-settings
  • ubuntustudio-performance-tweaks

I wasn’t aware of the Audio Configuration tool but it is installed. It has threadirqs and preempt=full checked. I read that nohz_full=all might still give some problems, but maybe they don’t affect my music production use case and I have enabled it because why not. We’ll see.

Would you recommend to remove the lowlatency kernel and install the generic now? Or just wait for the deprecation to take effect and hope that an upgrade takes care of this one day?

Read the descriptions on those carefully.

nohz_full=all doesn’t do what you think it’ll do, which is why it’s not a default in Ubuntu Studio. It’s mostly for virtualization workloads.

As far as removing the lowlatency kernel? It’s not necessary, and not installed by default in Ubuntu Studio (24.10 and later) if you have those kernel parameters checked. If you have the kernel perameter capability, that tells me you’re on 24.10, which means you certainly don’t need the lowlatency kernel anymore. In fact, it’s set for eventual deprecation.

2 Likes

Just a note to say that I followed your advice about disabling nohz_full=all (which indeed I had no clue what it was about) :sweat_smile: , switched from low-latency to the generic kernel, and all good with music production! Thank you very much.

2 Likes

Not sure I’m asking in the right place. Why do the builds here - Index of /mainline

differ from what I see in this app? I love trying new things and 6.13 is really new and this app only let’s me install one from DEC. Asking to learn - thank you!

Note that these kernels are solely for debugging purpose, they are lacking security patches, are completely unsupported and will not be updated, you should not use them unless being asked by the kernel team in a bug to verify fixes … they also do not use the Ubuntu config which will lead to problems in user space …

As for the tool, you should contact the people you got it from, this is definitely not any official Ubuntu software …

Oh and I can not stress enough with an official hat on (and another one on top) these kernels are UNSUPPORTED do not use them

3 Likes

Thank you! That makes sense. So, regardless of the Mainline app letting me install other ones and the news saying ‘this kernel has these improvements!’, just ignore it since I’m clearly not a debugger and just use the Ubuntu labeled one it comes with? (the mainline app has the Ubuntu on I can revert back to no problem)

1 Like

Yeah, you will get these improvements in Ubuntu too, it just takes some time to make sure everything gets tested properly, potential regressions are identified, the security patch sets are added on top etc

For some people whose hardware is too new to even work with the Ubuntu kernels, temporary using such mainline build might make sense to be able to run Ubuntu at all until their hardware is supported, but even for these people it should not be a long-term solution and they should eventually switch to a properly QA’ed and secured Ubuntu kernel once a version that supports their hardware lands in Ubuntu.

1 Like

Thank you for the replies! I’ll stick with the ubuntu one (it’s in the app’s list) and if I use the mainline one, know the possible stability issues.

This has been incredibly helpful and informative. Thank you again.

Hey everyone,

What do y’all think of this topic, it’s gotta be an excellent idea for Ubuntu gaming? :smiley: :video_game: :joystick:
I just wanna know what’s a response from you folks. :grinning:

unfortunately the final parts for extended af_unix mediation did not land in 6.12, but it appears that it did land in apparmor-next and now linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=26c200e28a322b308518cda764307c18d7df705d

Here’s hoping it lands in 6.14, if not 6.15 (https://www.reddit.com/r/Ubuntu/comments/zoz5qd/comment/m8866es/)

It looks like it has been pulled into the linux next branch as of February 10: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=26c200e28a322b308518cda764307c18d7df705d

With the new 6.11 kernel, I notice that some of my Ethernet interface names have changed.

On kernel 6.8.0-52-generic, my USB-C Ethernet adapter has the name “enx3814289aeaba”
But on kernel 6.11, it has the generic name “eth0”

I’ve tested on 3 different machines using different USB-C Ethernet adapters.

Is this intentional, or should I raise as a bug?

Out of curiosity, now that 6.14 is in rc4, when will 6.14 arrive on the daily images?

https://www.phoronix.com/news/Linux-6.14-rc4

1 Like

Hey there @YamiYukiSenpai :slightly_smiling_face:

I just checked what they’re going to include Linux 6.14, they’re thinking about including Linux 6.14 before Kernel Freeze starts, which it’s at April 3rd of this year.

You can learn more in here. :slightly_smiling_face:

Sure, they’re expecting to get it include at the end of the March or at the beginning of April of this year. Patience.

Do note, Closed-Source Kernel-Mode anti-cheat protected games like FORTNITE or
Grand Theft Auto V Online are still not playable quite yet. Due to not including a driver that allows it to work. But what does include, is NTSYNC, it has nothing to do with Closed-Source Kernel-Mode anti-cheats on Wine, but it does affect lots of games to make them run better than Windows like it needs to, which it’s nice. :slightly_smiling_face:

More like nice one, but not there yet. :slightly_smiling_face:

1 Like

The device naming policies and their matching should be stable-ish.

But Linux kernel X systemd-udevd together can sometimes make new choices given new or different information about the existing devices.

A bug report against systemd & linux packages would be interesting, together with sosreport attached, when booted with both 6.8 and 6.11 kernels.

1 Like

Hey :slight_smile:

What are the odds of setting CONFIG_ZRAM_MULTI_COMP=y to Kernel 6.8 / 6.11 packages?

With CONFIG_ZRAM_MULTI_COMP, zram can recompress pages using alternative (secondary) compression algorithms.

I was a very happy user of Ubuntu Studio on Acer Swift 5 but now I have to move
to surface pro 8.

There are kernel Patches for the surface that will solve my touchscreen problems found here:

I’m not at all into kernel coding and am curious.

  1. will patching to the surface kernel keep me away from getting importend updates of the official kernel?
  2. do you see any performance benefits using those patches?
  3. Another option is getting the touchscreen working somehow and stay with the original kernel.

Greetings, Stephan

Hi @dereber

I’m not on the kernel team, but the goal of that project is to upstream their patches to the Linux kernel even further upstream than Ubuntu, which they have done to an extent. It would be an immense undertaking for the kernel team at Canonical to apply and maintain these patches themselves.

I say this as someone who owns a Surface Pro 4.

Thanks @eeickmeyer,

so a way to go for me as a user would be
-patch my current kernel

  • after new ubuntu studio kernel release → patch again

correct or bs?

Just use the kernel from that repo. That’s what I do for mine. It has what you need.

1 Like