Opened 2 years ago

Last modified 6 months ago

#18108 new bug

Touchpad (i2c-PIXA3854:00 093A:0274) only recognized as PS/2 mouse, not working after rebooting from other operating systems

Reported by: taos Owned by: PreetpalKaur
Priority: normal Milestone: Unscheduled
Component: Drivers/Input Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by taos)

With hrev56595 64bit, my touchpad only works (partially - only left click available) after a cold boot into Haiku - or after then rebooting from Haiku into Haiku again. Haiku is usually started via rEFInd (but starting directly from an anyboot image doesn't change the observed behaviour).

Switching (in UEFI BIOS) the touchpad PS/2 emulation from 'automatic' to 'on' or 'off' doesn't change this. I can't find the touchpad model mentioned in syslog (or via listdev or listusb - outputs are attached).

The touchpad works as multitouch device in Windows 11 (after driver installation), Linux, and OpenBSD. libinput list-devices under linux sees it as PIXA3854:00 093A:0274 Touchpad. dmesg | grep PIXA then results in:

dmesg | grep PIXA
[    6.511030] input: PIXA3854:00 093A:0274 Mouse as /devices/pci0000:00/0000:00:15.3/i2c_designware.2/i2c-16/i2c-PIXA3854:00/0018:093A:0274.0002/input/input9
[    6.511234] input: PIXA3854:00 093A:0274 Touchpad as /devices/pci0000:00/0000:00:15.3/i2c_designware.2/i2c-16/i2c-PIXA3854:00/0018:093A:0274.0002/input/input10
[    6.511470] hid-generic 0018:093A:0274.0002: input,hidraw1: I2C HID v1.00 Mouse [PIXA3854:00 093A:0274] on i2c-PIXA3854:00
[   11.051765] input: PIXA3854:00 093A:0274 Mouse as /devices/pci0000:00/0000:00:15.3/i2c_designware.2/i2c-16/i2c-PIXA3854:00/0018:093A:0274.0002/input/input27
[   11.086455] input: PIXA3854:00 093A:0274 Touchpad as /devices/pci0000:00/0000:00:15.3/i2c_designware.2/i2c-16/i2c-PIXA3854:00/0018:093A:0274.0002/input/input28
[   11.086801] hid-multitouch 0018:093A:0274.0002: input,hidraw0: I2C HID v1.00 Mouse [PIXA3854:00 093A:0274] on i2c-PIXA3854:00

Edit: It might be a PixArt PCT3854QR touchpad.

Attachments (3)

listdev_hrev56959.txt (3.9 KB ) - added by taos 2 years ago.
output of listdev
listimage_hrev56959.txt (60.9 KB ) - added by taos 2 years ago.
output of listimage
syslog_hrev56595.log (223.5 KB ) - added by taos 2 years ago.
syslog of hrev56595 (after cold boot)

Download all attachments as: .zip

Change History (9)

by taos, 2 years ago

Attachment: listdev_hrev56959.txt added

output of listdev

by taos, 2 years ago

Attachment: listimage_hrev56959.txt added

output of listimage

by taos, 2 years ago

Attachment: syslog_hrev56595.log added

syslog of hrev56595 (after cold boot)

comment:1 by korli, 2 years ago

Which laptop is it?

comment:2 by taos, 2 years ago

Framework Laptop (12th Gen Intel Core)

According to frame.work it might have a PixArt PCT3854QR touchpad.

Last edited 2 years ago by taos (previous) (diff)

comment:3 by taos, 2 years ago

Description: modified (diff)

comment:4 by taos, 6 months ago

With UEFI BIOS versions 3.06 (in beta state for ~ 1 year) and 3.08 (released as stable last month) PS/2 emulation of the laptop got fixed ('auto' now means on, 'disabled' means off, and 'on' isn't an option anymore) and the touchpad started to work in Haiku as one-button mouse - even after rebooting from another operating system. How well, however, depends on Haiku revision.

At first, you had to press really hard to get a click registered by Haiku, then after a while even tap-to-click started to work (great times!). After an another Haiku update, just touching the touchpad to move the cursor frequently produced unintended right(?) clicks which opened context menus in inconvenient places. Usually, these context menus could be dismissed with the ESC key, so using Haiku with only the touchpad was still okay.

After updating from hrev57719 to hrev57734, the touchpad now stopped working completely (no matter which option is chosen in UEFI BIOS). It is still shown as PS/2 mouse in Input (if PS2/emulation is set to 'auto'), but doesn't react to any touch, tap or hard press. It is necessary to plug in a USB mouse for everything that can't be done with the keyboard alone.

I don't have another laptop that uses PS/2 emulation, so I can't check if this is hardware-specific or not.

Last edited 6 months ago by taos (previous) (diff)

comment:5 by waddlesplash, 6 months ago

I guess you must mean hrev57719 and hrev57734? I don't see anything in that range which would affect this, save maybe the "power saving" change, but if you don't have "power saving" enabled in ProcessController, that shouldn't affect anything.

in reply to:  5 comment:6 by taos, 6 months ago

Replying to waddlesplash:

I guess you must mean hrev57719 and hrev57734?

Yep :-) Sorry.

I've updated to hrev57737 and the former behaviour of the touchpad after rebooting from Windows/OpenBSD/Linux to Haiku is restored (touching/moving the cursor frequently results in unintended right-clicks, and each tap-to-left-click also immediately produces a right-click). So, just an unfortunate race condition, timing issue, or similar?

Note: See TracTickets for help on using tickets.