Bug 232040 - wmt driver fails to attach to Synaptics Touchscreen
Summary: wmt driver fails to attach to Synaptics Touchscreen
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: CURRENT
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-usb mailing list
Depends on:
Reported: 2018-10-07 18:11 UTC by Sergei Akhmatdinov
Modified: 2019-10-09 18:36 UTC (History)
3 users (show)

See Also:

usbconfig -d ugen0.2 dump_all_desc (1.92 KB, text/plain)
2019-04-23 05:51 UTC, Kubilay Kocak
no flags Details
Output of usbhid-dump (12.28 KB, text/plain)
2019-10-09 18:36 UTC, Sergei Akhmatdinov
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sergei Akhmatdinov 2018-10-07 18:11:24 UTC
I have a Lenovo YOGA 12 Thinkpad with a Synaptics Touchscreen. 

It gets detected as 

ugen0.2: <SYNAPTICS Synaptics Touch Digitizer V04> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (400mA)

by usbconfig and I get a corresponding /dev/uhid0 device.

usbconfig -d ugen0.2 dump_all_desc:

I can get the touchscreen working through webcamd, but the touch screen has issues detecting ButtonRelease when configured that way.

Trying to hook /dev/uhid0 up as a mouse through xorg.conf gives me a segfault when launching X.

I also have a usb_quirk setup to make the touchscreen get ignored by UMS, since moused likes to attach itself to it every time in the console. It does not seem to function as ums0, however.

Synaptics driver doesn't work with it either.
Comment 1 Sergei Akhmatdinov 2018-10-07 18:16:25 UTC
Forgot to mention that I am tracking head, updated world and kernel today.
Comment 2 Vladimir Kondratyev freebsd_committer 2018-10-09 20:52:34 UTC
Hi Sergei,

Could you attach HID descriptor of your touchscreen.

usbhid-dump (sysutils/usbhid-dump) can help you obtain it.
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2019-04-23 05:51:11 UTC
Created attachment 203907 [details]
usbconfig -d ugen0.2 dump_all_desc

Attach output of `usbconfig -d ugen0.2 dump_all_desc` mentioned in comment 0 just in case pastebin goes away.

@Vladimir Is this sufficient information or is usbhid-dump output still needed?
Comment 4 Vladimir Kondratyev freebsd_committer 2019-04-23 12:05:02 UTC
(In reply to Kubilay Kocak from comment #3)
> @Vladimir Is this sufficient information or is usbhid-dump output still needed?

usbhid-dump output is still needed. Unlike mices and keyboards, touchscreens do not have boot protocol records in USB interface descriptor so their detection is based on content of HID descriptor.
Comment 5 Sergei Akhmatdinov 2019-10-09 18:36:50 UTC
Created attachment 208210 [details]
Output of usbhid-dump

My apologies for not responding to this bug sooner.

Please find the output of usbhid-dump attached. The device is now detected as ugen0.3, I was not sure which descriptor corresponds to the device itself.