1 |
On 04/28/2016 06:07 PM, waltdnes@××××××××.org wrote: |
2 |
> On Thu, Apr 28, 2016 at 08:33:01AM -0500, Corbin wrote |
3 |
>> |
4 |
>> |
5 |
>> Questions ... if you will permit : |
6 |
>> |
7 |
>> Are you saying that in "make.conf" you set INPUT_DEVICES="evdev" and did |
8 |
>> a test compile run? |
9 |
>> The emerge you tried ... was it "xorg-base/xorg-x11"? |
10 |
>> Or did you try a meta package for a desktop? |
11 |
> |
12 |
> xorg-server, intending to add ICEWM later. |
13 |
> |
14 |
>> If a hard dependency link between Xorg server -> xf86-input-keyboard |
15 |
>> exists, this will never work. I have no idea at this point if this is |
16 |
>> true. What I have been reading suggests that the xf86-input keyboard and |
17 |
>> mouse libs are being phased out. |
18 |
>> |
19 |
>> With that call ?error? ... Xorg may be an impossible goal / waste of |
20 |
>> time on uClibc. |
21 |
> |
22 |
> I tried INPUT_DEVICES="evdev mouse keyboard", which probably caused |
23 |
> the problem. With INPUT_DEVICES="evdev" and VIDEO_CARDS="vesa fbdev", |
24 |
> things build OK. Whether they'll work, I don't know, but at least it |
25 |
> builds. ICEWM appears to be building too. Actually, ICEWM has a |
26 |
> "(uclibc)" USE flag which is automatically hard-invoked or hard-masked |
27 |
> depending on whether or not the system uses uclibc. |
28 |
> |
29 |
> James points to https://wiki.gentoo.org/wiki/Project:Hardened_uClibc |
30 |
> which mentions "Lilblue"... |
31 |
> |
32 |
>> Continued developments in uClibc have made it increasingly suitable |
33 |
>> for systems like Lilblue, our security-enhanced, fully featured |
34 |
>> XFCE4 desktop, amd64 system built on uClibc. |
35 |
> |
36 |
> WHEEEEEEEEEE! IT WOIKS! Whilst I was typing away, the ICEWM and |
37 |
> xterm builds finished. I've brought up the basic ICEWM window with 4 |
38 |
> work areas. The fixes to my problem were... |
39 |
> |
40 |
> INPUT_DEVICES="evdev" |
41 |
> VIDEO_CARDS="vesa fbdev" |
42 |
> enable "udev" flag in make.conf (actually it runs on eudev, but...) |
43 |
> |
44 |
> I've never used "evdev" before, so I was not familiar with how to set |
45 |
> it up. It's a bit disappointing, because evdev *DEMANDS* udev, so I can |
46 |
> forget about switching in busybox's mdev for udev. |
47 |
> |
48 |
> BTW, I stumbled over "1 weird little tip" on the internet, to make |
49 |
> debugging easier for many bootup problems, not just uclibc. Add the |
50 |
> "--noclear" option to the first console in /etc/inittab. With this |
51 |
> option, the initial login prompt does *NOT* clear away late bootup |
52 |
> output, including useful error messages... |
53 |
> |
54 |
> # TERMINALS |
55 |
> c1:12345:respawn:/sbin/agetty --noclear 38400 tty1 linux |
56 |
> c2:2345:respawn:/sbin/agetty 38400 tty2 linux |
57 |
> c3:2345:respawn:/sbin/agetty 38400 tty3 linux |
58 |
> c4:2345:respawn:/sbin/agetty 38400 tty4 linux |
59 |
> c5:2345:respawn:/sbin/agetty 38400 tty5 linux |
60 |
> c6:2345:respawn:/sbin/agetty 38400 tty6 linux |
61 |
> |
62 |
|
63 |
Great! Glad to hear it. |
64 |
|
65 |
Might want to update the forum posting ... or I can update the one I |
66 |
made with this info, if you want. |
67 |
|
68 |
It might save someone else a lot of head scratching :) |