[root@jeevan-81d2 jeevan]# uname -sr
Linux 5.6.8-1
Touchpad laptop (ASUS TUF 565DV-AL136T) not recognized
Any change with updating the firmware through fwupd? Any known drivers added for this hardware in MXlinux?
here are my results
[root@jeevan-81d2 arms]# fwupdmgr get-devices
81D2
│
├─ST1000LM035-1RK172:
│ Device ID: 177f92eb93c34b31de9c0f36b8475d3c091e8d0e
│ Summary: ATA Drive
│ Current version: LCM2
│ Vendor: Seagate (ATA:0x1BB1)
│ Serial Number: WL1JFSEC
│ GUIDs: 6a793116-b564-5cb0-a746-b2ca1f546ebe ← IDE\ST1000LM035-1RK172______________________LCM2
│ c2429a2a-62bf-54cb-b904-8fe019d0082b ← IDE\0ST1000LM035-1RK172______________________
│ a9922880-34d2-52dc-ac2b-5a1daeedcf7a ← ST1000LM035-1RK172
│ Device Flags: • Internal device
│ • Updatable
│ • Requires AC power
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│
└─System Firmware:
Device ID: 998dfd042e0c467f06b4dbf5134d3f556fafe6fd
Current version: 1461919780
Minimum Version: 1380122624
Vendor: LENOVO (DMI:LENOVO)
GUID: fb935162-0d9f-4738-8689-585d8fff14a9
Device Flags: • Internal device
• Updatable
• Requires AC power
• Needs a reboot after installation
• Cryptographic hash verification is available
• Device is usable for the duration of the update
[root@jeevan-81d2 arms]# fwupdmgr refresh
Firmware metadata last refresh: 11 hours ago. Use --force to refresh again.
[root@jeevan-81d2 arms]# fwupdmgr get-updates
• ST1000LM035-1RK172 has no available firmware updates
• System Firmware has no available firmware updates
No updatable devices
[root@jeevan-81d2 arms]#
No updates for fwupd either
Still looks mostly like a kernel change, any chance any of you can try and see if Linux 5.7 has any fixes/improvements?
See the doc to install linux-next:
https://kaosx.us/docs/kernels/
[root@jeevan-81d2 jeevan]# uname -sr
Linux 5.7.0-1-next
[root@jeevan-81d2 jeevan]# xin
xinit xinput
[root@jeevan-81d2 jeevan]# xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SIGMACHIP Usb Mouse id=10 [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)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ Power Button id=9 [slave keyboard (3)]
↳ EasyCamera: EasyCamera id=11 [slave keyboard (3)]
↳ Ideapad extra buttons id=12 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
[root@jeevan-81d2 jeevan]#
still no touchpad - however I am using the external USB mouse, so I can live with it. Another issue is no WIFI support for
[root@jeevan-81d2 jeevan]# inxi -n
Network: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: N/A
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
IF: enp2s0 state: down mac: e8:6a:64:39:4e:4d
IF-ID-1: enp3s0f3u4 state: unknown speed: N/A duplex: N/A mac: 86:e0:a3:a2:4d:df
[root@jeevan-81d2 jeevan]#
- Edited
Looks like Debian/Ubuntu patches the kernel for elantech:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1700657
Finding many links now for reports on this touchpad failing, examples:
https://askubuntu.com/questions/1049787/lenovo-ideapad-330-touchpad-not-working/1052566#1052566
https://bbs.archlinux.org/viewtopic.php?id=256002
One thing I can try is adjusting the kernel config and disable CONFIG_I2C_SMBUS
and CONFIG_MOUSE_PS2_ELANTECH_SMBUS
, this will be done/tested in linux-next (next build, for 5.7.2).
EDIT:
One more fairly common recommendation is to add psmouse.elantech_smbus=0
to the kernel boot line (should have the same effect as rebuilding the kernel with the elantech entries disabled).
Can any of you report back on the state of these touchpads using linux-next 5.7.2?
It did not worked for me (neither solved the audio in the other tread until the sof-firmware solution). I reinstalled KaOS and I am in the same status of no Touchpad device recognized by the OS.
I also think my computer has Elantech only to drive the trackpoint, but not the trackpad or Touchpad.
On the other hand, checking from an Ubuntu installation where the touchpad worked, it reports these HID devices:
lsmod | grep hid
hid_multitouch 28672 0
mac_hid 16384 0
hid_generic 16384 0
i2c_hid 28672 0
hid 131072 3 i2c_hid,hid_multitouch,hid_generic
dmesg | grep hid
[ 1.266899] hidraw: raw HID events driver (C) Jiri Kosina
[ 1.285833] i2c_hid i2c-SYNA8004:00: i2c-SYNA8004:00 supply vdd not found, using dummy regulator
[ 1.285843] i2c_hid i2c-SYNA8004:00: i2c-SYNA8004:00 supply vddl not found, using dummy regulator
[ 1.335326] hid-generic 0018:06CB:CD8B.0001: input,hidraw0: I2C HID v1.00 Mouse [SYNA8004:00 06CB:CD8B] on i2c-SYNA8004:00
[ 3.568446] hid-multitouch 0018:06CB:CD8B.0001: input,hidraw0: I2C HID v1.00 Mouse [SYNA8004:00 06CB:CD8B] on i2c-SYNA8004:00
dmesg | grep designware
[ 1.335203] input: SYNA8004:00 06CB:CD8B Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA8004:00/0018:06CB:CD8B.0001/input/input6
[ 1.335270] input: SYNA8004:00 06CB:CD8B Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA8004:00/0018:06CB:CD8B.0001/input/input7
[ 3.568228] input: SYNA8004:00 06CB:CD8B Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA8004:00/0018:06CB:CD8B.0001/input/input13
[ 3.568310] input: SYNA8004:00 06CB:CD8B Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-SYNA8004:00/0018:06CB:CD8B.0001/input/input14
That is so far the status
- Edited
So, is this with linux-next 5.7.2? Or psmouse.elantech_smbus=0
added to the kernel boot line?
Please don't be confused by my previous post. I remind you that the previous lsmod and dmesg outputs were in Ubuntu, where the touchpad worked perfectly. Not in KaOS with the current kernel. Also, when I went to linux-next, it also did not worked.
- Edited
kamilomelo Also, when I went to linux-next, it also did not worked.
Is it so hard to post exact outputs? 5.7.2 moved today, so there is no indication what you used. Your previous post just talks about didn't work
, then post about Ubuntu, no logs, no dmesg, no answers about kernel version or boot lines used or anything related to KaOS. This issue can only be resolved if there is actual help, not more posts it didn't work
or I also think my computer
.
Make sure to read asking and reporting the smart way.
- Edited
Yes, you are right, my bad...
Here are some outputs using linux-next (5.7.2-1). No boot lines used:
uname -r
5.7.2-1-next
Here the output of dmesg
As observed, there is a mention of "hid" in that log, but not mention of "touchpad"
[ 1.541755] hid: raw HID events driver (C) Jiri Kosina
Now, here the output of journalctl
It mentions a section for the initialization of "touchpad"
Elantech -> "elan" is mentioned in both logs only related to the trackpoint, which is different to the trackpad or touchpad in Lenovo machines, which works without issues.
Also the output of hwinfo:
hwinfo --mouse
48: PS/2 00.0: 10500 PS/2 Mouse
[Created at input.249]
Unique ID: AH6Q.7qlGUQk7T34
Hardware Class: mouse
Model: "TPPS/2 Elan TrackPoint"
Vendor: 0x0002
Device: 0x000a "TPPS/2 Elan TrackPoint"
Compatible to: int 0x0210 0x0003
Device File: /dev/input/mice (/dev/input/mouse0)
Device Files: /dev/input/mice, /dev/input/mouse0, /dev/input/event6, /dev/input/by-path/platform-i8042-serio-1-event-mouse, /dev/input/by-path/platform-i8042-serio-1-mouse
Device Number: char 13:63 (char 13:32)
Driver Info #0:
Buttons: 3
Wheels: 0
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=new, avail=yes, need=no, active=unknown
Finally, here is the list of devices with libinput.
Any other log or action you might find necessary?
P.S. My intention copying the outputs of dmesg in another distro (Ubuntu) was to show how the missing device was displayed there. Maybe this give us a hint in how to handle this for KaOS. Apologies for the confusion.
- Edited
Line 1 of the DMESG:
microcode: microcode updated early to revision 0xd6, date = 2020-04-23
So you got the latest intel-ucode (one of the changes for linux-next 5.7.2), so newer firmware not available .
thinkpad_acpi: Tablet mode switch found (type: GMMS), currently in laptop mode
[ 1.583516] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
[ 1.583516] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
Possible the above switch is blocking the touchpad? Is it a UEFI/BIOS switch or physical button you can push?
For the rest no trace whatsoever in the journal or dmesg about a touchpad (just plasma is doing the standard kcm stuff, not hardware related).
Does xinput list
list anything about a touchpad?
Any output for lsmod | grep hid
or lsmod | grep i2c
?
- Edited
As far as I know, there is no button/key that enable/disable the Touchpad in my machine (Lenovo X1C7). Only an UEFI/BIOS switch, which I deactivate and effectively disable the touchpad for other OS in the machine. I re-activate it, then the touchpad worked for the other OS, but not for KaOS.
I am using "5.7.2-1-next" and here are the outputs you sugested
xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ TPPS/2 Elan TrackPoint id=13 [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)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ Integrated Camera: Integrated C id=9 [slave keyboard (3)]
↳ Integrated Camera: Integrated I id=10 [slave keyboard (3)]
↳ sof-hda-dsp Headset Jack id=11 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=14 [slave keyboard (3)]
No mention of touchpad.
As for lsmod:
lsmod | grep hid
mac_hid 16384 0
i2c_hid 32768 0
hid 131072 1 i2c_hid
...
lsmod | grep i2c
i2c_algo_bit 16384 1 i915
i2c_i801 32768 0
i2c_hid 32768 0
hid 131072 1 i2c_hid
Since this change does not have any effect, I will revert it:
https://github.com/KaOSx/core/commit/1397b8a3076504712f1da95a4e43c6e4573415fe#diff-c3823a713c080ad6e13a46a541231695L3733
Could any of you test the last kernel known to work without issues for these touchpads? I uploaded on old 5.3 kernel for this (good to have linux-next installed, in case you have other issues booting with this kernel):
sudo pacman -U https://sourceforge.net/projects/kaosx/files/packages/linux-5.3.8-1-x86_64.pkg.tar.xz
and if you have linux-headers installed too:
sudo pacman -U https://sourceforge.net/projects/kaosx/files/packages/linux-headers-5.3.8-1-x86_64.pkg.tar.xz
- Edited
demm Could any of you test the last kernel known to work without issues for these touchpads?
In my case, a brand new Lenovo X1C7, I cannot see if the touchpad ever worked before in KaOS. I have only tested with kernels: 5.6.8-1 and 5.7.2-1, with results described in my posts before.
As suggested, I tried the kernel 5.3.8-1 and the "xinput list" and the "lsmod" looking for "hid" and "i2c" were exactly the same as posted before using the linux-next 5.7.2-1.
Here also the dmesg output in 5.3.8-1
Once again, I boot in the same machine using Ubuntu and run "xinput" and "lsmod" to try to find the drivers/devices names and I got the following (hope this will be useful):
user@UbuntuMachine:~$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SYNA8004:00 06CB:CD8B Mouse id=11 [slave pointer (2)]
⎜ ↳ SYNA8004:00 06CB:CD8B Touchpad id=12 [slave pointer (2)]
⎜ ↳ TPPS/2 Elan TrackPoint id=15 [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)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ Integrated Camera: Integrated C id=9 [slave keyboard (3)]
↳ Integrated Camera: Integrated I id=10 [slave keyboard (3)]
↳ sof-hda-dsp Headset Jack id=13 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=16 [slave keyboard (3)]
user@UbuntuMachine:~$ lsmod | grep hid
hid_multitouch 28672 0
mac_hid 16384 0
hid_generic 16384 0
i2c_hid 28672 0
hid 131072 3 i2c_hid,hid_multitouch,hid_generic
user@UbuntuMachine:~$ lsmod | grep i2c
i2c_algo_bit 16384 1 i915
i2c_i801 32768 0
i2c_hid 28672 0
hid 131072 3 i2c_hid,hid_multitouch,hid_generic
user@UbuntuMachine~$ uname -r
5.4.0-37-generic
It seems like these "hid-generic" and "hid-multitouch" drivers are related to the touchpad.
Do you have xf86-input-synaptics installed in Ubuntu? Please test linux-next 5.72 again, with that package added.
- Edited
The package xf86-intput-synaptics doesn't exist in the Ubuntu repository. There were other "synaptics" package matches but none of them were installed in Ubuntu (yet the touchpad worked perfectly there).
I tried KaOS linux-next 5.72 with the xf86-input-synaptics package added. Touchpad still not working. Even after hard rebooting the log outputs are the same as before
Just to follow up with my previous answer...
I have updated linux-next to the 5.7.4-1 and it remains the exact same outputs for xinput, dmesg and lsmod as I posted before for 5.7.2-1. The touchpad still not recognizable by KaOS.