vertex
2006-05-05, 01:13 PM CDT
I have two systems with basically identical hardware. The only real difference is with the lcd. The problem here is with the touchpad.
System one works fine, no issues. dmesg says this about the Synaptics device:
...
Synaptics Touchpad, model: 1, fw: 5.9, id: 0x926eb1, caps: 0x804719/0x0
input: SynPS/2 Synaptics TouchPad as /class/input/input1
...
System two does not work fine. The basic mouse functionality is there, but it appears that some of the errors I see in dmesg are preventing me from resuming from a suspend to disk.
dmesg after normal boot:
Synaptics Touchpad, model: 1, fw: 5.9, id: 0x926eb1, caps: 0x804719/0x0
input: SynPS/2 Synaptics TouchPad as /class/input/input1
psmouse.c: Failed to reset mouse on isa0060/serio3
...
psmouse.c: Failed to enable mouse on isa0060/serio3
dmesg after trying to resume:
Attempting manual resume
swsusp: Resume From Partition 3:5
PM: Checking swsusp image.
swsusp: Signature found, resuming
PM: Preparing processes for restore.
Stopping tasks: ======<6>Synaptics Touchpad, model: 1, fw: 5.9, id: 0x926eb1, caps: 0x804719/0x0
input: SynPS/2 Synaptics TouchPad as /class/input/input1
psmouse.c: Failed to reset mouse on isa0060/serio3
stopping tasks failed (1 tasks remaining)
Restarting tasks...<6> Strange, kseriod not stopped
done
PM: Resume from disk failed.
...
input: PS/2 Generic Mouse as /class/input/input2
psmouse.c: Failed to enable mouse on isa0060/serio3
I understand that there is some timeout causing the failed resume. I found some information from this thread:
http://www.ussg.iu.edu/hypermail/linux/kernel/0511.2/0687.html
Seeing how both of these system have identical touchpads, I am at a loss to explain why one is working correctly and the other is not.
Any help on this would be appriciated.
System one works fine, no issues. dmesg says this about the Synaptics device:
...
Synaptics Touchpad, model: 1, fw: 5.9, id: 0x926eb1, caps: 0x804719/0x0
input: SynPS/2 Synaptics TouchPad as /class/input/input1
...
System two does not work fine. The basic mouse functionality is there, but it appears that some of the errors I see in dmesg are preventing me from resuming from a suspend to disk.
dmesg after normal boot:
Synaptics Touchpad, model: 1, fw: 5.9, id: 0x926eb1, caps: 0x804719/0x0
input: SynPS/2 Synaptics TouchPad as /class/input/input1
psmouse.c: Failed to reset mouse on isa0060/serio3
...
psmouse.c: Failed to enable mouse on isa0060/serio3
dmesg after trying to resume:
Attempting manual resume
swsusp: Resume From Partition 3:5
PM: Checking swsusp image.
swsusp: Signature found, resuming
PM: Preparing processes for restore.
Stopping tasks: ======<6>Synaptics Touchpad, model: 1, fw: 5.9, id: 0x926eb1, caps: 0x804719/0x0
input: SynPS/2 Synaptics TouchPad as /class/input/input1
psmouse.c: Failed to reset mouse on isa0060/serio3
stopping tasks failed (1 tasks remaining)
Restarting tasks...<6> Strange, kseriod not stopped
done
PM: Resume from disk failed.
...
input: PS/2 Generic Mouse as /class/input/input2
psmouse.c: Failed to enable mouse on isa0060/serio3
I understand that there is some timeout causing the failed resume. I found some information from this thread:
http://www.ussg.iu.edu/hypermail/linux/kernel/0511.2/0687.html
Seeing how both of these system have identical touchpads, I am at a loss to explain why one is working correctly and the other is not.
Any help on this would be appriciated.