[Pkg-dkms-maint] Bug#637281: same issue here with custom kernels build with make-kpkg
soete.joel at scarlet.be
Sun Aug 21 14:17:01 UTC 2011
Playing around to re-install stuff, I figure out that in '/var/lib/dkms/vboxhost' a dir 4.1.0 wasn't removed after the
installation of 4.1.2?
After I remove it, I can re-install image and headers pkg of my linux-3.0.3 compilation and dkms 2.1 reach to rebuild kernel
modules vboxhost and nvidia. With dkms 2.2, I still have to find why it doesn't run 'auto installation service' for this kernel?
On 08/21/2011 02:55 PM, Joel Soete wrote:
> Hello all,
> I use to compile my custom kernel (for my hw) which I build with make-kpkg.
> I also have to install nvidia-kernel-dkms (the unstable 280.13-1) and the latest virtualbox-4.1 4.1.2.
> All was working fine until yesterday when I build the latest linux kernel 3.0.3 for mu debian testing 64bits installation
> and install image and headers pkg and I got the same message:
> Error! Could not locate dkms.conf file.
> File: does not exist.
> For what is weird, today I do the same exercise on my debian 32bit installation without any issue but only with
> nvidia-kernel-dkms (the unstable 280.13-1) and without any virtualbox?
> I 'locate' some dkms.conf on my 32bit install i find some interesting: "/usr/src/nvidia-280.13/dkms.conf" and
> "/var/lib/dpkg/info/dkms.conffiles" and are the same as on my 64bit installation.
> To recover usage of my 64bit GUI and vbox, I re-install the stable 'dkms_18.104.22.168-5_all.deb' but have to 'dpkg-reconfigure
> nvidia-kernel-dkms' and I still have to find why vbox module failed to compile with linux-3.0.3 but that's another story.
More information about the Pkg-dkms-maint