Opened 16 years ago
Closed 13 years ago
#3152 closed bug (fixed)
Mouse (trackpad) used to work fine - now unreliable.
Reported by: | alban | Owned by: | siarzhuk |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Mouse/PS2 | Version: | R1/Development |
Keywords: | Cc: | olive@… | |
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
The mouse (trackpad) is much less reliable in very recent Haiku releases. The mouse pointer sometimes hangs or freezes during or shortly after startup. mouse buttons are not responsive; there is a delay between clicking a button and the action taking place. This makes the user interface hard to use.
Syslog shows:-
KERN: ps2_hid: init_hardware KERN: ps2_hid: init_driver KERN: ps2: active multiplexing v1.1 enabled KERN: ps2_hid: publish_devices KERN: ps2_hid: uninit_driver KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/input/ps2_hid KERN: ps2: reset failed KERN: ps2: devfs_publish_device input/mouse/ps2/0, status = 0xffffffff KERN: ps2: reset failed KERN: ps2: devfs_publish_device input/mouse/ps2/1, status = 0xffffffff KERN: ps2: reset failed KERN: ps2: devfs_publish_device input/mouse/ps2/2, status = 0xffffffff KERN: ps2: devfs_publish_device input/touchpad/ps2/synaptics_3, status = 0x00000000 KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000 KERN: ps2: keyboard found KERN: ps2: probe_mouse Standard PS/2 mouse found KERN: ps2: devfs_publish_device input/mouse/ps2/standard_3, status = 0x00000000 KERN: ps2_hid: init_hardware KERN: ps2_hid: init_driver KERN: ps2: active multiplexing v1.1 enabled KERN: ps2_hid: publish_devices KERN: ps2_hid: uninit_driver KERN: loaded driver /boot/beos/system/add-ons/kernel/drivers/dev/input/ps2_hid KERN: ps2: reset failed KERN: ps2: devfs_publish_device input/mouse/ps2/0, status = 0xffffffff KERN: ps2: reset failed KERN: ps2: devfs_publish_device input/mouse/ps2/1, status = 0xffffffff KERN: ps2: reset failed KERN: ps2: devfs_publish_device input/mouse/ps2/2, status = 0xffffffff KERN: ps2: devfs_publish_device input/touchpad/ps2/synaptics_3, status = 0x00000000 KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000 KERN: ps2: keyboard found KERN: ps2: probe_mouse Standard PS/2 mouse found KERN: ps2: devfs_publish_device input/mouse/ps2/standard_3, status = 0x00000000
Attachments (2)
Change History (12)
comment:1 by , 16 years ago
Cc: | added |
---|
comment:2 by , 16 years ago
comment:3 by , 16 years ago
Component: | - General → Drivers/Mouse/PS2 |
---|---|
Description: | modified (diff) |
Owner: | changed from | to
comment:4 by , 16 years ago
Owner: | changed from | to
---|
I don't understand this. Why are we publishing a standard and a synaptics mouse at the same time and at the same index? Is this even supported? I only did the standard mouse part. Because stippi committed the patch with hrev28643 I'm reassigning it
KERN: ps2: devfs_publish_device input/touchpad/ps2/synaptics_3, status = 0x00000000
KERN: ps2: devfs_publish_device input/mouse/ps2/standard_3, status = 0x00000000
follow-up: 8 comment:6 by , 14 years ago
I have been having the same problem, but wasn't reporting since I was using USB mouse.
I have a HP NX8220 laptop with "Synaptics" touchpad. The mouse was working fine as "Standard Mouse" before touchpad features added. After touchpad features added the touchpad wasn't working.(Keyboard works fine). I'm getting the same syslog as above. But in order to be more helpful I'm adding a syslog with PS/2 command tracing enabled and a grep "ps2:" one.
comment:7 by , 14 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:8 by , 13 years ago
Replying to herdemir:
I have a HP NX8220 laptop with "Synaptics" touchpad. The mouse was working fine as "Standard Mouse" before touchpad features added. After touchpad features added the touchpad wasn't working.(Keyboard works fine). I'm getting the same syslog as above. But in order to be more helpful I'm adding a syslog with PS/2 command tracing enabled and a grep "ps2:" one.
Please try the latest nightly revisions. In hrev42329 I have fixed the issue with non-answering pass-through device as in your syslog.
Note that original bugs problem looks different - there are multiple reinitialization of ps2 module and the function of the mouse is periodically freeze - that is not a case of mentioned fix. So any syslog with activated PS2 _TRACE is welcomed.
comment:9 by , 13 years ago
Owner: | changed from | to
---|---|
Version: | R1/pre-alpha1 → R1/Development |
comment:10 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
This problem is introduced with hrev28643; also note #3138.