1 |
I mean that as: just reinstall Virtualbox as a first troubleshooting step. |
2 |
If that works, great. If it doesn’t, then that can be marked off the list |
3 |
as something that was tried. |
4 |
|
5 |
On Sat, Nov 27, 2021 at 8:21 AM Wols Lists <antlists@××××××××××××.uk> wrote: |
6 |
|
7 |
> On 27/11/2021 13:03, Jeremy Hendricks wrote: |
8 |
> > I’d recommend emerging Virtualbox again. It should just work with emerge |
9 |
> > @module-rebuild unless Virtualbox isn’t compatible with the newer |
10 |
> > version of kernel. |
11 |
> |
12 |
> HOW !?!? |
13 |
> |
14 |
> The problem is that they are already installed, so any attempt to emerge |
15 |
> them fails with "nothing to emerge". |
16 |
> |
17 |
> Unless I do an "emerge -C", but that of course will then break the old |
18 |
> kernel (assuming I might want to go back to it ...) |
19 |
> |
20 |
> Cheers, |
21 |
> Wol |
22 |
> > |
23 |
> > On Sat, Nov 27, 2021 at 8:00 AM Wols Lists <antlists@××××××××××××.uk |
24 |
> > <mailto:antlists@××××××××××××.uk>> wrote: |
25 |
> > |
26 |
> > On 27/11/2021 12:41, Peter Humphrey wrote: |
27 |
> > > On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote: |
28 |
> > >> Simple problem, after a kernel upgrade, virtualbox no longer |
29 |
> > works. This |
30 |
> > >> is to be expected, of course, BUT ... |
31 |
> > >> |
32 |
> > >> How do I fix it !!! |
33 |
> > >> |
34 |
> > >> What I always did on my old system was to re-emerge the modules. |
35 |
> > >> |
36 |
> > >> The docu says "emerge @module-rebuild". |
37 |
> > >> |
38 |
> > >> Both of these terminate with "nothing to rebuild". |
39 |
> > >> |
40 |
> > >> What else can I do? |
41 |
> > > |
42 |
> > > You could try 'emerge @x11-module-rebuild'. |
43 |
> > > |
44 |
> > Same result - nothing to rebuild :-( |
45 |
> > |
46 |
> > Cheers, |
47 |
> > Wol |
48 |
> > |
49 |
> |
50 |
> |
51 |
> |