1 |
quickpg the existing modules then try the remove/reinstall fix. You can |
2 |
then use "emerge -K =package" or even a manually reinstall (by coping |
3 |
them over the newer ones) to replace the modules if things don't work out. |
4 |
|
5 |
I would think in your case needing to keep kernel specific modules |
6 |
around this would be an attractive task to script keeping matching |
7 |
modules with a kernel and swapping them in and out as necessary. |
8 |
|
9 |
BillK |
10 |
|
11 |
|
12 |
On 28/11/21 08:11, Wols Lists wrote: |
13 |
> On 27/11/2021 22:15, Kees wrote: |
14 |
>> >The docu says "emerge @module-rebuild". |
15 |
>> |
16 |
>> |
17 |
>> >Both of these terminate with "nothing to rebuild". |
18 |
>> |
19 |
>> |
20 |
>> Strange. try: emerge virtualbox-modules |
21 |
>> |
22 |
>> That should be rebuild after everuy kernel upgrade and that happens |
23 |
>> normally with emerge @module-rebuild |
24 |
>> |
25 |
> "nothing to rebuild" |
26 |
> |
27 |
> It always USED to work ... |
28 |
> |
29 |
> Cheers, |
30 |
> Wol |
31 |
> |