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

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmHztFkACgkQ92eFu0QS MJj4xQ//d729D0YUbyxdkkHsbiyHAibRPhMvQqwZxOxrzs8vpBFIMoyO1WHL0euU Ojn2hXlBaaJwqtIQLyTkCFGHmgE3slj4FjeR72gN/6A58PqJfYF/v2RtyGinhr8U kl0Ve7qelwCbj0Qv2fw41AWYA9gg1fnMxEP+jgJsqBlpU7MK9gx4BKwYcgXPaytT dBubJ4tkUT27nund3S6LCaYG/vv/5aG4uTEeOa56hkOd/uLPmjN8sqMA0fKLSLRO 2KG2ojVkXtSmpWPmWlvsWuXbltU6luChdmr4QU940FIT+BAQuxLdXh+5/WsIaotw BiZGc11eF2ALAsMXvQB4om/ALnkoJJe+5QvbcSlvaKy2yRfN113DAdDfD5szI0+9 JH+C0pPwYgaYRH3upuZZ6hqrABKTVm0mO1Ymnt0AEGxDKEysImGLj8zdYWvPjwBz +W82VTHXf0OFxAfIXbdzvUVHOAw86VmUfXzY0pTSyq3VaSrLarw1XN8qOe+RKexA NlxV3lhmFyS/JxsmtEXJLBOYFu2J2qP/d2dOgWvrRPpyunjEPE/BiGWYlO1V4fs7 j0RwWmTrrN4C9AOC/RplxiWfp3kw7o4y4do+4Hwc8OLWC0xyGSZvKF31sNqWZ5Wm qcmXq5j69i7kYvobmXlZiqYB2OhOMM8ZqI9KhEFcs2sMQ/2trxk=
=TXYs
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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?

Bertram


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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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,
Bertram


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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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.

Bertram


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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Friday, 28 January 2022 12:53:12 GMT Wols Lists wrote:

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

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.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmHz60wACgkQseqq9sKV Zxnh0Q/9GoC9t5rjrJXEpS4LCYFJqW6jeW3/GVCPeEBBtTZrNryTkrkmlAPikQJM CCVq2Wtv/lHC4Nlgk1CQaJm+oLCU7nyBzp5S+ZJ084fz+yAe6MZYOGuS30CTKjbV AXi42OVeBeolAAzYgZmhXmOt0aaK45SC7CPXNlJhZrA1L2fXM2hF2dHbOzqg2TKf ZA+/+hjFdtt2s6w9jBF4ypVvz00ovqEwifX97NE+sWsGOsGRtIYSDSrPjKGr5k1i sqdB25keStGYsszVTEEeFgglMwmuANzr6Ta+H5rKxEkN+BeQCnQbiOxocuB49xsP +B3akPUHwDOtzpYnn4ASEDIGztumyDdDDLNj99PHizcJqKtslkzOUfHiPU5JgztI +Wrleva2xpq8NSZaOM1Gm4cNuk8EP1DyEfsAabmPTlipa7/3QDx61+lfN57szshe UKm1E0GcJnriI2kUYQ61Xh2y8/GkiOSKitl0kDm3A2TMC/Tz8Ge3mI7pG2SfeCJ1 Gb4ua+3RI+XuE48gmxWKOpEp4h9r84c3RO1GLwkKbmluEPQobBaP3ntSecbD6rOV L6/3P/o7XKnyWo/OG05CWGnlH2fmaqeugqbmnWPYHSVAloWCNe4POVM67k30Kp69 lrwDA+dTNcJvuo30wgyxg6e4ZAvqMHM/7vGl+tYPXc4HN16NeAI=
=Y2oQ
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmHz+84ACgkQ92eFu0QS MJjXGQ//blp+zvZbXUn8Ebl64CqADM7pTY0QbV8ujz6XFS7jWhaklKkXN8QX/1x9 to2vu51YIevmezyCtuQVOnLUwaaX2azQmJTP2IiDQTtA1fk/Q4PrY5KyGaYfx9V+ KbqCRurcVXSG9N/A0xEB7dJTqKAL1AJFF4EvNOuB+TL6FOKgJcg2kNSMuAZihGRO 5oJ7yjjoU9kna7WCQMD04dTI6jrCY7XBdJ8qIAc0pciRQC8VfHc7BCnlWHQbw274 UvVfveMdOKKgzrpSWcXCLfyUqM+KW0ewAZyLngqOiV+ULe7HsfZEn52SPtzcta+p 1NSAx7XosjLoxZn2OXrhH4eaDtGx5+cfsf0GZNticVHLZ3AP2q8TIKv9iG9KYK+m AqXOPpiAXSNKJynZD6eb1waKQL8W0UyHR5EKzHZ/5i3kx2gPtkXv22TX2FOdAglE PyRaAXz6ZqrDAlTH1GTBwzGUszS8LE06DjwnGNO7KK3TiMKDl8HIFiZMwVGncOdU KErf4V1ctd72HNMAVACOKC+Yg/GP6CPwH5jutFT3Jiga8IAoSXImeWHCvwvuyebQ zdhDJcpgkP5NQpfaBnIWm9E+TH/UIrKOMdwoEUBDucI8JLtJW098Zevb2x2/HAax auiq7lIUsaPVbLzieDNQddM4PJxuErKHE8mi1ZAXcIsEGauBgXU=
=tJKu
-----END PGP SIGNATURE-----

--- SoupGate-Win

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.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)