No need to ask here as Oct 6th is the Kernel Freeze date as shown in the Release Schedule.
The 6.0 kernel is not out yet as still at release candidates so no time for Ubuntu to test a 6.0 kernel in time for the 22.10 release. https://www.kernel.org
Anyway important kernel updates and fixes can always be backported if Ubuntu thinks they are worth the effort.
Hi, v6.0 is indeed too late to integrate into Kinetic / 22.10. However, the next milestone release of Ubuntu is 22.04.2 LTS point release in February 2023. The work to integrate HWE v5.19 and OEM v6.0 based kernels has already started, such that Canonical OEM certified laptops can benefit from v6.0 based OEM kernel on latest generation of hardware.
there are never exact timings for such things, and it pretty much depends on scheduling engineers to work on it between now and 22.04.2 release, and how much other things there are to do. I.e. there is 22.10 release to ship first.
Intel Arc GPU support in upstream linux kernels is still experimental.
As mentioned earlier 22.04 will have oem-6.0 kernel, and then it will have future hwe kernels from 23.04, 23.10, 24.04 releases. Thus yes, eventually 22.04 will have Intel Arc GPU support.
it made it out of proposed into updates, as an edge variant on 28th of October, but I’m not sure if it was actually usable as that publication was a security CVE.
It finally got marked as non-edge variant on 15th of December, and I can’t tell when it actually managed to get to updates, possibly like 6th of January.
But you can also lookup stable series patch level - i.e. Click on the tag of interest e.g. Ubuntu-5.19.0-24.25 browse tree and then check out the debian.master/upstream-stable there you will see which stable patch series are applied. FYI it is v5.19.17 so next update should be good. BTW it is already available in kinetic-proposed since 2022-11-16.
You can test it by installing it from kinetic-proposed, but note that it kinetic-proposed has many other package updates too. Alternatively you can opt into Kernels as in proposed PPA which only has the kinetic-proposed kernels alone.
Kernels in kinetic-proposed and the as-proposed-ppa are signed with secureboot keys.
Our cycle dates are listed on Kernel SRU Cycles currently planned to land in -updates sometime after 5th of December. If it slips the page will be updated, and we also send email announcements.
good, I’ve got some (nice) updates. I actually had 3 issues with this notebook*:
Rembrandt’s keyboard IRQ change. It’s working perfectly after upgrading ; I wish AMD had given us a little more time (or a switch in the BIOS), but ;
random crashes at boot time: more like black screen (the login screen failed to show up); furthermore, random pauses, stuttering, and outright crashes later on; originally only on 25% of boots, lately a little more frequent; no crash whatsoever after upgrading (will keep checking, I hope I will not need to update here);
on 5.19.0.23 I needed to disable the dGPU in the BIOS or else it wouldn’t boot (not showing anything); now it works after upgrading, and I even installed the proprietary drivers (which means I’m back on X now);
So right now I’m extremely happy about this upgrade. Thanks a lot… Sounds like a lot happened between 5.19.10 and 5.19.17.
– nachokb
(*) for the record, this is a Lenovo Yoga Slim 7 Pro X (AMD Rembrandt 6800HS + RTX 3050)
Как решить ошибку после удаления старых ядер -установленный linux-image-5.15.0-46-generic пакет скрипта после удаления подпроцесс вернул статус выхода ошибки 1 , теперь не могу войти в grub получаю ошибку grub-mkconfig не может быть успешно выполнен. сообщение об ошибке: файл suurcing */etc/default/grub’/usr/sbin/grub-mkconfig:35/etc/default/grub: синтаксическая ошибка: EOF в замене обратной кавычки( in English -grub-mkconfig could not be completed successfully. payment message: file suurcing */etc/default/grub’/usr/sbin/grub-mkconfig:35/etc/default/grub: syntax error: EOF in backquote replacement)
On 17th of November a broken config was pushed, which made the build machinery error out even before attempting builds and/or triggering notification of failed builds. I have a patch to unbreak it, and we will try to re-schedule build for it to catch up.
On behalf of Ask Ubuntu, and specifically this question I would like an authoritative response to the question by the Kernel Team. Specifically, if the mainline PPAs aren’t tested (as they shouldn’t be except for debugging purposes as stated on the wiki), I’d like such a statement from the Kernel Team, and for that to be appended to Kernel/MainlineBuilds - Ubuntu Wiki where possible so that we can treat that as authoritative documentation and answers.
I’m reachable on IRC with a single ping in #ubuntu-devel or via email (see launchpad) with a response. Or just answer the question on Ask Ubuntu