IBM T40p laptop. Has both stick mouse and touchpad. anaconda-written X config only had a Synaptics section - no mouse section. So the stick mouse didn't work. rawhide-20060726
Per ajax, this should work. If not, it's an X server bug.
notting, can you attach your X log and config?
Created attachment 133194 [details] X.org config file (written by anaconda)
Created attachment 133195 [details] X.org log file
Erm, assume Load "synaptics" isn't commented out. It behaves the same regardless.
*** Bug 201909 has been marked as a duplicate of this bug. ***
Fixed in xorg-x11-server-1.1.1-20, verified on my thinkpad. Now, if parsing the log file reveals no instances of the mouse driver or of the void driver, the server synthesizes a mouse device section.
*** Bug 202342 has been marked as a duplicate of this bug. ***
I pulled in 1.1.1-21 today after a 2 week holiday and i've been running xorg without a mouse section in xorg.conf for a while, to allow auto-detection. As of -21 (or probably -20, as read in post #7), it creates 2 devices, so the mouse moves twice as fast. It used to create only 1, so it worked fine before. Here's the relevant section of the log: (WW) <default pointer>: No Device specified, looking for one... (II) <default pointer>: Setting Device option to "/dev/input/mice" (--) <default pointer>: Device: "/dev/input/mice" (==) <default pointer>: Protocol: "Auto" (**) Option "CorePointer" (**) <default pointer>: Core Pointer (==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50 (**) <default pointer>: ZAxisMapping: buttons 4 and 5 (**) <default pointer>: Buttons: 9 (WW) <default pointer>: No Device specified, looking for one... (II) <default pointer>: Setting Device option to "/dev/input/mice" (--) <default pointer>: Device: "/dev/input/mice" (==) <default pointer>: Protocol: "Auto" (**) Option "AlwaysCore" (**) <default pointer>: always reports core events (==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50 (**) <default pointer>: ZAxisMapping: buttons 4 and 5 (**) <default pointer>: Buttons: 9
*** Bug 203021 has been marked as a duplicate of this bug. ***
*** Bug 203305 has been marked as a duplicate of this bug. ***