2

Installed Fedora 41 (Gnome) on an old Sony Vaio Tap 11. Almost everything works out of the box, more or less. Clicking/releasing the mouse buttons does not work. Tapping on the touchpad does not work either. It is a wireless keyboard/touchpad, connect via an integrated wireless usb adapter.

Using other mouse/keyboard devices connected via usb port works fine. But I'd like to use the the original keyboard/touchpad since it can be attached to the tablet with integrated magnets.

Before, the machine was running Windows 10 with no problems. Also, the button clicks are still recognized in the recovery/boot menu. Does not look like a Distro/OS problem. Tried Fedora KDE, MX Linux and Ubuntu. No success.

Similar problems, recent and old, have been mentioned here: https://forums.linuxmint.com/viewtopic.php?t=410547, https://askubuntu.com/questions/456006/sony-vaio-tap-11-touchpad-and-mouse-conflict, Touchpad buttons do not release after press (Debian Gnome and others), but no solution found so far ...

I installed gnome tweaks and input-remapper. That did not help.

The only way I could get any feedback from the mouse buttons is by using hid-recorder.

$ sudo hid-recorder --debugfs

Available devices:
/dev/hidraw0:   Cypress Semiconductor WUSB NL Dongle V1.89v
/dev/hidraw1:   STMicroelectronics ST_SENSOR_HUB
/dev/hidraw2:   Cypress Semiconductor WUSB NL Dongle V1.89v
/dev/hidraw3:   N-trig DuoSense
Select the device event number [0-3]: 0
D: 0
R: 143 05 01 09 02 a1 01 09 01 a1 00 85 01 95 05 75 01 05 09 19 01 29 05 15 01 25 05 81 02 95 01 75 03 81 01 75 08 95 03 05 01 09 30 09 31 09 38 15 81 25 7f 81 06 05 0c 0a 38 02 95 01 75 08 15 81 25 7f 81 06 c0 c0 06 00 ff 09 02 a1 01 85 04 15 00 26 ff 00 19 00 2a ff 00 75 10 95 01 81 00 c0 05 0c 09 01 a1 01 85 05 15 00 26 ff 03 19 00 2a ff 03 95 01 75 10 81 00 c0 06 02 ff 09 02 a1 01 85 06 09 02 15 00 26 ff 00 95 07 75 08 b1 02 c0
N: Cypress Semiconductor WUSB NL Dongle V1.89v
P: usb-0000:00:14.0-8.1/input1
I: 3 054c 0872
reading debug interface /sys/kernel/debug/hid/0003:054C:0872.0004/events instead of /dev/hidraw0
D: 0
E: 0.000000 6 01 01 00 00 00 00 # mouse btn left down
E: 1.718003 6 01 00 00 00 00 00 # mouse btn left up
E: 2.419912 6 01 02 00 00 00 00 # mouse button right down
E: 3.548968 6 01 00 00 00 00 00 # mouse button right up

Monitoring hidraw0 also recognizes mouse/touchpad movements.

evtest does recognize keyboard input (event4) and mouse/touchpad movement (event6) but no mouse button clicks. (I tried all devices.)

$ sudo evtest

No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:  Power Button
/dev/input/event1:  Lid Switch
/dev/input/event10: N-trig DuoSense
/dev/input/event11: N-trig DuoSense Mouse
/dev/input/event12: Sony Vaio Keys
/dev/input/event13: Sony Vaio Jogdial
/dev/input/event14: PC Speaker
/dev/input/event15: HDA Intel HDMI HDMI/DP,pcm=3
/dev/input/event16: HDA Intel HDMI HDMI/DP,pcm=7
/dev/input/event17: HDA Intel HDMI HDMI/DP,pcm=8
/dev/input/event18: HDA Intel PCH Mic
/dev/input/event19: HDA Intel PCH Headphone
/dev/input/event2:  Power Button
/dev/input/event3:  AT Translated Set 2 keyboard
/dev/input/event4:  Cypress Semiconductor WUSB NL Dongle V1.89v
/dev/input/event5:  Video Bus
/dev/input/event6:  Cypress Semiconductor WUSB NL Dongle V1.89v Mouse
/dev/input/event7:  Cypress Semiconductor WUSB NL Dongle V1.89v Consumer Control
/dev/input/event8:  N-trig DuoSense UNKNOWN
/dev/input/event9:  N-trig DuoSense Stylus
Select the device event number [0-19]: 6
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x54c product 0x872 version 0x111
Input device name: "Cypress Semiconductor WUSB NL Dongle V1.89v Mouse"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 272 (BTN_LEFT)
    Event code 273 (BTN_RIGHT)
    Event code 274 (BTN_MIDDLE)
    Event code 275 (BTN_SIDE)
    Event code 276 (BTN_EXTRA)
  Event type 2 (EV_REL)
    Event code 0 (REL_X)
    Event code 1 (REL_Y)
    Event code 6 (REL_HWHEEL)
    Event code 8 (REL_WHEEL)
    Event code 11 (REL_WHEEL_HI_RES)
    Event code 12 (REL_HWHEEL_HI_RES)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1743606884.077910, type 2 (EV_REL), code 1 (REL_Y), value -1
Event: time 1743606884.077910, -------------- SYN_REPORT ------------
Event: time 1743606884.096868, type 2 (EV_REL), code 1 (REL_Y), value -1
Event: time 1743606884.096868, -------------- SYN_REPORT ------------
Event: time 1743606884.119840, type 2 (EV_REL), code 0 (REL_X), value -1
Event: time 1743606884.119840, -------------- SYN_REPORT ------------
Event: time 1743606884.162847, type 2 (EV_REL), code 0 (REL_X), value -2
Event: time 1743606884.162847, type 2 (EV_REL), code 1 (REL_Y), value -1
Event: time 1743606884.162847, -------------- SYN_REPORT ------------

I read a lot in different forums but since I am relatively new to linux I could not find out how to tackle this problem. Am I missing a driver? Do I need to write udev rules or hwdb configs? Please advise!

Additional Infos:

https://gist.github.com/chilluminati/6c2aaf11a9032b3aa2a09632548c82c2#file-sony_vaio_tap_11_libinput_list_devices-txt

https://gist.github.com/chilluminati/23d1a5405f7d1303e4bf50c3116c058d#file-sony_vaio_tap_11_lsusb_v-txt

https://gist.github.com/chilluminati/00ba1eeb2a9786b2d224e90f683fe82f#file-sony_vaio_tap_11_udevadm_info_hidraw0-txt

https://gist.github.com/chilluminati/43652c98350f80cf5c4acd5fdff2aa2d#file-sony_vaio_tap_11_dmesg_grep_hidraw-txt

3
  • A well documented problem, you have really tried to solve this on your own, Good Show! ... I'm sure I can't really help here, but recommend you add the output from sudo lsusb and any relevant output you see from sudo lsusb -v. Also, if you have another system to experiment with, install same version of Fedora there and see what if you see any hints when you run the same set of diagnostics there. That is to say, see what info you can glean from a working system. Commented Apr 3 at 16:54
  • @shellter Thanks. I put quite some effort into this task. Everything I could gather from libinput, lsusb, udevadm and dmesg I added as gist links. (I tried to include them all as code but that what have been too many characters.) I actually have Fedora 41 (Gnome) running on another machine (the one I'm using right now). Maybe I can make sense of the diagnostics. But I guess I'm a bit lost without any pointers. :) Commented Apr 3 at 20:29
  • Divide and conquer. Compare one set of outputs at a time. Look for stuff that is different and doesn't make sense. (I would start with lsusb output, but there might be better places to start). Commented Apr 4 at 2:43

0

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.