Touchpad Mouse not recognized - Arch Linux - AMD 13

Andrew_Dekker · April 10, 2024, 8:39pm

I am running Arch on my AMD Framework. I’ve had the laptop for a couple months now and have not been able to get the touchpad working. If I run ubuntu live from usb the touchpad works.

Linux dti 6.8.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 05 Apr 2024 00:14:23 +0000 x86_64 GNU/Linux

Xinput list does not show the touchpad, dmesg does not show it either

dmesg | grep input
[122630.035989] hid-generic 0003:32AC:0002.0017: hiddev96,hidraw0: USB HID v1.11 Device [Framework HDMI Expansion Card] on usb-0000:c1:00.3-1/input1
[122637.779250] input: DP-2 as /devices/pci0000:00/0000:00:08.1/0000:c1:00.0/rc/rc0/input43
[122639.455031] input: ELECOM TrackBall Mouse DEFT Pro TrackBall as /devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5/5-1/5-1.3/5-1.3:1.0/0003:056E:0132.0018/input/input44
[122639.509722] hid-generic 0003:056E:0132.0018: input,hidraw0: USB HID v1.11 Keyboard [ELECOM TrackBall Mouse DEFT Pro TrackBall] on usb-0000:c3:00.3-1.3/input0
[122639.516958] input: ELECOM TrackBall Mouse DEFT Pro TrackBall as /devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5/5-1/5-1.3/5-1.3:1.1/0003:056E:0132.0019/input/input45
[122639.517121] hid-generic 0003:056E:0132.0019: input,hidraw1: USB HID v1.11 Mouse [ELECOM TrackBall Mouse DEFT Pro TrackBall] on usb-0000:c3:00.3-1.3/input1
[122639.526273] input: ELECOM TrackBall Mouse DEFT Pro TrackBall Consumer Control as /devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5/5-1/5-1.3/5-1.3:1.2/0003:056E:0132.001A/input/input46
[122639.584460] input: ELECOM TrackBall Mouse DEFT Pro TrackBall System Control as /devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5/5-1/5-1.3/5-1.3:1.2/0003:056E:0132.001A/input/input47
[122639.584839] hid-generic 0003:056E:0132.001A: input,hidraw4: USB HID v1.11 Device [ELECOM TrackBall Mouse DEFT Pro TrackBall] on usb-0000:c3:00.3-1.3/input2
[122639.592331] hid-generic 0003:056E:0132.001B: hiddev96,hidraw5: USB HID v1.10 Device [ELECOM TrackBall Mouse DEFT Pro TrackBall] on usb-0000:c3:00.3-1.3/input3
[122639.599650] input: DP-4 as /devices/pci0000:00/0000:00:08.1/0000:c1:00.0/rc/rc1/input48
[122639.634562] hid-generic 0003:32AC:0002.001C: hiddev97,hidraw6: USB HID v1.11 Device [Framework HDMI Expansion Card] on usb-0000:c1:00.3-1/input1
[164298.097233] hid-generic 0003:32AC:0002.001D: hiddev96,hidraw0: USB HID v1.11 Device [Framework HDMI Expansion Card] on usb-0000:c1:00.3-1/input1
[164312.734629] input: DP-4 as /devices/pci0000:00/0000:00:08.1/0000:c1:00.0/rc/rc0/input49
[164312.785419] hid-generic 0003:32AC:0002.001E: hiddev96,hidraw0: USB HID v1.11 Device [Framework HDMI Expansion Card] on usb-0000:c1:00.3-1/input1
[164354.240505] wacom 0003:056A:03C7.001F: hidraw1: USB HID v1.10 Device [Wacom Co.,Ltd. Intuos BT M] on usb-0000:c3:00.3-1.3/input0
[164354.240566] input: Wacom Intuos BT M Pen as /devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5/5-1/5-1.3/5-1.3:1.0/0003:056A:03C7.001F/input/input50
[164354.240823] input: Wacom Intuos BT M Pad as /devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5/5-1/5-1.3/5-1.3:1.0/0003:056A:03C7.001F/input/input52
[164354.716372] input: HD Webcam eMeet C960: HD Webcam as /devices/pci0000:00/0000:00:08.3/0000:c3:00.3/usb5/5-1/5-1.4/5-1.4:1.0/input/input53

Is there anyone else with Arch and an AMD framework that has this working?

Thanks

Mario_Limonciello · April 10, 2024, 9:14pm

Make sure these are in your Kconfig:

CONFIG_I2C_HID=y
CONFIG_I2C_HID_CORE=m
CONFIG_PINCTRL_AMD=y
CONFIG_I2C_HID_ACPI=m
CONFIG_HID_MULTITOUCH=m

Andrew_Dekker · April 11, 2024, 2:14pm

Thanks for the pointers, I think I’m getting closer.
my config looks like this:

CONFIG_I2C_HID=m
CONFIG_I2C_HID_CORE=m
CONFIG_PINCTRL_AMD=y
CONFIG_I2C_HID_ACPI=m
CONFIG_HID_MULTITOUCH=m

HID_MULTITOUCH was not loaded for some reason.
I added it:

echo “hid_multitouch” | sudo tee /etc/modules-load.d/hid_multitouch.conf

I then rebooted and the mouse still doesnt work.

lsmod | grep i2c
i2c_algo_bit 20480 1 amdgpu
i2c_piix4 32768 0
i2c_hid_acpi 12288 0
i2c_hid 40960 1 i2c_hid_acpi
i2c_dev 28672 0

lsmod | grep hid
uhid 20480 3
i2c_hid_acpi 12288 0
i2c_hid 40960 1 i2c_hid_acpi
mac_hid 12288 0
hid_multitouch 32768 0
hid_generic 12288 0
usbhid 77824 1 wacom

Am I missing other kernel modules?

Mario_Limonciello · April 11, 2024, 2:24pm

Those are the biggies. You must be missing something much more fundamental.
Post the full dmesg and kconfig somewhere I can see, I’ll see if anything stands out to me.

Andrew_Dekker · April 11, 2024, 2:29pm

Here is the pastebin
dmesg

kconfig

Thank you for looking at this for me!

Mario_Limonciello · April 11, 2024, 2:40pm

This is the most concerning issue to me. This will prevent the i2c stuff from working.

[    0.566676] i2c_designware AMDI0010:00: Unknown Synopsys component type: 0xffffffff
[    0.576510] i2c_designware AMDI0010:03: Unknown Synopsys component type: 0xffffffff

github.com

torvalds/linux/blob/20cb38a7af88dc40095da7c2c9094da3873fea23/drivers/i2c/busses/i2c-designware-common.c#L165


      
          		map_cfg.max_register = AMD_UCSI_INTR_REG;
          
          	if (reg == swab32(DW_IC_COMP_TYPE_VALUE)) {
          		map_cfg.reg_read = dw_reg_read_swab;
          		map_cfg.reg_write = dw_reg_write_swab;
          	} else if (reg == (DW_IC_COMP_TYPE_VALUE & 0x0000ffff)) {
          		map_cfg.reg_read = dw_reg_read_word;
          		map_cfg.reg_write = dw_reg_write_word;
          	} else if (reg != DW_IC_COMP_TYPE_VALUE) {
          		dev_err(dev->dev,
          			"Unknown Synopsys component type: 0x%08x\n", reg);
          		return -ENODEV;
          	}
          
          	/*
          	 * Note we'll check the return value of the regmap IO accessors only
          	 * at the probe stage. The rest of the code won't do this because
          	 * basically we have MMIO-based regmap so non of the read/write methods
          	 * can fail.
          	 */
          	dev->map = devm_regmap_init(dev->dev, NULL, dev, &map_cfg);

This means it can’t access a register properly. Can you please try to reset BIOS default settings (if you haven’t already)?

If that doesn’t help - what bootloader and boot process are you using? Any patches you’ve added to the kernel that could cause this?

Also tangentially related this stands out but isn’t the cause. I don’t know what is setting it, but I’ve never heard of that parameter for the i2c-hid driver.

[    3.701053] i2c_hid: unknown parameter 'force' ignored

Andrew_Dekker · April 11, 2024, 2:53pm

I set the bios to defaults. (I havent changed anything in there other than secure boot)

I am running ZFS on root with the ZFSBOOTLOADER.

I followed along eoli3n’s guides here:

github.com

eoli3n/archiso-zfs/blob/master/init

#!/bin/bash
# This script load zfs kernel module for any archiso.
# github.com/eoli3n
# Thanks to CalimeroTeknik on #archlinux-fr, FFY00 on #archlinux-projects, JohnDoe2 on #regex

exec &> >(tee "debug.log")

### Vars

verbose=0

### Functions

usage () {
    cat << EOF
Usage: ${0##*/} [-v]

    -v    increase verbosity
    -h    show this usage
EOF

This file has been truncated. show original

and use his install scripts to speed up the install process.

github.com

eoli3n/arch-config/blob/master/scripts/zfs/install/01-configure.sh

#!/usr/bin/env bash

set -e

exec &> >(tee "configure.log")

print () {
    echo -e "\n\033[1m> $1\033[0m\n"
}

ask () {
    read -p "> $1 " -r
    echo
}

menu () {
    PS3="> Choose a number: "
    select i in "$@"
    do 
        echo "$i"

This file has been truncated. show original

github.com

eoli3n/arch-config/blob/master/scripts/zfs/install/02-install.sh

#!/usr/bin/env bash

set -e

exec &> >(tee "install.log")

# Debug
if [[ "$1" == "debug" ]]
then
    set -x
    debug=1
fi

print () {
    echo -e "\n\033[1m> $1\033[0m\n"
    if [[ -n "$debug" ]]
    then
      read -rp "press enter to continue"
    fi
}

This file has been truncated. show original

I’m pretty sure I’ve installed some intel stuff into the kernel that I shouldnt have.

Shiroudan · April 11, 2024, 3:08pm

Might be worth it to check if grabbing a new kernel works and what you modified.
From my experience on Arch though, it’s usually easier to just backup your /home and reinstall. I don’t know anyone with FW AMD on Arch who’s experienced these issues (albeit with a sample size of 2), so it might just be your setup.

Mario_Limonciello · April 11, 2024, 3:21pm

Most of that shouldn’t matter. The kernel will only load what’s applicable. From the error above the base address register seems wrong, or something is blocking the read of the register.

From my experience on Arch though, it’s usually easier to just backup your /home and reinstall.

This is true. You can then also check if thing work in the installer and whittle down what causes the breakage. I’m not sure what patches go into making ZFS work in the kernel, but I’d question whether any of those are part of the problem.

Andrew_Dekker · April 11, 2024, 3:25pm

I’m going to give that a shot in the next day or two when I can dedicate a few hours to it. (I’ve got a pretty robust dotfiles repo and a set of ansible scripts to setup my system the way I like it now so a reinstall should only take a few hours.)

Thanks for your help!! I’ll report back what I find in case anyone else comes accross this in the future.