[РЕШЕНО] Ошибка № ...

среда

[Bug 2147585] Lspci.txt

apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2147585/+attachment/5985280/+files/Lspci.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2147585 Title: No sound from AMD ACP70 audio on ASUS TUF Gaming A14 FA401EA (Ryzen AI MAX+) Status in linux package in Ubuntu: Confirmed Bug description: ## System Information - Laptop: ASUS TUF Gaming A14 FA401EA - CPU: AMD Ryzen AI MAX+ 392 (Strix Point) with Radeon 8060S - Audio Device: AMD Audio Coprocessor (ACP70) - PCI ID 1022:15E2 - Subsystem: ASUSTeK Computer Inc. Device 1724 - Distribution: Ubuntu 25.10 (Questing Quokka) - Tested Kernels: 6.17.x, 6.18.x, 6.19.x, 7.0-rc7 ## Issue Description Internal speakers and headphone jack not working - only HDMI audio works. ## Symptoms - /proc/asound/cards only shows HDA Intel HDMI audio (card 0) - AMD ACP70 device detected in lspci (64:00.5) but no sound card created - Platform device acp_asoc_acp70.0 exists but has no playback devices - All ACP70 kernel modules load correctly but no audio card appears ## Expected Behavior Internal speakers and headphone jack should work like on Windows. ## lspci -v -s 64:00.5: 64:00.5 Multimedia controller: AMD Audio Coprocessor (rev 70) Subsystem: ASUSTeK Computer Inc. Device 1724 Kernel driver in use: snd_acp_pci ## Additional Information - HDMI audio works fine (card 0 - ATI R6xx HDMI) - USB audio devices work when plugged in - Similar issues reported for ASUS ProArt PX13 and other Strix Point devices - Bug #2117131 related to AMD ACP support in Ubuntu - This is a known upstream issue with AMD Strix Point (ACP70) --- ProblemType: Bug ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: jorge 2378 F.... pipewire jorge 2417 F.... wireplumber /dev/snd/controlC0: jorge 2417 F.... wireplumber /dev/snd/seq: jorge 2378 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2026-05-04 (79 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS TUF Gaming A14 FA401EA Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-ghostty XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.6-fa401ea root=UUID=b7a2fb2e-4f79-46e2-b537-230e08bc990c ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Tags: resolute wayland-session Uname: Linux 7.0.6-fa401ea x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd nordvpn plugdev render sudo users video _MarkForUpload: True dmi.bios.date: 01/28/2026 dmi.bios.release: 5.36 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FA401EA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA401EA 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: 3.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA401EA.304:bd01/28/2026:br5.36:efr3.3:svnASUS:pnTUFGamingA14FA401EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA401EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaTUFGamingA14: dmi.product.family: TUF Gaming A14 dmi.product.name: TUF Gaming A14 FA401EA dmi.product.version: 1.0 dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147585/+subscriptions

[Bug 2147585] Re: No sound from AMD ACP70 audio on ASUS TUF Gaming A14 FA401EA (Ryzen AI MAX+)

