| 1 |
On Friday, 28 January 2022 12:53:12 GMT Wols Lists wrote: |
| 2 |
> On 28/01/2022 12:37, Bertram Scharpf wrote: |
| 3 |
> > On Friday, 28. Jan 2022, 10:45:01 +0000, Wols Lists wrote: |
| 4 |
> >> On 28/01/2022 09:10, Bertram Scharpf wrote: |
| 5 |
> >>> after a kernel update and a |
| 6 |
> >>> |
| 7 |
> >>> # emerge -av @module-rebuild |
| 8 |
> >>> |
| 9 |
> >>> the VirtualBox modules cannot be found any more. |
| 10 |
> >> |
| 11 |
> >> You've updated your kernel, and you need to rebuild the modules, WHICH |
| 12 |
> >> DOES |
| 13 |
> >> NOT HAPPEN BY DEFAULT. |
| 14 |
> >> |
| 15 |
> >> So, set your default kernel to the currently running one, and "emerge |
| 16 |
> >> virtualbox-modules". |
| 17 |
> > |
| 18 |
> > I _did_ call |
| 19 |
> > |
| 20 |
> > # eselect kernel set 2 |
| 21 |
> > |
| 22 |
> > and, as I wrote |
| 23 |
> > |
| 24 |
> > # emerge -av @module-rebuild |
| 25 |
> > |
| 26 |
> > as I always do. |
| 27 |
> |
| 28 |
> My experience is that sort of thing doesn't help. Dunno why, but all the |
| 29 |
> "pick up changed dependencies" don't pick virtualbox up. |
| 30 |
> |
| 31 |
> > Anyway, a "depmod -a " helped. |
| 32 |
> |
| 33 |
> I'll have to try that. The only thing that's ever worked for me in the |
| 34 |
> past is explicitly emerging again. |
| 35 |
> |
| 36 |
> Thanks, |
| 37 |
> Cheers, |
| 38 |
> Wol |
| 39 |
|
| 40 |
All I usually do is build/install a new kernel, run 'emerge -1v @module- |
| 41 |
rebuild' and reboot. On occasions when I forgot to run @module-rebuild before |
| 42 |
I reboot with the new kernel, I ran it afterwards followed by a successful |
| 43 |
modprobe. From what I recall it just worked. |
| 44 |
|
| 45 |
What won't work is running modprobe while still running an old kernel, but the |
| 46 |
symlink while rebuilding any modules is pointing to a new kernel. I can't |
| 47 |
explain Bertram's experience. |
Archives