Bug 1634832 - Elantech touchpad has issues.
Summary: Elantech touchpad has issues.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 32
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-01 18:31 UTC by Evren Duman
Modified: 2021-05-11 13:42 UTC (History)
42 users (show)

Fixed In Version: kernel-5.11.19-300.fc34
Clone Of:
Environment:
Last Closed: 2021-05-11 13:42:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Xorg log under kernel 5.2.8; touchpad works (34.02 KB, text/plain)
2019-09-07 18:42 UTC, Steven Usdansky
no flags Details
Xorg log under kernel 5.2.9; touchpad does not work (33.05 KB, text/plain)
2019-09-07 18:42 UTC, Steven Usdansky
no flags Details

Description Evren Duman 2018-10-01 18:31:14 UTC
Description of problem:

Touchpad does not working any more. I don't know the exact kernel version that the problem has appeared first because i use mouse generally and i've noticed the issue so late.

Version-Release number of selected component (if applicable):

4.18.10-200.fc28.x86_64 #1 SMP Wed Sep 26 09:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


How reproducible:

Reboot 


Additional info:

$ dmesg | grep -i elan

[    2.013451] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
[    2.029917] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
[    2.046004] psmouse serio1: elantech: Elan sample query result 00, 23, c8
[    2.062395] psmouse serio1: elantech: Trying to set up SMBus access
[    2.062405] psmouse serio1: elantech: SMbus companion is not ready yet
[    2.116604] input: ETPS/2 Elantech TrackPoint as /devices/platform/i8042/serio1/input/input7
[    2.138207] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input5
[    7.171316] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
[    7.188138] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
[    7.204460] psmouse serio1: elantech: Elan sample query result 00, 23, c8
[    7.219067] psmouse serio1: elantech: Trying to set up SMBus access
[    7.226838] elan_i2c 6-0015: 6-0015 supply vcc not found, using dummy regulator
[    7.242918] elan_i2c 6-0015: failed to get resolution: -71
[    7.242969] elan_i2c: probe of 6-0015 failed with error -71




In the Arch forum they have a fix for the same problem but this fix is working just one time for me and after a reboot, it comes back to same status:

https://bugs.archlinux.org/task/59714


Temporary fix: 

sudo sh -c 'echo -n "elantech" > /sys/bus/serio/devices/serio1/protocol'

Comment 1 Evren Duman 2018-11-09 09:27:42 UTC
Problem still exists on Fedora 29 with the kernel 4.18.16-300.fc29.x86_64

Comment 2 Jeremy Cline 2018-12-03 17:30:20 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.
 
Fedora 29 has now been rebased to 4.19.5-300.fc29.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.

Comment 3 Evren Duman 2018-12-03 20:53:12 UTC
Unfortunately the problem still exists with kernel 4.19.5.300.fc29. 
 
kernel: elan_i2c 7-0015: failed to get resolution: -71
kernel: elan_i2c 7-0015: Dropping the link to regulator.0
kernel: elan_i2c: probe of 7-0015 failed with error -71

Comment 4 Evren Duman 2019-01-16 23:32:32 UTC
Same problem with the kernel 4.19.14.300.fc29.

Comment 5 Justin M. Forbes 2019-01-29 16:13:19 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs.

Fedora 29 has now been rebased to 4.20.5-200.fc29.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 6 Evren Duman 2019-01-30 20:04:26 UTC
Problem still exists on Fedora 29 with the kernel 4.20.4-200.fc29.

Comment 7 shawnbrown 2019-02-02 23:42:36 UTC
I have the same problem, myself (my touchpad device name is "ETPS/2 Elantech Touchpad"). I initially encountered this on Fedora 26. It was resolved (briefly) in Fedora 27 but returned in Fedora 28 through 29.

Here's the issue I filed at the time: bug 1477023

And here's an attachment 1307365 [details] showing the differences of the /proc/bus/input/devices on Fedora vs Ubuntu at the time.

Evren, thanks for keeping this issue alive.

Comment 8 shawnbrown 2019-02-03 00:43:10 UTC
I should add... The last kernel in Fedora that supported my Lenovo's "ETPS/2 Elantech Touchpad" was:

   4.18.19-100.fc27.x86_64

Comment 9 Evren Duman 2019-02-04 23:48:08 UTC
No fix with the current 4.20.5-200.fc29 kernel.

@shawnbrown thank you. It's quite annoying actually that waiting a fix for already working hardware before but the contributors have lots of work to do, so i can not complain, i wish i could understand the kernel c code and help to fix the problem.

Comment 10 Supreeth Raghuprakash 2019-03-15 19:33:33 UTC
I wish the kernel sources were made modular. There are thousands of engineers who are waiting to do small things, and yet the structure seems so complex and daunting. Could someone explain how we could start to analyse the problem? If we have to port an older driver into the latest kernel, how to get this patch over and run it on our existing linux (fedora) system?

Comment 11 Evren Duman 2019-07-26 09:06:17 UTC
Bug is still unfixed with the 5.1.19-300.fc30 kernel.

Comment 12 Evren Duman 2019-07-26 09:24:29 UTC
Additional info: 

