Not quite that easy, it seems.

There is no device /dev/vboxdrv any more.  Running /etc/init.d/vboxdrv setup 
give the following errors:

cp: missing destination file operand after `/tmp/vbox.1/Module.symvers'
Try `cp --help' for more information.
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.24-18-generic/build 
SUBDIRS=/tmp/vbox.1 SRCROOT=/tmp/vbox.1 modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.24-18-generic'
test -e include/linux/autoconf.h -a -e include/config/auto.conf || (            
\
        echo;                                                           \
        echo "  ERROR: Kernel configuration is invalid.";               \
        echo "         include/linux/autoconf.h or include/config/auto.conf 
are missing.";      \
        echo "         Run 'make oldconfig && make prepare' on kernel src to 
fix it.";  \
        echo;                                                           \
        /bin/false)
mkdir -p /tmp/vbox.1/.tmp_versions ; rm -f /tmp/vbox.1/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.1
  
gcc -m32 -Wp,-MD,/tmp/vbox.1/linux/.SUPDrv-linux.o.d  -nostdinc -isystem 
/usr/lib/gcc/i486-linux-gnu/4.2.3/include -D__KERNEL__  -Iinclude  -include 
include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs 
-fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -O2 
-pipe -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 
 -march=i586 -mtune=generic -ffreestanding -maccumulate-outgoing-args   
-Iinclude/asm-x86/mach-default -fomit-frame-pointer -g  -fno-stack-protector 
-Wdeclaration-after-statement -Wno-pointer-sign   
-I/lib/modules/2.6.24-18-generic/build/include  -I/tmp/vbox.1/ 
-I/tmp/vbox.1/include -I/tmp/vbox.1/r0drv/linux -D__KERNEL__ -DMODULE 
-D__LINUX__ -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DCONFIG_VBOXDRV_AS_MISC 
-D__X86__   -DMODULE -D"KBUILD_STR(s)=#s" 
-D"KBUILD_BASENAME=KBUILD_STR(SUPDrv_linux)"  
-D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o 
/tmp/vbox.1/linux/.tmp_SUPDrv-linux.o /tmp/vbox.1/linux/SUPDrv-linux.c
In file included from /tmp/vbox.1/include/iprt/types.h:55,
                 from /tmp/vbox.1/include/VBox/types.h:25,
                 from /tmp/vbox.1/SUPDRV.h:31,
                 from /tmp/vbox.1/linux/SUPDrv-linux.c:24:
include/linux/types.h:40: error: redefinition of typedef ‘uintptr_t’
/tmp/vbox.1/include/iprt/stdint.h:119: error: previous declaration 
of ‘uintptr_t’ was here
In file included from include/linux/thread_info.h:33,
                 from include/linux/preempt.h:9,
                 from include/linux/spinlock.h:49,
                 from /tmp/vbox.1/SUPDRV.h:84,
                 from /tmp/vbox.1/linux/SUPDrv-linux.c:24:
include/linux/bitops.h:6:1: warning: "BIT" redefined
In file included from /tmp/vbox.1/include/VBox/cdefs.h:24,
                 from /tmp/vbox.1/SUPDRV.h:30,
                 from /tmp/vbox.1/linux/SUPDrv-linux.c:24:
/tmp/vbox.1/include/iprt/cdefs.h:979:1: warning: this is the location of the 
previous definition
make[2]: *** [/tmp/vbox.1/linux/SUPDrv-linux.o] Error 1
make[1]: *** [_module_/tmp/vbox.1] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.24-18-generic'
make: *** [vboxdrv] Error 2
/var/log/vbox-install.log (END) 

Any more suggestions?  I tried a complete reinstall of 1.4.0, but did not make 
any difference.

On June 7, 2008 05:03:05 pm Erwin Mueller wrote:
> On Saturday 07 June 2008 22:21:13 Mike Jeays wrote:
> > I have been using Vbox 1.4.0 with Ubuntu's Gutsy Gibbon as host, with
> > great success running XP as a guest.  Yesterday, I upgraded the host to
> > Hardy Heron, and VirtualBox no longer works - I get:
> >
> > "VirtualBox kernel driver not installed. The vboxdrv kernel module was
> > either not loaded or /dev/vboxdrv was not created for some reason. Please
> > install the virtualbox-ose-modules package for your kernel, e.g.
> > virtualbox-ose-modules-generic.."
>
> You need to load the vboxdrv
> ~# modprobe vboxdrv
>
> If you get an error you can check if /dev/vboxdrv is readable by the group
> vboxusers and that your User is in this goup.
>
> ~$ ls -l /dev/vboxdrv
> crw-rw---- 1 root vboxusers 10, 59 2008-06-07 13:03 /dev/vboxdrv
>
> ~$ groups
> xxx xxx vboxusers xxx xxx
>
> If it's not you can fix it:
> ~# chmod g+r+w /dev/vboxdrv && chown root.vboxusers /dev/vboxdrv
> ~# adduser user vboxusers
>
> Than re login.
>
> _______________________________________________
> vbox-users mailing list
> [email protected]
> http://vbox.innotek.de/mailman/listinfo/vbox-users



-- 
Mike Jeays
http://www.jeays.ca

_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users

Reply via email to