Skip to contentSkip to conversation

2.6.0-mm1

DISCUSSION GCS 6 participants 27 messages Dec 24, 2003 – Dec 28, 2003 Input drivers

lore
Share & tools
lore

GCS

author
#0 lore raw

Hi,

Quoted 2 lines · Andrew Morton

It would be appreciated if people who have
significant patches in -mm could retest please.

It seems I can write CDs on my laptop now. AFAICR I was last trying it on
test8, but it was the same: if the image is over ~400Mb, the machine freezes hard. If it's shorter, then it's ok, but still some lock or sth is not unlocked, as the CPU is used more and more about five secs by one or two percent. Sooner or later it's crashed as well, but I could restart the machine before that happened. Rebooting to 2.4.2x and writing CDs there was working all the time.
So I do not know if it's fixed since test8, or in 2.6.0-mm1, but I am
happy with it. Also, I have two problems with 2.6.0-mm1:
- I can not deselect CONFIG_SCSI, only module or built-in available. Maybe something is depend on it, but could not figure out what (no CONFIG_BLK_DEV_IDESCSI, nothing is selected under CONFIG_SCSI).
- I have a synaptics touchpad, which is detected correctly, but only works if I set psmouse_noext=1. Under vanilla 2.6.0 it still works this way, but with 2.6.0-mm1 it works only on the console, but not under XFree86. Strange, as gpm interprets the input and pipes thru gpmdata to XFree86 4.3.0. Any idea what broke this configuration?

Thanks,
GCS

#1 lore raw
Quoted 17 lines · GCS

Hi,

Quoted 2 lines · Andrew Morton

It would be appreciated if people who have
significant patches in -mm could retest please.

It seems I can write CDs on my laptop now. AFAICR I was last trying it on
test8, but it was the same: if the image is over ~400Mb, the machine freezes hard. If it's shorter, then it's ok, but still some lock or sth is not unlocked, as the CPU is used more and more about five secs by one or two percent. Sooner or later it's crashed as well, but I could restart the machine before that happened. Rebooting to 2.4.2x and writing CDs there was working all the time.
So I do not know if it's fixed since test8, or in 2.6.0-mm1, but I am
happy with it. Also, I have two problems with 2.6.0-mm1:

Quoted 3 lines

- I can not deselect CONFIG_SCSI, only module or built-in available. Maybe something is depend on it, but could not figure out what (no CONFIG_BLK_DEV_IDESCSI, nothing is selected under CONFIG_SCSI).

Yes, this part of the config system is hard. It always has been. It's similar to "wtf do I have to enable to make the <foo> menu appear.

I bit of grepping tells us that CONFIG_USB_STORAGE turns on CONFIG_SCSI.

Quoted 5 lines

- I have a synaptics touchpad, which is detected correctly, but only works if I set psmouse_noext=1. Under vanilla 2.6.0 it still works this way, but with 2.6.0-mm1 it works only on the console, but not under XFree86. Strange, as gpm interprets the input and pipes thru gpmdata to XFree86 4.3.0. Any idea what broke this configuration?

Peter or Dmitry may be able to tell us.

author
#2 lore raw
Quoted 1 line · Andrew Morton

I bit of grepping tells us that CONFIG_USB_STORAGE turns on CONFIG_SCSI.

Thanks! Never throught. I could come up with this:
find . -name Kconfig| xargs grep --colour 'depends.* SCSI' (Execute in the kernel tree, and replace SCSI with whatever you like; may help others with similar questions).

Quoted 1 line

Peter or Dmitry may be able to tell us.

IMHO it's either:
serio-04-synaptics-cleanup.patch serio-06-synaptics-use-reconnect.patch synaptics-powerpro-fix.patch serio-pm-fix.patch input-02-add-psmouse_proto.patch (?) input-05-psmouse-fixes.patch input-07-remove-synaptics-config-option.patch (maybe?) input-08-synaptics-protocol-discovery.patch

Thus meanwhile I try to revert them. Anyway, as -mm1 is already bigger, is it possible that you release 2.6.1 in this year with some/most of the fixes in mm1?

GCS

author
#3 lore raw
Quoted 1 line · GCS

