I had an issue with the module build for vbox 3.1.2 breaking on the latest kernel ( /etc/rc.d/rc.vboxdrv setup ). Apparently the issue is that a kernel header (autoconf.h ) has changed its location in the module tree and hence the issue.
2 options:
1. upgrade to 3.1.4
2. create a symlink as follows
cd /usr/src/linux/include/linux
ln -s ../generated/autoconf.h autoconf.h
I am using the 13.1 build scripts from slackbuilds.org. I modified the scripts to build 3.2.12 rather than 3.2.10.
In 13.1 the main VirtualBox 3.2.12 OSE package built and installed without errors. The VirtualBox GUI starts without errors.
Running the virtualbox-kernel-mksrctarball.sh script built a kernel source package without errors.
Yet the VirtualBox kernel module won't build. I receive the following error:
Code:
]*** Building 'vboxdrv' module ***
make[1]: Entering directory `/dev/shm/virtualbox-kernel-3.2.12/vboxdrv'
make KBUILD_VERBOSE= -C /lib/modules/2.6.33.11-smp-2/build SUBDIRS=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv SRCROOT=/dev/shm/virtualbox-kernel-3.2.12/vboxdrv modules
[Code].....
I had no problems up to the newest kernel version. But for 2.6.40-4 akmods fails to build the kmod with the following error:
Code:
Building RPM using the command '/usr/bin/akmodsbuild --target x86_64 --kernels 2.6.40-4.fc15.x86_64 /usr/src/akmods/VirtualBox-OSE-kmod.latest'
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/akmodsbuild.yob64XwN/BUILD/VirtualBox-OSE-kmod-4.0.4/_kmod_build_2.6.40-4.fc15.x86_64/vboxnetflt/vboxnetflt.mod.o
LD [M] /tmp/akmodsbuild.yob64XwN/BUILD/VirtualBox-OSE-kmod-4.0.4/_kmod_build_2.6.40-
[Code]...
If others are have the problem of VirtualBox failing to build the kernel modules with kernel 2.6.32 try this :-
1. Install VirtualBox and watch as the kernel modules fail to compile.
2. Change the line
Code:
KFLAGS += -DRT_ARCH_AMD64
TO
Code:
KFLAGS += -DRT_ARCH_X86_64
In the following files :-
Code:
Line 231 /opt/VirtualBox/src/vboxdrv/Makefile
Line 170 /opt/VirtualBox/src/vboxnetadp/Makefile
Line 174 /opt/VirtualBox/src/vboxnetflt/Makefile
3. Run /etc/rc.d/rc.vboxdrv setup
You will now have a working VirtualBox setup. NB This is written purely from the standpoint of using the Closed source version of VB not the OSE version.
I started slax in cli mode and tried to install nvidia driver before running X but it won't install. My log:
Code:
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Sun Jan 10 04:21:14 2010
option status:
license pre-accepted : false
Update : false
Force update : false
Expert : false
uninstall : false
Driver info : false ....
ERROR: Unable to build the NVIDIA kernel module.
ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details.
I download "VirtualBox-3.1.2-56127-Linux_amd64.run" and installed it, and got a messages like this " virtualbox have been installed successfully in my system", but when I run virtualbox, I've been told "/etc/init.d/vboxdrv setup" something like that. And I run virtualbox in terminal, got this:
Warning: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (2.6.29.6) or it failed to load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until this problem is fixed.
I run "/etc/rc.d/rc.vboxdrv start" as a root, got messages like this :
Starting VirtualBox kernel module ...failed!
(modprobe vboxdrv failed.)
I installed openSUSE 11.2 on virtualbox. My host is windows 7. I tried to install the guest additions, but i get an error saying
Code:
Building VirtualBox Guest Additions Kernel Modules...Failed
(Your system does not seem to be set up to build kernel modules)
How should i go about to let my system build kernel modules?
I'm running Virtualbox from the Sun website (need the USB support) and it breaks after each kernel update.The problem is that I installed a lot of Ubuntu systems for transitioning windows users with Windows in virtualbox to ease the migration but I have to rerun vboxdrv setup after each kernel patch.
View 2 Replies View RelatedMy VMWare Player was working fine After updating the kernel it is throwing the error "Unable to build kernel module" my kernel is 2.6.40-4.fc15.x86_64 what to do?
View 2 Replies View RelatedI can't get the nVidia kernel module built. Each time DKMS runs to install it (I'm trying to install it with the nvidia-kernel-legacy-173xx-dkms package on ), the build fails with a different error. Here is an exemple /var/lib/dkms/nvidia/173.14.27/build/make.log (I have a geForce FX 5200 on the computer I'm trying to install the nVidia driver):
DKMS make.log for nvidia-173.14.27 for kernel 2.6.32-5-686 (i686)
dimanche 24 avril 2011, 17:28:09 (UTC+0200)
make: entrant dans le r©pertoire /var/lib/dkms/nvidia/173.14.27/build
[code]....
That's it guys. I have successfully installed the proprietary ati drivers in past 6.34 and 6.35 kernels but not in latest .6.36. I'm wondering if this have something to do with compatibility or not.
Installation log shows me some errors I can't recognize:
Code:
I'm trying to debug a module I programmed but I don't want to do it on the running host but against UML (don't want to reboot every 5 minutes).
The UML kernel I downloaded is 2.6.38.2. I have already downloaded the ubuntu kernel headers for this version (they belong to natty though I'm running maverick.... when I installed the .deb file with dpkg I had no problem at all).
Now I'd like to build said module against these headers. How can I do it?
Here's the makefile for my module code...
I have a fresh installation of Fedora14_x64 and after that I have updated the OS also.
Then I have installed VMware-Player-3.1.2-301548.x86_64.
All the installation procedure has completed successfully without any error.
But when I am going to run VMWare It is throwing some error.
I am attaching all the needed screenshot and log file also.
before i get a lot of annoyed responses, I did check the forum and found a couple older previous threads on this topic, but they don't seem to really explain any real solutions to the problem im having.Here's the story- I was looking around for instructions and found this "howto guide" on installing nvidia display driver [URL]I went through the steps he listed:
downloaded the driver packages, install the dependencies from the shell, and then i pressed CTRL+ALT+F2 to get out of X and into text mode. I stopped my gdm with the command: sudo /etc/init.d/gdm stopand then i tried to install the driver using: sudo sh (on my NVIDIA driver- his version was a bit outdated compared to the one I downloaded)But here is where the problem starts, as I go through the installation process and click yes, i reach the "progress bar" then the screen says "unable to build the NVIDIA kernel module". and then it just exits. What is going on here? Am I missing some other package or file?
I have downloaded latest version of sun vm virtual box foe Fedora 13 x64. After installing and creating a VM when I want to start vm I got this error. And when I enter this command on terminal :
/etc/init.d/vboxdrv setup
I get this error:
Code:
[root@localhost arash]# /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)
Log file:
Code:
[root@localhost arash]# cat /var/log/vbox-install.log
Makefile:159: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
[root@localhost arash]#
I am new to fedora core and needs desperate help.Now what i can notice is the kernel files doesnot match. will this makes a difference..what do you think ? How can i make the VirtualBox kernel module status [OK] ?
View 5 Replies View RelatedI am trying to install atheros AR5007EG on my toshiba laptop -i figured out that best way to install this wireless card is through madwifi -while configuring madwifi i get this error
I am posting the output of different commands so you can understand better -i manually tried to link the build directories to kernel-source which failed - i am not sure exactly what kernel source is and how i can link to kernel source -
My output:
I generally check what updates are being installed. This time sadly I didn't and again this kernel had one missing module. VirtualBox-OSE stopped working. It had been working fine with other upgrades. No it's not a problem with dkms or other stuff. This kernel doesn't have vboxdrv module like other kernels...i verified it...
[Code]...
The 2.6.38.8 version doesn't have vboxdrv module!....hence again I have to roll back to older kernel. So before blindly upgrading....read this message!
I have been having some problems with virtualbox starting. So here is the issue: When I start a VM I get the following: Code: Kernel driver not installed (rc=-1908). The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. reinstall the kernel module by executing
[code]...
I am seeing quite a few entries about the usb. I am not sure if that is common or if its unrelated. I am running x86 11.3, and virtualbox 4.0.4 I have tried to uninstall, and even go back to 3.2
I just up-graded to the latest version of the stable 11.4 64bit kernel on my laptop and it appears that the repositories have not compiled the VirtualBox driver module for the current kernel ... When I make /vboxdrv setup the message is:
Recompiling VirtualBox vboxadd kernel module, NOT. It has been packaged
I think this means that the installed module will not recompile has it was packaged. My kernel version is the lattest :
2.6.37.6-0.5-1
And my VirtualBox was installed from the Virtualization repos (4.0.8.11-1) even made the Vendor change and all. The version Before the lattest (4.0.4-1.6) did not work either. With the same problem. It is very easy to install VirtualBox from the Sun site and every time there is a Kernel up-date one can always make /etc/vboxdrv setup.
I'm trying to get Virtualbox up an running. So I have added virtualbox in my repo and added the key, looks fine so far. but afeter downloading I get this:
VirtualBox-3.0.8_53138_rhel5-1.x86_64
Creating group 'vboxusers'. VM users must be member of that group!
No precompiled module for this kernel found -- trying to build one. Messages
emitted during module compilation will be logged to /var/log/vbox-install.log.
Compilation of the kernel module FAILED! VirtualBox will not start until this problem is fixed. Please consult /var/log/vbox-install.log to find out why the kernel module does not compile. Most probably the kernel sources are not found. Install them and execute /etc/init.d/vboxdrv setup as root.
I'm trying to install the nVidia driver for a fresh Installation of OpenSUSE 11.4 (32-bit) but I'm running into some issues. I followed the instructions (SDB:NVIDIA the hard way - openSUSE) using the driver binary mentioned in the workaround link (NVIDIA DRIVERS 256.53 Certified) but the installer fails while building the kernel module with the following errors:
Code:
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Sun Mar 13 17:32:56 2011
[code]....
I am running Lenny and using VirtualBox OSE 1.6.6. In order to try squeeze I installed it in a VM. I tried to install Guest Additions also, but i get this error:
VirtualBox 1.6.6 Guest Additions installation
Building the VirtualBox Guest Additions kernel module...
Building the shared folder support kernel module...
Unable to build the kernel module.
I checked what /var/log/vboxadd-install.log had to say:
/usr/src/linux-headers-2.6.32-5-common/include/net/neighbour.h:115: error: variably modified a at file scope
/tmp/vbox.0/utils.c: In function 'sf_path_from_dentry:
[code].....
I tried with 3 versions of the kernel 2.6.32-5-686,2.6.32-5-484,2.6.32-3-686 but I cannot get it to work using any of them. Also I tried to install version 2.6.30-2-686 but I couldn't since synaptic said that it Depends: linux-kbuild-2.6.30 but it is not installable.
My problem is that it won't load the dkms module and Virtualbox will not run.
View 14 Replies View Relatedusing slakware64 13.1 modified sbo slackbuild for latest version..
View 7 Replies View RelatedI'm trying to build/install KDE 4.5.4, but I run into problems with the bindings package. Build fails with the following:
[Code]....
I'm building using the KDE slackbuild from sources dir, with the new KDE packages. edit: Well I decided to just take the risk of a not working KDE and commented out the bindings package. All other packages build fine. After this I crossed my fingers and rebooted, KDE loaded up. I gave the bindings package another go, and to my surprise it did build now. Got KDE up to date and it seems to be running fine.
here is the output:
[code]...
NVIDIA x86-256.44 fails to build against 2.6.36
I have installed Virtualbox PUEL in 64-bit 11.3. This is a fresh install. My computer has an onboard nvidia 8300GS graphics card. I do not think this is related to the issue. I added the virtualbox repository and installed the program via yast. when I type "VirtualBox" in the terminal I get the following output:
[code]...
I can not get gtkimageview-1.6.4 to build in current. It fails with a number of errors of type:
Code:
gtkanimview.c: In function 'gtk_anim_view_get_type':
/usr/include/glib-2.0/glib/gthread.h:339: error: dereferencing pointer 'value_location.1' does break strict-aliasing rules
/usr/include/glib-2.0/glib/gthread.h:339: note: initialized from here
I am running Lucid Lynx kernel 2.6.32.24. Soon after the latest kernel update I noticed that Virtualbox would not launch when I clicked on the icon. I have searched the Internet for days, tried numerous possible fixes, over hours of effort, but can't get it working at all. Ubuntu Lucid runs great!! There are no errors just a few blinks of the hard drive indicator and nothing. Is there anyone out there that has seen this same issue?
View 9 Replies View Related