I have been trying to run my vmachines in virtualbox with no success so I decided to install upgraded packages for upgraded kernel, this means to install them from Virtualization-kernel-HEAD repo.The error is about that known issue where the kernel module can't start.
I Just loaded 11.2 64 bit, initially the kernel was "default", however, after I installed my Nvidia drivers it changed to desktop, I'm not sure I understand? In GRUB my screen lists it as desktop. Is "default" somewhere? Was it replaced? Things seem to be working alright in most cases although I'm having inordinate problems with "virtual Box" and Vmware server. In Vbox the kernel module won't start.
I have downloaded vbox from its site and installed it. I created a vm but when I try to start it, I get error: 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. Please reinstall the kernel module by executing: '/etc/init.d/vboxdrv setup' 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.
And when I try 'sudo /etc/init.d/vboxdrv setup', I get: Stopping VirtualBox kernel modules done Uninstalling old VirtualBox DKMS kernel modules done Trying to register the VirtualBox kernel modules using DKMS failed (Failed, trying without DKMS) Recompiling VirtualBox kernel modules failed (Look at /var/log/vbox-install.log to find out what went wrong)
And this is /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.
It is bad enough that the kernel gods have basically required that the whole kernel source tree be installed and configured to compile even a simple module but they have made it so a module compiled on one kernel will not work on any other.
To make the situation worse much of the configuration needed to successfully compile a module has been left out of open suse11.3. If you want to replicate the problems may I suggest you attempt to compile the usb-skeleton.c driver example code that is included with each kernel. If it is the intent of the linux community to limit driver development to the professionals then congratulations.
I am working with OpenCL (note that is different from OpenGL) and recently upgraded from nvidia driver 190.29 to 195.36.15 . After a bit of experimentation i decided to downgrade back to 190.29
However after i did this X complains that i have nvidia kernel module 190.42 and it does not match with nvidia drive 190.29 . Could some one tell me how to recompile the kernel module for 190.29??
I'm using openSUSE 11.3 with an Intel Corporation Mobile 945GME Express Integrated Graphics Controller. The kernel driver in use is i915, however, in another distribution of Linux, two kernel modules are loaded: i915 and intelfb. I would like to know how to load module intelfb in openSUSE 11.3 as it seems to significantly improve my video card's responsiveness.
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:
I have just reinstalled OS 11.2 but this time the 64bit system variant. I installed the real-time kernel and saw that the apparmor module reported an error and wasn't loaded. I have never looked into apparmor and only knows it has something to do with security, and thus I wonder if it is important to do something with this issue? I plan to use the kernel-rt and have more or less always used a variant of this kernel flavour, often self built. Though I can not recall having seen that error before and I have not used a 64bit system before
I need to install module u32 into the netfilter module for kernel 2.6.27.
I did not see the source code in the kernel version I have. where can I find the code for U32 module.
I have checked "netfilter.org" and looks like POM is discontinued. Is the u32 module committed to kernel version 2.6.27 or need to patch it. If yes, where can I find the patch?
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've upgraded kernel 2.6.27.48-0.2-default to 2.6.27.54-0.1.1 on openSUSE 11.1. Before I tried to upgrade to 2.6.27.48-0.3-default where I encountered the same issue. After reboot it can not find the modules for 2.6.27.48-0.2-default which puzzled me to no end. Now I have found that the /boot which is on separate partition of ext2 type is not mounted. The mount command does not recognize ext2 and xfs anymore.
Clearly the initrd does not have the right modules. Since this is standard zypper up process I would expect this to work without issues since it has worked until the 2.6.27.48-0.2-default kernel without issues. Has something changed with the last 2 kernel versions that requires some extra actions from me and if so what do I have to do.
I have install windows XP and Fedora-14-X86_64 on dual boot, I want to run other OS on fedora by using Virtual machine. I have download and installed VirtaulBox-4.0.0 successfully but I cannot able to start it. I got error about Vbox driver not installed [error code:1908]. I have also installed DKMS package, but also didn't work.
Finally I found the actual problem was kernel not compatible with latest version of vbox and I need to update my kernel-headers. I also meet that solution by using command: yum install binutils gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel and its work fine, this command download and install the kernel compatible VirtualBox-3.2.* and now its works fine.
But problem is that when I booting my PC, it shows 3 options for entering OS rather then 2. 1. Fedora-14 (2.6.35.10.74.X86_64) [which is new one/updated after using that command] 2. Fedora-14 (2.6.35.6.45fc14.X86_64) [which is new one/updated after using that command] 3. Other [windows XP] How can i delete that old version- No.2?
I'm using Slackware 13.1 32bit and can't run virtualbox when I try to boot the virtual machine it shows me a window with the following message:
Quote:
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. Please reinstall the kernel module by executing
'/etc/init.d/vboxdrv setup' run - /etc/rc.d/rc.vboxdrv setup
Quote:
Stopping VirtualBox kernel module ...done. Recompiling VirtualBox kernel module ...failed! (Look at /var/log/vbox-install.log to find out what went wrong) Check /var/log/vbox-install.log
Quote:
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.33.4-smp/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( echo;
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:
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
Used to work perfectly. I attempted to install VPN client, result is can't connect to anything. Networks are seen by network manager, nothing happens when click connect. Results below:
Wireless LAN present in Hardware information. Atheros AR242x 802.11abg Wireless PCI Express Adapter (wlan0) Kernel Driver: ath5k 168c:001c /var/log/boot.msg
[code]....
Advice is to use output of dmesg command to find problem, but as above I don't get any results for this in terminal.
attempt to ping external site linux-cfi6:~ # ping -c 66.70.73.150 Usage: ping [-LRUbdfnqrvVaA] [-c count] [-i interval] [-w deadline]
Experienced that building the vbox guest additions (on the binary/non-free vbox) on a slackware --current guest (with windows *and* linux as a host) fails now with the new kernel's just released in --current?
I have a problem with my custom kernel when I want to create the Nvidia kernel module.After this finished I installed the image and headers and created the Nvidia kernel module. Everything worked fine.However, if I remove the linux-source from my home directory then I can't create the kernel module.Even though I have the headers for the kernel installed.
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 did it, I don't know exactly what I did, but OpenSuse 11.4 only boots to CLI when I fire it up using vbox 4.0.10. I was not able to attached a screenshot, I got an error saying that I did not have sufficient rights or something.
I have Vbox 4.0.4_OSE installed on my 11.4/KDE4.7 Laptop with Win7 and WinXP VMs installed. Generally runs well, although the Win7 VM seems to lock up on occasion if I ignore it for too long. Compared to having to reboot to Win7 to do the few things still stuck on Windoze, it is a GREAT solution.
Question: I have seen several forum items related to difficulty with dual boot systems and the installation of Win7SP1, regarding SP1s checking the MBR for the Win7 boot loader. Has anyone done a SP1 update to a VM on Vbox? It is sort of unclear what SP1 might see in the VM disk container associated with the VM. Since the initial load process for a new VM is time consuming, I thought I would ask first before blowing up my otherwise working Vbox system and then having to reload from scratch.
launching vBox lately pops-up this; but if I allow it to go ahead, I get this.. : the window has no end (!), no scroll bars nor any further info. If I first uninstall in Yast, will I lose all of my machines? Up until now these periodic updates have been a breeze, only sometimes needing a vbox setup afterwards to tweak the kernel
I installed recently opensuse 11.3 and then Virtualbox from Sun Webpage. I have a local printer connected to one of the usb ports. With 11.2, VBox saw perfectly that printer and I could connect normally to it. Now, VBox sees the printer: if I click on the usb icon in the status bar it appears, but dimmed, and I cannot connect to it. I tried to disconnect and reconnect the printer physically, but nothing changed.
Has anyone successfully installed the x64 on VBox? Is there a different way to install the x64, because I don't think VBox can process this version. The few problems I have are:
1) it freezes during Auto Configuration. 2) freezes during boot initialization. 3) after reboot it keeps prompting me to complete a failed install, and doesn't matter if I accept to complete or not, I have the same problem. 4) freezes randomly executing system programs.