[Kernel-packages] [Bug 2029899] Re: Update firmware for hwe-6.2/oem-6.5 kernel migrations
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3.22 --- linux-firmware (20220329.git681281e4-0ubuntu3.22) jammy; urgency=medium * Update firmware for hwe-6.2/oem-6.5 kernel migrations (LP: #2029899) - nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware - rtlwifi: Add firmware v4.0 for RTL8188FU - brcm: add configuration files for CyberTan WC121 - i915: Add DMC v2.18 for ADLP - ath11k: IPQ5018 hw1.0: add board-2.bin - ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 - rtl_bt: Add firmware and config files for RTL8821CS - brcm: Add nvram for the Advantech MICA-071 tablet - rtlwifi: Add firmware v16.0 for RTL8710BU aka RTL8188GU - rtw89: 8852b: add format-1 fw v0.29.26.0 - rtw89: 8852b: update format-1 fw to v0.29.29.0 - i915: Update ADLP DMC to v2.19 - rtw89: 8852b: update format-1 fw to v0.29.29.1 - rtlwifi: Add firmware v6.0 for RTL8192FU - amdgpu: add initial GC 11.0.3 firmware - amdgpu: add initial PSP 13.0.10 firmware - amdgpu: add initial SDMA 6.0.3 firmware - amdgpu: add initial SMU 13.0.10 firmware - i915: Update ADLP DMC to v2.20 - rtw89: 8852b: update fw to v0.29.29.3 -- Juerg Haefliger Tue, 17 Oct 2023 09:25:15 +0200 ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2029899 Title: Update firmware for hwe-6.2/oem-6.5 kernel migrations Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] When migrating to a new hwe kernel or introduced a oem kernel of a newer version, the firmware blobs might not match the expectation of the new kernel. [Fix] For linux-hwe-6.2/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/lunar \ linux-hwe-6.2/debian.hwe-6.2/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/lunar -- * d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it For linux-oem-6.5/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/mantic \ linux-oem-6.5/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/mantic -- * 41e615cf3 i915: Update ADLP DMC to v2.20 * 22fb12f2f amdgpu: add initial SMU 13.0.10 firmware * b3f512fb5 amdgpu: add initial SDMA 6.0.3 firmware * b1a7d7624 amdgpu: add initial PSP 13.0.10 firmware * d6d655ade amdgpu: add initial GC 11.0.3 firmware * b255f5b92 (tag: iwlwifi-fw-2023-06-29, korg-iwlwifi/for-upstream) iwlwifi: add new FWs from core80-39 release * 84d5550e9 amdgpu: update aldebaran firmware for amd.5.5 release * 08b854f02 rtlwifi: Add firmware v6.0 for RTL8192FU * 9f7502f1d rtw89: 8852b: update format-1 fw to v0.29.29.1 * 78a8782a9 (tag: iwlwifi-fw-2023-03-30) iwlwifi: add new FWs from core78-32 release * 7f490a9a4 Merge branch 'dmc-adlp_2.19-mtl_2.12' of git://anongit.freedesktop.org/drm/drm-firmware |\ | * 4ee236dbb i915: Update ADLP DMC to v2.19 * | 2c07f017f rtw89: 8852b: update format-1 fw to v0.29.29.0 * | b50cf9205 rtw89: 8852b: add format-1 fw v0.29.26.0 |/ * 6a55abe94 Merge https://github.com/pkshih/linux-firmware |\ | * 4cc3eda63 rtlwifi: Add firmware v16.0 for RTL8710BU aka RTL8188GU * | d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet |/ * 3653d692b rtl_bt: Add firmware and config files for RTL8821CS * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * a5046f435 (drm/dmc-adlp_2.18) i915: Add DMC v2.18 for ADLP * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it [Test Case] Boot linux-oem-6.5, linux-hwe-6.2 with Jammy base system. Also test that none of the original firmware have changed, and that all new ones are included in the deb. [Where problems could occur] These firmware blobs are only
[Kernel-packages] [Bug 2029899] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2029899 Title: Update firmware for hwe-6.2/oem-6.5 kernel migrations Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] When migrating to a new hwe kernel or introduced a oem kernel of a newer version, the firmware blobs might not match the expectation of the new kernel. [Fix] For linux-hwe-6.2/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/lunar \ linux-hwe-6.2/debian.hwe-6.2/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/lunar -- * d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it For linux-oem-6.5/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/mantic \ linux-oem-6.5/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/mantic -- * 41e615cf3 i915: Update ADLP DMC to v2.20 * 22fb12f2f amdgpu: add initial SMU 13.0.10 firmware * b3f512fb5 amdgpu: add initial SDMA 6.0.3 firmware * b1a7d7624 amdgpu: add initial PSP 13.0.10 firmware * d6d655ade amdgpu: add initial GC 11.0.3 firmware * b255f5b92 (tag: iwlwifi-fw-2023-06-29, korg-iwlwifi/for-upstream) iwlwifi: add new FWs from core80-39 release * 84d5550e9 amdgpu: update aldebaran firmware for amd.5.5 release * 08b854f02 rtlwifi: Add firmware v6.0 for RTL8192FU * 9f7502f1d rtw89: 8852b: update format-1 fw to v0.29.29.1 * 78a8782a9 (tag: iwlwifi-fw-2023-03-30) iwlwifi: add new FWs from core78-32 release * 7f490a9a4 Merge branch 'dmc-adlp_2.19-mtl_2.12' of git://anongit.freedesktop.org/drm/drm-firmware |\ | * 4ee236dbb i915: Update ADLP DMC to v2.19 * | 2c07f017f rtw89: 8852b: update format-1 fw to v0.29.29.0 * | b50cf9205 rtw89: 8852b: add format-1 fw v0.29.26.0 |/ * 6a55abe94 Merge https://github.com/pkshih/linux-firmware |\ | * 4cc3eda63 rtlwifi: Add firmware v16.0 for RTL8710BU aka RTL8188GU * | d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet |/ * 3653d692b rtl_bt: Add firmware and config files for RTL8821CS * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * a5046f435 (drm/dmc-adlp_2.18) i915: Add DMC v2.18 for ADLP * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it [Test Case] Boot linux-oem-6.5, linux-hwe-6.2 with Jammy base system. Also test that none of the original firmware have changed, and that all new ones are included in the deb. [Where problems could occur] These firmware blobs are only referenced in the new hwe/oem kernels, and shall not have side effect. [Other Info] While there is no hwe/oem kernel planned for Lunar, so only Jammy is nominated for fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043542] [NEW] Add MT7925 WiFi/BT support
Public bug reported: * WiFi - https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/ * ebe81e6b8659 wifi: mt76: connac: add more unified event IDs * 3c1199134874 wifi: mt76: connac: add more unified command IDs * 473f26fb167e wifi: mt76: connac: add data field in struct tlv * 975cd4d6d547 wifi: mt76: connac: add eht support for tx power * e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config * d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925 * 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init * 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset * Bluetooth - https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-2039771 ** Tags added: amd oem-priority originate-from-2039771 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043542 Title: Add MT7925 WiFi/BT support Status in HWE Next: New Status in linux-oem-6.5 package in Ubuntu: New Bug description: * WiFi - https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/ * ebe81e6b8659 wifi: mt76: connac: add more unified event IDs * 3c1199134874 wifi: mt76: connac: add more unified command IDs * 473f26fb167e wifi: mt76: connac: add data field in struct tlv * 975cd4d6d547 wifi: mt76: connac: add eht support for tx power * e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config * d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925 * 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init * 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset * Bluetooth - https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041496] Re: btmgmt --index broken in Mantic
This has landed in upstream bluez now: https://github.com/bluez/bluez/commit/303925b28110469ad002ac19ce0eb9c84d6aceb2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2041496 Title: btmgmt --index broken in Mantic Status in bluez package in Ubuntu: In Progress Bug description: On Mantic: $ btmgmt --index 1 info Unable to open 1: No such file or directory (2) Index list with 1 item hci0: Primary controller addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration current settings: powered ssp br/edr le secure-conn name rpi-5b-rev1d0-f88b short name hci0: Configuration options supported options: public-address missing options: Note the error 'Unable to open...' above. The machine has only a single hci so index 1 is invalid. The correct result should be: $ btmgmt --index 1 info Reading hci1 info failed with status 0x11 (Invalid Index) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2041496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029899] Re: Update firmware for hwe-6.2/oem-6.5 kernel migrations
Redo verification based on https://wiki.ubuntu.com/KernelTeam/FirmwareUpdates: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/lunar \ linux-hwe-6.2/debian.hwe-6.2/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/mantic -- * 84d5550e9 amdgpu: update aldebaran firmware for amd.5.5 release * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it They commits we want to skip per comment #2 and #3. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2029899 Title: Update firmware for hwe-6.2/oem-6.5 kernel migrations Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] When migrating to a new hwe kernel or introduced a oem kernel of a newer version, the firmware blobs might not match the expectation of the new kernel. [Fix] For linux-hwe-6.2/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/lunar \ linux-hwe-6.2/debian.hwe-6.2/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/lunar -- * d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it For linux-oem-6.5/jammy: $ debian/scripts/list-lts-update-files \ launchpad/jammy \ launchpad/mantic \ linux-oem-6.5/debian.oem/abi/fwinfo | \ xargs git log --graph --oneline launchpad/jammy..launchpad/mantic -- * 41e615cf3 i915: Update ADLP DMC to v2.20 * 22fb12f2f amdgpu: add initial SMU 13.0.10 firmware * b3f512fb5 amdgpu: add initial SDMA 6.0.3 firmware * b1a7d7624 amdgpu: add initial PSP 13.0.10 firmware * d6d655ade amdgpu: add initial GC 11.0.3 firmware * b255f5b92 (tag: iwlwifi-fw-2023-06-29, korg-iwlwifi/for-upstream) iwlwifi: add new FWs from core80-39 release * 84d5550e9 amdgpu: update aldebaran firmware for amd.5.5 release * 08b854f02 rtlwifi: Add firmware v6.0 for RTL8192FU * 9f7502f1d rtw89: 8852b: update format-1 fw to v0.29.29.1 * 78a8782a9 (tag: iwlwifi-fw-2023-03-30) iwlwifi: add new FWs from core78-32 release * 7f490a9a4 Merge branch 'dmc-adlp_2.19-mtl_2.12' of git://anongit.freedesktop.org/drm/drm-firmware |\ | * 4ee236dbb i915: Update ADLP DMC to v2.19 * | 2c07f017f rtw89: 8852b: update format-1 fw to v0.29.29.0 * | b50cf9205 rtw89: 8852b: add format-1 fw v0.29.26.0 |/ * 6a55abe94 Merge https://github.com/pkshih/linux-firmware |\ | * 4cc3eda63 rtlwifi: Add firmware v16.0 for RTL8710BU aka RTL8188GU * | d02d58aae brcm: Add nvram for the Advantech MICA-071 tablet |/ * 3653d692b rtl_bt: Add firmware and config files for RTL8821CS * f48fbe42c ath11k: IPQ5018 hw1.0: add to WLAN.HK.2.6.0.1-00861-QCAHKSWPL_SILICONZ-1 * 9dacec6da ath11k: IPQ5018 hw1.0: add board-2.bin * a5046f435 (drm/dmc-adlp_2.18) i915: Add DMC v2.18 for ADLP * 3723b4800 brcm: add configuration files for CyberTan WC121 * e9b83572f amdgpu: updated aldebaran firmware for amd-5.4 * 9aa8db1cc rtlwifi: Add firmware v4.0 for RTL8188FU * 2c2be4215 nvidia: add GA102/GA103/GA104/GA106/GA107 signed firmware * 4ffcf980a brcm: rename Rock960 NVRAM to AP6356S and link devices to it [Test Case] Boot linux-oem-6.5, linux-hwe-6.2 with Jammy base system. Also test that none of the original firmware have changed, and that all new ones are included in the deb. [Where problems could occur] These firmware blobs are only referenced in the new hwe/oem kernels, and shall not have side effect. [Other Info] While there is no hwe/oem kernel planned for Lunar, so only Jammy is nominated for fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2029899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043515] Re: Black screen on 6.5
*** This bug is a duplicate of bug 2042867 ***
https://bugs.launchpad.net/bugs/2042867
** This bug has been marked a duplicate of bug 2042867
Changing display resolution leads into black screen
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2043515
Title:
Black screen on 6.5
Status in linux package in Ubuntu:
New
Bug description:
Hello, the screen stays black under many resolutions on Ryzen on
kernel 6.5. It worked well up until the update (from 6.2). It seems to
be a known regression already fixed in upstream. Could you also apply
the patch https://www.spinics.net/lists/stable/msg679132.html? Thank
you.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Nov 14 22:48:59 2023
InstallationDate: Installed on 2023-08-07 (99 days ago)
InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-03 (12 days ago)
dmi.bios.date: 08/08/2023
dmi.bios.release: 1.35
dmi.bios.vendor: LENOVO
dmi.bios.version: R22ET65W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CNS17C00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 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.27
dmi.modalias:
dmi:bvnLENOVO:bvrR22ET65W(1.35):bd08/08/2023:br1.35:efr1.27:svnLENOVO:pn21CNS17C00:pvrThinkPadX13Gen3:rvnLENOVO:rn21CNS17C00:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CN_BU_Think_FM_ThinkPadX13Gen3:
dmi.product.family: ThinkPad X13 Gen 3
dmi.product.name: 21CNS17C00
dmi.product.sku: LENOVO_MT_21CN_BU_Think_FM_ThinkPad X13 Gen 3
dmi.product.version: ThinkPad X13 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043515/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043493] Re: Logitech StreamCam driver broken with update
*** This bug is a duplicate of bug 2043197 *** https://bugs.launchpad.net/bugs/2043197 ** This bug has been marked a duplicate of bug 2043197 USB bus error after upgrading to proposed kernel on lunar and jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043493 Title: Logitech StreamCam driver broken with update Status in linux package in Ubuntu: New Bug description: My Logitech StreamCam works with linux-image-5.15.0-88. With linux-image-5.15.0-90 it does not work and instead I get the syslog messages when plugging in such as that below (a longer extract is attached). Nov 14 16:02:12 mylaptop kernel: [ 482.608545] pci_bus :04: Allocating resources Nov 14 16:02:12 mylaptop kernel: [ 482.608572] pcieport :04:02.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 39] add_size 20 add_align 10 Nov 14 16:02:12 mylaptop kernel: [ 482.608584] pcieport :04:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608586] pcieport :04:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608590] pcieport :04:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608591] pcieport :04:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608594] pcieport :00:1c.4: PCI bridge to [bus 03-6d] Nov 14 16:02:12 mylaptop kernel: [ 482.608597] pcieport :00:1c.4: bridge window [io 0x2000-0x5fff] Nov 14 16:02:12 mylaptop kernel: [ 482.608601] pcieport :00:1c.4: bridge window [mem 0xac00-0xda0f] Nov 14 16:02:12 mylaptop kernel: [ 482.608604] pcieport :00:1c.4: bridge window [mem 0x6000-0xa9ff 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.948297] usb 4-2: new SuperSpeed USB device number 2 using xhci_hcd Nov 14 16:02:12 mylaptop kernel: [ 482.972432] usb 4-2: device descriptor read/8, error -71 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 2917 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 15:57:47 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378 InstallationDate: Installed on 2018-08-31 (1900 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package
when will this change be deployed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042912 Title: System hang after unplug/plug DP monitor with AMD W7500 card Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] The patch make sure MACO is supported only if BACO is supported. It creates a stricter rule for MACO to avoid MACO is enabled with BACO supports. It should be safe to apply stricter rules to enable features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039858] Re: Wireless not working on Dell XPS 9320 1360P (Intel 6E AX211 Wireless card) with kernel version 6.1.0-1023-oem on Ubuntu 22.04
The Intel 6E AX211 wireless card in my Dell XPS 13 Plus 9320 laptop does not work with kernel version 6.1.0-1025-oem on Ubuntu 22.04. After a week of trying to solve this, I found this page. Downgrading to kernel version 6.1.0-1024-oem solved the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2039858 Title: Wireless not working on Dell XPS 9320 1360P (Intel 6E AX211 Wireless card) with kernel version 6.1.0-1023-oem on Ubuntu 22.04 Status in linux-signed-oem-6.1 package in Ubuntu: Confirmed Bug description: Posting here since there are barely any reports on this issue except this Intel community forum ticket. https://community.intel.com/t5/Wireless/Wifi-is-not-working-on- ubuntu/m-p/1532192/thread-id/50189 In recent days (Oct 16 2023) wireless suddenly stopped working and the "wireless adapter not found" message is printed in Ubuntu's Wireless settings. The above ticket has most of the technical details, but it looks like it's an issue with the recent kernel version 6.1.0-1023-oem and happens on Dell XPS 9320 with Intel 6E AX211 Wireless Card. Note Intel have returned to the issue submitter and ask him to turn the issue back to Dell. Beats me why can't these two corporations figure the issue on their own and ask the user to act as a proxy. The current temporary solution until this issue is investigated and resolved is to downgrade the kernel version. The second most recent version I had available was 6.0.0-1021-oem and it resolved the issue. I followed this guide and it resolved it for me. https://www.groovypost.com/howto/how-to-downgrade-the-kernel-in- ubuntu/ Note that running Ubuntu updates can re-update your kernel version back. Link to "Ask Ubuntu" question since this issue took a considerable amount of my time to pinpoint. Hoping to save others the trouble: https://askubuntu.com/questions/1489313/wireless-not-working-on-dell- xps-9320-1360p-intel-6e-ax211-wireless-card-with To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.1/+bug/2039858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
Hi, the devel release (noble) was the same as mantic's changelog and didn't have the fix. I'm uploading the debdiff for noble also. I hope this answers your question. Please let me know if I missed something. Thanks. ** Patch added: "alsa-ucm-conf_1.2.9-1ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+attachment/5719456/+files/alsa-ucm-conf_1.2.9-1ubuntu4.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: New Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043515] Re: Black screen on 6.5
Huh, I have just noticed bug 2042867 which might even raise the true fix
for the issue. I am sorry for the churn.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2043515
Title:
Black screen on 6.5
Status in linux package in Ubuntu:
New
Bug description:
Hello, the screen stays black under many resolutions on Ryzen on
kernel 6.5. It worked well up until the update (from 6.2). It seems to
be a known regression already fixed in upstream. Could you also apply
the patch https://www.spinics.net/lists/stable/msg679132.html? Thank
you.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Nov 14 22:48:59 2023
InstallationDate: Installed on 2023-08-07 (99 days ago)
InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-03 (12 days ago)
dmi.bios.date: 08/08/2023
dmi.bios.release: 1.35
dmi.bios.vendor: LENOVO
dmi.bios.version: R22ET65W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CNS17C00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 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.27
dmi.modalias:
dmi:bvnLENOVO:bvrR22ET65W(1.35):bd08/08/2023:br1.35:efr1.27:svnLENOVO:pn21CNS17C00:pvrThinkPadX13Gen3:rvnLENOVO:rn21CNS17C00:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CN_BU_Think_FM_ThinkPadX13Gen3:
dmi.product.family: ThinkPad X13 Gen 3
dmi.product.name: 21CNS17C00
dmi.product.sku: LENOVO_MT_21CN_BU_Think_FM_ThinkPad X13 Gen 3
dmi.product.version: ThinkPad X13 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043515/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043515] [NEW] Black screen on 6.5
Public bug reported:
Hello, the screen stays black under many resolutions on Ryzen on kernel
6.5. It worked well up until the update (from 6.2). It seems to be a
known regression already fixed in upstream. Could you also apply the
patch https://www.spinics.net/lists/stable/msg679132.html? Thank you.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Nov 14 22:48:59 2023
InstallationDate: Installed on 2023-08-07 (99 days ago)
InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-03 (12 days ago)
dmi.bios.date: 08/08/2023
dmi.bios.release: 1.35
dmi.bios.vendor: LENOVO
dmi.bios.version: R22ET65W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CNS17C00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 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.27
dmi.modalias:
dmi:bvnLENOVO:bvrR22ET65W(1.35):bd08/08/2023:br1.35:efr1.27:svnLENOVO:pn21CNS17C00:pvrThinkPadX13Gen3:rvnLENOVO:rn21CNS17C00:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CN_BU_Think_FM_ThinkPadX13Gen3:
dmi.product.family: ThinkPad X13 Gen 3
dmi.product.name: 21CNS17C00
dmi.product.sku: LENOVO_MT_21CN_BU_Think_FM_ThinkPad X13 Gen 3
dmi.product.version: ThinkPad X13 Gen 3
dmi.sys.vendor: LENOVO
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2043515
Title:
Black screen on 6.5
Status in linux package in Ubuntu:
New
Bug description:
Hello, the screen stays black under many resolutions on Ryzen on
kernel 6.5. It worked well up until the update (from 6.2). It seems to
be a known regression already fixed in upstream. Could you also apply
the patch https://www.spinics.net/lists/stable/msg679132.html? Thank
you.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Nov 14 22:48:59 2023
InstallationDate: Installed on 2023-08-07 (99 days ago)
InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-03 (12 days ago)
dmi.bios.date: 08/08/2023
dmi.bios.release: 1.35
dmi.bios.vendor: LENOVO
dmi.bios.version: R22ET65W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CNS17C00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 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.27
dmi.modalias:
dmi:bvnLENOVO:bvrR22ET65W(1.35):bd08/08/2023:br1.35:efr1.27:svnLENOVO:pn21CNS17C00:pvrThinkPadX13Gen3:rvnLENOVO:rn21CNS17C00:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CN_BU_Think_FM_ThinkPadX13Gen3:
dmi.product.family: ThinkPad X13 Gen 3
dmi.product.name: 21CNS17C00
dmi.product.sku: LENOVO_MT_21CN_BU_Think_FM_ThinkPad X13 Gen 3
dmi.product.version: ThinkPad X13 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043515/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot
Hello Ian, It looks like we are mounting /dev: here is how /dev is mounted when you use the cm-chroot-sw-image command, jd-b91-s15sp4-11-07:~ # mount | grep image udev on /cm/images/default-image/dev type devtmpfs (rw,relatime,size=4096k,nr_inodes=1048576,mode=755,inode64) devpts on /cm/images/default-image/dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000) proc on /cm/images/default-image/proc type proc (rw,relatime) sysfs on /cm/images/default-image/sys type sysfs (rw,relatime) tmpfs on /cm/images/default-image/run type tmpfs (rw,relatime,inode64) It looks like the tar file DGXOS-6.1.0-DGX-H100.tar.gz is too large to upload here. If you have an alternate location, I can upload it there. --Sam -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2043059 Title: Installation errors out when installing in a chroot Status in linux-nvidia package in Ubuntu: New Bug description: Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.15.0-1040-nvidia ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.15.0-1040-nvidia cryptsetup: WARNING: Couldn't determine root device W: Couldn't identify type of root file system for fsck hook cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-5.15.0-1040-nvidia mkinitramfs: failed to determine device for / mkinitramfs: workaround is MODULES=most, check: grep -r MODULES /var/lib/kdump/initramfs-tools Error please report bug on initramfs-tools Include the output of 'mount' and 'cat /proc/mounts' update-initramfs: failed for /var/lib/kdump/initrd.img-5.15.0-1040-nvidia with 1. run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1 dpkg: error processing package linux-image-5.15.0-1040-nvidia (--configure): installed linux-image-5.15.0-1040-nvidia package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-5.15.0-1040-nvidia E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2043059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039732] Re: No graphic desktop environment on Google GCP instances
Kyler Can you please clarify who is asking who to verify proposed solution in linux-gcp/6.5.0-1009.9 kernel in comment#3 above? Is it waiting on Google or this is between your internal canonical teams? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039732 Title: No graphic desktop environment on Google GCP instances Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google reports not being able to display graphic desktop environment. [Fix] * CONFIG_SYSFB_SIMPLEFB was initially enabled in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next=0bf2a2472f71a3001a8a9a0849b6bed7e7069a7b. It was subsequently disabled for amd64 in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=master- next=40b0ce0833309133453c3dbc19753f62084c0a7a. This was not reflected in the GCP kernel config. [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression. Simple config change that was not taken from generic. [Other Info] * SF #00366439 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages
The attachment "use-triggers.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250109 Title: Please use dpkg-triggers for update-grub when installing or removing kernel packages Status in grub2 package in Ubuntu: In Progress Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in grub2 package in Debian: Won't Fix Bug description: Currently the kernel package runs update-grub every time one is installed or removed. This results in it being run a dozen times during a dist-upgrade, and this is rather time consuming and annoying. Please use a dpkg trigger to cause update-grub to be run only once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
Installed: https://github.com/AdnanHodzic/auto-cpufreq And sometimes it works and somtimes not. using the ap fucntion with the script below helps sometimes. https://github.com/benicovdw/manage-cpufreq/blob/main/manage_governor.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 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.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages
update-initramfs -c call by kernel postinst hook is not covered, but we need to make sure the initramfs is there at kernel configuration point because we need it to be there when updating boot loaders. e.g. if we triggered both in that case, update-grub could run before update-initramfs. if we included an initramfs-tools hook to run update-grub, update-grub could be run twice but update-initramfs only once. I propose we keep this bug for grub2 change to match upstream, but it may be worth revisiting how we can merge update-initramfs -c and update- initramfs -u calls when updating kernels and other packages touching initramfs in one session. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250109 Title: Please use dpkg-triggers for update-grub when installing or removing kernel packages Status in grub2 package in Ubuntu: In Progress Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in grub2 package in Debian: Won't Fix Bug description: Currently the kernel package runs update-grub every time one is installed or removed. This results in it being run a dozen times during a dist-upgrade, and this is rather time consuming and annoying. Please use a dpkg trigger to cause update-grub to be run only once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages
Draft fix for update-grub: https://salsa.debian.org/grub- team/grub/-/merge_requests/46 Still need to take care of grub-install at some point, haven't figured out the best approach there yet. ** Changed in: grub2 (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: grub2 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250109 Title: Please use dpkg-triggers for update-grub when installing or removing kernel packages Status in grub2 package in Ubuntu: In Progress Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in grub2 package in Debian: Won't Fix Bug description: Currently the kernel package runs update-grub every time one is installed or removed. This results in it being run a dozen times during a dist-upgrade, and this is rather time consuming and annoying. Please use a dpkg trigger to cause update-grub to be run only once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages
@Andy I'm unassigning you and changing the bug status as the initramfs part has been resolved, update-initramfs does if [ -n "$DPKG_MAINTSCRIPT_PACKAGE" ] && [ $# = 1 ] && [ "$1" = -u ]; then if dpkg-trigger --no-await update-initramfs; then echo "update-initramfs: deferring update (trigger activated)" exit 0 fi fi We can patch grub to do the same ** Changed in: initramfs-tools (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: initramfs-tools (Ubuntu) Assignee: Andy Whitcroft (apw) => (unassigned) ** Changed in: linux (Ubuntu) Assignee: Andy Whitcroft (apw) => (unassigned) ** Changed in: grub2 (Ubuntu) Assignee: Andy Whitcroft (apw) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1250109 Title: Please use dpkg-triggers for update-grub when installing or removing kernel packages Status in grub2 package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in grub2 package in Debian: Won't Fix Bug description: Currently the kernel package runs update-grub every time one is installed or removed. This results in it being run a dozen times during a dist-upgrade, and this is rather time consuming and annoying. Please use a dpkg trigger to cause update-grub to be run only once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042363] Comment bridged from LTC Bugzilla
--- Comment From david_pa...@uk.ibm.com 2023-11-14 05:51 EDT--- Ok, I will arrange for an update/upgrade to the latest kernel in the next week or so and turn on those rpcdebug settings when testing the issue. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042363 Title: AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl() on a Ubuntu 20.04 NFSV4 server Status in linux package in Ubuntu: New Bug description: ---Problem Description--- AIX 7.3 NFS client frequently returns an EIO error to an application when reading or writing to a file that has been locked with fcntl(). NFS server is Ubuntu 20.04.6 LTS, GNU/Linux 5.4.0-139-generic x86_64. The problem does not appear to affect other combinations of NFS client (including AIX 7.2) with this NFS server. The AIX team have indicated that the cause of the EIO is triggered by the NFS server returning a BAD_SEQID error which leads to the AIX NFS client incorrectly zeroing the stateid, which then leads to the NFS server returning a BAD_STATEID error and the NFS client then returns the EIO error. The AIX team would like to understand why the BAD_SEQID has been returned. ---uname output--- Linux duckseason 5.4.0-156-generic #173-Ubuntu SMP Tue Jul 11 07:25:22 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Machine Type = VMware ESXi Server 7.0 4 x Intel(R) Xeon(R) Gold 6348H CPU @ 2.30GHz ---Steps to Reproduce--- We cannot offer a simple way to recreate the problem as it involves IBM MQ running on two primary machines (AIX) using the Ubuntu server for it's HA NFSv4 storage. However, we can provide any requested trace or dumps from any or all of the involved machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1628204] Re: linux: 4.4.0-41.61 -proposed tracker
best iformation about the https://thepetblogs.com/micro-bully/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007050 Title: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password) Status in initramfs-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Bug description: With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. -- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3 libtext-iconv-perl 1.7-7build3 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.3-2 libtirpc-common 1.3.2-2ubuntu0.1 libtirpc3 1.3.2-2ubuntu0.1 libudev1 249.11-0ubuntu3.6 libunistring2 1.0-1 libuuid1 2.37.2-4ubuntu3 libxxhash0 0.8.1-1 libzstd1 1.4.8+dfsg-3build1 linux-base 4.5ubuntu9 linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1 logsave 1.46.5-2ubuntu1.1 lsb-base 11.1.0ubuntu4 mount 2.37.2-4ubuntu3 openssl 3.0.2-0ubuntu1.8 os-prober 1.79ubuntu2 passwd 1:4.8.1-2ubuntu2.1 perl-base 5.34.0-3ubuntu1.1 sensible-utils 0.0.17 systemd-hwe-hwdb 249.11.2 tar 1.34+dfsg-1build3 ubuntu-keyring 2021.03.26 ucf 3.0043 udev 249.11-0ubuntu3.6 util-linux 2.37.2-4ubuntu3 uuid-runtime 2.37.2-4ubuntu3 zlib1g 1:1.2.11.dfsg-2ubuntu9.2 zstd 1.4.8+dfsg-3build1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-12 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: linux-image-5.19.0-28-generic 5.19.0-28.29~22.04.1 PackageArchitecture: amd64 ProcCpuinfoMinimal: processor: 7 vendor_id: GenuineIntel cpu family : 6 model: 140 model name : 11th
[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device
Hi, I see debdiffs for the stable releases, but what's the status of the devel release? It is Fix Released already? Can you please adjust the bug tasks accordingly? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: New Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
Forwarded adding surface_aggregator_registry to dracut: https://github.com/dracutdevs/dracut/pull/2558 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007050 Title: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password) Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. -- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3 libtext-iconv-perl 1.7-7build3 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.3-2 libtirpc-common 1.3.2-2ubuntu0.1 libtirpc3 1.3.2-2ubuntu0.1 libudev1 249.11-0ubuntu3.6 libunistring2 1.0-1 libuuid1 2.37.2-4ubuntu3 libxxhash0 0.8.1-1 libzstd1 1.4.8+dfsg-3build1 linux-base 4.5ubuntu9 linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1 logsave 1.46.5-2ubuntu1.1 lsb-base 11.1.0ubuntu4 mount 2.37.2-4ubuntu3 openssl 3.0.2-0ubuntu1.8 os-prober 1.79ubuntu2 passwd 1:4.8.1-2ubuntu2.1 perl-base 5.34.0-3ubuntu1.1 sensible-utils 0.0.17 systemd-hwe-hwdb 249.11.2 tar 1.34+dfsg-1build3 ubuntu-keyring 2021.03.26 ucf 3.0043 udev 249.11-0ubuntu3.6 util-linux 2.37.2-4ubuntu3 uuid-runtime 2.37.2-4ubuntu3 zlib1g 1:1.2.11.dfsg-2ubuntu9.2 zstd 1.4.8+dfsg-3build1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-12 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Package: linux-image-5.19.0-28-generic 5.19.0-28.29~22.04.1 PackageArchitecture: amd64 ProcCpuinfoMinimal: processor: 7 vendor_id: GenuineIntel cpu family : 6 model: 140
[Kernel-packages] [Bug 2007050] Re: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password)
I checked the included modules on Ubuntu 23.10 (linux 6.5.0-10-generic) and following modules are included: 8250_dw pinctrl_tigerlake (pinctrl-tigerlake.ko) surface_aggregator surface_hid surface_hid_core Following modules are not included, but will be included by the fix for bug #2042710: intel_lpss intel_lpss_pci Following module needs to be included (also dracut is affected): surface_aggregator_registry -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007050 Title: Microsoft Surface Laptop 4 keyboard not available during early boot (can't enter disk unlock password) Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. -- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3 libtext-iconv-perl 1.7-7build3 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.3-2 libtirpc-common 1.3.2-2ubuntu0.1 libtirpc3 1.3.2-2ubuntu0.1 libudev1 249.11-0ubuntu3.6 libunistring2 1.0-1 libuuid1 2.37.2-4ubuntu3 libxxhash0 0.8.1-1 libzstd1 1.4.8+dfsg-3build1 linux-base 4.5ubuntu9 linux-modules-5.19.0-28-generic 5.19.0-28.29~22.04.1 logsave 1.46.5-2ubuntu1.1 lsb-base 11.1.0ubuntu4 mount 2.37.2-4ubuntu3 openssl 3.0.2-0ubuntu1.8 os-prober 1.79ubuntu2 passwd 1:4.8.1-2ubuntu2.1 perl-base 5.34.0-3ubuntu1.1 sensible-utils 0.0.17 systemd-hwe-hwdb 249.11.2 tar 1.34+dfsg-1build3 ubuntu-keyring 2021.03.26 ucf 3.0043 udev 249.11-0ubuntu3.6 util-linux 2.37.2-4ubuntu3 uuid-runtime 2.37.2-4ubuntu3 zlib1g 1:1.2.11.dfsg-2ubuntu9.2 zstd 1.4.8+dfsg-3build1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-12 (0 days
[Kernel-packages] [Bug 2030972] Re: No speakers sound on MSI Cyborg 15 A12V (Alder Lake PCH-P High Definition Audio)
No news about this bug? No fixes or workarounds? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2030972 Title: No speakers sound on MSI Cyborg 15 A12V (Alder Lake PCH-P High Definition Audio) Status in linux package in Ubuntu: Confirmed Bug description: Recently my brother bought this gaming Laptop ( https://www.msi.com/Laptop/Cyborg-15-A12VX/Specification ) , and I installed on it Ubuntu 23.04 (6.2.0-26-generic) . Everything works great, but he can't hear nothing on the laptop speakers. If he plug a headphones, or use HDMI don't have this problem. I see a lot of similar issues with this audio device, Alder Lake PCH-P High Definition Audio, in other distros and seems to be an old kernel problem: https://askubuntu.com/questions/1454834/no-sound-out-of-laptop- speakers-with-alder-lake-audio-controller https://bugzilla.kernel.org/show_bug.cgi?id=216311 I hope it will be fixed soon to avoid having to use headphones. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-07-05 (48 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Micro-Star International Co., Ltd. Cyborg 15 A12VF NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=gl_ES.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic root=UUID=1900688e-0b4b-4a99-839b-91e783371cf8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 Tags: lunar Uname: Linux 6.2.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 03/27/2023 dmi.bios.release: 3.9 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E15K1IMS.309 dmi.board.asset.tag: Default string dmi.board.name: MS-15K1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE15K1IMS.309:bd03/27/2023:br3.9:svnMicro-StarInternationalCo.,Ltd.:pnCyborg15A12VF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-15K1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku15K1.3: dmi.product.family: GF dmi.product.name: Cyborg 15 A12VF dmi.product.sku: 15K1.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2030972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039869] Re: Devlink reload hangs: fix race and lock issue
** Tags removed: verification-needed-jammy-linux-bluefield
** Tags added: verification-done-jammy-linux-bluefield
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2039869
Title:
Devlink reload hangs: fix race and lock issue
Status in linux-bluefield package in Ubuntu:
Invalid
Status in linux-bluefield source package in Jammy:
Fix Committed
Bug description:
Summary:
Machine hangs when doing devlink reload
How to reproduce:
Host:
[root@bu-lab24v ~]# echo '2' > /sys/class/net/ens2f0np0/device/sriov_numvfs
Arm:
root@bu-lab24v-oob:~# uname -r
5.15.0-1027-bluefield
root@bu-lab24v-oob:~# devlink dev eswitch set pci/:03:00.0 mode switchdev
root@bu-lab24v-oob:~# devlink dev reload pci/:03:00.0
*Hangs*
Arm dmesg:
[ 1089.747409] INFO: task devlink:8753 blocked for more than 120 seconds.
[ 1089.760560] Tainted: G OE 5.15.0-1027-bluefield
#29-Ubuntu
[ 1089.775086] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 1089.790829] task:devlink state:D stack:0 pid: 8753 ppid: 5090
flags:0x0004
[ 1089.790838] Call trace:
[ 1089.790840] __switch_to+0xf8/0x150
[ 1089.790857] __schedule+0x2b8/0x790
[ 1089.790865] schedule+0x64/0x140
[ 1089.790870] schedule_preempt_disabled+0x18/0x24
[ 1089.790874] __mutex_lock.constprop.0+0x1a0/0x680
[ 1089.790878] __mutex_lock_slowpath+0x40/0x90
[ 1089.790883] mutex_lock+0x64/0x70
[ 1089.790887] devl_lock+0x1c/0x30
[ 1089.790893] mlx5_detach_device+0x58/0x190 [mlx5_core]
[ 1089.791055] mlx5_unload_one+0x40/0xe4 [mlx5_core]
[ 1089.791177] mlx5_devlink_reload_down+0x184/0x270 [mlx5_core]
[ 1089.791318] devlink_reload+0x214/0x290
Fixes:
Checking the OFED source code, we found this missing devl trap group
also need to be backported to avoid deadlock.
void mlx5_detach_device(struct mlx5_core_dev *dev, bool suspend)
{
...
#ifdef HAVE_DEVL_PORT_REGISTER
#ifdef HAVE_DEVL_TRAP_GROUPS_REGISTER
devl_assert_locked(priv_to_devlink(dev));
#else
devl_lock(devlink);
#endif /* HAVE_DEVL_TRAP_GROUPS_REGISTER */
#endif /* HAVE_DEVL_PORT_REGISTER */
mutex_lock(_intf_mutex);
#ifdef HAVE_DEVL_PORT_REGISTER
Related issue:
#2032378 Devlink backport: fix race and lock issue
So cherry-pick the patch below
commit 852e85a704c2e11c050bdea286bc438aba4f4a22
Author: Jiri Pirko
Date: Sat Jul 16 13:02:34 2022 +0200
net: devlink: add unlocked variants of devling_trap*() functions
Add unlocked variants of devl_trap*() functions to be used in drivers
called-in with devlink->lock held.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2039869/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-6-generic and above (MANTIC)
just did another fresh noble xubuntu daily install .. 11/14/2023
bluetooth sound is jittery .. even without a browser
started..vmlinux-6.5.0-9-generic .. is on the install media..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038539
Title:
bluetooth connections are unstable with linux-image-6.5.0-6-generic
and above (MANTIC)
Status in linux package in Ubuntu:
New
Bug description:
Seems some random network activity regularly breaks bluetooth connections..
headphones connect and reconnect or suffer breaks in sound etc.
Started with this kernel version linux-image-6.5.0-7 .. previous kernel
linux-image-6.5.0-5 works perfectly
Booting into the older kernel restores bluetooth stability.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-7-generic 6.5.0-7.7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1690 F wireplumber
/dev/snd/controlC0: derk 1690 F wireplumber
/dev/snd/seq:derk 1687 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Thu Oct 5 08:33:01 2023
InstallationDate: Installed on 2023-10-04 (1 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Slim 5 16ABR8
dmi.ec.firmware.release: 1.21
dmi.modalias:
dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8:
dmi.product.family: IdeaPad Slim 5 16ABR8
dmi.product.name: 82XG
dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8
dmi.product.version: IdeaPad Slim 5 16ABR8
dmi.sys.vendor: LENOVO
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derk 1691 F wireplumber
/dev/snd/controlC0: derk 1691 F wireplumber
/dev/snd/seq:derk 1688 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-10-04 (12 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
Tags: mantic
Uname: Linux 6.5.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: L9CN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad Slim 5 16ABR8
dmi.ec.firmware.release: 1.21
dmi.modalias:
[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10
Hi,
I had another look, and it seems like the Ubuntu package is not including the
iwlwifi-QuZucode files.
Instead it contains the files in a compressed format: iwlwifi-QuZucode.zst
So I assume the system searches for the uncompressed files, which are not
present on my system after doing a clean install.
I checked the Ubuntu 23.04 version of the linux-firmware package, and
that one does contain the .ucode files:
https://packages.ubuntu.com/lunar/linux-firmware
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2040106
Title:
Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and
bluetooth did not work anymore.
Looking at the dmesg output I saw this:
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
..
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
no suitable firmware found!
minimum version required: iwlwifi-QuZ-a0-hr-b0-39
minimum version required: iwlwifi-QuZ-a0-hr-b0-59
These files did seem to exist in /lib/firmware.
I did sudo apt install linux-firmware/mantic --reinstall
Which did not fix it.
I manually overwrote the iwlwifi... files with the corresponding files from
linux-firmware-20230804.tar.gz and this did fix the issue.
I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.
So my best guess is that something is wrong in the latest firmware
package.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
apt-cache policy linux-firmware
linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
*** 20230919.git3672ccab-0ubuntu2.1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
Uname: Linux 5.10.0-1053-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: joep 2545 F wireplumber
/dev/snd/controlC0: joep 2545 F wireplumber
/dev/snd/seq:joep 2537 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 15:19:18 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85
InstallationDate: Installed on 2021-10-16 (736 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1053-oem N/A
linux-backports-modules-5.10.0-1053-oem N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
dmi.bios.date: 07/13/2023
dmi.bios.release: 1.22
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.22.0
dmi.board.name: 0NG7N9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5560
dmi.product.sku: 0A62
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2040106/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040526] Re: Backport RDMA DMABUF
** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** No longer affects: linux (Ubuntu Jammy) ** No longer affects: linux-nvidia (Ubuntu Jammy) ** Changed in: linux-nvidia (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia (Ubuntu) Assignee: (unassigned) => Ian May (ian-may) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2040526 Title: Backport RDMA DMABUF Status in linux package in Ubuntu: Won't Fix Status in linux-nvidia package in Ubuntu: Fix Committed Bug description: SRU Justification: [Impact] * From Nvidia: "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths." Upstream Reference https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ The patch "[PATCH 1/4] net/mlx5: Add IFC bits for mkey ATS" is already in Jammy and was included in: "2a1e6097e9b9 UBUNTU: SAUCE: RDMA/core: Updated ib_peer_memory" [Test Plan] * Testing instructions are outlined in the SF case and has been tested on in house hardware and externally by Nvidia. [Where problems could occur?] * This introduces new code paths so regression potential should be low. [Other Info] * SF#00370664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040526] Re: Backport RDMA DMABUF
** Package changed: linux-nvidia (Ubuntu) => linux (Ubuntu) ** Also affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2040526 Title: Backport RDMA DMABUF Status in linux package in Ubuntu: Won't Fix Status in linux-nvidia package in Ubuntu: Fix Committed Bug description: SRU Justification: [Impact] * From Nvidia: "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths." Upstream Reference https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ The patch "[PATCH 1/4] net/mlx5: Add IFC bits for mkey ATS" is already in Jammy and was included in: "2a1e6097e9b9 UBUNTU: SAUCE: RDMA/core: Updated ib_peer_memory" [Test Plan] * Testing instructions are outlined in the SF case and has been tested on in house hardware and externally by Nvidia. [Where problems could occur?] * This introduces new code paths so regression potential should be low. [Other Info] * SF#00370664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043493] Re: Logitech StreamCam driver broken with update
** Attachment added: "Extract of syslog after plugging in Logitech StreamCam" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043493/+attachment/5719317/+files/syslog-extract.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043493 Title: Logitech StreamCam driver broken with update Status in linux package in Ubuntu: New Bug description: My Logitech StreamCam works with linux-image-5.15.0-88. With linux-image-5.15.0-90 it does not work and instead I get the syslog messages when plugging in such as that below (a longer extract is attached). Nov 14 16:02:12 mylaptop kernel: [ 482.608545] pci_bus :04: Allocating resources Nov 14 16:02:12 mylaptop kernel: [ 482.608572] pcieport :04:02.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 39] add_size 20 add_align 10 Nov 14 16:02:12 mylaptop kernel: [ 482.608584] pcieport :04:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608586] pcieport :04:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608590] pcieport :04:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608591] pcieport :04:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608594] pcieport :00:1c.4: PCI bridge to [bus 03-6d] Nov 14 16:02:12 mylaptop kernel: [ 482.608597] pcieport :00:1c.4: bridge window [io 0x2000-0x5fff] Nov 14 16:02:12 mylaptop kernel: [ 482.608601] pcieport :00:1c.4: bridge window [mem 0xac00-0xda0f] Nov 14 16:02:12 mylaptop kernel: [ 482.608604] pcieport :00:1c.4: bridge window [mem 0x6000-0xa9ff 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.948297] usb 4-2: new SuperSpeed USB device number 2 using xhci_hcd Nov 14 16:02:12 mylaptop kernel: [ 482.972432] usb 4-2: device descriptor read/8, error -71 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 2917 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 15:57:47 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378 InstallationDate: Installed on 2018-08-31 (1900 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043493] [NEW] Logitech StreamCam driver broken with update
Public bug reported: My Logitech StreamCam works with linux-image-5.15.0-88. With linux-image-5.15.0-90 it does not work and instead I get the syslog messages when plugging in such as that below (a longer extract is attached). Nov 14 16:02:12 mylaptop kernel: [ 482.608545] pci_bus :04: Allocating resources Nov 14 16:02:12 mylaptop kernel: [ 482.608572] pcieport :04:02.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 39] add_size 20 add_align 10 Nov 14 16:02:12 mylaptop kernel: [ 482.608584] pcieport :04:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608586] pcieport :04:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608590] pcieport :04:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608591] pcieport :04:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608594] pcieport :00:1c.4: PCI bridge to [bus 03-6d] Nov 14 16:02:12 mylaptop kernel: [ 482.608597] pcieport :00:1c.4: bridge window [io 0x2000-0x5fff] Nov 14 16:02:12 mylaptop kernel: [ 482.608601] pcieport :00:1c.4: bridge window [mem 0xac00-0xda0f] Nov 14 16:02:12 mylaptop kernel: [ 482.608604] pcieport :00:1c.4: bridge window [mem 0x6000-0xa9ff 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.948297] usb 4-2: new SuperSpeed USB device number 2 using xhci_hcd Nov 14 16:02:12 mylaptop kernel: [ 482.972432] usb 4-2: device descriptor read/8, error -71 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 2917 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 15:57:47 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378 InstallationDate: Installed on 2018-08-31 (1900 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy package-from-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043493 Title: Logitech StreamCam driver broken with update Status in linux package in Ubuntu: New Bug description: My Logitech StreamCam works with linux-image-5.15.0-88. With linux-image-5.15.0-90 it does not work and instead I get the syslog messages when plugging in such as that below (a longer extract is attached). Nov 14 16:02:12 mylaptop kernel: [ 482.608545] pci_bus :04: Allocating resources Nov 14 16:02:12 mylaptop kernel: [ 482.608572] pcieport :04:02.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 39] add_size 20 add_align 10 Nov 14 16:02:12 mylaptop kernel: [ 482.608584] pcieport :04:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608586] pcieport :04:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608590] pcieport :04:02.0: BAR 15: no space for [mem size
[Kernel-packages] [Bug 2040526] Re: Backport RDMA DMABUF
** Package changed: linux (Ubuntu) => linux-nvidia (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2040526 Title: Backport RDMA DMABUF Status in linux-nvidia package in Ubuntu: Incomplete Status in linux-nvidia source package in Jammy: Incomplete Bug description: SRU Justification: [Impact] * From Nvidia: "We are working on a high performance networking solution with real customers. That solution is being developed using the Ubuntu 22.04 LTS distro release and the distro kernel (lowlatency flavour). This “dma_buf” patchset consists of upstreamed patches that allow buffers to be shared between drivers thus enhancing performance while reducing copying of data. Our team is currently engaged in the development of a high-performance networking solution tailored to meet the demands of real-world customers. This cutting-edge solution is being crafted on the foundation of Ubuntu 22.04 LTS, utilizing the distribution's kernel, specifically the lowlatency flavor. At the heart of our innovation lies the transformative "dma_buf" patchset, comprising a series of patches that have been integrated into the upstream kernel in 5.16 and 5.17. These patches introduce a groundbreaking capability: enabling the seamless sharing of buffers among various drivers. This not only bolsters the solution's performance but also minimizes the need for data copying, effectively enhancing efficiency across the board. The new functionality is isolated such that existing user will not execute these new code paths." Upstream Reference https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ The patch "[PATCH 1/4] net/mlx5: Add IFC bits for mkey ATS" is already in Jammy and was included in: "2a1e6097e9b9 UBUNTU: SAUCE: RDMA/core: Updated ib_peer_memory" [Test Plan] * Testing instructions are outlined in the SF case and has been tested on in house hardware and externally by Nvidia. [Where problems could occur?] * This introduces new code paths so regression potential should be low. [Other Info] * SF#00370664 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2040526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Maybe not for your G2 ALC. This ticket was specifically focused on the G4 AMN laptops. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013030] Re: button power
Hello, Same issue in Ubuntu Budgie 22.04 with kernel 6.2.0-36. See the French forum : https://forum.ubuntu-fr.org/viewtopic.php?id=2082015 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013030 Title: button power Status in linux package in Ubuntu: Confirmed Bug description: im using ubuntu budgie after update , i get error button poweer off or shutdown and restart my laptop ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-21-generic 5.19.0-21.21 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: s4ms986 F wireplumber /dev/snd/controlC0: s4ms986 F wireplumber /dev/snd/seq:s4ms984 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Tue Mar 28 14:33:29 2023 InstallationDate: Installed on 2023-03-20 (8 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Release amd64 (20221018.1) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X421DA_M413DA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=3a69deb1-040b-4c32-a1f0-1569b04a0404 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-21-generic N/A linux-backports-modules-5.19.0-21-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2021 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X421DA.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X421DA 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:bvnAmericanMegatrendsInc.:bvrX421DA.303:bd10/08/2021:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX421DA_M413DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX421DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X421DA_M413DA 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/2013030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1516025] Re: Realtek ALC3661 Alienware14 / Soundoutput / Jack
Investing basics lay the foundation for individuals seeking to navigate the world of financial markets and wealth accumulation. At its core, investing involves deploying capital with the expectation of generating returns over time. https://thefinancialappetite.net/category/getting- started/investing-basics/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1516025 Title: Realtek ALC3661 Alienware14 / Soundoutput / Jack Status in ALSA driver: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When watching the following video (but also audio from other programs) with the volume at 100%, the audio loudness is lower in comparison to the same audio being played at 100% in Windows 10: https://www.youtube.com/watch?v=YQHsXMglC9A ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imran 1619 F pulseaudio /dev/snd/controlC1: imran 1619 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 13 18:08:07 2015 HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1 InstallationDate: Installed on 2015-11-07 (5 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Alienware Alienware 14 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmware1.149.1 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2014 dmi.bios.vendor: Alienware dmi.bios.version: A09 dmi.board.name: 07MJ2Y dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A09 dmi.modalias: dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09: dmi.product.name: Alienware 14 dmi.product.version: A09 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1516025/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Hi, Does the last messages indicates that the fix will be available in an upcoming update for the OS? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags removed: verification-needed-jammy-linux-oem-6.1 verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.1 verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039816] Re: Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node scobee-kernel
This seems to be related to the way hisi_sec2 implements aead,
specifically with authenc(hmac(sha1),cbc(aes)),
authenc(hmac(sha256),cbc(aes)) and authenc(hmac(sha512),cbc(aes)). Other
aead algorithms seem to work fine as they don't rely on this module.
Notice that net:xfrm_policy.sh also fails similarly on this node, as it also
uses aes and sha1. See LP #2011414.
When running either net:vrf-xfrm-tests.sh or net:xfrm_policy.sh, we get the
same output from dmesg:
`hisi_sec2 :76:00.0: flag[3], icv[2]`, showing that something is off with
the integrity check value.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2039816
Title:
Regression for net:vrf-xfrm-tests.sh with 5.15 kernel on ARM64 node
scobee-kernel
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Bug description:
Issue found on ARM64 node scobee-kernel with:
* J-5.15.0-86.95 lowlatency
* 5.15.0-85.95~20.04.2 generic
* F-5.15.0-86.95~20.04.1 lowlatency
* F-5.15.0-87.96~20.04.1 lowlatency-64k
Test failed with:
$ sudo ./vrf-xfrm-tests.sh
No qdisc on VRF device
TEST: IPv4 no xfrm policy [ OK ]
TEST: IPv6 no xfrm policy [ OK ]
TEST: IPv4 xfrm policy based on address [FAIL]
TEST: IPv6 xfrm policy based on address [FAIL]
TEST: IPv6 xfrm policy with VRF in selector [ OK ]
TEST: IPv4 xfrm policy with xfrm device [FAIL]
TEST: IPv6 xfrm policy with xfrm device [FAIL]
netem qdisc on VRF device
TEST: IPv4 no xfrm policy [ OK ]
TEST: IPv6 no xfrm policy [ OK ]
TEST: IPv4 xfrm policy based on address [FAIL]
TEST: IPv6 xfrm policy based on address [FAIL]
TEST: IPv6 xfrm policy with VRF in selector [ OK ]
TEST: IPv4 xfrm policy with xfrm device [FAIL]
TEST: IPv6 xfrm policy with xfrm device [FAIL]
Tests passed: 6
Tests failed: 8
And this issue does not exist with the following combination:
* F-generic-5.15.0-86.96~20.04.1 howzit-kernel
* F-generic-5.15.0-86.96~20.04.1 wright-kernel
* F-generic-64k-5.15.0-85.95~20.04.2 kopter-kernel
* F-lowlatency-5.15.0-88.98~20.04.1 howzit-kernel
* F-lowlatency-5.15.0-85.94 starmie-kernel
* F-lowlatency-64k-5.15.0-85.94~20.04.1 howzit-kernel
* J-lowlatency-64k-5.15.0-85.94 starmie-kernel
* J-lowlatency-64k-5.15.0-86.95 howzit-kernel
So it looks like this is hardware related.
And the cause seems to be commit cb43c60 (" selftests: net: vrf-xfrm-tests:
change authentication and encryption algos"), which lands on the Jammy tree
since:
* Ubuntu-5.15.0-85.95
* Ubuntu-lowlatency-5.15.0-85.94
With this commit reverted, this test can pass on node scobee-kernel
with 5.15.0-87-lowlatency-64k
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2039816/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043400] Re: xrandr can't set default resolution
** Package changed: x11-xserver-utils (Ubuntu) => nvidia-graphics-
drivers-535 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2043400
Title:
xrandr can't set default resolution
Status in nvidia-graphics-drivers-535 package in Ubuntu:
New
Bug description:
sometimes when i play with wine and various old programs application fails
and keeps reolution which it set
when it happends, before ubuntu 23.10 i was able to launch xrandr -s
1680x1050 and had my original resolution back
after upgrade to 23.10 it doesn't work
xrandr -q lists correct resolution as first one
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 480mm x 300mm
1680x1050 59.95 +
1920x1080 59.94*
1280x1024 75.0260.02
1280x960 60.00
1280x720 60.0059.94
1152x864 75.00
1024x768 75.0370.0760.00
800x600 75.0072.1960.3256.25
640x480 75.0072.8159.9459.93
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)
but attempt to set it fails
xrandr -s 1680x1050
Size 1680x1050 not found in available modes
i can set all other resolutions (this is why current one listed is
1980x1080), except the one i need
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: x11-xserver-utils 7.7+9build1
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 13 16:52:28 2023
DistUpgraded: 2023-11-03 12:42:15,779 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING!
Diff between built and installed module!) (WARNING! Diff between built and
installed module!) (WARNING! Diff between built and installed module!)
(WARNING! Diff between built and installed module!) (WARNING! Diff between
built and installed module!)
GraphicsCard:
NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX
2070 SUPER] [1462:c729]
InstallationDate: Installed on 2022-12-23 (325 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=d944c09b-3160-4d61-9aa0-32372d3381dd ro quiet splash vt.handoff=7
SourcePackage: x11-xserver-utils
UpgradeStatus: Upgraded to mantic on 2023-11-03 (10 days ago)
dmi.bios.date: 10/27/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2806
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B550-PLUS WIFI II
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2806:bd10/27/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB550-PLUSWIFIII:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Kernel-packages] [Bug 2031287] Re: sysdig-dkms failed to build with J-6.5
moving to the right package ** Package changed: linux-oem-6.5 (Ubuntu) => sysdig (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031287 Title: sysdig-dkms failed to build with J-6.5 Status in ubuntu-kernel-tests: New Status in sysdig package in Ubuntu: Invalid Status in sysdig source package in Jammy: Confirmed Bug description: ubuntu_sysdig_smoke_test failed because of sysdig DKMS build failed with J-oem-6.5 Error! Bad return status for module build on kernel: 6.5.0-1002-oem (x86_64) Consult /var/lib/dkms/sysdig/0.27.1/build/make.log for more information. dpkg: error processing package sysdig-dkms (--configure): installed sysdig-dkms package post-installation script subprocess returned error exit status 10 Processing triggers for man-db (2.10.2-1) ... Processing triggers for libc-bin (2.35-0ubuntu3.1) ... Errors were encountered while processing: sysdig-dkms needrestart is being skipped since dpkg has failed W: --force-yes is deprecated, use one of the options starting with --allow instead. E: Sub-process /usr/bin/dpkg returned an error code (1) Running 'dkms status -m sysdig | grep installed' Running 'cat /var/lib/dkms/sysdig/*/build/make.log' DKMS make.log for sysdig-0.27.1 for kernel 6.5.0-1002-oem (x86_64) Thu Aug 10 12:17:20 UTC 2023 make: Entering directory '/usr/src/linux-headers-6.5.0-1002-oem' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0 You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0 CC [M] /var/lib/dkms/sysdig/0.27.1/build/main.o CC [M] /var/lib/dkms/sysdig/0.27.1/build/dynamic_params_table.o CC [M] /var/lib/dkms/sysdig/0.27.1/build/fillers_table.o CC [M] /var/lib/dkms/sysdig/0.27.1/build/flags_table.o CC [M] /var/lib/dkms/sysdig/0.27.1/build/ppm_events.o In file included from ./include/linux/linkage.h:7, from ./arch/x86/include/asm/cache.h:5, from ./include/linux/cache.h:6, from ./arch/x86/include/asm/current.h:9, from ./include/linux/sched.h:12, from ./arch/x86/include/asm/syscall.h:14, from /var/lib/dkms/sysdig/0.27.1/build/main.c:19: /var/lib/dkms/sysdig/0.27.1/build/main.c: In function ‘sysdig_init’: ./include/linux/export.h:29:22: error: passing argument 1 of ‘class_create’ from incompatible pointer type [-Werror=incompatible-pointer-types] 29 | #define THIS_MODULE (&__this_module) | ~^~~ | | | struct module * /var/lib/dkms/sysdig/0.27.1/build/main.c:2484:36: note: in expansion of macro ‘THIS_MODULE’ 2484 | g_ppm_class = class_create(THIS_MODULE, PROBE_DEVICE_NAME); |^~~ In file included from ./include/linux/device.h:31, from ./include/linux/cdev.h:8, from /var/lib/dkms/sysdig/0.27.1/build/main.c:26: ./include/linux/device/class.h:230:54: note: expected ‘const char *’ but argument is of type ‘struct module *’ 230 | struct class * __must_check class_create(const char *name); | ^~~~ /var/lib/dkms/sysdig/0.27.1/build/main.c:2484:23: error: too many arguments to function ‘class_create’ 2484 | g_ppm_class = class_create(THIS_MODULE, PROBE_DEVICE_NAME); | ^~~~ ./include/linux/device/class.h:230:29: note: declared here 230 | struct class * __must_check class_create(const char *name); | ^~~~ cc1: some warnings being treated as errors make[2]: *** [scripts/Makefile.build:251: /var/lib/dkms/sysdig/0.27.1/build/main.o] Error 1 make[2]: *** Waiting for unfinished jobs make[1]: *** [/usr/src/linux-headers-6.5.0-1002-oem/Makefile:2037: /var/lib/dkms/sysdig/0.27.1/build] Error 2 make: *** [Makefile:234: __sub-make] Error 2 make: Leaving directory '/usr/src/linux-headers-6.5.0-1002-oem' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034095] Re: Fix a regression from 6.3-rc1 which causes Cirrus audio codec resume failure
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Mantic) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Invalid ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034095 Title: Fix a regression from 6.3-rc1 which causes Cirrus audio codec resume failure Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] [Impact] The two CS42L42 codecs fails to output sound after runtime resume since kernel 6.3-rc1. [Fix] Backport a fix from Cirrus on https://patchwork.kernel.org/project/alsa-devel/patch/20230904160033.908135-1-vita...@opensource.cirrus.com/. [Test] 1. Power on the laptop 2. Wait for at least 1 minute after login Ubuntu 3. Go to the audio settings and press the audio output test button 4. Verify if there's any audio output [Where problems could occur] It only happens on particular audio codec and clarified by the vendor that the delay during resume will suffice after fix across different versions of kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043400] [NEW] xrandr can't set default resolution
You have been subscribed to a public bug:
sometimes when i play with wine and various old programs application fails and
keeps reolution which it set
when it happends, before ubuntu 23.10 i was able to launch xrandr -s 1680x1050
and had my original resolution back
after upgrade to 23.10 it doesn't work
xrandr -q lists correct resolution as first one
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 480mm x 300mm
1680x1050 59.95 +
1920x1080 59.94*
1280x1024 75.0260.02
1280x960 60.00
1280x720 60.0059.94
1152x864 75.00
1024x768 75.0370.0760.00
800x600 75.0072.1960.3256.25
640x480 75.0072.8159.9459.93
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)
but attempt to set it fails
xrandr -s 1680x1050
Size 1680x1050 not found in available modes
i can set all other resolutions (this is why current one listed is
1980x1080), except the one i need
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: x11-xserver-utils 7.7+9build1
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 13 16:52:28 2023
DistUpgraded: 2023-11-03 12:42:15,779 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING!
Diff between built and installed module!) (WARNING! Diff between built and
installed module!) (WARNING! Diff between built and installed module!)
(WARNING! Diff between built and installed module!) (WARNING! Diff between
built and installed module!)
GraphicsCard:
NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 2070
SUPER] [1462:c729]
InstallationDate: Installed on 2022-12-23 (325 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=d944c09b-3160-4d61-9aa0-32372d3381dd ro quiet splash vt.handoff=7
SourcePackage: x11-xserver-utils
UpgradeStatus: Upgraded to mantic on 2023-11-03 (10 days ago)
dmi.bios.date: 10/27/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2806
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B550-PLUS WIFI II
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2806:bd10/27/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB550-PLUSWIFIII:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
[Kernel-packages] [Bug 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
New
Status in linux source package in Jammy:
New
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
New
Status in linux-oem-6.1 source package in Mantic:
New
Status in linux-oem-6.5 source package in Mantic:
New
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
New
Status in linux-oem-6.5 source package in Noble:
New
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042912 Title: System hang after unplug/plug DP monitor with AMD W7500 card Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] The patch make sure MACO is supported only if BACO is supported. It creates a stricter rule for MACO to avoid MACO is enabled with BACO supports. It should be safe to apply stricter rules to enable features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043469] [NEW] Low-latency kernel can't load to desktop
Public bug reported: 23.10 fresh install. Generic kernel boots without problems. lowlatency can't boot to desktop, it gets stuck and shows black screen with cursor blinking. The same PC worked yesterday with 23.04 and low latency without problems. I have been running lowlatency kernel in this machine for a couple of years, no problems. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-lowlatency 6.5.0.10.10.10 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 12:25:24 2023 InstallationDate: Installed on 2023-11-13 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: linux-meta-lowlatency UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-lowlatency (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2043469 Title: Low-latency kernel can't load to desktop Status in linux-meta-lowlatency package in Ubuntu: New Bug description: 23.10 fresh install. Generic kernel boots without problems. lowlatency can't boot to desktop, it gets stuck and shows black screen with cursor blinking. The same PC worked yesterday with 23.04 and low latency without problems. I have been running lowlatency kernel in this machine for a couple of years, no problems. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-lowlatency 6.5.0.10.10.10 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 12:25:24 2023 InstallationDate: Installed on 2023-11-13 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: linux-meta-lowlatency UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lowlatency/+bug/2043469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029281] Re: Soundwire support for Dell SKU0C87 devices
uploaded to noble
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2029281
Title:
Soundwire support for Dell SKU0C87 devices
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Triaged
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Triaged
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2029281
== firmware-sof ==
[Impact]
Missing soundwire firmware support for Intel MTL deivces.
[Fix]
Depends on sof-bin v2.7.1 release from
https://github.com/thesofproject/sof-bin/tree/v2023.09.1. Two commits
specifically:
*
https://github.com/thesofproject/sof-bin/commit/ad8dfcc182d3e0a5ce06a7fe9ed7717a04cad06b
("Add sof-v2.7 for Intel Meteor Lake hardware")
*
https://github.com/thesofproject/sof-bin/commit/5f010669084d64df29d77a436b6ffa0095565668
("Add more sof-v2.7.1 Intel MTL binaries")
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so oem-6.5/jammy is the target
series, and Mantic for best effort MTL support. Noble is also
nominated of course.
== linux ==
[Impact]
Missing soundwire support for Dell SKU0C87 deivces.
[Fix]
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so only OEM-6.5, Mantic, and
Unstable are nominated for fix.
== original bug description ==
kernel: sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4
kernel: sof-audio-pci-intel-mtl :00:1f.3: Direct firmware load for
intel/sof-ipc4/mtl/sof-mtl.ri failed with error -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof firmware file is
missing, you might need to
kernel: sof-audio-pci-intel-mtl :00:1f.3: download it from
https://github.com/thesofproject/sof-bin/
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP
firmware -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed
err: -2
kernel: kauditd_printk_skb: 33 callbacks suppressed
Required fixes:
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2029281/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar and jammy
** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043197 Title: USB bus error after upgrading to proposed kernel on lunar and jammy Status in linux package in Ubuntu: Triaged Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: == SRU Justification == [Impact] USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel. [Fix] Use logarithmic encoding for the bMaxPacketSize0 value. [Test] With the patch applied, SuperSpeed devices can be enumerated across several reboots. [Where problems could occur] The switch case for Wireless USB (not USB WiFi dongle) was removed by the fix. I am not aware of the existence of any Wireless USB device. But if they do exist, this patch may the packet size encoding on them. == Original Bug Report == [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 16.0 dmi.bios.vendor: HP dmi.bios.version: S12 Ver. 02.16.00 dmi.board.name: 8810 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.23 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA: dmi.product.family: 103C_53307F HP ProOne dmi.product.name:
[Kernel-packages] [Bug 2034688] Re: installation of kernel headers fail with "Read-only file system" error
If you're in this inconsistent state and dpkg requires to reinstall the packages you can force the removal of the package with dpkg option --force-remove-reinstreq For instance: dpkg --purge --force-remove-reinstreq linux-headers-6.5.0-10-generic To list the packages that are half-installed use: dpkg -l "linux-headers*" Note that kernel headers are not the only package affected but everything that tries to write to kernel-protected directories will be, such as extra modules or firmware. This is a known issue and is being worked on. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034688 Title: installation of kernel headers fail with "Read-only file system" error Status in ubuntu-desktop-installer: Triaged Status in linux package in Ubuntu: In Progress Bug description: Mantic 20230907 Installation of packages that ship files in /lib/modules or /lib/firmware are expected to fail, so their installation must be prevented. For instance: $ apt install linux-headers-generic-6.3.0-7 Reading package lists... Building dependency tree... Reading state information... linux-headers-6.3.0-7 is already the newest version (6.3.0-7.7). The following packages will be upgraded: linux-headers-6.3.0-7-generic 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 51 not fully installed or removed. Need to get 0 B/3,667 kB of archives. After this operation, 27.9 MB of additional disk space will be used. (Reading database ... 132615 files and directories currently installed.) Preparing to unpack .../linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb ... Unpacking linux-headers-6.3.0-7-generic (6.3.0-7.7) over (6.3.0-7.7) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb (--unpack): error creating symbolic link './lib/modules/6.3.0-7-generic/build': Read-only file system dpkg: error while cleaning up: unable to remove newly-extracted version of '/lib/modules/6.3.0-7-generic/build': Read-only file system Errors were encountered while processing: /var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2034688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar and jammy
** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043197 Title: USB bus error after upgrading to proposed kernel on lunar and jammy Status in linux package in Ubuntu: Triaged Status in linux source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Bug description: == SRU Justification == [Impact] USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel. [Fix] Use logarithmic encoding for the bMaxPacketSize0 value. [Test] With the patch applied, SuperSpeed devices can be enumerated across several reboots. [Where problems could occur] The switch case for Wireless USB (not USB WiFi dongle) was removed by the fix. I am not aware of the existence of any Wireless USB device. But if they do exist, this patch may the packet size encoding on them. == Original Bug Report == [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 16.0 dmi.bios.vendor: HP dmi.bios.version: S12 Ver. 02.16.00 dmi.board.name: 8810 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.23 dmi.chassis.type: 13
[Kernel-packages] [Bug 2032247] Comment bridged from LTC Bugzilla
--- Comment From s...@de.ibm.com 2023-11-14 04:02 EDT--- Hi doko, are there any news regarding the cross packages? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2032247 Title: [UBUNTU 23.04] S390: static-PIE programs segfaults if libc6-dev-s390x-cross package is installed Status in Ubuntu on IBM z Systems: New Status in gcc-12 package in Ubuntu: New Status in gcc-13 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: == by Stefan == A simple helloworld program build and linked as static-PIE segfaults while startup in __libc_setup_tls: $ gcc -c -fPIE -static-pie -o hello.o hello.c $ gcc -o hello hello.o -static-pie Note: If only libc6-dev package is installed, all is fine. If both libc6-dev and libc6-dev-s390x-cross packages are installed, you will see the mentioned segfault. Linking with "-Wl,-v" dumps the used linker command and it shows the used startup-files: /usr/lib/s390x-linux-gnu/rcrt1.o => from libc6-dev /usr/s390x-linux-gnu/lib/crti.o => from libc6-dev-s390x-cross /usr/lib/gcc/s390x-linux-gnu/12/crtbeginS.o /usr/lib/gcc/s390x-linux-gnu/12/crtendS.o /usr/s390x-linux-gnu/lib/crtn.o => from libc6-dev-s390x-cross Linking as static-PIE requires the rcrt1.o file, which is not available in libc6-dev-s390x-cross package, but in libc6-dev. Due to this mixing of the startup-files, you get the segfault. This issue can be fixed by enabling static-PIE also in the libc6-dev-s390x-cross package, then all startup-files belong to the same package. For s390x static-PIE was introduced in glibc 2.36: commit "S390: Enable static PIE" (in glibc 2.36) https://sourceware.org/git/?p=glibc.git;a=commit;h=728894dba4a19578bd803906de184a8dd51ed13c There is a configure check which do a link-test to ensure that a suitable binutils(ld) version is used. Afterwards static-PIE is automatically enabled. The required binutils-patches are first included in binutils 2.39. According to the build log of package cross-toolchain-base (see https://launchpad.net/ubuntu/+source/cross-toolchain-base/66ubuntu3/+build/25689036), the libc6-dev-s390x-cross package is cross-build on x86_64 and the mentioned configure check fails: running configure fragment for sysdeps/s390/s390-64 checking for s390-specific static PIE requirements... no In this cross build, glibc is configured in order to first build the crt-startup-files, which are needed to complete the cross-gcc build. At this time, the sysroot does not contain the crt-files or libc.so itself. Thus the "linking" configure check is failing. After building the cross-gcc, glibc is build without re-configuring. Thus static-PIE is not enabled. In glibc-upstream, this configure check is now adjusted and it allows checking binutils by version number: commit "s390x: Fix static PIE condition for toolchain bootstrapping." (will be in glibc 2.39) https://sourceware.org/git/?p=glibc.git;a=commit;h=f5f96b784beb3480e0e8d10e250ca7e6063ab881 Perhaps you also have to pick the following commits by Sam James which adjusted the tests in between (both are in glibc 2.36): - commit "s390: use $READELF" https://sourceware.org/git/?p=glibc.git;a=commit;h=c376ff3287b9b0f78a4f8951313c6dae60cbdfea - commit "s390: use LC_ALL=C for readelf call" https://sourceware.org/git/?p=glibc.git;a=commit;h=2249ec60a987f9a7aa585890de2bd365b3656d28 In addition to the static-PIE configure-checks, there are those other s390-specific configure-checks to determine which IFUNC-optimizations can be build and used as default. Those also fail for libc6-dev-s390x-cross as linking is also involved: running configure fragment for sysdeps/s390 checking for __builtin_tbegin... yes checking for S390 vector instruction support... no configure: WARNING: Use binutils with vector-support in order to use optimized implementations. checking for S390 vector support in gcc... no checking for S390 arch13 zarch instruction support... no checking for S390 z10 zarch instruction support as default... no checking for S390 z196 zarch instruction support as default... no checking for S390 z13 zarch instruction support as default... no checking for S390 arch13 zarch instruction support as default... no Those checks were also adjusted in glibc-upstream. Please also pick this commits: commit "S390: Use compile-only instead of also link-tests in configure." (in glibc 2.38) https://sourceware.org/git/?p=glibc.git;a=commit;h=368b7c614b102122b86af3953daea2b30230d0a8 I've observed this issue on Ubuntu 23.04 with glibc 2.37 and binutils 2.40: binutils/lunar-updates,lunar-security,now 2.40-2ubuntu4.1 s390x [installed] libc6-dev-s390x-cross/lunar,now 2.37-0ubuntu2cross1 all [installed] libc6-dev/lunar,now 2.37-0ubuntu2 s390x [installed] libc6-s390x-cross/lunar,now
[Kernel-packages] [Bug 2034688] Re: installation of kernel headers fail with "Read-only file system" error
There are more reports of users hitting that issue on https://discourse.ubuntu.com/t/tpm-backed-full-disk-encryption-is- coming-to-ubuntu-discussion , it also seems not easy to go back to a working apt ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034688 Title: installation of kernel headers fail with "Read-only file system" error Status in ubuntu-desktop-installer: Triaged Status in linux package in Ubuntu: In Progress Bug description: Mantic 20230907 Installation of packages that ship files in /lib/modules or /lib/firmware are expected to fail, so their installation must be prevented. For instance: $ apt install linux-headers-generic-6.3.0-7 Reading package lists... Building dependency tree... Reading state information... linux-headers-6.3.0-7 is already the newest version (6.3.0-7.7). The following packages will be upgraded: linux-headers-6.3.0-7-generic 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 51 not fully installed or removed. Need to get 0 B/3,667 kB of archives. After this operation, 27.9 MB of additional disk space will be used. (Reading database ... 132615 files and directories currently installed.) Preparing to unpack .../linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb ... Unpacking linux-headers-6.3.0-7-generic (6.3.0-7.7) over (6.3.0-7.7) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb (--unpack): error creating symbolic link './lib/modules/6.3.0-7-generic/build': Read-only file system dpkg: error while cleaning up: unable to remove newly-extracted version of '/lib/modules/6.3.0-7-generic/build': Read-only file system Errors were encountered while processing: /var/cache/apt/archives/linux-headers-6.3.0-7-generic_6.3.0-7.7_amd64.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2034688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042850] Re: Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52 BMC
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042850 Title: Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52 BMC Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2042423 Subject: [mantic:linux] drm/ast: Add BMC virtual connector SRU Justification: [Impact] On systems with Aspeed 2600 revision 52 GPUs, the display fails to progress to the login prompt. With the commit (added in 6.5.0-6.6) commit: 916ae609a033cbb55661905d310ba2358b7621ea Author: Jocelyn Falempe Date:Thu Jul 13 15:41:31 2023 +0200 Subject: drm/ast: report connection status on Display Port. the Aspeed 2600 rev 52 GPUs have issues. They need the commit: This change was dependant on the upstream change commit e329cb53b45da475966c4b2e49f6a4a430f307fa Author: Jocelyn Falempe Date: Thu Jul 13 15:41:30 2023 +0200 Subject: drm/ast: Add BMC virtual connector https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e329cb53b45da475966c4b2e49f6a4a430f307fa in order to have the display work correctly on the rev52 GPUs. [Fix] With cherry-picking this change, the functionality of BMCs using Aspeed 2600 rev52 GPUs work as expected, as they did prior to the regression in 6.5.0-6.6. [Test Plan] I have tested this on multiple versions of Aspeed 2600 GPU enabled BMCs, and the revision 52 systems that required the nomodeset option to boot to the prompt, now boot fine and display the login prompt, and there is no regression on the other systems. I have tested this on different Aspeed GPUs, and have not seen any regressions, or unexpected behaviour. [Where problems could occur] As this fixes a regression of functionality for the mantic kernel's Aspeed GPU driver on a very specific version of some BMCs to the state it was was in the mantic 6.5.0-5.5 kernel, I think there is little room for regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029281] Re: Soundwire support for Dell SKU0C87 devices
This bug was fixed in the package firmware-sof - 2.2.6-1ubuntu2
---
firmware-sof (2.2.6-1ubuntu2) noble; urgency=medium
* Soundwire support for Dell SKU0C87 devices. LP: #2029281
- Add sof-v2.7 for Intel Meteor Lake hardware.
- Add more sof-v2.7.1 Intel MTL binaries
-- You-Sheng Yang Thu, 02 Nov 2023
12:18:57 +0800
** Changed in: firmware-sof (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2029281
Title:
Soundwire support for Dell SKU0C87 devices
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Triaged
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Triaged
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2029281
== firmware-sof ==
[Impact]
Missing soundwire firmware support for Intel MTL deivces.
[Fix]
Depends on sof-bin v2.7.1 release from
https://github.com/thesofproject/sof-bin/tree/v2023.09.1. Two commits
specifically:
*
https://github.com/thesofproject/sof-bin/commit/ad8dfcc182d3e0a5ce06a7fe9ed7717a04cad06b
("Add sof-v2.7 for Intel Meteor Lake hardware")
*
https://github.com/thesofproject/sof-bin/commit/5f010669084d64df29d77a436b6ffa0095565668
("Add more sof-v2.7.1 Intel MTL binaries")
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so oem-6.5/jammy is the target
series, and Mantic for best effort MTL support. Noble is also
nominated of course.
== linux ==
[Impact]
Missing soundwire support for Dell SKU0C87 deivces.
[Fix]
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
[Test Case]
Test audio functions on Tributo MTL platforms.
[Where problems could occur]
New devices, may need further polishments.
[Other Info]
This is for Intel MTL based platforms, so only OEM-6.5, Mantic, and
Unstable are nominated for fix.
== original bug description ==
kernel: sof-audio-pci-intel-mtl :00:1f.3: hda codecs found, mask 4
kernel: sof-audio-pci-intel-mtl :00:1f.3: Direct firmware load for
intel/sof-ipc4/mtl/sof-mtl.ri failed with error -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof firmware file is
missing, you might need to
kernel: sof-audio-pci-intel-mtl :00:1f.3: download it from
https://github.com/thesofproject/sof-bin/
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: failed to load DSP
firmware -2
kernel: sof-audio-pci-intel-mtl :00:1f.3: error: sof_probe_work failed
err: -2
kernel: kauditd_printk_skb: 33 callbacks suppressed
Required fixes:
* bin: https://github.com/thesofproject/sof/pull/7911
* kernel: https://github.com/thesofproject/linux/pull/4468
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2029281/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043449] [NEW] package zfs-dkms 2.1.5-1ubuntu6~22.04.1 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10
Public bug reported: hedgemonkey@orangemonkey:~$ sudo apt-get install zfs-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: debhelper Recommended packages: zfs-zed zfsutils-linux The following packages will be REMOVED: zfsutils-linux The following NEW packages will be installed: zfs-dkms 0 upgraded, 1 newly installed, 1 to remove and 3 not upgraded. Need to get 2,345 kB of archives. After this operation, 16.5 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 zfs-dkms all 2.1.5-1ubuntu6~22.04.1 [2,345 kB] Fetched 2,345 kB in 0s (21.2 MB/s) Preconfiguring packages ... (Reading database ... 200773 files and directories currently installed.) Removing zfsutils-linux (2.1.6-0york1~22.04) ... Selecting previously unselected package zfs-dkms. (Reading database ... 200500 files and directories currently installed.) Preparing to unpack .../zfs-dkms_2.1.5-1ubuntu6~22.04.1_all.deb ... Unpacking zfs-dkms (2.1.5-1ubuntu6~22.04.1) ... Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.1) ... Loading new zfs-2.1.5 DKMS files... Building for 5.10.160-rockchip Building initial module for 5.10.160-rockchip configure: error: *** None of the expected "file_fallocate" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.5-1ubuntu6~22.04.1 *** Compatible Kernels: 3.10 - 5.19 ERROR (dkms apport): kernel package linux-headers-5.10.160-rockchip is not supported Error! Bad return status for module build on kernel: 5.10.160-rockchip (aarch64) Consult /var/lib/dkms/zfs/2.1.5/build/make.log for more information. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 10 Processing triggers for man-db (2.10.2-1) ... Processing triggers for initramfs-tools (0.140ubuntu13.4) ... update-initramfs: Generating /boot/initrd.img-5.10.160-rockchip flash-kernel: installing version 5.10.160-rockchip Errors were encountered while processing: zfs-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.1 Uname: Linux 5.10.160-rockchip aarch64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: zfsutils-linux:arm64: Remove zfs-dkms:arm64: Install NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue Nov 14 08:39:28 2023 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: zfs-linux Title: package zfs-dkms 2.1.5-1ubuntu6~22.04.1 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 jammy need-duplicate-check third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2043449 Title: package zfs-dkms 2.1.5-1ubuntu6~22.04.1 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 Status in zfs-linux package in Ubuntu: New Bug description: hedgemonkey@orangemonkey:~$ sudo apt-get install zfs-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: debhelper Recommended packages: zfs-zed zfsutils-linux The following packages will be REMOVED: zfsutils-linux The following NEW packages will be installed: zfs-dkms 0 upgraded, 1 newly installed, 1 to remove and 3 not upgraded. Need to get 2,345 kB of archives. After this operation, 16.5 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 zfs-dkms all 2.1.5-1ubuntu6~22.04.1 [2,345 kB] Fetched 2,345 kB in 0s (21.2 MB/s) Preconfiguring packages ... (Reading database ... 200773 files and directories currently installed.) Removing zfsutils-linux (2.1.6-0york1~22.04) ... Selecting previously unselected package zfs-dkms. (Reading database ... 200500 files and directories currently installed.) Preparing to unpack .../zfs-dkms_2.1.5-1ubuntu6~22.04.1_all.deb ... Unpacking zfs-dkms (2.1.5-1ubuntu6~22.04.1) ... Setting
[Kernel-packages] [Bug 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10
Can you post the full log from a failure?
$ sudo journalctl -k -b 0 (use -1, -2, ... for earlier boots).
'failed with error -2' means the firmware file is not found, so I'm
puzzled...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2040106
Title:
Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and
bluetooth did not work anymore.
Looking at the dmesg output I saw this:
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
..
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
no suitable firmware found!
minimum version required: iwlwifi-QuZ-a0-hr-b0-39
minimum version required: iwlwifi-QuZ-a0-hr-b0-59
These files did seem to exist in /lib/firmware.
I did sudo apt install linux-firmware/mantic --reinstall
Which did not fix it.
I manually overwrote the iwlwifi... files with the corresponding files from
linux-firmware-20230804.tar.gz and this did fix the issue.
I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.
So my best guess is that something is wrong in the latest firmware
package.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
apt-cache policy linux-firmware
linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
*** 20230919.git3672ccab-0ubuntu2.1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
Uname: Linux 5.10.0-1053-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: joep 2545 F wireplumber
/dev/snd/controlC0: joep 2545 F wireplumber
/dev/snd/seq:joep 2537 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 15:19:18 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85
InstallationDate: Installed on 2021-10-16 (736 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1053-oem N/A
linux-backports-modules-5.10.0-1053-oem N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
dmi.bios.date: 07/13/2023
dmi.bios.release: 1.22
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.22.0
dmi.board.name: 0NG7N9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5560
dmi.product.sku: 0A62
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2040106/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
