Touchpad on the Acer Aspire Swift 113-31 does not work out of the box. Fedora 28, kernel 4.16.9. dmesg output is as follows: May 22 06:53:40 hyemi kernel: i2c_hid i2c-SYNA7DAB:00: i2c-SYNA7DAB:00 supply vdd not found, using dummy regulator May 22 06:53:45 hyemi kernel: i2c_hid i2c-SYNA7DAB:00: failed to reset device. May 22 06:53:51 hyemi kernel: i2c_hid i2c-SYNA7DAB:00: failed to reset device. May 22 06:53:58 hyemi kernel: i2c_hid i2c-SYNA7DAB:00: failed to reset device. May 22 06:54:04 hyemi kernel: i2c_hid i2c-SYNA7DAB:00: failed to reset device. May 22 06:54:05 hyemi kernel: i2c_hid i2c-SYNA7DAB:00: can't add hid device: -61 May 22 06:54:05 hyemi kernel: i2c_hid: probe of i2c-SYNA7DAB:00 failed with error -61 The BIOS in this laptop has the following setting: Touchpad: Basic|Advanced With this helpful help-text: "Please make sure i2C driver is installed before Advanced feature enabled. Otherwise, touchpad will be no function." As "no function" isn't ideal I tried "Basic". This changes the dmesg output to: May 22 09:17:26 hyemi kernel: psmouse serio4: synaptics: Your touchpad (PNP: SYN7db5 SYN1b00 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kernel.org. May 22 09:17:26 hyemi kernel: psmouse serio4: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2a1, caps: 0xf00223/0x840300/0x12e800/0x0, board id: 3217, fw id: 2314823 and so far it seems to work fine as a "psmouse" instead of a i2c device. I am not sure what, if anything, I am missing out on by not having the "advanced" (i2c) touchpad. Two finger scrolling seems to work fine. I suppose it's four finger scrolling or something. Regardless, I'm leaving this bug here since Advanced does not work and perhaps someone will care on a rainy day. Perhaps someone other hardware has the same touchpad without a "basic|advanced" setting and will have a problem. I have the technology so I can dump acpi or other information if it's somehow remotely useful, just tell me the commands required. From my personal use of this hardware it doesn't seem to matter.
This is a kernel bug, not a libinput bug, closing it here. I'm CC-ing Benjamin in case he has any good ideas, please do attach a dmesg though of the failed startup.
Just a quick note. For Synaptics devices, the "basic" mode only reports 2 full fingers with caveats when you start using more than 2. You'll also get a lower refresh rate over i2c. On I2C, you should have 5 fingers support with a decent refresh rate (8ms for the 5 fingers). I believe the issue is related to https://patchwork.kernel.org/patch/10408725/ There has been countless recent devices with a broken i2c-hid because of a misconfiguration in the i2c-designware driver. When you get a chance, it could be interesting to try a v4.18 kernel or a current released kernel with the patch backported. And as Peter mentioned, a full dmesg would be interesting to confirm.
Created attachment 139704 [details] dmesg with touchpad set to advanced and no function, 4.16.9-300.fc28.x86_64 incriminating dmesg evidence of boot with touchpad set to Advanced in BIOS and no touchpad function in X.
Created attachment 139705 [details] dmesg, bug fixed somehow, 4.17.0-0.rc6.git1 Touchpad in [Advanced] mode in BIOS appears to work fine with 4.17.0-0.rc6.git1. It worked on three cold boots in a row. It also works after suspend to RAM two times in a row. I see no reason to test further as it probably still works if I boot and/or suspend all day. Specific kernel is 4.17.0-0.rc6.git1.1.vanilla.knurd.1.fc28.x86_64 which is some kind of vanilla kernel git build with a Fedora stock kernel .config. The only thing changed between testing kernel 4.16.9 and 4.17.0-0.rc6.git1 was [Secure boot] to False in BIOS since this kernel is not signed and I'll have to blindly trust that this knurd guy didn't make it evil (he probably isn't). Bug is much likely resolved.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.