Fedora 9 recompile kernel???

[Arkolis]

I recently upgraded to fedora 9 and my virtual machine xp, will no longer run.

ive tried to recompile the kernel like i did in fedora 8 but it doesnt work. thanks

VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root.
VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).


Result Code:
0x80004005
Component:
Console
Interface:
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

[Whitee]

I'm having a hell of a time with Fedora 9 also...

/etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module [ OK ]
Recompiling VirtualBox kernel module [FAILED]
(Look at /var/log/vbox-install.log to find out what went wrong)
[root@gwhite-xp-2 kernels]# cat /var/log/vbox-install.log
which: no dkms in (/sbin:/usr/sbin:/bin:/usr/bin)
Makefile:127: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.


Can't seem to get the kernel source installed for
2.6.25-14.fc9.i686

ls /usr/src/kernels/
2.6.25.3-18.fc9.i686

is all I seem to be able to get...

Any sudgestions?

[Brian Jester]

Here's the solution:

Code: Select all

Step 1: Get the kernel-devel package (as well as a few others)

sudo yum install make automake autoconf gcc kernel-devel

Code: Select all

Step 2: sudo /etc/init.d/vboxdrv setup

Code: Select all

Step 3: Run the setup file for VirtualBox:

Code: Select all

Step 4: Add yourself to the “vboxusers” group:

su -
usermod -G vboxusers -a username
exit

5.) Run, and enjoy!

VirtualBox

hth,
-Brian

[Arkolis]

After a while of playing with it I got it to work,

although ironically fedora 9 says usermod command not found so i had to add it threw the users and groups thing.

Thanks.

[scottro]

For an explanation of that command not found see
http://home.nyc.rr.com/computertaijutsu/rhpath.html

(It comes up so frequently on Fedoraforums that I put up a page about it.)
Actually, you can also use gpasswd which is in /usr/bin, so it will be in your path with sudo or an su without the -.

gpasswd -a john vboxusers

[netlurker]

Thanks for the solution Brian, much simpler than it looked. Almost have my F9 box up to the functionality of F8 now.

[the4thchild]

I got a similar error message which was fixed by installing dkms:

Code: Select all

sudo yum install dkms

[FergatROn]

Excellent, thanks fellas. I had the same problem with my Fedora 9. I did the

Code: Select all

sudo yum install make automake autoconf gcc kernel-devel

And it seems the only one I was missing was "kernel-devel". After installing that the recompile was a piece of cake.

[gursoyklr]

Makefile:143: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Durdu.

problem continue

my system fedora 9

I installed
yum install make automake autoconf gcc kernel-devel
yum install dkms
yum install gcc
yum install make automake autoconf gcc kernel-devel
/etc/init.d/vboxdrv setup

just this not working>usermod -G vboxusers -a username from me how I can do?

[Sasquatch]

Update your system to the lastest packages, then reboot and make sure that you are booted in the latest available kernel. Check the versions of your kernel with the kernel-devel package, they must be the same.

[gursoyklr]

thanks

[root@gursoykiler gursoykiler]# yum install kernel-devel.i686
Loaded plugins: refresh-packagekit
Setting up Install Process
Parsing package install arguments
Package kernel-devel-2.6.27.15-78.2.23.fc9.i686 already installed and latest version
Nothing to do I didnt understand

[Sasquatch]

Are you running the i686 kernel, and is it that exact version too? If you run uname -a, you will get the kernel version information.

[mythink]

I am having same issue,
** Compiling vboxdrv
Makefile:140: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.

when check, /etc/init.d/vboxdrv
I believe the issue lies here:
find /lib/modules/`uname -r` -name "vboxdrv\.*" 2>/dev/null|grep -q vboxdrv

uname -r
2.6.9-67.0.0.0.1.ELsmp

cd /lib/modules/2.6.9-67.0.0.0.1.ELsmp
no vboxdrv listed here in the kernel files installing from Linux RHEL RPM: VirtualBox-2.2.2_46594_rhel4-1.i386.rpm
Downloaded from sun directly.

seems some files are to be added by the RMP then compiled with the kernel, any one have any ideas or resolution.

Thanks in advance.

[phe]

Hello,

I have the same problem.

Is your problem solved now?
How did you solved it ?

Originally I had F9 (kernel 2.6.26.6-79) running with Virtualbox 2.0.4.

After update of my kernel to 2.6.27.21-78.2.41 I updated also VB to 2.2.2.

But now my virtualbox will not start its machines.

When I go into /usr/bin/ and I start it from there I get followong result :

[root@f9 bin]# VirtualBox
VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",)
failed: /usr/lib/virtualbox/VirtualBox.so: undefined symbol: _ZN8QPainter10drawPixmapERK7QPointFRK7QPixmap
[root@f9 bin]#

I did :

Code: Select all

[root@f9 bin]# yum install gcc gcc-c++ make automake kernel-devel
Loaded plugins: downloadonly, refresh-packagekit
Setting up Install Process
Parsing package install arguments
Package gcc-4.3.0-8.i386 already installed and latest version
Package gcc-c++-4.3.0-8.i386 already installed and latest version
Package 1:make-3.81-12.fc9.i386 already installed and latest version
Package automake-1.10.1-2.noarch already installed and latest version
Package kernel-devel-2.6.27.21-78.2.41.fc9.i686 already installed and latest version
Nothing to do
[root@f9 bin]#

vbox-install.log :

Code: Select all

make KBUILD_VERBOSE=1 -C /lib/modules/2.6.27.21-78.2.41.fc9.i686/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
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.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.0
gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -isystem /usr/lib/gcc/i386-redhat-linux/4.3.0/include -D__KERNEL__ -Iinclude -I/u

Code: Select all

[root@f9 log]# rpm -qa | grep gcc | sort
gcc-4.3.0-8.i386
gcc-c++-4.3.0-8.i386
gcc-gfortran-4.3.0-8.i386
libgcc-4.3.0-8.i386

[root@f9 log]# rpm -qa | grep qt | sort
avahi-qt3-0.6.22-11.fc9.i386
dbus-qt-0.70-4.fc9.i386
pinentry-qt-0.7.4-5.fc9.i386
poppler-qt4-0.8.7-1.fc9.i386
qt3-3.3.8b-14.fc9.i386
qt3-designer-3.3.8b-14.fc9.i386
qt3-devel-3.3.8b-14.fc9.i386
qt-4.4.3-5.fc9.i386
qt-devel-4.4.3-5.fc9.i386
qt-mysql-4.4.3-5.fc9.i386
qtparted-0.4.5-18.fc9.i386
qt-x11-4.4.3-5.fc9.i386

[root@f9 log]# rpm -qa | grep '27.21'|sort
kernel-2.6.27.21-78.2.41.fc9.i686
kernel-devel-2.6.27.21-78.2.41.fc9.i686
kernel-firmware-2.6.27.21-78.2.41.fc9.noarch
kernel-headers-2.6.27.21-78.2.41.fc9.i386

[root@f9 log]# uname -a
Linux f9.localhost.localdomain 2.6.27.21-78.2.41.fc9.i686 #1 SMP Mon Mar 23 23:45:58 EDT 2009 i686 athlon i386 GNU/Linux

Someone any idea ?

Thanks,

phe