On Sun, 05 Feb 2012 22:48:07 +0000
Sérgio Basto <[email protected]> wrote:

> On Sun, 2012-02-05 at 19:28 -0500, Lucélio Gomes de Freitas wrote: 
> > Hi List,
> > 
> > I'm happy, because the must of this list is cooperation and not
> > competition, thank you all.
> > This makes a winner team.
> > 
> > Em 05-02-2012 14:27, Sérgio Basto escreveu:
> > > On Sun, 2012-02-05 at 14:59 -0500, Lucélio Gomes de Freitas wrote:
> > >> If executing(root privileges):
> > >>
> > >> ERROR: modinfo: could not find module vboxdrv
> > >> ERROR: modinfo: could not find module vboxnetflt
> > >> ERROR: modinfo: could not find module vboxnetadp
> > >>
> > >> Does anyone could give me a hand? 
> > > Hi, I am co-maintainer of VirtualBox on rpmfusion 
> > > this is a little odd , 
> > > ll /lib/modules/3.2.2-1.fc16.x86_64/extra/VirtualBox-OSE/vboxdrv.ko 
> > >
> > > so I guess a reboot will fix the loading of modules kernel , this
> > > is a
> > Not exactly, many reboots were donne.
> > > kernel 3.2.2-1 , I don't remember has any trouble with this
> > > kernel, but I will check it on office, Monday.
> > >
> > > here I got 
> > > lsmod | grep vbox
> > > vboxnetadp             13382  0 
> > > vboxnetflt             23424  0 
> > > vboxdrv               263468  3 vboxnetadp,vboxnetflt
> > I noticed the problem since kernel Fedora 3.1.9-1.fc16.x86_64.
> > Today the same problem occurs and after a "sudo yum update" I was
> > not able to start the saved WinVista64.
> > 
> > Until today the solution I found was:
> > 1=> "sudo yum remove VirtualBox-OSE.x86_64" and
> > 2=> "sudo yum install VirtualBox-OSE.x86_64" and boot.
> > 
> > On remove/installation everything works.  It works now, and I have
> > to wait until next update.
> 
> ERROR: modinfo: could not find module vboxdrv
> is pretty clear vboxdrv.ko for the kernel in question is not there. 
> 
> rpm
> -qf /lib/modules/3.2.2-1.fc16.x86_64/extra/VirtualBox-OSE/vboxdrv.ko
> kmod-VirtualBox-OSE-3.2.2-1.fc16.x86_64-4.1.8-1.fc16.7.x86_64
> 
> you may grab this
> kmod-VirtualBox-OSE-3.2.2-1.fc16.x86_64-4.1.8-1.fc16.7.x86_64 package
> from yum or build it with akmod-VirtualBox-OSE.x86_64 
> have you kmod-VirtualBox-OSE.x86_64 ? 
> 
> kmod-VirtualBox-OSE.x86_64 : is a meta-package without payload which
> sole purpose is to require the VirtualBox-OSE kernel module(s) for the
> newest kernel.
> to make sure you get it together with a new kernel.
> > I hope in next update it does not stop working. Solved or not I'll
> > post the result here.
> 
> you will have VirtualBox-OSE-kmod-4.1.8-1.fc16.8 soon for
> kernel-3.2.3 , if you don't use akmods , install
> kmod-VirtualBox-OSE.x86_64 first . Should give you a sync between
> kernel and kmod. 
> 
> 
> Best regards,

AFAIK The module vboxdrv is not needed for operation of VB, just its
install.
Locate the source directory and check the state of the modules needed
for VB to run, check from here
/usr/share/virtualbox/src/vboxhost/
try and manual compile one of the modules, if that fails you will have
a better idea of whats not working. Maybe start with vboxnet.
HTH

-- 

-- 
Best wishes / 73
Richard Bown

e-mail: [email protected]   or   [email protected]

nil carborundum a illegitemis
##################################################################################
Ham Call G8JVM . OS Fedora FC16 x86_64 on a Dell Insiron N5030 laptop
Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W ( degs
mins ) QRV HF + VHF Microwave 23 cms:140W,13 cms:100W,6 cms:10W & 3
cms:5W
##################################################################################
 



------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community

Reply via email to