Bug 7113 - Nvidia driver v304.37 does not provide kmod(nvidia-current) dependency
Summary: Nvidia driver v304.37 does not provide kmod(nvidia-current) dependency
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-19 20:10 CEST by Vladimir Gurevich
Modified: 2012-08-19 23:01 CEST (History)
1 user (show)

See Also:
Source RPM: nvidia-current-kernel-3.5.2-desktop-1.mga3-304.37-1.mga3.nonfree, dkms-nvidia-current-304.37-1.mga3.nonfree
CVE:
Status comment:


Attachments

Description Vladimir Gurevich 2012-08-19 20:10:09 CEST
Description of problem:

The previous Nvidia-related packages used the kmod(nvidia-current) dependency for the proprietary Nvidia kernel driver. For example, the package nvidia-current-kernel-3.5.1-desktop-1.mga3-295.71-1.mga3.nonfree would provide the dependancy 

 kmod(nvidia-current)= 295.71-1.mga3.nonfree

Subsequently the packages that needed the driver (e.g. x11-driver-video-nvidia-current-295.71-1.mga3.nonfree).

The latest packages with the kernel driver (nvidia-current-kernel-3.5.2-desktop-1.mga3-304.37-1.mga3.nonfree, dkms-nvidia-current-304.37-1.mga3.nonfree) provide a different dependency:

  kmod(nvidia) = 304.37

The problem is that the packages that need it check for kmod(nvidia-current) instead and thus the installation (upgrade) fails.

Please,
   1) Standardaze the dependency naming  (nvidia or nvidia-current)
   2) Standardize the dependency value (i.e. just the version of Nvidia driver or the version of the corresponding Mageia package)
   3) Rebuild the RPMs accordingly

Thanks,
Vladimir
Comment 1 Thomas Backlund 2012-08-19 21:06:03 CEST
Sorry, I missed that upstream changed from nvidia-current to nvidia so it started to provide kmod(nvidia) instead of kmod(nvidia-current)...

I have added provides kmod(nvidia-current) to nvidia-current-304.37-2.mga3 and kmod-nvidia-current-304.37-2.mga3 so it should work again...

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED

Comment 2 Thomas Backlund 2012-08-19 22:22:26 CEST
Actually that was not enough to cope with our driver handling as pointed out by Anssi.

I reverted that change, and fixed it properly in:

nvidia-current-304.37-3.mga3
kmod-nvidia-current-304.37-3.mga3

by replacing the dkms.conf provided by nVidia with our customized one, so it will work again as intended...
Comment 3 Vladimir Gurevich 2012-08-19 23:01:50 CEST
Yep! I was just about to file another bug, that the module would load on 3.5.1, but not on 3.5.2, but you, guys, fixed it!

Everything works for me now.

Thanks a lot,
Vladimir

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