Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: [gentoo-user] Module vboxdrv cannot be found

100 views
Skip to first unread message

Neil Bothwick

unread,
Jan 28, 2022, 4:20:03 AM1/28/22
to
On Fri, 28 Jan 2022 10:10:32 +0100, Bertram Scharpf wrote:

> after a kernel update and a
>
> # emerge -av @module-rebuild
>
> the VirtualBox modules cannot be found any more.
>
> # find /lib/modules/`uname -r` -name 'vbox*'
> /lib/modules/5.15.16-gentoo/misc/vboxnetflt.ko
> /lib/modules/5.15.16-gentoo/misc/vboxdrv.ko
> /lib/modules/5.15.16-gentoo/misc/vboxnetadp.ko
> # modprobe vboxdrv
> modprobe: FATAL: Module vboxdrv not found in directory
> /lib/modules/5.15.16-gentoo
>
> What is going on here?

Does running "depmod -a" help? This should be done automatically, but it
doesn't hurt to try.


--
Neil Bothwick

WinErr 008: Broken window - Watch out for glass fragments

Bertram Scharpf

unread,
Jan 28, 2022, 4:20:03 AM1/28/22
to
Hi,

after a kernel update and a

# emerge -av @module-rebuild

the VirtualBox modules cannot be found any more.

# find /lib/modules/`uname -r` -name 'vbox*'
/lib/modules/5.15.16-gentoo/misc/vboxnetflt.ko
/lib/modules/5.15.16-gentoo/misc/vboxdrv.ko
/lib/modules/5.15.16-gentoo/misc/vboxnetadp.ko
# modprobe vboxdrv
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.15.16-gentoo

What is going on here?

Thanks in advance.

Bertram


--
Bertram Scharpf
Stuttgart, Deutschland/Germany
http://www.bertram-scharpf.de

Bertram Scharpf

unread,
Jan 28, 2022, 5:30:04 AM1/28/22
to
On Friday, 28. Jan 2022, 09:16:09 +0000, Neil Bothwick wrote:
> On Fri, 28 Jan 2022 10:10:32 +0100, Bertram Scharpf wrote:
> > after a kernel update and a
> >
> > # emerge -av @module-rebuild
> >
> > the VirtualBox modules cannot be found any more.
>
> Does running "depmod -a" help? This should be done automatically, but it
> doesn't hurt to try.

Exactly what I looked for. Thanks!

Is it a portage bug that "depmod" doesn't get done
automatically any more? Was it because "/boot" wasn't
mounted during the module rebuild?

Wols Lists

unread,
Jan 28, 2022, 5:50:04 AM1/28/22
to
On 28/01/2022 09:10, Bertram Scharpf wrote:
> Hi,
>
> after a kernel update and a
>
> # emerge -av @module-rebuild
>
> the VirtualBox modules cannot be found any more.
>
> # find /lib/modules/`uname -r` -name 'vbox*'
> /lib/modules/5.15.16-gentoo/misc/vboxnetflt.ko
> /lib/modules/5.15.16-gentoo/misc/vboxdrv.ko
> /lib/modules/5.15.16-gentoo/misc/vboxnetadp.ko
> # modprobe vboxdrv
> modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.15.16-gentoo
>
> What is going on here?
>
You've updated your kernel, and you need to rebuild the modules, WHICH
DOES NOT HAPPEN BY DEFAULT.

So, set your default kernel to the currently running one, and "emerge
virtualbox-modules". If that doesn't work, in my case it was I over-rode
the default make options so

"EMERGE_DEFAULT_OPS = "" emerge virtualbox-modules"

and if that doesn't work, well, I'm out of ideas ...

Cheers,
Wol

Bertram Scharpf

unread,
Jan 28, 2022, 7:40:03 AM1/28/22
to
On Friday, 28. Jan 2022, 10:45:01 +0000, Wols Lists wrote:
> On 28/01/2022 09:10, Bertram Scharpf wrote:
> > after a kernel update and a
> >
> > # emerge -av @module-rebuild
> >
> > the VirtualBox modules cannot be found any more.
>
> You've updated your kernel, and you need to rebuild the modules, WHICH DOES
> NOT HAPPEN BY DEFAULT.
>
> So, set your default kernel to the currently running one, and "emerge
> virtualbox-modules".

