| 1 |
On 28/01/2022 12:37, Bertram Scharpf wrote: |
| 2 |
> On Friday, 28. Jan 2022, 10:45:01 +0000, Wols Lists wrote: |
| 3 |
>> On 28/01/2022 09:10, Bertram Scharpf wrote: |
| 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 |
>> You've updated your kernel, and you need to rebuild the modules, WHICH DOES |
| 11 |
>> NOT HAPPEN BY DEFAULT. |
| 12 |
>> |
| 13 |
>> So, set your default kernel to the currently running one, and "emerge |
| 14 |
>> virtualbox-modules". |
| 15 |
> |
| 16 |
> I _did_ call |
| 17 |
> |
| 18 |
> # eselect kernel set 2 |
| 19 |
> |
| 20 |
> and, as I wrote |
| 21 |
> |
| 22 |
> # emerge -av @module-rebuild |
| 23 |
> |
| 24 |
> as I always do. |
| 25 |
|
| 26 |
My experience is that sort of thing doesn't help. Dunno why, but all the |
| 27 |
"pick up changed dependencies" don't pick virtualbox up. |
| 28 |
> |
| 29 |
> Anyway, a "depmod -a " helped. |
| 30 |
> |
| 31 |
I'll have to try that. The only thing that's ever worked for me in the |
| 32 |
past is explicitly emerging again. |
| 33 |
|
| 34 |
Thanks, |
| 35 |
Cheers, |
| 36 |
Wol |
Archives