Created attachment 1243612 [details]
Description of problem:
The touchpad doesn't work.
I've seen some reports online that this touchpad may be connected via i2c instead of usb.
I'm running kernel 4.9.4-201.fc25.x86_64
NOTE, the touchscreen does work.
Also note, to get the kernel booting at all, I had to pass "acpi=noirq" to the kernel command line.
I'm attaching lsusb/lspci/dmesg output.
Any other information I can provide that would be useful?
Created attachment 1243613 [details]
Created attachment 1243614 [details]
Can you attach the output of acpidump (as root) also. I want to check if the device is enumerated in the DSDT.
Created attachment 1244295 [details]
acpidump ascii output
Here's the dump. Thanks for taking a look at this.
Thanks for the logs. So it appears the touchpad is connected with HID over I2C, but the device is not enumerated. The problem is that the I2C adapater is on the PCI0 bus, meaning that the adapter just failed at loading. The lspci output shows that you are using intel_lpss_pci for those adapter, and the dmesg shows that they are failing at probing:
[ 4.195021] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
[ 4.195031] intel-lpss 0000:00:15.0: can't find IRQ for PCI INT A; please try using pci=biosirq
[ 4.195065] intel-lpss: probe of 0000:00:15.0 failed with error -22
[ 4.207148] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002)
[ 4.207159] intel-lpss 0000:00:15.1: can't find IRQ for PCI INT B; please try using pci=biosirq
[ 4.207182] intel-lpss: probe of 0000:00:15.1 failed with error -22
So please try booting with pci=biosirq as mentioned, and if it still doesn't help, we might be missing a better IRQ support for Skylake here. In that case, could you try the v4.10-rc from the Fedora Rawhide nodebug kernel?
Short story: user error, removing "acpi=noirq" from the boot parameters resulted in a functional touchpad
Long story: I was having trouble booting the installer from a usb thumbstick, through trial and error I attempted adding "acpi=noirq" and booting from a usb dvd drive.
It think it was the booting from a dvd drive that fixed booting, and not the acpi=noirq (that's my best guess).
So, removing "acpi=noirq" resolves the issue.
My apologies for the false alarm.
No worries. Glad you found out the issue.