apport information ** Tags added: apport-collected resolute wayland-session ** Description changed: ## System Information - Laptop: ASUS TUF Gaming A14 FA401EA - CPU: AMD Ryzen AI MAX+ 392 (Strix Point) with Radeon 8060S - Audio Device: AMD Audio Coprocessor (ACP70) - PCI ID 1022:15E2 - Subsystem: ASUSTeK Computer Inc. Device 1724 - Distribution: Ubuntu 25.10 (Questing Quokka) - Tested Kernels: 6.17.x, 6.18.x, 6.19.x, 7.0-rc7 ## Issue Description Internal speakers and headphone jack not working - only HDMI audio works. ## Symptoms - /proc/asound/cards only shows HDA Intel HDMI audio (card 0) - AMD ACP70 device detected in lspci (64:00.5) but no sound card created - Platform device acp_asoc_acp70.0 exists but has no playback devices - All ACP70 kernel modules load correctly but no audio card appears ## Expected Behavior Internal speakers and headphone jack should work like on Windows. ## lspci -v -s 64:00.5: 64:00.5 Multimedia controller: AMD Audio Coprocessor (rev 70) Subsystem: ASUSTeK Computer Inc. Device 1724 Kernel driver in use: snd_acp_pci ## Additional Information - HDMI audio works fine (card 0 - ATI R6xx HDMI) - USB audio devices work when plugged in - Similar issues reported for ASUS ProArt PX13 and other Strix Point devices - Bug #2117131 related to AMD ACP support in Ubuntu - This is a known upstream issue with AMD Strix Point (ACP70) + --- + ProblemType: Bug + ApportVersion: 2.34.0-0ubuntu2 + Architecture: amd64 + AudioDevicesInUse: + USER PID ACCESS COMMAND + /dev/snd/controlC1: jorge 2378 F.... pipewire + jorge 2417 F.... wireplumber + /dev/snd/controlC0: jorge 2417 F.... wireplumber + /dev/snd/seq: jorge 2378 F.... pipewire + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 26.04 + InstallationDate: Installed on 2026-05-04 (79 days ago) + InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) + MachineType: ASUS TUF Gaming A14 FA401EA + Package: linux (not installed) + ProcEnviron: + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-ghostty + XDG_RUNTIME_DIR=<set> + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.6-fa401ea root=UUID=b7a2fb2e-4f79-46e2-b537-230e08bc990c ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M + ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 + Tags: resolute wayland-session + Uname: Linux 7.0.6-fa401ea x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin lxd nordvpn plugdev render sudo users video + _MarkForUpload: True + dmi.bios.date: 01/28/2026 + dmi.bios.release: 5.36 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: FA401EA.304 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: FA401EA + 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: 3.3 + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA401EA.304:bd01/28/2026:br5.36:efr3.3:svnASUS:pnTUFGamingA14FA401EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA401EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaTUFGamingA14: + dmi.product.family: TUF Gaming A14 + dmi.product.name: TUF Gaming A14 FA401EA + dmi.product.version: 1.0 + dmi.sys.vendor: ASUS ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2147585/+attachment/5985275/+files/AlsaInfo.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2147585 Title: No sound from AMD ACP70 audio on ASUS TUF Gaming A14 FA401EA (Ryzen AI MAX+) Status in linux package in Ubuntu: Confirmed Bug description: ## System Information - Laptop: ASUS TUF Gaming A14 FA401EA - CPU: AMD Ryzen AI MAX+ 392 (Strix Point) with Radeon 8060S - Audio Device: AMD Audio Coprocessor (ACP70) - PCI ID 1022:15E2 - Subsystem: ASUSTeK Computer Inc. Device 1724 - Distribution: Ubuntu 25.10 (Questing Quokka) - Tested Kernels: 6.17.x, 6.18.x, 6.19.x, 7.0-rc7 ## Issue Description Internal speakers and headphone jack not working - only HDMI audio works. ## Symptoms - /proc/asound/cards only shows HDA Intel HDMI audio (card 0) - AMD ACP70 device detected in lspci (64:00.5) but no sound card created - Platform device acp_asoc_acp70.0 exists but has no playback devices - All ACP70 kernel modules load correctly but no audio card appears ## Expected Behavior Internal speakers and headphone jack should work like on Windows. ## lspci -v -s 64:00.5: 64:00.5 Multimedia controller: AMD Audio Coprocessor (rev 70) Subsystem: ASUSTeK Computer Inc. Device 1724 Kernel driver in use: snd_acp_pci ## Additional Information - HDMI audio works fine (card 0 - ATI R6xx HDMI) - USB audio devices work when plugged in - Similar issues reported for ASUS ProArt PX13 and other Strix Point devices - Bug #2117131 related to AMD ACP support in Ubuntu - This is a known upstream issue with AMD Strix Point (ACP70) --- ProblemType: Bug ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: jorge 2378 F.... pipewire jorge 2417 F.... wireplumber /dev/snd/controlC0: jorge 2417 F.... wireplumber /dev/snd/seq: jorge 2378 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2026-05-04 (79 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: ASUS TUF Gaming A14 FA401EA Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-ghostty XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.6-fa401ea root=UUID=b7a2fb2e-4f79-46e2-b537-230e08bc990c ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Tags: resolute wayland-session Uname: Linux 7.0.6-fa401ea x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd nordvpn plugdev render sudo users video _MarkForUpload: True dmi.bios.date: 01/28/2026 dmi.bios.release: 5.36 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FA401EA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA401EA 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: 3.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA401EA.304:bd01/28/2026:br5.36:efr3.3:svnASUS:pnTUFGamingA14FA401EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA401EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaTUFGamingA14: dmi.product.family: TUF Gaming A14 dmi.product.name: TUF Gaming A14 FA401EA dmi.product.version: 1.0 dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147585/+subscriptions

