[Bug 2163555] Re: [ASUS ROG Strix G18 G814JVR] BIOS 320/322 expose conflicting ACPI namespace: duplicate XHCI _UPC/_PLD and PEGP._S0W definitions

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163555 Title: [ASUS ROG Strix G18 G814JVR] BIOS 320/322 expose conflicting ACPI namespace: duplicate XHCI _UPC/_PLD and PEGP._S0W definitions Status in linux package in Ubuntu: New Bug description: System: - ASUS ROG Strix G18 G814JVR - Ubuntu 26.04 LTS - kernel 7.0.0-29-generic / Ubuntu 7.0.0-29.29-generic - running-kernel ACPICA: 20251212 - BIOS tested: - G814JVR.320, 2024-10-24 - G814JVR.322, 2025-10-01 The system produces a large set of ACPI BIOS errors on every boot. I have isolated multiple reproducible namespace conflicts in the firmware ACPI tables and reproduced them independently with upstream ACPICA iasl 20260408. The most visible boot errors include: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.I2C1.TPL1], AE_NOT_FOUND ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.I2C3.TPL1], AE_NOT_FOUND and duplicate objects for every XHCI RHUB port: \_SB.PC00.XHCI.RHUB.HS01._UPC \_SB.PC00.XHCI.RHUB.HS01._PLD ... HS01 through HS14 SS01 through SS10 all failing with AE_ALREADY_EXISTS. Additional firmware errors include unresolved LPCB.SEN2, missing WMI WQ00, and \_TZ.THRM being unresolved while evaluating \_SB.IETM._OSC. I upgraded the machine from BIOS 320 to the current BIOS 322. The same ACPI errors remain. I captured the full ACPI table sets before and after the BIOS upgrade and compared them. The SSDTs directly implicated in these failures are byte-for-byte identical between BIOS 320 and BIOS 322, including: - ssdt1.dat (DPTF / thermal-related table) - ssdt7.dat (_ASUS_ RplSBTbt) - ssdt10.dat (_ASUS_ TbtTypeC) - ssdt11.dat (_ASUS_ UsbCTabl) - ssdt12.dat (INTEL xh_rplsb) - DMAR BIOS 322 did change the DSDT and several other tables, so it was a real firmware-table update, but the implicated SSDTs were not updated. I then built upstream ACPICA 20260408 and reproduced the namespace conflicts outside the running kernel. XHCI collision isolation: DSDT + ssdt12.dat (INTEL xh_rplsb) fails immediately with: Firmware Error (ACPI): Failure creating named object [\_SB.PC00.XHCI.RHUB.HS01._UPC], AE_ALREADY_EXISTS This is the same error emitted by the running Ubuntu kernel. For comparison: - DSDT + ssdt10 (TbtTypeC): succeeds - DSDT + ssdt11 (UsbCTabl): succeeds - ssdt10 + ssdt11: succeeds - ssdt10 + ssdt12: succeeds - ssdt11 + ssdt12: succeeds Therefore the XHCI collision is specifically between the DSDT and the INTEL xh_rplsb SSDT, not between the ASUS Type-C tables. There is a second independent namespace collision: ssdt5.dat (SaSsdt) ssdt7.dat (_ASUS_ RplSBTbt) Both combinations: target=ssdt5 external=ssdt7 target=ssdt7 external=ssdt5 fail with: Failure creating named object [\_SB.PC00.PEG1.PEGP._S0W], AE_ALREADY_EXISTS The complete BIOS-322 table set also fails ACPICA 20260408 disassembly on that same PEGP._S0W object. The extracted AML further shows that the DSDT and INTEL xh_rplsb table provide overlapping XHCI RHUB port _UPC/_PLD definitions rather than the tables being mutually exclusive. This demonstrates an internally conflicting ACPI namespace supplied by the G814JVR firmware and reproducible with both the ACPICA version in the Ubuntu kernel and upstream ACPICA 20260408. There is a separate runtime xHCI/USB failure being tracked in Ubuntu bug #2163551. That incident involved an xHCI Host System Error and an IOMMU/DMAR DMA-read fault for 00:14.0. Because these ACPI errors concern the same XHCI controller namespace, they may be relevant platform context, but I am NOT claiming that the ACPI namespace defect has been proven to cause the runtime xHCI failure. Please advise whether this should be handled with a kernel ACPI quirk/table override or escalated to ASUS/firmware vendor, and whether any additional ACPI table analysis is useful. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 22:06:34 2026 IwDevWlo1Link: Not connected. MachineType: ASUSTeK COMPUTER INC. ROG Strix G18 G814JVR_G814JVR ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=ZFS=UbuntuZFS/root ro quiet splash SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-05 (70 days ago) dmi.bios.date: 10/01/2025 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G814JVR.322 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G814JVR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.49 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG814JVR.322:bd10/01/2025:br5.27:efr0.49:svnASUSTeKCOMPUTERINC.:pnROGStrixG18G814JVR_G814JVR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG814JVR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaROGStrixG18: dmi.product.family: ROG Strix G18 dmi.product.name: ROG Strix G18 G814JVR_G814JVR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163555/+subscriptions

