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/184.108.40.206-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?
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).
I get this when trying to launch a VB after making one with wizzard.
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/220.127.116.11-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 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/18.104.22.168-smp kernel modules tree found for kernel "22.214.171.124-smp"
I tried to look into the directory and there was only modules under 126.96.36.199. So I tried to change the command into: Quote: mkinitrd -c -k 188.8.131.52 -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 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'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 Arch Linux quite a few weeks ago; but I'm still trying my best to install the nividia display driver for my graphics card (nVidia Geforce 2 MX 400). Not only in Arch but have tried installing on other distros and still failed. I have read up all the documentations and I still find it hard to do this task. When I used the terminal and executed the NVIDIA-Linux-x86-94.43.01-pkg1.run file without any window manager running, I get this problem:
ERROR: Unable to determine the version of the kernel sources located in '/lib/modules/2.6.35-ARCH/build'. 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.
ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at nvidia.com.
Now I'm using Arch Linux Kernel 2.6.35 and I have got the source. But where am I suppose to put it now? I do not want to change the kernel. I just want the nVidia installer to identify that there is a kernel source so that it can install. I have searched up a lot on websites and ended up with no proper guide.
This is a very old driver. So since now I have the nVidia driver installation package and also the kernel source,
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
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 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:
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. I've dkms installed and did a reboot as well.
I can see this error occurring in multiple past versions of suse. The answer seems to involve recompiling the open source version of VBox, but this is surely overkill. Isn't there a way to either a)get the right kernel version of VBox for 11.3 or b)set whatever permissions are required.
In all the answer so far I can't see a solution I can understand for these combinations, sues 11.3 and VBox 3.2.8. The error is consistent, and if the install doesn't work properly (it took my a few attempts even to install it without error messages) then surely its an issue either for Oracle or Suse? It runs ok but hwen trying to fire up a newly created XP VM this error message occurs trying to switch from W764bit to suse11.3 64bit
I just installed a Puppy Linux 5.1 to a VirtualBox VM and selected hardware virtualization. It installed ok and then later I noticed I had not unloaded the kvm and kvm_intel modules. I was then surprised to notice the vbox modules were also loaded. It used to be you had to kick out the kvm modules before you could even boot a VM in VirtualBox using SVM or VT-X. If you didn't you'd get some error message in Vbox have to quit and restart it after removed the kvm modules.
Is this a neat new functionality of VirtualBox or something that was improved in Fedora?
I just installed a fresh CentOS 5.2 32bit system. I used "The Perfect Server" server document from Howtoforge and went through those steps and then added Webmin administration console. I then tried to install VMware Workstation 6.5 onto the system. I downloaded the latest VMware bundle, ran it and everything went fine. I then try to run vmware and I get the following messages
C header files matching your running kernel were not found
Before youcan run VMware Workstation, several modules must be compiled and loaded into the running kernel
Kernel Headers 2.6.18-92.1.22.el5.centos.plusPAE
Kernel headers for version 2.6.18-92.1.22.el5.centos.plusPAE were not found. If you installed them in non-default path you can..
I have, for days, been trying to get a Fedora 15 server to send audio output to the system monitor, an ASUS VH242H, via HDMI. The video portion works perfectly, allowing me to appreciate GNOME 3 for the first time. Sound, on the other hand, is non-existent.
From many, many threads on this problem, I have at least been able to provide some info which might help resolve this. Unfortunately, I have now read too much and followed too many suggestions to be able to find my way through the morass. So, once again, I built a completely new system to ensure a clean start.
Note also that to simplify things, I disabled the on-board audio in BIOS so only Nvidia has any sound output capability. Initially, 'alsamixer -V all' identifies the card and the chip as being PulseAudio. That would change if I used the <F6> option but I have not done so to keep things 'clean' at this point. The 'Master' is full on (100<>100), so muting is not a problem. Next, I searched for the device from the output of /proc/asound/card0 which would match the monitor.
The one device associated with the monitor_name is eld#3.0:
monitor_present 1 eld_valid 1 monitor_name ASUS VH242H
Both the kernel driver and the kernel modules are not what I think I should have. The kernel driver should be HDA NVidia for starters, no? Running modprobe -l and looking for nvidia returns:
'kernel/drivers /video/nvidia/nvidiafb.ko'and 'extra/nvidia/nvidia.ko' But I have not attempted anything beyond this point because I am just too confused as to what needs to be done and who or what manages these values effectively.
I am having some issues compiling kernel modules against the pre-built OpenSUSE kernel. Whenever I compile a module and try to load it, I get something like:
Code: insmod fs/smbfs/smbfs.ko insmod: error inserting 'fs/smbfs/smbfs.ko': -1 Invalid module format It doesn't actually matter what the module is, they all do the same thing. I have tried the above mentioned smbfs, I've also tried:vmware kernel module
I want to remotely install OpenSUSE on one of my servers. I followed the instructions given at SDB:Remote installation - openSUSE, but it didn't work. (My server reverted back to the already installed system.) I think this has to do with a special kernel module (megaraid_sas) that is necessary for the raid controller. Without this module, the kernel cannot find any disk. Of course, the module is not included in the initrd provided by OpenSUSE. I know how to add files to the initrd, but I have no idea where I have to put the required kernel module and which config file inside the initrd must be modified to make the kernel load the module.
Error! Your kernel source for kernel 184.108.40.206-166.fc12.x86_64 cannot be found at /lib/modules/220.127.116.11-166.fc12.x86_64/build or /lib/modules/18.104.22.168-166.fc12.x86_64/source. You can use the --kernelsourcedir option to tell DKMS where it's located.
Failed to install using DKMS, attempting to install without: Makefile:152: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
im running suse 11.3_x64 clean install along side with Win7 Pro _x64 had a big fight installing Vbox 3.2.8 PUEL edition but i need to test some VMWare products like 'VMWare vShpere (ESXi 4..0.1 - which i couldn't install in a vm in Vbox) ' before putting it in production enviroment in some of my clients. version: VMware-Workstation-Full-7.0.0-203739.x86_64 The installation of vmware was quite simple with no errors. the problem kicks in after the first reboot when i try to run it. before installing vmware i installed the following:
When i try to run vmware workstation the 1st error kicks in: Before you can run vmware, several modules must be compiled and loaded into the running kernel:
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.
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 -> /usr/src/vboxdrv-3.1.6
DKMS: add Completed.
Error! Your kernel source for kernel 22.214.171.124-99.fc12.i686.PAE cannot be found at /lib/modules/126.96.36.199-99.fc12.i686.PAE/build or /lib/modules/188.8.131.52-99.fc12. code....
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'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 have just compiled a new kernel. When I boot into this new kernel and do an lsmod it is only running two modules. The only thing I changed in the configuration file was to compile ext4 file system into the kernel. My computer is an HP Pavilion dv4. The two modules are lirc_ene0100 and lirc_dev. I am running Ubuntu 10.04. The new kernel is 184.108.40.206+drm33.5. The kernel seems to work fine but I need to know why and how it can only be running two modules.