input-02-add-psmouse_proto.patch (?)

Just found out psmouse_noext is deprecated. I have specified
psmouse_proto then, but imps and exps (and bare too, but I have not tested it, as reading the code it seems psmouse_noext falls back to bare) are the same. On the console touchpad is working, under XFree86 4.3.0 is not. To be more specific, the buttons do work, but I can not move the pointer at all. Well, first I thought the middle two buttons are for scrolling, as they are placed (and IIRC, they do scroll under m$ win), but the top button is like the left button and the bottom button is for paste, ie middle button on three buttons mices.

GCS

#6 lore raw
In reply to Andrew Morton
Quoted 7 lines · Andrew Morton
Quoted 5 lines

- I have a synaptics touchpad, which is detected correctly, but only works if I set psmouse_noext=1. Under vanilla 2.6.0 it still works this way, but with 2.6.0-mm1 it works only on the console, but not under XFree86. Strange, as gpm interprets the input and pipes thru gpmdata to XFree86 4.3.0. Any idea what broke this configuration?

Peter or Dmitry may be able to tell us.

On the other hand, the synaptics touchpad on my laptop works under 2.6.0-mm1 without the need to use the above parameter. I don't get the jitter I reported for vanilla 2.6.0 synaptics support, but I do get an occasional small mouse jump.

Other than that, 2.6.0-mm1 appears to be working well on my Presario 12XL325 laptop.

author
#26 lore raw
In reply to GCS
Quoted 4 lines · GCS

[...] but still some lock or sth
is not unlocked, as the CPU is used more and more about five secs by one or two percent. Sooner or later it's crashed as well, but I could restart the machine before that happened.

