Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > muc.lists.freebsd.multimedia > #13601

[Bug 298871] Touchpad on Lenovo T14 AMD only recognized after second boot

From bugzilla-noreply@freebsd.org
Newsgroups muc.lists.freebsd.multimedia
Subject [Bug 298871] Touchpad on Lenovo T14 AMD only recognized after second boot
Date 2026-11-15 06:59 +0000
Organization Newsgate at muc.de e.V.
Message-ID <bug-298871-12827-3eyEdIWHYC@https.bugs.freebsd.org/bugzilla/> (permalink)
References <bug-298871-12827@https.bugs.freebsd.org/bugzilla/>

Show all headers | View raw


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=298871

--- Comment #16 from David Bidner <david@crap.solutions> ---
Today I hit this bug too! So it is not fixed on -CURRENT.

With debug.psm.loglevel=5 and a finger dragged over the pad, it streams only

  psmintr: 80 00 00 c0 00 00
  psmintr: 80 00 00 c1 00 00      (only while the clickpad is pressed)

i.e. Z=0, W=0, X=Y=0, so proc_synaptics() drops every frame
(f[0].p < min_pressure || f[0].x < 2).  In the working state the same pad sends
w=2 extended frames (90 ../a0 ..), parsed as e.g. [x=2139, y=3564], pressure
73,
width 4.

The pad attaches normally and a re-probe reads the full capability set, so it
is
not a missed discovery. READ_MODES returns mode byte 0xc5 in the broken state
as
well as in the working one.

devctl detach psm0; devctl attach psm0 (full re-probe, which already does
reset_aux_dev() -> 0xFF twice) does NOT help, and a warm reboot did not help
for
me. only a real power cycle did.

-- 
You are receiving this mail because:
You are the assignee for the bug.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de

Back to muc.lists.freebsd.multimedia | Previous | Next | Find similar | Unroll thread


Thread

[Bug 298871] Touchpad on Lenovo T14 AMD only recognized after second boot bugzilla-noreply@freebsd.org - 2026-11-15 06:59 +0000

csiph-web