On Fri, 28 Jan 2022 13:10:36 +0000, Michael 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.
In Bertram's case, emerge did build modules for the new kernel, as evidenced by the find output he gave. The modules were there, in the path that modprobe said they weren't, which is why a lack of depmod was my first suspect. This may just be one of those things where the phase of the moon conflicted with Bertram's star sign, or it may be reproducible, in which case filing a bug report would help. -- Neil Bothwick There was a young man from the border Who had an attention disorder. When he reached the last line He would run out of time And
pgpejDKjGnU7S.pgp
Description: OpenPGP digital signature
