So I worked around the bug the old fashioned way.
Purged dkms completely from my system, then removed the folder /var/lib/dkms then reinstalled my videocard and wireless network adapter drivers Then reconfigured virutalbox
1640 sudo aptitude purge dkms 1641 cd ~ 1642 sudo rm -r /var/lib/dkms 1643 sudo aptitud install dkms 1644 sudo aptitude install dkms 1645 dkms status 1646 sudo dpkg-reconfigure virtualbox-3.2 1647 dkms status
bcmwl, 5.60.48.36+bdcom, 2.6.32-24-generic, x86_64: installed fglrx, 8.723.1, 2.6.32-24-generic, x86_64: installed vboxdrv, 3.2.6, 2.6.32-24-generic, x86_64: installed vboxnetadp, 3.2.6, 2.6.32-24-generic, x86_64: installed vboxnetflt, 3.2.6, 2.6.32-24-generic, x86_64: installed
Question remains. Why does dkms get stuck, holding on to old entries, without cleaning them up?
So I worked around the bug the old fashioned way.
Purged dkms completely from my system, then removed the folder /var/lib/dkms
then reinstalled my videocard and wireless network adapter drivers
Then reconfigured virutalbox
1640 sudo aptitude purge dkms
1641 cd ~
1642 sudo rm -r /var/lib/dkms
1643 sudo aptitud install dkms
1644 sudo aptitude install dkms
1645 dkms status
1646 sudo dpkg-reconfigure virtualbox-3.2
1647 dkms status
bcmwl, 5.60.48.36+bdcom, 2.6.32-24-generic, x86_64: installed
fglrx, 8.723.1, 2.6.32-24-generic, x86_64: installed
vboxdrv, 3.2.6, 2.6.32-24-generic, x86_64: installed
vboxnetadp, 3.2.6, 2.6.32-24-generic, x86_64: installed
vboxnetflt, 3.2.6, 2.6.32-24-generic, x86_64: installed
Question remains. Why does dkms get stuck, holding on to old entries, without cleaning them up?