Update: I could trigger this bug in 2.6.0-mm1 as well with the Linux
port of Head over Heels (classic game from C64). The CPU was getting more and more used, so the game slowed down. I could quit then from the game and XFree86. I did an emergency sync, and it succeded. Issued halt, but it stopped at init sending term to all processes, so I tried a hard power off. I got an error, something about slab, maybe at line 168. It was scrolled out too fast by the stack-trace, and at the end:
ACPI-0094: *** Error: Could not acquire interpreter mutex Crashed there. :-(

GCS

#4 lore raw
In reply to GCS
Quoted 12 lines · GCS
Quoted 1 line · GCS

input-02-add-psmouse_proto.patch (?)

Just found out psmouse_noext is deprecated. I have specified
psmouse_proto then, but imps and exps (and bare too, but I have not tested it, as reading the code it seems psmouse_noext falls back to bare) are the same. On the console touchpad is working, under XFree86 4.3.0 is not. To be more specific, the buttons do work, but I can not move the pointer at all. Well, first I thought the middle two buttons are for scrolling, as they are placed (and IIRC, they do scroll under m$ win), but the top button is like the left button and the bottom button is for paste, ie middle button on three buttons mices.

May we see your dmegs, XF86Config and the parameters you are passing to GPM please? Btw, what version of GPM are you using?

As far as reverting patches I would start with
input-08-synaptics-protocol-discovery.patch

Dmitry

author
#5 lore raw
Quoted 2 lines · Dmitry Torokhov

May we see your dmegs, XF86Config and the parameters you are passing to GPM please?

Sure, sorry for not doing it earlier:
-- dmesg --
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12 Synaptics Touchpad, model: 1
Firmware: 5.6
180 degree mounted touchpad
Sensor: 18
new absolute packet format
Touchpad has extended capability bits
-> four buttons
-> multifinger detection
-> palm detection
input: SynPS/2 Synaptics TouchPad on isa0060/serio4
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0 -- dmesg --

-- XF86Config-4 --
Section "Module"

        Load    "GLcore"
        Load    "bitmap"
        Load    "dbe"
        Load    "ddc"
        Load    "dri"
        Load    "extmod"
        Load    "glx"
        Load    "int10"
        Load    "record"
        Load    "speedo"
        Load    "type1"
        Load    "vbe"
        Load    "xtt"
        Load    "synaptics"

EndSection

Section "InputDevice"

        Driver        "synaptics"
        Identifier    "Configured Mouse"
        Option        "Device"        "/dev/gpmdata"
        Option        "Protocol"      "auto-dev"
        Option        "LeftEdge"      "1900"
        Option        "RightEdge"     "5400"
        Option        "TopEdge"       "1900"
        Option        "BottomEdge"    "4000"
        Option        "FingerLow"     "25"
        Option        "FingerHigh"    "30"
        Option        "MaxTapTime"    "180"
        Option        "MaxTapMove"    "220"
        Option        "VertScrollDelta" "100"
        Option        "MinSpeed"      "0.02"
        Option        "MaxSpeed"      "0.18"
        Option        "AccelFactor" "0.0010"
        Option        "SHMConfig"     "on"

# Option "Repeater" "/dev/ps2mouse"
EndSection
-- XF86Config-4 --

The Synaptics driver used is 0.12.2, compiled for myself, evdev is in module, but ofcourse it's loaded before XFree86 starts. (I have stripped down the files a bit, if you would like to see the whole files or other parts, please ask - I thought it would be easier to see the relevant lines only). gpm is configured by /etc/gpm.conf , but it should be:
gpm -m /dev/psaux -t ps2 -R raw
Also, the XFree86 Synaptics driver prints this while starting and switching between console and XFree86:
Synaptics DeviceInit called
SynapticsCtrl called.
Synaptics DeviceOn called
Synaptics DeviceOff called
[the last two repeated more times]

Quoted 1 line

Btw, what version of GPM are you using?

I am running Debian Sid, thus I also thought gpm is the newest; as I
do understand I should use 1.20.1, which is the latest AFAIK. Thus I was shocked a bit on what 'dpkg -l gpm' gives:
ii gpm 1.19.6-12.1 General Purpose Mouse Interface
More than a year old! Already filed an important bug on this. Sorry, it seems to be the problem, or at least produces strange behavior:
I plugged in an USB mouse, which works while the touchpad still not under XFree86 (both works at the same time under console - even if I did not specified any additional config for gpm). The config for XFree86:
-- XF86Config-4 --
Section "InputDevice"

        Identifier      "USB Mouse"
        Driver          "mouse"
        Option          "CorePointer"
        Option          "Device"                "/dev/input/mice"
        Option          "Protocol"              "imps/2"
        Option          "Emulate3Buttons"       "true"
        Option          "ZAxisMapping"          "4 5"

EndSection
-- XF86Config-4 --

Made it the only one pointer input. Now, if I kill gpm with 'gpm -k', then the touchpad begins to work! Sometimes if I release it, then the pointer jumps a bit from where I pointed it, but that's all. I'm not good in mice stuff, so I can't explain this. Anyway, I will try to compile a newer gpm, change it's device, so play a bit; maybe I can come up with something.

Quoted 2 lines

As far as reverting patches I would start with
input-08-synaptics-protocol-discovery.patch

It did not help. :-(

Thanks, and Merry Christmas!
GCS

#7 lore raw
In reply to Andrew Morton
Quoted 1 line · Andrew Morton

GCS <[email protected]> wrote:

[..SKIP..]

Quoted 8 lines
Quoted 6 lines

- I have a synaptics touchpad, which is detected correctly, but only works if I set psmouse_noext=1. Under vanilla 2.6.0 it still works
this way, but with 2.6.0-mm1 it works only on the console, but not under XFree86. Strange, as gpm interprets the input and pipes thru gpmdata to XFree86 4.3.0. Any idea what broke this configuration?

Peter or Dmitry may be able to tell us.

Whew.. that wasn't easy to spot... When doing PS/2 emulation for touchpads that use absolute events, when processing BTN_TOUCH event mousedev would stop on the very first client. So in your normal case only GPM would see the Synaptics but once you killed GPM XFree would be the first in line and magically start working.

My guess you didn't see that in stock 2.6.0 because you were compiling without Synaptics support.

I am sending 2 patches - one to remove mouse jitter with Synaptics when it is used through mousedev (PS/2 emulation) - mousedev will use 3 point history and average when calculating deltas, the other one is the fix for the problem you are experiencing. They should apply to 2.6.0-mm1 and to stock 2.6.0 with minimal jitter.

Dmitry

#8 lore raw

Re: 2.6.0-mm1 - Patch 1/2 - mousedev-remove-jitter

===================================================================

[email protected], 2003-12-23 02:24:12-05:00, [email protected]
Input: when calculating deltas for touchpads that generate
absolute events use average over the last 3 packets to remove jitter

 mouse/synaptics.c |   11 ++++---
 mousedev.c        |   84 +++++++++++++++++++++++++++++++-----------------------
 2 files changed, 56 insertions(+), 39 deletions(-)

===================================================================

drivers/input/mouse/synaptics.c +7 -4
diff -Nru a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
@@ -553,15 +553,18 @@
 		finger_width = 0;
 	}
 
-	/* Post events */
+	/* Post events
+	 * BTN_TOUCH has to be first as mousedev relies on it when doing
+	 * absolute -> relative conversion
+	 */
+	if (hw.z > 30) input_report_key(dev, BTN_TOUCH, 1);
+	if (hw.z < 25) input_report_key(dev, BTN_TOUCH, 0);
+
 	if (hw.z > 0) {
 		input_report_abs(dev, ABS_X, hw.x);
 		input_report_abs(dev, ABS_Y, YMAX_NOMINAL + YMIN_NOMINAL - hw.y);
 	}
 	input_report_abs(dev, ABS_PRESSURE, hw.z);
-
-	if (hw.z > 30) input_report_key(dev, BTN_TOUCH, 1);
-	if (hw.z < 25) input_report_key(dev, BTN_TOUCH, 0);
 
 	input_report_abs(dev, ABS_TOOL_WIDTH, finger_width);
 	input_report_key(dev, BTN_TOOL_FINGER, num_fingers == 1);
drivers/input/mousedev.c +49 -35

123 lines not on this page · raw message

#9 lore raw

Re: 2.6.0-mm1 - Patch 2/2 - mousedev-dont-stop

===================================================================

[email protected], 2003-12-25 03:56:28-05:00, [email protected]
Input: correctly perform PS/2 (mousedev) emulation for touchpads
generating absolute events (do not stop with the first client)

 mousedev.c |   16 +++++++++-------
 1 files changed, 9 insertions(+), 7 deletions(-)

===================================================================

drivers/input/mousedev.c +9 -7
diff -Nru a/drivers/input/mousedev.c b/drivers/input/mousedev.c
@@ -148,14 +148,16 @@
 					break;
 
 				case EV_KEY:
+					if (code == BTN_TOUCH && test_bit(BTN_TOOL_FINGER, handle->dev->keybit)) {
+						/* Handle touchpad data */
+						list->touch = value;
+						if (!list->touch)
+							list->pkt_count = 0;
+						break;
+					}
+
 					switch (code) {
-						case BTN_TOUCH: /* Handle touchpad data */
-							if (test_bit(BTN_TOOL_FINGER, handle->dev->keybit)) {
-								list->touch = value;
-								if (!list->touch)
-									list->pkt_count = 0;
-								return;
-							}
+						case BTN_TOUCH:
 						case BTN_0:
 						case BTN_FORWARD:
 						case BTN_LEFT:   index = 0; break;
author
#25 lore raw
In reply to Dmitry Torokhov
Quoted 5 lines · Dmitry Torokhov

I am sending 2 patches - one to remove mouse jitter with Synaptics when it is used through mousedev (PS/2 emulation) - mousedev will use 3 point history and average when calculating deltas, the other one is the fix for the problem you are experiencing. They should apply to 2.6.0-mm1 and to stock 2.6.0 with minimal jitter.

I have applied both to 2.6.0-mm1. They are just working, no jumping
mouse pointer when I release the touchpad, and both touchpad+usb mouse working on console and under XFree86 as well. OK, I could not really understand how they are working, as for me it seems gpm interprets /dev/psaux only, and get both pointing device right, still XFree86 which reads data replicated by gpm via gpmdata can't handle the USB mouse directly. I had to use a separate config, which reads /dev/input/mice as well. I think it's because XFree86's synaptics driver skip events from the USB mouse. Anyway, thanks for your help and work!

Merry Christmas!
GCS

Signature · 3 lines
BorsodChem Joint-Stock Company				Linux Support Center
Software engineer					Developer
+36-48-511211/12-99                                     +36-20-4441745
#10 lore raw

Synaptics problems in -mm1

In reply to Dmitry Torokhov

Hi,

it seems one of the synaptics-related patches in 2.6.0-mm1 kills off the pointer stick on my T40p. 2.6.0 vanilla works just fine in that department. Thought you might want to know.

Reverting

input-08-synaptics-protocol-discovery.patch input-07-remove-synaptics-config-option.patch synaptics-powerpro-fix.patch

did not seem to help. I failed to figure out a way to easily revert

serio-06-synaptics-use-reconnect.patch
serio-04-synaptics-cleanup.patch

so that I didn't try.

Signature · 1 line
Tomas Szepe <[email protected]>
author
#11 lore raw

Re: Synaptics problems in -mm1

Quoted 3 lines · Tomas Szepe

it seems one of the synaptics-related patches in 2.6.0-mm1 kills off the pointer stick on my T40p. 2.6.0 vanilla works just fine in that department. Thought you might want to know.

I had the same problems, but Dmitry provided two additional patches,
which made my one working. Have you tried them? You can find them in the thread.

Cheers,
GCS
Ps:Somehow I know you, just don't know where - are you Hungarian?

#12 lore raw

Re: Synaptics problems in -mm1

Quoted 9 lines · On Dec-27 2003, Sat, 13:24 +0100 GCS <[email protected]> wrote:
Quoted 3 lines · Tomas Szepe

it seems one of the synaptics-related patches in 2.6.0-mm1 kills off the pointer stick on my T40p. 2.6.0 vanilla works just fine in that department. Thought you might want to know.

I had the same problems, but Dmitry provided two additional patches, which made my one working. Have you tried them? You can find them in the thread.

Unfortunately, the two patches from this thread don't solve the mm1 problem I'm seeing, the stick keeps on resting. :)

Quoted 1 line

Ps:Somehow I know you, just don't know where - are you Hungarian?

Not really, it's just the name.

Signature · 1 line
Tomas Szepe <[email protected]>
#13 lore raw

Re: Synaptics problems in -mm1

In reply to Tomas Szepe
Quoted 12 lines · Tomas Szepe

Hi,

it seems one of the synaptics-related patches in 2.6.0-mm1 kills off the pointer stick on my T40p. 2.6.0 vanilla works just fine in that department. Thought you might want to know.

Reverting

input-08-synaptics-protocol-discovery.patch input-07-remove-synaptics-config-option.patch synaptics-powerpro-fix.patch

Quoted 6 lines

did not seem to help. I failed to figure out a way to easily revert

serio-06-synaptics-use-reconnect.patch
serio-04-synaptics-cleanup.patch

so that I didn't try.

I have a couple of questions (I am not familiar with IBM hardware so please bear with me...):
- Is it detected as Synaptics but does not work?
- Should it be detected as Synaptics?
- Does it work if you pass psmouse_noext=1 or psmouse_proto=bare? And what about psmouse_proto=imps and psmouse_proto=exps
- Does it work if you give 2.6.0-test10-mm1 a quick boot?
- dmesg, input section of you XFree and version and parameters that are passed to GPM.

Thank you,

Dmitry

#23 lore raw

Re: Synaptics problems in -mm1

In reply to Tomas Szepe

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It kills the mouse tap on an Asus M3700N laptop too...

Mind Booster Noori

- --
==================================================
Marcos Daniel Marado Torres AKA Mind Booster Noori
/"\ http://student.dei.uc.pt/~marado
\ / [email protected]
X ASCII Ribbon Campaign
/ \ against HTML e-mail and Micro$oft attachments
==================================================

Quoted 19 lines · Tomas Szepe

Hi,

it seems one of the synaptics-related patches in 2.6.0-mm1 kills off the pointer stick on my T40p. 2.6.0 vanilla works just fine in that department. Thought you might want to know.

Reverting

input-08-synaptics-protocol-discovery.patch input-07-remove-synaptics-config-option.patch synaptics-powerpro-fix.patch

did not seem to help. I failed to figure out a way to easily revert

serio-06-synaptics-use-reconnect.patch
serio-04-synaptics-cleanup.patch

so that I didn't try.

Quoted 8 lines

--
Tomas Szepe <[email protected]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQE/7cfQmNlq8m+oD34RAqUVAKDiNxT4XZgyDxsB2AzTqrUnmWfqkgCfZLah 18UNuecee424OP85exMvWW4=
=hki0
-----END PGP SIGNATURE-----

#14 lore raw

Re: Synaptics problems in -mm1

In reply to Dmitry Torokhov
Quoted 3 lines · On Dec-27 2003, Sat, 12:28 -0500 Dmitry Torokhov <[email protected]>…
Quoted 3 lines

it seems one of the synaptics-related patches in 2.6.0-mm1 kills off the pointer stick on my T40p. 2.6.0 vanilla works just fine in that department. Thought you might want to know.

...

Quoted 2 lines

I have a couple of questions (I am not familiar with IBM hardware so please bear with me...):

No problem.

There are two pointer controllers on the T40p: a stick and a pad. With 2.6.0, just compiling in synaptics support and running gpm as "gpm -t ps2 -m /dev/psaux" or XFree with

  Option          "Protocol"      "PS/2"
  Option          "Device"        "/dev/psaux"

gives perfect results, both controllers work, even with all the (3 + 2) buttons.

With 2.6.0-mm1 (the same .config of course), however, the stick does nothing.

Quoted 1 line

- Is it detected as Synaptics but does not work?

Yes.

Quoted 1 line

- Should it be detected as Synaptics?

I believe so.

Quoted 1 line

- Does it work if you pass psmouse_noext=1 or psmouse_proto=bare?

psmouse_noext=1 no change
psmouse_proto=bare no change

Quoted 1 line

And what about psmouse_proto=imps and psmouse_proto=exps

psmouse_proto=imps no change
psmouse_proto=exps no change

Quoted 1 line

- Does it work if you give 2.6.0-test10-mm1 a quick boot?

Hmmm, let's see.
[time passes]

-> No.

Linux version 2.6.0-test10-mm1 (kala@ns) (gcc version 3.3.2) #1 Sat Dec 27 18:59:17 CET 2003
...
mice: PS/2 mouse device common for all mice
input: PC Speaker
synaptics reset failed
synaptics reset failed
synaptics reset failed
Synaptics Touchpad, model: 1
Firmware: 5.9
Sensor: 44
new absolute packet format
Touchpad has extended capability bits
-> multifinger detection
-> palm detection
-> pass-through port
input: SynPS/2 Synaptics TouchPad on isa0060/serio1
serio: Synaptics pass-through port at isa0060/serio1/input0

Quoted 2 lines

- dmesg, input section of you XFree and version and parameters that are passed to GPM.

Working kernel dmesg:

Linux version 2.6.0 (kala@ns) (gcc version 2.95.3 20010315 (release)) #1 Sat Dec 27 18:59:59 CET 2003
...
mice: PS/2 mouse device common for all mice
input: PC Speaker
Synaptics Touchpad, model: 1
Firmware: 5.9
Sensor: 44
new absolute packet format
Touchpad has extended capability bits
-> multifinger detection
-> palm detection
-> pass-through port
input: SynPS/2 Synaptics TouchPad on isa0060/serio1
serio: Synaptics pass-through port at isa0060/serio1/input0
input: PS/2 Generic Mouse on synaptics-pt/serio0

Broken kernel dmesg:

Linux version 2.6.0-mm1 (kala@ns) (gcc version 3.3.2) #1 Sat Dec 27 14:12:13 CET 2003
...
mice: PS/2 mouse device common for all mice
input: PC Speaker
serio: i8042 AUX port at 0x60,0x64 irq 12
synaptics reset failed
synaptics reset failed
synaptics reset failed
Synaptics Touchpad, model: 1
Firmware: 5.9
Sensor: 44
new absolute packet format
Touchpad has extended capability bits
-> multifinger detection
-> palm detection
-> pass-through port
input: SynPS/2 Synaptics TouchPad on isa0060/serio1
serio: Synaptics pass-through port at isa0060/serio1/input0
...
psmouse.c: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 5 bytes away.

gpm is 1.19.6.
XFree is 4.3.0.
gpm parameters & XFree input config - see above.

Signature · 1 line
Tomas Szepe <[email protected]>
#15 lore raw

Re: Synaptics problems in -mm1

Quoted 5 lines · Tomas Szepe

mice: PS/2 mouse device common for all mice
input: PC Speaker
synaptics reset failed
synaptics reset failed
synaptics reset failed

Ok, are you running with cpufreq? I think it ACPI PM timer if you have it activated - I am having problems with it myself but didn't have time to look closer. Could you try booting with clock=tsc or clock=pit and see if it fixes the touchpad.

Dmitry

#16 lore raw

Re: Synaptics problems in -mm1

Quoted 7 lines · On Dec-27 2003, Sat, 13:23 -0500 Dmitry Torokhov <[email protected]>…
Quoted 5 lines

mice: PS/2 mouse device common for all mice
input: PC Speaker
synaptics reset failed
synaptics reset failed
synaptics reset failed

Ok, are you running with cpufreq?

Yes, but
1) I've been on AC all the time.
2) 2.6.0 works.