$ journalctl --since today | grep elan
Tem 26 09:35:11  kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
Tem 26 09:35:11  kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
Tem 26 09:35:11  kernel: psmouse serio1: elantech: Elan sample query result 00, 23, c8
Tem 26 09:35:11  kernel: psmouse serio1: elantech: Trying to set up SMBus access
Tem 26 09:35:11  kernel: psmouse serio1: elantech: SMbus companion is not ready yet
Tem 26 09:35:17  kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
Tem 26 09:35:17  kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
Tem 26 09:35:17  kernel: psmouse serio1: elantech: Elan sample query result 00, 23, c8
Tem 26 09:35:17  kernel: psmouse serio1: elantech: Trying to set up SMBus access
Tem 26 09:35:17  kernel: elan_i2c 7-0015: 7-0015 supply vcc not found, using dummy regulator
Tem 26 09:35:17  kernel: elan_i2c 7-0015: failed to get resolution: -71
Tem 26 09:35:17  kernel: elan_i2c: probe of 7-0015 failed with error -71
Tem 26 11:54:17  kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
Tem 26 11:54:17  kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
Tem 26 11:54:17  kernel: psmouse serio1: elantech: Elan sample query result 00, 23, c8
Tem 26 11:54:17  kernel: psmouse serio1: elantech: Trying to set up SMBus access
Tem 26 11:54:17  kernel: psmouse serio1: elantech: SMbus companion is not ready yet
Tem 26 11:54:23  kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
Tem 26 11:54:23  kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
Tem 26 11:54:23  kernel: psmouse serio1: elantech: Elan sample query result 00, 23, c8
Tem 26 11:54:23  kernel: psmouse serio1: elantech: Trying to set up SMBus access
Tem 26 11:54:23  kernel: elan_i2c 6-0015: 6-0015 supply vcc not found, using dummy regulator
Tem 26 11:54:23  kernel: elan_i2c 6-0015: failed to get resolution: -5
Tem 26 11:54:23  kernel: elan_i2c: probe of 6-0015 failed with error -5
Tem 26 11:56:27  dracut[2297]: -rw-r--r--   1 root     root         4532 Feb 14 23:03 usr/lib/modules/5.1.19-300.fc30.x86_64/kernel/drivers/hid/hid-elan.ko.xz
Tem 26 11:56:48  kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
Tem 26 11:56:48  kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
Tem 26 11:56:48  kernel: psmouse serio1: elantech: Elan sample query result 00, 23, c8
Tem 26 11:56:48  kernel: psmouse serio1: elantech: Trying to set up SMBus access
Tem 26 11:56:48  kernel: psmouse serio1: elantech: SMbus companion is not ready yet
Tem 26 11:56:54  kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
Tem 26 11:56:54  kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
Tem 26 11:56:54  kernel: psmouse serio1: elantech: Elan sample query result 00, 23, c8
Tem 26 11:56:54  kernel: psmouse serio1: elantech: Trying to set up SMBus access
Tem 26 11:56:54  kernel: elan_i2c 6-0015: 6-0015 supply vcc not found, using dummy regulator
Tem 26 11:56:54  kernel: elan_i2c 6-0015: failed to get resolution: -5
Tem 26 11:56:54  kernel: elan_i2c: probe of 6-0015 failed with error -5



$ cat /sys/bus/serio/devices/serio0/firmware_id
PNP: LEN0071 PNP0303

Comment 13 Evren Duman 2019-07-26 09:26:36 UTC
Additional info: 

$ journalctl --since today | grep elan
Tem 26 09:35:11  kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
Tem 26 09:35:11  kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
Tem 26 09:35:11  kernel: psmouse serio1: elantech: Elan sample query result 00, 23, c8
Tem 26 09:35:11  kernel: psmouse serio1: elantech: Trying to set up SMBus access
Tem 26 09:35:11  kernel: psmouse serio1: elantech: SMbus companion is not ready yet
Tem 26 09:35:17  kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
Tem 26 09:35:17  kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
Tem 26 09:35:17  kernel: psmouse serio1: elantech: Elan sample query result 00, 23, c8
Tem 26 09:35:17  kernel: psmouse serio1: elantech: Trying to set up SMBus access
Tem 26 09:35:17  kernel: elan_i2c 7-0015: 7-0015 supply vcc not found, using dummy regulator
Tem 26 09:35:17  kernel: elan_i2c 7-0015: failed to get resolution: -71
Tem 26 09:35:17  kernel: elan_i2c: probe of 7-0015 failed with error -71
Tem 26 11:54:17  kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
Tem 26 11:54:17  kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
Tem 26 11:54:17  kernel: psmouse serio1: elantech: Elan sample query result 00, 23, c8
Tem 26 11:54:17  kernel: psmouse serio1: elantech: Trying to set up SMBus access
Tem 26 11:54:17  kernel: psmouse serio1: elantech: SMbus companion is not ready yet
Tem 26 11:54:23  kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
Tem 26 11:54:23  kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
Tem 26 11:54:23  kernel: psmouse serio1: elantech: Elan sample query result 00, 23, c8
Tem 26 11:54:23  kernel: psmouse serio1: elantech: Trying to set up SMBus access
Tem 26 11:54:23  kernel: elan_i2c 6-0015: 6-0015 supply vcc not found, using dummy regulator
Tem 26 11:54:23  kernel: elan_i2c 6-0015: failed to get resolution: -5
Tem 26 11:54:23  kernel: elan_i2c: probe of 6-0015 failed with error -5
Tem 26 11:56:27  dracut[2297]: -rw-r--r--   1 root     root         4532 Feb 14 23:03 usr/lib/modules/5.1.19-300.fc30.x86_64/kernel/drivers/hid/hid-elan.ko.xz
Tem 26 11:56:48  kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
Tem 26 11:56:48  kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
Tem 26 11:56:48  kernel: psmouse serio1: elantech: Elan sample query result 00, 23, c8
Tem 26 11:56:48  kernel: psmouse serio1: elantech: Trying to set up SMBus access
Tem 26 11:56:48  kernel: psmouse serio1: elantech: SMbus companion is not ready yet
Tem 26 11:56:54  kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
Tem 26 11:56:54  kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
Tem 26 11:56:54  kernel: psmouse serio1: elantech: Elan sample query result 00, 23, c8
Tem 26 11:56:54  kernel: psmouse serio1: elantech: Trying to set up SMBus access
Tem 26 11:56:54  kernel: elan_i2c 6-0015: 6-0015 supply vcc not found, using dummy regulator
Tem 26 11:56:54  kernel: elan_i2c 6-0015: failed to get resolution: -5
Tem 26 11:56:54  kernel: elan_i2c: probe of 6-0015 failed with error -5



