Bug 711773

Summary:	dkms dones not work at boot time
Product:	[Fedora] Fedora	Reporter:	John Mev <zikamev>
Component:	dkms	Assignee:	sunil <sunil_gupta2>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	15	CC:	mario_limonciello, sunil_gupta2, tcallawa, zikamev
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-07-27 18:43:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description John Mev 2011-06-08 12:58:21 UTC

Description of problem:

dkms does not work at boot time

Version-Release number of selected component (if applicable):

dkms-2.1.0.1-1.fc12.noarch

How reproducible:

During boot the message indicates that dkms will build the news modules but does nothing else.

Steps to Reproduce:
1.
install F 15 with kernel-devel, dkms package and devel tools

2. 
install virtualbox or proprietary driver ATI . At install time, dkms will build the modules

3.
update kernel and kernel-devel; reboot and see : the modules aren't build ans the drivers don't work.

  
Actual results:

no module build at kernel update

Expected results:

module(s) build at kernel update

Additional info:

Comment 1 sunil 2011-07-27 12:16:30 UTC

looks like you are hitting the bug 

https://bugzilla.redhat.com/show_bug.cgi?id=702483

Comment 2 Mario Limonciello 2011-07-27 15:19:11 UTC

Yes, please update to 2.2.0.2 and it should hopefully go away.

Comment 3 John Mev 2011-07-27 18:42:19 UTC

(In reply to comment #1)
> looks like you are hitting the bug 
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=702483

Exact. I apologize

I'm waiting for the update in the repos to update.

thanks

Comment 4 John Mev 2011-07-27 18:43:54 UTC


*** This bug has been marked as a duplicate of bug 702483 ***