Hi Benjamin, > Why do always people want to blacklist those drivers when they have a good chance to make their device working? My apologies. I wasn't very clear. My previous dmesg and other outputs were done without anything blacklisted. I only did blacklisting in an entirely separate endeavor based on several things I'd read that were workarounds for older Elantech touchpads. The good news is, I managed to get Kernel 4.17 RC 5 up and running last night. The bad news is, the touchpad was still not detected. Here is the /proc/version info: Linux version 4.17.0-041700rc5-generic (kernel@tangerine) (gcc version 7.3.0 (Ubuntu 7.3.0-18ubuntu2)) #201805132030 SMP Mon May 14 00:32:50 UTC 2018 dmesg and acpidump output are attached in the zip file "kernel_4.17_RC5_report.zip" at the bottom comment of the Launchpad bug report here: https://bugs.launchpad.net/ubuntu/cosmic/+source/linux/+bug/1770862 Thank you for your help! On Wed, May 16, 2018 at 2:58 AM, Benjamin Tissoires <benjamin.tissoires@xxxxxxxxx> wrote: > Hi, > > On Tue, May 15, 2018 at 5:58 AM, Were Turtle <wereturtledev@xxxxxxxxx> wrote: >> [1.] One line summary of the problem: >> ASUS GU501GM Elantech touchpad not detected >> >> [2.] Full description of the problem/report: >> The touchpad on the new ASUS GU501GM (the junior Zephyrus M that is a >> Best Buy exclusive) does not seem to be detected whatsoever with >> "xinput list". Windows 10 device manager shows the touchpad as >> ELAN:1201, HID_DEVICE:00FF1006. I've tried various combinations of >> i8042.* kernel parameters, as well as psmouse.proto=bare and different >> combinations for acpi_osi, but to no avail. I've also tried >> blacklisting i2c_hid and hid_multitouch. I've tried the mainstream > > Why do always people want to blacklist those drivers when they have a > good chance to make their device working? > > There are multiple reports of issues with recent Asus laptops. For instance: > https://www.spinics.net/lists/linux-input/msg56193.html > https://bugzilla.redhat.com/show_bug.cgi?id=1510649 > > and others are related to ELAN1200 devices that are not enumerated > correctly by i2c-hid: > https://bugzilla.redhat.com/show_bug.cgi?id=1543769 > > The reason in the latter case is because of the IRQ pins that are not > correctly mapped IIRC. It should have been fixed in a v4.17-rc kernel > though. > > Could you provide a full dmesg without any blacklisted driver so we > see if there is an error somewhere? > > Also could you provide the output of acpidump as root so we have a > better idea on how the touchpad is declared in the DSDT. > > Cheers, > Benjamin > >> kernel 4.16.7, also to no avail. The latest release candidates (#4 and >> #5) for 4.17 and 4.16.8 would not let me start X, though I noticed no >> touchpad miracle while I was in the SDDM login screen (I'm on Kubuntu >> 18.04). (Sorry, I am too inexperienced to figure out why X won't >> start on newer mainline kernels. I was sure to uninstall the nvidia >> drivers before installing them.) >> >> [3.] Keywords (i.e., modules, networking, kernel): >> >> [4.] Kernel version (from /proc/version): >> >> Linux version 4.16.7-041607-lowlatency (kernel@tangerine) (gcc version >> 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #201805021131 SMP PREEMPT Wed May 2 >> 15:44:57 UTC 2018 >> >> [5.] Output of Oops.. message >> N/A >> >> [6.] A small shell script or example program which triggers the >> problem (if possible) >> N/A >> >> [X.] Other notes, patches, fixes, workarounds: >> Please see all the "xinput list", dmesg, devices, and Xorg.0.log >> outputs attached at >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770862 >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-input" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
