Hi guys ! 🙂

I love KaOS and i installed it (lastest iso 2020) on my new Asus laptop last week.

Unfortunately the touchpad isn't recognized. At first, i thought it was because of the kernel version 5.4 . So i upgraded kernel to 5.5.1 but it didn't change anything and my touchpad is still unrecognized.

I don't know what to do...

Here is the output of xinput:

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ USB OPTICAL MOUSE id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Asus Wireless Radio Control id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ Sleep Button id=10 [slave keyboard (3)]
↳ USB2.0 HD UVC WebCam: USB2.0 HD id=12 [slave keyboard (3)]
↳ Asus WMI hotkeys id=13 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]

Thanks in advance !!
PS: It's my first post and my english isn't very good sry ^^"

@SanjyASZ Welcome to KaOS.
Did the touchpad also not work in Live mode?
Checked dmesg and journalctl for any errors/messages regarding the touchpad? Also check/post the /var/log/Xorg.0.log for any messages regarding the touchpad.
Does the touchpad show in hwinfo --mouse? Post the output of that command to show what hardware this is.
And to be sure, you did not hit a button on the laptop to turn of the touchpad?

Thank you for you quick answer Demm 🙂

Did the touchpad also not work in Live mode?

No touchpad didn't work too in KaOS live mode :/

journalctl, i got an ACPI error but i do not know if it is related or not.

-- Logs begin at Sun 2020-02-09 17:58:03 CET, end at Sun 2020-02-09 21:12:24 CET. --
févr. 09 21:08:00 Asteria kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.SWUS], AE_NOT_FOUND (20191018/dswload2-159)
févr. 09 21:08:00 Asteria kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20191018/psobject-220)
févr. 09 21:08:00 Asteria kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.SWUS.SWDS], AE_NOT_FOUND (20191018/dswload2-159)
févr. 09 21:08:00 Asteria kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20191018/psobject-220)
févr. 09 21:08:00 Asteria kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
févr. 09 21:08:01 Asteria kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xbd2e9000-0xbd2e9fff flags 0x200] vs bd2e9000 4000
févr. 09 21:08:01 Asteria kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xbd2ed000-0xbd2edfff flags 0x200] vs bd2ed000 4000
févr. 09 21:08:02 Asteria kernel: ACPI Error: Divide by zero (20191018/utmath-478)
févr. 09 21:08:02 Asteria kernel: ACPI Error: Aborting method \_SB.ATKD.WMNB due to previous error (AE_AML_DIVIDE_BY_ZERO) (20191018/psparse-529)
févr. 09 21:08:03 Asteria kernel: kvm: disabled by bios
févr. 09 21:08:03 Asteria kernel: kvm: disabled by bios
févr. 09 21:08:03 Asteria kernel: kvm: disabled by bios
févr. 09 21:08:03 Asteria kernel: kvm: disabled by bios
févr. 09 21:08:03 Asteria kernel: kvm: disabled by bios
févr. 09 21:08:03 Asteria kernel: kvm: disabled by bios
févr. 09 21:08:03 Asteria kernel: kvm: disabled by bios
févr. 09 21:08:03 Asteria kernel: kvm: disabled by bios
févr. 09 21:08:04 Asteria kernel: [drm:dm_helpers_parse_edid_caps [amdgpu]] *ERROR* Couldn't read SADs: -2
févr. 09 21:08:05 Asteria systemd-backlight[534]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
févr. 09 21:08:05 Asteria systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.

Here is the Xorg log :
https://paste.ee/p/kEPgM

And the hwinfo --mouse info
There is only my usb mouse x)

38: USB 00.0: 10503 USB Mouse
[Created at usb.122]
Unique ID: CiZ2.VqQxadZ7ky5
Parent ID: uIhY.buxry1DL_88
SysFS ID: /devices/pci0000:00/0000:00:08.1/0000:05:00.3/usb3/3-3/3-3:1.0
SysFS BusID: 3-3:1.0
Hardware Class: mouse
Model: "Pixart Imaging Optical Mouse"
Hotplug: USB
Vendor: usb 0x093a "Pixart Imaging, Inc."
Device: usb 0x2521 "Optical Mouse"
Revision: "1.00"
Compatible to: int 0x0210 0x0045
Driver: "usbhid"
Driver Modules: "usbhid"
Device File: /dev/input/mice (/dev/input/mouse0)
Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event9, /dev/input/by-path/pci-0000:05:00.3-usb-0:3:1.0-event-mouse, /dev/input/by-id/usb-093a_USB_OPTICAL_MOUSE-event-mouse, /dev/input/by-id/usb-093a_USB_OPTICAL_MOUSE-mouse, /dev/input/by-path/pci-0000:05:00.3-usb-0:3:1.0-mouse
Device Number: char 13:63 (char 13:32)
Speed: 1.5 Mbps
Module Alias: "usb:v093Ap2521d0100dc00dsc00dp00ic03isc01ip02in00"
Driver Info #0:
Buttons: 5
Wheels: 4
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #41 (Hub)

Contrary I hit the touchpad button to try to reactivate it...

So far no indication what the touchpad hardware might be, nor any errors/messages about it, looks like it is completely disabled. One more try to find the hardware:

sudo libinput list-devices

And pastebin the full dmesg output, this snippet is not about touchpad.