[Bug 2161448] Re: mt7921u: USB Wi-Fi enters unrecoverable state after prolonged uptime; NetworkManager/supplicant stalls followed by USB disconnect deadlock

[Bug 2161148] Re: [SRU] intel_backlight (i915/eDP AUX-DPCD) stops responding to live brightness writes in 7.0.0-28-generic (works in 6.17.0-40-generic)

Thank you for the detailed report. Could you please provide the following? - From a boot where the problem occurred, open a terminal and copy and paste the command below. It will save the complete kernel log as dmesg.txt in your home folder. After the command finishes, attach that file to this bug: sudo dmesg > ~/dmesg.txt - While running an affected Ubuntu kernel, open a terminal and copy and paste the command below. It will add the diagnostic information directly to this report: apport-collect 2161148 This issue looks to be much alike https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161309, would you mind looking at comment #4 and #10 and possibly doing a few more checks? You'll need to revert any boot line params you have added and update grub to I can have a clear picture whether you are hitting exactly the same issue. Thanks! ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Krystian Kaniewski (kkaniewski) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161148 Title: [SRU] intel_backlight (i915/eDP AUX-DPCD) stops responding to live brightness writes in 7.0.0-28-generic (works in 6.17.0-40-generic) Status in linux package in Ubuntu: Incomplete Bug description: After the kernel update to 7.0.0-28-generic (HWE, arrived alongside a KDE Plasma update), the internal laptop screen brightness became stuck at maximum. The /sys/class/backlight/intel_backlight/brightness sysfs value still changes correctly (both via the KDE Plasma slider and via manual echo > brightness), and org.kde.powerdevil.backlighthelper is invoked successfully each time, but the physical panel brightness no longer follows the value at runtime. Booting the previous kernel (6.17.0-40-generic) with the exact same GRUB configuration (no special kernel parameters) restores correct behaviour immediately: both the slider and manual sysfs writes change the physical screen brightness as expected. This points to a regression in the i915 driver's eDP AUX/DPCD backlight write path in 7.0.0-28-generic, not an issue with KDE Plasma/powerdevil (which was ruled out — see tests below). System information Laptop: Dell Vostro 15 3510 GPU: Intel UHD Graphics G4 (Tiger Lake-LP GT2, 48EU) — i915 0000:00:02.0, device ID 9a78, "tigerlake/uy" OS: Ubuntu Noble 24.04 (KDE neon on top) Desktop: KDE Plasma (recently updated) Broken kernel: linux-image-7.0.0-28-generic (7.0.0-28.28~24.04.1, via linux-generic-hwe-24.04) Working kernel: linux-image-6.17.0-40-generic (6.17.0-40.40~24.04.1) GRUB config: default, no special parameters (GRUB_CMDLINE_LINUX_DEFAULT="quiet splash") Steps to reproduce (on 7.0.0-28-generic) Boot into 7.0.0-28-generic with a clean/default GRUB command line. Check the sysfs interface: ls /sys/class/backlight/ → intel_backlight cat /sys/class/backlight/intel_backlight/brightness cat /sys/class/backlight/intel_backlight/max_brightness → e.g. 410 / 1023 Change brightness via the KDE Plasma slider, or manually: echo 200 | sudo tee /sys/class/backlight/intel_backlight/brightness Observe: the sysfs value updates correctly (confirmed by reading it back), and org.kde.powerdevil.backlighthelper is activated successfully in the journal, but the physical screen brightness does not change — it stays at the level set at boot time by systemd-backlight. Steps to reproduce the working case (6.17.0-40-generic) Boot into 6.17.0-40-generic with the same, unmodified GRUB command line. Note the sysfs interface uses a different (raw PWM-like) brightness scale on this kernel, e.g. max_brightness in the tens of thousands rather than 1023. Repeat the same slider / manual echo test. Observe: the physical screen brightness follows the value correctly, both from the KDE Plasma slider and from manual sysfs writes. What we ruled out KDE Plasma / powerdevil is not at fault. org.kde.powerdevil.backlighthelper is called successfully via D-Bus/KAuth every time the slider is moved, on both kernels, and the sysfs value is written correctly in both cases. The failure is purely between "sysfs value" and "physical panel output", which is below the desktop environment / kernel userspace boundary. Not a permissions issue. /sys/class/backlight/intel_backlight/brightness write succeeds (verified via direct sudo tee), the value persists when re-read. Tried acpi_backlight=native and acpi_backlight=vendor kernel parameters on 7.0.0-28-generic: acpi_backlight=vendor → intel_backlight sysfs interface disappears entirely (i915: [drm] Skipping intel_backlight registration in dmesg), no backlight class device is exposed at all on this hardware. acpi_backlight=native → interface present, sysfs value changes, but no physical brightness change (same broken behaviour as default). Tried i915.enable_dpcd_backlight=1 and =3 (note: per modinfo i915, this parameter is actually boolean, so both likely evaluated to the same "enabled" state) combined with acpi_backlight=native: Fixed the boot-time initial brightness (screen now dims to the value saved/restored by systemd-backlight at boot, instead of being stuck at 100%). Did not fix live/runtime updates — slider and manual sysfs writes still don't change the physical brightness after boot. dmesg during a live brightness write shows no relevant AUX/DPCD/backlight error messages on 7.0.0-28-generic (driver does not log at that verbosity by default) — happy to gather more verbose i915 debug logs if useful (e.g. via drm.debug). Expected behaviour Writing to /sys/class/backlight/intel_backlight/brightness (whether via the desktop environment or directly) should change the physical panel brightness at runtime, as it does on 6.17.0-40-generic with identical hardware and GRUB configuration. Actual behaviour On 7.0.0-28-generic, only the kernel's own boot-time backlight restoration (systemd-backlight@backlight:intel_backlight.service) succeeds in setting a correct initial physical brightness (and only when acpi_backlight=native i915.enable_dpcd_backlight=1 is set); all subsequent runtime writes to the sysfs brightness file are silently ignored by the hardware, even though the sysfs value itself updates. Current workaround Pinning/holding the working kernel as default via GRUB (GRUB_DEFAULT=saved + grub-set-default) and holding the linux- image-7.0.0-28-generic / linux-generic-hwe-24.04 packages to prevent apt from reactivating the broken kernel on the next update. Additional info available on request Full journalctl -b output around powerdevil/backlight activity on both kernels dmesg output on both kernels Willing to test additional kernel parameters or debug builds if it helps narrow down the regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161148/+subscriptions

