SOLVED: Custom kernel on my pretty new FW13 without mouse pointer

Hello!
I’m pretty happy with my laptop apart from one thing. I’m typically building my own kernel because i can. The latest ones i built started fine apart from the missing mouse. Are there non- intuitive kernel options that are needed to get a working mouse? I used the hid_multitouch driver combined with varying hid drivers, but to no avail - no mouse pointer to be seen. Affected OS is Debian 12 (stable) which runs rather fine with Debian kernels. The non-working kernel has version 6.14.0-rc2 but older versions show the same problem.
The FW13 has an AMD 7040 CPU.
Cheers & good night!

I’ll check what kernel module I use in Gentoo and report back.

I’m replying now so that I can more easily find this post later.

1 Like

https://wiki.gentoo.org/wiki/Framework_Laptop_13#Touchpad_not_working

You may refer to this guide for troubleshooting:

Verify the “HID over I2C transport layer ACPI” is available.
If “PIXA3854” cannot be found in the dmesg log, then the kernel is likely missing driver support.

1 Like

I think Kings is right. Here’s my dmesg output showing the “mouse” is being accessed over I2C.

[ +0.000164] input: PIXA3854:00 093A:0274 Mouse as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0002/input/input4
[ +0.000074] input: PIXA3854:00 093A:0274 Touchpad as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0002/input/input5
[ +0.000063] hid-generic 0018:093A:0274.0002: input,hidraw1: I2C HID v1.00 Mouse [PIXA3854:00 093A:0274] on i2c-PIXA3854:00

Thanks already, i’ll have that checked in a few minutes. It’s a bit embarrassing without pointing device!
Reboot ensuing…

This seems to be the culprit! The only relevant line in journalctl output is:
Apr 13 09:45:03 rapunzel kernel: i2c i2c-PIXA3854:00: deferred probe pending: (reason unknown)
After pulling my USB mouse out of a cardboard box, i even found a mouse pointer. I’ll stick to the guide that was posted. Thanks a ton!
tim

It seems i enabled all the necessary drivers, but compiled the wifi and graphics drivers into the kernel. Turning these two drivers into modules seemingly fixed the issue!
@Kings Thanks for fast and informative input, this went rather quick!

Must now check how the #fediverse instance i attend behaves like. The original debian kernel had some hickup loading the site. That particular site seems down right now.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.