I _did_ call

# eselect kernel set 2

and, as I wrote

# emerge -av @module-rebuild

as I always do.

Anyway, a "depmod -a " helped.

Thanks,

Wols Lists

unread,
Jan 28, 2022, 8:00:04 AM1/28/22
to
On 28/01/2022 12:37, Bertram Scharpf wrote:
> On Friday, 28. Jan 2022, 10:45:01 +0000, Wols Lists wrote:
>> On 28/01/2022 09:10, Bertram Scharpf wrote:
>>> after a kernel update and a
>>>
>>> # emerge -av @module-rebuild
>>>
>>> the VirtualBox modules cannot be found any more.
>>
>> You've updated your kernel, and you need to rebuild the modules, WHICH DOES
>> NOT HAPPEN BY DEFAULT.
>>
>> So, set your default kernel to the currently running one, and "emerge
>> virtualbox-modules".
>
> I _did_ call
>
> # eselect kernel set 2
>
> and, as I wrote
>
> # emerge -av @module-rebuild
>
> as I always do.

My experience is that sort of thing doesn't help. Dunno why, but all the
"pick up changed dependencies" don't pick virtualbox up.
>
> Anyway, a "depmod -a " helped.
>
I'll have to try that. The only thing that's ever worked for me in the
past is explicitly emerging again.

Thanks,
Cheers,
Wol

Michael

unread,
Jan 28, 2022, 8:20:04 AM1/28/22
to
All I usually do is build/install a new kernel, run 'emerge -1v @module-
rebuild' and reboot. On occasions when I forgot to run @module-rebuild before
I reboot with the new kernel, I ran it afterwards followed by a successful
modprobe. From what I recall it just worked.

What won't work is running modprobe while still running an old kernel, but the
symlink while rebuilding any modules is pointing to a new kernel. I can't
explain Bertram's experience.
signature.asc

Bertram Scharpf

unread,
Jan 28, 2022, 8:30:04 AM1/28/22
to
On Friday, 28. Jan 2022, 13:10:36 +0000, Michael wrote:
> What won't work is running modprobe while still running an old kernel, but the
> symlink while rebuilding any modules is pointing to a new kernel. I can't
> explain Bertram's experience.

I cannot retrace what exactly happened, but I suppose it's
one reboot I missed.

Neil Bothwick

unread,
Jan 28, 2022, 9:30:04 AM1/28/22
to
On Fri, 28 Jan 2022 13:10:36 +0000, Michael wrote:

> > > # emerge -av @module-rebuild
> > >
> > > as I always do.
> >
> > My experience is that sort of thing doesn't help. Dunno why, but all
> > the "pick up changed dependencies" don't pick virtualbox up.
> >
> > > Anyway, a "depmod -a " helped.
> >
> > I'll have to try that. The only thing that's ever worked for me in the
> > past is explicitly emerging again.
> >
> > Thanks,
> > Cheers,
> > Wol
>
> All I usually do is build/install a new kernel, run 'emerge -1v @module-
> rebuild' and reboot. On occasions when I forgot to run @module-rebuild
> before I reboot with the new kernel, I ran it afterwards followed by a
> successful modprobe. From what I recall it just worked.
>
> What won't work is running modprobe while still running an old kernel,
> but the symlink while rebuilding any modules is pointing to a new
> kernel. I can't explain Bertram's experience.

In Bertram's case, emerge did build modules for the new kernel, as
evidenced by the find output he gave. The modules were there, in the path
that modprobe said they weren't, which is why a lack of depmod was my
first suspect. This may just be one of those things where the phase of the
moon conflicted with Bertram's star sign, or it may be reproducible, in
which case filing a bug report would help.


--
Neil Bothwick

There was a young man from the border
Who had an attention disorder.
When he reached the last line
He would run out of time
And

Peter Humphrey

unread,
Jan 28, 2022, 11:00:05 AM1/28/22
to
On Friday, 28 January 2022 14:21:02 GMT Neil Bothwick wrote:
> There was a young man from the border
> Who had an attention disorder.
> When he reached the last line
> He would run out of time
> And

There was a young curate from Kew,
Who kept a young cat in a pew.
He taught it each week
Alphabetical Greek,
But it never did get further than mu.

--
Regards,
Peter.
0 new messages