You are not logged in.
Pages: 1
Hello I just compile my new kernel, and am having trouble installing virtual box when I run vboxdrv setup rc.d gives me the following error
:: Unloading VirtualBox kernel modules [DONE]
:: Recompiling VirtualBox kernel modules [BUSY]
Look at /var/log/vbox-install.log to find out what went wrong
Look at /var/log/vbox-install.log to find out what went wrong
Look at /var/log/vbox-install.log to find out what went wrong
Look at /var/log/vbox-install.log to find out what went wrong
[DONE]
:: Reloading VirtualBox kernel modules [DONE]
the system is first installed, so apart from the kernel is all pretty standard, I use gnome 3.
I copy the file / var / log that says what the problem is, but I do not know how to fix that, someone can help me?
Makefile:172: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
cp: cannot stat `/tmp/vboxdrv-Module.symvers': No such file or directory
Makefile:94: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
cp: cannot stat `/tmp/vboxdrv-Module.symvers': No such file or directory
Makefile:90: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
cp: cannot stat `/tmp/vboxdrv-Module.symvers': No such file or directory
Makefile:94: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
Last edited by mrtnfs (2011-07-22 14:54:27)
Offline
do uname -r and paste the output
also pacman -Q kernel26
Give what you have. To someone, it may be better than you dare to think.
Offline
[martin@arch ~]$ uname -r
2.6.39.3-vanilla
[martin@arch ~]$ pacman -Q kernel26
kernel26 2.6.39.3-1
Offline
ok, see the problem? don't know how you installed that but the headers are missing
i don't get it what's the point of using that kernel. our default kernel is vanilla now
Last edited by wonder (2011-07-20 17:08:56)
Give what you have. To someone, it may be better than you dare to think.
Offline
the name "vanilla" I put it to differentiate it from the "ARCH", simply because I wanted to learn how to compile a kernel. apart from that I remove some things that I didnt needed
I did not know that the arch was vanilla kernel in the wiki I read that was patched
anyway do not really understand the problem. What should I do to run a custom kernel with virtualbox?
(this is the first time I mess with the kernel, excuse the ignorance)
Last edited by mrtnfs (2011-07-20 17:18:06)
Offline
@mrtnfs nothing. vboxdrv works fine with all kernels but your kernel is just bugged/broken. ask the maintainer of that kernel package into aur
Give what you have. To someone, it may be better than you dare to think.
Offline
the kernel source I downloaded from the www.kernel.org, maybe is misconfigured .. but thanks anyway
Offline
don't you need the kernel headers to be able to compile the vbox modules? So since you have a custom kernel, you will need the appropriate custom kernel headers.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
and where I get the kernel headers I need? the only one in the repositories is that I have installed, also search the AUR
Offline
just compile another kernel, download the sources from the official website, but this time use the .config file for archlinux kernel, but I keep getting the same error, so I assume it is not a kernel bug if an error in the some configuration file that dictates which direction to turn the module, any ideas please?
Offline
You must have had sources if you compiled a vanilla kernel in the first place.
How did you compile your kernel (makepkg, manual)?
Where do you keep the kernel sources? You didn't remove them by any chance, did you?
EDIT: Now that I think of it you must have had kernel headers as well, if you compiled your own kernel.
If you did delete the sources, don't worry. Those ~500M sitting there seemingly with no puprose was just begging to be removed, atfer my first kernel compilation...
Last edited by lukaszan (2011-07-21 13:51:16)
Offline
do a ls /usr/src/
Give what you have. To someone, it may be better than you dare to think.
Offline
I use the script found on the wiki, and I think the commands used are "make menuconfig", then do "make bzImage", "make modules" "make modules_install" and then use "mkinitricpio"
I do not delete the sources (when you say the sources you mean the files in / usr / src rigth?), but i do change its name because the script creates a folder called linux-2.6.39.3-KNL, I change the name to linux-2.6.39.3-vanilla. I did this only because if installing nvidia-all (AUR) creates the modules in a folder that is not the kernel folder (the folder would be / lib/modules/2.6.39.3-KNL and kernel modules are in / lib/modules/2.6.39.3-vanilla. was the way I found to make it work nvidia)
now I can not do ls / usr / src because I'm reinstalling, I get frustrated enough and I'll try it all again, I will try to compile the kernel without the script, although I do not see that changing much
but the moment I wrote the post my / usr / src tar.bz2 file should contain the download, and two folders: linux-6.2.39-ARCH and linux-2.6.39.3-vanilla
PS: my / lib / modules / dir at the time of the post also contained 2 folders: 2.6.39.3-vanilla and 2.6.39-ARCH
Last edited by mrtnfs (2011-07-21 16:01:20)
Offline
Yeah, you have some symlinks in /lib/modules/aaa pointing to sources in /usr/src/bbb. If you change the name of bbb after compilation you mess them up and sources won't be found.
Don't know how that script of yours works, but for manual kernel compilation:
- 'bbb' should be 'linux' (you can make it a symlink linux -> linux-2.6.39.3 or whatever it is now), although technically it could be anything.
- 'aaa' will be created automatically when you do 'make modules_install', and it will reflect the name of your kernel 'uname -r'
Offline
ready, that was the problem, rename the sources .. thanks
Offline
Pages: 1