Quoted 3 lines

I think it ACPI PM timer if you have it activated - I am having problems with it myself but didn't have time to look closer. Could you try booting with clock=tsc or clock=pit and see if it fixes the touchpad.

clock=tsc appears to fix the problem.
clock=pit no change.

Signature · 1 line
Tomas Szepe <[email protected]>
#17 lore raw

Re: Synaptics problems in -mm1

Quoted 9 lines · Tomas Szepe

On Dec-27 2003, Sat, 13:23 -0500

Quoted 6 lines · Dmitry Torokhov
Quoted 5 lines

mice: PS/2 mouse device common for all mice
input: PC Speaker
synaptics reset failed
synaptics reset failed
synaptics reset failed

Quoted 6 lines
Quoted 1 line

Ok, are you running with cpufreq?

Yes, but
1) I've been on AC all the time.
2) 2.6.0 works.

Well, I have a daemon that monitors load and dynamically switches between high and low frequency...

Quoted 7 lines
Quoted 4 lines

I think it ACPI PM timer if you have it activated - I am having problems with it myself but didn't have time to look closer. Could you try booting with clock=tsc or clock=pit and see if it fixes the touchpad.

clock=tsc appears to fix the problem.
clock=pit no change.

Ok, good. So it is the timer funkiness. I would suggest not using ACPI PM timer for now then. And yes, timer_pit does not have cpufreq hooks either so it probably not the best timesource with cpufreq either, so stick with TSC.

