| 1 |
Alan McKinnon <alan.mckinnon@×××××.com> writes: |
| 2 |
|
| 3 |
> On 07/12/2016 17:34, Harry Putnam wrote: |
| 4 |
>> Setup: |
| 5 |
>> |
| 6 |
>> gentoo 32bit vbox guest on win 10 64bit host |
| 7 |
>> Installed xorg-server, lxde Meta pkgs and deps |
| 8 |
>> (along with many other pkgs ... to many to list |
| 9 |
>> here but included at the end) |
| 10 |
>> |
| 11 |
>> uname -a: |
| 12 |
>> Linux g0 4.8.8-gentoo #2 Fri Nov 18 20:16:14 EST 2016 i686 Intel(R) |
| 13 |
>> Xeon(R) CPU X5450 @ 3.00GHz GenuineIntel GNU/Linux |
| 14 |
>> |
| 15 |
>> Theoretically the install should be ready now to run X and lxde. |
| 16 |
>> However, when I run `startlxde' nothing whatsoever happens. At least |
| 17 |
>> not at the command line or visibly. Prompt just returns lamely. |
| 18 |
>> |
| 19 |
>> However, if I run startx. The vm crashes clear to power off or |
| 20 |
>> sometimes just becomes inoperable with these error messages showing. |
| 21 |
>> (Note: nothing can be clicked moved or etc at this point) |
| 22 |
> |
| 23 |
> |
| 24 |
> |
| 25 |
> Your first problem seems to be you don't have any input or output |
| 26 |
> devices. Please post |
| 27 |
> |
| 28 |
> - eix xorg-server |
| 29 |
> - values of INPUT_DEVICES and VIDEO_CARDS from make.conf |
| 30 |
|
| 31 |
> - confirm that you built the kernel with evdev and the kernel module is |
| 32 |
> loaded |
| 33 |
|
| 34 |
harry > eix xorg-server |
| 35 |
[I] x11-base/xorg-server |
| 36 |
Available versions: 1.12.4-r5(0/1.12.4) 1.12.4-r7(0/1.12.4) 1.15.2-r2(0/1.15.2) 1.15.2-r4(0/1.15.2) 1.16.4(0/1.16.1) 1.16.4-r5(0/1.16.1) 1.17.4(0/1.17.4) (~)1.18.0(0/1.18.0) (~)1.18.1(0/1.18.1) (~)1.18.2(0/1.18.2) (~)1.18.3(0/1.18.3) 1.18.4(0/1.18.4) [M](~)1.19.0(0/1.19.0) **9999(0/9999) {dmx doc glamor ipv6 kdrive libressl minimal nptl selinux static-libs +suid systemd tslib +udev unwind wayland xephyr xnest xorg xvfb} |
| 37 |
Installed versions: 1.18.4(21:29:32 12/06/16)(doc glamor suid udev xorg -dmx -ipv6 -kdrive -libressl -minimal -selinux -static-libs -systemd -tslib -unwind -wayland -xephyr -xnest -xvfb) |
| 38 |
Homepage: https://www.x.org/wiki/ |
| 39 |
Description: X.Org X servers |
| 40 |
|
| 41 |
------- --------- ---=--- --------- -------- |
| 42 |
|
| 43 |
harry > grep VIDEO /etc/portage/make.conf |
| 44 |
VIDEO_CARDS="virtualbox" |
| 45 |
|
| 46 |
I don't have anthing in make.conf about Input devices nor have I had |
| 47 |
on 2 other gentoo installs that successfully ran lxde. |
| 48 |
|
| 49 |
I've used the same make.conf with little variation on all three |
| 50 |
|
| 51 |
------- ------- ---=--- ------- ------- |
| 52 |
|
| 53 |
harry > cd /lib/modules |
| 54 |
|
| 55 |
harry > grep -r evdev.ko * |
| 56 |
Binary file 4.8.8-gentoo/modules.dep.bin matches |
| 57 |
4.8.8-gentoo/modules.order:kernel/drivers/input/evdev.ko |
| 58 |
4.8.8-gentoo/modules.dep:kernel/drivers/input/evdev.ko: |
| 59 |
|
| 60 |
------- ------- ---=--- ------- ------- |
| 61 |
|
| 62 |
harry > sudo lsmod |
| 63 |
Module Size Used by |
| 64 |
vboxguest 171071 0 |
| 65 |
evdev 8704 0 |
| 66 |
|
| 67 |
|
| 68 |
> There's a decent X11 install page on the gentoo wiki, did you follow it? |
| 69 |
> Installing on vbox is not too different from installing on metal except |
| 70 |
> you don't use the video driver for the physical card, you use the vbox |
| 71 |
> one (it's virtualized). |
| 72 |
|
| 73 |
I used the gentoo lxde wiki, which basically says that once you've got |
| 74 |
a basic gentoo install AND the xorg-server is installed you are ready |
| 75 |
to install lxde. It recommends using the meta package which I did. |
| 76 |
|
| 77 |
I assumed emerge would take care of dependants. |
| 78 |
|
| 79 |
> Lastly, why a 32 bit guest on a 64 bit host? There's little benefit from |
| 80 |
> doing that, and amd64 is far better supported in general than x86_64. |
| 81 |
> Plus you just create more work for the host. |
| 82 |
|
| 83 |
Does that have bearing on my problem? |
| 84 |
|
| 85 |
There were two reasons: |
| 86 |
1) I hadn't yet found the BIOS switch to turn on Virtualization and |
| 87 |
the newer VBox since late 4.XX I think, do not even offer 64 bit |
| 88 |
if it is not set in bios. So the vbox version I used didn't have |
| 89 |
that on offer. |
| 90 |
|
| 91 |
2) I found the discussions about the new approach with 2 sets of |
| 92 |
libraries and so forth to be pretty confusing... don't recall now |
| 93 |
exactly what things confused me... so I went straight 32 bit with the |
| 94 |
idea it would be less confusing. And for 2 gentoo installs that |
| 95 |
seemed to be born out. |
| 96 |
|
| 97 |
Since I had no trouble with those, thought I would stay with the tried |
| 98 |
and true approach. But apparently I missed something important or |
| 99 |
some such. |
Archives