On Friday, 28 January 2022 12:53:12 GMT Wols Lists wrote: > On 28/01/2022 12:37, Bertram Scharpf wrote: > > On Friday, 28. Jan 2022, 10:45:01 +0000, Wols Lists wrote: > >> On 28/01/2022 09:10, Bertram Scharpf wrote: > >>> after a kernel update and a > >>> > >>> # emerge -av @module-rebuild > >>> > >>> the VirtualBox modules cannot be found any more. > >> > >> You've updated your kernel, and you need to rebuild the modules, WHICH > >> DOES > >> NOT HAPPEN BY DEFAULT. > >> > >> So, set your default kernel to the currently running one, and "emerge > >> virtualbox-modules". > > > > I _did_ call > > > > # eselect kernel set 2 > > > > and, as I wrote > > > > # emerge -av @module-rebuild > > > > as I always do. > > My experience is that sort of thing doesn't help. Dunno why, but all the > "pick up changed dependencies" don't pick virtualbox up. > > > Anyway, a "depmod -a " helped. > > I'll have to try that. The only thing that's ever worked for me in the > past is explicitly emerging again. > > Thanks, > Cheers, > Wol
All I usually do is build/install a new kernel, run 'emerge -1v @module- rebuild' and reboot. On occasions when I forgot to run @module-rebuild before I reboot with the new kernel, I ran it afterwards followed by a successful modprobe. From what I recall it just worked. What won't work is running modprobe while still running an old kernel, but the symlink while rebuilding any modules is pointing to a new kernel. I can't explain Bertram's experience.
signature.asc
Description: This is a digitally signed message part.
