| 1 |
On Sonntag 27 September 2009, David Relson wrote: |
| 2 |
> On Sun, 27 Sep 2009 14:01:02 -0400 |
| 3 |
> |
| 4 |
> Walter Dnes wrote: |
| 5 |
> > On Sun, Sep 27, 2009 at 08:15:46AM -0700, walt wrote |
| 6 |
> > |
| 7 |
> > > I'm using the vbox svn repository from Sun, so I haven't tried |
| 8 |
> > > building the portage version. |
| 9 |
> > |
| 10 |
> > As I mentioned, I'm using Sun's install because the portage install |
| 11 |
> > dies. |
| 12 |
> > |
| 13 |
> > > What problem do you see? |
| 14 |
> > |
| 15 |
> > At bootup I get... |
| 16 |
> > * Starting VirtualBox kernel module ... |
| 17 |
> > * modprobe vboxdrv failed. Please use 'dmesg' to find out why |
| 18 |
> > |
| 19 |
> > I'm attaching dmesg output in the hope that someone can figure this |
| 20 |
> > out. |
| 21 |
> |
| 22 |
> Do you have vboxdrv in your kernel? My kernel has the module build, |
| 23 |
> as evidenced by command 'locate vboxdrv' displaying: |
| 24 |
> |
| 25 |
> /lib64/modules/2.6.28-gentoo-r5-xfs/misc/vboxdrv.ko |
| 26 |
> |
| 27 |
> I'm don't know which kernel option creates vboxdrv, but google surely |
| 28 |
> knows :-> |
| 29 |
> |
| 30 |
> HTH, |
| 31 |
> |
| 32 |
> David |
| 33 |
> |
| 34 |
|
| 35 |
none does. You have to emerge the vbox driver. |
Archives