$ cat /sys/bus/serio/devices/serio0/firmware_id
PNP: LEN0071 PNP0303


$ dmesg | grep -i elan
[    2.563107] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
[    2.580161] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
[    2.595214] psmouse serio1: elantech: Elan sample query result 00, 23, c8
[    2.611472] psmouse serio1: elantech: Trying to set up SMBus access
[    2.611478] psmouse serio1: elantech: SMbus companion is not ready yet
[    2.666947] input: ETPS/2 Elantech TrackPoint as /devices/platform/i8042/serio1/input/input7
[    2.696115] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input5
[    7.227461] audit: type=1400 audit(1564131412.790:34): avc:  denied  { read } for  pid=671 comm="systemd-sysv-ge" name="Elantec.sh" dev="dm-0" ino=787098 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0
[    7.227467] systemd-sysv-generator[671]: Failed to open /etc/rc.d/init.d/Elantec.sh: Permission denied
[    8.542359] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001)
[    8.558315] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10.
[    8.574976] psmouse serio1: elantech: Elan sample query result 00, 23, c8
[    8.593131] psmouse serio1: elantech: Trying to set up SMBus access
[    8.610603] elan_i2c 6-0015: 6-0015 supply vcc not found, using dummy regulator
[    8.622713] elan_i2c 6-0015: failed to get resolution: -5
[    8.622759] elan_i2c: probe of 6-0015 failed with error -5

Comment 14 Justin M. Forbes 2019-08-20 17:40:18 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs.

Fedora 30 has now been rebased to 5.2.9-200.fc30.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31.

If you experience different issues, please open a new bug report for those.

Comment 15 Joe Doss 2019-09-05 22:29:13 UTC
This is still an issue with Thinkpad T490s laptops.

kernel-5.2.11-200

$ cat /sys/bus/serio/devices/serio0/firmware_id
PNP: LEN0071 PNP0303

Comment 16 Steven Usdansky 2019-09-07 18:42:10 UTC
Created attachment 1612709 [details]
Xorg log under kernel 5.2.8; touchpad works

Comment 17 Steven Usdansky 2019-09-07 18:42:53 UTC
Created attachment 1612710 [details]
Xorg log under kernel 5.2.9; touchpad does not work

Comment 18 Steven Usdansky 2019-09-07 19:19:35 UTC
Xorg logs are for FC30 kernels 5.2.8 and 5.2.9 on HP Stream 14 with Elantech touchpad. Issue persists with  kernel 5.3.0-0.rc6.git0.1.fc31.x86_64.

Possibly related to changes to Elantech touchpad handling in kernel 5.2.9?  commit 883a2a80f79ca5c0c105605fafabd1f3df99b34c upstream.

Comment 19 Jehú Herrera 2019-09-08 20:29:15 UTC
I have the same issue with kernel 5.2.11-200.fc30.x86_64 on an HP Notebook with Fedora 30 and Arch Linux

Dmesg:
dmesg | grep elan
[    4.899821] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5e0f01)
[    4.916320] psmouse serio1: elantech: Synaptics capabilities query result 0x70, 0x16, 0x0a.
[    4.932718] psmouse serio1: elantech: Elan sample query result 0b, 01, a7
[    4.949777] psmouse serio1: elantech: Trying to set up SMBus access
[    4.949796] psmouse serio1: elantech: SMbus companion is not ready yet
[   28.377627] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5e0f01)
[   28.392595] psmouse serio1: elantech: Synaptics capabilities query result 0x70, 0x16, 0x0a.
[   28.407576] psmouse serio1: elantech: Elan sample query result 0b, 01, a7
[   28.422583] psmouse serio1: elantech: Trying to set up SMBus access
[   28.487962] elan_i2c 9-0015: 9-0015 supply vcc not found, using dummy regulator
[   28.497556] elan_i2c 9-0015: failed to get product ID: -6
[   28.539986] elan_i2c 9-0015: failed to get product ID: -71
[   28.582124] elan_i2c 9-0015: failed to get product ID: -71
[   28.613575] elan_i2c: probe of 9-0015 failed with error -71

