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?
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.
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) , switched from low-latency to the generic kernel, and all good with music production! Thank you very much.
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
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)
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.
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.
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.
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.