1 |
On 04/27/2016 04:31 PM, waltdnes@××××××××.org wrote: |
2 |
> On Wed, Apr 27, 2016 at 12:25:41PM -0500, Corbin wrote |
3 |
>> |
4 |
>> On 04/27/2016 09:12 AM, waltdnes@××××××××.org wrote: |
5 |
>>> I'm testing uclibc in a 32-bit QEMU Gentoo VM. I want to eventually |
6 |
>>> install on my ancient 32-bit-only netbook. I'm running into problems. |
7 |
>>> See https://forums.gentoo.org/viewtopic-p-7912494.html |
8 |
>>> |
9 |
>>> To summarize... |
10 |
>>> * static IP works for eth0, but dhcpcd fails, which is bad news for a |
11 |
>>> laptop or netbook |
12 |
>>> * when building x-rg-server, the builds for xf86-input-keyboard and |
13 |
>>> xf86-video-intel fail to compile |
14 |
>>> * www-client/w3m fails to build, so I can't even get decent textmode |
15 |
>>> web browsing |
16 |
>>> |
17 |
>> |
18 |
>> You already found my test load :) |
19 |
>> Glad it helped someone. |
20 |
>> |
21 |
>> Did you have/add "evdev" in "make.conf" for INPUT_DEVICES? |
22 |
>> "evdev" is built-into-the-kernel or a kernel module. The newer input |
23 |
>> function, augmenting/replacing the AT keyboard and /dev/psaux. |
24 |
>> ( Seems "evdev" is almost replacing the functions of "xf86-input" |
25 |
>> libraries for Xorg.) |
26 |
> |
27 |
> No. Do I have to set something in the kernel? Will the keyboard work |
28 |
> with evdev and without xf86-input-keyboard? My netbook uses framebuffer |
29 |
> video driver, so I might try using that in the uclibc VM. |
30 |
> |
31 |
>> What CPU flags did you set/unset for the build? |
32 |
>> |
33 |
>> My reason for asking ... a lot of software has an unmarked dependency on |
34 |
>> "sse/sse2". If the info on the Atom CPU I found was correct ... it |
35 |
>> doesn't have sse/sse2 instruction sets. |
36 |
> |
37 |
> My Atom netbook has them, according to /proc/cpuinfo |
38 |
> |
39 |
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge |
40 |
> mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx |
41 |
> constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl |
42 |
> vmx est tm2 ssse3 xtpr pdcm movbe lahf_lm dtherm tpr_shadow vnmi |
43 |
> flexpriority |
44 |
> |
45 |
> Note also the "movbe" flag. *I CANNOT TEST RUN MY NETBOOK-OPTIMIZED |
46 |
> CODE I BUILD IN THE QEMU VM*. QEMU claims to emulate "Atom" CPUs. |
47 |
> There are over 100 different atoms in the periodic table known to |
48 |
> physicists, and Intel is just as bad, with all their "Atom" variants. |
49 |
> QEMU's "Atom" emulation does not support the "movbe" flag. So I simply |
50 |
> run with the host CPU in a 32-bit VM, and set "-march=native". When |
51 |
> building for the netbook, I build with "-march=bonnell". Important |
52 |
> distinction... |
53 |
> |
54 |
> different "-march" values != crossdev |
55 |
> |
56 |
> As long as the "CHOST" variable is identical, you can build for |
57 |
> different "-march" variants, even those that won't run in the build |
58 |
> environment. |
59 |
> |
60 |
>> Useful Info : https://wiki.gentoo.org/wiki/Safe_CFLAGS |
61 |
> |
62 |
> See also http://gentoo-en.vfose.ru/wiki/Safe_Cflags#-march.3Dnative |
63 |
> |
64 |
> gcc -march=native -E -v - </dev/null 2>&1 | grep cc1 |
65 |
> |
66 |
> Ignore all the fancy flags. Both of those pages come up with output |
67 |
> that shows "-march=bonnell" on my Atom |
68 |
> https://en.wikipedia.org/wiki/Bonnell_%28microarchitecture%29 |
69 |
> |
70 |
> I have a standard glibc 32-bit VM which I use for Gentoo distcc for |
71 |
> the Atom, as well as manually building Pale Moon web browser. I use the |
72 |
> following settings for both... |
73 |
> |
74 |
> CFLAGS="-O2 -march=bonnell -mfpmath=sse -pipe -fomit-frame-pointer \ |
75 |
> -fno-unwind-tables -fno-asynchronous-unwind-tables" |
76 |
> |
77 |
> CCFLAGS="${CFLAGS}" |
78 |
> |
79 |
> "-march=bonnell" implies all the other flags, so no need to enter them |
80 |
> into the CFLAGS variable. |
81 |
> |
82 |
> Thanks for that initial post. I had almost given up on even a minimal |
83 |
> install, before I found it. |
84 |
> |
85 |
|
86 |
Your Welcome. |
87 |
|
88 |
Link for "evdev" : https://en.wikipedia.org/wiki/Evdev |
89 |
|
90 |
The default kernel config has "evdev" built into the kernel. |
91 |
|
92 |
On my desktop, Nvidia drivers do look for and use "evdev" without |
93 |
Wayland support in Xorg. ( XFCE ) |
94 |
|
95 |
This might be pedantic ... |
96 |
... add "sse sse2 sse3 ssse3 mmx acpi -mmxext" to your USE flags in |
97 |
"make.conf" ( if not already present. ) Some packages look for those |
98 |
flags in strange ways. |
99 |
|
100 |
Using a one-problem-at-a-time approach ... |
101 |
|
102 |
< Proposed Test / Xorg Fix > |
103 |
... adding "libinput" to the USE flags in your "make.conf". |
104 |
... setting INPUT_DEVICES="evdev" in "make.conf". |
105 |
|
106 |
Desktops that should work with "libinput/evdev" ONLY are QT4, QT5, XFCE. |
107 |
XFCE provides its own keyboard library and config applets/plugins. Don't |
108 |
know about QT4 / QT5. |
109 |
|
110 |
If you have not already done this ... might want to set |
111 |
VIDEO_CARDS="fbdev vesa" or just "fbdev" to save compile time. |
112 |
|
113 |
This is getting very interesting. |
114 |
Please let us know how this works out :) |