Journalctl:
journalctl --since today | grep elan
sep 08 07:51:44 localhost.localdomain kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5e0f01)
sep 08 07:51:44 localhost.localdomain kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x70, 0x16, 0x0a.
sep 08 07:51:44 localhost.localdomain kernel: psmouse serio1: elantech: Elan sample query result 0b, 01, a7
sep 08 07:51:44 localhost.localdomain kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5e0f01)
sep 08 07:51:44 localhost.localdomain kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x70, 0x16, 0x0a.
sep 08 07:51:44 localhost.localdomain kernel: psmouse serio1: elantech: Elan sample query result 0b, 01, a7
sep 08 14:22:26 hp-notebook dracut[9711]: -rw-r--r--   1 root     root         4532 Feb 14  2019 usr/lib/modules/5.2.11-200.fc30.x86_64/kernel/drivers/hid/hid-elan.ko.xz
sep 08 09:25:02 hp-notebook kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5e0f01)
sep 08 09:25:02 hp-notebook kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x70, 0x16, 0x0a.
sep 08 09:25:02 hp-notebook kernel: psmouse serio1: elantech: Elan sample query result 0b, 01, a7
sep 08 09:25:02 hp-notebook kernel: psmouse serio1: elantech: Trying to set up SMBus access
sep 08 09:25:02 hp-notebook kernel: psmouse serio1: elantech: SMbus companion is not ready yet
sep 08 14:25:18 hp-notebook kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5e0f01)
sep 08 14:25:18 hp-notebook kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x70, 0x16, 0x0a.
sep 08 14:25:18 hp-notebook kernel: psmouse serio1: elantech: Elan sample query result 0b, 01, a7
sep 08 14:25:18 hp-notebook kernel: psmouse serio1: elantech: Trying to set up SMBus access
sep 08 14:25:18 hp-notebook kernel: elan_i2c 9-0015: 9-0015 supply vcc not found, using dummy regulator
sep 08 14:25:18 hp-notebook kernel: elan_i2c 9-0015: failed to get product ID: -71
sep 08 14:25:18 hp-notebook kernel: elan_i2c 9-0015: failed to get product ID: -71
sep 08 14:25:18 hp-notebook kernel: elan_i2c 9-0015: failed to get product ID: -71
sep 08 14:25:18 hp-notebook kernel: elan_i2c: probe of 9-0015 failed with error -71
sep 08 09:30:15 hp-notebook kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5e0f01)
sep 08 09:30:15 hp-notebook kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x70, 0x16, 0x0a.
sep 08 09:30:15 hp-notebook kernel: psmouse serio1: elantech: Elan sample query result 0b, 01, a7
sep 08 09:30:15 hp-notebook kernel: psmouse serio1: elantech: Trying to set up SMBus access
sep 08 09:30:15 hp-notebook kernel: psmouse serio1: elantech: SMbus companion is not ready yet
sep 08 14:30:31 hp-notebook kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5e0f01)
sep 08 14:30:31 hp-notebook kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x70, 0x16, 0x0a.
sep 08 14:30:31 hp-notebook kernel: psmouse serio1: elantech: Elan sample query result 0b, 01, a7
sep 08 14:30:31 hp-notebook kernel: psmouse serio1: elantech: Trying to set up SMBus access
sep 08 14:30:32 hp-notebook kernel: elan_i2c 9-0015: 9-0015 supply vcc not found, using dummy regulator
sep 08 14:30:32 hp-notebook kernel: elan_i2c 9-0015: failed to get product ID: -6
sep 08 14:30:32 hp-notebook kernel: elan_i2c 9-0015: failed to get product ID: -71
sep 08 14:30:32 hp-notebook kernel: elan_i2c 9-0015: failed to get product ID: -71
sep 08 14:30:32 hp-notebook kernel: elan_i2c: probe of 9-0015 failed with error -71
sep 08 09:35:29 localhost.localdomain kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5e0f01)
sep 08 09:35:29 localhost.localdomain kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x70, 0x16, 0x0a.
sep 08 09:35:29 localhost.localdomain kernel: psmouse serio1: elantech: Elan sample query result 0b, 01, a7
sep 08 10:02:39 hp-notebook kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5e0f01)
sep 08 10:02:39 hp-notebook kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x70, 0x16, 0x0a.
sep 08 10:02:39 hp-notebook kernel: psmouse serio1: elantech: Elan sample query result 0b, 01, a7
sep 08 10:02:39 hp-notebook kernel: psmouse serio1: elantech: Trying to set up SMBus access
sep 08 10:02:39 hp-notebook kernel: psmouse serio1: elantech: SMbus companion is not ready yet
sep 08 15:03:00 hp-notebook kernel: psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5e0f01)
sep 08 15:03:00 hp-notebook kernel: psmouse serio1: elantech: Synaptics capabilities query result 0x70, 0x16, 0x0a.
sep 08 15:03:00 hp-notebook kernel: psmouse serio1: elantech: Elan sample query result 0b, 01, a7
sep 08 15:03:00 hp-notebook kernel: psmouse serio1: elantech: Trying to set up SMBus access
sep 08 15:03:00 hp-notebook kernel: elan_i2c 9-0015: 9-0015 supply vcc not found, using dummy regulator
sep 08 15:03:00 hp-notebook kernel: elan_i2c 9-0015: failed to get product ID: -6
sep 08 15:03:00 hp-notebook kernel: elan_i2c 9-0015: failed to get product ID: -71
sep 08 15:03:00 hp-notebook kernel: elan_i2c 9-0015: failed to get product ID: -71
sep 08 15:03:00 hp-notebook kernel: elan_i2c: probe of 9-0015 failed with error -71


