I don't know what to tell you. Last night, my touchpad worked. Today after a dnf update -y it doesn't work. It's like it's not even there. Reproducible: Always Steps to Reproduce: Try to use touchpad Actual Results: It doesn't work Expected Results: It should work libinput-1.26.2-1.fc42.x86_64
Same here. Touchpad not working in sway.
Also touchpad is not visible where queried like this in terminal: swaymsg -i get_inputs | grep -i touchpad. When booted in to previous server instance, touchpad worked correctly. Most probably, this server update: 6.12.0-0.rc0.20240926git11a299a7933e.13.fc42.x86_64 has broken touchpad functionality.
Sorry. swaymsg -t get_inputs | grep -i touchpad
Same here. My touchpad is: 45: USB 00.0: 0000 Unclassified device [Created at usb.122] Unique ID: CiZ2.OSF0R9UKr39 Parent ID: uIhY.2DFUsyrieMD SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0 SysFS BusID: 3-3:1.0 Hardware Class: unknown Model: "Synaptics Unclassified device" Hotplug: USB Vendor: usb 0x06cb "Synaptics, Inc." Device: usb 0x00fc Serial ID: "43009016c083" Speed: 12 Mbps Module Alias: "usb:v06CBp00FCd0000dcFFdsc10dpFFicFFisc00ip00in00" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #48 (Hub)
Created attachment 2049554 [details] dmesg Here is the dmesg output on my system. The only mention of a touchpad is from the new PixArt driver...
Thanks for the logs. We have here a new driver trying to get control of your touchpad, and of course you probably don't have a PixArt touchpad to begin with. Could you also attach a working (v6.11.x) dmesg so I can blame the driver on the LKML?
Created attachment 2049572 [details] dmesg from 6.11, with working touchpad
FWIW, the faulty driver is scheduled to be removed from 6.12-rcx. However, the input maintainer would like to have some more debugging traces: https://lore.kernel.org/linux-input/Zvv1_bHoH94-e33b@google.com/T/#m7bb828fde72b62f24b767c86ebc48861eeae8bdf > I see. It is interesting that the first probe fails: > > [ 1.649119] psmouse serio1: pixart_ps2: init: Unable to query PixArt touchpad hardware. > > > but then it goes and detects it a bit later: > > [ 1.945075] input: PS/2 PixArt clickpad as /devices/platform/i8042/serio1/input/input5 > > It would be curious to get the logs of the failing case with > i8042.debug=1 Thow I would recomend not to type anything like your password on the keyboard when extracting that log, because it might get caught in the dmesg (or change it before your reboot to a dumb one, extract the dmesg, and then re-change it). We would appreciate if anybody could provide those logs. Thanks!
@btissoir I'm afraid it might for some devices have nothing to do with the pixart driver. I'm running on `6.12.0-0.rc1.20241001gite32cde8d2bd7.18.fc42.x86_64`, the latest git kernel, and disabled `CONFIG_MOUSE_PS2_PIXART`, from what I can understand from the code is that it shouldn't even detect the touchpad as PixArt at all because the drivers are now not included in the kernel. I did this by following: https://docs.fedoraproject.org/en-US/quick-docs/kernel-build-custom/#_building_a_kernel_from_the_fedora_dist_git And adding `# CONFIG_MOUSE_PS2_PIXART is not set` to the `kernel-local` file. After compiling the kernel I double checked if it was the case by checking `/boot/config-$(uname -r)`. This confirmed there was no CONFIG_MOUSE_PS2_PIXART config in the current kernel's config. I also checked my boot log (/var/log/boot.log) and the logs in the gnome logs app and no results for pixart at all. The device I'm using is the ASUS Zenbook S 14 UX5406 running Fedora Linux 41. In the stable 6.11 kernel the touchpad is working correctly, being detected as follows: ``` I: Bus=0018 Vendor=2808 Product=0218 Version=0100 N: Name="ASUF1208:00 2808:0218 Mouse" P: Phys=i2c-ASUF1208:00 S: Sysfs=/devices/pci0000:00/0000:00:19.1/i2c_designware.3/i2c-3/i2c-ASUF1208:00/0018:2808:0218.0003/input/input12 U: Uniq= H: Handlers=mouse1 event7 B: PROP=0 B: EV=17 B: KEY=30000 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0018 Vendor=2808 Product=0218 Version=0100 N: Name="ASUF1208:00 2808:0218 Touchpad" P: Phys=i2c-ASUF1208:00 S: Sysfs=/devices/pci0000:00/0000:00:19.1/i2c_designware.3/i2c-3/i2c-ASUF1208:00/0018:2808:0218.0003/input/input13 U: Uniq= H: Handlers=mouse2 event8 B: PROP=5 B: EV=1b B: KEY=e520 10000 0 0 0 0 B: ABS=2e0800000000003 B: MSC=20 Device: ASUF1208:00 2808:0218 Mouse Kernel: /dev/input/event7 Group: 4 Seat: seat0, default Capabilities: pointer Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock: n/a Left-handed: disabled Nat.scrolling: disabled Middle emulation: n/a Calibration: n/a Scroll methods: *button Click methods: none Disable-w-typing: n/a Disable-w-trackpointing: n/a Accel profiles: flat *adaptive custom Rotation: n/a Device: ASUF1208:00 2808:0218 Touchpad Kernel: /dev/input/event8 Group: 4 Seat: seat0, default Size: 125x76mm Capabilities: pointer gesture Tap-to-click: disabled Tap-and-drag: enabled Tap drag lock: disabled Left-handed: disabled Nat.scrolling: disabled Middle emulation: disabled Calibration: n/a Scroll methods: *two-finger edge Click methods: *button-areas clickfinger Disable-w-typing: enabled Disable-w-trackpointing: enabled Accel profiles: flat *adaptive custom Rotation: n/a ``` Which do not show up at all on the 6.12 kernel on `libinput list-devices` or `lsusb`, even with pixart disabled. It does however still show up in hwinfo on 6.12: ``` ... P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:45/ASUF1208:00 M: ASUF1208:00 R: 00 U: acpi E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:45/ASUF1208:00 E: SUBSYSTEM=acpi E: MODALIAS=acpi:ASUF1208:PNP0C50: E: USEC_INITIALIZED=5371232 E: ID_VENDOR_FROM_DATABASE=Asuscom Network Inc ... /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:45/ASUF1208:00 ``` Any idea how I can reactive this as an input device? Any things I can try to get it to work? I'm able to build custom kernels if needed.
@wendellmisiedjan, can you attach both dmesg, the one with the 6.12 fedora kernel that was faulty initially, and the new one you just compiled. Also, if you reboot to the 6.11 kernel is everything OK (please attach a third dmesg)? One thing that might be an issue is if the device is not completely reset (so cold boot), but it should be fine given that you rebooted...
(In reply to Benjamin Tissoires from comment #10) > @wendellmisiedjan, can you attach both dmesg, the one with the > 6.12 fedora kernel that was faulty initially, and the new one you just > compiled. > > Also, if you reboot to the 6.11 kernel is everything OK (please attach a > third dmesg)? > > One thing that might be an issue is if the device is not completely reset > (so cold boot), but it should be fine given that you rebooted... Don't now how to 'attach' here but here are three gists for dmesg: - Linux version 6.11.0-63.fc41.x86_64: https://gist.github.com/ItsWendell/3069e39fb612d4213fd8710ecea86dbd This link above is the latest stable 6.11 from Fedora's default repositories, here the trackpad works fine. - 12.0-0.0.next.20241002.418.vanilla.fc41.x86_64: https://gist.github.com/ItsWendell/4e0b6cc7516909e2da226f3b843e25bd This link above is the latest official Fedora Vanilla Kernel from the @kernel-vanilla/next corp. - 6.12.0-0.rc1.20241001gite32cde8d2bd7.18.fc42.x86_64 This is the latest build from git, build using instructions here: https://docs.fedoraproject.org/en-US/quick-docs/kernel-build-custom/#_building_a_kernel_from_the_fedora_dist_git, where I removed CONFIG_MOUSE_PS2_PIXART from the kernel config by adding `# CONFIG_MOUSE_PS2_PIXART is not set` to the `kernel-local` file. Let me know if there's anything else I can sent or test out.
I forgot to attach the link for 6.12.0-0.rc1.20241001gite32cde8d2bd7.18.fc42.x86_64 without CONFIG_MOUSE_PS2_PIXART: https://gist.github.com/ItsWendell/719013dd40ad9ffc1ba945dca40f729d
I saw that the Vanilla kernel updated, so I also tried that one, here's a summary again: Output of dmesg: - 6.11.0-63.fc41.x86_64: https://gist.github.com/ItsWendell/3069e39fb612d4213fd8710ecea86dbd - Working touchpad - 6.12.0-0.rc1.20241001gite32cde8d2bd7.18.fc42.x86_64:https://gist.github.com/ItsWendell/719013dd40ad9ffc1ba945dca40f729d - Touchpad not working, custom build Fedora Linux Kernel, no CONFIG_MOUSE_PS2_PIXART - 6.12.0-0.0.next.20241002.418.vanilla.fc41.x86_64: https://gist.github.com/ItsWendell/4e0b6cc7516909e2da226f3b843e25bd - @kernel-vanilla/next - 2024-10-02 - Touchpad not working - 6.12.0-0.0.next.20241003.419.vanilla.fc41.x86_64:https://gist.github.com/ItsWendell/a80391c1a67f41ebc0cba3432e47ba47 - @kernel-vanilla/next - 2024-10-03 - Touchpad not working
sigh, so it seems we have another problem. Most likely i2c or ACPI related... We would need to bisect the faulty commit, and bisecting on real hardware is a pain. In any cases, we can try to shorten the bisect by testing the first building kernel of https://copr.fedorainfracloud.org/coprs/g/kernel-vanilla/mainline/builds/ -> 6.12.0-0.rc0.20240920gt2004cef1.207.vanilla should give us if commit 2004cef1 is bad or good. But given that this commit has already i2c and HID changes in it, this will probably be a bad commit. If it's a good one, we can try the next until we find the first bad. anyway, the more tests of upstream kernels we have, the better we'll be able to pinpoint the culprit.
(In reply to Benjamin Tissoires from comment #14) > sigh, so it seems we have another problem. Most likely i2c or ACPI related... > > > We would need to bisect the faulty commit, and bisecting on real hardware is > a pain. > > In any cases, we can try to shorten the bisect by testing the first building > kernel of > https://copr.fedorainfracloud.org/coprs/g/kernel-vanilla/mainline/builds/ > -> 6.12.0-0.rc0.20240920gt2004cef1.207.vanilla should give us if commit > 2004cef1 is bad or good. > > But given that this commit has already i2c and HID changes in it, this will > probably be a bad commit. > > If it's a good one, we can try the next until we find the first bad. > > anyway, the more tests of upstream kernels we have, the better we'll be able > to pinpoint the culprit. I just did a clean build straight from the linux kernel git, and this seems fixed in 7ec462100ef9142344ddbf86f2c3008b97acddbe, likely because of the following merge: - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f23aa4c0761a70bfd046dd5755281667f0769a94
> I just did a clean build straight from the linux kernel git, and this seems fixed in 7ec462100ef9142344ddbf86f2c3008b97acddbe, great! > likely because of the following merge: > > - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f23aa4c0761a70bfd046dd5755281667f0769a94 I highly doubt that. Your normal boot should never hit that code path. It would only be triggered if you have udev-hid-bpf and all it does is reject the HID-BPF program. In no ways it would prevent PS/2 or i2c-hid to spin up. a3f9a74d210bf5b80046a840d3e9949b5fe0a67c is the revert of the PixArt commit, and it seems more appropriate, but why this wasn't solving the previous builds is a mystery.
Ah right, I'm fairly new to the lower-level Linux kernel world, might be that my previous custom kernel build didn't properly get rid of CONFIG_MOUSE_PS2_PIXART entirely. Thanks for the support anyways. Quite happy with the latest kernel build I did and looks like 6.12.rc2 is coming soon, runs quite stable on my ASUS Zenbook S 14 UX5406SA with lunar lake.
It looks like we might have reverted the problematic change based on the comments here. But fwiw, I have a Red Hat issued Thinkpad P1 Gen4 with the same issue. Let me know if we need anything additional for this one. Brief details: ❯ uname -r 6.12.0-0.rc1.17.fc42.x86_64 ❯ sudo dmesg | grep touchpa Place your right index finger on the fingerprint reader [ 2.349392] psmouse serio1: pixart_ps2: init: Unable to query PixArt touchpad hardware. I don't think there's anything overly relevant, but just in-case, a fpaste --sysinfo: https://paste.centos.org/view/fce7fcad And dmesg: https://paste.centos.org/view/6be6c004 If there's a brew build of a kernel you need testing, I'm happy to give it a run.
I have Lenovo Yoga Slim and the touchpad doesn't work with 6.12. Seems like the drivers got removed from the kernel. This is from 6.11: grep -i designware config-6.11.0-63.fc42.x86_64 ... CONFIG_I2C_DESIGNWARE_CORE=y CONFIG_I2C_DESIGNWARE_SLAVE=y CONFIG_I2C_DESIGNWARE_PLATFORM=y CONFIG_I2C_DESIGNWARE_BAYTRAIL=y CONFIG_I2C_DESIGNWARE_PCI=y ... And the same from 6.12: grep -i designware config-6.12.0-0.rc1.20241005git27cc6fdf7201.22.fc42.x86_64 ... # CONFIG_I2C_DESIGNWARE_CORE is not set # CONFIG_SPI_DESIGNWARE is not set # CONFIG_SND_DESIGNWARE_I2S is not set ? What was the issue that caused the removal?
I have Asus Zenbook 14 UX3405MA (Meteor Lake) and the touchpad doesn't work with 6.12rc2 ---> 6.12.0-0.rc2.223.vanilla (https://copr.fedorainfracloud.org/coprs/g/kernel-vanilla/mainline-wo-mergew/). Touchpad is a Designware product.
> This is from 6.11: > grep -i designware config-6.11.0-63.fc42.x86_64 > ... > CONFIG_I2C_DESIGNWARE_CORE=y > CONFIG_I2C_DESIGNWARE_SLAVE=y > CONFIG_I2C_DESIGNWARE_PLATFORM=y > CONFIG_I2C_DESIGNWARE_BAYTRAIL=y > CONFIG_I2C_DESIGNWARE_PCI=y > ... > > And the same from 6.12: > grep -i designware config-6.12.0-0.rc1.20241005git27cc6fdf7201.22.fc42.x86_64 > ... > # CONFIG_I2C_DESIGNWARE_CORE is not set > # CONFIG_SPI_DESIGNWARE is not set > # CONFIG_SND_DESIGNWARE_I2S is not set > ? > What was the issue that caused the removal? Ouch, very much ouch. It seems that this driver got disabled in 28b3da71f8a3bbd4947adeeba223527776e01927 in dist-git. That I2C driver is used in many platforms, and disabling it is probably some sort of mistake. I'll try to track down Justin, I'm not sure about his BZ handle
(In reply to as400 from comment #20) > I have Asus Zenbook 14 UX3405MA (Meteor Lake) and the touchpad doesn't work > with 6.12rc2 ---> 6.12.0-0.rc2.223.vanilla > (https://copr.fedorainfracloud.org/coprs/g/kernel-vanilla/mainline-wo-mergew/ > ). > > Touchpad is a Designware product. @lukasz.pl Good catch! I can confirm that this is the issue. I just ran a custom build on `v6.12-rc2` with the following .config changes and it made my touchpad work on ASUS Zenbook S 14 UX5406SA on Fedora Linux 41. `olddefconfig` + the following configs changed: ``` CONFIG_I2C_DESIGNWARE_CORE=y CONFIG_I2C_DESIGNWARE_SLAVE=y CONFIG_I2C_DESIGNWARE_PLATFORM=m CONFIG_I2C_DESIGNWARE_AMDPSP=y CONFIG_I2C_DESIGNWARE_BAYTRAIL=y CONFIG_I2C_DESIGNWARE_PCI=m CONFIG_SPI_DESIGNWARE=m CONFIG_SND_DESIGNWARE_I2S=m CONFIG_SND_DESIGNWARE_PCM=y # # DesignWare-based PCIe controllers # CONFIG_PCIE_DW=y CONFIG_PCIE_DW_HOST=y CONFIG_PCI_MESON=m CONFIG_PCIE_DW_PLAT=y CONFIG_PCIE_DW_PLAT_HOST=y ```
(In reply to wendellmisiedjan from comment #22) > @lukasz.pl Good catch! I can confirm that this is the issue. I > just ran a custom build on `v6.12-rc2` with the following .config changes > and it made my touchpad work on ASUS Zenbook S 14 UX5406SA on Fedora Linux > 41. > > > `olddefconfig` + the following configs changed: > > ``` > CONFIG_I2C_DESIGNWARE_CORE=y > CONFIG_I2C_DESIGNWARE_SLAVE=y > CONFIG_I2C_DESIGNWARE_PLATFORM=m Note this one must be: CONFIG_I2C_DESIGNWARE_PLATFORM=y Since one some platform I2cSerialBus OpRegion accesses are used for ACPI devices _PR0 (power on) methods which run way before any modules get loaded. > CONFIG_I2C_DESIGNWARE_AMDPSP=y > CONFIG_I2C_DESIGNWARE_BAYTRAIL=y > CONFIG_I2C_DESIGNWARE_PCI=m This one used to be =y too for similar reasons. The below options are all unrelated should be left at their old values. > CONFIG_SPI_DESIGNWARE=m > > CONFIG_SND_DESIGNWARE_I2S=m > CONFIG_SND_DESIGNWARE_PCM=y > > # > # DesignWare-based PCIe controllers > # > CONFIG_PCIE_DW=y > CONFIG_PCIE_DW_HOST=y > CONFIG_PCI_MESON=m > CONFIG_PCIE_DW_PLAT=y > CONFIG_PCIE_DW_PLAT_HOST=y > ```
*** Bug 2271136 has been marked as a duplicate of this bug. ***
I have submitted a merge-request to fix the I2C_DESIGNWARE related options for the next rawhide kernel build: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3429
(In reply to darin from comment #19) > I have Lenovo Yoga Slim and the touchpad doesn't work with 6.12. Seems like > the drivers got removed from the kernel. > > This is from 6.11: > grep -i designware config-6.11.0-63.fc42.x86_64 > ... > CONFIG_I2C_DESIGNWARE_CORE=y > CONFIG_I2C_DESIGNWARE_SLAVE=y > CONFIG_I2C_DESIGNWARE_PLATFORM=y > CONFIG_I2C_DESIGNWARE_BAYTRAIL=y > CONFIG_I2C_DESIGNWARE_PCI=y > ... > > And the same from 6.12: > grep -i designware config-6.12.0-0.rc1.20241005git27cc6fdf7201.22.fc42.x86_64 > ... > # CONFIG_I2C_DESIGNWARE_CORE is not set > # CONFIG_SPI_DESIGNWARE is not set > # CONFIG_SND_DESIGNWARE_I2S is not set > ? > What was the issue that caused the removal? Thanks for pointing this out. I had not set the configs for Fedora yet for 6.12, but it appears that a new arch is supported by those drivers. Our automation turned it off in pending, which overrides all of our already set bits. I am fixing it for today's rc2 build.
(In reply to Justin M. Forbes from comment #26) > Thanks for pointing this out. I had not set the configs for Fedora yet for > 6.12, but it appears that a new arch is supported by those drivers. Our > automation turned it off in pending, which overrides all of our already set > bits. I am fixing it for today's rc2 build. Justin, note I already submitted a MR to fix this: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3429
For me the touchpad is back (Asus UX3405MA - Meteor Lake - Designware touchpad). Thanks guys !
fwiw, my Thinkpad P1 Gen4 touchpad works after the revert in the rc2 kernel: Removed the overrides: ❯ sudo rpm-ostree override reset kernel kernel-core kernel-modules-extra kernel-modules kernel-modules-core Checking out tree af81569... done Resolving dependencies... done Applying 2 overrides and 252 overlays Processing packages... done Running pre scripts... done Running post scripts... done Running posttrans scripts... done Writing rpmdb... done Writing OSTree commit... done Staging deployment... done Freed: 84.3 MB (pkgcache branches: 0) Upgraded: kernel 6.11.1-300.fc41 -> 6.12.0-0.rc2.24.fc42 kernel-core 6.11.1-300.fc41 -> 6.12.0-0.rc2.24.fc42 kernel-modules 6.11.1-300.fc41 -> 6.12.0-0.rc2.24.fc42 kernel-modules-core 6.11.1-300.fc41 -> 6.12.0-0.rc2.24.fc42 kernel-modules-extra 6.11.1-300.fc41 -> 6.12.0-0.rc2.24.fc42 Run "systemctl reboot" to start a reboot Reboot and check dmesg: ❯ sudo dmesg | grep touch Place your right index finger on the fingerprint reader [ 2.664401] hid-multitouch 0018:04F3:3197.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN067A:00 04F3:3197] on i2c-ELAN067A:00 ❯ uname -r 6.12.0-0.rc2.24.fc42.x86_64
Original bug-creator here: fix confirmed in 6.12.0-0.rc2.24.fc42.x86_64 I: Bus=0018 Vendor=06cb Product=cd8b Version=0100 N: Name="SYNA8004:00 06CB:CD8B Touchpad" P: Phys=i2c-SYNA8004:00 S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-SYNA8004:00/0018:06CB:CD8B.0002/input/input14 U: Uniq= H: Handlers=mouse3 event7 B: PROP=5 B: EV=1b B: KEY=e520 10000 0 0 0 0 B: ABS=2e0800000000003 B: MSC=20 Thanks Justin!
Hi all: First of all, I'm very sorry that due to the PIxArt patch everyone's touchapd is not working properly. I have since fixed the flaws on the new version of the patch[1] and verified it on TPPS/2 and SynPS/2 Synaptics TouchPad devices, but the patch was unresponsive for a long time. I'm guessing it may be that someone who had the problem before is needed to help verify that the patch is correct. If anyone is interested in helping me to verify the patch if it is convenient for them, many thanks! [1]:https://lore.kernel.org/all/20241023083805.2164641-1-zhoubinbin@loongson.cn/
My touchapad is *-input:5 product: HTIX5288:00 0911:5288 Touchpad physical id: 7 logical name: input7 logical name: /dev/input/event4 logical name: /dev/input/mouse0 capabilities: i2c Touchpad was ok last time in kernel 6.11 Not working ok in kernel 6.12 and 6.14 It's working in not comfortable way using 2 fingers to move cursor, and 3 fingers to scroll Using one finger only is causing jumping cursor randomly at all screen