Bug 139072

Created attachment 106600 [details]
log file of Xorg after modifying the Xorg.conf in step 4

If you have synaptics rpm installed, then you'll find additional info
on how get it working in /usr/share/doc/synaptics. Particularly it's
needed to recompile kernel adding some features (evdev) and even patch
it beforehand, if you have ALPS synaptics touchpad. 
I'm going to do the same and my assumption is that after this
patch/compile there'll be additional event handler in /proc...

CONFIG_MOUSE_PS2=y
CONFIG_INPUT_EVDEV=y

these are already in the config of the standard FC3 kernel, so i guess  i don't need to 
recompile
i don't have a ALPS touchpad
i just want to get the basic pointing/clicking to work, no special features like tap

here is the resolution:

i added "i8042.nomux" to the kernel line in /etc/grub.conf

the touchpad worked after the next reboot

i guess this should either be added to the grub.conf automatically, or it should work 
without it beeing there

An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

i've changed the bug to "fc4" since it still occurs still with a fully updated fc4 system (kernel 1398 or 
something)

so, the touchpad only works if "i8042.nomux" is in the kernel line in "/etc/grub.conf"

i've also "psmouse=proto.imps" in the kernel line so if this might cause problems plese tell me so i can 
retest without it

Confirmed that I'm having similar in the latest FC4 kernel (actually,
I'm on devel 2.6.12-1.1446_FC4 for various reasons) on my IBM T40
thinkpad.  As stated above, EVDEV is compiled into the standard
kernel, as is SHMEM. My xorg.conf sections:

Section "ServerLayout"
        Identifier     "Default Layout"
        Screen      0  "Screen0" 0 0
        InputDevice    "Mouse0" "CorePointer"
        InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "Synaptics" "AlwaysCore"
EndSection

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "IMPS/2"
        Option      "Device" "/dev/input/mice"
        Option      "ZAxisMapping" "4 5"
        Option      "Emulate3Buttons" "yes"
EndSection

Section "InputDevice"
        Identifier  "Synaptics"
        Driver      "synaptics"
        Option      "Device" "/dev/input/event0"
        Option      "Protocol" "event"
        Option "SendCoreEvents"
        Option "SHMConfig" "on"
        Option "LeftEdge" "1900"
        Option "RightEdge" "5400"
(etc.)
EndSection

Without "i8042.nomux" on the grub kernel line, Xorg.0.log:
(II) Synaptics touchpad driver version 0.14.0
Synaptics no synaptics event device found (checked 3 nodes)
(**) Option "Device" "/dev/input/mice"
Query no Synaptics: 6003C8
(EE) Synaptics no synaptics touchpad detected and no repeater device
(EE) Synaptics Unable to query/initialize Synaptics hardware.
(EE) PreInit failed for input device "Synaptics"
(II) UnloadModule: "synaptics"
(II) XINPUT: Adding extended input device "Keyboard0" (type:
KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) Mouse0: ps2EnableDataReporting: succeeded

With "i8042.nomux" it seems to get a bit further:
(II) Synaptics touchpad driver version 0.14.0
(**) Option "Device" "/dev/input/event0"
(**) Option "SHMConfig" "on"
(**) Option "LeftEdge" "1900"
(**) Option "RightEdge" "5400"
(**) Option "TopEdge" "1400"
(**) Option "BottomEdge" "4500"
(**) Option "FingerLow" "25"
(**) Option "FingerHigh" "30"
(**) Option "MaxTapTime" "180"
(**) Option "MaxTapMove" "220"
(**) Option "VertScrollDelta" "100"
(EE) Synaptics no synaptics touchpad detected and no repeater device
(EE) Synaptics Unable to query/initialize Synaptics hardware.
(EE) PreInit failed for input device "Synaptics"
(II) UnloadModule: "synaptics"
(II) XINPUT: Adding extended input device "Keyboard0" (type:
KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) Mouse0: ps2EnableDataReporting: succeeded

# synclient -l
Can't access shared memory area. SHMConfig disabled?
(separate problem?)

# cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab54
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000078 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 event1
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

# ls -l /dev/input/event?
0 crw-rw----  1 root root 13, 64 Aug 25  2005 /dev/input/event0
0 crw-rw----  1 root root 13, 65 Aug 25  2005 /dev/input/event1

Sorry if it's a configuration problem, please put me right - I just
can't see it. My touchpad works fine - but as a normal mouse with no
synaptic enhancements.  I also boot with "psmouse.proto=imps" as I've
found mouse behaviour erratic without but removing this doesn't help.
I've also tried "auto-dev" as protocol /dev/input/mice as device - 
- doesn't find it at all.  The synaptics docs conflict somewhat over
what to use. Is this a bug, or am I just doing something wrong?

Mass update to all FC4 bugs:

An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (2.6.13.2). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.

Please retest with this update, and update this bug if necessary.

Thanks.

as of  2.6.13-1.1526_FC4 the addition of "i8042.nomux" is still needed to get the touchpad to do 
anything. "psmouse=proto.imps" isn't needed and doesn't have an impact. 
bug still open

2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.

Thank you.

still the same with "2.6.14-1.1637_FC4"
why don't you just close it as WONTFIX, if you aren't going to fix it anyway...?

it's not a case of not wanting to fix it, it's a case of the number of bugs
filed overwhelming developers.

The lack of hardware to test with also means we're somewhat dependant on being
hopeful that upstream changes will correct the problem.  Contacting the upstream
developers of the synaptics driver may help your situation, as those guys have
the hardware to test with, as well as knowledge of the driver internals.

What version of the synaptics rpm do you have installed ?

>it's not a case of not wanting to fix it, it's a case of the number of bugs filed overwhelming 
developers.
sorry didn't want to sound rude

>What version of the synaptics rpm do you have installed ?
0.14.0-2

>Contacting the upstream developers of the synaptics driver may help your situation
but shouldn't the touchpad work for basic point&click even without the synaptics driver?
from the homepage "A Synaptics touchpad by default operates in compatibility mode by emulating a 
standard mouse. However, by using a dedicated driver, more advanced features of the touchpad 
becomes available."
in this case this would be a kernel bug and not a bug in the synaptics driver?

maybe. but they know this hardware better than I do, and may be familiar with
this problem already, and have pointers to a solution.

This is a mass-update to all currently open kernel bugs.

A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

Thank you.

i've been working with upstream and this *should* be fixed in 2.6.16

great, thanks.
If you have a pointer to an upstream patch that solves it, I can backport it to
the next 2.6.15 update FC4 gets.

i was informed the bug is fixed in 2.6.16 because :
"With 2.6.16 "usb-handoff" will be active by default so everything should work out of the box."

i don't think backporting that is neccesary

thanks

fixed in FC5 due to having a 2.6.16-based kernel

[This comment added as part of a mass-update to all open FC4 kernel bugs]

FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel.  As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
to FC5.

Please retest with Fedora Core 5.

Thank you.

A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.