THIS WORK TO ME:
Add this kernel parameter to /etc/default/grub:
psmouse.elantech_smbus=0

Comment 20 Steven Usdansky 2019-09-09 11:55:10 UTC
Adding kernel parameter psmouse.elantech_smbus=0 worked for me too. Thanks.

Comment 21 Jiannan Liu 2019-10-01 15:10:44 UTC
The kernel parameter psmouse.elantech_smbus=0 works.

Comment 22 Einer Petersen 2019-10-17 14:46:14 UTC
Thank You Jim Smith!!!!!!!

This also worked for me :-)

Machine: MSI GS63
Touchpad: Elantech 1200
Kernel: 5.3.5-200.fc30.x86_64 #1 SMP Tue Oct 8 12:41:15 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux




Einer

Comment 23 FH 2019-10-24 08:01:42 UTC
Elan Trackpoint and Touchpad did break on Thinkpad P52 when Fedora 30 moved from kernel 5.2.18 to 5.3.5 / 5.3.6.
psmouse.elantech_smbus=0 successfully circumvents this regression. Thanks for this hint !!!!

Comment 24 ThinkPad 2019-10-30 03:24:51 UTC
Thank you Jehú Herrera. Adding the kernel param from Comment 19 worked. 

ThinkPad X390
Kernel: 5.3.7-301
Fedora 31

Last kernel version to have the trackpoint or trackpad working: 
Kernel: 5.2.18-200
Fedora 30

Comment 25 Jehú Herrera 2019-11-12 04:03:13 UTC
Hey guys, my touchpad its working without the kernel parameter in Fedora 31 with kernel 5.3.8-300.fc31.x86_64, upgrade your to fedora 31 or update your kernel to 5.3.8

