[Kernel-packages] [Bug 1908153] Re: [Alienware 15 R4, Realtek ALC3266, Black Headphone Out or internal speakers] Underruns, dropouts or crackling sound
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1908153 Title: [Alienware 15 R4, Realtek ALC3266, Black Headphone Out or internal speakers] Underruns, dropouts or crackling sound Status in linux package in Ubuntu: Expired Bug description: With this latest update (Linux 5.4.0-58), the sound is now crackling. Feels like DMA buffer underruns, but I'm not sure. Not seeing a significant CPU load that might have aggravated it, nor am I seeing any complaints in syslog or kern.log. Restarting pulseaudio and running alsa force-reload had no effect. These sound issues started with the same update that caused the ath10k_pci driver to become extremely unreliable (filed as bug 1908106). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ddt 22891 F pulseaudio /dev/snd/controlC0: ddt 22891 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 14:55:14 2020 InstallationDate: Installed on 2020-03-23 (266 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Dec 14 07:32:47 ddtlap dbus-daemon[859]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=124 pid=1157 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Dec 14 08:11:14 ddtlap pulseaudio[1157]: Failed to create sink input: sink is suspended. Dec 14 08:12:19 ddtlap pulseaudio[1157]: Failed to create sink input: sink is suspended. Dec 14 08:13:47 ddtlap dbus-daemon[859]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.70" (uid=1000 pid=1553 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.3" (uid=0 pid=855 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Alienware 15 R4, Realtek ALC3266, Black Headphone Out, Left] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to focal on 2020-05-12 (216 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 15 R4 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware15R4:pvr1.7.0:rvnAlienware:rnAlienware15R4:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 15 R4 dmi.product.sku: 0876 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ddt 22891 F pulseaudio /dev/snd/controlC0: ddt 22891 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-23 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6708 Microdia Integrated_Webcam_FHD Bus 001 Device 002: ID 187c:0550 Alienware Corporation AW-ELC Bus 001 Device 004: ID 0cf3:e301 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware 15 R4 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=875cff72-a3db-4709-ac4d-ce80b29b9970 ro i915.alpha_support=1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
** Changed in: makedumpfile (Ubuntu Focal) Importance: Undecided => High ** Changed in: makedumpfile (Ubuntu Groovy) Importance: Undecided => High ** Changed in: makedumpfile (Ubuntu Hirsute) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Status in makedumpfile source package in Hirsute: Confirmed Bug description: [Impact] On arm64 and kernels 5.4+ makedumpfile fails. Upstream patches solve this bug : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183 [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583 [Test Case] OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done [Regression Potential] Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option removes get_elf_loads function this function was only used with --mem-usage option , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19) the information needed is in vmcoreinfo Any regression potential would affect the --mem-usage only Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo arm64 only make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing VA_BITS does not work on Linux 5.4 and later. Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, however this way of calculation breaks after 5.4. This commit gets the VA_BITS from vmcoreinfo and as a safeguard it uses the old way of deriving VA_BITS only if reading from vmcoreinfo doesn't work. From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later use later kernel so not great regression potentional and if any it would only affect arm64. Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA arm64 only Linux 5.4 and later kernels for arm64 changed the kernel VA space arrangement and introduced 52-bit kernel VAs by merging branch commit b333b0ba2346. Support 5.9+ kernels with vmcoreinfo entries and 5.4+ kernels with best guessing. This patch makes adjustemnt to properly calculate vabits_actual, max_physmem_bits, page_offset Any regression potential would affect only arm64 and the calculation of the above variables. [Other] For H only the 3 commits are needed and they cherry-pick. For G and F the 3rd commit does not apply and an extra commit is needed : commit da0d25ffa585c9a1adb94562c815daa393b1ee5e
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu Groovy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: New Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in kdump-tools source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+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 1918024] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1918024 Title: ZFS/fwupd infinite loop Status in linux package in Ubuntu: Confirmed Bug description: Infinite loop of ZFS/fwupd events slowing system to a crawl after waking. Mar 6 12:37:56 fuel zed: eid=3668 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:56 fuel zed: eid=3669 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:56 fuel zed: eid=3670 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:56 fuel zed: eid=3671 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:57 fuel zed: eid=3672 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:57 fuel zed: eid=3673 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:57 fuel zed: eid=3674 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:57 fuel zed: eid=3675 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:57 fuel fwupd[9611]: 20:37:57:0979 FuEngine ata failed to change udev device /sys/devices/pci:00/:00:1f.2/ata8/host7/target7:0:0/7:0:0:0/block/sdb: cannot ensure ID: FuUdevDevice: Mar 6 12:37:57 fuel fwupd[9611]: WDC WD40EZRZ-00GXCB0 Mar 6 12:37:57 fuel fwupd[9611]: Serial: WD-WCC7K5PENUZC Mar 6 12:37:57 fuel fwupd[9611]: Flags:none Mar 6 12:37:57 fuel fwupd[9611]: Version: 80.00A80 Mar 6 12:37:57 fuel fwupd[9611]: 20:37:57:0985 FuEngine ata failed to change udev device /sys/devices/pci:00/:00:1f.2/ata8/host7/target7:0:0/7:0:0:0/block/sdb/sdb9: cannot ensure ID: FuUdevDevice: Mar 6 12:37:57 fuel fwupd[9611]: WDC WD40EZRZ-00GXCB0 Mar 6 12:37:57 fuel fwupd[9611]: Serial: WD-WCC7K5PENUZC Mar 6 12:37:57 fuel fwupd[9611]: Flags:none Mar 6 12:37:57 fuel fwupd[9611]: Version: 80.00A80 Mar 6 12:37:58 fuel fwupd[9611]: 20:37:58:0070 FuEngine ata failed to change udev device /sys/devices/pci:00/:00:1f.2/ata8/host7/target7:0:0/7:0:0:0/block/sdb/sdb1: cannot ensure ID: FuUdevDevice: Mar 6 12:37:58 fuel fwupd[9611]: WDC WD40EZRZ-00GXCB0 Mar 6 12:37:58 fuel fwupd[9611]: Serial: WD-WCC7K5PENUZC Mar 6 12:37:58 fuel fwupd[9611]: Flags:none Mar 6 12:37:58 fuel fwupd[9611]: Version: 80.00A80 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-44-generic 5.8.0-44.50 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mcmurtri 8333 F pulseaudio /dev/snd/controlC0: mcmurtri 8333 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Mar 6 12:38:40 2021 InstallationDate: Installed on 2018-10-28 (860 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash mitigations=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-12-14 (82 days ago) dmi.bios.date: 03/13/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25b dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25b:bd03/13/2018:br5.6:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1918024] [NEW] ZFS/fwupd infinite loop
Public bug reported: Infinite loop of ZFS/fwupd events slowing system to a crawl after waking. Mar 6 12:37:56 fuel zed: eid=3668 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:56 fuel zed: eid=3669 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:56 fuel zed: eid=3670 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:56 fuel zed: eid=3671 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:57 fuel zed: eid=3672 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:57 fuel zed: eid=3673 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:57 fuel zed: eid=3674 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:57 fuel zed: eid=3675 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:57 fuel fwupd[9611]: 20:37:57:0979 FuEngine ata failed to change udev device /sys/devices/pci:00/:00:1f.2/ata8/host7/target7:0:0/7:0:0:0/block/sdb: cannot ensure ID: FuUdevDevice: Mar 6 12:37:57 fuel fwupd[9611]: WDC WD40EZRZ-00GXCB0 Mar 6 12:37:57 fuel fwupd[9611]: Serial: WD-WCC7K5PENUZC Mar 6 12:37:57 fuel fwupd[9611]: Flags:none Mar 6 12:37:57 fuel fwupd[9611]: Version: 80.00A80 Mar 6 12:37:57 fuel fwupd[9611]: 20:37:57:0985 FuEngine ata failed to change udev device /sys/devices/pci:00/:00:1f.2/ata8/host7/target7:0:0/7:0:0:0/block/sdb/sdb9: cannot ensure ID: FuUdevDevice: Mar 6 12:37:57 fuel fwupd[9611]: WDC WD40EZRZ-00GXCB0 Mar 6 12:37:57 fuel fwupd[9611]: Serial: WD-WCC7K5PENUZC Mar 6 12:37:57 fuel fwupd[9611]: Flags:none Mar 6 12:37:57 fuel fwupd[9611]: Version: 80.00A80 Mar 6 12:37:58 fuel fwupd[9611]: 20:37:58:0070 FuEngine ata failed to change udev device /sys/devices/pci:00/:00:1f.2/ata8/host7/target7:0:0/7:0:0:0/block/sdb/sdb1: cannot ensure ID: FuUdevDevice: Mar 6 12:37:58 fuel fwupd[9611]: WDC WD40EZRZ-00GXCB0 Mar 6 12:37:58 fuel fwupd[9611]: Serial: WD-WCC7K5PENUZC Mar 6 12:37:58 fuel fwupd[9611]: Flags:none Mar 6 12:37:58 fuel fwupd[9611]: Version: 80.00A80 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-44-generic 5.8.0-44.50 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mcmurtri 8333 F pulseaudio /dev/snd/controlC0: mcmurtri 8333 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Mar 6 12:38:40 2021 InstallationDate: Installed on 2018-10-28 (860 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Default string ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash mitigations=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-44-generic N/A linux-backports-modules-5.8.0-44-generic N/A linux-firmware1.190.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-12-14 (82 days ago) dmi.bios.date: 03/13/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25b dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25b:bd03/13/2018:br5.6:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1918024 Title: ZFS/fwupd infinite loop Status in linux package in Ubuntu: New Bug description: Infinite loop of ZFS/fwupd events slowing system to a crawl after waking. Mar 6 12:37:56 fuel zed: eid=3668 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:56 fuel zed: eid=3669 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar 6 12:37:56 fuel zed: eid=3670 class=config_sync pool_guid=0x2D095FFB2B65A8E6 Mar
[Kernel-packages] [Bug 1917528] Re: bcmwl-kernel-source fails to build on Linux 5.10
Yep, this is "a problem" for me running Hirsute Lubuntu on both my mac '09 MBP and just now tried to check it on my '12 cMP in Lu 21.04 and tried to "add the driver" via Add'l drivers and it would not install the driver . . . . It's less of a problem on the desktop unit, because it is plugged in, both appear to be using BCM4322 wifi units . . . but, this problem is a "show-stopper" for for laptop . . . must have wifi capability in that machine. Wifi was working fine as of this recent Wed night, logged into Lu 21.04 .. . connected to wifi, saw that there was a large "794 package upgrade" available, ran it through the wifi . . . but on reboot, wifi was "gone" . . . . Fortunately at that location I could use ethernet, but yesterday at my other part-time job, no such luck . . . no capacity for wifi. Today I messed around with it and found that as this post mentions "bcmwl-kernel-source" package is "not friendly" with the kernel??? Please advise. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1917528 Title: bcmwl-kernel-source fails to build on Linux 5.10 Status in bcmwl package in Ubuntu: Confirmed Bug description: OS: Kubuntu 21.04 Installing bcmwl-kernel-source on Linux 5.10 kernel will fail. This didn't happen on Kubuntu 20.10. During the installation the messages are: Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.10.0-14-generic Building for architecture x86_64 Building initial module for 5.10.0-14-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.10.0-14-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: errore nell'elaborare il pacchetto bcmwl-kernel-source (--configure): il sottoprocesso installato pacchetto bcmwl-kernel-source script post-installation ha restituito lo stato di errore 10 Si sono verificati degli errori nell'elaborazione: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) Logs report: $ cat /var/crash/bcmwl-kernel-source.0.crash ProblemType: Package DKMSBuildLog: DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 5.10.0-14-generic (x86_64) Tue Mar 2 08:50:04 PM CET 2021 make: Entering directory '/usr/src/linux-headers-5.10.0-14-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_iw.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.o /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_pci_probe’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:784:2: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 784 | if ((val & 0xff00) != 0) | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:786:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 786 | bar1_size = pci_resource_len(pdev, 2); | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c: In function ‘wl_dev_ioctl’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: implicit declaration of function ‘get_fs’; did you mean ‘get_ds’? [-Werror=implicit-function-declaration] 461 | fs = get_fs(); | ^~ | get_ds /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:461:7: error: incompatible types when assigning to type ‘mm_segment_t’ from type ‘int’ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:2: error: implicit declaration of function ‘set_fs’; did you mean ‘sget_fc’? [-Werror=implicit-function-declaration] 462 | set_fs(get_ds()); | ^~ | sget_fc In file included from /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:26: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:600:19: error: ‘KERNEL_DS’ undeclared (first use in this function); did you mean ‘KERNFS_NS’? 600 | #define get_ds() (KERNEL_DS) | ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:462:9: note: in expansion of macro ‘get_ds’ 462 | set_fs(get_ds()); | ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:600:19: note: each undeclared identifier is reported only once for each function it appears in 600 |
[Kernel-packages] [Bug 1918013] [NEW] package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi, 3-model-b.txt lib/firmware/brcm
Public bug reported: Upgrade error Unpacking linux-firmware (1.195) over (1.194) ... dpkg: error processing archive /tmp/apt-dpkg-install-N6i2Cp/86-linux-firmware_1. 195_all.deb (--unpack): trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 update-initramfs: Generating /boot/initrd.img-5.8.0-1017-raspi ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] ProcVersionSignature: Ubuntu 5.8.0-1017.20+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu59 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dad1239 F pulseaudio /dev/snd/pcmC1D0p: dad1239 F...m pulseaudio /dev/snd/controlC0: dad1239 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Mar 6 14:59:23 2021 Dependencies: ErrorMessage: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 ImageMediaBuild: 20210302 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1280x1024M@60 smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware StagingDrivers: bcm2835_v4l2 bcm2835_isp bcm2835_codec bcm2835_mmal_vchiq snd_bcm2835 vc_sm_cma Title: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed to install/upgrade: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 hirsute staging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1918013 Title: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed to install/upgrade: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 Status in linux-firmware package in Ubuntu: New Bug description: Upgrade error Unpacking linux-firmware (1.195) over (1.194) ... dpkg: error processing archive /tmp/apt-dpkg-install-N6i2Cp/86-linux-firmware_1. 195_all.deb (--unpack): trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 update-initramfs: Generating /boot/initrd.img-5.8.0-1017-raspi ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] ProcVersionSignature: Ubuntu 5.8.0-1017.20+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu59 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dad1239 F pulseaudio /dev/snd/pcmC1D0p: dad1239 F...m pulseaudio /dev/snd/controlC0: dad1239 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Mar 6 14:59:23 2021 Dependencies: ErrorMessage: trying to overwrite
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
I have 8086:9d71 on a Xiaomi Redmi laptop and it dose cause some sides. If you simply disable the SST driver and fallback to the legacy hda driver, despite the various NID pin errors on different machines, the digital microphone won't work at all. Maybe the only solution to this is to 1)looking forward to sof firmware support, which is not much possible since the hardware(8086:9d71) we're using is based on kbl, or 2) get the proper SST driver for this platform working, it's the only firmware that supports both dmic and sound output. -- 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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+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 1452318] Re: Faulty behavior when resuming from suspend
I still have this issue on Ubuntu 20.04, Kernel 5.4.0-66-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/1452318 Title: Faulty behavior when resuming from suspend Status in linux package in Ubuntu: Fix Released Bug description: Waking from suspend, everything seems normal, except the graphical elements and text on my desktop are not drawn properly. Sometimes, moving the mouse over icons can cause them to be redrawn, sometimes not. It appears not to matter how I initiate the suspend (e.g. by closing laptop lid, or by calling pm-suspend explicitly) and it appears not to matter whether I am using an external display or the laptop's own screen. All other hardware appears to be working, and I can restart the laptop by clicking where the icons ought to be. The only symptom seems to be that the drawing does not happen correctly. I'm not sure what additional information I should provide to help diagnose the problem, so please advise me. Also, if this is more likely to be a xfce issue, then please change the package on the bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed May 6 17:17:51 2015 InstallationDate: Installed on 2015-05-04 (1 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452318/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I want to politely point out that this thread is not helping anymore; it
has become mere chit-chat. Things were confusing to begin with and
unfortunately it is becoming more confusing. What is the fix? Does is
work with a particular kernel? The use of mainline kernel 5.11 should
solve all the problems? Is this nvidia gpu issue related to the solution
to the trackpad? Why can't the external monitor work, even with the AMD
iGPU? Most importantly, what one should do to have a working touchpad,
working nvida gpu and working external monitor? Please reply only if you
know what are you going to write.
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
[Kernel-packages] [Bug 1917885] Re: No longer able to install latest nvidia driver with ubuntu-drivers autoinstall
I was able to run the ubuntu-drivers install command without problems on a liveusb (kubuntu 20.04, the same as my system). There seems to be something wrong with my installation. I'm sorry for posting this as a bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1917885 Title: No longer able to install latest nvidia driver with ubuntu-drivers autoinstall Status in linux-restricted-modules package in Ubuntu: New Bug description: Following the latest update of nvidia-drivers-460, my second monitor stopped working. I purged that package and attempted to reinstall with ubuntu-drivers autoinstall. The following error occured: linux-modules-nvidia-460-generic : Depends: nvidia-kernel-common-460 (<= 460.39-1) but 460.56-0ubuntu0.20.04.1 is to be installed I'm not sure why the dependency would say <= instead of >=. I suspect this is part of why my 2nd monitor stopped working and I'm having trouble reinstalling the latest driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1917885/+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 1917977] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1917977 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1917977 Title: Synaptiks touchpad not detected in kernel Status in linux package in Ubuntu: Incomplete Bug description: After using "cat /proc/bus/input/devices" no touchpad shows up same with xinput and other commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917977/+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
