You are not logged in.
I installed Virtualbox, however I cannot launch any OS because the vboxdrv module doesn't exists for the latest kernel (I found another module for the 2.6.23 kernel); so the GUI says that I should execute this:
/etc/init.d/vboxdrv setup
However that file doesn't exists. I already tried to uninstall virtualbox and reinstalling from pacman, but still no luck.
What should I do? Is this a bug?
Thanks in advance.
Proud Ex-Arch user.
Still an ArchLinux lover though.
Currently on Kubuntu 9.10
Offline
Hi,
for the virtualbox-bin package, here is a patch:
--- vboxdrv/include/iprt/types.h 2007-10-18 19:07:37.000000000 +0200
+++ vboxdrv.new/include/iprt/types.h 2007-12-13 22:12:04.000000000 +0100
@@ -58,8 +58,9 @@
/*
* Kludge for the linux kernel:
* 1. sys/types.h doesn't mix with the kernel.
- * 2. Starting with 2.6.19 linux/types.h typedefs bool and linux/stddef.h
+ * 2. Starting with 2.6.19, linux/types.h typedefs bool and linux/stddef.h
* declares false and true as enum values.
+ * 3. Starting with 2.6.24, linux/types.h typedefs uintptr_t.
* We work around these issues here and nowhere else.
*/
# include <stddef.h>
@@ -69,8 +70,11 @@
# define bool linux_bool
# define true linux_true
# define false linux_false
+# define uintptr_t linux_uintptr_t
+# include <linux/autoconf.h>
# include <linux/types.h>
# include <linux/stddef.h>
+# undef uintptr_t
# undef false
# undef true
# undef bool
Apply this to the virtualbox code....runs here fine.
Offline
"IMPORTANT:
Anytime your kernel version changes due to upgrade, recompile, etc., you will need to rebuid the virtualbox kernel module using "vbox_build_module". This binary will be located in one of the following locations: /sbin, /bin, or /usr/bin and must be executed with superuser priveleges. After rebuilding the module, don't forget to load it with: modprobe vboxdrv!"
Just run /usr/bin/vbox_build_module as root. It worked here without any problems after the kernel update.
EDIT: Looking above, I seems that I was lucky!
Last edited by azleifel (2008-02-10 22:22:26)
Offline
Apply this to the virtualbox code....runs here fine.
I haven't tried it yet, but I want to be certain about how this is done. How and where should this patch be added?
Offline
upgrade to the latest version of virtualbox (1.5.4) and the module will compile well on 2.6.24
Give what you have. To someone, it may be better than you dare to think.
Offline
"IMPORTANT:
Anytime your kernel version changes due to upgrade, recompile, etc., you will need to rebuid the virtualbox kernel module using "vbox_build_module". This binary will be located in one of the following locations: /sbin, /bin, or /usr/bin and must be executed with superuser priveleges. After rebuilding the module, don't forget to load it with: modprobe vboxdrv!"Just run /usr/bin/vbox_build_module as root. It worked here without any problems after the kernel update.
EDIT: Looking above, I seems that I was lucky!
Nope, It doesn't exists.
Proud Ex-Arch user.
Still an ArchLinux lover though.
Currently on Kubuntu 9.10
Offline
upgrade to the latest version of virtualbox (1.5.4) and the module will compile well on 2.6.24
Happens that I just installed Virtualbox from pacman, so I really haven't used it before on Arch... and i guess that I have the latest version, so there must be something wrong with the package (maybe?)...
Proud Ex-Arch user.
Still an ArchLinux lover though.
Currently on Kubuntu 9.10
Offline
maybe because i use virtualbox_bin ?
Last edited by wonder (2008-02-11 17:38:35)
Give what you have. To someone, it may be better than you dare to think.
Offline
Offline
wonder wrote:maybe because i use virtualbox_bin ?
I use the virtualbox-bin package, too. But without the patch the module won't compile. I'm using it on arch64.
This is curious. I have virtualbox_bin 1.5.4-4 installed (Arch64) and when I look in /opt/VirtualBox-1.5.4/src/include/iprt/types.h I find that it already has that patch applied?
Offline
For me it went fine. Arch i686 and VirtualBox bin version. So no need for any patch here, as from what I can see it's not implemented in the build.
Offline
azleifel wrote:"IMPORTANT:
Anytime your kernel version changes due to upgrade, recompile, etc., you will need to rebuid the virtualbox kernel module using "vbox_build_module". This binary will be located in one of the following locations: /sbin, /bin, or /usr/bin and must be executed with superuser priveleges. After rebuilding the module, don't forget to load it with: modprobe vboxdrv!"Just run /usr/bin/vbox_build_module as root. It worked here without any problems after the kernel update.
EDIT: Looking above, I seems that I was lucky!
Nope, It doesn't exists.
Isn't hindsight wonderful. The unasked question was: What exact virtualbox package did you install?
Offline
I just noticed that I have the very same problem.
I installed the PUEL version from AUR awhile back. Do I have to re-install a new version from AUR again for the new kernel?
R.
Offline
I just noticed that I have the very same problem.
I installed the PUEL version from AUR awhile back. Do I have to re-install a new version from AUR again for the new kernel?R.
virtualbox-modules 1.5.4-1 has been flagged as out of date in AUR, so I guess that it's going to be just a matter of time before an updated version appears.
Offline
I modified the PKGBUILD for the virtualbox-modules package. Simply change the kernel version from 2.6.23-ARCH to 2.6.24-ARCH (or whatever kernel you have installed) and makepkg.
That's the beauty of ABS.
Who is this doin' this synthetic type of alpha beta psychedelic funkin'?
Offline
I modified the PKGBUILD for the virtualbox-modules package. Simply change the kernel version from 2.6.23-ARCH to 2.6.24-ARCH (or whatever kernel you have installed) and makepkg.
That's the beauty of ABS.
Where exactly do we change the kernel version. There are 5 files inside the AUR download (the latest available) including a "patch" file -vboxnet.patch- that according to some postings should make the upgrade work (but it does not for me) and I cannot find anywhere a reference to the kernel that I can alter.
Am I looking at the wrong files, is there another AUR download that I should be using?
Thanks.
R.
Offline
virtualbox-modules goes with the virtualbox-ose package and it appears to now be updated for kernel 2.6.24. For the non-gpl, puel, vitrtualbox_bin (or whatever you call it) version I believe you need the patch above.
Last edited by tesjo (2008-02-13 04:49:51)
Offline
virtualbox-modules goes with the virtualbox-ose package and it appears to now be updated for kernel 2.6.24. For the non-gpl, puel, vitrtualbox_bin (or whatever you call it) version I believe you need the patch above.
Completly right!
Offline
Well ... that's most interesting. I downloaded the latest PUEL version and it fails to compile with the following error:
==> Making package: virtualbox_bin 1.5.4-4 (Wed Feb 13 07:32:25 EST 2008)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Missing Dependencies:
-> patch
==> ERROR: Could not resolve all dependencies.
The error does not make sense to me since (a) I had the application running until up the latest kernel update, so I cannot have missing dependencies and (b) I now downloaded the latest AUR version where the patch file was added.
Any ideas?
Thanks.
R.
Offline
Offline
Daniel,
Sorry if I sound a little dumb, I'm not really familiar with AUR. I downloaded the latest version and the patch file is there. The error I posted is issued when I use the latest version of VirtualBox, which includes that patch file, to make the package. Or you mean to say that I have to copy the contents of that file somewhere?
Thanks for the help.
R.
Offline
No, you don't have to copy any file anywhere. You have everything in one directory and run makepkg (that is what I understand from your last post). But to build the package you need the package "patch" from the [core] repository. So just install the package patch with "pacman -S patch" and run makepkg again in the directory with the files of virtualbox, which you have download from the AUR.
Offline
I think that's where the confusion is. When I got the package from AUR it had:
-rw-r--r-- 1 ralvez users 217 2008-01-08 15:58 interfaces
-rw-r--r-- 1 ralvez users 3596 2008-01-20 11:38 PKGBUILD
-rwx------ 1 ralvez users 174 2007-12-30 04:23 vbox_build_module
-rw-r--r-- 1 ralvez users 2384 2007-12-30 07:39 vbox.install
-rw-r--r-- 1 ralvez users 2179 2007-12-30 07:31 vboxnet.patch
So the patch file is there (in bold text) ... and is not executable is a text file. That's why I'm asking if I have to do something with it to make the whole thing work.
Since it is just a plain text file if I try to use it as an upgrade patch it fails with error:
loading package data... error: error while reading package vboxnet.patch: Unrecognized archive format: Invalid or incomplete multibyte or wide character
error: failed to add target 'vboxnet.patch'
So, I'm stuck. I see no way to solve the problem.
R.
Edit: On re-reading your post I wonder what package from core are you referring to? I was under the impression that when we use AUR we are "fetching" files not from core but form the AUR source.
Am I wrong?
Last edited by ralvez (2008-02-13 22:50:31)
Offline
Daniel,
Never mind. I figured it out. I tested for pamcan -S patch .... and sure enough I got it!!
Then the rest was easy. Thanks for your help!!
R.
Offline
"makepkg -s" will download missing dependencies from the repositories and install them for you. Just a tip.
Who is this doin' this synthetic type of alpha beta psychedelic funkin'?
Offline