Comment 26 Jehú Herrera 2019-11-12 04:05:58 UTC
(In reply to Jehú Herrera from comment #25)
> Hey guys, my touchpad its working without the kernel parameter in Fedora 31
> with kernel 5.3.8-300.fc31.x86_64, upgrade to fedora 31 or update your
> kernel to 5.3.8

Comment 27 Cait Macleod 2019-12-02 01:14:30 UTC
Hi folks,

My Thinkpad T490s touchpad  is still seeing touchpad issues even after after updating to Fedora 31 kernel 5.3.11-300.fc31.x86_64.

It initially worked when I installed Fedora 30 with kernel-5.0.9-301.fc30.x86_64, then broke when I upgraded to kernel-5.3.8-200.fc30.x86_64.

Trying the kernel setting recommended above does resolve the issue though, so thanks for the assist!

Comment 28 Evren Duman 2020-01-08 22:14:46 UTC
For Thinkpad L480, the issue has been solved with F31 Beta. It's been a while and i couldn't find the exact kernel version that F31 Beta has released with but the touchpad works well with all kernels from Beta to current 5.3.16-300.fc31.

Comment 29 Badre 2020-01-13 22:34:21 UTC
Just installed Fedora 30 on a new Lenovo T490s and did not see the issue with kernel 5.0.9-301.fc30.x86_64. However after upgrading kernel to 5.4.7-100.fc30.x86_64, the touchpad no longer responds. Note that I have tried adding 'psmouse.elantech_smbus=0' to /etc/default/grub but that did not seem to help. I was only able to resolve the issue by reverting to the earlier kernel version.

Comment 30 Hans de Goede 2020-01-14 09:17:53 UTC
@Badre, have you tried doing a "cat /proc/cmdline" after changing the /etc/default/grub file to verify that the 'psmouse.elantech_smbus=0' was actually passed to the kernel ?

Just editing that file is not enough, you need to also run "grub2-mkconfig -o /etc/grub2-efi.cfg" on EFI systems or "grub2-mkconfig -o /etc/grub2.cfg" on systems using legacy / classic BIOS boot.

Because of this it is a good idea to always verify if you have successfully passed the kernel commandline option in question by doing "cat /proc/cmdline" after rebooting.

Comment 31 Badre 2020-01-15 14:41:52 UTC
Thank you for the clarification Hans. I rebooted after changing /etc/default/grub but did not check /proc/cmdline. I will try the procedure that you have provided once I get a chance to upgrade.

Comment 32 Randy Barlow 2020-01-15 19:32:26 UTC
I like to use grubby to set the cmdline because it's a bit simpler. There's a post here describing how to use it:

https://fedoramagazine.org/setting-kernel-command-line-arguments-with-fedora-30/

Comment 33 Maros Kopec 2020-02-17 11:54:51 UTC
Hello,

no issue on Fedora 31. 

Laptop: T490s
Kernel: 5.4.18-200
Fedora 31


However I was not able to use touchpad (or trackpoint) on Live Media created by Fedora Media Writer. After the installation the issues were still present. Running 'dnf upgrade' resolved all issues.

Fedora Media Writer: mediawriter-4.1.4-3.fc31.x86_64

Comment 34 Justin M. Forbes 2020-03-03 16:25:07 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs.

Fedora 31 has now been rebased to 5.5.7-200.fc31.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32.

If you experience different issues, please open a new bug report for those.

Comment 35 Evren Duman 2020-03-05 08:01:01 UTC
With 5.5.7-200.fc31 kernel, trackpoint and it's three button are working well. Touchpad also works mostly but left and right buttons under the touchpad don't respond.

Comment 36 Bruce Petrie 2020-04-10 03:31:23 UTC
On Fedora 30, Samsung series 5 laptop w/ ET PS/2 touchpad was working just fine. Did an upgrade to Fedora 31, tapping suddenly stopped working. Mouse movement, two finger scrolling, etc still worked just fine.

searching for advice, found following:

Made sure xorg-x11-drv-libinput was installed, it was already there.

$ cd /etc/X11/xorg.conf.d
$ cat 40-libinput.conf 
Section "InputClass"
        Identifier "libinput touchpad catchall"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Driver "libinput"
        Option "Tapping" "on"
EndSection

reboot and tapping works again. Hopes this helps someone, lost several hours looking for this solution.

Comment 37 Konrad Kleine 2020-04-24 11:23:54 UTC
After rebooting my system T490s to the new kernel (with no other changes) I no longer have the problems that my trackball and touchpad don't work.

kkleine@work ~$ uname -a
Linux work 5.5.17-200.fc31.x86_64 #1 SMP Mon Apr 13 15:29:42 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

kkleine@work ~$ lsb_release -a
LSB Version:	:core-4.1-amd64:core-4.1-noarch
Distributor ID:	Fedora
Description:	Fedora release 31 (Thirty One)
Release:	31
Codename:	ThirtyOne

See also BZ1773879#c12

Comment 38 Ricardo Rodriguez 2020-07-07 02:31:54 UTC
The same problem is on fedora 32, not working the fix with grub, the kernel that has an intermient bug/issue.\

➜  ~ sudo dmidecode | grep -A 9 "System Information"
System Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Product Name: ROG Zephyrus G15 GA502IV_GA502IV
	Version: 1.0       
	Serial Number: XXXXXXXX
	UUID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXX
	Wake-up Type: Power Switch
	SKU Number:  
	Family: ROG Zephyrus G15

➜  ~  uname -a
Linux ryzen 5.7.6-201.fc32.x86_64 #1 SMP Mon Jun 29 15:15:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

➜  ~  lsb_release -a
LSB Version:	:core-4.1-amd64:core-4.1-noarch
Distributor ID:	Fedora
Description:	Fedora release 32 (Thirty Two)
Release:	32
Codename:	ThirtyTwo


output when is working:
➜  ~ xinput list 
⎡ Virtual core pointer                      id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ PixArt Lenovo USB Optical Mouse           id=11   [slave  pointer  (2)]
⎜   ↳ ASUSTeK Computer Inc. N-KEY Device Consumer Control   id=14   [slave  pointer  (2)]
⎜   ↳ ELAN1205:00 04F3:30E9 Mouse               id=15   [slave  pointer  (2)]
⎜   ↳ ELAN1205:00 04F3:30E9 Touchpad            id=16   [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)]
    ↳ ASUSTeK Computer Inc. N-KEY Device        id=12   [slave  keyboard (3)]
    ↳ ASUSTeK Computer Inc. N-KEY Device        id=13   [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                          id=17   [slave  keyboard (3)]
    ↳ ASUSTeK Computer Inc. N-KEY Device Consumer Control   id=18   [slave  keyboard (3)]
➜  ~


Outpupt not (not working)
➜  ~ xinput list
⎡ Virtual core pointer                      id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ PixArt Lenovo USB Optical Mouse           id=11   [slave  pointer  (2)]
⎜   ↳ ASUSTeK Computer Inc. N-KEY Device Consumer Control   id=14   [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)]
    ↳ ASUSTeK Computer Inc. N-KEY Device        id=12   [slave  keyboard (3)]
    ↳ ASUSTeK Computer Inc. N-KEY Device        id=13   [slave  keyboard (3)]
    ↳ Asus WMI hotkeys                          id=15   [slave  keyboard (3)]
    ↳ ASUSTeK Computer Inc. N-KEY Device Consumer Control   id=16   [slave  keyboard (3)]



Output working
➜  ~ dmesg | grep -i elan
[    2.044809] i2c_hid i2c-ELAN1205:00: supply vdd not found, using dummy regulator
[    2.044820] i2c_hid i2c-ELAN1205:00: supply vddl not found, using dummy regulator
[    2.065285] input: ELAN1205:00 04F3:30E9 Mouse as /devices/platform/AMDI0010:03/i2c-0/i2c-ELAN1205:00/0018:04F3:30E9.0002/input/input6
[    2.065375] input: ELAN1205:00 04F3:30E9 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c-ELAN1205:00/0018:04F3:30E9.0002/input/input7
[    2.065510] hid-generic 0018:04F3:30E9.0002: input,hidraw1: I2C HID v1.00 Mouse [ELAN1205:00 04F3:30E9] on i2c-ELAN1205:00
[    2.158031] input: ELAN1205:00 04F3:30E9 Mouse as /devices/platform/AMDI0010:03/i2c-0/i2c-ELAN1205:00/0018:04F3:30E9.0002/input/input8
[    2.158135] input: ELAN1205:00 04F3:30E9 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c-ELAN1205:00/0018:04F3:30E9.0002/input/input9
[    2.158216] hid-multitouch 0018:04F3:30E9.0002: input,hidraw1: I2C HID v1.00 Mouse [ELAN1205:00 04F3:30E9] on i2c-ELAN1205:00

