1 |
On 28/01/2022 09:10, Bertram Scharpf wrote: |
2 |
> Hi, |
3 |
> |
4 |
> after a kernel update and a |
5 |
> |
6 |
> # emerge -av @module-rebuild |
7 |
> |
8 |
> the VirtualBox modules cannot be found any more. |
9 |
> |
10 |
> # find /lib/modules/`uname -r` -name 'vbox*' |
11 |
> /lib/modules/5.15.16-gentoo/misc/vboxnetflt.ko |
12 |
> /lib/modules/5.15.16-gentoo/misc/vboxdrv.ko |
13 |
> /lib/modules/5.15.16-gentoo/misc/vboxnetadp.ko |
14 |
> # modprobe vboxdrv |
15 |
> modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.15.16-gentoo |
16 |
> |
17 |
> What is going on here? |
18 |
> |
19 |
You've updated your kernel, and you need to rebuild the modules, WHICH |
20 |
DOES NOT HAPPEN BY DEFAULT. |
21 |
|
22 |
So, set your default kernel to the currently running one, and "emerge |
23 |
virtualbox-modules". If that doesn't work, in my case it was I over-rode |
24 |
the default make options so |
25 |
|
26 |
"EMERGE_DEFAULT_OPS = "" emerge virtualbox-modules" |
27 |
|
28 |
and if that doesn't work, well, I'm out of ideas ... |
29 |
|
30 |
Cheers, |
31 |
Wol |