My touchpad is an Elantech 1200 i think. I forgot to mention it but i have a dual boot with windows 10 ^^"

There is absolute no sign of a touchpad, no errors, nothing. So make sure to boot in your Windows install and check if it is sill working there.

7 days later

Heya, similar issue here on a fresh install of latest KaOS iso on my Asus X505ZA Ryzen 5.
Also the touchpad didn't worked on live, but in no other distro I ever got a non working touchpad on a fresh install. It has something to do with the kernal version I guess but still as with the OP, neither do I see any sign of hardware getting recognized by the kernal.

It looks like generic problem, my laptop arrives with Ubuntu, touchpad works, after installing KaOS it's not even showing in lscpi nor xinput. Something definitely is missing, since i've not using it, it's not a problem to me, but at least i want to confirm that problem is real.

Okay so I did tried linux-next 5.5.x and the issue still persists.

Since no hardware I have available shows this issue, I have to rely on reports to try and debug. So far nothing useful has been shown, not even what hardware is effected, only the OP posted system specs (but no specifics of the touchpad). Are those effected on the same laptop, same touchpad? If it is the kernel, what kernel version did this start?

The issue might be hardware specific as I am using the same Elantech 1200 touchpad.
Just to let you know, the touchpad works real fine on 5.4.18-1-MANJARO (KDE), although it fails to work on live medium.

libinput on my manjaro system gives the following output

Device: ELAN1200:00 04F3:303E Touchpad
Kernel: /dev/input/event13
Group: 9
Seat: seat0, default
Size: 103x71mm
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
Accel profiles: none
Rotation: n/a

  • demm replied to this.

    theventus my manjaro system

    Which kernel? All I can find is that the elantech 1200 has kernel related issues, so would be good to know which kernel was working.

    And for all of you,dmesg | grep elan, does it show any?

    Have any of you tried reloading the needed module, added some restrictions? Try the following and see if the touchpad is at least found:

    sudo rmmod psmouse
    sudo modprobe psmouse proto=exps

    Two finger scrolling won't be supported then.

    Further research for Elantech 1200 showed this started after linux 5.2.8, so the above comments about other distros working make sense, since they are on older kernels at that time.
    Seems for some, they could get the touchpad to the state of 5.2.8 and before by adding elantech_smbus=0 synaptics_intertouch=0 to the kernel boot line (or adding that to the bootloader kernel line).

    I am using a manjaro system with 5.4.18-1-MANJARO and I have tried the latest available kernel there i.e. 5.5.2-1 works fine as well.

    Sorry demm but I have switched to manjaro back so I won't be able to check if your suggestions work. But it is highly appreciated mate! This project is awesome, in near future I'm going to try this again on my other machines.

    Idk how this might be useful but I'm quoting the dmesg output from my manjaro kde below as it seems it indeed has some issues with manjaro too but they somehow made it work it seems.

    sudo dmesg | grep ELAN
    [ 7.985996] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator
    [ 7.986014] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vddl not found, using dummy regulator
    [ 10.733538] input: ELAN1200:00 04F3:303E Mouse as /devices/platform/AMDI0010:01/i2c-0/i2c-ELAN1200:00/0018:04F3:303E.0001/input/input13
    [ 10.733674] input: ELAN1200:00 04F3:303E Touchpad as /devices/platform/AMDI0010:01/i2c-0/i2c-ELAN1200:00/0018:04F3:303E.0001/input/input14
    [ 10.733770] hid-generic 0018:04F3:303E.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN1200:00 04F3:303E] on i2c-ELAN1200:00
    [ 10.795416] input: ELAN1200:00 04F3:303E Mouse as /devices/platform/AMDI0010:01/i2c-0/i2c-ELAN1200:00/0018:04F3:303E.0001/input/input15
    [ 10.795517] input: ELAN1200:00 04F3:303E Touchpad as /devices/platform/AMDI0010:01/i2c-0/i2c-ELAN1200:00/0018:04F3:303E.0001/input/input16
    [ 10.795583] hid-multitouch 0018:04F3:303E.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN1200:00 04F3:303E] on i2c-ELAN1200:00

    5 days later

    Hi guys
    dmesg | grep elan shows nothing x)
    reloading psmouse module didn't work ...
    elantech_smbus=0 synaptics_intertouch=0 same with these :/

    My keyboard backlight doesn't work as well (in kaos only), i think it's related i forgot to mention it too 😅

    3 months later

    Hello, I just installed May 2020 release, and it looks like the problem persists, I think I can live with it, but if I can test something for you, let me know

    • demm replied to this.

      joseangel-leyva I can test something for you, let me know

      See my previous post (#14) in this thread for needed info and trial to see if adding to the kernel line helps.

      I tried but it did not work, reading on some other places they recommend i2c-tools package, but it's not in the repo list

      Please post the logs as asked for, so far no-where near enough debug info to try and fix. Links for the i2c-tools recommendations? I do not see any in the source for that that addresses elantech. "Nothing" or "did not work" is not a helpful response, full dmesg is needed, system info, error logs and so on.
      https://kaosx.us/docs

      Has any of you tried to get the latest firmware for your system with fwupd?
      https://kaosx.us/packages/view.php?repo=main&name=fwupd-1.4.2-1