I installed VirtualBox-OSE and VirtualBox-Kernel from the Slackbuilds at slackbuilds.org.When I start VirtualBox I get the following message on the CLI: Code: WARNING: The vboxdrv kernel module is not loaded.Either there is no module available for the current kernel (2.6.33.4-smp) 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 gave /etc/rc.d/rc.vboxdrv executable permissions, and then ran.The only issue is, I have to do this each time that I reboot, should I add 'modprobe vboxdrv' to one of the startup scripts or is something else wrong?
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:
Recently I had updated the kernel but afterwards I can't run virtualbox because the kernel modules aren't loaded.
Virtual box: 3.1.4 r57640 OpenSuse110-x86_64 Open Suse 11.0 running kernel-default-2.6.25.20-0.7
When I try to start vboxdrv manually I can find the message: kernel: warning: `VirtualBox' uses deprecated v2 capabilities in a way that may be insecure.
After I installed the older kernel-default-2.6.25.20-0.6 version I can start virtualbox.
But, much to my suprise, I also get this message with this kernel level. But still, the kerneldrivers are loaded and I can run virtualbox.
I've Ubuntu 9.10 with 2.6.31-20 kernel.Sound kernel module is loaded, but doesn't works ;((. I have not got any errors and all programs (e.g. mplayer) thinks that sound driver is present and works OK but I can't hear a sound...A part from lspci -vvnn
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]
I have a zyxel dsl (usb) moden, which needs a firmware portion to work, called cxacru-fw.bin.
I have been using this modem using with at least two different slackware distributions, even when the atm drivers were not included in the kernel.
Presently I am using slackware 13.0, with the vmlinuz-huge-smp-2.6.29.6-smp kernel.
I downlowded the 2.6.34 kernel, because I need it for a new webcam, compiled and installed it, and oops! the modem does not work anymore.
I am pretty sure I have configured the kernel correctly; dmesg tells me the modem is recognized by the kernel, as it is with the previous one, but the firmware is not loaded, because the DSL led remains off.
I attach the kernel configuration lines:
I have tried forcing the kernel to load the firmware, using but it didn't work either.
I heva Debian "Lenny" 5.0 with a 2.6.31.3 kernel. I've got some trouble with VirtualBox.When I start virtualbox I get such outbut:
Quote:
[sergey@localhost:~]$ virtualbox WARNING: The character device /dev/vboxdrv does not exist. install the virtualbox-ose-modules package for your kernel and load the module named vboxdrv into your system. You will not be able to start VMs until this problem is fixed.
But when I do 'insmod vboxdrv.ko' (or even w/o '.ko', 'modprobe vboxdrv') it says that there is no vboxdrv.ko.What have I to do to run virtual-machines? (NOTE: Kernel 2.6.31.3 I've compiled manually, and there is no virtualbox-ose-modules package for kernel 2.6.31.3 in repository)
I'm having problems with Screen and VirtualBox, and the problems seem similar as if crucial components have vanished. Here is the screen issue and the last three posts are me. Basically, the solutions have been temporary so far. I changed the mode and group of /var/run/screen like the OP said but have not shutdown yet, so I don't know if that's a permanent solution yet. The other two temporary solutions didn't prove to be temporary until I shutdown and came back several hours later. Screen was still working after a reboot.
The same thing is happening with VBox: after doing what VBox tells me to do, the solution was temporary, and the same problem popped up after the next boot. Here are similar problems: I made sure I was in the vboxusers group. I added the module like the first one said, and it took me to another level of malfunction. I didn't take a screenshot or make a note of the first error message, but I've attached the second. Also, sudo /etc/init.d/vboxdrv setup did not work this time after adding the module. Like the first link said, vboxdrv didn't exist for him or her, so maybe my problem is similar. My terminal says it "Cannot unload module vboxdrv".
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 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 trying to see if a module that i loaded on Redhat succeeds.The module is from intel called vtune_drv-x32_64-2.6.18-194.el5smp.ko.When I run the script during the installation process, it shows that it is successful.Is the "0" at the end of line meaning that the module is not successfully loaded?
I am trying to install 11.2 on a system with RAID-1 /boot partition and RAID-10 /(root) partition. I have done this before with 10.3 but am hitting a wall with 11.2. In particular, the boot image loads and then halts when it tries to load the RAID-10 root partition saying that the personality is not laoded. modprobe shows that the raid10 module does not appear to be part of the boot image. I cannot find anything in the installation that will allow me to specify a module to include in the init image. How do I tell the installer to include an additional module?
I have an Acer 1551-4755 notebook with AR5B93 wireless chipset. ath9k is loaded and my card is detected as Atheros AR928X PCI-Express wireless network adapter. However, the ath9k driver is only allowing me to connect at 802.11g speed in spite of the fact that my WRT310N loaded with DD-WRT is in mixed mode. I am able to connect at wireless N speed with my D-Link DWA-130 usb dongle, but this is a rather backward solution. Is there a way to work around this issue, ie an updated ath9k or other madwifi driver? I would hate to resort to ndiswrapper for a natively supported chipset. I am using openSuSE 11.3 for the first time, long time Fedora user.
After much tiddling'n'fiddling I finally got my new Linksys WUSB600N v2 working. Contrary to many posts, mine did NOT work with either the standard rt2870sta module, nor the updated version from the driver:wireless repo. Also the rt2870 version from the ralink website didn' t work. After a days worth of Googling I came across this post. The bottom line?
1. Download rt3572 from the Ralink website. 2. Add {USB_DEVICE(0x1737,0x0079)}, /* WUSB600N v2 */ to common/rtusb_dev_id.c 3. Follow README_STA
I did not install firmware packages. And be sure the rt2800sta module doesn' t get loaded. (you could just remove it, I suppose.)
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 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 am trying to set up wireless on my desktop. It has no internet whatsoever, I could hook up ethernet but I would have to transfer the whole computer across the house. I installed ndiswrapper from the installation CD. I also installed NDISGTK which is some GUI with the ndiswrapper. I clicked Install New Driver, I am pretty sure I have all the other necessary files along with the mn710.inf, but I get the error:"Module could not be loaded. Error was:FATAL: Could not read '/lib/modules/2.6.35-22-generic/kernel/ubuntu/ndiswrapper/ndiswrapper.ko': No such file or directory"After clicking ok, it shows the driver there, but my card is still not working, no lights or anything. Does anyone know what that error is and how I can get it working?
I got an acer aspire 5532 last year for Christmas and I want to try the new 10.04 ubuntu on a partition with windows 7. I installed it successfully on drive E and when I boot up I get a black screen like this:typed boot and got: "error: no loaded kernel."How do I fix this?
I recently updated the kernel from SLES 11 to SLES 11 SP1 .However my kernel modules are not getting loaded and they throw an error such as shown below:"Errornserting mii : Unknown symbol in module, or unknown parameter (see dmesg)"
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 have Ubuntu installed in my machine, I also have Windows Vista.I have been using Ubuntu perfectly well, today I received the following message when chose to boot Ubuntu:GNU GRUB version 1.97 beta 4[Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device/flies completions]
I've been looking forward to making the switch to Ubuntu for a while, but ever since I did, the road's been pockmarked with errors and hassles. That's, primarily, because I don't know what the hell I'm doing. Let me explain how I installed Ubuntu: All I did to install Ubuntu was download the file from the website and run the program. I didn't burn anything onto a CD or USB; I just clicked on the .exe file and let it run from there. Everything worked great - all I had to do was boot my laptop and choose from either Windows 7 or Ubuntu. Now, I had no idea how to watch videos, so I started to install a lot of stuff from the Synaptic Download Manager. Now, I don't know all of what I downloaded, but it was mainly games. The next thing I know, I get this page when I choose Ubuntu:
Code:
GNU GRUB version 1.97~beta4 [minimal BASH-like line editing is supported. For the first word, TAB lists possible command completion. Anywhere else TAB lists possible device/file completions.] sh:grub> _
So I hit TAB and try the easiest command on the list, BOOT. This is what I get when I try boot:
