| 1 |
On Friday, 28. Jan 2022, 10:45:01 +0000, Wols Lists wrote: |
| 2 |
> On 28/01/2022 09:10, Bertram Scharpf wrote: |
| 3 |
> > after a kernel update and a |
| 4 |
> > |
| 5 |
> > # emerge -av @module-rebuild |
| 6 |
> > |
| 7 |
> > the VirtualBox modules cannot be found any more. |
| 8 |
> |
| 9 |
> You've updated your kernel, and you need to rebuild the modules, WHICH DOES |
| 10 |
> NOT HAPPEN BY DEFAULT. |
| 11 |
> |
| 12 |
> So, set your default kernel to the currently running one, and "emerge |
| 13 |
> virtualbox-modules". |
| 14 |
|
| 15 |
I _did_ call |
| 16 |
|
| 17 |
# eselect kernel set 2 |
| 18 |
|
| 19 |
and, as I wrote |
| 20 |
|
| 21 |
# emerge -av @module-rebuild |
| 22 |
|
| 23 |
as I always do. |
| 24 |
|
| 25 |
Anyway, a "depmod -a " helped. |
| 26 |
|
| 27 |
Thanks, |
| 28 |
Bertram |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Bertram Scharpf |
| 33 |
Stuttgart, Deutschland/Germany |
| 34 |
http://www.bertram-scharpf.de |
Archives