[Bug 2161234] Re: Touchpad Unusable and Random Screen Freeze After Installing Linux

** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161234 Title: Touchpad Unusable and Random Screen Freeze After Installing Linux Status in linux package in Ubuntu: Confirmed Bug description: OS: Linux Mint 22.3 (based on Ubuntu 24.04 LTS) Kernel: 7.0.0-28-generic (Ubuntu HWE kernel) DE: Cinnamon Hardware: Laptop: LENOVO 21Q4 ThinkBook 14 G7+ ASP CPU: AMD Ryzen AI 9 H 365 w/ Radeon 880M (12 cores) GPU: AMD/ATI Device 150e (Radeon 880M iGPU) Touchpad: GXTP5100:00 27C6:01E9 (Goodix) The touchpad uses the I2C-HID protocol. Issue 1: Touchpad completely unresponsive Symptoms: The touchpad is detected by the system (xinput and dmesg show the device), but it does not respond to any touch or movement at the login screen and remains non-functional after login. This issue has occured when installing & using the OS. Issue 2: Random UI freezes Symptoms: After a random period (1 to 10 hours) of normal use, the UI freezes completely. The mouse cursor can still be moved using an external USB mouse, but clicking and keyboard shortcuts (e.g. Alt+F2) does not respond. Audio plays normally. Temporary Solution: Pressing Ctrl+Alt+Backspace to restart the UI session restores functionality temporarily. Steps to Reproduce: Install Linux Mint 22 (or any Ubuntu 24.04 based distro with kernel 6.8+, note that ALL kernels provided doesn't provide the solution to the problem). Boot into the system. The touchpad will not work from the login screen onwards. Use the system normally; the UI will freeze within 1-10 hours. --- ProblemType: Bug ApportVersion: 2.28.2-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 InstallationDate: Installed on 2026-03-08 (135 days ago) InstallationMedia: Linux Mint 22.3 "Zena" - Release amd64 20260108 IwConfig: lo no wireless extensions. enp98s0 no wireless extensions. wlp97s0 no wireless extensions. MachineType: LENOVO 21Q4 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-28-generic root=UUID=2e08b9c8-43cb-4c4e-8598-590d92bb4341 ro i8042.nopnp=1 i8042.direct=1 i2c_hid.ignore_quirk=1 systemd.mask=cloud-init.service systemd.mask=cloud-init-local.service amdgpu.sg_display=0 ProcVersionSignature: Ubuntu 7.0.0-28.28~24.04.1-generic 7.0.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-7.0.0-28-generic N/A linux-backports-modules-7.0.0-28-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 Tags: zena Uname: Linux 7.0.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 03/27/2025 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: PXCN25WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76577 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 14 G7+ ASP dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrPXCN25WW:bd03/27/2025:br1.25:efr1.25:svnLENOVO:pn21Q4:pvrThinkBook14G7+ASP:rvnLENOVO:rnLNVNB161216:rvrSDK0T76577WIN:cvnLENOVO:ct10:cvrThinkBook14G7+ASP:skuLENOVO_MT_21Q4_BU_idea_FM_ThinkBook14G7+ASP:pfaThinkBook14G7+ASP: dmi.product.family: ThinkBook 14 G7+ ASP dmi.product.name: 21Q4 dmi.product.sku: LENOVO_MT_21Q4_BU_idea_FM_ThinkBook 14 G7+ ASP dmi.product.version: ThinkBook 14 G7+ ASP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161234/+subscriptions

[Bug 2161102] Re: Regression: Intel TigerLake eDP backlight broken after Linux 7.0.0-27 (Dell Latitude 5420)

Thanks for reporting the bug and providing the logs already! This issue looks to be much alike https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161309, would you mind looking at comment #4 and #10 and possibly doing a few more checks? You'll need to revert any boot line params you have added and update grub to I can have a clear picture whether you are hitting exactly the same issue. Thanks! ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Krystian Kaniewski (kkaniewski) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161102 Title: Regression: Intel TigerLake eDP backlight broken after Linux 7.0.0-27 (Dell Latitude 5420) Status in linux package in Ubuntu: Confirmed Bug description: **Title** Regression: Intel TigerLake eDP backlight broken after Linux 7.0.0-27 on Dell Latitude 5420 --- ### Hardware * Laptop: Dell Latitude 5420 * BIOS: 1.54.1 * GPU: Intel TigerLake (i915) * Internal display: AU Optronics eDP panel * External display: Lenovo T2254pC (HDMI) --- ### Kernel versions Working: ``` 7.0.0-27-generic ``` Broken: ``` 7.0.0-28-generic ``` --- ### Description After upgrading from kernel 7.0.0-27 to 7.0.0-28, the internal laptop display brightness can no longer be controlled. The GNOME brightness slider still moves normally, but the panel brightness does not change. The external HDMI monitor continues to work normally. Booting back into kernel 7.0.0-27 immediately restores normal brightness control. This makes the issue appear to be a kernel regression. --- ### Working kernel ``` $ cat /sys/class/backlight/intel_backlight/max_brightness 96000 $ cat /sys/class/backlight/intel_backlight/brightness 96000 $ cat /sys/class/backlight/intel_backlight/actual_brightness 96000 ``` Brightness changes correctly. --- ### Broken kernel ``` $ cat /sys/class/backlight/intel_backlight/max_brightness 1023 $ cat /sys/class/backlight/intel_backlight/brightness 1023 $ cat /sys/class/backlight/intel_backlight/actual_brightness 1023 ``` Changing the brightness slider updates these values between 10 and 1023, but the physical panel brightness never changes. --- ### Additional information The internal panel is detected correctly. PSR is disabled: ``` PSR mode: disabled ``` The issue occurs only after updating to kernel 7.0.0-28. Rolling back to kernel 7.0.0-27 restores full functionality immediately without any other changes. This looks like a regression in Intel i915 eDP backlight handling. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ali-masroori 4129 F.... wireplumber /dev/snd/seq: ali-masroori 4113 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 17:22:16 2026 InstallationDate: Installed on 2026-05-30 (48 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. Latitude 5420 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=/boot/vmlinuz-7.0.0-28-generic root=UUID=483412b7-bd4f-4bbc-81f0-7ea79150a588 ro quiet splash i915.enable_dpcd_backlight=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2026 dmi.bios.release: 1.54 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.54.1 dmi.board.name: 01M3M4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.54.1:bd04/23/2026:br1.54:svnDellInc.:pnLatitude5420:pvr:rvnDellInc.:rn01M3M4:rvrA00:cvnDellInc.:ct10:cvr:sku0A20:pfaLatitude: dmi.product.family: Latitude dmi.product.name: Latitude 5420 dmi.product.sku: 0A20 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161102/+subscriptions

[Bug 2161309] Re: Backlight regression

Thanks Neal! It looks like 7.1.3 actually already had the fix included then. I'm now trying to make sure whether f30fddb4402313aa5301a74d721638d343395269 is a real fix here and also trace back first revision mainline kernel version it was applied to, but it can be a little bit difficult sometimes. Would you mind testing two more mainline kernels? 7.1-r5: https://kernel.ubuntu.com/mainline/v7.1-rc5/ - expected to fail 7.1-r7: https://kernel.ubuntu.com/mainline/v7.1-rc7/ - expected to pass -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161309 Title: Backlight regression Status in linux package in Ubuntu: Confirmed Bug description: ThinkPad T480 Intel UHD 620 brightness works on 7.0.0-27 brightness fails on 7.0.0-28 /sys/class/backlight/intel_backlight changes but panel does not ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: neal 3608 F.... wireplumber /dev/snd/seq: neal 3589 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 12:47:12 2026 InstallationDate: Installed on 2026-07-12 (8 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 20L6S6L601 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=1cea3fcd-0665-4cb4-a85a-4ebc58d5aed0 ro quiet splash acpi_backlight=native 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: 09/06/2025 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET81W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S6L601 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN24ET81W(1.56):bd09/06/2025:br1.56:efr1.22:svnLENOVO:pn20L6S6L601:pvrThinkPadT480:rvnLENOVO:rn20L6S6L601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT480:pfaThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S6L601 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161309/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-meta-azure-6.8/6.8.0-1063.71~22.04.1)

All autopkgtests for the newly accepted linux-meta-azure-6.8 (6.8.0-1063.71~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/unknown (arm64) dm-writeboost/2.2.13-1ubuntu4 (amd64) dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1 (amd64) evdi/unknown (arm64) glibc/2.35-0ubuntu3.13 (amd64, arm64) lime-forensics/1.9.1-3 (arm64) linux-azure-6.8/6.8.0-1063.71~22.04.1 (amd64, arm64) wireguard/unknown (arm64) 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-meta-azure-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 2161309] Re: Backlight regression

Hi, interestingly 7.1.3 doesn't have the regression in, both GNOME brightness control and keyboard buttons work as expected. uname -r is 7.1.3-070103-generic Neal -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161309 Title: Backlight regression Status in linux package in Ubuntu: Confirmed Bug description: ThinkPad T480 Intel UHD 620 brightness works on 7.0.0-27 brightness fails on 7.0.0-28 /sys/class/backlight/intel_backlight changes but panel does not ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: neal 3608 F.... wireplumber /dev/snd/seq: neal 3589 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 12:47:12 2026 InstallationDate: Installed on 2026-07-12 (8 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 20L6S6L601 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=1cea3fcd-0665-4cb4-a85a-4ebc58d5aed0 ro quiet splash acpi_backlight=native 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: 09/06/2025 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET81W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S6L601 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN24ET81W(1.56):bd09/06/2025:br1.56:efr1.22:svnLENOVO:pn20L6S6L601:pvrThinkPadT480:rvnLENOVO:rn20L6S6L601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT480:pfaThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S6L601 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161309/+subscriptions

вторник

[Bug 2156858] Re: [SRU] Fix GPU throttling limits on Strix Halo

[Bug 2156972] Re: Camera output is vague and color is abnormal

This bug was fixed in the package linux-oem-6.17 - 6.17.0-1030.30 --------------- linux-oem-6.17 (6.17.0-1030.30) noble; urgency=medium * noble/linux-oem-6.17: 6.17.0-1030.30 -proposed tracker (LP: #2160672) * Suspend resume time is too long on EliteBook 8 G1a 13 (LP: #2160183) - SAUCE: wifi: ath12k: avoid MHI deinit during suspend -- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 15 Jul 2026 13:49:00 +0800 ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: Fix Committed => 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/2156972 Title: Camera output is vague and color is abnormal Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux-oem-7.0 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux-oem-7.0 source package in Noble: Invalid Status in linux source package in Questing: Won't Fix Status in linux-oem-6.17 source package in Questing: Invalid Status in linux-oem-7.0 source package in Questing: Invalid Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux-oem-7.0 source package in Resolute: Fix Committed Status in linux source package in Stonking: In Progress Status in linux-oem-6.17 source package in Stonking: Invalid Status in linux-oem-7.0 source package in Stonking: Invalid Bug description: [SRU Justification] [Impact] The camera output is abnormal, and it takes longer time to start the camera. kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected [Fix] Upstream commit 477620dccf3e ("media: intel/ipu6: Improve DWC PHY HSFREQRANGE band selection for overlapping ranges") in v7.2-rc1 fixes commit 1e7eeb301696 ("media: intel/ipu6: add the CSI2 DPHY implementation") from v6.10. [Test Plan] 1. capture video stream and verify the video quality. $ gst-launch-1.0 v4l2src ! videoconvert ! avimux ! filesink location=out.avi 2. check no error found in dmesg $ sudo dmesg |grep intel_ipu6_isys [Where problems could occur] The regression can be considered as low, because the patch is meant to locate a band with higher osc_freq_target for best hardware utilization. No other part is touched. [Other Info] While this affects kernels >= v6.10, nominate for all the newer kernels. And since this is already in v7.2-rc1, skip Unstable. ========== original bug report ========== The camera output is abnormal, and it takes longer time to start the camera. I record the video by command: $ gst-launch-1.0 v4l2src ! videoconvert ! avimux ! filesink location=out.avi Some errors reported in the driver: kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Payload checksum (CRC) error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: DPHY recoverable synchronization error kernel: intel_ipu6_isys.isys intel_ipu6.isys.40: csi2-0 error: Single packet header error corrected Proposed fix was in https://github.com/intel/ipu6-drivers/pull/447. This affects kernel v6.10 and up, which added D-PHY implementation in commit 1e7eeb301696 ("media: intel/ipu6: add the CSI2 DPHY implementation"). It's then submitted into upstream as commit 477620dccf3e ("media: intel/ipu6: Improve DWC PHY HSFREQRANGE band selection for overlapping ranges") in v7.2-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156972/+subscriptions

[Bug 2158229] Re: MT7925 wifi is hard blocked on Dell's machine

This bug was fixed in the package linux-oem-6.17 - 6.17.0-1030.30 --------------- linux-oem-6.17 (6.17.0-1030.30) noble; urgency=medium * noble/linux-oem-6.17: 6.17.0-1030.30 -proposed tracker (LP: #2160672) * Suspend resume time is too long on EliteBook 8 G1a 13 (LP: #2160183) - SAUCE: wifi: ath12k: avoid MHI deinit during suspend -- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 15 Jul 2026 13:49:00 +0800 ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: Fix Committed => 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/2158229 Title: MT7925 wifi is hard blocked on Dell's machine Status in linux package in Ubuntu: New Status in linux-hwe-7.0 package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-hwe-7.0 source package in Noble: Fix Released Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Questing: Won't Fix Status in linux-hwe-7.0 source package in Questing: Invalid Status in linux-oem-6.17 source package in Questing: Invalid Status in linux source package in Resolute: In Progress Status in linux-hwe-7.0 source package in Resolute: Invalid Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux source package in Stonking: New Status in linux-hwe-7.0 source package in Stonking: Invalid Status in linux-oem-6.17 source package in Stonking: Invalid Bug description: [Impact] The Wi-Fi is hard blocked on Dell systems (CIDs: 202505-36757, 202501-36195, 202501-36253) and HP systems with Mediatek MT7925 cards. The wireless connection cannot be used. The rfkill state shows: $ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes [Fix] We revert the hardware rfkill polling feature for Mediatek MT7925 cards. This polling feature was introduced upstream in v6.16. We also revert the local DMI quirk for HP systems since polling is now disabled. Reverted commits: • Revert "wifi: mt76: mt7925: add rfkill_poll for hardware rfkill" (reverts upstream commit e54b870212c079bef4ff61238f8c1278a14d1863 from v6.16) • Revert local DMI quirk commit for HP systems (reverts local commit 20c9b07dcea9d49c876c9532a48a6dc88f43d0f9) [Test Plan] Check the rfkill state on affected hardware: $ rfkill list Without the patches: The Wireless LAN interface shows "Hard blocked: yes". The Wi-Fi connection does not work. With the patches: The Wireless LAN interface shows "Hard blocked: no". The Wi-Fi connection works. [Where problems could occur] This change affects the mt76 Mediatek wireless driver. If a system has a physical wireless switch that needs software polling, the switch will stop working. Toggling the physical switch would not change the Wi-Fi block state. ========================================================= [Impact] The wifi is hard blocked and can't be used randomly. [Test] 1. Boot up Machine 2. Run `rfkill list` to check wlan0 block state Wireless: Mediatek Inc. - 14c3:7925 ubuntu@localhost:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: yes [Affected Machines] 202505-36757 202501-36195 202501-36253 [Similar Issue] https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.14/+bug/2127044 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.17.0-1020-oem 6.17.0-1020.20 ProcVersionSignature: Ubuntu 6.17.0-1020.20-oem 6.17.13 Uname: Linux 6.17.0-1020-oem x86_64 ApportVersion: 2.28.2-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1918 F.... pipewire ubuntu 1922 F.... wireplumber /dev/snd/controlC0: ubuntu 1922 F.... wireplumber /dev/snd/seq: ubuntu 1918 F.... pipewire CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Jun 25 05:43:16 2026 DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04b-proposed-20250604-520 InstallationDate: Installed on 2026-05-07 (49 days ago) InstallationMedia: Ubuntu OEM 24.04.2 LTS "Noble Numbat" - Release amd64 (20250603) IwConfig: lo no wireless extensions. enp195s0f0 no wireless extensions. wlp194s0 no wireless extensions. MachineType: Dell Inc. Dell Pro Max 14 MC14255 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1020-oem root=UUID=881d0e73-6adc-444d-90b2-9491672e82b1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.17.0-1020-oem N/A linux-backports-modules-6.17.0-1020-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux-oem-6.17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2025 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0WT010 dmi.board.vendor: Dell Inc. dmi.board.version: D01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd09/09/2025:br1.4:efr1.3:svnDellInc.:pnDellProMax14MC14255:pvr:rvnDellInc.:rn0WT010:rvrD01:cvnDellInc.:ct10:cvr:sku0D80: dmi.product.family: Dell Pro Max Laptops dmi.product.name: Dell Pro Max 14 MC14255 dmi.product.sku: 0D80 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158229/+subscriptions