Bug 135239 - kernel needs i8042.nomux boot option to correctly detect Synaptics TouchPad
Summary: kernel needs i8042.nomux boot option to correctly detect Synaptics TouchPad
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: i686 SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Vojtech Pavlik
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-22 22:50 UTC by Philip Tuckey
Modified: 2005-11-23 18:26 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
boot.msg showing Synaptics touchpad detection (29.49 KB, text/plain)
2005-11-22 22:56 UTC, Philip Tuckey 		Details
boot.msg showing only generic PS/2 mouse detection (23.71 KB, text/plain)
2005-11-22 22:58 UTC, Philip Tuckey 		Details
Output of dmidecode (15.52 KB, text/plain)
2005-11-23 14:05 UTC, Philip Tuckey 		Details
Patch to add the S7010 to MUX blacklist (825 bytes, patch)
2005-11-23 15:51 UTC, Vojtech Pavlik 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Tuckey 2005-11-22 22:50:45 UTC 
This is using kernel 2.6.13-15-default.
Without i8042.nomux, kernel detects only "PS/2 Generic Mouse on isa0060/serio4"
With i8042.nomux, kernel detects "SynPS/2 Synaptics TouchPad on isa0060/serio1", which then works fine with the Xorg synaptics driver. (This boot option also cures mouse synchronisation loss craziness when resuming from a suspend.)
Hardware is a Fujitsu-Siemens Lifebook S7010.
I will attach boot.msg files showing this behaviour.
Comment 1 Philip Tuckey 2005-11-22 22:56:21 UTC 
Created attachment 58314 [details]
boot.msg showing Synaptics touchpad detection
Comment 2 Philip Tuckey 2005-11-22 22:58:20 UTC 
Created attachment 58315 [details]
boot.msg showing only generic PS/2 mouse detection
Comment 5 Vojtech Pavlik 2005-11-23 10:08:45 UTC 
Can you please provide the output of 'dmidecode' on your machine?
We need to add it to the list of machine (mostly from Fujitsu-Siemens) which
don't have working Active Multiplexing implementations, resulting in incorrect
detection of attached devices, and other troubles during operation (lost sync, etc).
Comment 6 Philip Tuckey 2005-11-23 14:05:04 UTC 
Created attachment 58420 [details]
Output of dmidecode
Comment 7 Vojtech Pavlik 2005-11-23 15:51:00 UTC 
Created attachment 58453 [details]
Patch to add the S7010 to MUX blacklist

This patch will fix the problem. It'll be added to
the upstream kernel soon.
Comment 8 Vojtech Pavlik 2005-11-23 15:52:03 UTC 
Thanks for reporting the problem, and giving your dmidecode. The above
patch will be applied to upstream kernel soon. Until then, please use the
kernel option (add it to /boot/grub/menu.lst).
Comment 9 Philip Tuckey 2005-11-23 18:26:43 UTC 
OK, thanks.