[Pkg-virtualbox-devel] Bug#563073: (no subject)

Mike stuff at mikepalmer.net
Fri Jan 8 20:49:22 UTC 2010


I noticed the same problem with dkms. It seems that there is something 
leaving behind kernel modules every time it updates. I removed/purged 
virtualbox-ose-dkms and re-installed only to find this in dmesg:

vboxnetadp: disagrees about version of symbol module_layout

I purged again, went and looked in:

/lib/modules/2.6.32-trunk-amd64/updates/dkms

Only to find vboxnetadp.ko and vboxnetflt.ko were still sitting in there 
even though the package was purged and no kernel modules should have 
existed on the disk. Removing those by hand and re-installing 
virtualbox-ose-dkms fixes the problem and I can now use virtualbox 
again. Seems like something is missing on the post uninstall or dkms 
purge scripts but I haven't had a chance to go find out what 
script/system should be removing these things. Still new to dkms and the 
rules about how its supposed to be doing things. Should it be 
overwriting those files somehow or should it be removing then 
re-installing them after they are rebuilt? Its apparently not doing 
either with vboxnetadp.ko and vboxnetflt.ko  but is with vboxdrv.ko.

-Mike





More information about the Pkg-virtualbox-devel mailing list