As far as I know, it is well understood by the user community that the mainline PPA kernels are untested and unsupported. However, it is expected that the .deb files are actually available via successful compile. Yes, sometimes something goes wrong and one or more versions of the compile breaks for a few days. For my part of it and for the last decade (until this year), if the PPA compile was broken, I would eventually go on the Ubuntu kernel IRC and inquire about it. Typically someone called APW would fix the compile issue within 24 hours. It is important to note that the build issues have always been something downstream at Ubuntu/Canonical and not due to some upstream source issue. This past year the mainline PPA compiles for amd64 have been broken rather often, including now and since mid November. The compile fix mentioned above by @xnox doesn’t seems to have worked.
My main linux volunteer effort is via the upstream kernel power management group. I use the Ubuntu Mainline PPA on a weekly basis, and extract the Ubuntu kernel configuration from it. If the Mainline compile is broken, then I don’t update the kernel configuration for my own kernel compiles. Availability of the mainline kernel PPA is nice for those that do not compile their own kernel, and for the reasons stated on the wiki and copied to the above referenced ask ubuntu question.
EDIT 1: Correction: The Ubuntu Mainline PPA build failure of 2015.09.13 for kernel 4.3-rc1 was due to an upstream source issue. My own compile failed then also.
EDIT 2: Example IRC mainline compile fix request session.
I would strongly recommend making it bold, or expand on that to include that this means retroactive ‘monitoring’ of the PPA is limited to if someone requests a rebuild for a sane reason, etc.
Edit: Using my wiki editor powers I bolded that line to make it stand out.
I would limit this to “regular users” in the community - we have a TON of new people on Ask Ubuntu who are not aware of this and don’t read the documentation, thus leading to these kinds of questions.
I’ll include a note about that, though without a fix this is something that people’ll complain about because, well, as i said they’re a little ignorant the general user base.
These kernels are not supported and are not appropriate for production use. Additionally, these kernels do not receive any security updates, therefore if you install them manually via the Mainline PPA, you will never receive a security update or patch for that version.
Edited your blurb for readability but put it in the same bold area because, well, not every user reads this and those that do probably are looking for install instructions and glazing over the rest (if it’s bold we can say “Did you read the wiki documentation? It says right here in big bold print that these are unsupported…” among other things if they question it.)
@zika
As this was already asked a number of times, you have the answer above. Whenever Canonical decides a mainline kernel is needed for their testing a new kernel will be provided.
Not the answer I wanted either but if you need a kernel take the time and build it yourself. Happy config editing … rinse and repeat.
Would there be a way to upgrade the kernel in the update GUI in the future? This is one thing I liked about Lunux Mint – that I could update to newer kernels within update manager.
Thanks I disagree removing the mainline kernels…
With the latest approved Kernel for Ubuntu is the at most approved
kernel by Canonical… https://ubuntu.com/community/canonical
Their are a lot more… Server ? https://ubuntu.com/download/server https://canonical.com/ https://ubuntu.com/download/desktop https://www.kernel.org/
How often does a Ubuntu Kernel change versions ?
Yearly or just by version release of the kernel ?
I have installed the bleeding edge kernel a few times.
Worked … other times I helped with the bugs…
Persistence makes Ubuntu better.
How does Ubuntu decide to go with New kernel releases?
You would think that Ubuntu would be appreciative of users testing kernels on their systems and reporting any issues they find, even if it were the non-rc one’s like 6.0, 6.1 and 6.1.1 stable.
Canonical has a business to run. If their business does not need a new kernel built for their testing then no one has the time or resources to fix any breakage with the automated mainline kernel builds.
Until Canonical chooses which new Linux kernel to use for Lunar Lobster testing it is unlikely for these mainline kernel builds to be fixed. I suspect Canonical will pick 6.1 as it is an LTS kernel but the Lunar release is not an Ubuntu LTS so who knows ?
Anyway Feature Freeze is the end of February, so for sure it will be fixed by sometime in February.
Also Ubuntu Testing week is in March.
See Lunar Lobster Release Schedule
I want to specify the kernel version to 5.4.0-125, but the code i use in user-data doesn’t work . When install the OS , it will always update to 5.4.0-150.
kernel:
package: linux-image-5.4.0-125-generic
Yes, I use the cloud-init user-data to install os automatically.
My config file :
autoinstall:
version: 1
refresh-installer:
update: no #Network configuration for DHCP
network:
network:
version: 2
ethernets:
any:
match:
name: eno*
dhcp4: true
In general, Ubuntu updates are rolling, meaning your kernel just like all the other packages will be upgraded. 5.4.0-125 is a very old kernel build which is no longer supported. It is not recommended to install individual kernel ABI packages, and instead you should only install the meta that will keep your systems updated (as is done by default).
Why are you trying to install an obsolete and security vulnerable build of v5.4 kernel, when latest abi is 150?
Did you make your customer at least aware that you are installing something with well known and documented vulnerabilities so that hackers even have a tutorial how to break in ? You seem to be doing your customer quite a disservice here if you do not try to convince them to use a kernel with the fixes…
