Framwork 16 i2c-hid touchpad suddenly "jerky"

[LilyIsTrans]

Hi y'all!

As of this morning, the touchpad for my Framework laptop 16 is "jerky", that is, as I move my finger on the touchpad, the mouse will move for a moment, then stop, then move for a moment again, and so on.
It was not doing this yesterday, and I hadn't updated anything or changed any settings before going to bed.
I have had one issue with the touchpad before, about half the time on boot the touchpad would simply not be picked up at all, which I fixed by rebuilding my kernel with i2c-hid and i2c-hid-acpi as modules, and then simply unloading and reloading those with modprobe whenever the touchpad isn't picked up, which has been working fine for the last few weeks.
I have tried rebooting a few times, which has not made any obvious difference.

My dmesg output currently ends with this:

[pietinger]

LilyIsTrans,

Welcome to Gentoo Forums !

As a first check I would boot with an UbuntuLiveCD and check if there is the same behaviour. If yes, your touchpad is broken.

If no, save the dmesg of the Ubuntu boot, the lsmod and lspci -nnk.

(TBH, if there was really no change in your Gentoo system, then it is very likely that your touchpad is defective.)
_________________
https://wiki.gentoo.org/wiki/User:Pietinger

[LilyIsTrans]

Thanks!

I just tried it, and unfortunately, you were right; the behaviour is identical on Ubuntu, so it's almost certainly a hardware problem.

Regardless, I thank you, both for the help, and the warm welcome

[sinatosk]

***Copy/Paste from another thread - https://forums.gentoo.org/viewtopic-p-8841358.html#8841358

Does your keyboard/touchpad sometimes show/work and sometimes not ?

I'm using an FW16 myself with Gentoo and sometimes after boot and tty showing, if I press some keys as soon as the tty shows, no chars show but then after about 0.5-2 seconds they do but sometimes they don't and I have to cold reboot

https://community.frame.work/t/touchpad-not-working-since-update-archlinux/50304

https://bugzilla.kernel.org/show_bug.cgi?id=218836

What Arch Linux did was not put the kernel modules related to the keyboard in the initramfs which basically increases the delay of the modules loading which in turn gives the device a bit more time to correctly initialize

https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/commit/e835a32f0d4e44e2897e52a4eb151f95f4e18329

and it looks like a new driver is in the works ( it's not in 6.11 yet )

https://lore.kernel.org/linux-input/cover.1715224143.git.zhoubinbin@loongson.cn/T/#t

[pietinger]