Touchpad not working after installation is over

Hii everyone I am new to arch linux ( garuda ) , I am facing touchpad issues in my laptop the touchpad is not working on garuda linux , it was working during the installation but after the installation it stopped working , I am having an HP pavillion 15 gaming laptop and my hardware details are

System:    Kernel: 5.14.8-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0 
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=b394cb36-0493-48d9-a35f-d557291d2bc1 
rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 
systemd.unified_cgroup_hierarchy=1 loglevel=3 
Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM 
Distro: Garuda Linux base: Arch Linux 
Machine:   Type: Laptop System: HP product: HP Pavilion Gaming Laptop 15-ec1xxx v: N/A serial: <filter> 
Chassis: type: 10 serial: <filter> 
Mobo: HP model: 87B1 v: 31.21 serial: <filter> UEFI: AMI v: F.20 date: 11/04/2020 
Battery:   ID-1: BAT0 charge: 34.4 Wh (67.5%) condition: 51.0/51.0 Wh (100.0%) volts: 11.7 min: 11.6 
model: Hewlett-Packard Primary type: Li-ion serial: N/A status: Discharging cycles: 459 
CPU:       Info: 6-Core model: AMD Ryzen 5 4600H with Radeon Graphics bits: 64 type: MT MCP arch: Zen 2 
family: 17 (23) model-id: 60 (96) stepping: 1 microcode: 8600106 cache: L2: 3 MiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 71862 
Speed: 1397 MHz min/max: 1400/3000 MHz boost: enabled Core speeds (MHz): 1: 1397 2: 1397 
3: 1385 4: 1395 5: 1397 6: 1397 7: 1397 8: 1397 9: 1592 10: 1395 11: 1397 12: 1397 
Vulnerabilities: Type: itlb_multihit status: Not affected 
Type: l1tf status: Not affected 
Type: mds status: Not affected 
Type: meltdown status: Not affected 
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
Type: spectre_v2 
mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling 
Type: srbds status: Not affected 
Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA TU117M vendor: Hewlett-Packard driver: nvidia v: 470.74 
alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1f99 class-ID: 0300 
Device-2: AMD Renoir vendor: Hewlett-Packard driver: amdgpu v: kernel bus-ID: 04:00.0 
chip-ID: 1002:1636 class-ID: 0300 
Device-3: Quanta HP TrueVision HD Camera type: USB driver: uvcvideo bus-ID: 3-3:2 
chip-ID: 0408:5365 class-ID: 0e02 
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: modesetting 
display-ID: :0 screens: 1 
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9") 
Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x193mm (13.5x7.6") diag: 394mm (15.5") 
OpenGL: renderer: AMD RENOIR (DRM 3.42.0 5.14.8-zen1-1-zen LLVM 12.0.1) v: 4.6 Mesa 21.2.2 
direct render: Yes 
Audio:     Device-1: NVIDIA vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 01:00.1 
chip-ID: 10de:10fa class-ID: 0403 
Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: Hewlett-Packard 
driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x bus-ID: 04:00.5 chip-ID: 1022:15e2 
class-ID: 0480 
Device-3: AMD Family 17h HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel 
bus-ID: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403 
Sound Server-1: ALSA v: k5.14.8-zen1-1-zen running: yes 
Sound Server-2: JACK v: 1.9.19 running: no 
Sound Server-3: PulseAudio v: 15.0 running: no 
Sound Server-4: PipeWire v: 0.3.37 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard 
driver: r8169 v: kernel port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200 
IF: eno1 state: down mac: <filter> 
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: e000 bus-ID: 03:00.0 
chip-ID: 8086:2723 class-ID: 0280 
IF: wlo1 state: up mac: <filter> 
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-4:3 chip-ID: 8087:0029
class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:    Local Storage: total: 931.51 GiB used: 10.76 GiB (1.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400
serial: <filter> rev: RKM2 scheme: GPT
Partition: ID-1: / raw-size: 48.83 GiB size: 48.83 GiB (100.00%) used: 10.69 GiB (21.9%) fs: btrfs
dev: /dev/sda6 maj-min: 8:6
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%) used: 62.3 MiB (24.3%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 48.83 GiB size: 48.83 GiB (100.00%) used: 10.69 GiB (21.9%) fs: btrfs
dev: /dev/sda6 maj-min: 8:6
ID-4: /var/log raw-size: 48.83 GiB size: 48.83 GiB (100.00%) used: 10.69 GiB (21.9%) fs: btrfs
dev: /dev/sda6 maj-min: 8:6
ID-5: /var/tmp raw-size: 48.83 GiB size: 48.83 GiB (100.00%) used: 10.69 GiB (21.9%) fs: btrfs
dev: /dev/sda6 maj-min: 8:6
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 7.13 GiB used: 1.5 MiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 46.1 C mobo: 45.0 C gpu: amdgpu temp: 45.0 C
Fan Speeds (RPM): N/A
Info:      Processes: 321 Uptime: 12m wakeups: 1 Memory: 7.13 GiB used: 2.32 GiB (32.5%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1184 lib: 290
Shell: fish v: 3.3.1 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06

Is the touchpad enabled, both in KDE settings and if there's a function key that will "lock" the touchpad?

Have you tried a different kernel, e.g. linux-lts ?

4 Likes

beat me to it, and i accidentally clicked it , then spent the next 10 mins looking for my mouse :joy:

1 Like

i tried lts still it wasn't working , I checked the touchpad settings from all settings there it was not detecting the touchpad

If this is a new model you could do the other way round, and try the linux-mainline, as newer HW could be better managed there.

1 Like

Yes, although it was working in the live installer environment, so it should be supported by the 5.14 kernel… :thinking:

Can you boot the live environment again and find out what sort of touchpad it is?

2 Likes

whats is linux-mainline sir , I am new to linux so I dont know such terms

how can I check type of touchpad from live environment

Open Garuda Settings Manager, Kernels, push Refresh and you'll see a list of installable kernels. But as notes above, I missed the fact that the touchpad was recognized in the live USB :blush:. But you could try anyway...
From the live USB, I think you could provide the output of:
lsusb
xinput
libinput list-devices

2 Likes