Public bug reported: 16.10 beta 2, as installed fresh, has working keyboard and touchscreen on my Acer Chromebook R11. However, after dist-upgrade they're lost, so touchscreen doesn't work and I need to use external keyboard.
Looking at config diff, the likely culprit is: +CONFIG_PINCTRL_AMD=y CONFIG_PINCTRL_BAYTRAIL=y -CONFIG_PINCTRL_CHERRYVIEW=y -CONFIG_PINCTRL_INTEL=y -CONFIG_PINCTRL_BROXTON=y -CONFIG_PINCTRL_SUNRISEPOINT=y +CONFIG_PINCTRL_CHERRYVIEW=m +CONFIG_PINCTRL_INTEL=m +CONFIG_PINCTRL_BROXTON=m +CONFIG_PINCTRL_SUNRISEPOINT=m As indicated at https://github.com/GalliumOS/galliumos- distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.". So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to m instead of y causes at least the touchscreen regression, and probably the keyboard one too. --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: timo 1922 F.... pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware 1.161 Tags: yakkety Uname: Linux 4.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/21/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected yakkety ** Tags added: apport-collected yakkety ** Description changed: 16.10 beta 2, as installed fresh, has working keyboard and touchscreen on my Acer Chromebook R11. However, after dist-upgrade they're lost, so touchscreen doesn't work and I need to use external keyboard. Looking at config diff, the likely culprit is: +CONFIG_PINCTRL_AMD=y CONFIG_PINCTRL_BAYTRAIL=y -CONFIG_PINCTRL_CHERRYVIEW=y -CONFIG_PINCTRL_INTEL=y -CONFIG_PINCTRL_BROXTON=y -CONFIG_PINCTRL_SUNRISEPOINT=y +CONFIG_PINCTRL_CHERRYVIEW=m +CONFIG_PINCTRL_INTEL=m +CONFIG_PINCTRL_BROXTON=m +CONFIG_PINCTRL_SUNRISEPOINT=m As indicated at https://github.com/GalliumOS/galliumos- distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.". - So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW - one) to m instead of y causes at least the touchscreen regression, and - probably the keyboard one too. + So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to m instead of y causes at least the touchscreen regression, and probably the keyboard one too. + --- + ApportVersion: 2.20.3-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USER PID ACCESS COMMAND + /dev/snd/controlC0: timo 1922 F.... pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.10 + InstallationDate: Installed on 2016-10-04 (0 days ago) + InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2a Intel Corp. + Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: GOOGLE Cyan + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 + RelatedPackageVersions: + linux-restricted-modules-4.8.0-17-generic N/A + linux-backports-modules-4.8.0-17-generic N/A + linux-firmware 1.161 + Tags: yakkety + Uname: Linux 4.8.0-17-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/21/2016 + dmi.bios.vendor: coreboot + dmi.chassis.type: 3 + dmi.chassis.vendor: GOOGLE + dmi.modalias: dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: + dmi.product.name: Cyan + dmi.product.version: 1.0 + dmi.sys.vendor: GOOGLE -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630238 Title: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11 Status in linux package in Ubuntu: New Bug description: 16.10 beta 2, as installed fresh, has working keyboard and touchscreen on my Acer Chromebook R11. However, after dist-upgrade they're lost, so touchscreen doesn't work and I need to use external keyboard. Looking at config diff, the likely culprit is: +CONFIG_PINCTRL_AMD=y CONFIG_PINCTRL_BAYTRAIL=y -CONFIG_PINCTRL_CHERRYVIEW=y -CONFIG_PINCTRL_INTEL=y -CONFIG_PINCTRL_BROXTON=y -CONFIG_PINCTRL_SUNRISEPOINT=y +CONFIG_PINCTRL_CHERRYVIEW=m +CONFIG_PINCTRL_INTEL=m +CONFIG_PINCTRL_BROXTON=m +CONFIG_PINCTRL_SUNRISEPOINT=m As indicated at https://github.com/GalliumOS/galliumos- distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.". So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to m instead of y causes at least the touchscreen regression, and probably the keyboard one too. --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: timo 1922 F.... pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware 1.161 Tags: yakkety Uname: Linux 4.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/21/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