Dmitry

#18 lore raw

Re: Synaptics problems in -mm1

Quoted 9 lines
Quoted 9 lines
Quoted 7 lines · Dmitry Torokhov
Quoted 5 lines

mice: PS/2 mouse device common for all mice
input: PC Speaker
synaptics reset failed
synaptics reset failed
synaptics reset failed

Ok, are you running with cpufreq?

Quoted 7 lines
Quoted 4 lines

Yes, but
1) I've been on AC all the time.
2) 2.6.0 works.

Well, I have a daemon that monitors load and dynamically switches between high and low frequency...

Sure, I've got one, too, but configured it to always go full throttle when on AC.

Quoted 5 lines
Quoted 5 lines
Quoted 4 lines

I think it ACPI PM timer if you have it activated - I am having problems with it myself but didn't have time to look closer. Could you try booting with clock=tsc or clock=pit and see if it fixes the touchpad.

Quoted 7 lines
Quoted 2 lines

clock=tsc appears to fix the problem.
clock=pit no change.

Ok, good. So it is the timer funkiness. I would suggest not using ACPI PM timer for now then. And yes, timer_pit does not have cpufreq hooks either so it probably not the best timesource with cpufreq either, so stick with TSC.

Stupid me, I absolutely forgot that I had enabled CONFIG_X86_PM_TIMER (nonexistent in 2.6.0 stock) which indeed seems to be the culprit. Please accept my apologies. -mm1 with that config option unset won't lose the stick, either.

