Description of problem: I am running the latest x86_64 version of mageia 6 (6.1?). The upgrading of kernel version 4.14.xx is problematic. The kernel gets installed, but not updated in grub. Kernel version 4.18.20 was installed as a dependence for kernel 4.14.xx, and the userspace headers for 4.18.20 is not available. Neither one of this should happen. I notice that kernel 4.18.20 is not actively maintained. The last change date is last year. The worst part is that the userspace kernel headers for 4.18.20 is not available, and therefore, dkms building of third party drivers (nvidia) cannot proceed. Version-Release number of selected component (if applicable): How reproducible: Just need to check Steps to Reproduce: 1. Remove 4.18.20 2. (Re)Install 4.14.106 (or any other 4.14.xx version) 3. This will install 4.18.20 as a dependence. kernel-server-latest does point to 4.18.20, but the userspace headers points to 4.14.106.
(In reply to Wonder Full from comment #0) > Description of problem: > > I am running the latest x86_64 version of mageia 6 (6.1?). The upgrading of > kernel version 4.14.xx is problematic. The kernel gets installed, but not > updated in grub. > > Kernel version 4.18.20 was installed as a dependence for kernel 4.14.xx, and > the userspace headers for 4.18.20 is not available. kernel 4.18.20 is only available from the backports repositories. Those repositories are "use at your own risk" I don't read that you willingly selected that kernel from backports, it is disable the backports repositories and downgrade your kernel packages and cpupower to the last version from /6/x86_64/media/core/updates/ (currently 4.14.116) If the issue with grub persists, then that is most likely bug 22274 @ tmb Are there still users that need kernel 4.18.20 and if so, do you plan to push matching userspace headers to backports testing?
Assignee: bugsquad => kernelCC: (none) => marja11, tmb
s/it is disable/it is better to disable/
is it still valid on mageia 7 ?
CC: (none) => mageia
No, this seems to be Mageia 6. We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there. As a result we are setting this bug to CLOSED:OLD
Resolution: (none) => OLDCC: (none) => ouaurelienStatus: NEW => RESOLVED