Lector de Feeds

‎Kernel series in Cauldron: s/stablenew/stable-testing/ in the first line

← Older revision Revision as of 16:33, 28 August 2025 Line 89: Line 89:  == Kernel series in Cauldron == == Kernel series in Cauldron ==    −In cauldron we now have -mainline, -stablenew, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.).+In cauldron we now have -mainline, -stable-testing, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.).     The stable-testing (formerly -stablenew) series is (in theory) the newest stable after -mainline, resembling [https://www.kernel.org upstream] though not matching one-to-one, as those might change more often. The stable-testing (formerly -stablenew) series is (in theory) the newest stable after -mainline, resembling [https://www.kernel.org upstream] though not matching one-to-one, as those might change more often. Marja

‎Backport kernels: Bug 34563 solved.

← Older revision Revision as of 16:03, 28 August 2025 (5 intermediate revisions by the same user not shown)Line 79: Line 79:  '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.'' '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.''    −'''Do not try to install''' 'kernel-stable-userspace-headers'. '''Yet.''' ''- It should be possible to have either that or kernel-userspace-headers installed, one at a time, but currently is not easy (See {{Bug|34545}}). The packages are used for building applications.'' +'''Regarding kernel-stable-userspace-headers''' contra ''kernel-userspace-headers'' for 6.6 kernels: The packages are used for building applications; use the one for the current kernel you build for. For the package managers to work correctly, you need to update mageia-repos and meta-task packages to 9.4 versions, at time of writing found in updates_testing.  ''(Note that they conflict each other but currently there is a bug that kernel-stable-userspace-headers can not be uninstalled because a conflict/dependency problem.)''     '''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.  Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source '''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.  Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source     '''If running VirtualBox''': Currently {{Bug|34408}}, before launching guests, you need to <br> '''If running VirtualBox''': Currently {{Bug|34408}}, before launching guests, you need to <br> −$ sudo rmmod kvm_intel<br>+$ sudo rmmod kvm_intel ''(When using Intel CPU; If you have AMD CPU then instead execute rmmod kvm_amd.)'' <br>  $ sudo rmmod kvm $ sudo rmmod kvm    Line 91: Line 91:  In cauldron we now have  -mainline, -stablenew, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.). In cauldron we now have  -mainline, -stablenew, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.).    −The -stablenew series is (in theory) the newest stable after -mainline, resembling [https://www.kernel.org upstream] though not matching one-to-one, as those might change more often.+The stable-testing (formerly -stablenew) series is (in theory) the newest stable after -mainline, resembling [https://www.kernel.org upstream] though not matching one-to-one, as those might change more often.     The -lts series also allows testing compatibility with the "previous" latest working LTS series, which could be useful in many cases, e.g. for proprietary drivers (e.g., NVIDIA) when they won't build anymore on newer kernels or for verifying different hardware behavior of older hardware with respect to newer kernels. The -lts series also allows testing compatibility with the "previous" latest working LTS series, which could be useful in many cases, e.g. for proprietary drivers (e.g., NVIDIA) when they won't build anymore on newer kernels or for verifying different hardware behavior of older hardware with respect to newer kernels. Line 97: Line 97:  Note that it is not guaranteed that all series cover all architectures and flavors. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavor (e.g., desktop), or new flavors may emerge (e.g., desktop-tunedv3 for x86_64-v3). Note that it is not guaranteed that all series cover all architectures and flavors. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavor (e.g., desktop), or new flavors may emerge (e.g., desktop-tunedv3 for x86_64-v3).    −As an example, on August 13 2025 we had the following kernels in Cauldron:+As an example, on August 28 2025 we had the following kernels in Cauldron: −* kernel-mainline -> 6.16.0 (x86_64, desktop only)+* kernel-mainline -> 6.17.0-rc3 (x86_64, desktop only) −* kernel-stablenew -> 6.15.7 (x86_64, desktop only)+* kernel-stable-testing -> 6.16.2 (x86_64, desktop only) −* kernel-stable -> 6.14.11 (x86_64, desktop only)+** ''(kernel-stablenew -> 6.15.7 (x86_64, desktop only) - this series gets obsoleted in favour of kernel-stable-testing.)'' −* kernel -> 6.12.41 (all arches, all flavours)+* kernel-stable -> 6.15.11 (x86_64, desktop only)  +* kernel -> 6.12.43 (all arches, all flavours)  * kernel-lts -> 6.6.100 (all arches, all flavours) * kernel-lts -> 6.6.100 (all arches, all flavours) Morgano

‎Backport kernels: Bug 34563 boot menu

← Older revision Revision as of 17:14, 27 August 2025 Line 78: Line 78:     '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.'' '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.''  +  +'''Boot menu do not update''' ({{Bug|34563}}), getting fixed in 6.12.43+. If you install a kernel and do not find it in boot menu, run {{cmd|update-grub2}} as root.     '''Do not try to install''' 'kernel-stable-userspace-headers'. '''Yet.''' ''- It should be possible to have either that or kernel-userspace-headers installed, one at a time, but currently is not easy (See {{Bug|34545}}). The packages are used for building applications.''    '''Do not try to install''' 'kernel-stable-userspace-headers'. '''Yet.''' ''- It should be possible to have either that or kernel-userspace-headers installed, one at a time, but currently is not easy (See {{Bug|34545}}). The packages are used for building applications.''    Morgano