| 1 |
Stroller <stroller@××××××××××××××××××.uk> writes: |
| 2 |
|
| 3 |
[...] |
| 4 |
|
| 5 |
> I would be looking primarily at the next point the word "error" comes up properly, which is here: |
| 6 |
> |
| 7 |
> from /var/tmp/portage/app-emulation/virtualbox-guest-additions-5.1.14/work/VirtualBox-5.1.14/src/VBox/Runtime/common/alloc/alloc.cpp:34: |
| 8 |
> /lib/modules/4.9.10-gentoo/build/arch/x86/include/asm/atomic.h: In function ‘int atomic_read(const atomic_t*)’: |
| 9 |
> /lib/modules/4.9.10-gentoo/build/include/linux/compiler.h:305:42: error: uninitialized const member in ‘union atomic_read(const atomic_t*)::<anonymous>’ |
| 10 |
> union { typeof(x) __val; char __c[1]; } __u; \ |
| 11 |
|
| 12 |
|
| 13 |
First off, thanks for the leg work on this. |
| 14 |
|
| 15 |
Using search terms from your finding: |
| 16 |
I did find something that might make some difference on the error you |
| 17 |
found (above). |
| 18 |
|
| 19 |
https://bugs.gentoo.org/show_bug.cgi?id=603472 |
| 20 |
|
| 21 |
It is a bug already on the bug setup... and one of the heavy hitters |
| 22 |
there has this to say: |
| 23 |
|
| 24 |
"Lars Wendler (Polynomial-C) gentoo-dev 2017-02-08 15:44:54 UTC |
| 25 |
This is an issue that - according to upstream - will not be fixed anytime soon. |
| 26 |
So I suggest to use 4.4 LTS kernel for Gentoo guests VMs for the time being." |
| 27 |
|
| 28 |
Maybe if I backed up to a 4.4 kernel I'd have better luck. |
| 29 |
|
| 30 |
However, I can report that if USER reinstalls the standard vbox |
| 31 |
guest-additions that come with each release of vbox (It can be |
| 32 |
initiated by the `Devices' menu on the vbox interface (last item = |
| 33 |
Insert Guest additions into cdrom )). (And does it enough times) It |
| 34 |
seems to work thereafter, (the needed module is present) assuming that |
| 35 |
installation finishes with no errors. |
| 36 |
|
| 37 |
After wards I saw the glad tidings: |
| 38 |
|
| 39 |
reader > sudo lsmod |
| 40 |
Module Size Used by |
| 41 |
vboxvideo 36795 2 |
| 42 |
vboxguest 201560 4 vboxvideo |
| 43 |
ttm 69735 1 vboxvideo |
| 44 |
|
| 45 |
It seems to matter when you install the vbox [not from portage] |
| 46 |
guest-additions because I did so several times during my efforts to |
| 47 |
get X working. Finally it made a difference. |
| 48 |
|
| 49 |
You are expected to re-install them after any kernel build but I did |
| 50 |
that as well and still it only worked after a certain point... maybe |
| 51 |
once I managed to get enough stuff installed from emerge. |
| 52 |
|
| 53 |
So, to summarize It appears you are not likely to get things working |
| 54 |
with too new a kernel but can possibly fall back on repeated |
| 55 |
reinstalls of the vbox guest-additions. |
| 56 |
|
| 57 |
In my case I've succesfully built a 4.9.10 kernel and managed to get X |
| 58 |
working even though two virtual-box packages from portage failed to |
| 59 |
build |
| 60 |
x11-drivers/xf86-video-virtualbox-5.1.14 |
| 61 |
app-emulations/virtualbox-guest-additionsvirtualbox-guest-additions |
| 62 |
|
| 63 |
So, I've got X up and successfully installed my desktop of choice |
| 64 |
lxde. Things are looking up. |
Archives