I mean that as: just reinstall Virtualbox as a first troubleshooting step. If that works, great. If it doesn’t, then that can be marked off the list as something that was tried.
On Sat, Nov 27, 2021 at 8:21 AM Wols Lists <[email protected]> wrote: > On 27/11/2021 13:03, Jeremy Hendricks wrote: > > I’d recommend emerging Virtualbox again. It should just work with emerge > > @module-rebuild unless Virtualbox isn’t compatible with the newer > > version of kernel. > > HOW !?!? > > The problem is that they are already installed, so any attempt to emerge > them fails with "nothing to emerge". > > Unless I do an "emerge -C", but that of course will then break the old > kernel (assuming I might want to go back to it ...) > > Cheers, > Wol > > > > On Sat, Nov 27, 2021 at 8:00 AM Wols Lists <[email protected] > > <mailto:[email protected]>> wrote: > > > > On 27/11/2021 12:41, Peter Humphrey wrote: > > > On Saturday, 27 November 2021 12:29:10 GMT Wols Lists wrote: > > >> Simple problem, after a kernel upgrade, virtualbox no longer > > works. This > > >> is to be expected, of course, BUT ... > > >> > > >> How do I fix it !!! > > >> > > >> What I always did on my old system was to re-emerge the modules. > > >> > > >> The docu says "emerge @module-rebuild". > > >> > > >> Both of these terminate with "nothing to rebuild". > > >> > > >> What else can I do? > > > > > > You could try 'emerge @x11-module-rebuild'. > > > > > Same result - nothing to rebuild :-( > > > > Cheers, > > Wol > > > > >
