1 |
Duncan, |
2 |
thank you. Still nothing is working for me. Here's my make.conf |
3 |
|
4 |
CFLAGS="-march=athlon64 -Os -pipe" |
5 |
CXXFLAGS="${CFLAGS}" |
6 |
CHOST="x86_64-pc-linux-gnu" |
7 |
MAKEOPT="-j3" |
8 |
#FEATURES="ccache" |
9 |
#FEATURES="-sandbox emerge sandbox" |
10 |
USE="X acpi aiglx alsa aoss apache2 asf bzip2 cairo d fam firefox gdm gif |
11 |
glitz gphoto2 gstreamer gtk imap jpeg json laptop mad mng mp3 mp4 mpeg |
12 |
mysql nptl nptlonly ntfs nvidia opengl pdf png pop pop3d postfix |
13 |
quicktime raw remote samba scp screen scsh smime smp smtp spell sqlite |
14 |
svg symlink syslog threads tiff tk truetype unicode x264 xcb xcomposite |
15 |
xine xml xorg xscreensaver xterm-color xv xvid -arts -dbus -eds -esd -evo |
16 |
-games -ipv6 -kde -langpacks -mono -nautilus -nspr -nss -php |
17 |
-qt3 -qt4 -servletapi -sesame2 -session -gnome hal" |
18 |
|
19 |
VIDEO_CARDS="nv vesa fbdev nvidia" |
20 |
INPUT_DEVICES="evdev keyboard mouse synaptics" |
21 |
#PORTDIR_OVERLAY=/usr/portage-overlay/ |
22 |
|
23 |
And I have this at the top of my xorg.conf: |
24 |
Section "ServerLayout" |
25 |
Identifier "X.org Configured" |
26 |
Screen 0 "Screen0" 0 0 |
27 |
InputDevice "Mouse0" "CorePointer" |
28 |
InputDevice "Synaptics Touchpad" "CorePointer" |
29 |
InputDevice "Keyboard0" "CoreKeyboard" |
30 |
EndSection |
31 |
|
32 |
Section "ServerFlags" |
33 |
Option "AutoAddDevices" "true" |
34 |
Option "AutoEnableDevices" "true" |
35 |
Option "AllowEmptyInput" "false" |
36 |
EndSection |
37 |
|
38 |
Section "Files" |
39 |
ModulePath "/usr/lib64/xorg/modules" |
40 |
FontPath "/usr/share/fonts/misc/" |
41 |
FontPath "/usr/share/fonts/TTF/" |
42 |
FontPath "/usr/share/fonts/OTF" |
43 |
FontPath "/usr/share/fonts/Type1/" |
44 |
FontPath "/usr/share/fonts/100dpi/" |
45 |
FontPath "/usr/share/fonts/75dpi/" |
46 |
EndSection |
47 |
|
48 |
My kernel has the event inteface support. |
49 |
I was not able to properly install HAL, and this is the only |
50 |
possibility of the problems, I am getting a file colisiont problem. |
51 |
Since I didn't have hal enabled (I don't see why I need it), I did |
52 |
enable it now, and emerge update. |
53 |
This is what I get at the end, then it stops there "emerge --update |
54 |
--newuse --deep world" |
55 |
|
56 |
* /etc/udev/rules.d/90-hal.rules |
57 |
* /sbin/umount.hal |
58 |
* /lib/udev/hal_unmount |
59 |
* /usr/lib64/libhal.so.1 |
60 |
* /usr/lib64/libhal.so |
61 |
* /usr/lib64/libhal-storage.so.1 |
62 |
* /usr/lib64/libhal-storage.so |
63 |
* /usr/lib64/hal/scripts/linux/hal-system-wol-enable-linux |
64 |
* /usr/lib64/hal/scripts/linux/hal-system-wol-enabled-linux |
65 |
* /usr/lib64/hal/scripts/linux/hal-system-wol-supported-linux |
66 |
* |
67 |
* Searching all installed packages for file collisions... |
68 |
* |
69 |
* Press Ctrl-C to Stop |
70 |
* |
71 |
* None of the installed packages claim the file(s). |
72 |
* |
73 |
* Package 'sys-apps/hal-0.5.11-r8' merged despite file collisions. If |
74 |
* necessary, refer to your elog messages for the whole content of the |
75 |
* above message. |
76 |
|
77 |
Any idea ? |
78 |
|
79 |
|
80 |
|
81 |
On Sun, Apr 12, 2009 at 10:57 AM, Duncan <1i5t5.duncan@×××.net> wrote: |
82 |
> Mansour Al Akeel <mansour.alakeel@×××××.com> posted |
83 |
> 20090412081011.GA4008@××××.lan, excerpted below, on Sun, 12 Apr 2009 |
84 |
> 05:10:11 -0300: |
85 |
> |
86 |
>> Martin, thank you for the fast reply. I just tried recompiling the |
87 |
>> drivers under x11-driver/* but still no luck. |
88 |
>> |
89 |
> |
90 |
> I don't see a Serverflags section in your xorg.conf, which means if you |
91 |
> have compiled xorg-server with the hal USE flag it almost certainly WILL |
92 |
> ignore your xorg.conf InputDevice section settings and hotplug using HAL. |
93 |
> |
94 |
> (No, I'm not sure what it does if you emerge xorg-server with USE=-hal.) |
95 |
> |
96 |
> Here's a quote from the xorg.conf manpage, Serverflags section, for the |
97 |
> particular option in question: |
98 |
> |
99 |
> Option "AllowEmptyInput" "boolean" |
100 |
> |
101 |
> If enabled, don't add the standard keyboard and mouse drivers, |
102 |
> if there are no input devices in the config file. Enabled by |
103 |
> default if AutoAddDevices and AutoEnableDevices is enabled, |
104 |
> otherwise disabled. If AllowEmptyInput is on, devices using |
105 |
> the kbd, mouse or vmmouse driver are ignored. |
106 |
> |
107 |
> (As noted there's the related AutoAddDevices and AutoEnableDevices |
108 |
> options as well. They're enabled by default, so this one is as well.) |
109 |
> |
110 |
> As I've posted in other threads, this is all covered in Gentoo's xorg- |
111 |
> server 1.5 upgrade guide, with the various configuration alternatives, |
112 |
> here (watch the wrap): |
113 |
> |
114 |
> http://www.gentoo.org/proj/en/desktop/x/x11/xorg-server-1.5-upgrade- |
115 |
> guide.xml |
116 |
> |
117 |
> The idea is to use hal hotplugging goodness by default but allow fallback |
118 |
> to the xorg.conf configured drivers when hal breaks. |
119 |
> |
120 |
> Note that the upgrade guide has a link to a special hal *.fdi file for |
121 |
> synaptics users. You can drop that into /etc/hal/fdi/policy, making any |
122 |
> modifications to it you'd like just as you would to the xorg.conf |
123 |
> InputDevice section for a synaptics pad, and it should work. |
124 |
> |
125 |
> |
126 |
> FWIW, when I first upgraded here (I'm on ~arch so I upgraded some time |
127 |
> ago), I had all sorts of problems, because it was trying to default to |
128 |
> evdev, which I didn't have compiled for xorg or the kernel either one! I |
129 |
> temporarily solved that by using the AllowEmptyInput option above, then |
130 |
> later, thus getting mouse and keyboard working normally again, then only |
131 |
> later, when I had time to mess with it, tried the evdev stuff. |
132 |
> |
133 |
> When I DID try evdev I followed the (then) upgrade guide, and STILL |
134 |
> couldn't get it to work. After trying various *.fdi edits for hours, I |
135 |
> eventually realized I needed evdev enabled in my kernel as well. The |
136 |
> upgrade guide at the time mentioned enabling it in INPUT_DEVICES in |
137 |
> make.conf but did *NOT* mention the kernel. That was only a few days |
138 |
> before they went stable with the new version and upgrade guide so I had |
139 |
> to hustle to get the bug in and they had to hustle to get the |
140 |
> instructions for the kernel added, but my experience and bug is why |
141 |
> that's in the upgrade guide now. |
142 |
> |
143 |
> After I enabled evdev in the kernel, it pretty much "just worked", altho |
144 |
> I did need to modify a *.fdi file based on the various documentations to |
145 |
> match the keyboard key and merge an input.x11.options.XkbModel key with a |
146 |
> value changed from the default "evdev" to "microsoftpro", to enable the |
147 |
> extra keys on my Logitech keyboard. That bit is roughly the same except |
148 |
> for the keyboard as you're doing for the mouse by dropping that synaptics |
149 |
> *.fdi file in that policy subdir as I mentioned above. |
150 |
> |
151 |
> One final thing. Anybody with SDL merged for anything (often games) |
152 |
> should pay attention to the troubleshooting tip at the bottom of the |
153 |
> upgrade guide. I'm not sure it applies to a synaptics, but at least a |
154 |
> regular mouse won't work in SDL apps using evdev, otherwise. I noticed |
155 |
> my DOSBOX/SDL keyboard mapping is a bit funky using the evdev keyboard |
156 |
> driver too, but DOSBOX has a remapping tool, which has worked for now. |
157 |
> Maybe I'll look into that angle further later, but the hint about |
158 |
> disabling dga for SDL apps using the mouse sure helped for it! |
159 |
> |
160 |
> -- |
161 |
> Duncan - List replies preferred. No HTML msgs. |
162 |
> "Every nonfree program has a lord, a master -- |
163 |
> and if you use the program, he is your master." Richard Stallman |
164 |
> |
165 |
> |
166 |
> |