[Bug 2163568] Re: [i915][xe] Failed to read TMDS config: -6 on HDMI-A-1 (Alder Lake-P iGPU, Acer Aspire A715-76G) - external monitor never lights up

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163568 Title: [i915][xe] Failed to read TMDS config: -6 on HDMI-A-1 (Alder Lake-P iGPU, Acer Aspire A715-76G) - external monitor never lights up Status in linux package in Ubuntu: New Bug description: Summary ------- External HDMI monitor connected to the Intel iGPU HDMI port never gets a picture. Kernel log repeats every ~16 seconds since boot: [drm] *ERROR* [CONNECTOR:516:HDMI-A-1] Failed to read TMDS config: -6 `xrandr` shows HDMI-1 as "connected" but with an implausible fallback resolution (6880x2880), consistent with a failed EDID/DDC read rather than a real mode. Hardware -------- - Laptop: Acer Aspire A715-76G - iGPU: Intel Alder Lake-P UHD Graphics [8086:46a3] (0000:00:02.0) - HDMI port is wired to this GPU - dGPU: NVIDIA RTX 2050 (GA107), mux-less Optimus, no physical video output of its own - BIOS: InsydeH20, version V1.57 (2026-05-28) - latest available, no relevant multi-monitor/IGD options exposed - OS: Ubuntu 26.04 - Kernel: 7.0.0-29-generic (also reproduced on mainline-adjacent `xe` force-probe of the same kernel) Steps to reproduce ------------------ 1. Cold boot into Ubuntu with an external monitor connected via HDMI. 2. Monitor is detected but shows no signal / no picture. 3. `journalctl -k -b | grep -i -E "tmds|hdmi"` shows repeated "Failed to read TMDS config: -6" (errno -6 = ENXIO) on CONNECTOR:516:HDMI-A-1. What I already ruled out ------------------------- - Cable: tested with a second HDMI cable, same result. - Port/monitor: monitor+cable tested and recognized fine; same monitor works perfectly under Windows 11 on the exact same hardware/cable/port (both cold boot and warm reboot from a fully logged-in Windows session into Ubuntu). - prime-select mode: tested both `nvidia` and `on-demand`, no difference (expected, since the HDMI port is physically on the iGPU, not the dGPU). - Driver: forced the newer `xe` driver via `i915.force_probe=!46a3 xe.force_probe=46a3` - identical "Failed to read TMDS config: -6" error occurs with `xe` as well, just with the `xe` module name in the log instead of `i915`. This points to a failure in the shared GMBUS/DDC/i2c transaction layer, not in driver-specific logic. - BIOS: no Internal Graphics / IGD Multi-Monitor / DVMT / CSM options exist in this InsydeH20 BIOS to test. - Newer kernel: attempted to test mainline v7.1.5, but it fails to boot due to Secure Boot ("bad shim lock signature") since mainline builds are unsigned; not tested with Secure Boot disabled. Expected behavior ----------------- External HDMI monitor should light up on Linux the same way it does on Windows with identical hardware. Additional info ---------------- Please find attached: `journalctl -k -b` output, `lspci -nnk` VGA section, `xrandr` output, and dmesg from apport. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: alex 3919 F.... pipewire alex 3933 F.... wireplumber /dev/snd/seq: alex 3919 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 14:45:00 2026 InstallationDate: Installed on 2026-08-14 (1 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Acer Aspire A715-76G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=34813e31-7b29-4b9f-8baa-6216c89d517a ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2026 dmi.bios.release: 1.57 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Metis_ADP dmi.board.vendor: ADL dmi.board.version: V1.57 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.57:bd05/28/2026:br1.57:efr1.4:svnAcer:pnAspireA715-76G:pvrV1.57:rvnADL:rnMetis_ADP:rvrV1.57:cvnChassisManufacturer:ct10:cvrChassisVersion:sku0000000000000000:pfaAspire7: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-76G dmi.product.sku: 0000000000000000 dmi.product.version: V1.57 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163568/+subscriptions

[Bug 2163585] Re: No out-of-tree kernel module can load on 7.0.0-29-generic: "Invalid relocation target" on R_X86_64_64 against .gnu.linkonce.this_module

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163585 Title: No out-of-tree kernel module can load on 7.0.0-29-generic: "Invalid relocation target" on R_X86_64_64 against .gnu.linkonce.this_module Status in linux package in Ubuntu: New Bug description: On Ubuntu 26.04 with linux-image-7.0.0-29-generic, no out-of-tree kernel module will load. Modules build cleanly and sign correctly, but insmod fails with "Invalid module format" and the kernel logs an invalid relocation target. Reproducer — a six-line module with no dependencies is enough:   mkdir -p ~/hellomod && cd ~/hellomod   printf '#include <linux/module.h>\nstatic int __init h(void){return 0;}\nstatic void __exit b(void){}\nmodule_init(h);\nmodule_exit(b);\nMODULE_LICENSE("GPL");\n' > hello.c   printf 'obj-m += hello.o\n' > Makefile   make -C /lib/modules/$(uname -r)/build M=$PWD modules   sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \     /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der hello.ko   sudo insmod hello.ko Expected: module loads. Actual: insmod: ERROR: could not insert module hello.ko: Invalid module format dmesg:   module: x86/modules: Invalid relocation target, existing value is   nonzero for sec 41, idx 1, type 1, loc ffffffffc31564d0, val   ffffffffc34c0010 readelf identifies the failing section as .gnu.linkonce.this_module. Its relocation section contains only the two standard entries every kernel module has:   Offset Type Symbol   0x138 R_X86_64_64 init_module + 0   0x490 R_X86_64_64 cleanup_module + 0 Environment:   Ubuntu 26.04 LTS   Linux 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 17 2026   Kernel built with gcc 15.2.0 (Ubuntu 15.2.0-16ubuntu1), GNU ld 2.46   Modules built with the same gcc 15.2.0 — vermagic matches   linux-image, linux-headers and linux-modules are all 7.0.0-29.29, so     there is no version skew between the running kernel and the build     headers   Secure Boot enabled, MOK enrolled, signing verified working (an     unsigned module fails differently, with "Key was rejected by service")   CONFIG_MODULE_COMPRESS_ZSTD=y   CONFIG_MITIGATION_ITS=y, but the CPU reports "Not affected" and booting     with indirect_target_selection=off makes no difference   nvidia on this system is the prebuilt linux-modules-nvidia-595-open     package, built alongside the kernel rather than via DKMS, so it is     not a working out-of-tree counter-example. There are no other DKMS     modules installed to compare against. Originally found while trying to load tuxedo-drivers for keyboard backlight control. Reproduced with tuxedo-drivers 4.22.3, tuxedo-drivers 4.21.0 and tuxedo-keyboard 3.2.10 — three releases across two unrelated codebases, all failing identically — which is what led to the minimal reproducer above. Caveat: very small modules do appear to load (tuxedo_compatibility_check, ~12KB, loads fine), so there may be a discriminator I have not identified, and the failure may not be as universal as the reproducer suggests. No earlier kernel is installed on this system, so I have not been able to test whether this is specific to the 7.0.0-29 ABI. Regression in 7.0.0-29-generic: out-of-tree modules fail to load with "Invalid relocation target" on .gnu.linkonce.this_module (works on 7.0.0-27) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: matt 5277 F.... wireplumber  /dev/snd/controlC0: matt 5277 F.... wireplumber  /dev/snd/seq: matt 5271 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 21:42:44 2026 InstallationDate: Installed on 2026-08-15 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp5s0f0Link: Not connected. Lsusb:  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  Bus 001 Device 002: ID 1e7d:2c2e ROCCAT Lua Mouse  Bus 001 Device 003: ID 5986:2170 Bison Electronics Inc. BisonCam,NB Pro  Bus 001 Device 004: ID 8087:0036 Intel Corp. BE200 Bluetooth  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: 3XS Gamer ProcEnviron:  LANG=en_US.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=UUID=7cabd3ec-7315-40bf-9c08-7a571a4ec64a ro quiet splash indirect_target_selection=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2025 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 9.5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd12/05/2025:br7.8:efr9.5:svn3XS:pnGamer:pvrNotApplicable:rvnNotebook:rnV3xxSNR:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:sku562254:pfaScanComputers: dmi.product.family: Scan Computers dmi.product.name: Gamer dmi.product.sku: 562254 dmi.product.version: Not Applicable dmi.sys.vendor: 3XS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163585/+subscriptions

[Bug 2163585] Re: No out-of-tree kernel module can load on 7.0.0-29-generic: "Invalid relocation target" on R_X86_64_64 against .gnu.linkonce.this_module

** Description changed: On Ubuntu 26.04 with linux-image-7.0.0-29-generic, no out-of-tree kernel module will load. Modules build cleanly and sign correctly, but insmod fails with "Invalid module format" and the kernel logs an invalid relocation target. Reproducer — a six-line module with no dependencies is enough: - mkdir -p ~/hellomod && cd ~/hellomod - printf '#include <linux/module.h>\nstatic int __init h(void){return 0;}\nstatic void __exit b(void){}\nmodule_init(h);\nmodule_exit(b);\nMODULE_LICENSE("GPL");\n' > hello.c - printf 'obj-m += hello.o\n' > Makefile - make -C /lib/modules/$(uname -r)/build M=$PWD modules - sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \ - /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der hello.ko - sudo insmod hello.ko +   mkdir -p ~/hellomod && cd ~/hellomod +   printf '#include <linux/module.h>\nstatic int __init h(void){return 0;}\nstatic void __exit b(void){}\nmodule_init(h);\nmodule_exit(b);\nMODULE_LICENSE("GPL");\n' > hello.c +   printf 'obj-m += hello.o\n' > Makefile +   make -C /lib/modules/$(uname -r)/build M=$PWD modules +   sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \ +     /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der hello.ko +   sudo insmod hello.ko Expected: module loads. Actual: insmod: ERROR: could not insert module hello.ko: Invalid module format dmesg: - module: x86/modules: Invalid relocation target, existing value is - nonzero for sec 41, idx 1, type 1, loc ffffffffc31564d0, val - ffffffffc34c0010 +   module: x86/modules: Invalid relocation target, existing value is +   nonzero for sec 41, idx 1, type 1, loc ffffffffc31564d0, val +   ffffffffc34c0010 readelf identifies the failing section as .gnu.linkonce.this_module. Its relocation section contains only the two standard entries every kernel module has: - Offset Type Symbol - 0x138 R_X86_64_64 init_module + 0 - 0x490 R_X86_64_64 cleanup_module + 0 +   Offset Type Symbol +   0x138 R_X86_64_64 init_module + 0 +   0x490 R_X86_64_64 cleanup_module + 0 Environment: - Ubuntu 26.04 LTS - Linux 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 17 2026 - Kernel built with gcc 15.2.0 (Ubuntu 15.2.0-16ubuntu1), GNU ld 2.46 - Modules built with the same gcc 15.2.0 — vermagic matches - linux-image, linux-headers and linux-modules are all 7.0.0-29.29, so - there is no version skew between the running kernel and the build - headers - Secure Boot enabled, MOK enrolled, signing verified working (an - unsigned module fails differently, with "Key was rejected by service") - CONFIG_MODULE_COMPRESS_ZSTD=y - CONFIG_MITIGATION_ITS=y, but the CPU reports "Not affected" and booting - with indirect_target_selection=off makes no difference - nvidia on this system is the prebuilt linux-modules-nvidia-595-open - package, built alongside the kernel rather than via DKMS, so it is - not a working out-of-tree counter-example. There are no other DKMS - modules installed to compare against. +   Ubuntu 26.04 LTS +   Linux 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 17 2026 +   Kernel built with gcc 15.2.0 (Ubuntu 15.2.0-16ubuntu1), GNU ld 2.46 +   Modules built with the same gcc 15.2.0 — vermagic matches +   linux-image, linux-headers and linux-modules are all 7.0.0-29.29, so +     there is no version skew between the running kernel and the build +     headers +   Secure Boot enabled, MOK enrolled, signing verified working (an +     unsigned module fails differently, with "Key was rejected by service") +   CONFIG_MODULE_COMPRESS_ZSTD=y +   CONFIG_MITIGATION_ITS=y, but the CPU reports "Not affected" and booting +     with indirect_target_selection=off makes no difference +   nvidia on this system is the prebuilt linux-modules-nvidia-595-open +     package, built alongside the kernel rather than via DKMS, so it is +     not a working out-of-tree counter-example. There are no other DKMS +     modules installed to compare against. Originally found while trying to load tuxedo-drivers for keyboard backlight control. Reproduced with tuxedo-drivers 4.22.3, tuxedo-drivers 4.21.0 and tuxedo-keyboard 3.2.10 — three releases across two unrelated codebases, all failing identically — which is what led to the minimal reproducer above. Caveat: very small modules do appear to load (tuxedo_compatibility_check, ~12KB, loads fine), so there may be a discriminator I have not identified, and the failure may not be as universal as the reproducer suggests. No earlier kernel is installed on this system, so I have not been able to test whether this is specific to the 7.0.0-29 ABI. + + Regression in 7.0.0-29-generic: out-of-tree modules fail to load with + "Invalid relocation target" on .gnu.linkonce.this_module (works on + 7.0.0-27) + ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: - USER PID ACCESS COMMAND - /dev/snd/controlC1: matt 5277 F.... wireplumber - /dev/snd/controlC0: matt 5277 F.... wireplumber - /dev/snd/seq: matt 5271 F.... pipewire +  USER PID ACCESS COMMAND +  /dev/snd/controlC1: matt 5277 F.... wireplumber +  /dev/snd/controlC0: matt 5277 F.... wireplumber +  /dev/snd/seq: matt 5271 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 21:42:44 2026 InstallationDate: Installed on 2026-08-15 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp5s0f0Link: Not connected. Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 002: ID 1e7d:2c2e ROCCAT Lua Mouse - Bus 001 Device 003: ID 5986:2170 Bison Electronics Inc. BisonCam,NB Pro - Bus 001 Device 004: ID 8087:0036 Intel Corp. BE200 Bluetooth - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub +  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub +  Bus 001 Device 002: ID 1e7d:2c2e ROCCAT Lua Mouse +  Bus 001 Device 003: ID 5986:2170 Bison Electronics Inc. BisonCam,NB Pro +  Bus 001 Device 004: ID 8087:0036 Intel Corp. BE200 Bluetooth +  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: 3XS Gamer ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR=<set> +  LANG=en_US.UTF-8 +  PATH=(custom, no user) +  SHELL=/bin/bash +  TERM=xterm-256color +  XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=UUID=7cabd3ec-7315-40bf-9c08-7a571a4ec64a ro quiet splash indirect_target_selection=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2025 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 9.5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd12/05/2025:br7.8:efr9.5:svn3XS:pnGamer:pvrNotApplicable:rvnNotebook:rnV3xxSNR:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:sku562254:pfaScanComputers: dmi.product.family: Scan Computers dmi.product.name: Gamer dmi.product.sku: 562254 dmi.product.version: Not Applicable dmi.sys.vendor: 3XS -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163585 Title: No out-of-tree kernel module can load on 7.0.0-29-generic: "Invalid relocation target" on R_X86_64_64 against .gnu.linkonce.this_module Status in linux package in Ubuntu: New Bug description: On Ubuntu 26.04 with linux-image-7.0.0-29-generic, no out-of-tree kernel module will load. Modules build cleanly and sign correctly, but insmod fails with "Invalid module format" and the kernel logs an invalid relocation target. Reproducer — a six-line module with no dependencies is enough:   mkdir -p ~/hellomod && cd ~/hellomod   printf '#include <linux/module.h>\nstatic int __init h(void){return 0;}\nstatic void __exit b(void){}\nmodule_init(h);\nmodule_exit(b);\nMODULE_LICENSE("GPL");\n' > hello.c   printf 'obj-m += hello.o\n' > Makefile   make -C /lib/modules/$(uname -r)/build M=$PWD modules   sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \     /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der hello.ko   sudo insmod hello.ko Expected: module loads. Actual: insmod: ERROR: could not insert module hello.ko: Invalid module format dmesg:   module: x86/modules: Invalid relocation target, existing value is   nonzero for sec 41, idx 1, type 1, loc ffffffffc31564d0, val   ffffffffc34c0010 readelf identifies the failing section as .gnu.linkonce.this_module. Its relocation section contains only the two standard entries every kernel module has:   Offset Type Symbol   0x138 R_X86_64_64 init_module + 0   0x490 R_X86_64_64 cleanup_module + 0 Environment:   Ubuntu 26.04 LTS   Linux 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 17 2026   Kernel built with gcc 15.2.0 (Ubuntu 15.2.0-16ubuntu1), GNU ld 2.46   Modules built with the same gcc 15.2.0 — vermagic matches   linux-image, linux-headers and linux-modules are all 7.0.0-29.29, so     there is no version skew between the running kernel and the build     headers   Secure Boot enabled, MOK enrolled, signing verified working (an     unsigned module fails differently, with "Key was rejected by service")   CONFIG_MODULE_COMPRESS_ZSTD=y   CONFIG_MITIGATION_ITS=y, but the CPU reports "Not affected" and booting     with indirect_target_selection=off makes no difference   nvidia on this system is the prebuilt linux-modules-nvidia-595-open     package, built alongside the kernel rather than via DKMS, so it is     not a working out-of-tree counter-example. There are no other DKMS     modules installed to compare against. Originally found while trying to load tuxedo-drivers for keyboard backlight control. Reproduced with tuxedo-drivers 4.22.3, tuxedo-drivers 4.21.0 and tuxedo-keyboard 3.2.10 — three releases across two unrelated codebases, all failing identically — which is what led to the minimal reproducer above. Caveat: very small modules do appear to load (tuxedo_compatibility_check, ~12KB, loads fine), so there may be a discriminator I have not identified, and the failure may not be as universal as the reproducer suggests. No earlier kernel is installed on this system, so I have not been able to test whether this is specific to the 7.0.0-29 ABI. Regression in 7.0.0-29-generic: out-of-tree modules fail to load with "Invalid relocation target" on .gnu.linkonce.this_module (works on 7.0.0-27) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC1: matt 5277 F.... wireplumber  /dev/snd/controlC0: matt 5277 F.... wireplumber  /dev/snd/seq: matt 5271 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 21:42:44 2026 InstallationDate: Installed on 2026-08-15 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp5s0f0Link: Not connected. Lsusb:  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  Bus 001 Device 002: ID 1e7d:2c2e ROCCAT Lua Mouse  Bus 001 Device 003: ID 5986:2170 Bison Electronics Inc. BisonCam,NB Pro  Bus 001 Device 004: ID 8087:0036 Intel Corp. BE200 Bluetooth  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: 3XS Gamer ProcEnviron:  LANG=en_US.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=UUID=7cabd3ec-7315-40bf-9c08-7a571a4ec64a ro quiet splash indirect_target_selection=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2025 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 9.5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd12/05/2025:br7.8:efr9.5:svn3XS:pnGamer:pvrNotApplicable:rvnNotebook:rnV3xxSNR:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:sku562254:pfaScanComputers: dmi.product.family: Scan Computers dmi.product.name: Gamer dmi.product.sku: 562254 dmi.product.version: Not Applicable dmi.sys.vendor: 3XS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163585/+subscriptions

[Bug 2163585] [NEW] No out-of-tree kernel module can load on 7.0.0-29-generic: "Invalid relocation target" on R_X86_64_64 against .gnu.linkonce.this_module

Public bug reported: On Ubuntu 26.04 with linux-image-7.0.0-29-generic, no out-of-tree kernel module will load. Modules build cleanly and sign correctly, but insmod fails with "Invalid module format" and the kernel logs an invalid relocation target. Reproducer — a six-line module with no dependencies is enough: mkdir -p ~/hellomod && cd ~/hellomod printf '#include <linux/module.h>\nstatic int __init h(void){return 0;}\nstatic void __exit b(void){}\nmodule_init(h);\nmodule_exit(b);\nMODULE_LICENSE("GPL");\n' > hello.c printf 'obj-m += hello.o\n' > Makefile make -C /lib/modules/$(uname -r)/build M=$PWD modules sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \ /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der hello.ko sudo insmod hello.ko Expected: module loads. Actual: insmod: ERROR: could not insert module hello.ko: Invalid module format dmesg: module: x86/modules: Invalid relocation target, existing value is nonzero for sec 41, idx 1, type 1, loc ffffffffc31564d0, val ffffffffc34c0010 readelf identifies the failing section as .gnu.linkonce.this_module. Its relocation section contains only the two standard entries every kernel module has: Offset Type Symbol 0x138 R_X86_64_64 init_module + 0 0x490 R_X86_64_64 cleanup_module + 0 Environment: Ubuntu 26.04 LTS Linux 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 17 2026 Kernel built with gcc 15.2.0 (Ubuntu 15.2.0-16ubuntu1), GNU ld 2.46 Modules built with the same gcc 15.2.0 — vermagic matches linux-image, linux-headers and linux-modules are all 7.0.0-29.29, so there is no version skew between the running kernel and the build headers Secure Boot enabled, MOK enrolled, signing verified working (an unsigned module fails differently, with "Key was rejected by service") CONFIG_MODULE_COMPRESS_ZSTD=y CONFIG_MITIGATION_ITS=y, but the CPU reports "Not affected" and booting with indirect_target_selection=off makes no difference nvidia on this system is the prebuilt linux-modules-nvidia-595-open package, built alongside the kernel rather than via DKMS, so it is not a working out-of-tree counter-example. There are no other DKMS modules installed to compare against. Originally found while trying to load tuxedo-drivers for keyboard backlight control. Reproduced with tuxedo-drivers 4.22.3, tuxedo-drivers 4.21.0 and tuxedo-keyboard 3.2.10 — three releases across two unrelated codebases, all failing identically — which is what led to the minimal reproducer above. Caveat: very small modules do appear to load (tuxedo_compatibility_check, ~12KB, loads fine), so there may be a discriminator I have not identified, and the failure may not be as universal as the reproducer suggests. No earlier kernel is installed on this system, so I have not been able to test whether this is specific to the 7.0.0-29 ABI. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: matt 5277 F.... wireplumber /dev/snd/controlC0: matt 5277 F.... wireplumber /dev/snd/seq: matt 5271 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 21:42:44 2026 InstallationDate: Installed on 2026-08-15 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp5s0f0Link: Not connected. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1e7d:2c2e ROCCAT Lua Mouse Bus 001 Device 003: ID 5986:2170 Bison Electronics Inc. BisonCam,NB Pro Bus 001 Device 004: ID 8087:0036 Intel Corp. BE200 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: 3XS Gamer ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=UUID=7cabd3ec-7315-40bf-9c08-7a571a4ec64a ro quiet splash indirect_target_selection=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2025 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 9.5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd12/05/2025:br7.8:efr9.5:svn3XS:pnGamer:pvrNotApplicable:rvnNotebook:rnV3xxSNR:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:sku562254:pfaScanComputers: dmi.product.family: Scan Computers dmi.product.name: Gamer dmi.product.sku: 562254 dmi.product.version: Not Applicable dmi.sys.vendor: 3XS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163585 Title: No out-of-tree kernel module can load on 7.0.0-29-generic: "Invalid relocation target" on R_X86_64_64 against .gnu.linkonce.this_module Status in linux package in Ubuntu: New Bug description: On Ubuntu 26.04 with linux-image-7.0.0-29-generic, no out-of-tree kernel module will load. Modules build cleanly and sign correctly, but insmod fails with "Invalid module format" and the kernel logs an invalid relocation target. Reproducer — a six-line module with no dependencies is enough: mkdir -p ~/hellomod && cd ~/hellomod printf '#include <linux/module.h>\nstatic int __init h(void){return 0;}\nstatic void __exit b(void){}\nmodule_init(h);\nmodule_exit(b);\nMODULE_LICENSE("GPL");\n' > hello.c printf 'obj-m += hello.o\n' > Makefile make -C /lib/modules/$(uname -r)/build M=$PWD modules sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 \ /var/lib/shim-signed/mok/MOK.priv /var/lib/shim-signed/mok/MOK.der hello.ko sudo insmod hello.ko Expected: module loads. Actual: insmod: ERROR: could not insert module hello.ko: Invalid module format dmesg: module: x86/modules: Invalid relocation target, existing value is nonzero for sec 41, idx 1, type 1, loc ffffffffc31564d0, val ffffffffc34c0010 readelf identifies the failing section as .gnu.linkonce.this_module. Its relocation section contains only the two standard entries every kernel module has: Offset Type Symbol 0x138 R_X86_64_64 init_module + 0 0x490 R_X86_64_64 cleanup_module + 0 Environment: Ubuntu 26.04 LTS Linux 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 17 2026 Kernel built with gcc 15.2.0 (Ubuntu 15.2.0-16ubuntu1), GNU ld 2.46 Modules built with the same gcc 15.2.0 — vermagic matches linux-image, linux-headers and linux-modules are all 7.0.0-29.29, so there is no version skew between the running kernel and the build headers Secure Boot enabled, MOK enrolled, signing verified working (an unsigned module fails differently, with "Key was rejected by service") CONFIG_MODULE_COMPRESS_ZSTD=y CONFIG_MITIGATION_ITS=y, but the CPU reports "Not affected" and booting with indirect_target_selection=off makes no difference nvidia on this system is the prebuilt linux-modules-nvidia-595-open package, built alongside the kernel rather than via DKMS, so it is not a working out-of-tree counter-example. There are no other DKMS modules installed to compare against. Originally found while trying to load tuxedo-drivers for keyboard backlight control. Reproduced with tuxedo-drivers 4.22.3, tuxedo-drivers 4.21.0 and tuxedo-keyboard 3.2.10 — three releases across two unrelated codebases, all failing identically — which is what led to the minimal reproducer above. Caveat: very small modules do appear to load (tuxedo_compatibility_check, ~12KB, loads fine), so there may be a discriminator I have not identified, and the failure may not be as universal as the reproducer suggests. No earlier kernel is installed on this system, so I have not been able to test whether this is specific to the 7.0.0-29 ABI. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: matt 5277 F.... wireplumber /dev/snd/controlC0: matt 5277 F.... wireplumber /dev/snd/seq: matt 5271 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 21:42:44 2026 InstallationDate: Installed on 2026-08-15 (0 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp5s0f0Link: Not connected. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1e7d:2c2e ROCCAT Lua Mouse Bus 001 Device 003: ID 5986:2170 Bison Electronics Inc. BisonCam,NB Pro Bus 001 Device 004: ID 8087:0036 Intel Corp. BE200 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: 3XS Gamer ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=UUID=7cabd3ec-7315-40bf-9c08-7a571a4ec64a ro quiet splash indirect_target_selection=off crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2025 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08 dmi.board.asset.tag: Tag 12345 dmi.board.name: V3xxSNR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 9.5 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08:bd12/05/2025:br7.8:efr9.5:svn3XS:pnGamer:pvrNotApplicable:rvnNotebook:rnV3xxSNR:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:sku562254:pfaScanComputers: dmi.product.family: Scan Computers dmi.product.name: Gamer dmi.product.sku: 562254 dmi.product.version: Not Applicable dmi.sys.vendor: 3XS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163585/+subscriptions

[Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]

================================================================================ LINUX AUDIO FIX FOR HUAWEI AMD LAPTOPS ================================================================================ Author: Linux Community / Michael Lorentz Date: July 2026 Hardware: Huawei MateBook with AMD Ryzen processor (CX11970 audio codec) System: Linux Mint / Ubuntu / Other distributions with PipeWire ================================================================================ STEP-BY-STEP SOLUTION ================================================================================ PROBLEM DESCRIPTION: Audio on built-in laptop speakers does NOT work. Audio on headphones connected to the mini-jack DOES work. ================================================================================ STEP 1: CHECK AUDIO DEVICE STATUS ================================================================================ Open a terminal and run: $ pactl list short sinks If you see "SUSPENDED" status for the speaker device, this confirms the problem. Check if the sound card is detected: $ aplay -l You should see a card with the CX11970 codec (or similar). ================================================================================ STEP 2: IMMEDIATE AUDIO RESTORATION (QUICKEST METHOD) ================================================================================ Perform a full system restart: $ sudo reboot After restart, speaker audio should be restored. NOTE: If this doesn't work, proceed to Step 3. ================================================================================ STEP 3: MANUAL FIX (IF RESTART DID NOT HELP) ================================================================================ Run the following commands in the given order: $ sudo alsactl init $ sudo alsactl store $ systemctl --user restart pipewire pipewire-pulse $ pactl set-default-sink alsa_output.pci-0000_02_00.6.analog-stereo $ pactl set-sink-volume alsa_output.pci-0000_02_00.6.analog-stereo 80% Test if audio works: $ speaker-test -t wav -c 2 ================================================================================ STEP 4: CHECK IF SPEAKERS ARE MUTED IN ALSA MIXER ================================================================================ $ alsamixer Press F6 and select your sound card (Generic_1 or CX11970). Check these channels: - Master - PCM - Speaker - Headphone If any shows "MM" (muted), press M on the keyboard to unmute. Use the arrow keys to set volume to approximately 80%. ================================================================================ STEP 5: AUTOMATIC STARTUP SCRIPT ================================================================================ To automate the fix at every system startup, create a script: $ mkdir -p ~/bin $ nano ~/bin/fix-audio.sh Paste the following content: ----------------------------------------------------------------------------- #!/bin/bash # Audio fix script for Huawei AMD sleep 30 # Reset ALSA sudo alsactl init 2>/dev/null # Restart PipeWire systemctl --user restart pipewire pipewire-pulse 2>/dev/null # Force speaker output pactl set-card-profile alsa_card.pci-0000_02_00.6 output:analog-stereo+input:analog-stereo 2>/dev/null pactl set-default-sink alsa_output.pci-0000_02_00.6.analog-stereo 2>/dev/null pactl set-sink-volume alsa_output.pci-0000_02_00.6.analog-stereo 80% 2>/dev/null pactl set-sink-mute alsa_output.pci-0000_02_00.6.analog-stereo 0 2>/dev/null echo "$(date) - Audio fixed" >> /tmp/fix-audio.log ----------------------------------------------------------------------------- $ chmod +x ~/bin/fix-audio.sh ================================================================================ STEP 6: ADD SCRIPT TO AUTOSTART ================================================================================ $ nano ~/.config/autostart/fix-audio.desktop Paste (replace [USER] with your username): ----------------------------------------------------------------------------- [Desktop Entry] Type=Application Name=Fix Audio Exec=/home/[USER]/bin/fix-audio.sh Icon=audio-card X-GNOME-Autostart-enabled=true ----------------------------------------------------------------------------- ================================================================================ STEP 7: ALLOW SUDO WITHOUT PASSWORD (OPTIONAL) ================================================================================ To allow the script to run without asking for a password: $ sudo visudo -f /etc/sudoers.d/fix-audio Add (replace [USER] with your username): ----------------------------------------------------------------------------- [USER] ALL=(ALL) NOPASSWD: /home/[USER]/bin/fix-audio.sh ----------------------------------------------------------------------------- ================================================================================ STEP 8: DESKTOP SHORTCUT FOR QUICK FIX ================================================================================ Create a desktop shortcut to fix audio with one click: $ nano ~/Desktop/Fix-Audio.desktop Paste: ----------------------------------------------------------------------------- [Desktop Entry] Type=Application Name=Fix Audio Exec=gnome-terminal -- bash -c "sudo alsactl init; systemctl --user restart pipewire pipewire-pulse; pactl set-default-sink alsa_output.pci-0000_02_00.6.analog-stereo; pactl set-sink-volume alsa_output.pci-0000_02_00.6.analog-stereo 80%; echo 'Audio fixed!'; read -p 'Press Enter'" Icon=audio-card Terminal=true ----------------------------------------------------------------------------- $ chmod +x ~/Desktop/Fix-Audio.desktop ================================================================================ STEP 9: RESET PIPEWIRE CONFIGURATION (IF OTHER METHODS FAIL) ================================================================================ If none of the above methods work, perform a full PipeWire reset: $ systemctl --user stop pipewire pipewire-pulse $ rm -rf ~/.config/pipewire $ rm -rf ~/.config/pulse $ rm -rf ~/.local/state/wireplumber $ rm -rf ~/.cache/pipewire $ systemctl --user start pipewire pipewire-pulse Then repeat Step 3. ================================================================================ STEP 10: INSTALL PAVUCONTROL (GRAPHICAL AUDIO MANAGEMENT TOOL) ================================================================================ $ sudo apt install pavucontrol Run: $ pavucontrol Go to the "Output Devices" tab: - Find the CX11970 device (or similar) - Click the green checkmark (Set as default) - In the "Port" dropdown, select "Speaker" instead of "Headphones" ================================================================================ DIAGNOSTICS - HOW TO CHECK WHAT'S WRONG ================================================================================ Check if the sound card is detected: $ aplay -l Check device status: $ pactl list short sinks Check available ports: $ pactl list cards | grep -A 20 "CX11970" Check kernel logs: $ dmesg | grep -i "snd\|audio\|hda" Check loaded modules: $ lsmod | grep snd ================================================================================ COMPARING "GOOD" AND "BAD" STATES ================================================================================ Save "good" state (when audio works): $ sudo cp -r /etc/modprobe.d /tmp/modprobe.d.good $ sudo cp -r /etc/modules-load.d /tmp/modules-load.d.good $ sudo cp -r /etc/pulse /tmp/pulse-system.good $ sudo cp -r /usr/share/pipewire /tmp/pipewire-share.good $ lsmod | grep snd > /tmp/snd-modules.good Save "bad" state (when audio does NOT work): $ sudo cp -r /etc/modprobe.d /tmp/modprobe.d.bad $ sudo cp -r /etc/modules-load.d /tmp/modules-load.d.bad $ sudo cp -r /etc/pulse /tmp/pulse-system.bad $ sudo cp -r /usr/share/pipewire /tmp/pipewire-share.bad $ lsmod | grep snd > /tmp/snd-modules.bad Compare states: $ diff -r /tmp/modprobe.d.good /tmp/modprobe.d.bad $ diff -r /tmp/modules-load.d.good /tmp/modules-load.d.bad $ diff -r /tmp/pulse-system.good /tmp/pulse-system.bad $ diff -r /tmp/pipewire-share.good /tmp/pipewire-share.bad $ diff /tmp/snd-modules.good /tmp/snd-modules.bad If diff shows no differences - the problem is in hardware registers. ================================================================================ WHAT DOES NOT WORK - WHAT NOT TO TRY ================================================================================ The following solutions have been tested and failed: | Method | Why It Failed | |--------|---------------| | Cron @reboot with delay | Runs too early | | Systemd service after sound.target | Runs before BIOS state is fully applied | | Disabling suspend in WirePlumber | Does not address hardware register state | | Blacklisting ACP modules | Does not reset hardware state | | Kernel parameters | Cannot override hardware register state | | Watchdog scripts | BIOS does not create configuration files | ================================================================================ ADDITIONAL INFORMATION - ROOT CAUSE OF THE PROBLEM ================================================================================ The problem occurs because BIOS/UEFI during initialization writes the audio controller state to hardware registers. Linux reads this state and applies it, which causes speakers to be marked as "unavailable." The state is stored in HARDWARE REGISTERS which: - Are not accessible via software tools - Are only reset during a full POST (Power-On Self-Test) - Are not dependent on configuration files This is why software solutions (scripts, file modifications) cannot fix the problem if the cause is in the hardware registers. ================================================================================ SUMMARY - MOST EFFECTIVE SOLUTIONS ================================================================================ 1. SYSTEM RESTART - always restores audio $ sudo reboot 2. MANUAL FIX - when restart doesn't help $ sudo alsactl init $ systemctl --user restart pipewire pipewire-pulse $ pactl set-default-sink alsa_output.pci-0000_02_00.6.analog-stereo 3. STARTUP SCRIPT - automate the fix Create ~/bin/fix-audio.sh and add to autostart 4. DESKTOP SHORTCUT - one-click quick fix ================================================================================ IMPORTANT NOTE - THE F12 / F2 BIOS ISSUE ================================================================================ During extensive testing, a critical discovery was made regarding how the problem is triggered: | BIOS Entry Method | Effect on Audio | |-------------------|-----------------| | F12 (boot device selection menu) | ❌ Speaker audio STOPS WORKING | | F2 (BIOS configuration / boot order) | ✅ Audio remains INTACT | THIS MEANS: - Entering BIOS itself is NOT the problem - The problem is the SPECIFIC hardware initialization mechanism used by F12 - If you need to change boot settings - use F2, not F12 HOW THIS WORKS: 1. BIOS/UEFI via F12 initializes the audio controller in a specific mode 2. This state is written to hardware registers 3. Linux reads and applies this state 4. The state causes speakers to be marked as "unavailable" 5. The system defaults to headphones as output RECOMMENDATION: - Avoid using F12 (boot menu) unless absolutely necessary - Use F2 (BIOS configuration) to change boot order - If you must use F12, perform a full restart without entering BIOS afterward -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2073049 Title: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression] Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: This laptop has had non-functioning internal sound (based on AMD Renoir) until Ubuntu 24.04, which made it work thanks to a bugfix in the kernel. Unfortunately, the sound is completely broken with kernel from package "linux-image-6.8.0-38-generic" (6.8.0-38.38): the internal speakers are not even listed in the sound GUI (I am using "mate-volume- control", with Ubuntu-Mate. When I boot the laptop on Linux 6.8.0-36-generic, the speakers are listed and the sound works normally. This might be related to this bug in Linux kernel: https://bugzilla.kernel.org/show_bug.cgi?id=218959 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-38-generic 6.8.0-38.38 ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/seq: julier 2643 F.... pipewire  /dev/snd/pcmC0D3p: julier 2643 F...m pipewire  /dev/snd/controlC0: julier 2645 F.... wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Jul 14 11:03:18 2024 InstallationDate: Installed on 2022-04-18 (818 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220418) MachineType: HUAWEI HVY-WXX9 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic root=UUID=e5259488-061f-48f2-b6ca-9ebd58053ca3 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions:  linux-restricted-modules-6.8.0-38-generic N/A  linux-backports-modules-6.8.0-38-generic N/A  linux-firmware 20240318.git3b128b60-0ubuntu2.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-28 (76 days ago) dmi.bios.date: 03/17/2023 dmi.bios.release: 2.17 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.17 dmi.board.asset.tag: N/A dmi.board.name: HVY-WXX9-PCB-B1 dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 2.17 dmi.modalias: dmi:bvnHUAWEI:bvr2.17:bd03/17/2023:br2.17:efr2.17:svnHUAWEI:pnHVY-WXX9:pvrM1010:rvnHUAWEI:rnHVY-WXX9-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook D dmi.product.name: HVY-WXX9 dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI [Impact] Huawei MateBook D14 AMD got no sound after commit: 4af565de9f8c ("ASoC: amd: acp: fix for acp pdm configuration check") which is introduced in v6.8.5 stable updates. [Fix] Invokes platform specific acp pin configuration check functions. Upstream fix: 09068d624c490 ("ASoC: amd: acp: fix for acp platform device creation failure") [Test] Bug reporter tested on hardware, sound output OK. Also verified on ThinkPad T14 AMD, sound output OK too. [Where problems could occur] It may break sound output of AMD platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073049/+subscriptions

[Bug 2147556] Re: Logitech, Inc. HD Pro Webcam C920 no longer works

Solved in 7.0.0-29-generic ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2147556 Title: Logitech, Inc. HD Pro Webcam C920 no longer works Status in linux package in Ubuntu: Fix Released Bug description: This logitech webcam has been working for years in Ubuntu. Something broke after kernel 6.11.11 : 046d:082d Logitech, Inc. HD Pro Webcam C920 I'm currently at 6.17.20.20. Somewhere in the interim there was one kernel that worked with this device, but all others kernels do not work. ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: linux-image-6.17.0-20-generic 6.17.0-20.20 ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13 Uname: Linux 6.17.0-20-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: kms 5813 F.... wireplumber /dev/snd/controlC0: kms 5806 F.... pipewire kms 5813 F.... wireplumber /dev/snd/seq: kms 5806 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 18:23:34 2026 InstallationDate: Installed on 2021-10-12 (1639 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Latitude 7320 Detachable ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-20-generic root=UUID=b5bc6390-52a3-4ffc-9214-018cf62caeb4 ro quiet splash i915.enable_psr=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 RelatedPackageVersions: firmware-sof N/A linux-firmware 20250901.git993ff19b-0ubuntu1.9 SourcePackage: linux UpgradeStatus: Upgraded to questing on 2025-11-03 (156 days ago) dmi.bios.date: 12/23/2025 dmi.bios.release: 1.45 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.45.0 dmi.board.name: 0TNW0H dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 32 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.45.0:bd12/23/2025:br1.45:svnDellInc.:pnLatitude7320Detachable:pvr:rvnDellInc.:rn0TNW0H:rvrA01:cvnDellInc.:ct32:cvr:sku0A45: dmi.product.family: Latitude dmi.product.name: Latitude 7320 Detachable dmi.product.sku: 0A45 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2024-11-22T14:15:34.725524 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147556/+subscriptions

[Bug 2163551] [NEW] Intel Raptor Lake xHCI stalls with stale USB devices; USB input and external display freeze, i8042 keyboard also stops responding

Public bug reported: System: Ubuntu desktop on ASUS laptop Kernel: 7.0.0-29-generic Summary: During normal desktop use, USB input stopped functioning. The external USB keyboard and USB wireless mouse both stopped responding, while the built-in I2C touchpad continued to work. At approximately 2026-08-14 19:27 EDT I captured the system while it was in the failed state. The affected USB devices were still enumerated by lsusb and registered as Linux input devices with usbhid bound: - Intel Raptor Lake USB 3.2 Gen 2x2 xHCI controller: 0000:00:14.0 - USB wireless mouse: usb-0000:00:14.0-6, /dev/input/event12 - USB keyboard: usb-0000:00:14.0-1.2.4, /dev/input/event6 Both event devices remained present but produced no input events. Testing the raw event devices with: sudo timeout 10s od -An -tx1 /dev/input/event12 sudo timeout 10s od -An -tx1 /dev/input/event6 produced no data while moving/clicking the mouse or pressing keyboard keys. I then physically unplugged USB devices, including an external USB optical drive and other peripherals. The disconnected devices continued to appear in lsusb. This suggests that the kernel USB topology had become stale and disconnect events were no longer being processed. A second external monitor also froze, continuing to display its last image. The external displays are connected through a USB/USB-C HDMI adapter/dock. The built-in touchpad continued working throughout. It is an I2C HID device and is not connected through xHCI. Recovery test: I unbound and rebound the Intel xHCI controller: echo -n '0000:00:14.0' | sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind sleep 3 echo -n '0000:00:14.0' | sudo tee /sys/bus/pci/drivers/xhci_hcd/bind After rebinding xhci_hcd: - the USB mouse immediately worked again - USB devices could be reconnected normally - the external USB keyboard worked again - the previously frozen second monitor began working again However, the laptop's built-in keyboard remained nonfunctional. The built-in keyboard is separately registered as: AT Raw Set 2 keyboard /sys/devices/platform/i8042/serio0/ driver: /sys/bus/serio/drivers/atkbd It also produced no usable keyboard input. Unbinding and rebinding atkbd: echo -n serio0 | sudo tee /sys/bus/serio/drivers/atkbd/unbind sleep 2 echo -n serio0 | sudo tee /sys/bus/serio/drivers/atkbd/bind did NOT restore the laptop keyboard. The I2C touchpad remained functional. A search of the kernel journal during the failure for: i8042|serio|atkbd|keyboard|xhci|usb|hid|irq|interrupt|ACPI|timeout|error produced no messages. Expected result: USB devices should continue processing input and disconnect events. The built-in keyboard should remain functional. External displays should not freeze. Actual result: The Intel xHCI/USB path stopped processing input/disconnect activity while devices remained enumerated. An external display froze simultaneously. Resetting xhci_hcd restored the USB devices and external display, but the separate i8042/atkbd laptop keyboard remained nonfunctional. Additional observation: I have previously experienced external-display corruption when monitors are connected through the same USB/USB-C HDMI adapter/dock. I do not yet know whether those incidents have the same root cause, but I am including this as a potentially relevant correlation. Reproducibility: Not yet intentionally reproduced. This occurred during normal use with multiple USB peripherals/hubs and external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 19:43:44 2026 IwDevWlo1Link: Not connected. MachineType: ASUSTeK COMPUTER INC. ROG Strix G18 G814JVR_G814JVR ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=ZFS=UbuntuZFS/root ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-05 (70 days ago) WifiSyslog: dmi.bios.date: 10/24/2024 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G814JVR.320 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G814JVR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.49 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG814JVR.320:bd10/24/2024:br5.27:efr0.49:svnASUSTeKCOMPUTERINC.:pnROGStrixG18G814JVR_G814JVR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG814JVR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaROGStrixG18: dmi.product.family: ROG Strix G18 dmi.product.name: ROG Strix G18 G814JVR_G814JVR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Attachment added: "full-journal.txt" https://bugs.launchpad.net/bugs/2163551/+attachment/5992266/+files/full-journal.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163551 Title: Intel Raptor Lake xHCI stalls with stale USB devices; USB input and external display freeze, i8042 keyboard also stops responding Status in linux package in Ubuntu: New Bug description: System: Ubuntu desktop on ASUS laptop Kernel: 7.0.0-29-generic Summary: During normal desktop use, USB input stopped functioning. The external USB keyboard and USB wireless mouse both stopped responding, while the built-in I2C touchpad continued to work. At approximately 2026-08-14 19:27 EDT I captured the system while it was in the failed state. The affected USB devices were still enumerated by lsusb and registered as Linux input devices with usbhid bound: - Intel Raptor Lake USB 3.2 Gen 2x2 xHCI controller: 0000:00:14.0 - USB wireless mouse: usb-0000:00:14.0-6, /dev/input/event12 - USB keyboard: usb-0000:00:14.0-1.2.4, /dev/input/event6 Both event devices remained present but produced no input events. Testing the raw event devices with: sudo timeout 10s od -An -tx1 /dev/input/event12 sudo timeout 10s od -An -tx1 /dev/input/event6 produced no data while moving/clicking the mouse or pressing keyboard keys. I then physically unplugged USB devices, including an external USB optical drive and other peripherals. The disconnected devices continued to appear in lsusb. This suggests that the kernel USB topology had become stale and disconnect events were no longer being processed. A second external monitor also froze, continuing to display its last image. The external displays are connected through a USB/USB-C HDMI adapter/dock. The built-in touchpad continued working throughout. It is an I2C HID device and is not connected through xHCI. Recovery test: I unbound and rebound the Intel xHCI controller: echo -n '0000:00:14.0' | sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind sleep 3 echo -n '0000:00:14.0' | sudo tee /sys/bus/pci/drivers/xhci_hcd/bind After rebinding xhci_hcd: - the USB mouse immediately worked again - USB devices could be reconnected normally - the external USB keyboard worked again - the previously frozen second monitor began working again However, the laptop's built-in keyboard remained nonfunctional. The built-in keyboard is separately registered as: AT Raw Set 2 keyboard /sys/devices/platform/i8042/serio0/ driver: /sys/bus/serio/drivers/atkbd It also produced no usable keyboard input. Unbinding and rebinding atkbd: echo -n serio0 | sudo tee /sys/bus/serio/drivers/atkbd/unbind sleep 2 echo -n serio0 | sudo tee /sys/bus/serio/drivers/atkbd/bind did NOT restore the laptop keyboard. The I2C touchpad remained functional. A search of the kernel journal during the failure for: i8042|serio|atkbd|keyboard|xhci|usb|hid|irq|interrupt|ACPI|timeout|error produced no messages. Expected result: USB devices should continue processing input and disconnect events. The built-in keyboard should remain functional. External displays should not freeze. Actual result: The Intel xHCI/USB path stopped processing input/disconnect activity while devices remained enumerated. An external display froze simultaneously. Resetting xhci_hcd restored the USB devices and external display, but the separate i8042/atkbd laptop keyboard remained nonfunctional. Additional observation: I have previously experienced external-display corruption when monitors are connected through the same USB/USB-C HDMI adapter/dock. I do not yet know whether those incidents have the same root cause, but I am including this as a potentially relevant correlation. Reproducibility: Not yet intentionally reproduced. This occurred during normal use with multiple USB peripherals/hubs and external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 19:43:44 2026 IwDevWlo1Link: Not connected. MachineType: ASUSTeK COMPUTER INC. ROG Strix G18 G814JVR_G814JVR ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=ZFS=UbuntuZFS/root ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-05 (70 days ago) WifiSyslog: dmi.bios.date: 10/24/2024 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G814JVR.320 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G814JVR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.49 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG814JVR.320:bd10/24/2024:br5.27:efr0.49:svnASUSTeKCOMPUTERINC.:pnROGStrixG18G814JVR_G814JVR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG814JVR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaROGStrixG18: dmi.product.family: ROG Strix G18 dmi.product.name: ROG Strix G18 G814JVR_G814JVR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163551/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp-6.8/6.8.0-1067.75~22.04.1)

All autopkgtests for the newly accepted linux-restricted-modules-gcp-6.8 (6.8.0-1067.75~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-gcp-6.8 [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions

[Bug 1117804] Re: ausearch doesn't show AppArmor denial messages

Hello Tyler, or anyone else affected, Accepted audit into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/audit/1:3.1.2-2.1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: audit (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed-noble ** Changed in: audit (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1117804 Title: ausearch doesn't show AppArmor denial messages Status in AppArmor: Confirmed Status in audit package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in audit source package in Jammy: Fix Committed Status in audit source package in Noble: Fix Committed Status in audit source package in Questing: Won't Fix Status in audit source package in Resolute: Fix Committed Status in audit source package in Stonking: Fix Released Bug description: [ Impact ]  * The following command should display all AppArmor AVC events: `ausearch --message AVC`; however, it doesn't work: ``` yachie@virtual:/etc/apparmor.d$ ausearch --message AVC <no matches> ```  * Users currently must inspect `/var/log/audit.log` to find the missing AppArmor AVC events: ``` yachie@virtual:/etc/apparmor.d$ sudo cat /var/log/audit.log type=AVC msg=audit(1774470501.870:1117918): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/proc/2009624/cmdline" pid=106062 comm="in:imuxsock" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 FSUID="root" OUID="root" type=AVC msg=audit(1774470501.927:1117919): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/proc/2009636/cmdline" pid=106062 comm="in:imuxsock" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 FSUID="root" OUID="root" ```  * The root cause is that `ausearch` is checking for a `tclass` field in the AppArmor events, because AppArmor is using event id `1400` (assigned to SELinux) instead of `1500`.  * AppArmor events don't have a `tclass` field, so `ausearch` treats every AppArmor event as 'malformed' and hides them. We can reveal the 'malformed' events with the `--debug` flag:  ``` yachie@virtual:~$ ausearch --message AVC --debug ( ... a ton of unrelated events ... ) Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.176:616): apparmor="AUDIT" operation="change_onexec" class="file" info="change_profile unprivileged unconfined converted to stacking" profile="unconfined" name="lsb_release" pid=5443 comm="aa-exec" Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:617): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/nsswitch.conf" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:618): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/passwd" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:619): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/bash.bashrc" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:620): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/home/yachie/.bashrc" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:621): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/home/yachie/.bash_history" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:622): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/home/yachie/.bash_history" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:623): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/inputrc" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 <no matches>  ```  * This bug makes `auditd` very difficult to use on Ubuntu: having the `auditd` package installed hides AVC events from the kernel log AND `ausearch` doesn't reveal them, making AppArmor events seemingly vanish unless you know where to look. [ Test plan ] # Install the relevant packages 1. sudo apt install apparmor auditd # Run the reproducer 2. aa-exec --profile=lsb_release bash # generates a ton of denials; see below: ``` root@jammy-vm:~# aa-exec --profile lsb_release bash bash: /etc/bash.bashrc: Permission denied bash: /root/.bashrc: Permission denied bash-5.1# exit ``` # Run `ausearch` and search for AVC events 3. ausearch --message AVC 3a. Unpatched package output (fail): ``` root@jammy-vm:~# ausearch --message AVC <no matches> ``` 3b. Patched package output (success): ``` root@jammy-vm:~# ausearch --message AVC ---- time->Tue Jul 14 21:03:18 2026 type=PROCTITLE msg=audit(1784062998.789:100): proctitle="bash" type=SYSCALL msg=audit(1784062998.789:100): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7f6a7274c150 a2=80000 a3=0 items=0 ppid=562 pid=3449 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=4294967295 comm="bash" exe="/usr/bin/bash" subj=lsb_release key=(null) type=AVC msg=audit(1784062998.789:100): apparmor="DENIED" operation="open" profile="lsb_release" name="/etc/nsswitch.conf" pid=3449 comm="bash" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 ---- time->Tue Jul 14 21:03:18 2026 type=PROCTITLE msg=audit(1784062998.789:101): proctitle="bash" type=SYSCALL msg=audit(1784062998.789:101): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7f6a7274c2ac a2=80000 a3=0 items=0 ppid=562 pid=3449 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=4294967295 comm="bash" exe="/usr/bin/bash" subj=lsb_release key=(null) type=AVC msg=audit(1784062998.789:101): apparmor="DENIED" operation="open" profile="lsb_release" name="/etc/passwd" pid=3449 comm="bash" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 ---- ( ...continues ) ``` [ Where problems could occur ]  * Currently, all AppArmor events are treated as 'malformed' SELinux events when they are actually well-formed AppArmor events.  * This patch modifies the filtration behavior of `ausearch` by making the `tclass` field optional, thus making AppArmor events be treated as well-formed SELinux events.  * The regression risk with this patch is such that potentially well- formed events will be hidden by `ausearch` unintentionally, or truly malformed events will be allowed past the filter.  * One major caveat is that regressions with respect to actual SELinux events are difficult to test on Ubuntu; some malformed SELinux events would potentially be allowed through the filter with this patch, or well-formed SELinux events hidden. This patch essentially trades correctness in the SELinux case for correctness in the AppArmor case. [ Other info ]  * Debian likely doesn't want this patch, as Debian officially won't be making any changes until upstream does [3].  * Upstream AppArmor can't move their event id to the `1500` range any time soon. AppArmor was moved to the `1400` range to align with the Linux kernel LSM infrastructure [2].  * Upstream `auditd` (audit-userspace) doesn't have anything to fix because it's AppArmor that's sending the events down the wrong channel [6].  * This patch comes from SUSE; they've been carrying it for well over a decade [4], and they seem to still be carrying it even after switching to SELinux by default [5]. Targeted releases: All currently supported releases and all releases moving forward until AppArmor moves back to the `1500` event range or Ubuntu switches to SELinux by default. [1] Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726 [2] AA using 1400 reason: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726#39 [3] Debian `wontfix` closure: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726#88 [4] SUSE KB: https://support.scc.suse.com/s/kb/audit-log-file-that-has-the-apparmor-AVC-entries-that-ausearch-can-t-read-1583239408721?language=en_US [5] SUSE Patch: https://build.opensuse.org/projects/security/packages/audit/files/audit-ausearch-do-not-require-tclass.patch [6] Upstream audit-userspace bug report: https://github.com/linux-audit/audit-userspace/issues/351 [ Original bug (for posterity after over a decade) ] The following command should display all AVC denials: ausearch -m avc However, it doesn't work with AppArmor denials. Here's a quick test case to generate a denial, search for it with ausearch, and see that no messages are displayed: $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current cat: /proc/self/attr/current: Permission denied $ sudo ausearch -m avc -c cat <no matches> ausearch claims that there are no matches, but there's a matching audit message if you look in audit.log: type=AVC msg=audit(1360193426.539:64): apparmor="DENIED" operation="open" parent=8253 profile="/usr/sbin/tcpdump" name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1117804/+subscriptions

[Bug 2161635] Re: shutdown hang. power and fans remain on forever

same bug ( shutdown hang. power and fans remain on forever ) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161635 Title: shutdown hang. power and fans remain on forever Status in linux package in Ubuntu: Confirmed Bug description: Intermittent shutdown hang — fans and power remain on for several minutes after shutdown is initiated, requiring a forced power-off. Appears to correlate with upgrade from kernel `7.0.0-27-generic` to `7.0.0-28-generic`. ## System Information - **Laptop:** Lenovo IdeaPad L340-15API, Type 81LW - **CPU/APU:** AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx (Picasso/Raven2, VBIOS 113-PICASSO-114) - **BIOS/UEFI:** ARCN37WW, dated 05/14/2021 — confirmed to be the latest version available from Lenovo for this model - **OS:** Kubuntu 26.04 LTS, KDE Plasma 6.6.5, Wayland session only (no X11) - **Kernel at time of both incidents:** `7.0.0-28-generic` - **Kernel previously in use for ~3 weeks with no incident:** `7.0.0-27-generic` ## Symptom A normal shutdown is initiated (via the desktop environment's shutdown menu). All applications and the session close normally, and the screen goes blank as expected. However, the laptop's fans and power/status continue running for an extended period afterward (~10 minutes observed) with no display output. The system does not respond to the power button being pressed briefly; holding it for ~10 seconds forces a full power-off. This has occurred at least five times, on separate dates, all while running kernel `7.0.0-28-generic`. It is intermittent and has not been reproduced on demand. ## Timeline / Possible Regression - Kernel upgraded from `7.0.0-27-generic` to `7.0.0-28-generic`: approximately 6 days before the first observed hang - No shutdown hang was observed at any point during the ~3 weeks of normal use on `7.0.0-27-generic` - All observed hangs occurred while running `7.0.0-28-generic` ## Log Evidence In all two incidents that was observed, the OS-level shutdown sequence completed fully and normally — `systemd-shutdown` reached its final logged steps (syncing filesystems, sending SIGTERM to remaining processes, journal stopping) in well under two seconds, with no hung services, timeouts, or errors within the shutdown sequence itself: ```markup systemd[1]: Reached target poweroff.target - System Power Off. systemd[1]: Shutting down. systemd-shutdown[1]: Syncing filesystems and block devices. systemd-shutdown[1]: Sending SIGTERM to remaining processes… systemd-journald[XXX]: Journal stopped ``` No further OS-level logging exists beyond this point in either incident, since journald stops at this stage by design. This indicates the hang occurs after the kernel/OS has finished its shutdown work and handed off control to firmware/hardware to actually power off — i.e., after the point where OS logging can capture anything further. **An anomaly present in both incidents' boot logs** (occurring at boot time, not at shutdown time, in each of the two affected boots): ```markup acpi PNP0C02:01: Could not reserve [io 0x0cf9] ``` Port `0xCF9` is the standard ACPI reset/power-off control register. The kernel reports being unable to reserve this I/O port at boot in both of the affected boots. It has not been confirmed whether this is causally related to the later shutdown hang, or a separate, possibly benign condition that happens to co-occur; it is the only anomaly of any kind found in either boot's logs relating to ACPI/power management. **Incident #2 additionally showed** a non-fatal timeout during the shutdown sequence: ```markup systemd[1]: user@1000.service: State 'stop-sigterm' timed out. Killing. systemd[1]: user@1000.service: Killing process 1410 (systemd) with signal SIGKILL. systemd[1]: user@1000.service: Killing process 1924 (obexd) with signal SIGKILL. systemd[1]: user@1000.service: Failed with result 'timeout'. ``` `obexd` is the Bluetooth OBEX object-exchange daemon. This timeout added a delay of several seconds to the shutdown sequence but did not by itself account for the full multi-minute hang, since the OS-level shutdown sequence still completed normally afterward (reaching `poweroff.target` as shown above). Checking a separate, unrelated boot (a normal desktop logout/login cycle, not a shutdown-hang incident) showed the same `user@1000.service`/`obexd` stop completing cleanly and quickly with no timeout, so this specific timeout was not confirmed to be a consistent, repeatable pattern. ## What Has Been Checked and Ruled out - USB and Ethernet Wake-on-LAN settings (`enp3s0`, and the USB interfaces associated with the wifi/Bluetooth combo chip, Qualcomm Atheros QCA9377) — checked directly via sysfs and already found to be `disabled` - A `powertop` report flagged several devices' wakeup settings as suboptimal for battery-life purposes — determined on inspection to be an unrelated battery-tuning recommendation, not connected to the shutdown hang - A manually-installed GRUB boot theme present on the system — confirmed to be cosmetic only (fonts and images, no scripts or kernel parameter changes) and unrelated - BIOS confirmed to already be at the latest version available from Lenovo for this model - Secure Boot was disabled during troubleshooting; no mechanism was identified connecting Secure Boot state to this issue, and no kernel modules or packages were found to have been blocked or held back as a result of it having previously been enabled - A BIOS setting called "Flip to Boot," reported elsewhere by other Lenovo IdeaPad owners as a fix for an outwardly identical symptom, was searched for in this laptop's BIOS but is not present as an available option on this model/BIOS revision - Kernel boot parameter `reboot=acpi` was tried as a mitigation (to prefer the ACPI-defined reset method) — this did **not** prevent recurrence; the hang occurred again with this parameter active, and the `0xCF9` reservation anomaly was still present in that boot's log, unchanged - Kernel boot parameter `amdgpu.gpu_recovery=1` was also in place during both incidents (added in response to a separate, unrelated `amdgpu` PSP firmware issue on this same machine) — did not appear to have any effect on this shutdown-hang issue either way ## Filesystem/data Safety Note In both observed incidents, disks were confirmed fully synced and filesystems unmounted (per the log excerpt above) before the hang began. Forcing a power-off via the power button at this stage has not resulted in any observed filesystem corruption or data loss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161635/+subscriptions

[Bug 2163506] Re: Integrated webcam (Chicony 04f2:b6cb) on Lenovo Yoga Slim 7 Pro 14IHU5 (model 82NC) doesnt work after upgrading to Ubuntu 24.04

## Summary Integrated webcam (Chicony 04f2:b6cb) on Lenovo Yoga Slim 7 Pro 14IHU5 (model 82NC) enumerates correctly, negotiates UVC formats, and streams isochronous packets with zero USB errors — but every video payload contains only the 12-byte UVC stream header and **no pixel data**. Camera indicator LED turns on, ealthy, but no application (ffmpeg, v4l2-ctl rawstream capture, Chrome/Google Meet, Zoom) ever receives a usable frame. This is a regression: the camera worked normally undeUbuntu 22.04 on this same machine, before upgradin ## System - Laptop: Lenovo Yoga Slim 7 Pro 14IHU5, system model 82NC, BIOS FJCN69WW - OS: Ubuntu 24.04.4 LTS (previously worked fine o) - Kernels tested: 6.8.0-137-generic (GA) and 6.14.0-37-generic (HWE) — **identical failure on both**, confirmed with matched usbmon captures on each (see below). This rules ouegression between 6.8 and 6.14; the break happenedsomewhere between 22.04's kernel/driver stack and 24.04's. - Camera: Chicony Electronics Integrated Camera, U bcdDevice 80.18 - Composite device: RGB sensor on interface 0/1 (UVC 1.10, /dev/video0-1), separate IR sensor on interface 2/3 (UVC 1.50, /dev/video2-3, used for Windows Hello / face auth format-negotiation failure, not the focus of thisreport) - Camera exposes 3 vendor Extension Units (XUs) r, which are typically used by the OEM Windowsdriver to perform proprietary sensor init: - XU 4: guid {1229a78c-47b4-4094-b0ce-db07386f - XU 7: guid {26b8105a-0713-4870-979d-da79444bb68e} - XU 8: guid {0f3f95dc-2632-4c4e-92c9-a04782f4 ## Possible IPU6 connection This machine also has an Intel IPU6 MIPI camera stack path available (`linux-modules-ipu6-generic-hwe-24.04` / `linux-modules-ipu6-6.14.0-37-generic` packages exring earlier troubleshooting the reporter installed and then removed/purged these IPU6 packages, without effect on the UVC camera's frame delivery either way (tested with them absent). It's possible the working 22.04 setup relr-init path (or an older `uvcvideo` with adevice-specific quirk/XU sequence) that isn't present in 24.04's stack — worth checking whether `linux-modules-ipu6-generic-hwe-24.04` (properly is the behavior, though it was not observed to helpin this case. Separately, and not the cause of the camera bug itself: removing the IPU6 packages had an unrelated destructive side effect — `linux-modules-extra-6.14.0-37-generic` (containinGPU/other drivers) was left uninstalled, breakingWiFi, touchpad, and display scaling specifically on 6.14 until reinstalled. That has been resolved and is mentioned only for completeness/context. ## Steps to reproduce v4l2-ctl -d /dev/video0 --set-fmt-video=width=640,height=480,pixelformat=YUYV --stream-mmap --stream-count=5 --stream-to=/tmp/ Result: hangs until interrupted; output file is 0 bytes. Same result via `ffmpeg -f v4l2 -i /dev/video0 ...` (both `mjpeg` and `yuyv422` input formats): ffmpeg opens the device,iption, but gets EOF with no decodable frame.Identical result on both 6.8.0-137-generic and 6.14.0-37-generic. ## Evidence: usbmon capture during a stream attempt Captured via `/sys/kernel/debug/usb/usbmon/3u` whioth kernels. USB control-plane traffic (formatprobe/commit, altsetting select) completes normally. Isochronous IN completions on endpoint 1 look like this, repeated for theentire capture with no errors, on **both** kernel C Zi:3:002:1 0:1:15352:0 32 0:0:12 0:2940:12 0:5880:12 0:8820:12 0:11760:12 94080 = 0c8c0000 000075c3 9f017d07 00000000... Every isochronous packet descriptor completes withual_length=12 bytes** — exactly the size of a bareUVC payload header (FID/EOF/PTS/SCR fields) with zero image bytes following it. This pattern is consistent across hundreds of isochronous packets captured on each kernel; no URcol errors anywhere in dmesg on either kernel. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163506 Title: Integrated webcam (Chicony 04f2:b6cb) on Lenovo Yoga Slim 7 Pro 14IHU5 (model 82NC) doesnt work after upgrading to Ubuntu 24.04 Status in linux package in Ubuntu: New Bug description: ## Summary Integrated webcam (Chicony 04f2:b6cb) on Lenovo Yoga Slim 7 Pro 14IHU5 (model 82NC) enumerates correctly, negotiates UVC formats, and streams isochronous packets with zero USB errors — but every video payload contains only the 12-byte UVC stream header and **no pixel data**. Camera indicator LED turns on, USB traffic looks nominally healthy, but no application (ffmpeg, v4l2-ctl raw stream capture, Chrome/Google Meet, Zoom) ever receives a usable frame. This is a regression: the camera worked normally before upgrading this machine from Ubuntu 22.04 to 24.04. ## System - Laptop: Lenovo Yoga Slim 7 Pro 14IHU5, system model 82NC, BIOS FJCN69WW - OS: Ubuntu 24.04.4 LTS - Kernels tested: 6.8.0-137-generic (GA) and 6.14.0-37-generic (HWE) — **both affected** - Camera: Chicony Electronics Integrated Camera, USB ID 04f2:b6cb, bcdUVC 1.10, bcdDevice 80.18 - Composite device: RGB sensor on interface 0/1 (UVC 1.10, /dev/video0-1), separate IR sensor on interface 2/3 (UVC 1.50, /dev/video2-3, used for Windows Hello / face auth — reproduces its own distinct format-negotiation failure, not the focus of this report) - Camera exposes 3 vendor Extension Units (XUs) in its VideoControl descriptor, which are typically used by the OEM Windows driver to perform proprietary sensor init: - XU 4: guid {1229a78c-47b4-4094-b0ce-db07386fb938} - XU 7: guid {26b8105a-0713-4870-979d-da79444bb68e} - XU 8: guid {0f3f95dc-2632-4c4e-92c9-a04782f43bc8} ## Steps to reproduce ``` v4l2-ctl -d /dev/video0 --set-fmt-video=width=640,height=480,pixelformat=YUYV \ --stream-mmap --stream-count=5 --stream-to=/tmp/raw_test.yuv ``` Result: hangs until interrupted; output file is 0 bytes. Same result via `ffmpeg -f v4l2 -i /dev/video0 ...` (both `mjpeg` and `yuyv422` input formats): ffmpeg opens the device, receives format/stream description, but gets EOF with no decodable frame. ## Evidence: usbmon capture during a stream attempt Captured via `/sys/kernel/debug/usb/usbmon/3u` while streaming was active. USB control-plane traffic (format probe/commit, altsetting select) completes normally. Isochronous IN completions on endpoint 1 look like this, repeated for the entire capture with no errors: ``` C Zi:3:002:1 0:1:15352:0 32 0:0:12 0:2940:12 0:5880:12 0:8820:12 0:11760:12 94080 = 0c8c0000 000075c3 9f017d07 00000000... ``` Every isochronous packet descriptor completes with status 0 (success) but **actual_length=12 bytes** — exactly the size of a bare UVC payload header (FID/EOF/PTS/SCR fields) with zero image bytes following it. This pattern is consistent across ~475 isochronous packets captured; no URB errors, no babble, no protocol errors anywhere in dmesg. ## What's been ruled out - USB autosuspend (device was suspending; disabling via udev `power/control=on` fixed an earlier separate symptom — the browser's "camera not found" error disappeared once the device reliably stays powered — but did not fix frame delivery) - `uvcvideo quirks=128` (UVC_QUIRK_FIX_BANDWIDTH) — no effect - `power_line_frequency` control (known bug class on other Lenovo-integrated cameras, see kernel patch "media: uvcvideo: Fix power line control for Lenovo Integrated Camera" for Shine-Optics 3277:009e) — set explicitly via v4l2-ctl, no effect - Lenovo EC camera-power gate (`/sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/camera_power`) — toggled off/on, no effect, reads `1` (enabled) - No physical privacy shutter on this model; no dedicated Fn camera-toggle hotkey found - No pending firmware updates for "Integrated Camera" via fwupd/LVFS - Fresh `modprobe -r uvcvideo && modprobe uvcvideo` before each test to rule out stale driver state - GNOME camera privacy toggle off (not blocking), correct udev ACL for /dev/video0, no other process holding the device open, no `/etc/modprobe.d` blacklist affecting uvcvideo/i2c_hid/psmouse ## Working theory The three vendor Extension Units suggest the OEM Windows driver performs a proprietary init/wake sequence on the sensor via one of these XUs before it will actually output pixel data. `uvcvideo`'s generic UVC negotiation (probe/commit/altsetting) succeeds because that part of the protocol is standard, but without the correct XU command sequence the sensor silently stays in a "streaming but dark" state — it acknowledges the stream request and sends header-only payloads, but never activates actual pixel readout. Since this camera reportedly worked under this same laptop before upgrading Ubuntu 22.04 → 24.04, something changed (kernel version, uvcvideo driver behavior, or firmware quirk table) between the two setups; a bisect against the 22.04 kernel/driver version would help narrow this down further. ## Requested - Guidance on whether a uvcvideo quirk/XU-init patch is feasible for this device, similar to the existing "Fix power line control for Lenovo Integrated Camera" precedent - Any pointers to existing bug reports for Chicony 04f2:b6cb or Lenovo model 82NC camera issues ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-137-generic 6.8.0-137.137 ProcVersionSignature: Ubuntu 6.8.0-137.137-generic 6.8.12 Uname: Linux 6.8.0-137-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: raghu 3845 F.... pipewire raghu 3849 F.... wireplumber /dev/snd/seq: raghu 3845 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 20:28:25 2026 HibernationDevice: RESUME=none InstallationDate: Installed on 2023-05-23 (1179 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: LENOVO 82NC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_px4ncd@/vmlinuz-6.8.0-137-generic root=ZFS=rpool/ROOT/ubuntu_px4ncd ro quiet splash i8042.direct i8042.dumbkbd RelatedPackageVersions: linux-restricted-modules-6.8.0-137-generic N/A linux-backports-modules-6.8.0-137-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.29 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2022 dmi.bios.release: 1.69 dmi.bios.vendor: LENOVO dmi.bios.version: FJCN69WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76485 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 Pro 14IHU5 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrFJCN69WW:bd03/21/2022:br1.69:efr1.31:svnLENOVO:pn82NC:pvrYogaSlim7Pro14IHU5:rvnLENOVO:rnLNVNB161216:rvrSDK0T76485WIN:cvnLENOVO:ct10:cvrYogaSlim7Pro14IHU5:skuLENOVO_MT_82NC_BU_idea_FM_YogaSlim7Pro14IHU5: dmi.product.family: Yoga Slim 7 Pro 14IHU5 dmi.product.name: 82NC dmi.product.sku: LENOVO_MT_82NC_BU_idea_FM_Yoga Slim 7 Pro 14IHU5 dmi.product.version: Yoga Slim 7 Pro 14IHU5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163506/+subscriptions