Slackware :: VirtualBox Failing To Build Kernel Modules
Jan 10, 2010
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 was trying to install VirtualBox through the YaST > Software Management but it is not working, someone in the forum told me that I have to download the OSE version and do it manual way. Finally I am able to start up VB but not able to use the network connection. Thus I am trying to do this:
/etc/init.d/vboxdrv setup. I get this error:
[code]...
When I type dmesg, it shows me a bunch of info which I don't know what should look for. When I type modprobe vboxnetflt, I get the error: FATAL: Error inserting vboxnetflt (/lib/modules/2.6.37.1-1.2-default/updates/vboxnetflt.ko): Invalid module format. what should I do in order to get my VB to be able to connect to the internet?
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
my error when trying to run a VB (Virtualbox). Error as copied from error box. install the virtualbox-ose-modules package for your kernel and execute 'modprobe vboxdrv' as root. VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).
[code]...
I get this when trying to launch a VB after making one with wizzard.
I am trying to setup Slacware 13.1 x86_64 to a encrypted partition. I used the README_CRYPT.TXT howto : [URL] At the step when I create an initrd.gz I get this error: Quote: ERROR: No /lib/modules/2.6.33.4-smp kernel modules tree found for kernel "2.6.33.4-smp"
I tried to look into the directory and there was only modules under 2.6.44.3. So I tried to change the command into: Quote: mkinitrd -c -k 2.6.33.4 -m ext3 -f ext3 -r cryptroot -C /dev/sda2
This command was successful, but I don't know if this is alright. I made the changes in lilo.conf, add initrd = initrd.gz. This is all on unencrypted /boot partition. The boot=/dev/sda1 I also set for the unencrypted boot partition. When I boot the system I get a kernel panic:
Since new kernel 3.0 update I cannot rebuild vmware modules
Quote:
sudo vmware-modconfig --console --install-all Unable to initialize kernel module configuration
how to do that. Where do I insert the "CONFIG_LOCALVERSION" line.
Quote:
Same here. This seems to be due to the kernel version being "3.0" instead of "3.0.0". Recompiling the Kernel (and all modules based on it, e.g. nvidia) with CONFIG_LOCALVERSION=".0-ARCH" allows me to compile the modules and run VMware.
This has got me stumped. I expected to do /etc/init.d/vboxdrv setup after the upgrade from 11.3 to 11.4 but the command fails. The log is (it seems to repeat so I only quote the final bits to make it fit into the wordcount limit):
Code: make KBUILD_VERBOSE=1 -C /lib/modules/2.6.37.1-1.2-desktop/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
I opted to install my Linux Fedora distribution, in a SUN VM (Virtualbox). [URL] I have 2 questions:
My current max res available to select is 1024x768. Can I run at 1920x1200? My display indicated that it is 'Unknown'. I don't know if that is in on the deal, or not...
Second question: When installing VBOXADDITIONS_3.1.2_56127, I am getting the error: Building the VirtualBox Guest Additions kernel modules [FAILED]
If I am displaying the log correctly, it indicates: Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop Pictures are located here, in the EVGA Linux forum: [URL] I am new to both Linux, and Fedora.
My mission statement: To run Linux using the Fedora distribution, in a VM window under Windows 7 64bit Ultimate, with the ability for scripting using Bash, with the Perl programming language installed, and use Apache Tomcat to monitor both apps, and various VM installs, on numerous Servers via the internet.
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]...
I'm trying to install Sun VirtualBox Additions into Fedora 12 which is installed in VirtualBox running on top of Windows 7. As the Fedora install was originally a live distro which was then installed to the HD, it may be missing some essential files for compiling.
My attempt to install the VBoxLinux additions is incomplete and I can't get the full range of video displays. The largest is This is the error message: "Your system does not seem to be set up to build kernel modules".
Should I update Fedora to install all the updates available? I did find one webpage which gave an accurate list of files to install for this purpose but can't find it now.
I'm trying to install some wireless drivers, but apparently I don't have a /lib/modules/<kernel>/build directory, which is causing the Makefile to throw an error. Is there a specific place I should point the Makefile at?
I upgrade my slackware to slackware-current. But, when I look /etc/rc.d/rc.modules, it's still symlink to old kernel. Is this normal? Or i must change the symlink manually?
i want to do is dual boot windows, Slackware, and Debian. I don't care if i use lilo or grub, they are both equally familiar to me, just above nort. i have made attempts at editing the lilo.conf file, which said it had warnings but i didn't know how to view the warnings. It made it so i could select it, but when i did it booted the slack kernel with debian with no modules. get slack, debian and windows all running on my machine the way they're intended?
I upgraded to the latest -current just like always. I do the kernel packages last. This time, the machine failed to boot, telling me that it could not find the kernel modules. Well, rats.
I booted with a slackware dvd, passed the huge.s kernel, and booted into /dev/sda7, which is my main partition. I mounted /dev/sda7, and installed the kernel-modules-2.6.35.11 pkg. Rebooted, and got the same error?
I booted again with the dvd, mounted the partition, and navigated to /lib/modules - no 2.6.35.11 in there!
I would like to recompile my kernel to add few modules to it but I would like to keep my current configuration so as not to have troubles with missing drivers for my hardware and stuff.
My main computer (HP Pavilion 510n) only allows 512 meg ram.I've never built a kernel for Slackware.I'm running 13.0 :2.6.29.6 #1 Mon Dec 7 16:34:06 CST 2009 i686 Intel(R) Celeron(TM)CPU 1200MHz GenuineIntel GNU/Linux.Would there be any advantage to build a new kernel for 512 megs ram maximum? I do basic stuff with this: browse, email, video clips, music.
I tried to build the virtualbox 3.1.6 kernel using the files from slackbuilds.org and I got this error that says it cannot find the kernel include directory. My current kernel is 2.6.33.2 (slack 13.1).
I tried SOME_VAR=/usr/include --> (I forgot the exact variable name, but I used the variable name I saw in the error message) just a guess , but it didn't work of course.
Is it at /usr/src/linux-2.6.33.2/include or something like that? Or is there anything wrong with the slackbuild script?
I'm building an i7 based machine and I've been looking at kernel optimizations for it. One kernel option that I'm sketchy on and haven't been able to find a good resource for is for MAXIMUM NUMA NODES. The default is 6, but I'm not sure if this is best for my particular hardware or not and I'm not exactly sure what this is all about.
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.)
For some reason, when I click on the Slackbuild link for virtualbox-kernel (3.1.6) for virtualbox-kernel-3.1.6.tar.xz , it downloads as virtualbox-kernel-3.1.6.tar.tar. The file is misnamed. If it is renamed virtualbox-kernel-3.1.6.tar.xz , the SlackBuild works just fine.
I just rebuild the kernel for slackware 13, everything works, but root file system which is ext3 is mounted as ext2. Normally I've build ext3, ext4 and so on as modules, not in the kernel... but if I do this, then the kernel mounts the file system as ext2, which is build in the kernel. I also modified rc.modules so I can make sure that ext3,ext4,jbd are loaded, but it doesnt work.
I'm using VMWare Workstation 7.0.1 on my F12 x64 System with a self-made Kernel 2.6.32-7.The last days everything went fine, but since todays morning i can't run VMWare anymore.It tells me, that there are no Modules for my Kernel and when i try to build them i get the following error:
Code: Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmmon-only'
My new laptop works out of the box except for the video and the ethernet. For this, I have to use a later kernel than the Debian kernel (debian squeeze is currently 2.6.32). Upgrading to the new kernel (without moving to the testing dist itself) was pretty easy. I just installed linux-image-2.6.38-2-amd64 and linux-base from the testing distribution by manually downloading and using dpkg. After that, ethernet and video started working.
However, my virtualbox installation no longer works because the drivers do not match the kernel. I am used to this; whenever debian upgrades the kernel on me, I have to run "/etc/init.d/vboxdrv setup". This rebuilds the drivers. This failed for me, however, because it could not find the headers. So, I installed some more packages:
i am trying to build a EC2 image using VMBuilder and it keeps failing. i read and it seems that i need to install GRUB version 1 instead of 2. i tried to find documention on how to replace it but no luck. i am no expert in Linux.
I am building a minimized 6.2.2 linux kernel using slackware on a dinosaur of a computer: AMD Athlon +1700 Single Core processor, 1gig of DDR SDRAM. This is my first time compiling a linux kernel, so before I make any major mistakes, I could use some help in determining which filesystems I absolutely must enable support for. Ext2 is allready in.
