Ubuntu
dkms package

DKMS Autoinstaller ignores added modules

Bug #867922 reported by Mario Limonciello
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dkms (Ubuntu)
Fix Released
Undecided
Mario Limonciello
Ubuntu ubuntu-11.10
Oneiric
Fix Released
Undecided
Mario Limonciello
Ubuntu ubuntu-11.10
fglrx-installer (Ubuntu)
Won't Fix
Undecided
Unassigned
Oneiric
Won't Fix
Undecided
Unassigned
fglrx-installer-updates (Ubuntu)
Won't Fix
Undecided
Unassigned
Oneiric
Won't Fix
Undecided
Unassigned

Bug Description

v: 2.2.0.2-1ubuntu3

This is a regression from natty. The DKMS autoinstaller service is now ignoring modules that have been added but not built for the first time.

This causes the fglrx driver to not work properly in OEM installs because in an OEM install it creates an upstart job that will "dkms add" followed by calling the autoinstaller service.

The reason the code was added to DKMS was to avoid trying to rebuild drivers on every upgrade if they failed to build the first time.

Revision history for this message
Mario Limonciello (superm1) wrote :

This can either be fixed by:

1) Removing this functionality from DKMS to test for the 'added' status.
2) Modify fglrx (and fglrx-updates) to call 'dkms install -m fglrx -v $VER' instead of 'dkms add -m fglrx -v $VER; dkms autoinstall'

Revision history for this message
Mario Limonciello (superm1) wrote :

I'm not sure if there are other drivers that use the autoinstaller service like this. If so, it might make more sense to do <1>. Otherwise I think I would prefer to do <2> for oneiric.

Changed in fglrx-installer (Ubuntu):
milestone: none → ubuntu-11.10
Changed in fglrx-installer-updates (Ubuntu):
milestone: none → ubuntu-11.10
Changed in fglrx-installer (Ubuntu):
status: New → Confirmed
Changed in fglrx-installer-updates (Ubuntu):
status: New → Confirmed
Changed in dkms (Ubuntu):
status: New → Confirmed
milestone: none → ubuntu-11.10
Revision history for this message
Alberto Milone (albertomilone) wrote :

honestly, I'd rather fix the issue in dkms instead of modifying 6 nvidia packages and 2 fglrx packages in Oneiric.

Revision history for this message
Mario Limonciello (superm1) wrote :

Ok, that is a lot to update. I've committed to DKMS master to not skip the modules in the 'added' state and uploaded to oneiric.

Changed in fglrx-installer (Ubuntu):
status: Confirmed → Won't Fix
Changed in fglrx-installer-updates (Ubuntu):
status: Confirmed → Won't Fix
Changed in fglrx-installer (Ubuntu):
milestone: ubuntu-11.10 → none
Changed in fglrx-installer-updates (Ubuntu):
milestone: ubuntu-11.10 → none
Changed in dkms (Ubuntu Oneiric):
status: Confirmed → Fix Committed
assignee: nobody → Mario Limonciello (superm1)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dkms - 2.2.0.2-1ubuntu4

---------------
dkms (2.2.0.2-1ubuntu4) oneiric; urgency=low

  * Autoinstall modules that have just been added too. (LP: #867922)
 -- Mario Limonciello <email address hidden> Wed, 05 Oct 2011 18:17:21 -0500

Changed in dkms (Ubuntu Oneiric):
status: Fix Committed → Fix Released
Revision history for this message
Alberto Milone (albertomilone) wrote :

Thanks a lot, Mario!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.