Thanks!

Signature · 1 line
Tomas Szepe <[email protected]>
#24 lore raw

Re: Synaptics problems in -mm1

In reply to Marcos D. Marado Torres
Quoted 1 line · Marcos D. Marado Torres

It kills the mouse tap on an Asus M3700N laptop too...

Mousedev PS/2 emulation for touchpads in absolute mode does not support taps. You will either have to use Peter Osterlund's XFree86 driver at:
http://w1.894.telia.com/~u89404340/touchpad/index.html
and an updated version of GPM at http://www.geocities.com/dt_or/gpm
or disable native Synaptics support using psmouse_proto option (bare, imps or exps; any of them should do the trick).

Dmitry

#19 lore raw

Re: Synaptics problems in -mm1

In reply to Tomas Szepe
Quoted 6 lines · Tomas Szepe
Quoted 5 lines
Quoted 1 line

Dmitry Torokhov <[email protected]> wrote:

Ok, good. So it is the timer funkiness. I would suggest not using ACPI PM timer for now then. And yes, timer_pit does not have cpufreq hooks either so it probably not the best timesource with cpufreq either, so stick with TSC.

Quoted 6 lines

Stupid me, I absolutely forgot that I had enabled CONFIG_X86_PM_TIMER (nonexistent in 2.6.0 stock) which indeed seems to be the culprit. Please accept my apologies. -mm1 with that config option unset won't lose the stick, either.

