1 |
On Thursday, 4 February 2021 17:25:35 GMT n952162 wrote: |
2 |
|
3 |
> Sorry, if I gave the impression, when I said: |
4 |
> |
5 |
> /I tried that (using "module-rebuild")/ |
6 |
> |
7 |
> that I ran it without the "@". I was just referring to the original |
8 |
> suggestion had "@module*s*-rebuild". |
9 |
|
10 |
Oops! My apologies - I was running from apparently faulty memory! :-) |
11 |
|
12 |
|
13 |
> Did you run on the host, after you updated your VBox: |
14 |
> |
15 |
> emerge -uaDv @modules-rebuild |
16 |
> |
17 |
> In fact, it had emerged successfully: |
18 |
> |
19 |
> ... |
20 |
> [ebuild U ] sys-libs/timezone-data-2020e::gentoo |
21 |
> [2020d::gentoo] USE="nls -leaps-timezone -zic-slim" 659 KiB |
22 |
> [ebuild U ] app-eselect/eselect-pinentry-0.7.1::gentoo |
23 |
> [0.7::gentoo] 0 KiB |
24 |
> [ebuild U ] virtual/perl-Data-Dumper-2.174.0-r2::gentoo |
25 |
> [2.174.0-r1::gentoo] 0 KiB |
26 |
> [ebuild NS ] sys-kernel/gentoo-sources-5.4.92:5.4.92::gentoo |
27 |
> [4.19.86:4.19.86::gentoo, 5.4.38:5.4.38::gentoo, |
28 |
> 5.4.66:5.4.66::gentoo, 5.4.80-r1:5.4.80-r1::gentoo] USE="-build |
29 |
> -experimental -symlink" 2938 KiB |
30 |
> |
31 |
> Total: 4 packages (3 upgrades, 1 in new slot), Size of downloads: |
32 |
> 3596 KiB |
33 |
> ... |
34 |
> |
35 |
> but failed to run. |
36 |
> |
37 |
> > I assume you have already installed 'app-emulation/virtualbox-modules' at |
38 |
> > least once, if VBox was working OK until recently? Otherwise, emerge the |
39 |
> > package 'app-emulation/virtualbox-modules' and modprobe each module |
40 |
> > keeping an eye in dmesg to make sure they load without further errors. |
41 |
> |
42 |
> I followed this advice, to load each module (from equery files |
43 |
> virtualbox-modules) by hand, and that worked, for whatever reason that |
44 |
> it didn't work before after unloading the modules by hand, as |
45 |
> recommended by Jack ... they were not loaded when I just loaded them now |
46 |
> ... ah - naturally, I loaded them with sudo, but didn't use sudo when I |
47 |
> ran startvm ... Hmmm. We'll see how it starts up tomorrow ;-) |
48 |
|
49 |
OK, as long as the VBox modules were rebuilt after the new kernel symlink was |
50 |
set under /usr/src/linux they should (re)load after a reboot. |
51 |
|
52 |
Loading modules manually requires you run modprobe as root. |
53 |
|
54 |
However, you do not need to start VBox as root, arguably you shouldn't. Just |
55 |
make sure your user is a member of group "vboxusers": |
56 |
|
57 |
# gpasswd -a <user> vboxusers |
58 |
|
59 |
Logout/in as the named user before you can run VBox again. |
60 |
|
61 |
More info you should need it can be found here: |
62 |
|
63 |
https://wiki.gentoo.org/wiki/VirtualBox |