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?
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?
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.
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".
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.
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.
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
# 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.
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
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 303 |
Nodes: | 16 (2 / 14) |
Uptime: | 72:59:30 |
Calls: | 6,805 |
Calls today: | 1 |
Files: | 12,325 |
Messages: | 5,399,878 |