Please see lengthy descriptions in bug 10698 and bug 10699 When a kernel is removed that has a dkms module installed upon it then dkms build is not removed. dkms status shows it as still being installed upon the kernel which has been since uninstalled. This causes problems with loading the modules. Nvidia falls back to nouveau etc. It's possible this also affects the main kernel-desktop etc but they have pre-built kmod packages available for them so would be less obvious. The orphan dkms builds can be individually manually uninstalled/removed but it exits with an error code. The simplest workaround is to remove the dkms- package and reinstall it so that the modules are rebuilt for each kernel. Reproducible: Steps to Reproduce:
I wonder if that's why my alpha 1 installation went back to Nouveau and I had to find an Nvidia driver in the software list to install - I've never had that before with Mageia. Carolyn
CC: (none) => isolde
I think this has caused some issues with the recent kernel update Thomas
Setting to cauldron as there is no fix yet AFAIK
Whiteboard: (none) => MGA4TOOVersion: 3 => Cauldron
CC: (none) => rverschelde
Whiteboard: MGA4TOO => MGA4TOO MGA5TOO
Valid kernel 4.1.8 in mga5
Whiteboard: MGA4TOO MGA5TOO => MGA5TOO
CC: (none) => doktor5000
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.
Assignee: tmb => kernel
Is this problem still valid?
CC: (none) => fri
I have not seen this problem with nvidia nor VirtualBox kernel modules while i have uninstalled and installed many kernels last year with them. And never heard of this problem what i remember.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
I dont know *when* it go fixed - probably long time ago
Resolution: FIXED => OLD