Output not working
➜  ~ dmesg | grep -i elan
[    0.000000] Command line: BOOT_IMAGE=(hd1,gpt3)/vmlinuz-5.7.6-201.fc32.x86_64 root=/dev/mapper/fos--live-root ro resume=/dev/mapper/fos--live-swap rd.lvm.lv=fos-live/root rd.lvm.lv=fos-live/swap rhgb quiet systemd.unified_cgroup_hierarchy=0 psmouse.elantech_smbus=0
[    0.165677] Kernel command line: BOOT_IMAGE=(hd1,gpt3)/vmlinuz-5.7.6-201.fc32.x86_64 root=/dev/mapper/fos--live-root ro resume=/dev/mapper/fos--live-swap rd.lvm.lv=fos-live/root rd.lvm.lv=fos-live/swap rhgb quiet systemd.unified_cgroup_hierarchy=0 psmouse.elantech_smbus=0
[    2.049689] i2c_hid i2c-ELAN1205:00: HID over i2c has not been provided an Int IRQ
[    2.049801] i2c_hid: probe of i2c-ELAN1205:00 failed with error -22

Comment 39 Ricardo Rodriguez 2020-07-10 17:30:08 UTC
a Workarroung if your kernel detects the i2c_hid elan. but works in one time and another not.

Here it is for manual test:

sudo rmmod i2c_hid
sudo modprobe i2c_hid

in a script using systemd 

$ cat touchpad-asus-i2c_elan.bash

#!/usr/bin/env bash
#!/usr/bin/env bash

_script_0="/usr/bin/touchpad_asus.bash"
_daemon_0="touchpad_asus.service"
_daemon_path_0="/lib/systemd/system/touchpad_asus.service"
_shell_0="/bin/bash"

sudo bash -c "cat > ${_script_0}" << EOF
#!/usr/bin/env bash
sudo rmmod i2c_hid
sudo modprobe i2c_hid
EOF

sudo chmod +x ${_script_0}

sudo bash -c "cat > ${_daemon_path_0}" << EOF
[Unit]
Description=Touchpad elan i2c_hid work-arround-fix

[Service]
Type=simple
ExecStart=${_shell_0} ${_script_0}

[Install]
WantedBy=multi-user.target
EOF

sudo systemctl daemon-reload && sudo systemctl start ${_daemon_0} && \
    sudo systemctl enable ${_daemon_0} && sudo systemctl status ${_daemon_0}

Comment 40 Evren Duman 2020-07-30 13:22:39 UTC
For L480 from 5.5.7-200.fc31 to the current 5.7.10-201.fc32, touchpad works well except click areas at the bottom corners.

Comment 41 Luke Jones 2021-04-04 04:25:43 UTC
A number of us who have ASUS laptops and similar touchpad model are requiring the `amd_pinctrl` module to be built in to the kernel by default to solve this.

Is it at all possible to have this be the default configuration for this module?

Comment 42 Bill Dietrich 2021-04-28 17:07:30 UTC
Similar bug (or at least same workaround works) on Fedora 34 on a KDE Slimbook II laptop, which does NOT have an Elantech touchpad as far as I can tell.

Usually after a cold boot, the mouse-cursor will not appear, and the OS will say there are no mouse or touchpad devices detected.  Usually after a restart (warm reboot), mouse and touchpad will work fine.

Workaround when mouse and touchpad are not detected: do "sudo rmmod i2c_hid && sudo modprobe i2c_hid".

Never saw this problem on Kubuntu 20.10 (using X).  This is my first day running Fedora 34 (using Wayland).

