[Kernel-packages] [Bug 2035559] Re: upgrade to latest proposed kernel 6.5.0-5 failed
fenris@ThinkPad-P1 ~> sudo apt install tp-smapi-dkms [sudo] password for fenris: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: tp-smapi-dkms 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 32.3 kB of archives. After this operation, 121 kB of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu mantic/universe amd64 tp-smapi-dkms amd64 0.44-1ubuntu1 [32.3 kB] Fetched 32.3 kB in 8s (4,118 B/s) Selecting previously unselected package tp-smapi-dkms. (Reading database ... 391838 files and directories currently installed.) Preparing to unpack .../tp-smapi-dkms_0.44-1ubuntu1_amd64.deb ... Unpacking tp-smapi-dkms (0.44-1ubuntu1) ... Setting up tp-smapi-dkms (0.44-1ubuntu1) ... fenris@ThinkPad-P1 ~> -- 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/2035559 Title: upgrade to latest proposed kernel 6.5.0-5 failed Status in linux package in Ubuntu: Invalid Status in tp-smapi package in Ubuntu: New Bug description: Setting up linux-headers-6.5.0-5-generic (6.5.0-5.5) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-5-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 6.5.0-5-generic (x86_64) Consult /var/lib/dkms/tp_smapi/0.43/build/make.log for more information. dkms autoinstall on 6.5.0-5-generic/x86_64 succeeded for nvidia dkms autoinstall on 6.5.0-5-generic/x86_64 failed for tp_smapi(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.5.0-5-generic ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.5.0-5-generic (--configure): installed linux-headers-6.5.0-5-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-22.04: linux-headers-generic-hwe-22.04 depends on linux-headers-6.5.0-5-generic; however: Package linux-headers-6.5.0-5-generic is not configured yet. dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured Setting up linux-image-6.5.0-5-generic (6.5.0-5.5) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic-hwe-22.04: linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 6.5.0.5.7); however: Package linux-headers-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-oem-22.04: linux-oem-22.04 depends on linux-generic-hwe-22.04; however: Package linux-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-oem-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.5.0-5-generic; however: Package linux-headers-6.5.0-5-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfNo apport report written because the error message indicates its a followup error from a previous failure. No apport repo rt written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already igured dpkg: dependency problems prevent configuration of linux-headers-oem-22.04: linux-headers-oem-22.04 depends on linux-headers-generic-hwe-22.04; however: Package
[Kernel-packages] [Bug 2035559] Re: upgrade to latest proposed kernel 6.5.0-5 failed
removed the tp-smapi-dkms package solved the upgrade -- 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/2035559 Title: upgrade to latest proposed kernel 6.5.0-5 failed Status in linux package in Ubuntu: Confirmed Bug description: Setting up linux-headers-6.5.0-5-generic (6.5.0-5.5) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-5-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 6.5.0-5-generic (x86_64) Consult /var/lib/dkms/tp_smapi/0.43/build/make.log for more information. dkms autoinstall on 6.5.0-5-generic/x86_64 succeeded for nvidia dkms autoinstall on 6.5.0-5-generic/x86_64 failed for tp_smapi(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.5.0-5-generic ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.5.0-5-generic (--configure): installed linux-headers-6.5.0-5-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-22.04: linux-headers-generic-hwe-22.04 depends on linux-headers-6.5.0-5-generic; however: Package linux-headers-6.5.0-5-generic is not configured yet. dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured Setting up linux-image-6.5.0-5-generic (6.5.0-5.5) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic-hwe-22.04: linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 6.5.0.5.7); however: Package linux-headers-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-oem-22.04: linux-oem-22.04 depends on linux-generic-hwe-22.04; however: Package linux-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-oem-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.5.0-5-generic; however: Package linux-headers-6.5.0-5-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfNo apport report written because the error message indicates its a followup error from a previous failure. No apport repo rt written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already igured dpkg: dependency problems prevent configuration of linux-headers-oem-22.04: linux-headers-oem-22.04 depends on linux-headers-generic-hwe-22.04; however: Package linux-headers-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-headers-oem-22.04 (--configure): dependency problems - leaving unconfigured Processing triggers for linux-image-6.5.0-5-generic (6.5.0-5.5) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-5-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 6.5.0-5-generic (x86_64) Consult
[Kernel-packages] [Bug 2035559] [NEW] upgrade to latest proposed kernel 6.5.0-5 failed
Public bug reported: Setting up linux-headers-6.5.0-5-generic (6.5.0-5.5) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-5-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 6.5.0-5-generic (x86_64) Consult /var/lib/dkms/tp_smapi/0.43/build/make.log for more information. dkms autoinstall on 6.5.0-5-generic/x86_64 succeeded for nvidia dkms autoinstall on 6.5.0-5-generic/x86_64 failed for tp_smapi(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.5.0-5-generic ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.5.0-5-generic (--configure): installed linux-headers-6.5.0-5-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-22.04: linux-headers-generic-hwe-22.04 depends on linux-headers-6.5.0-5-generic; however: Package linux-headers-6.5.0-5-generic is not configured yet. dpkg: error processing package linux-headers-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured Setting up linux-image-6.5.0-5-generic (6.5.0-5.5) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic-hwe-22.04: linux-generic-hwe-22.04 depends on linux-headers-generic-hwe-22.04 (= 6.5.0.5.7); however: Package linux-headers-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-oem-22.04: linux-oem-22.04 depends on linux-generic-hwe-22.04; however: Package linux-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-oem-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.5.0-5-generic; however: Package linux-headers-6.5.0-5-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfNo apport report written because the error message indicates its a followup error from a previous failure. No apport repo rt written because MaxReports is reached already No apport report written because MaxReports is reached already No apport report written because MaxReports is reached already igured dpkg: dependency problems prevent configuration of linux-headers-oem-22.04: linux-headers-oem-22.04 depends on linux-headers-generic-hwe-22.04; however: Package linux-headers-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-headers-oem-22.04 (--configure): dependency problems - leaving unconfigured Processing triggers for linux-image-6.5.0-5-generic (6.5.0-5.5) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-5-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j12 KERNELRELEASE=6.5.0-5-generic -C /lib/modules/6.5.0-5-generic/build M=/var/lib/dkms/tp_smapi/0.43/build HDAPS=1...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/tp-smapi-dkms.0.crash' Error! Bad return status for module build on kernel: 6.5.0-5-generic (x86_64) Consult /var/lib/dkms/tp_smapi/0.43/build/make.log for more information. dkms autoinstall on 6.5.0-5-generic/x86_64 succeeded for nvidia dkms autoinstall on 6.5.0-5-generic/x86_64 failed for tp_smapi(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.5.0-5-generic ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
attached devices , xinput and Xorg log ** Attachment added: "attachments.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5315595/+files/attachments.zip -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
even worse it didn't detect/worked since booting up my laptop. removing from modprobe and adding it back still did not work :( -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor:
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
I'm having this issue with my Lenovo x240 , running ubuntu 19.10 with kernel 5.3.0-26-generic -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None
[Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
thanks @kzapalowicz however in Zesty ver. 1:10.0-1ubuntu2. Please advise. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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
[Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
yeah, we are more than happy to test the fixes. Can't wait for the PPA, hope it will land in Zesty as well .. Kind Regards, ejat @ fenris -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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
[Kernel-packages] [Bug 1223194] [NEW] [Apple Inc. MacBookPro7, 1] suspend/resume failure [non-free: wl]
Public bug reported: suspend / resume failure ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-5-generic 3.11.0-5.11 ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0 Uname: Linux 3.11.0-6-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: root 1069 F pommed fenris 2481 F pulseaudio Date: Sat Sep 7 02:40:43 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=36bf745f-eaf3-48cd-8009-c73bbd4c6cb1 InstallationDate: Installed on 2012-10-31 (313 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) InterpreterPath: /usr/bin/python3.3 MachineType: Apple Inc. MacBookPro7,1 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-6-generic root=UUID=4885b3dd-8eca-44ca-8396-2b75167e8cad ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-6-generic N/A linux-backports-modules-3.11.0-6-generic N/A linux-firmware1.113 SourcePackage: linux Title: [Apple Inc. MacBookPro7,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/07/11 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B0E.071400 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B0E.071400:bd11/07/11:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume saucy suspend -- 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/1223194 Title: [Apple Inc. MacBookPro7,1] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: New Bug description: suspend / resume failure ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-5-generic 3.11.0-5.11 ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0 Uname: Linux 3.11.0-6-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: root 1069 F pommed fenris 2481 F pulseaudio Date: Sat Sep 7 02:40:43 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=36bf745f-eaf3-48cd-8009-c73bbd4c6cb1 InstallationDate: Installed on 2012-10-31 (313 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) InterpreterPath: /usr/bin/python3.3 MachineType: Apple Inc. MacBookPro7,1 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-6-generic root=UUID=4885b3dd-8eca-44ca-8396-2b75167e8cad ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-6-generic N/A linux-backports-modules-3.11.0-6-generic N/A linux-firmware1.113 SourcePackage: linux Title: [Apple Inc. MacBookPro7,1] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/07/11 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP71.88Z.0039.B0E.071400 dmi.board.name: Mac-F222BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F222BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B0E.071400:bd11/07/11:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8: dmi.product.name: MacBookPro7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to:
