this issue is not specific to my current DE (Niri), as it has occurred on GNOME and KDE aswell (all Wayland)
my touchpad can only register single-finger clicks - moving the cursor doesn't work, multi-finger clicks (i.e. two fingers for right click) get generalized to a single-finger input and register as a regular click
would appreciate some help as I miss using my touchpad :p
#Touchpad not working?
54 messages · Page 1 of 1 (latest)
Touchpad not working?
Does this issue occur on X11 or no? I'd like to see first if this is isolated to Wayland only
lspci should show the device. usually searching that will lead you in the right direction. sounds like the driver package may need to be installed.
You ignored the litany, provide output of inxi -Fza and dmesg | grep -i hid. Also, try adding i2c_hid_acpi to MODULES in /etc/mkinitcpio.conf and run mkinitcpio -P.
on X11 my touchpad becomes a built-in paperweight (tested on XFCE, Xorg session)
oh I see
@winter pumice Could you do lscpi as instructed here? Also, may I know what your laptop is
will do when i get home, forgot to bring my ssd
Do you boot from a portable SSD?
hardware is a Dell Chromebook 3120 2-in-1
I don't know if that affects anything but interesting to know
i have stuff from libinput from previous help sesh's
such as my touchpad showing up as a mouse and touchpad (seperate devices)
if that info would help at all
I see, give me a second
Could you do this for me
Type sudo libinput list-devices and then sudo libinput quirk list /dev/input/evenN where eventN is the path for your input device
For the first part, do show me what it is first
will do when i get home soon
which input device though?
since my touchpad is registered as a mouse AND touchpad on event8 and event9 respectively iirc
both event8 and event9 output nothing
literally nothing
00:00.0 Host bridge: Intel Corporation Alder Lake-N Processor Host Bridge/DRAM Registers
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-N [UHD Graphics]
00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant
00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01)
00:0d.0 USB controller: Intel Corporation Alder Lake-N Processor USB 3.2 xHCI Controller
00:14.0 USB controller: Intel Corporation Alder Lake-N PCH USB 3.2 Gen 2x1 (10 Gb/s) xHCI Host Controller
00:14.2 RAM memory: Intel Corporation Alder Lake-N PCH Shared SRAM
00:14.3 Network controller: Intel Corporation Alder Lake-N PCH CNVi WiFi
00:15.0 Serial bus controller: Intel Corporation Alder Lake-N PCH I2C Controller
00:15.1 Serial bus controller: Intel Corporation Alder Lake-N PCH I2C Controller
00:15.3 Serial bus controller: Intel Corporation Alder Lake-N PCH I2C Controller
00:16.0 Communication controller: Intel Corporation Alder Lake-N PCH HECI Controller
00:19.0 Serial bus controller: Intel Corporation Alder Lake-N I2C Controller #4
00:19.1 Serial bus controller: Intel Corporation Alder Lake-N I2C Controller #5
00:1a.0 SD Host controller: Intel Corporation Alder Lake-N eMMC Controller
00:1e.0 Communication controller: Intel Corporation Alder Lake-N Serial IO UART Host Controller
00:1f.0 ISA bridge: Intel Corporation Alder Lake-N PCH eSPI Controller
00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake-N PCH High Definition Audio Controller
00:1f.5 Serial bus controller: Intel Corporation Alder Lake-N SPI (flash) Controller
ill come back to this in a bit
kk
heres the outputs of inxi -Fza and dmesg | grep -i hid
oh yeah my bootc arch setup probably technically isnt vanilla arch
ill remove the vanilla tag
ok, that's the device. not sure why it shows up hid-generic and hid-multitouch, but that's probably not an issue.
hid-multitouch 0018:04F3:439B.0004: input,hidraw3: I2C HID v1.00 Device [ELAN900C:00 04F3:439B] on i2c-ELAN900C:00
what does
journalctl -xb | grep elan_i2c
show in terminal?
if you see the line shown in this page, the fix is listed right below it.
https://wiki.archlinux.org/title/Laptop#Elantech
if that doesn't work, this might help too.
https://wiki.archlinux.org/title/Libinput#Configuration
journalctl command gives no output
also, could this line from dmesg have anything to do with my issue?
[ 1.998415] i2c_hid_acpi i2c-ELAN900C:00: i2c_hid_get_input: IRQ triggered but there's no data
@winter pumice Sorry, i forgot to get back to you
Could you check if this works
Create /etc/libinput/local-overrides.quirks
Add this
[Uldren Touchpad]
MatchName=ELAN900C:00*
MatchBus=i2c
AttrResolutionHint=31x31
AttrPressureRange=10:8
and reboot? or logout and back in?
rebooted after making the file (ensured the filename was correct, contents were correct), nothing changed
ic, ill get back to u
after some minor research, skipping the deets, i2c doesn't like hid. Some bios' have a setting to set the touchpad to hid or i2c, or basic to advanced, the setting might be tied to efi, so you can try looking around in the bios for touchpad settings. Some might only be able to do that within the windows driver software. And some might not even have the setting.
Someone else found a loose screw that was apparently shorting something out causing similar issues.
you're running a brand new kernel, so I can't see that being the issue, but def a possibility. I think there's an app to manage kernels on cachy, so should be able to install an older one there. But that can be a bit much for new users...
if you post the output of
dmesg
and
journalctl -xb
as well as
lsmod | grep i2c
and
lsmod | grep hid
can check more, but check the bios settings in the meantime.
bios settings have nothing in terms of touchpad stuff
since my hardware is a chromebook, im using altfw to boot Arch if thats important at all
just wanted to ask if you found anything
unfortunately i havent, but i do have a general solution that might work
do tell?
[ELAN Touchpad]
MatchName=*ELAN*Touchpad*
AttrResolutionHint=31x31
AttrPressureRange=10:8
Delete /etc/libinput/local-overrides.quirks (don't if it already existed before you opened this thread) and then recreate it again with this as the content
@winter pumice
will try
do i reboot or just logout
i rebooted, nothing changed
damn