Fedora Installation :: Errors For VirtualBox / Kernel Source For Kernel 184.108.40.206-99.fc Cannot Be Found?
Apr 21, 2010
Trying to install virtualbox in F12 but fails when recompiling kernel module. Output of vbox-install log is:
Attempting to install using DKMS
removing old DKMS module vboxdrv version 3.1.6
Deleting module version: 3.1.6
completely from the DKMS tree.
Creating symlink /var/lib/dkms/vboxdrv/3.1.6/source ->
DKMS: add Completed.
Error! Your kernel source for kernel 220.127.116.11-99.fc12.i686.PAE cannot be found
/lib/modules/18.104.22.168-99.fc12.i686.PAE/build or /lib/modules/22.214.171.124-99.fc12.
I installed the latest kernel liquorix (2.6.35) but when i want to install the Nvidia driver downloaded on the Nvidia website (256.53), i have an error message because Nvidia doesn't found the kernel source tree.
I install linux-image-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb, linux-headers-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb and build-essential. I don't understand why the installation doesn't works.
I'm just installed OpenSuse 11.3 (64) on a 30gb SSD, hoping to get virtualbox 4.0 running to virtualize an instance of Windows 7.I went through some pain with my Nvidia video card and actually getting vb to install, but through lots of searching and tinkering got here.I created a vm in the vb control panel, but when I go to start it I get:
Code: Failed to open a session for the virtual machine Win7Main. The virtual machine 'Win7Main' has terminated unexpectedly during startup with exit code 1.
I have installed the fedora 14, but there is no kernel source tree.I read the doc "building a custom kernel".But I don't want to rebuild a new kernel.I just want to install the source tree of current kernel.Could someone tell me the way?
uname -r prints 2.6.18-164.el5 Yum install kernel-headers/kernel-devel gives me 2.6.18-194 When trying to run virtualbox I get an error: Kernel Driver not installed: (rc=-1908) Please reinstall the kernel module by running "/etc/init.d/vboxdrv setup" as root...
/etc/init.d/vboxdrv setup Stopping VirtualBox kernel modules [OK] Uninstalling old VirtualBox DKMS kernel modules [OK] Trying to register the VirtualBox kernel modules using DKMS Error! Your kernel headers for kernel 2.6.18-164.el5 cannot be found at /lib/modules/2.6.18-164.el5/build or /lib/modules/2.6.18-164.el5/source. [FAILED] (Failed, trying without DKMS) Recompiling VirtualBox kernel modules [FAILED] (Look at /var/log/vbox-install.log to find out what went wrong)
I'm assuming the setup program is using the output from uname -r to determine the kernel, the problem is the kernel sources I've got from yum do not jibe with the uname value.
I get the following error message trying to install dazuko on xubuntu 10.04: "headers for target kernel version could not be found" But when I run sudo apt-get install linux-headers-$(uname -r), I get the message that I already installed the headers. My current kernel is 2.6.34-020634-generic
How can I install dazuko withouth having this problem??
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:
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/126.96.36.199-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'm trying to get a fedora guest running reliable smp under VirtualBox 3.0.6. The VirtualBox manual says "Some Linux distributions, for example Fedora, ship a Linux kernel configured for a timer frequency of 1000Hz. We recommend to recompile the guest kernel and to select a timer frequency of 100Hz." So I tried recompiling the kernel. Being a responsible lad, when it came to setting the kernel specs:
Code: # Polite request for people who spin their own kernel rpms: # please modify the "buildid" define in a way that identifies # that the kernel isn't the stock distribution kernel, for example, # by setting the define to ".local" or ".bz123456" # # % define buildid .local %define buildid .rim_for_vbox I've successfully built and installed kernel, headers and firmware:kernel-188.8.131.52-43.rim_for_vbox.fc11.x86_64.rpm kernel-firmware-184.108.40.206-43.rim_for_vbox.fc11.x86_64.rpm kernel-headers-220.127.116.11-43.rim_for_vbox.fc11.x86_64.rpm The system is working fine (well, so far). But trying to install the VirtualBox Guest Additions kernel add-ons still gives me
Please install the build and header files for your current Linux kernel. The current kernel version is 18.104.22.168-43.rim_for_vbox.fc11.x86_64. I'm pretty sure this is because my kernel doesn't match the development packagekernel-devel-22.214.171.124-43.fc11 (x86_64). So the key question is, how on Earth do I create a development package to match the responsibly-renamed kernel?
I have made a full install of Slack 13.37.0. When I try to run the installer of the NVIDIA GF 8400GS card (NVIDIA-Linux-x86-180.29-pkg1.run) downloaded from [URL], I receive an error message. It says that the kernel source cannot be indetified/found. /lib/modules/126.96.36.199-smp/source and .../build links to /usr/src/linux-188.8.131.52-smp, which contains the full kernel source (can be compiled), including the header .h files in include/linux. The same NVIDIA installer can be run successfully on my previous Slack 11.
Code: Building modules, stage 2. MODPOST 3053 modules WARNING: modpost: Found 60 section mismatch(es).To see full details build your kernel with:'make CONFIG_DEBUG_SECTION_MISMATCH=y' CC arch/x86/crypto/aesni-intel.mod.o[code]....
There is even much more error output but it looks like it is basically the same issue.
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.
I am trying to install the Nvidia Quadro NVS 110 169.04 drivers but am having issues during install. Prior to attempting my install I did install the kernel-devel rpm so it can compile. after running the RPM I get. Quote: No precompiled kernel interface was found to match your kernel; would you like the installer to attempt to download a kernel interface for your kernel from the NVIDIA ftp site [URL]?
which of course does not work. next it says Quote: "No precompiled kernel interface was found to match your kernel; this means that the installer will need to compile a new kernel interface.. i hit okay and move on to. Quote: Error: Unable to find the kernel sources tree for the currently running kernel. Please make sure you have installed the kernel source files for your kernel and that they are properly configured; on Red Hat linux systems, for example be sure you have the 'kernel-source' or 'kernel-devel' RPM installed. if you know the correct kernel source files are installed, you may specify the kernel source path with the "--kernel-source-path' command line option
I am running an Hp Pavillion dv6000 with the Broadcom card that never seems to work for Linux. I recently talked with my friend who said he found a way to get it work.following his instructions I opened Synaptic and checked the package bmcwl-kernel-source to be installed.I went through the process of it all and it said it had install successfully. I restarted the computer and when I tried to enter my operating system I got this error "Kernel panic - not syncing : VFS : Unable to mount root fs on unknown - block(8,1)" I have previous versions of Linux on my computer so I can still get in to those if need be but I don't know how to undo what I did or why it isn't working for that matter. Does anyone have any ideas as to why I am getting this error and how I can fix it?
It sounds like he's making a difference between the kernel "source code" and the kernel itself(as in the downloaded file/ files) but the way he talks about both is the same.So then, if one had already "installed" the "kernel sources code," why would he need the "tarball with the newest Linux kernel?" He's already "installed" a kernel, right?
I'm running CentOS 5.3 and would like to know what the "best" or "proper" method is to build a custom kernel using the generic kernel sources from kernel.org. Most of the references I've found talk about modifying the current CentOS kernel using the RPM way. I really want to have the latest kernel due to some important security issues that haven't been addressed in the current CentOS 5.3 kernel.
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/184.108.40.206-smp kernel modules tree found for kernel "220.127.116.11-smp"
I tried to look into the directory and there was only modules under 18.104.22.168. So I tried to change the command into: Quote: mkinitrd -c -k 22.214.171.124 -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:
I've just installed clean copies of both VirtualBox v4.0.8 and Fedora 15. Now I have followed the instructions here : [url] to install the latest VBox guest additions.
Each time I try I get the following message:
The headers for the current running kernel were not found. If the following module compilation fails then this could be the reason. The missing package can be installed with yum install kernel-devel-126.96.36.199-32.fc15.i686.PAE.
However, if I run that command I am told there is no such package available. The guest addition installer continues seemingly OK, but after a restart they are not loaded.
I've just moved to Fedora from Ubuntu due to major issues with its new version.
I want to load the package madwifi under opensuse from Index of /suse/11.1, but RealPlayer did not function correctly. The reason why I want to use madwifi is that I cannot start my internet with opensuse 11.1 using motherboard from asus with the ethernet adapter from Atheros AR 8121/AR8113 PCI-E Version 188.8.131.52. When I compile the delivered Linux drivers I got the failure message "Makefile:61: Linux kernel source not found". So I decided to take rpm from opensuse within madwifi. How/Where can I get the corrosponding madwifi elsewhere?
there is an issue with the way the Linux Kernel addresses memory by default and the graphic drivers for my Asus G1Sn. I have a patch that I had compiled against a custom kernel for 2.6.27.xx how ever it does not work with the latest kernel in Fedora 11. It is beyond me to rewrite the patch to work with a different kernel.
I use a pretty fresh installed RHEL 5.4, which should be very similar to Fedora. After the basic installation I installed xen and xen-kernel via yum with no errors. I can select the xen-kernel at boot time. But after booting the normal kernel shows up.
I wanted to try VirtualBox so I did: Code: yum install vboxgtk
In the list of dependencies I found that it needs to download kernel. I was just curious to know that why can't it manage with the PAE kernel. It requires the kernel 184.108.40.206-174.2.3.fc12 whereas I've got its PAE version working right now. Can someone please explain why is it so?
When I install the latest F12 kernel, my F12 installation freezes immediately on boot. The previous kernel booted fine. It's a little strange, because if I edit the grub.conf to use the old kernel, the freeze still occurs.Is anyone getting Kernel 220.127.116.11-174.2.22 to work in virtualbox? (both yes and no answers would be useful here)Does anyone have any idea of the cause (and especially, why updating the kernel would cause the _old_ kernel to freeze as well)
I've run today command: "sudo yum update" and I've noticed that the new kermel have been installed (18.104.22.168-174.2.3.fc12.x86_64). After that installation .. my camputer has several errors while booting and it doesn't want to start. So while booting I can see Code...