I2C HID Trackpad not working on Lenovo Yoga S730 in SculptOS; F12 Leitzentrale also affected

Hardware
1

Hardware Details:

  • Lenovo Yoga S730-13IWL
  • Touchpad is an I2C HID multitouch device (VID:PID 04f3:30bc)
  • ACPI MSFT0001
  • No PS/2 or USB fallback
  • It works on Linux via i2c_hid + hid-multitouch

Additionally, F12 stops toggling the Leitzentrale after launching any GUI component from the depot. This does not occur on my ThinkPad X230. The Yoga uses a modern HID/ACPI keyboard with Lenovo “Ideapad extra buttons”, and it appears that after a GUI client starts, F12 is no longer delivered as a regular key event to Leitzentrale. Im guessing its a hardware-specific keyboard event routing issue rather than a general focus problem?

*Pic to show that I’m still having fun :slight_smile:

PXL_20260130_064806328_2
PXL_20260130_064806328_21920×1080 397 KB

Edit: change tag to Hardware

1 Like
2

Unfortunately, there is only incomplete support for i2c_hid-driven devices in Sculpt. We’ve enabled this for a few (e.g. tigerlake-based framework laptops) via the touchpad launcher. However, since I assume your Yoga S730 has a Skylake microarchitecture, the ported driver is not going to work on your device.

3

Thanks.

I did enable the touchpad launcher, but you’re right, it didn’t help.

So, am I dead in the water, or is there a possibility it’ll be supported down the line?

As for losing F12 functionality, any ideas there?

4

There is some quite low priority work going on. It, however, kind of depends also on the pre-boot platform discovery mentioned for 26.11 on the road map.

5

Not yet, have you double-checked that there is no Fn-key locking enabled?

6

What’s one more year :face_savoring_food:

I’m hoping this will get support eventually. The trackpad is much larger and will be easier to use than the one on my x230. Plus, the 1080p screen on my Yoga is much nicer to look at.

No, it only becomes disabled when I add any componant from the depot

7

Sorry to bump unnecessarily, but I wonder if there is anything I can do to assist by way of testing etc? Or will this be more useful once 26.11 has been cut?

8

As Stefan pointed out last week, the necessity for boot-time ACPI discovery increases. In principle, you could get all the required information from a running Linux system but we don’t have a guide for this. Even with all the information at hand, however, the issue remains that the current driver does not support your platform. Yet, it is probably merely a matter of adding a few compilation units and testing. If you are keen on getting your hands dirty with this, please feel free.