[Solved] Building vboxdrv with custom kernel

Question

I noticed a Loading Modules     [FAIL] during boot yesterday so I decided to investigate it.
[siegemachine@Siege-LapLinux ~]$ sudo modprobe vboxdrv
Password:
FATAL: Module vboxdrv not found.
[siegemachine@Siege-LapLinux ~]$ sudo /etc/rc.d/vboxdrv setup
:: Removing VirtualBox kernel modules [DONE]
:: Compiling VirtualBox kernel modules [BUSY] Look at /tmp/vbox-install.log to find out what went wrong
Look at /tmp/vbox-install.log to find out what went wrong
Look at /tmp/vbox-install.log to find out what went wrong
[siegemachine@Siege-LapLinux ~]$ yaourt -S kernel26-headers
warning: kernel26-headers-2.6.39.1-1 is up to date -- reinstalling
Now I read in this forum
https://bbs.archlinux.org/viewtopic.php?id=107733
that if I have a custom kernel then I have to have the custom kernel-headers to go with it in order to build the virtualbox driver module.  The problem is the kernel I got is from the AUR
[siegemachine@Siege-LapLinux ~]$ yaourt -Qi kernel26-kamal
Name : kernel26-kamal
Version : 2.6.39.1-1
And I've tried searching the AUR and there doesn't appear to be any kernel-headers to match the kernel.  When I build the kernel should I build it with the regular name and not with -kamal on the end of the kernel and see if that would work for building the virtualbox modules? Or should I boot off the regular kernel (I have both) and build it there, then reboot on this kernel and see if it works? Or finally, do I need to somehow build the kernel-headers for this kernel myself, install them, and then build the modules?
Last edited by SiegeMachine (2011-06-24 03:47:57)

Answer 1

Aha well my friend noticed in the PKGBUILD for kernel26-kamal actually builds the kernel headers for that kernel but it doesn't isntall them so I just downloaded the PKGBUILD and built it myself again with makepkg instead of using yaourt then I could install the header package and built the module after.  In the end all is good.