Bug 208547 - ELAN1205 touchpad is not working on ASUS G15
Summary: ELAN1205 touchpad is not working on ASUS G15
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: I2C (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-14 14:08 UTC by Alexei
Modified: 2020-09-06 16:38 UTC (History)
3 users (show)

See Also:
Kernel Version: 5.8.0-rc6
Tree: Mainline
Regression: No


Attachments
dmesg (108.48 KB, text/plain)
2020-07-14 14:08 UTC, Alexei
Details
dmidecode (10.22 KB, text/plain)
2020-07-14 14:08 UTC, Alexei
Details
input devices (6.50 KB, text/plain)
2020-07-14 14:09 UTC, Alexei
Details
5.8.0-rc6-1-mainline dmesg (90.60 KB, text/plain)
2020-07-21 05:15 UTC, Alexei
Details

Description Alexei 2020-07-14 14:08:16 UTC
Created attachment 290265 [details]
dmesg

Hello, I have a new Laptop since kernel 5.7.2-arch1-1. Now I'm using 5.8.0-rc5-mainline and the touchpad is still not working.
Laptop manufacturer: Asus
Model: ROG-Zephyrus-G15 GA502IV

BIOS fastboot is disabled.
No hardware issue with the touchpad. It works in Windows (have dual-boot)

It looks like kernel recognizes the touchpad but doesn't enable it.

# dmesg | grep -i elan
[ 4.830134] i2c_hid i2c-ELAN1205:00: supply vdd not found, using dummy regulator
[ 4.830150] i2c_hid i2c-ELAN1205:00: supply vddl not found, using dummy regulator 

No input device is added in /proc/bus/input/devices => no xinput device is present.
Comment 1 Alexei 2020-07-14 14:08:59 UTC
Created attachment 290267 [details]
dmidecode
Comment 2 Alexei 2020-07-14 14:09:18 UTC
Created attachment 290269 [details]
input devices
Comment 3 Alexei 2020-07-19 12:31:38 UTC
For some reason, I can't make "modprobe i2c_hid debug=1" debug messages to show. But adding 'i2c-hid.dyndbg=+p' kernel option added new message:

[    4.838769] i2c_hid i2c-ELAN1205:00: supply vdd not found, using dummy regulator
[    4.838783] i2c_hid i2c-ELAN1205:00: supply vddl not found, using dummy regulator
*[    4.838887] i2c_hid i2c-ELAN1205:00: nothing at this address: -121*

And want to add observation about udevadm monitor output while removing+adding i2c_hid module: 

KERNEL[398.302991] remove   /bus/i2c/drivers/i2c_hid (drivers)
KERNEL[398.303037] remove   /module/i2c_hid (module)
UDEV  [398.304991] remove   /bus/i2c/drivers/i2c_hid (drivers)
UDEV  [398.305579] remove   /module/i2c_hid (module)
KERNEL[398.369281] add      /module/i2c_hid (module)
KERNEL[398.369473] add      /devices/LNXSYSTM:00/LNXSYBUS:00/AMDI0010:03/ELAN1205:00/wakeup/wakeup50 (wakeup)
UDEV  [398.370121] add      /module/i2c_hid (module)
UDEV  [398.370769] add      /devices/LNXSYSTM:00/LNXSYBUS:00/AMDI0010:03/ELAN1205:00/wakeup/wakeup50 (wakeup)
KERNEL[398.370954] remove   /devices/LNXSYSTM:00/LNXSYBUS:00/AMDI0010:03/ELAN1205:00/wakeup/wakeup50 (wakeup)
KERNEL[398.371066] add      /bus/i2c/drivers/i2c_hid (drivers)
UDEV  [398.371942] remove   /devices/LNXSYSTM:00/LNXSYBUS:00/AMDI0010:03/ELAN1205:00/wakeup/wakeup50 (wakeup)
UDEV  [398.372218] add      /bus/i2c/drivers/i2c_hid (drivers)
Comment 4 Alexei 2020-07-21 05:15:04 UTC
Created attachment 290385 [details]
5.8.0-rc6-1-mainline dmesg

Upgraded to the 5.8.0-rc6-1-mainline. Still the same massage in dmesg.
Comment 5 Casey 2020-07-30 09:51:27 UTC
Same problem, upgrade to kernel 5.7.11, still not working.
Comment 6 Alexei 2020-08-31 08:08:38 UTC
Having the same error on the latest 5.9rc3 kernel.

How can I debug it? I did read some kernel documentation on i2c but it didn't came a long way for me. 

# hwinfo shows this data for ELAN:
  P: /devices/LNXSYSTM:00/LNXSYBUS:00/AMDI0010:03/ELAN1205:00
  L: 0
  E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/AMDI0010:03/ELAN1205:00
  E: SUBSYSTEM=acpi
  E: MODALIAS=acpi:ELAN1205:PNP0C50:
  E: USEC_INITIALIZED=5509997
  E: ID_VENDOR_FROM_DATABASE=ELAD srl

But i2c_hid module still reports 
[    5.611799] i2c_hid i2c-ELAN1205:00: nothing at this address: -121

So, I did try i2c-tools
# i2cdetect -l
i2c-3	i2c       	AMDGPU DM aux hw bus 0          	I2C adapter
i2c-1	i2c       	AMDGPU DM i2c hw bus 0          	I2C adapter
i2c-8	i2c       	NVIDIA i2c adapter 1 at 1:00.0  	I2C adapter
i2c-6	smbus     	SMBus PIIX4 adapter port 2 at 0b00	SMBus adapter
i2c-4	i2c       	NVIDIA GPU I2C adapter          	I2C adapter
i2c-2	i2c       	AMDGPU DM i2c hw bus 1          	I2C adapter
i2c-0	i2c       	Synopsys DesignWare I2C adapter 	I2C adapter
i2c-9	i2c       	NVIDIA i2c adapter 7 at 1:00.0  	I2C adapter
i2c-7	smbus     	SMBus PIIX4 adapter port 1 at 0b20	SMBus adapter
i2c-5	smbus     	SMBus PIIX4 adapter port 0 at 0b00	SMBus adapter


# i2cdetect -r -a 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0 using receive byte commands.
I will probe address range 0x00-0x7f.
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: 00 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

but i2cdump reports some strange data
# i2cdump -a 0 0x00
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x0, mode byte
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
10: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
20: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
30: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
40: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
50: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
60: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
70: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
80: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
90: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
a0: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
b0: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
c0: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
d0: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
e0: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????
f0: 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b 0b    ????????????????

Note You need to log in before you can comment on or make changes to this bug.