Thanks!

Great! Thank you for letting me know.

Dmitry

#20 lore raw

Re: Synaptics problems in -mm1

In reply to Tomas Szepe
Quoted 7 lines · Tomas Szepe
Quoted 4 lines

I think it ACPI PM timer if you have it activated - I am having problems with it myself but didn't have time to look closer. Could you try booting with clock=tsc or clock=pit and see if it fixes the touchpad.

clock=tsc appears to fix the problem.
clock=pit no change.

So we've established that it is an interaction between the input code, the ACPI PM time code and cpufreq, yes? That's a bit of a witches brew.

Does anyone know what aspect of the ACPI PM timer behaviour could cause this?

#21 lore raw

Re: Synaptics problems in -mm1

Quoted 9 lines · Andrew Morton
Quoted 7 lines · Tomas Szepe
Quoted 4 lines

I think it ACPI PM timer if you have it activated - I am having problems with it myself but didn't have time to look closer. Could you try booting with clock=tsc or clock=pit and see if it fixes the touchpad.

clock=tsc appears to fix the problem.
clock=pit no change.

Quoted 8 lines

So we've established that it is an interaction between the input code, the ACPI PM time code and cpufreq, yes? That's a bit of a witches brew.

Does anyone know what aspect of the ACPI PM timer behaviour could cause this?

From my limited experience ACPI PM timer just gets the time wrong.

At least psmouse times out much quicker than 4 seconds when resetting the touchpad which causes many problems.

Looking at the PM timer was on my TODO list ever since it was included in -mm... I tried installing cpufreq handler to do the same adjustments for loops_per_jiffy as in timer_pit but I was still getting pretty much the same result - time goes too quickly.

Dmitry

#22 lore raw

Re: Synaptics problems in -mm1

In reply to Andrew Morton
Quoted 11 lines · On Dec-27 2003, Sat, 16:00 -0800 Andrew Morton <[email protected]> wrote:
Quoted 7 lines · Tomas Szepe
Quoted 4 lines

I think it ACPI PM timer if you have it activated - I am having problems with it myself but didn't have time to look closer. Could you try booting with clock=tsc or clock=pit and see if it fixes the touchpad.

clock=tsc appears to fix the problem.
clock=pit no change.

So we've established that it is an interaction between the input code, the ACPI PM time code and cpufreq, yes? That's a bit of a witches brew.

Ok, I have verified this witch is not _that_ cunning. cpufreq actually seems to be innocent, I am able to reproduce the problem with CONFIG_CPU_FREQ unset.

Signature · 1 line
Tomas Szepe <[email protected]>