Bug 10771 - dkms builds are not removed when kernels are uninstalled which causes problems loading modules
Summary: dkms builds are not removed when kernels are uninstalled which causes problem...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-15 15:51 CEST by claire robinson
Modified: 2024-02-19 17:11 CET (History)
4 users (show)

See Also:
Source RPM: kernel-rt kernel-tmb, kernel-linus, kernel-vserver
CVE:
Status comment:


Attachments

Description claire robinson 2013-07-15 15:51:22 CEST
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:
Comment 1 Carolyn Rowse 2013-08-15 14:59:59 CEST
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

Comment 2 claire robinson 2014-06-20 14:27:10 CEST
I think this has caused some issues with the recent kernel update Thomas
Comment 3 claire robinson 2015-02-17 16:59:57 CET
Setting to cauldron as there is no fix yet AFAIK

Whiteboard: (none) => MGA4TOO
Version: 3 => Cauldron

Rémi Verschelde 2015-04-14 18:13:37 CEST

CC: (none) => rverschelde

Samuel Verschelde 2015-05-31 22:47:09 CEST

Whiteboard: MGA4TOO => MGA4TOO MGA5TOO

Comment 4 claire robinson 2015-10-01 15:52:53 CEST
Valid kernel 4.1.8 in mga5

Whiteboard: MGA4TOO MGA5TOO => MGA5TOO

Florian Hubold 2015-10-07 20:55:32 CEST

CC: (none) => doktor5000

Comment 5 Marja Van Waes 2016-08-26 11:43:16 CEST
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

Comment 6 Morgan Leijström 2022-08-08 20:43:02 CEST
Is this problem still valid?

CC: (none) => fri

Comment 7 Morgan Leijström 2024-02-19 17:08:12 CET
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) => FIXED
Status: NEW => RESOLVED

Comment 8 Morgan Leijström 2024-02-19 17:11:40 CET
I dont know *when* it go fixed - probably long time ago

Resolution: FIXED => OLD


Note You need to log in before you can comment on or make changes to this bug.