Mageia forum

Not sure this is a bug, or bad formulated message or i have had too little coffee...

To me it looks like it have dkms-nvidia340 version 340.96-36 installed ( it say so itself, and other tools agree)
and then it refuse to install kernel because dkms-nvidia340 < 340.96-36 ??

Code: Select all

[root@goran morgor]# LC_ALL=C urpmi --auto-update
medium "Core Release" is up-to-date
medium "Core Updates" is up-to-date
medium "Nonfree Release" is up-to-date
medium "Nonfree Updates" is up-to-date
medium "Tainted Release" is up-to-date
medium "Tainted Updates" is up-to-date
medium "Core 32bit Release" is up-to-date
medium "Core 32bit Updates" is up-to-date
medium "Nonfree 32bit Release" is up-to-date
medium "Nonfree 32bit Updates" is up-to-date
medium "Tainted 32bit Release" is up-to-date
medium "Tainted 32bit Updates" is up-to-date
Package dkms-nvidia340-340.96-36.mga6.nonfree.x86_64 is already installed
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch   
(medium "Core Release")
  cpupower                       4.6.1        1.mga6        x86_64 
  kernel-desktop-4.6.1-1.mga6    1            1.mga6        x86_64 
  kernel-desktop-devel-4.6.1-1.> 1            1.mga6        x86_64 
  kernel-desktop-devel-latest    4.6.1        1.mga6        x86_64 
  kernel-desktop-latest          4.6.1        1.mga6        x86_64 
89MB of additional disk space will be used.
57MB of packages will be retrieved.
Proceed with the installation of the 5 packages? (Y/n) y


installing kernel-desktop-devel-4.6.1-1.mga6-1-1.mga6.x86_64.rpm kernel-desktop-4.6.1-1.mga6-1-1.mga6.x86_64.rpm kernel-desktop-devel-latest-4.6.1-1.mga6.x86_64.rpm kernel-desktop-latest-4.6.1-1.mga6.x86_64.rpm cpupower-4.6.1-1.mga6.x86_64.rpm from /var/cache/urpmi/rpms
Installation failed:    dkms-nvidia340 < 340.96-36 conflicts with kernel-desktop-4.6.1-1.mga6-1-1.mga6.x86_64

morgano wrote:To me it looks like it have dkms-nvidia340 version 340.96-36 installed ( it say so itself, and other tools agree)
and then it refuse to install kernel because dkms-nvidia340 < 340.96-36 ??

Code: Select all

Installation failed:    dkms-nvidia340 < 340.96-36 conflicts with kernel-desktop-4.6.1-1.mga6-1-1.mga6.x86_64

No it says there's a conflict between the package dkms-nvidia340 for versions lower then 340.96-36 against the package kernel-desktop-4.6.1, this has not much to do with the version number.

Can you show the output of

Code: Select all

rpm -qa|sort grep nvidia

Code: Select all

# rpm -qa | grep nvidia | sort
dkms-nvidia340-340.96-35.mga6.nonfree
dkms-nvidia340-340.96-36.mga6.nonfree
dkms-nvidia-current-361.45.11-1.mga6.nonfree
nvidia340-doc-html-340.96-36.mga6.nonfree
nvidia340-kernel-4.1.15-desktop-2.mga5-340.96-1.mga5.nonfree
nvidia-current-doc-html-361.45.11-1.mga6.nonfree
x11-driver-video-nvidia340-340.96-36.mga6.nonfree
x11-driver-video-nvidia-current-361.45.11-1.mga6.nonfree

So why do the system still have -35 while it have installed -36?
This is an upgraded system from mga5, and I kept that kernel, it seem that it was using that ;

Code: Select all

# urpme dkms-nvidia340-340.96-35.mga6.nonfree.x86.64       
okänt paket: dkms-nvidia340-340.96-35.mga6.nonfree.x86.64
[root@goran morgor]# urpme dkms-nvidia340-340.96-35.mga6.nonfree.x86_64
tar bort dkms-nvidia340-340.96-35.mga6.nonfree.x86_64
varning: Unable to get systemd shutdown inhibition lock

-------- Uninstall Beginning --------
Module:  nvidia340
Version: 340.96-35.mga6.nonfree
Kernel:  4.6.0-desktop-1.mga6 (x86_64)
-------------------------------------

Status: This module version was INACTIVE for this kernel.
depmod......

DKMS: uninstall Completed.

-------- Uninstall Beginning --------
Module:  nvidia340
Version: 340.96-35.mga6.nonfree
Kernel:  4.1.15-desktop-2.mga5 (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

nvidia340.ko.xz:
 - Uninstallation
   - Deleting from: /lib/modules/4.1.15-desktop-2.mga5/dkms/drivers/char/drm/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

nvidia-uvm.ko.xz:
 - Uninstallation
   - Deleting from: /lib/modules/4.1.15-desktop-2.mga5/dkms/drivers/char/drm/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.
depmod.....

DKMS: uninstall Completed.

-------- Uninstall Beginning --------
Module:  nvidia340
Version: 340.96-35.mga6.nonfree
Kernel:  4.6.0-desktop-0.rc7.4.mga6 (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

nvidia340.ko.xz:
 - Uninstallation
   - Deleting from: /lib/modules/4.6.0-desktop-0.rc7.4.mga6/dkms/drivers/char/drm/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


nvidia-uvm.ko.xz:
 - Uninstallation
   - Deleting from: /lib/modules/4.6.0-desktop-0.rc7.4.mga6/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod.....

DKMS: uninstall Completed.

------------------------------
Deleting module version: 340.96-35.mga6.nonfree
completely from the DKMS tree.
------------------------------
Done.
tar bort paket dkms-nvidia340-340.96-35.mga6.nonfree.x86_64
      1/1: tar bort dkms-nvidia340-340.96-35.mga6.nonfree.x86_64
                                 ############################################################################

I wonder if the system was supposed to still use have both -35 and -36 of dkms-nvidia340-340.96, if so why.

This system do have problems with the updater hanging occasionally, i will start a new thread about that...
(and yes i have "# rpm --rebuilddb" just in case)

morgano wrote:I wonder if the system was supposed to still use have both -35 and -36 of dkms-nvidia340-340.96, if so why.

This system do have problems with the updater hanging occasionally, i will start a new thread about that...
(and yes i have "# rpm --rebuilddb" just in case)

No it shouldn't, you probably ended an update while it was in the middle of a transaction, so it could not remove the old package.