I have been testing dkms-2.0.16 and i can reach the conclusion that when
upgrading a dkms package and the module kernel is the same, what dkms do it
to first install the kernel module and then removes it, but ill paste here
the complete output of the install and an upgrading:
~x86_64]# rpm -Uvh dkms-virtualbox-1.4.0-0.svn3059.1mde2007.1.x86_64.rpm
erro: Não consegui analisar o /mnt/nfs/acer/home: Permissão negada
A preparar... ########################################### [100%]
1:dkms-virtualbox ########################################### [100%]
+ /usr/sbin/dkms --rpm_safe_upgrade add -m virtualbox -v
1.4.0-0.svn3059.1mde2007.1
Creating symlink /var/lib/dkms/virtualbox/1.4.0-0.svn3059.1mde2007.1/source ->
/usr/src/virtualbox-1.4.0-0.svn3059.1mde2007.1
DKMS: add Completed.
+ /usr/sbin/dkms --rpm_safe_upgrade build -m virtualbox -v
1.4.0-0.svn3059.1mde2007.1
Preparing kernel 2.6.17-14mdv for module build:
(This is not compiling a kernel, just preparing kernel symbols)
Storing current .config to be restored when complete
Running Generic preparation routine
make mrproper....
using /proc/config.gz
make oldconfig.....
make prepare.....
Building module:
cleaning build area....(bad exit status: 2)
make KERNELRELEASE=2.6.17-14mdv -C /lib/modules/2.6.17-14mdv/build
M=/var/lib/dkms/virtualbox/1.4.0-0.svn3059.1mde2007.1/build.....
cleaning build area....(bad exit status: 2)
cleaning kernel tree (make mrproper).....
DKMS: build Completed.
+ /usr/sbin/dkms --rpm_safe_upgrade install -m virtualbox -v
1.4.0-0.svn3059.1mde2007.1
Running module version sanity check.
vboxdrv.ko.gz:
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/2.6.17-14mdv/kernel/3rdparty/vbox/
depmod....
DKMS: install Completed.
+ /sbin/modprobe vboxdrv
+ :
+ /usr/share/rpm-helper/add-service virtualbox 1 virtualbox
[root at mmodem-pc x86_64]# rpm -Uvh
dkms-virtualbox-1.4.0-0.svn3059.1mde2007.2.x86_64.rpm
erro: o acesso ao dkms-virtualbox-1.4.0-0.svn3059.1mde2007.2.x86_64.rpm
falhou: Arquivo ou diretório não encontrado
[root at mmodem-pc x86_64]# rpm -Uvh
dkms-virtualbox-1.4.0-0.svn3059.2mde2007.1.x86_64.rpm
erro: Não consegui analisar o /mnt/nfs/acer/home: Permissão negada
A preparar... ########################################### [100%]
1:dkms-virtualbox ########################################### [100%]
+ /usr/sbin/dkms --rpm_safe_upgrade add -m virtualbox -v
1.4.0-0.svn3059.2mde2007.1
Creating symlink /var/lib/dkms/virtualbox/1.4.0-0.svn3059.2mde2007.1/source ->
/usr/src/virtualbox-1.4.0-0.svn3059.2mde2007.1
DKMS: add Completed.
+ /usr/sbin/dkms --rpm_safe_upgrade build -m virtualbox -v
1.4.0-0.svn3059.2mde2007.1
Preparing kernel 2.6.17-14mdv for module build:
(This is not compiling a kernel, just preparing kernel symbols)
Storing current .config to be restored when complete
Running Generic preparation routine
make mrproper....
using /proc/config.gz
make oldconfig.....
make prepare.....
Building module:
cleaning build area....(bad exit status: 2)
make KERNELRELEASE=2.6.17-14mdv -C /lib/modules/2.6.17-14mdv/build
M=/var/lib/dkms/virtualbox/1.4.0-0.svn3059.2mde2007.1/build.....
cleaning build area....(bad exit status: 2)
cleaning kernel tree (make mrproper).....
DKMS: build Completed.
+ /usr/sbin/dkms --rpm_safe_upgrade install -m virtualbox -v
1.4.0-0.svn3059.2mde2007.1
Running module version sanity check.
Good news! Module version 1.4.0 for vboxdrv.ko.gz
exactly matches what is already found in kernel 2.6.17-14mdv.
DKMS will not replace this module.
You may override by specifying --force.
+ /sbin/modprobe vboxdrv
+ :
+ /usr/share/rpm-helper/add-service virtualbox 2 virtualbox
+ /usr/sbin/dkms --rpm_safe_upgrade remove -m virtualbox -v
1.4.0-0.svn3059.1mde2007.1 --all
-------- Uninstall Beginning --------
Module: virtualbox
Version: 1.4.0-0.svn3059.1mde2007.1
Kernel: 2.6.17-14mdv (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
vboxdrv.ko.gz:
- Uninstallation
- Deleting from: /lib/modules/2.6.17-14mdv/kernel/3rdparty/vbox/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
DKMS: uninstall Completed.
------------------------------
Deleting module version: 1.4.0-0.svn3059.1mde2007.1
completely from the DKMS tree.
------------------------------
Done.
+ /usr/share/rpm-helper/del-service virtualbox 1 virtualbox
The intention in this upgrade was to only test and confirm this terrible bug,
since many times is needed to upgrade between releases to apply for example a
patch.
And as it can be seen the kernel module was removed, but how can that be
possible when the intention of a dkms install is to add a kernel module to
the active kernel tree?
regards,
--
Zé
Linux user #378762