Corroborating datapoint on a different AMD platform (Strix Halo APU Radeon 8060s, not RX 9070): same -34 -> -38 regression window, same symptom. Hardware: BOSGAME M5 (board: Sixunited AXB35-02), AMD Ryzen AI Max+ 395, Radeon 8060S (gfx1151), DCN 3.5.1, BIOS 3.10 (2026-03-09). OS: Linux Mint 22.3 (Ubuntu 24.04 "noble" base), X11. Symptom: intermittent horizontal "purple" lines flashing randomly across both external displays (2x 2560x1440). No amdgpu errors in dmesg. Reproduces on native DisplayPort, native HDMI, and via a USB-C (DP-alt) dock. Regression window: - BAD: linux-image-7.0.0-38-generic (7.0.0-38.38~24.04.4) - GOOD: linux-image-7.0.0-34-generic (7.0.0-34.34~24.04.1) - GOOD: linux-image-6.17.0-1033-oem Booting 7.0.0-34 makes the line artifacts disappear, matching the original report. Ruled out on this machine: - memtest86+ full pass (memory) - monitors, cables and ports swapped between DP/HDMI; no change - amdgpu.dcdebugmask=0x4 (DSC disabled): no effect - amdgpu.dcdebugmask=0x84E (DSC + stutter + clock gating + MPO + IPS disabled): no effect - PSR not applicable (external displays only; sinks report PSR support 0) Happy to attach dmesg / drm debug logs from either kernel if that helps. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169313 Title: amdgpu: horizontal tearing/corruption in windows on RX 9070 with 7.0.0-38, not on 7.0.0-34 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 7.0.0-34 to 7.0.0-38, windows (Chrome while scrolling, Nautilus, desktop) intermittently show horizontal slicing/pixel corruption. No amdgpu errors in dmesg. Booting 7.0.0-34 makes the problem go away. GPU: RX 9070, Mesa 26.0.8, GNOME Wayland, 4K @ 120 Hz over DisplayPort, 133% scaling. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-34-generic 7.0.0-34.34 ProcVersionSignature: Ubuntu 7.0.0-34.34-generic 7.0.14 Uname: Linux 7.0.0-34-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: alexander 6520 F.... wireplumber /dev/snd/controlC0: alexander 6520 F.... wireplumber /dev/snd/controlC1: alexander 6520 F.... wireplumber /dev/snd/seq: alexander 6495 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 2 13:08:49 2026 InstallationDate: Installed on 2026-08-14 (50 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Micro Computer (HK) Tech Limited DeskMini Series ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-34-generic root=UUID=d9b5ca69-c01b-4738-b254-a9ce7a16fc74 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/05/2026 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.15 dmi.board.asset.tag: Default string dmi.board.name: DRFXL dmi.board.vendor: Meigao Innovation Technology (Shen Zhen) Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.15:bd01/05/2026:br5.29:svnMicroComputer(HK)TechLimited:pnDeskMiniSeries:pvr1.0:rvnMeigaoInnovationTechnology(ShenZhen)Co.,Ltd:rnDRFXL:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:skuMGDRFXL:pfaMINISFORUM: dmi.product.family: MINISFORUM dmi.product.name: DeskMini Series dmi.product.sku: MGDRFXL dmi.product.version: 1.0 dmi.sys.vendor: Micro Computer (HK) Tech Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169313/+subscriptions
суббота
[Bug 2171313] [NEW] mt7925e can't connect to Wi-Fi 7 (MLO) access points when the BIOS disables 802.11be for the country (Canada)
Public bug reported: SUMMARY On a Lenovo IdeaPad Slim 5 16AGP11 (MediaTek MT7925, driver mt7925e) in Canada, Ubuntu 26.04 can't connect to any Wi-Fi network whose access point advertises a Wi-Fi 7 Basic Multi-Link element. The kernel refuses every authentication attempt before a single frame is sent, and wpa_supplicant never falls back to a normal (non-MLO) connection. These networks are therefore unusable. About 30 other devices connect to the same access point without trouble, including other Ubuntu laptops. This laptop connects normally to networks that don't advertise a Multi-Link element. Cause, in short: the BIOS disables 802.11be (Wi-Fi 7) for Canada in its ACPI MTCL table, so mt7925e marks every channel NO_EHT. But mt7925e still advertises MLO support (WIPHY_FLAG_SUPPORTS_MLO), and its EHT capabilities stay advertised too. wpa_supplicant therefore requests an MLO authentication. mac80211 drops the connection to HE because of NO_EHT, stops seeing the AP's Multi-Link element, and rejects the request with "Rejecting MLO as it is not supported by AP". HARDWARE AND SOFTWARE - Lenovo IdeaPad Slim 5 16AGP11, machine type 83S2, BIOS TGCN13WW (02/28/2026) - MEDIATEK MT7925 802.11be PCIe [14c3:7925], subsystem Lenovo [17aa:e0ff], driver mt7925e - Ubuntu 26.04.1 LTS - Kernels: 7.0.0-30-generic (7.0.0-30.30, upstream 7.0.12) and 7.0.0-38-generic (7.0.0-38.38, upstream 7.0.14). Both are affected. - Firmware: linux-firmware-mediatek 20260319.git217ca6e4-0ubuntu1.2 (WM firmware build 20260605184805). The newer upstream build 20260813113118 fails the same way. - wpasupplicant 2:2.11-0ubuntu5, network-manager 1.54.3-2ubuntu3.1 - Regulatory domain: CA, set by the driver ("CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=CA") - Access point: a Wi-Fi 7 router with a Basic Multi-Link element on every SSID. <SSID-1> is a separate single-link MLD per band (5745 MHz and 2432 MHz). <SSID-2> is one 2-link MLD (link 0 on 5745 MHz, link 1 on 2432 MHz). STEPS TO REPRODUCE 1. Use this laptop (BIOS TGCN13WW) somewhere the regulatory country becomes CA ("iw reg get" shows "country CA"). 2. With the default NetworkManager + wpa_supplicant, connect to a Wi-Fi 7 access point that advertises a Multi-Link element (an MLO SSID, or a single-link MLD). 3. Watch "journalctl -f". EXPECTED RESULT The laptop connects: with MLO if Wi-Fi 7 is allowed, otherwise as a normal non-MLO Wi-Fi 6 (HE) connection. iwd does the latter on the same machine. ACTUAL RESULT No connection. Each BSS fails within about 60 ms: the kernel logs "regulatory prevented using AP config, downgraded" and "Rejecting MLO as it is not supported by AP", then wpa_supplicant logs "SME: Authentication request to the driver failed". No authentication frame is sent. wpa_supplicant ignore-lists the BSSID, tries the next one (again with MLO), and after that temporarily disables the network. This repeats on every attempt, on both kernels and with both firmware builds. LOGS (redacted) 7.0.0-38-generic, 2-link MLD SSID: [ 259.994810] wpa_supplicant[6403]: wlo1: SME: Trying to authenticate with <BSSID-2a> (SSID='<SSID-2>' freq=5745 MHz) [ 260.060118] kernel: wlo1: [link 0] regulatory prevented using AP config, downgraded [ 260.060318] kernel: wlo1: Rejecting MLO as it is not supported by AP [ 260.063602] wpa_supplicant[6403]: wlo1: SME: Authentication request to the driver failed [ 260.063628] wpa_supplicant[6403]: wlo1: Added BSSID <BSSID-2a> into ignore list, ignoring for 10 seconds [ 260.367503] wpa_supplicant[6403]: wlo1: SME: Trying to authenticate with <BSSID-2b> (SSID='<SSID-2>' freq=2432 MHz) [ 260.418124] kernel: wlo1: [link 1] regulatory prevented using AP config, downgraded [ 260.418326] kernel: wlo1: Rejecting MLO as it is not supported by AP [ 260.421295] wpa_supplicant[6403]: wlo1: SME: Authentication request to the driver failed [ 260.421316] wpa_supplicant[6403]: wlo1: Added BSSID <BSSID-2b> into ignore list, ignoring for 10 seconds 7.0.0-30-generic, SSID with a single-link MLD per band: [ 4.284069] kernel: mt7925e 0000:03:00.0: WM Firmware Version: ____000000, Build Time: 20260605184805 [ 9.670529] wpa_supplicant[1611]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=CA [ 13.698595] wpa_supplicant[1611]: wlo1: SME: Trying to authenticate with <BSSID-1a> (SSID='<SSID-1>' freq=5745 MHz) [ 13.762101] kernel: wlo1: [link 0] regulatory prevented using AP config, downgraded [ 13.762266] kernel: wlo1: Rejecting MLO as it is not supported by AP [ 13.769397] wpa_supplicant[1611]: wlo1: SME: Authentication request to the driver failed [ 14.077020] wpa_supplicant[1611]: wlo1: SME: Trying to authenticate with <BSSID-1b> (SSID='<SSID-1>' freq=2432 MHz) [ 14.139096] kernel: wlo1: [link 0] regulatory prevented using AP config, downgraded [ 14.139250] kernel: wlo1: Rejecting MLO as it is not supported by AP [ 14.142303] wpa_supplicant[1611]: wlo1: SME: Authentication request to the driver failed 7.0.0-38-generic with upstream firmware build 20260813113118: the same sequence. Driver state while affected (7.0.0-30-generic): - "iw reg get": country CA: DFS-FCC, both global and for phy#0 - Channel flags read through nl80211: NO_EHT on 14/14 2.4 GHz, 28/28 5 GHz and 59/59 6 GHz channels; NO_HE on none - "iw phy": "EHT Iftypes: managed" is still listed in all three bands ANALYSIS (from the v7.0.12 source; the logic is the same in mainline v7.3-rc7, wireless-next and the mt76 tree) 1. mt792x_acpi_get_mtcl_conf() reads the BIOS ACPI MTCL v3 table. CA is in cc_list_be, and its 802.11be bits (4-5) are 0, so mt7925_regd_be_ctrl() sets dev->has_eht = false. The firmware's CLC BE_CTRL list is HK ZA IQ UA RU PK, without CA, so the restriction comes from the BIOS. 2. mt7925_regd_channel_update() then sets IEEE80211_CHAN_NO_EHT on every channel. 3. mt7925_init_mlo_caps() sets WIPHY_FLAG_SUPPORTS_MLO at registration, and nothing clears it. mt7925_init_eht_caps() returns early without clearing the EHT capabilities set earlier, so those stay advertised too. 4. wpa_supplicant sees MLO support and the AP's Multi-Link element, and requests an MLD authentication. 5. In mac80211, ieee80211_determine_chan_mode() lowers the mode from EHT to HE because of NO_EHT and re-parses the AP's elements without the Multi-Link element. ieee80211_prep_channel() then returns -EINVAL ("Rejecting MLO as it is not supported by AP"). 6. wpa_supplicant 2.11 has no fallback to a non-MLO connection for this case. Suggested fixes (sent upstream): mt7925 shouldn't advertise MLO or EHT while has_eht is false. mac80211 and/or wpa_supplicant should fall back to a non-MLO association when EHT can't be used on the channel. WORKAROUND Switch NetworkManager to the iwd backend. iwd 3.10 never requests MLO and connects as Wi-Fi 6 (HE, 80 MHz). sudo apt install iwd network-manager-iwd sudo systemctl mask --now wpa_supplicant /etc/iwd/main.conf (both lines were needed with this chip; the first keeps the wlo1 interface that the saved NetworkManager profiles are tied to, and the second avoids about 10% packet loss and about 380 ms latency with power save on): [DriverQuirks] DefaultInterface=mt7925e PowerSaveDisable=mt7925e /etc/NetworkManager/conf.d/90-wifi-backend-iwd.conf: [device] wifi.backend=iwd Then: sudo systemctl enable --now iwd sudo systemctl restart NetworkManager Note: with the iwd backend, NetworkManager only matched a WPA3-only (SAE) profile after its key-mgmt was changed to wpa-psk. iwd still uses SAE for it. UPSTREAM AND RELATED - Upstream report: linux-wireless@vger.kernel.org, <lore.kernel.org link> - Lenovo has been asked whether a BIOS update enables 802.11be for Canada in the MTCL table. - Related: LP: #2121342 (Enable Wi-Fi 7 MLO on MTK MT7925) - Not tested on a mainline kernel build; the relevant code is unchanged in v7.3-rc7. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 1: skipped: root access not used when collecting this report Date: Fri Oct 16 12:31:24 2026 InstallationDate: Installed on 2026-10-15 (1 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: LENOVO 83S2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=<uuid> 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) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 1: skipped: root access not used when collecting this report dmi.bios.date: 02/28/2026 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: TGCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76574 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16AGP11 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrTGCN13WW:bd02/28/2026:br1.13:efr1.13:svnLENOVO:pn83S2:pvrIdeaPadSlim516AGP11:rvnLENOVO:rnLNVNB161216:rvrSDK0T76574WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516AGP11:skuLENOVO_MT_83S2_BU_idea_FM_IdeaPadSlim516AGP11:pfaIdeaPadSlim516AGP11: dmi.product.family: IdeaPad Slim 5 16AGP11 dmi.product.name: 83S2 dmi.product.sku: LENOVO_MT_83S2_BU_idea_FM_IdeaPad Slim 5 16AGP11 dmi.product.version: IdeaPad Slim 5 16AGP11 dmi.sys.vendor: LENOVO ** 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/2171313 Title: mt7925e can't connect to Wi-Fi 7 (MLO) access points when the BIOS disables 802.11be for the country (Canada) Status in linux package in Ubuntu: New Bug description: SUMMARY On a Lenovo IdeaPad Slim 5 16AGP11 (MediaTek MT7925, driver mt7925e) in Canada, Ubuntu 26.04 can't connect to any Wi-Fi network whose access point advertises a Wi-Fi 7 Basic Multi-Link element. The kernel refuses every authentication attempt before a single frame is sent, and wpa_supplicant never falls back to a normal (non-MLO) connection. These networks are therefore unusable. About 30 other devices connect to the same access point without trouble, including other Ubuntu laptops. This laptop connects normally to networks that don't advertise a Multi-Link element. Cause, in short: the BIOS disables 802.11be (Wi-Fi 7) for Canada in its ACPI MTCL table, so mt7925e marks every channel NO_EHT. But mt7925e still advertises MLO support (WIPHY_FLAG_SUPPORTS_MLO), and its EHT capabilities stay advertised too. wpa_supplicant therefore requests an MLO authentication. mac80211 drops the connection to HE because of NO_EHT, stops seeing the AP's Multi-Link element, and rejects the request with "Rejecting MLO as it is not supported by AP". HARDWARE AND SOFTWARE - Lenovo IdeaPad Slim 5 16AGP11, machine type 83S2, BIOS TGCN13WW (02/28/2026) - MEDIATEK MT7925 802.11be PCIe [14c3:7925], subsystem Lenovo [17aa:e0ff], driver mt7925e - Ubuntu 26.04.1 LTS - Kernels: 7.0.0-30-generic (7.0.0-30.30, upstream 7.0.12) and 7.0.0-38-generic (7.0.0-38.38, upstream 7.0.14). Both are affected. - Firmware: linux-firmware-mediatek 20260319.git217ca6e4-0ubuntu1.2 (WM firmware build 20260605184805). The newer upstream build 20260813113118 fails the same way. - wpasupplicant 2:2.11-0ubuntu5, network-manager 1.54.3-2ubuntu3.1 - Regulatory domain: CA, set by the driver ("CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=CA") - Access point: a Wi-Fi 7 router with a Basic Multi-Link element on every SSID. <SSID-1> is a separate single-link MLD per band (5745 MHz and 2432 MHz). <SSID-2> is one 2-link MLD (link 0 on 5745 MHz, link 1 on 2432 MHz). STEPS TO REPRODUCE 1. Use this laptop (BIOS TGCN13WW) somewhere the regulatory country becomes CA ("iw reg get" shows "country CA"). 2. With the default NetworkManager + wpa_supplicant, connect to a Wi-Fi 7 access point that advertises a Multi-Link element (an MLO SSID, or a single-link MLD). 3. Watch "journalctl -f". EXPECTED RESULT The laptop connects: with MLO if Wi-Fi 7 is allowed, otherwise as a normal non-MLO Wi-Fi 6 (HE) connection. iwd does the latter on the same machine. ACTUAL RESULT No connection. Each BSS fails within about 60 ms: the kernel logs "regulatory prevented using AP config, downgraded" and "Rejecting MLO as it is not supported by AP", then wpa_supplicant logs "SME: Authentication request to the driver failed". No authentication frame is sent. wpa_supplicant ignore-lists the BSSID, tries the next one (again with MLO), and after that temporarily disables the network. This repeats on every attempt, on both kernels and with both firmware builds. LOGS (redacted) 7.0.0-38-generic, 2-link MLD SSID: [ 259.994810] wpa_supplicant[6403]: wlo1: SME: Trying to authenticate with <BSSID-2a> (SSID='<SSID-2>' freq=5745 MHz) [ 260.060118] kernel: wlo1: [link 0] regulatory prevented using AP config, downgraded [ 260.060318] kernel: wlo1: Rejecting MLO as it is not supported by AP [ 260.063602] wpa_supplicant[6403]: wlo1: SME: Authentication request to the driver failed [ 260.063628] wpa_supplicant[6403]: wlo1: Added BSSID <BSSID-2a> into ignore list, ignoring for 10 seconds [ 260.367503] wpa_supplicant[6403]: wlo1: SME: Trying to authenticate with <BSSID-2b> (SSID='<SSID-2>' freq=2432 MHz) [ 260.418124] kernel: wlo1: [link 1] regulatory prevented using AP config, downgraded [ 260.418326] kernel: wlo1: Rejecting MLO as it is not supported by AP [ 260.421295] wpa_supplicant[6403]: wlo1: SME: Authentication request to the driver failed [ 260.421316] wpa_supplicant[6403]: wlo1: Added BSSID <BSSID-2b> into ignore list, ignoring for 10 seconds 7.0.0-30-generic, SSID with a single-link MLD per band: [ 4.284069] kernel: mt7925e 0000:03:00.0: WM Firmware Version: ____000000, Build Time: 20260605184805 [ 9.670529] wpa_supplicant[1611]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=CA [ 13.698595] wpa_supplicant[1611]: wlo1: SME: Trying to authenticate with <BSSID-1a> (SSID='<SSID-1>' freq=5745 MHz) [ 13.762101] kernel: wlo1: [link 0] regulatory prevented using AP config, downgraded [ 13.762266] kernel: wlo1: Rejecting MLO as it is not supported by AP [ 13.769397] wpa_supplicant[1611]: wlo1: SME: Authentication request to the driver failed [ 14.077020] wpa_supplicant[1611]: wlo1: SME: Trying to authenticate with <BSSID-1b> (SSID='<SSID-1>' freq=2432 MHz) [ 14.139096] kernel: wlo1: [link 0] regulatory prevented using AP config, downgraded [ 14.139250] kernel: wlo1: Rejecting MLO as it is not supported by AP [ 14.142303] wpa_supplicant[1611]: wlo1: SME: Authentication request to the driver failed 7.0.0-38-generic with upstream firmware build 20260813113118: the same sequence. Driver state while affected (7.0.0-30-generic): - "iw reg get": country CA: DFS-FCC, both global and for phy#0 - Channel flags read through nl80211: NO_EHT on 14/14 2.4 GHz, 28/28 5 GHz and 59/59 6 GHz channels; NO_HE on none - "iw phy": "EHT Iftypes: managed" is still listed in all three bands ANALYSIS (from the v7.0.12 source; the logic is the same in mainline v7.3-rc7, wireless-next and the mt76 tree) 1. mt792x_acpi_get_mtcl_conf() reads the BIOS ACPI MTCL v3 table. CA is in cc_list_be, and its 802.11be bits (4-5) are 0, so mt7925_regd_be_ctrl() sets dev->has_eht = false. The firmware's CLC BE_CTRL list is HK ZA IQ UA RU PK, without CA, so the restriction comes from the BIOS. 2. mt7925_regd_channel_update() then sets IEEE80211_CHAN_NO_EHT on every channel. 3. mt7925_init_mlo_caps() sets WIPHY_FLAG_SUPPORTS_MLO at registration, and nothing clears it. mt7925_init_eht_caps() returns early without clearing the EHT capabilities set earlier, so those stay advertised too. 4. wpa_supplicant sees MLO support and the AP's Multi-Link element, and requests an MLD authentication. 5. In mac80211, ieee80211_determine_chan_mode() lowers the mode from EHT to HE because of NO_EHT and re-parses the AP's elements without the Multi-Link element. ieee80211_prep_channel() then returns -EINVAL ("Rejecting MLO as it is not supported by AP"). 6. wpa_supplicant 2.11 has no fallback to a non-MLO connection for this case. Suggested fixes (sent upstream): mt7925 shouldn't advertise MLO or EHT while has_eht is false. mac80211 and/or wpa_supplicant should fall back to a non-MLO association when EHT can't be used on the channel. WORKAROUND Switch NetworkManager to the iwd backend. iwd 3.10 never requests MLO and connects as Wi-Fi 6 (HE, 80 MHz). sudo apt install iwd network-manager-iwd sudo systemctl mask --now wpa_supplicant /etc/iwd/main.conf (both lines were needed with this chip; the first keeps the wlo1 interface that the saved NetworkManager profiles are tied to, and the second avoids about 10% packet loss and about 380 ms latency with power save on): [DriverQuirks] DefaultInterface=mt7925e PowerSaveDisable=mt7925e /etc/NetworkManager/conf.d/90-wifi-backend-iwd.conf: [device] wifi.backend=iwd Then: sudo systemctl enable --now iwd sudo systemctl restart NetworkManager Note: with the iwd backend, NetworkManager only matched a WPA3-only (SAE) profile after its key-mgmt was changed to wpa-psk. iwd still uses SAE for it. UPSTREAM AND RELATED - Upstream report: linux-wireless@vger.kernel.org, <lore.kernel.org link> - Lenovo has been asked whether a BIOS update enables 802.11be for Canada in the MTCL table. - Related: LP: #2121342 (Enable Wi-Fi 7 MLO on MTK MT7925) - Not tested on a mainline kernel build; the relevant code is unchanged in v7.3-rc7. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 1: skipped: root access not used when collecting this report Date: Fri Oct 16 12:31:24 2026 InstallationDate: Installed on 2026-10-15 (1 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: LENOVO 83S2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=<uuid> 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) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 1: skipped: root access not used when collecting this report dmi.bios.date: 02/28/2026 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: TGCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76574 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16AGP11 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrTGCN13WW:bd02/28/2026:br1.13:efr1.13:svnLENOVO:pn83S2:pvrIdeaPadSlim516AGP11:rvnLENOVO:rnLNVNB161216:rvrSDK0T76574WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516AGP11:skuLENOVO_MT_83S2_BU_idea_FM_IdeaPadSlim516AGP11:pfaIdeaPadSlim516AGP11: dmi.product.family: IdeaPad Slim 5 16AGP11 dmi.product.name: 83S2 dmi.product.sku: LENOVO_MT_83S2_BU_idea_FM_IdeaPad Slim 5 16AGP11 dmi.product.version: IdeaPad Slim 5 16AGP11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171313/+subscriptions
[Bug 2171312] [NEW] amdgpu: horizontal screen corruption on RX 9070 XT at 4K 120/160Hz (DSC) with 7.0.0-38; 7.0.0-34 is fine
Public bug reported: Disclaimer: this bug report was co-authoured with Claude code with assistance in finding the cause. Package: linux-image-7.0.0-38-generic (7.0.0-38.38) Regression from: linux-image-7.0.0-34-generic (7.0.0-34.34), which works correctly Release: Ubuntu 26.04 (resolute) SUMMARY After upgrading from 7.0.0-34 to 7.0.0-38, horizontal band artifacts appear across the screen whenever a large part of the display changes, for example GNOME overview and workspace transitions, or the KDE Plasma logout fade. Booting 7.0.0-34 with no other changes makes the problem disappear. HARDWARE - GPU: AMD Radeon RX 9070 XT (Navi 48, 1002:7550), Sapphire, driver amdgpu - Monitor: MSI MPG 274U E16M, 3840x2160, connected over DisplayPort (DP-2) - Mode: 3840x2160 at 160Hz (also affected at 120Hz). 60Hz is clean. - Mesa 26.0.8, linux-firmware 20260319 (both unchanged between the working and broken kernels) SOFTWARE - GNOME Shell 50.1 on Wayland (Mutter), 1.25x fractional scaling - KDE Plasma Wayland session also tested (see below) DISPLAY LINK STATE (7.0.0-38, from /sys/kernel/debug/dri/1/DP-2/) - dsc_clock_en: 1 (DSC active) - dsc_slice_width: 480 - dsc_bits_per_pixel: 256 (16 bpp) - link_settings: 4 lanes, rate 0x1e (HBR3), full speed, no link-training downgrade SYMPTOMS - Horizontal bands of corruption spanning the screen during full-screen animations. - Not seen in fullscreen games. - Not seen at 60Hz (which does not need DSC). - Reproduces in both GNOME and KDE Plasma, so it is not compositor-specific. KEY FINDING With power_dpm_force_performance_level=auto the memory clock idles at 96 MHz (pp_dpm_mclk level 0) and the artifacts appear. With echo high > /sys/class/drm/card1/device/power_dpm_force_performance_level the artifacts disappear in both GNOME and KDE. Switching back to auto brings them back. This suggests memory clock switching is not completing within the vblank window on this DSC mode, which does not happen on 7.0.0-34. REPRODUCE 1. Boot 7.0.0-38 with the 4K 160Hz monitor on DisplayPort. 2. Leave the performance level on auto and let the GPU idle. 3. Open the GNOME overview or switch workspaces. POSSIBLE CAUSES (from comparing the 7.0.0-34 and 7.0.0-38 changelogs; I have not read the diffs or bisected) - drm/amd/display: consolidate DCN vblank/flip handling onto vupdate_no_lock - drm/amd/display: Fix DTB DTO updates breaking live pixel rate sources - drm/amd/display: ISM (idle state manager) fixes - drm/amdgpu: Fix context pstate override handling WORKAROUNDS - Boot 7.0.0-34. - Force power_dpm_force_performance_level=high. - Use 60Hz. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Oct 18 02:53:09 2026 InstallationDate: Installed on 2023-06-15 (1220 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) IwDevWlp5s0Link: Not connected. MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-04-24 (177 days ago) dmi.bios.date: 01/04/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F35 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF35:bd01/04/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX570MB: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** 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/2171312 Title: amdgpu: horizontal screen corruption on RX 9070 XT at 4K 120/160Hz (DSC) with 7.0.0-38; 7.0.0-34 is fine Status in linux package in Ubuntu: New Bug description: Disclaimer: this bug report was co-authoured with Claude code with assistance in finding the cause. Package: linux-image-7.0.0-38-generic (7.0.0-38.38) Regression from: linux-image-7.0.0-34-generic (7.0.0-34.34), which works correctly Release: Ubuntu 26.04 (resolute) SUMMARY After upgrading from 7.0.0-34 to 7.0.0-38, horizontal band artifacts appear across the screen whenever a large part of the display changes, for example GNOME overview and workspace transitions, or the KDE Plasma logout fade. Booting 7.0.0-34 with no other changes makes the problem disappear. HARDWARE - GPU: AMD Radeon RX 9070 XT (Navi 48, 1002:7550), Sapphire, driver amdgpu - Monitor: MSI MPG 274U E16M, 3840x2160, connected over DisplayPort (DP-2) - Mode: 3840x2160 at 160Hz (also affected at 120Hz). 60Hz is clean. - Mesa 26.0.8, linux-firmware 20260319 (both unchanged between the working and broken kernels) SOFTWARE - GNOME Shell 50.1 on Wayland (Mutter), 1.25x fractional scaling - KDE Plasma Wayland session also tested (see below) DISPLAY LINK STATE (7.0.0-38, from /sys/kernel/debug/dri/1/DP-2/) - dsc_clock_en: 1 (DSC active) - dsc_slice_width: 480 - dsc_bits_per_pixel: 256 (16 bpp) - link_settings: 4 lanes, rate 0x1e (HBR3), full speed, no link-training downgrade SYMPTOMS - Horizontal bands of corruption spanning the screen during full-screen animations. - Not seen in fullscreen games. - Not seen at 60Hz (which does not need DSC). - Reproduces in both GNOME and KDE Plasma, so it is not compositor-specific. KEY FINDING With power_dpm_force_performance_level=auto the memory clock idles at 96 MHz (pp_dpm_mclk level 0) and the artifacts appear. With echo high > /sys/class/drm/card1/device/power_dpm_force_performance_level the artifacts disappear in both GNOME and KDE. Switching back to auto brings them back. This suggests memory clock switching is not completing within the vblank window on this DSC mode, which does not happen on 7.0.0-34. REPRODUCE 1. Boot 7.0.0-38 with the 4K 160Hz monitor on DisplayPort. 2. Leave the performance level on auto and let the GPU idle. 3. Open the GNOME overview or switch workspaces. POSSIBLE CAUSES (from comparing the 7.0.0-34 and 7.0.0-38 changelogs; I have not read the diffs or bisected) - drm/amd/display: consolidate DCN vblank/flip handling onto vupdate_no_lock - drm/amd/display: Fix DTB DTO updates breaking live pixel rate sources - drm/amd/display: ISM (idle state manager) fixes - drm/amdgpu: Fix context pstate override handling WORKAROUNDS - Boot 7.0.0-34. - Force power_dpm_force_performance_level=high. - Use 60Hz. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Oct 18 02:53:09 2026 InstallationDate: Installed on 2023-06-15 (1220 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) IwDevWlp5s0Link: Not connected. MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-04-24 (177 days ago) dmi.bios.date: 01/04/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F35 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF35:bd01/04/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX570MB: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171312/+subscriptions
[Bug 2171286] Re: ipu-bridge: HIMX1092 entry without a driver breaks IPU7 camera (ov02c10)
Hi, just want to add more information on this after looking into kernel lore ----------------------------------- The HIMX1092 entry comes from mainline: - commit 4fdb0342f05e "media: ipu-bridge: Add Himax HM1092 IR sensor", authored by Jake Steinman, applied by Sakari Ailus, first released in v7.3-rc1. There is NO HM1092 sensor driver in mainline as of v7.3-rc7. The driver series ("media: i2c: Add HM1092 camera sensor driver", v6, August 2026) is still under review. The posting of the ipu-bridge patch itself said it depended on that driver and "should wait for it". Removing the single HIMX1092 line from ipu_supported_sensors[] restores normal behaviour. Since an upstream driver is unlikely to arrive before the final 7.3 release, consider reverting 4fdb0342f05e (or drop the entry) or wait for it to be available for backporting to 7.3 on Stonking. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171286 Title: ipu-bridge: HIMX1092 entry without a driver breaks IPU7 camera (ov02c10) Status in linux package in Ubuntu: New Bug description: Kernel 7.3's ipu-bridge has a sensor entry for the IR sensor: IPU_SENSOR_CONFIG("HIMX1092", 2, 180000000, 180480000) but 7.3 ships no driver for the HM1092. ipu-bridge therefore creates a graph endpoint for it that is never bound, and the IPU7 ISYS async notifier waits for it forever. The comment above the table itself says "Do not add an entry for a sensor that is not actually supported." My setup -------- Ubuntu 26.10 on XPS 13 (9350), pre-installed with Ubuntu 24.04 LTS, IPU7 ov02c10 camera. Effect ------ - The RGB sensor (ov02c10 12-0036) binds through Intel CVS's sub-notifier rather than ISYS's bound() callback, so no /dev/v4l-subdev node is created for it while the ISYS notifier is incomplete. - Intel's camera HAL (libcamhal-ipu7x) cannot set the sensor's format or controls, so the picture comes out with wrong colours / exposure. Steps to reproduce ------------------ 1. Boot 7.3.0-9-generic on a Lunar Lake laptop whose ACPI tables list HIMX1092 (e.g. Dell XPS 13 9350). 2. `journalctl -k -b | grep "sensor registration"` → nothing. 3. `sudo cat /sys/kernel/debug/v4l2-async/pending_async_subdevices` → the HIMX1092 endpoint above is pending. 4. `ls /dev/v4l-subdev*` and check for ov02c10 → no subdev for the sensor. Temporary workaround -------------------- Rebuilding ipu-bridge from the 7.3.0-9.9 source with only the HIMX1092 entry removed (out-of-tree DKMS module): "All sensor registration completed." returns, `v4l-subdev5: ov02c10 12-0036` appears, and the camera's colours are correct. No other change was needed for this part. AI assistance declaration ------------------------- This bug was investigated with the help of an AI assistant. That said, I ran the tests on my own hardware and confirmed the results above (the missing "All sensor registration completed." message and pending HIMX1092 endpoint on the stock kernel, and the camera working correctly with the workaround). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171286/+subscriptions
[Bug 2171286] Re: ipu-bridge: HIMX1092 entry without a driver breaks IPU7 camera (ov02c10)
** 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/2171286 Title: ipu-bridge: HIMX1092 entry without a driver breaks IPU7 camera (ov02c10) Status in linux package in Ubuntu: New Bug description: Kernel 7.3's ipu-bridge has a sensor entry for the IR sensor: IPU_SENSOR_CONFIG("HIMX1092", 2, 180000000, 180480000) but 7.3 ships no driver for the HM1092. ipu-bridge therefore creates a graph endpoint for it that is never bound, and the IPU7 ISYS async notifier waits for it forever. The comment above the table itself says "Do not add an entry for a sensor that is not actually supported." My setup -------- Ubuntu 26.10 on XPS 13 (9350), pre-installed with Ubuntu 24.04 LTS, IPU7 ov02c10 camera. Effect ------ - The RGB sensor (ov02c10 12-0036) binds through Intel CVS's sub-notifier rather than ISYS's bound() callback, so no /dev/v4l-subdev node is created for it while the ISYS notifier is incomplete. - Intel's camera HAL (libcamhal-ipu7x) cannot set the sensor's format or controls, so the picture comes out with wrong colours / exposure. Steps to reproduce ------------------ 1. Boot 7.3.0-9-generic on a Lunar Lake laptop whose ACPI tables list HIMX1092 (e.g. Dell XPS 13 9350). 2. `journalctl -k -b | grep "sensor registration"` → nothing. 3. `sudo cat /sys/kernel/debug/v4l2-async/pending_async_subdevices` → the HIMX1092 endpoint above is pending. 4. `ls /dev/v4l-subdev*` and check for ov02c10 → no subdev for the sensor. Temporary workaround -------------------- Rebuilding ipu-bridge from the 7.3.0-9.9 source with only the HIMX1092 entry removed (out-of-tree DKMS module): "All sensor registration completed." returns, `v4l-subdev5: ov02c10 12-0036` appears, and the camera's colours are correct. No other change was needed for this part. AI assistance declaration ------------------------- This bug was investigated with the help of an AI assistant. That said, I ran the tests on my own hardware and confirmed the results above (the missing "All sensor registration completed." message and pending HIMX1092 endpoint on the stock kernel, and the camera working correctly with the workaround). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171286/+subscriptions
[Bug 2171307] Re: No audio output (Dummy Output only) on HP OmniBook X Flip 14-kb0xxx, Panther Lake, kernel 7.3.0-9 (Ubuntu 26.10)
** 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/2171307 Title: No audio output (Dummy Output only) on HP OmniBook X Flip 14-kb0xxx, Panther Lake, kernel 7.3.0-9 (Ubuntu 26.10) Status in linux package in Ubuntu: New Bug description: **Summary** The speakers and headphone output do not work. GNOME and PipeWire only show "Dummy Output". The sound card `sof-soundwire` is registered, but the kernel finds no SoundWire machine driver for this laptop, so no speaker sink is created. **Hardware** - HP OmniBook X Flip Laptop 14-kb0xxx, BIOS F.10, audio subsystem ID 103c:8ea4 - Intel Core Ultra Series 3 (Panther Lake) audio controller, 8086:e428 - Realtek RT712 (SoundWire link 3), 2x TI TAS2783 speaker amps (link 2) **Versions** - Ubuntu 26.10, linux 7.3.0-9-generic (#9-Ubuntu, Oct 5 2026) - linux-firmware 20260915.git1522c78a.1ubuntu, firmware-sof-signed 2026.09-1 - alsa-ucm-conf 1.2.16.1-1ubuntu1, pipewire 1.6.8, wireplumber 0.5.17 **Steps** 1. Boot, open Settings > Sound. 2. Only "Dummy Output" is listed. `wpctl status` shows the same, and the card profile list is off / HiFi (unavailable) / pro-audio. **Expected:** speaker and headphone outputs. **Key log lines** ``` sof-audio-pci-intel-ptl 0000:00:1f.3: No SoundWire machine driver found for the ACPI-reported configuration: sof-audio-pci-intel-ptl 0000:00:1f.3: link 2 mfg_id 0x0102 part_id 0x0000 version 0x3 sof-audio-pci-intel-ptl 0000:00:1f.3: link 3 mfg_id 0x025d part_id 0x0712 version 0x3 sof-audio-pci-intel-ptl 0000:00:1f.3: Use SoundWire default machine driver with function topologies slave-tas2783 sdw:0:2:0102:0000:01:c: Direct firmware load for 8EA4-2-0xC.bin failed with error -2 slave-tas2783 sdw:0:2:0102:0000:01:9: Direct firmware load for 8EA4-2-0x9.bin failed with error -2 ``` Also `UBSAN: shift-out-of-bounds in sound/soc/sof/ipc4-topology.c:2471:13`. **Findings** - The TAS2783 driver requests `8EA4-2-0x{9,C}.bin`, but linux-firmware ships `8EA4-0-2-0x{9,C}.bin.zst` and `8EA4-1-2-0x{9,C}.bin.zst` (an extra index field). Creating symlinks for the requested names in `/lib/firmware` removes the load errors. - That does not restore sound. The kernel has no machine-driver match for RT712 + 2x TAS2783, and the ACPI tables do not describe the amps as SDCA speaker functions. Only the jack, mic and HDMI topologies get loaded, never the installed `sof-sdca-2amp-id2.tplg`. - I have not tested a kernel patch. This probably needs a `soc-acpi-intel-ptl-match.c` entry or equivalent. I have also filed it upstream with the SOF project. **Request:** please include audio support for this model in a kernel update, and align the TAS2783 firmware file naming between the kernel and linux-firmware packages. ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: linux-image-7.3.0-9-generic 7.3.0-9.9 ProcVersionSignature: Ubuntu 7.3.0-9.9-generic 7.3.0-rc6 Uname: Linux 7.3.0-9-generic x86_64 ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: kevin 8192 F.... wireplumber /dev/snd/seq: kevin 8188 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 20:56:37 2026 InstallationDate: Installed on 2026-10-17 (0 days ago) InstallationMedia: Ubuntu 26.10 "Stonking Stingray" - Official amd64 (20261013) MachineType: HP HP OmniBook X Flip Laptop 14-kb0xxx ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.3.0-9-generic root=UUID=be9e4e6d-9ff2-4d3c-89fe-f954199f0334 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: 04/16/2026 dmi.bios.release: 15.10 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8EA4 dmi.board.vendor: HP dmi.board.version: 12.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 12.26 dmi.modalias: dmi:bvnInsyde:bvrF.10:bd04/16/2026:br15.10:efr12.26:svnHP:pnHPOmniBookXFlipLaptop14-kb0xxx:pvrType1ProductConfigId:rvnHP:rn8EA4:rvr12.26:cvnHP:ct31:cvrChassisVersion:skuDQ8R9EA#ABU:pfa103C_5335M8HPOmniBookX: dmi.product.family: 103C_5335M8 HP OmniBook X dmi.product.name: HP OmniBook X Flip Laptop 14-kb0xxx dmi.product.sku: DQ8R9EA#ABU dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171307/+subscriptions
пятница
[Bug 2161930] Re: LG Monitor shows black screen when set to 144hz
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161930 Title: LG Monitor shows black screen when set to 144hz Status in linux package in Ubuntu: Expired Bug description: ### Issue I have a PC connected to an LG 27GL850-B Ultragear QHD monitor. When I launch Ubuntu, the LG screen displays a black screen by default. If I change the refresh rate from 144hz to 120hz the monitor will work correctly. ### Expected behavior The monitor should be configured to display correctly by default. ### System Info * OS: Ubuntu 26.04 LTS * Hardware Model: ASUS TUF GAMING B550M-PLUS _WI-FI_ * Processor: AMD Ryzen™ 5 5600X × 12 * Graphics: zink Vulkan 1.4(NVIDIA GeForce RTX™ 4070 SUPER (NVK AD104)) * Firmware Version: 3621 * Kernel Version: Linux 7.0.0-14-generic ### XOrg version xorg: Installed: (none) Candidate: 1:7.7+26ubuntu1 Version table: 1:7.7+26ubuntu1 500 500 http://archive.ubuntu.com/ubuntu resolute/universe amd64 Packages ### Extra info * I am booting Ubuntu off an unmodified USB image in "Try Ubuntu" mode * I have two monitors connected. The 144hz LG connected via DisplayPort and a 60hz Dell connected via HDMI * The same issue occurred when booting my PC on Linux Mint ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 26.04.2 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 22:34:47 2026 LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161930/+subscriptions
[Bug 2171268] Re: [ASUS ExpertCenter / Raptor Lake] Internal speakers produce no sound (Realtek ALC256 / SOF driver)
snd_hda_intel: dmic_detect=0 snd_intel_dspcfg: dsp_driver=1 snd_hda_intel: patch=hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw,hda-jack-retask.fw ------------------------------------------ Please remove ^these customizations, and any others you've made to fix this issue, reboot and run the following command to gather relevant logs: apport-collect 2171268 ** Package changed: linux (Ubuntu) => alsa-driver (Ubuntu) ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171268 Title: [ASUS ExpertCenter / Raptor Lake] Internal speakers produce no sound (Realtek ALC256 / SOF driver) Status in alsa-driver package in Ubuntu: Incomplete Bug description: Issue Description: Internal speakers are completely silent on an ASUS ExpertCenter laptop with Intel Raptor Lake platform using the Sound Open Firmware (SOF) driver and Realtek ALC256 codec. Hardware & System Info: - Model: ASUS ExpertCenter (Intel Raptor Lake) - Audio Codec: Realtek ALC256 - OS: Ubuntu Linux 26.04 - Sound Server: PipeWire / WirePlumber - Low-level driver: snd-sof-pci-intel-tgl Verification & Troubleshooting Performed: 1. Hardware functional test: Audio and speakers operate correctly during BIOS hardware diagnostics (rules out physical hardware failure). 2. Volume / Mute checks: ALSA Mixer (`alsamixer`) and PipeWire show Master, Speaker, and PCM channels unmuted (`00`) and set to appropriate volume levels. 3. Troubleshooting attempts: - Modifying module parameters (`options snd-intel-dspcfg dsp_driver=1`) - Disabling Fast Boot in BIOS - Updating to the latest mainline kernel - Overriding pin configuration via `hdajackretask` None of these attempts produced audio output through the internal speakers. Diagnostic Log Attached: I have attached the full diagnostic output generated by `alsa-info.sh` (containing ACPI tables, pin configurations, and SOF driver dmesg logs). Request: Please review the attached alsa-info log to include the proper pin-mapping quirk/patch for this ASUS ExpertCenter model in future kernel/firmware updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2171268/+subscriptions
[Bug 2127044] Re: MT7925 wifi is hard blocked on HP's machine
** Tags added: linux-firmware-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/2127044 Title: MT7925 wifi is hard blocked on HP's machine Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-firmware-mediatek package in Ubuntu: Invalid Status in linux-oem-6.14 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-firmware-mediatek source package in Noble: In Progress Status in linux-oem-6.14 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: Fix Released Status in linux-firmware-mediatek source package in Questing: Won't Fix Status in linux-oem-6.14 source package in Questing: Invalid Status in linux-oem-6.17 source package in Questing: Invalid Bug description: [Impact] The wifi is hard blocked and can't be used randomly. [Fix] The issue is introduced by commit 085749115fd37 ("wifi: mt76: mt7925: add rfkill_poll for hardware rfkill") The machine doesn't support this feature may lead to undefined behavior, and MTK will submit a firmware to fix this issue in the near feature. For short-term solution, we made a DMI quick to list the machines that doesn't support this feature. [Test] 1. Boot up HP Z2 Mini G1a Workstation 2. Run `rfkill list` to check wlan0 block state 3. Re-plug power cord and then check rfkill state again 4. The wlan0 should not be hard blocked. [Where problems could occur] Should be pretty safe to return the function call directly, since the machine doesn't support it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2127044/+subscriptions
[Bug 2171046] Re: Firmware-less serdev device returns ENODEV for modalias, breaking sysfs enumeration
** 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/2171046 Title: Firmware-less serdev device returns ENODEV for modalias, breaking sysfs enumeration Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: The Dell UART backlight driver creates a serial0-0 serdev device without ACPI or Device Tree firmware metadata. When userspace reads its modalias sysfs file, serdev tries to generate an alias from ACPI and OF data; both lookups return -ENODEV , which serdev incorrectly propagates as a read failure. The modalias should instead be readable with empty content, because this manually created device has no firmware alias. Returning -ENODEV makes sysfs enumeration fail and causes Checkbox dkms_info_attachment to abort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171046/+subscriptions
[Bug 2171271] Re: Slow resume (~75s) from lid/keyboard on ASUS UM3406HA after upgrade to 26.04
** 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/2171271 Title: Slow resume (~75s) from lid/keyboard on ASUS UM3406HA after upgrade to 26.04 Status in linux package in Ubuntu: New Bug description: Since upgrading to Ubuntu 26.04 (kernel 7.0.0-38), waking from s2idle by opening the lid, pressing keys, or pressing the power button takes about 75 seconds. Waking by RTC alarm (amd-s2idle test) is instant. The problem did not exist before the upgrade. BIOS updated from 304 to 308, no change. Hardware: ASUS Zenbook 14 UM3406HA, AMD Ryzen 7 8840HS. amd-s2idle report attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: mmm 2375 F.... wireplumber /dev/snd/controlC0: mmm 2375 F.... wireplumber /dev/snd/seq: mmm 2266 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 00:56:06 2026 InstallationDate: Installed on 2025-11-02 (348 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: ASUSTeK COMPUTER INC. ASUS Zenbook 14 UM3406HA_UM3406HA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-12 (4 days ago) dmi.bios.date: 07/23/2025 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM3406HA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM3406HA 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.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3406HA.308:bd07/23/2025:br5.29:svnASUSTeKCOMPUTERINC.:pnASUSZenbook14UM3406HA_UM3406HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3406HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSZenbook14: dmi.product.family: ASUS Zenbook 14 dmi.product.name: ASUS Zenbook 14 UM3406HA_UM3406HA 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/2171271/+subscriptions
[Bug 2171271] [NEW] Slow resume (~75s) from lid/keyboard on ASUS UM3406HA after upgrade to 26.04
Public bug reported: Since upgrading to Ubuntu 26.04 (kernel 7.0.0-38), waking from s2idle by opening the lid, pressing keys, or pressing the power button takes about 75 seconds. Waking by RTC alarm (amd-s2idle test) is instant. The problem did not exist before the upgrade. BIOS updated from 304 to 308, no change. Hardware: ASUS Zenbook 14 UM3406HA, AMD Ryzen 7 8840HS. amd-s2idle report attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: mmm 2375 F.... wireplumber /dev/snd/controlC0: mmm 2375 F.... wireplumber /dev/snd/seq: mmm 2266 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 00:56:06 2026 InstallationDate: Installed on 2025-11-02 (348 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: ASUSTeK COMPUTER INC. ASUS Zenbook 14 UM3406HA_UM3406HA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-12 (4 days ago) dmi.bios.date: 07/23/2025 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM3406HA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM3406HA 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.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3406HA.308:bd07/23/2025:br5.29:svnASUSTeKCOMPUTERINC.:pnASUSZenbook14UM3406HA_UM3406HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3406HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSZenbook14: dmi.product.family: ASUS Zenbook 14 dmi.product.name: ASUS Zenbook 14 UM3406HA_UM3406HA 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 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2171271 Title: Slow resume (~75s) from lid/keyboard on ASUS UM3406HA after upgrade to 26.04 Status in linux package in Ubuntu: New Bug description: Since upgrading to Ubuntu 26.04 (kernel 7.0.0-38), waking from s2idle by opening the lid, pressing keys, or pressing the power button takes about 75 seconds. Waking by RTC alarm (amd-s2idle test) is instant. The problem did not exist before the upgrade. BIOS updated from 304 to 308, no change. Hardware: ASUS Zenbook 14 UM3406HA, AMD Ryzen 7 8840HS. amd-s2idle report attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: mmm 2375 F.... wireplumber /dev/snd/controlC0: mmm 2375 F.... wireplumber /dev/snd/seq: mmm 2266 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 00:56:06 2026 InstallationDate: Installed on 2025-11-02 (348 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: ASUSTeK COMPUTER INC. ASUS Zenbook 14 UM3406HA_UM3406HA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-12 (4 days ago) dmi.bios.date: 07/23/2025 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM3406HA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM3406HA 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.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3406HA.308:bd07/23/2025:br5.29:svnASUSTeKCOMPUTERINC.:pnASUSZenbook14UM3406HA_UM3406HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3406HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSZenbook14: dmi.product.family: ASUS Zenbook 14 dmi.product.name: ASUS Zenbook 14 UM3406HA_UM3406HA 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/2171271/+subscriptions
четверг
[Bug 2169736] Re: RTC device disappears after updating to 7.0.0-39-generic
Thank you very much for reporting this issue. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Resolute) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Medium => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Resolute) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169736 Title: RTC device disappears after updating to 7.0.0-39-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: Issue seen on 26.04 and probably other series as well. ubuntu@dell-latitude-5411-c27717:~$ uname -a Linux dell-latitude-5411-c27717 7.0.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 22 16:06:43 UTC 2026 x86_64 GNU/Linux ubuntu@dell-latitude-5411-c27717:~$ cat /sys/class/rtc/rtc0/since_epoch 1791307002 # Update to 7.0.0-39-generic and reboot ubuntu@dell-latitude-5411-c27717:~$ uname -a Linux dell-latitude-5411-c27717 7.0.0-39-generic #39-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 24 11:18:19 UTC 2026 x86_64 GNU/Linux ubuntu@dell-latitude-5411-c27717:~$ cat /sys/class/rtc/rtc0/since_epoch cat: /sys/class/rtc/rtc0/since_epoch: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-39-generic 7.0.0-39.39 ProcVersionSignature: Ubuntu 7.0.0-39.39-generic 7.0.14 Uname: Linux 7.0.0-39-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2123 F.... wireplumber /dev/snd/seq: ubuntu 2102 F.... pipewire CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/) Date: Wed Oct 7 01:19:33 2026 InstallationDate: Installed on 2026-05-19 (141 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlo1Link: Not connected. MachineType: Dell Inc. Latitude 5411 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-39-generic root=UUID=16b44133-d26e-466c-8e12-da20de044692 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/03/2020 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd05/03/2020:br1.1:svnDellInc.:pnLatitude5411:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku09C0:pfaLatitude: dmi.product.family: Latitude dmi.product.name: Latitude 5411 dmi.product.sku: 09C0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2169736/+subscriptions