Another user says (https://pay.reddit.com/r/Fedora/comments/n0cz4g/fedora_34_mouse_and_touchpad_not_recognized_after/gw6jgl4/) he's seen this problem on ASUS laptop using various releases of Fedora with kernels 5.5 and above, at least.  My Kubuntu distro was using kernel 5.8; now Fedora 34 is using kernel 5.11.

I can't figure out what brand of touchpad I have.    "dmesg | grep input" shows:

	[    0.643596] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
	[    0.643622] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
	[    0.643644] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2
	[    0.643664] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
	[    0.698183] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
	[    1.258997] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1e/LNXVIDEO:00/input/input5
	[    1.395194] input: UNIW0001:00 093A:0255 Mouse as /devices/platform/AMDI0010:02/i2c-0/i2c-UNIW0001:00/0018:093A:0255.0001/input/input6
	[    1.395318] input: UNIW0001:00 093A:0255 Touchpad as /devices/platform/AMDI0010:02/i2c-0/i2c-UNIW0001:00/0018:093A:0255.0001/input/input7
	[    1.395398] hid-generic 0018:093A:0255.0001: input,hidraw0: I2C HID v1.00 Mouse [UNIW0001:00 093A:0255] on i2c-UNIW0001:00
	[    1.455947] input: UNIW0001:00 093A:0255 Mouse as /devices/platform/AMDI0010:02/i2c-0/i2c-UNIW0001:00/0018:093A:0255.0001/input/input8
	[    1.456039] input: UNIW0001:00 093A:0255 Touchpad as /devices/platform/AMDI0010:02/i2c-0/i2c-UNIW0001:00/0018:093A:0255.0001/input/input9
	[    1.456114] hid-multitouch 0018:093A:0255.0001: input,hidraw0: I2C HID v1.00 Mouse [UNIW0001:00 093A:0255] on i2c-UNIW0001:00
	[   11.919619] input: PC Speaker as /devices/platform/pcspkr/input/input10
	[   12.150888] input: HD Webcam: HD Webcam as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3:1.0/input/input11
	[   12.171941] input: HD Webcam: IR Camera as /devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-3/1-3:1.2/input/input12
	[   12.262649] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:04:00.1/sound/card0/input13
	[   12.324708] snd_hda_codec_realtek hdaudioC1D0:    inputs:
	[   12.361571] input: HD-Audio Generic Mic as /devices/pci0000:00/0000:00:08.1/0000:04:00.6/sound/card1/input14
	[   12.361649] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:04:00.6/sound/card1/input15

I don't see any option in INXI to show input devices.

Comment 43 Gustavo Alves 2021-04-28 19:10:17 UTC
Hello,

I have a Lenovo S145 laptop with Ryzen 3700u CPU and the same happens. Sometimes the touchpad works and sometimes it doesn't (although the mouse always seem to work). This doesn't happen when using the Fedora Installer Live Image.

I've tried the workaround stated by #c42 (Bill) and it temporarily fixes the problem.

Comment 44 Gustavo Alves 2021-04-28 19:15:24 UTC
(In reply to Gustavo Alves from comment #43)
> Hello,
> 
> I have a Lenovo S145 laptop with Ryzen 3700u CPU and the same happens.
> Sometimes the touchpad works and sometimes it doesn't (although the mouse
> always seem to work). This doesn't happen when using the Fedora Installer
> Live Image.
> 
> I've tried the workaround stated by #c42 (Bill) and it temporarily fixes the
> problem.

I forgot to write here, but my touchpad isn't Elantech but Synaptics TM3336-004 according to dmesg.

Comment 45 Bill Dietrich 2021-04-28 19:24:59 UTC
(In reply to Gustavo Alves from comment #43)

Thanks for the comment, that reminded me of a couple of things I forgot to say:

- yes, that workaround only works until next boot

- I had same problem in Live Installer (booted from USB) as I do now with the installed system (booted from SSD)

- I'm using KDE on Fedora 34

Comment 46 Bill Dietrich 2021-04-29 11:12:13 UTC
Person whose reddit comment I linked to previously said this:

"I think this is an issue with the AMD 4/5xxx series ... Supposedly the issue is that sometimes i2c_hid loads before pinctrl_amd. You could build pinctrl_amd into the kernel or use a custom kernel that has it."

My system has an AMD 4800H CPU.

Comment 47 Fedora Program Management 2021-04-29 15:54:38 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 48 Hans de Goede 2021-05-06 14:02:38 UTC
(In reply to Luke Jones from comment #41)
> A number of us who have ASUS laptops and similar touchpad model are
> requiring the `amd_pinctrl` module to be built in to the kernel by default
> to solve this.
> 
> Is it at all possible to have this be the default configuration for this
> module?

Thank you for providing this info, that is very useful to know.

I've submitted 2 merge-requests to make amd_pinctrl builtin from now on:

1. For the rawhide kernels:
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1112

2. For the upcoming Fedora 33+ 5.12 kernel builds:
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1114


I've also started a test/scratch build of the latest 5.11.18 kernel with amd_pinctrl builtin, which you can use until the 5.12 kernel becomes available.

This is building here atm:
https://koji.fedoraproject.org/koji/taskinfo?taskID=67362080

This build should be finished in a couple of hours, here are some generic instructions for directly installing a kernel from koji (the Fedora builtsystem) :
https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt

Note since this is not an official build, it is not signed, so you need to disable secure-boot to boot this kernel. Signed 5.12 builds should show up soonish (for the upcoming 5.12 kernel test day).

Comment 49 Justin M. Forbes 2021-05-06 16:35:23 UTC
Since there will still be a couple more 5.11 builds (I expect 5.11.19 tomorrow), I went ahead and cherry-picked that commit to the fedora-5.11 branch and it should end up in 5.11.19 and newer kernels.

Comment 50 Hans de Goede 2021-05-06 20:01:41 UTC
(In reply to Justin M. Forbes from comment #49)
> Since there will still be a couple more 5.11 builds (I expect 5.11.19
> tomorrow), I went ahead and cherry-picked that commit to the fedora-5.11
> branch and it should end up in 5.11.19 and newer kernels.

Great, thank you!

Comment 51 Hans de Goede 2021-05-11 13:42:04 UTC
The amd_pinctrl is builtin starting with the kernel-5.11.19-300.fc34 kernel which is available now, so I'm closing this.

Feel free to re-open if you are still seeing issues with kernel-5.11.19-300.fc34 or newer.


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