[Kernel-packages] [Bug 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
About the enable proposed ppa: It was the actual official proposed pocket for mantic and jammy. sth like this: deb [arch=amd64] http://archive.ubuntu.com/ubuntu/ jammy-proposed main restricted About the two additional steps: I did run them in mantic and jammy in my verification (#3 and #4). Thx. -- 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/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2055283 [Impact] We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image and booting up, the bluetooth couldn't work at all. Checking the dmesg, the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, but there is no this firmware in the linux-firmware of Jammy, and I also checked the Mantic and Noble, Mandic doesn't have this firmware too, Noble already has the firmware since the upstream linux-firmware integrated the intel/ibt-0180-4150.sfi last year. [Fix] Backport 4 commits from upstream linux-firmware, these 4 commits are all on intel/ibt-0180-4150.sfi|ddc [Test Case] Put the firmware into the /lib/firmware/intel/, reboot the machine, check dmesg, the bluetooth driver loads the firmware successfully, run hciconfig, the hci0 shows up. run checkbox testcase, it could pass. [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] [Where problems could occur] Probably could make the Intel AX201 BT adapter couldn't work, but the possibility is very low, we tested the firmware on different lenovo machines with the BT adapter AX201, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2063096] Re: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle
** Description changed: - This is for tracking purpose + [Impact] + + On a Dell laptop, When we do suspend/resume test, we found the + realtek wifi couldn't work after resume, from the dmesg, we found + the error log as below: + Log: + 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: fw security fail + 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: download firmware fail + 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 0x1E0 = 0x62 + 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 0x83F2 = 0x8 + + [Fix] + + Backport a commit from mainline kernel (linux-next), this will retry firmware + loading for 5 times. + + [Test Case] + + run suspend/resume test case for over 100 times, the wifi still + works. + + [Where problems could occur] + + This commit comes from mailine kernel, and it doesn't change existing + driver except loading firmware a couple of more times if there is an error. + In theory this will not introduce regression. ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid -- 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/2063096 Title: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] On a Dell laptop, When we do suspend/resume test, we found the realtek wifi couldn't work after resume, from the dmesg, we found the error log as below: Log: 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: fw security fail 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: download firmware fail 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 0x1E0 = 0x62 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 0x83F2 = 0x8 [Fix] Backport a commit from mainline kernel (linux-next), this will retry firmware loading for 5 times. [Test Case] run suspend/resume test case for over 100 times, the wifi still works. [Where problems could occur] This commit comes from mailine kernel, and it doesn't change existing driver except loading firmware a couple of more times if there is an error. In theory this will not introduce regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063096/+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 2063096] [NEW] RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle
Public bug reported: This is for tracking purpose ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2056141 somerville ** Package changed: linux-firmware (Ubuntu) => linux-oem-6.5 (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Hui Wang (hui.wang) ** Tags added: oem-priority originate-from-2056141 somerville -- 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/2063096 Title: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle Status in HWE Next: New Status in linux 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.5 source package in Jammy: New Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: This is for tracking purpose To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063096/+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 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
** Description changed: + This is SRU template for linux kernel: + + [Impact] + + On a Dell laptop, let it connect to a WiFi router, connect a BT + device, then disconnect it, connect the bt device again, we expect + the device could be connected successfully, but it couldn't and + the BT firmeware crashed. + + [Fix] + + Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel + patches, here we send the MR for 2 kernel patches. The firmware PR was + already sent out. And one of the patches is from linux-next, the other is + from rtw.git and is going to be merged to linux-next soon. + + [Test Case] + + + With the upgraded firmware + kernel with the 2 kernel patches, bt + firmware will not crash anymore and bt could connect / disconnect + many many bt devices. + + [Where problems could occur] + + This MR comes from upstream commits, it has low possibility to + introduce regression. If the bt or wifi on this laptop couldn't + work as well as before, it is possible that this MR introduces + regression. According to our test, the wifi and bt could work well + with upgraded firmware. + + === This SRU template is for linux-firmware: BugLink: https://bugs.launchpad.net/bugs/2060904 [Impact] On a Dell laptop, let it connect to a WiFi router, connect a BT device, then disconnect it, connect the bt device again, we expect the device could be connected successfully, but it couldn't and the BT firmeware crashed. [Fix] Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel patches, here we send the MR for firmware first. And it is backward compatible, the upgraded firmware could work with kernel without those 2 patches as well as before. [Test Case] With the upgraded firmware + kernel without the 2 kernel patches, the wifi and bt could work as well / bad as before. With the upgraded firmware + kernel with the 2 kernel patches, bt firmware will not crash anymore and bt could connect / disconnect many many bt devices. [Where problems could occur] This MR comes from upstream commit, it has low possibility to introduce regression. If the bt or wifi on this laptop couldn't work as well as before, it is possible that this MR introduces regression. According to our test, the wifi and bt could work well with upgraded firmware. -- 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/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: New Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Mantic: New Status in linux-firmware source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux-oem-6.8 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: This is SRU template for linux kernel: [Impact] On a Dell laptop, let it connect to a WiFi router, connect a BT device, then disconnect it, connect the bt device again, we expect the device could be connected successfully, but it couldn't and the BT firmeware crashed. [Fix] Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel patches, here we send the MR for 2 kernel patches. The firmware PR was already sent out. And one of the patches is from linux-next, the other is from rtw.git and is going to be merged to linux-next soon. [Test Case] With the upgraded firmware + kernel with the 2 kernel patches, bt firmware will not crash anymore and bt could connect / disconnect many many bt devices. [Where problems could occur] This MR comes from upstream commits, it has low possibility to introduce regression. If the bt or wifi on this laptop couldn't work as well as before, it is possible that this MR introduces regression. According to our test, the wifi and bt could work well with upgraded firmware. === This SRU template is for linux-firmware: BugLink: https://bugs.launchpad.net/bugs/2060904 [Impact] On a Dell laptop, let it connect to a WiFi router, connect a BT device, then disconnect it, connect the bt device again, we
[Kernel-packages] [Bug 2062412] Re: No input through internal microphone (Ryzen 6000)
*** This bug is a duplicate of bug 2061254 *** https://bugs.launchpad.net/bugs/2061254 This issue was already reported in #2061254. ** This bug has been marked a duplicate of bug 2061254 No mic detected - Ubuntu 24.04 Beta -- 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/2062412 Title: No input through internal microphone (Ryzen 6000) Status in linux package in Ubuntu: New Bug description: The microphone in a Thinkpad P14S (AMD) Gen 4 stopped working after updating from 23.10 to 24.04 Beta with kernel 6.8.0-22-generic. This is a known problem and a patch may be included in kernel 6.8.3. Is it possible to backport this patch? Or is the plan to wait for a kernel update? It would be good use the microphone in 24.04. The symptoms are exactly as described in https://bbs.archlinux.org/viewtopic.php?pid=2162297#p2162297 Reportedly the patch is included in https://github.com/zen-kernel/zen-kernel/blob/6.7/main/sound/soc/amd/yc/acp6x-mach.c#L59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+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 2046315] Re: panel flickering after the i915.psr2 is enabled
** Description changed: + SRU verificaton for Noble and oem-6.8-noble: + + [Impact] + In Dell oem project, we found the graphic is flickering on some + machines, finally we narrowed down the issue on (some specific panels + + i915.psr2 enabled), and the issue was reported to Intel, Intel fixed + the issue in the most recent mainline kernel. Here backporting the + patches to Noble kernel. + + It is hard to backport the patches to mantic and oem-6.5, so we wrote + a workaround patch to disable the psr2 for those pannels in the oem-6.5. + + https://gitlab.freedesktop.org/drm/intel/-/issues/9739 + + [Fix] + cherry-pick 8 patches from mainline kernel + + [Test] + I applied the patches to Noble kernel and built a testing kernel, and + Dell validated the testing kernel on those machines, the graphic + didn't flicker anymore. + + I installed the testing kernel on some machines with Intel 13th, 12th + 11th and 10th gen cpu, the grahic worked well too. + + [Where problems could occur] + This patchset changes the fast wake settings for some gpu, it is + possible to make the graphic flicker, but this possibility is very + low, since the patchset comes from mainline kernel and we validated + the patchset on different gens of Intel cpus. + + === + BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. -- 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/2046315 Title: panel flickering after the i915.psr2 is enabled Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: SRU verificaton for Noble and oem-6.8-noble: [Impact] In Dell oem project, we found the graphic is flickering on some machines, finally we narrowed down the issue on (some specific panels + i915.psr2 enabled), and the issue was reported to Intel, Intel fixed the issue in the most recent mainline kernel. Here backporting the patches to Noble kernel. It is hard to backport the patches to mantic and oem-6.5, so we wrote a workaround patch to disable the psr2 for those pannels in the oem-6.5. https://gitlab.freedesktop.org/drm/intel/-/issues/9739 [Fix] cherry-pick 8 patches from mainline kernel [Test] I applied the patches to Noble kernel and built a testing kernel, and Dell validated the testing kernel on those machines, the graphic didn't flicker anymore. I installed the testing kernel on some machines with Intel 13th, 12th 11th and 10th gen cpu, the grahic worked well too. [Where problems could occur] This patchset changes the fast wake settings for some gpu, it is possible to make the graphic flicker, but this possibility is very low, since the patchset comes from mainline kernel and we validated the patchset on different gens of Intel cpus. === BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug
[Kernel-packages] [Bug 2046315] Re: panel flickering after the i915.psr2 is enabled
** Summary changed: - panel flickering after enabling the psr2 + panel flickering after the i915.psr2 is enabled -- 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/2046315 Title: panel flickering after the i915.psr2 is enabled Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2046315] Re: panel flickering after enabling the psr2
** Summary changed: - oem-6.5: disable psr2 for some panels according to edid + panel flickering after enabling the psr2 -- 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/2046315 Title: panel flickering after enabling the psr2 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2046681] Re: jammy-oem-6.5: one more panel needs to disable psr2
For oem-6.8 and noble kernels, the fix will be merged by https://bugs.launchpad.net/ubuntu/jammy/+source/linux- oem-6.8/+bug/2046315 -- 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/2046681 Title: jammy-oem-6.5: one more panel needs to disable psr2 Status in HWE Next: New Status in linux package in Ubuntu: Triaged 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 Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.8 (Ubuntu Jammy) Status: New => Invalid -- 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/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2061254] Re: No mic detected - Ubuntu 24.04 Beta
I checked the latest ubuntu noble kernel, the fix is already merged to this kernel through this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060531 Please wait for the upcoming release version of noble kernel. commit 6a9156867a5ce4ded2967ca46b0a8d755d9a1ee7 Author: Jiawei Wang Date: Wed Mar 13 09:58:53 2024 +0800 ASoC: amd: yc: Revert "add new YC platform variant (0x63) support" BugLink: https://bugs.launchpad.net/bugs/2060531 commit 37bee1855d0e3b6dbeb8de71895f6f68cad137be upstream. This reverts commit 316a784839b21b122e1761cdca54677bb19a47fa, that enabled Yellow Carp (YC) driver for PCI revision id 0x63. Mukunda Vijendar [1] points out that revision 0x63 is Pink Sardine platform, not Yellow Carp. The YC driver should not be enabled for this platform. This patch prevents the YC driver from being incorrectly enabled. Link: https://lore.kernel.org/linux-sound/023092e1-689c-4b00-b93f-4092c3724...@amd.com/ [1] Signed-off-by: Jiawei Wang Link: https://msgid.link/r/20240313015853.3573242-3...@jwang.link Signed-off-by: Mark Brown Signed-off-by: Greg Kroah-Hartman Signed-off-by: Paolo Pisati ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Noble) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Changed in: linux (Ubuntu Noble) 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/2061254 Title: No mic detected - Ubuntu 24.04 Beta Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: On Ubuntu 23.10, my laptop microphone is detected/working fine, but can't be detected on Ubuntu 24.04. Tried direct direct install of 24.04 and upgrade fromo 23.10, same problem ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:burnarz 43101 F pipewire /dev/snd/controlC0: burnarz 43106 F wireplumber /dev/snd/controlC1: burnarz 43106 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 01:04:10 2024 InstallationDate: Installed on 2024-04-13 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240412) MachineType: LENOVO 83AR PackageArchitecture: all ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2024 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: MDCN33WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Pro 5 16APH8 dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrMDCN33WW:bd01/24/2024:br1.33:efr1.33:svnLENOVO:pn83AR:pvrIdeaPadPro516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrIdeaPadPro516APH8:skuLENOVO_MT_83AR_BU_idea_FM_IdeaPadPro516APH8: dmi.product.family: IdeaPad Pro 5 16APH8 dmi.product.name: 83AR dmi.product.sku: LENOVO_MT_83AR_BU_idea_FM_IdeaPad Pro 5 16APH8 dmi.product.version: IdeaPad Pro 5 16APH8 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061254/+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 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Noble) Status: New => In Progress -- 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/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: New Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Mantic: New Status in linux-firmware source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux-oem-6.8 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: This SRU template is for linux-firmware: BugLink: https://bugs.launchpad.net/bugs/2060904 [Impact] On a Dell laptop, let it connect to a WiFi router, connect a BT device, then disconnect it, connect the bt device again, we expect the device could be connected successfully, but it couldn't and the BT firmeware crashed. [Fix] Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel patches, here we send the MR for firmware first. And it is backward compatible, the upgraded firmware could work with kernel without those 2 patches as well as before. [Test Case] With the upgraded firmware + kernel without the 2 kernel patches, the wifi and bt could work as well / bad as before. With the upgraded firmware + kernel with the 2 kernel patches, bt firmware will not crash anymore and bt could connect / disconnect many many bt devices. [Where problems could occur] This MR comes from upstream commit, it has low possibility to introduce regression. If the bt or wifi on this laptop couldn't work as well as before, it is possible that this MR introduces regression. According to our test, the wifi and bt could work well with upgraded firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+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 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
** Description changed: - This bug is for tracking purpose + This SRU template is for linux-firmware: + + BugLink: https://bugs.launchpad.net/bugs/2060904 + + [Impact] + + On a Dell laptop, let it connect to a WiFi router, connect a BT + device, then disconnect it, connect the bt device again, we expect + the device could be connected successfully, but it couldn't and + the BT firmeware crashed. + + [Fix] + + Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel + patches, here we send the MR for firmware first. And it is backward + compatible, the upgraded firmware could work with kernel without + those 2 patches as well as before. + + [Test Case] + + With the upgraded firmware + kernel without the 2 kernel patches, + the wifi and bt could work as well / bad as before. + + With the upgraded firmware + kernel with the 2 kernel patches, bt + firmware will not crash anymore and bt could connect / disconnect + many many bt devices. + + [Where problems could occur] + + This MR comes from upstream commit, it has low possibility to + introduce regression. If the bt or wifi on this laptop couldn't + work as well as before, it is possible that this MR introduces + regression. According to our test, the wifi and bt could work well + with upgraded firmware. -- 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/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-firmware source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Mantic: New Status in linux-firmware source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux-oem-6.8 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: This SRU template is for linux-firmware: BugLink: https://bugs.launchpad.net/bugs/2060904 [Impact] On a Dell laptop, let it connect to a WiFi router, connect a BT device, then disconnect it, connect the bt device again, we expect the device could be connected successfully, but it couldn't and the BT firmeware crashed. [Fix] Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel patches, here we send the MR for firmware first. And it is backward compatible, the upgraded firmware could work with kernel without those 2 patches as well as before. [Test Case] With the upgraded firmware + kernel without the 2 kernel patches, the wifi and bt could work as well / bad as before. With the upgraded firmware + kernel with the 2 kernel patches, bt firmware will not crash anymore and bt could connect / disconnect many many bt devices. [Where problems could occur] This MR comes from upstream commit, it has low possibility to introduce regression. If the bt or wifi on this laptop couldn't work as well as before, it is possible that this MR introduces regression. According to our test, the wifi and bt could work well with upgraded firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+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 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
Installed the linux/6.5.0-33.33 kernel in -proposed, and the issue is fixed by the kernel. ** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- 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/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] In an oem project, we found the max playback volume of the headphone is too high on 2 LG machines, it could bring harm to listeners. As requested by OEM customer, we need to decrease the max volume. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booting with the patched kernel, plug the headphone, set the playback volue to max, run: amixer -c1 contents | grep -n2 "Headphone Playback Volume" The value is 77,77 instead of 87,87 like below: numid=1,iface=MIXER,name='Headphone Playback Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=87,step=0 : values=77,77 [Where problems could occur] This patch changes the amplifier's default value, probably will make the audio malfunction, but this change is specific to those 2 LG machines (by SSID), will not bring regression to other machines. For those 2 machines, we already tested patch, the audio worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+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 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
Installed the linux/5.15.0-104.114 kernel in -proposed, and the issue is fixed by this kernel. ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- 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/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] In an oem project, we found the max playback volume of the headphone is too high on 2 LG machines, it could bring harm to listeners. As requested by OEM customer, we need to decrease the max volume. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booting with the patched kernel, plug the headphone, set the playback volue to max, run: amixer -c1 contents | grep -n2 "Headphone Playback Volume" The value is 77,77 instead of 87,87 like below: numid=1,iface=MIXER,name='Headphone Playback Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=87,step=0 : values=77,77 [Where problems could occur] This patch changes the amplifier's default value, probably will make the audio malfunction, but this change is specific to those 2 LG machines (by SSID), will not bring regression to other machines. For those 2 machines, we already tested patch, the audio worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+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 2060904] [NEW] Fix the RTL8852CE BT FW Crash based on SER false alarm
Public bug reported: This bug is for tracking purpose ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.8 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.8 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Noble) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Tags: oem-priority originate-from-2059397 somerville ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Noble) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-6.8 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.8 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.8 (Ubuntu Noble) Assignee: (unassigned) => Hui Wang (hui.wang) ** Tags added: oem-priority originate-from-2059397 somerville -- 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/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-firmware source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Mantic: New Status in linux-firmware source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux-oem-6.8 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: New Status in linux-oem-6.5 source pac
[Kernel-packages] [Bug 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
Verification for jammy: Install the ubuntu jammy on the machine in question, enable proposed ppa, run sudo apt-get update, run sudo apt install linux-firmware, the inux-firmware/20230919.git3672ccab-0ubuntu2.10 is installed. reboot the machine, check dmesg, there is no "loading firmware failure" log, connect a bt headset (PLT_BBTGO2), the bt headset could pair, play sound and capture sound. Verification done on jammy. ** Tags added: verification-done-jammy -- 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/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2055283 [Impact] We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image and booting up, the bluetooth couldn't work at all. Checking the dmesg, the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, but there is no this firmware in the linux-firmware of Jammy, and I also checked the Mantic and Noble, Mandic doesn't have this firmware too, Noble already has the firmware since the upstream linux-firmware integrated the intel/ibt-0180-4150.sfi last year. [Fix] Backport 4 commits from upstream linux-firmware, these 4 commits are all on intel/ibt-0180-4150.sfi|ddc [Test Case] Put the firmware into the /lib/firmware/intel/, reboot the machine, check dmesg, the bluetooth driver loads the firmware successfully, run hciconfig, the hci0 shows up. run checkbox testcase, it could pass. [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] [Where problems could occur] Probably could make the Intel AX201 BT adapter couldn't work, but the possibility is very low, we tested the firmware on different lenovo machines with the BT adapter AX201, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
Verification for mantic: Install the ubuntu mantic on the machine in question, enable proposed ppa, run sudo apt-get update, run sudo apt install linux-firmware, the linux-firmware/20230919.git3672ccab-0ubuntu2.10 is installed. reboot the machine, check dmesg, there is no "loading firmware failure" log, connect a bt headset (PLT_BBTGO2), the bt headset could pair, play sound and capture sound. Verification done on mantic. ** Tags added: verification-done-mantic -- 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/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2055283 [Impact] We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image and booting up, the bluetooth couldn't work at all. Checking the dmesg, the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, but there is no this firmware in the linux-firmware of Jammy, and I also checked the Mantic and Noble, Mandic doesn't have this firmware too, Noble already has the firmware since the upstream linux-firmware integrated the intel/ibt-0180-4150.sfi last year. [Fix] Backport 4 commits from upstream linux-firmware, these 4 commits are all on intel/ibt-0180-4150.sfi|ddc [Test Case] Put the firmware into the /lib/firmware/intel/, reboot the machine, check dmesg, the bluetooth driver loads the firmware successfully, run hciconfig, the hci0 shows up. run checkbox testcase, it could pass. [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] [Where problems could occur] Probably could make the Intel AX201 BT adapter couldn't work, but the possibility is very low, we tested the firmware on different lenovo machines with the BT adapter AX201, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
** Description changed: - This is for tracking purpose. + [Impact] + In an oem project, we found the max playback volume of the headphone + is too high on 2 LG machines, it could bring harm to listeners. As + requested by OEM customer, we need to decrease the max volume. + + + [Fix] + Cherry-pick a mainline kernel patch, this could fix this issue. + + [Test] + Booting with the patched kernel, plug the headphone, set the playback + volue to max, run: + amixer -c1 contents | grep -n2 "Headphone Playback Volume" + + The value is 77,77 instead of 87,87 like below: + numid=1,iface=MIXER,name='Headphone Playback Volume' + ; type=INTEGER,access=rw---R--,values=2,min=0,max=87,step=0 + : values=77,77 + + + [Where problems could occur] + This patch changes the amplifier's default value, probably + will make the audio malfunction, but this change is specific + to those 2 LG machines (by SSID), will not bring regression + to other machines. For those 2 machines, we already tested patch, + the audio worked well. ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) 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/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: [Impact] In an oem project, we found the max playback volume of the headphone is too high on 2 LG machines, it could bring harm to listeners. As requested by OEM customer, we need to decrease the max volume. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booting with the patched kernel, plug the headphone, set the playback volue to max, run: amixer -c1 contents | grep -n2 "Headphone Playback Volume" The value is 77,77 instead of 87,87 like below: numid=1,iface=MIXER,name='Headphone Playback Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=87,step=0 : values=77,77 [Where problems could occur] This patch changes the amplifier's default value, probably will make the audio malfunction, but this change is specific to those 2 LG machines (by SSID), will not bring regression to other machines. For those 2 machines, we already tested patch, the audio worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+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 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
** Summary changed: - alsa/realtek: adjust headphone max output valume on 2 LG machines + alsa/realtek: adjust max output valume for headphone on 2 LG machines -- 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/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: This is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+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 2058573] [NEW] alsa/realtek: adjust headphone max output valume on 2 LG machines
Public bug reported: This is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: jinju oem-priority originate-from-2055127 ** Package changed: linux-oem-6.5 (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Tags added: jinju oem-priority originate-from-2055127 -- 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/2058573 Title: alsa/realtek: adjust headphone max output valume on 2 LG machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: This is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
** Tags removed: verification-needed-jammy-linux-ibm-gt-fips ** Tags added: verification-done-jammy-linux-ibm-gt-fips -- 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
** Tags removed: verification-needed-jammy-linux-ibm-gt-fips ** Tags added: verification-done-jammy-linux-ibm-gt-fips -- 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/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
** Description changed: - This is for tracking purpose + BugLink: https://bugs.launchpad.net/bugs/2055283 + + [Impact] + + We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image + and booting up, the bluetooth couldn't work at all. Checking the dmesg, + the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, + but there is no this firmware in the linux-firmware of Jammy, and I + also checked the Mantic and Noble, Mandic doesn't have this firmware too, + Noble already has the firmware since the upstream linux-firmware integrated + the intel/ibt-0180-4150.sfi last year. + + + [Fix] + + Backport 4 commits from upstream linux-firmware, these 4 commits are all + on intel/ibt-0180-4150.sfi|ddc + + + [Test Case] + + Put the firmware into the /lib/firmware/intel/, reboot the machine, + check dmesg, the bluetooth driver loads the firmware successfully, + + run hciconfig, the hci0 shows up. + + run checkbox testcase, it could pass. + [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] + + + [Where problems could occur] + + Probably could make the Intel AX201 BT adapter couldn't work, but the possibility + is very low, we tested the firmware on different lenovo machines with the BT adapter + AX201, all worked well. -- 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/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2055283 [Impact] We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image and booting up, the bluetooth couldn't work at all. Checking the dmesg, the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, but there is no this firmware in the linux-firmware of Jammy, and I also checked the Mantic and Noble, Mandic doesn't have this firmware too, Noble already has the firmware since the upstream linux-firmware integrated the intel/ibt-0180-4150.sfi last year. [Fix] Backport 4 commits from upstream linux-firmware, these 4 commits are all on intel/ibt-0180-4150.sfi|ddc [Test Case] Put the firmware into the /lib/firmware/intel/, reboot the machine, check dmesg, the bluetooth driver loads the firmware successfully, run hciconfig, the hci0 shows up. run checkbox testcase, it could pass. [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] [Where problems could occur] Probably could make the Intel AX201 BT adapter couldn't work, but the possibility is very low, we tested the firmware on different lenovo machines with the BT adapter AX201, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2055283] [NEW] Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
Public bug reported: This is for tracking purpose ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Jammy) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux-firmware (Ubuntu Mantic) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: oem-priority originate-from-2054554 sutton ** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Mantic) Status: New => Fix Committed ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-firmware (Ubuntu Mantic) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-firmware (Ubuntu Mantic) Status: Fix Committed => In Progress ** Tags added: oem-priority originate-from-2054554 sutton -- 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/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Bug description: This is for tracking purpose To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- 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/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: Fix Committed 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: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
booting with 6.5.0-25.25, and run L2CAP test case, all testcase in PTS could pass. Verification done for Mantic. ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux ** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
booting with 5.15.0-100.110, and run L2CAP test case, all testcase in PTS could pass. Verification done for 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
** Tags removed: verification-needed-jammy-linux-oem-6.1 ** Tags added: verification-done-jammy-linux-oem-6.1 -- 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/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2045517] Re: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S
Installed the proposed kernel (1014) to some lenovo/dell/hp machines, the audio worked as well as before. verification done. ** 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/2045517 Title: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S 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 Committed Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] To support HP stella's latest machine, we need to backport some new PCIIDs and corresponding drivers to our OEM kernel, the requirement is here: https://docs.google.com/spreadsheets/d/1_usKzZDxjtqlUzdOUPXvzNzSzhjRqcaV/edit#gid=1748766508 This pull-request is to unitfy and add some audio controller's ID, but to do so, need to apply some depending patches otherwise it will have conflict to introduce the new ID and new driver to OEM kernel. unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S [Fix] This add the audio driver for machines with Intel Arrowlake. [Test case] Boot the patched kernel on a Arrowlake machine, the audio function could work. Boot the patches kernel on non-Arrowlake machines, the audio function could work as well as before. [Where problems could occur] Could lose some pciids and make the auido driver not work on those machines, and could not play sound or record sound. But this possibility is very low, I checked each patch carefully and I verify the patcheset on some lenovo an dell machines. From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based on it, added new PCIID and audio support for arrowlake-s, need to backport them to oem-6.5, this is a preparation for supporting HP latest laptops: unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045517/+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 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
** Package changed: linux-oem-6.1 (Ubuntu) => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in HWE Next: New Status in pulseaudio package in Ubuntu: New Status in pulseaudio source package in Jammy: New Status in pulseaudio source package in Mantic: New Status in pulseaudio source package in Noble: New Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2051895] [NEW] Lenovo XT99 BT headset can't work in HFP profile
Public bug reported: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile Status in linux-oem-6.1 package in Ubuntu: New Bug description: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051895/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
Lunar kernel reaches EOL, so set "won't fix" for L kernel. ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Won't Fix -- 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/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium -- 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/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
** Description changed: - This bug is for tracking purpose. + BugLink: https://bugs.launchpad.net/bugs/2051050 + + Currently this patch is in the linux-next, and will be in the + mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble + kernel, Noble kernel will have this patch automatically. + + [Impact] + In the gnome audio setting, if we adjust balancing setting, it doesn't + work at all on a Dell machine with cirrus codec, that is because with + the current driver, the exported amixer controls can't be handled by + pulseaudio. + + [Fix] + Cherry-pick a mainline kernel patch, this could fix this issue. + + [Test] + Booted with the patched kernel, move the bar to the left or right to + adjust the balance, we could hear the sound from left channel or right + channel accordingly. + + [Where problems could occur] + This change will not create "Master Volume" amixer controls, probably + will make the audio control malfunction, that is we couldn't control + playback or capture volume correctly, but this regression possibility + is very low, we already tested the patch on the machines with cirrus + codec, they all worked well as before. ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) -- 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/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: New Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Lunar: New Status in linux source package in Mantic: New Status in linux source package in Noble: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2051050 Currently this patch is in the linux-next, and will be in the mainline kernel v6.8-rc2, there is no need to SRU this patch to Noble kernel, Noble kernel will have this patch automatically. [Impact] In the gnome audio setting, if we adjust balancing setting, it doesn't work at all on a Dell machine with cirrus codec, that is because with the current driver, the exported amixer controls can't be handled by pulseaudio. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booted with the patched kernel, move the bar to the left or right to adjust the balance, we could hear the sound from left channel or right channel accordingly. [Where problems could occur] This change will not create "Master Volume" amixer controls, probably will make the audio control malfunction, that is we couldn't control playback or capture volume correctly, but this regression possibility is very low, we already tested the patch on the machines with cirrus codec, they all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2051050] Re: Audio balancing setting doesn't work with the cirrus codec
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => Fix Committed ** No longer affects: linux-oem-6.1 (Ubuntu Mantic) ** No longer affects: linux-oem-6.1 (Ubuntu Lunar) ** No longer affects: linux-oem-6.1 (Ubuntu Noble) ** No longer affects: linux-oem-6.5 (Ubuntu Lunar) ** No longer affects: linux-oem-6.5 (Ubuntu Mantic) ** No longer affects: linux-oem-6.5 (Ubuntu Noble) ** Tags added: oem-priority originate-from-2047895 somerville -- 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/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: New Status in linux source package in Noble: Fix Committed Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2051050] [NEW] Audio balancing setting doesn't work with the cirrus codec
Public bug reported: This bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Committed ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Fix Committed ** Tags: oem-priority originate-from-2047895 somerville ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2051050 Title: Audio balancing setting doesn't work with the cirrus codec Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed 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: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: New Status in linux source package in Noble: Fix Committed Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051050/+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 2045517] Re: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S
Yes. They are all in the v6.7 -- 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/2045517 Title: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S Status in linux package in Ubuntu: Incomplete 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: New Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] To support HP stella's latest machine, we need to backport some new PCIIDs and corresponding drivers to our OEM kernel, the requirement is here: https://docs.google.com/spreadsheets/d/1_usKzZDxjtqlUzdOUPXvzNzSzhjRqcaV/edit#gid=1748766508 This pull-request is to unitfy and add some audio controller's ID, but to do so, need to apply some depending patches otherwise it will have conflict to introduce the new ID and new driver to OEM kernel. unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S [Fix] This add the audio driver for machines with Intel Arrowlake. [Test case] Boot the patched kernel on a Arrowlake machine, the audio function could work. Boot the patches kernel on non-Arrowlake machines, the audio function could work as well as before. [Where problems could occur] Could lose some pciids and make the auido driver not work on those machines, and could not play sound or record sound. But this possibility is very low, I checked each patch carefully and I verify the patcheset on some lenovo an dell machines. From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based on it, added new PCIID and audio support for arrowlake-s, need to backport them to oem-6.5, this is a preparation for supporting HP latest laptops: unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045517/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
The review request is for Jammy kernel, I sent the review request on Jan 9, and already got 2 Acks. This patch will be handled in the cycle 2024.02.05, and will finish the SRU in the week of 04-Mar. -- 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
** Changed in: linux (Ubuntu Jammy) 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and my mobile phone, all worked as well as before. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. It has possibility to make some bt devices could not work with patched kernel, but this possibility is very low, I tested the patched kernel with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all worked as well as before. [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
** Description changed: + The patch is merged in mainline kernel v6.7-rc7, so Noble kernel + already have this fix. And this patch is CCed to sta...@vger.kernel.org, + M and L kernel will have this fix with the SRU update sooner or later. + For Jammy kernel, an OEM customer is waiting for this patch + to be merged to Jammy kernel and OEM kernel, here I submit the + review reqeust for Jammy only. + + [Impact] + An OEM customer want to do the bluetooth profile testing suite (PTS) + test, and they found if sending 2 commands and one of them is "unknown + comands", the bluetooth stack doesn't reply the ack as expected, this + broke the customer's PTS test. + + [Fix] + Cherry-pick a mainline kernel patch, this could fix this issue. + + [Test] + After applying the patch, test it with PTS: + + 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection +over PSM 0x1011, which is the default PSM for l2test, the testing tool for +L2CAP layer provided by bluez. + + 2. Set device as connectable: + $ sudo btmgmt connectable on + + 3. Run l2test on the device in preparation for testing: + $ sudo l2test -d + + 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate +L2CAP connection automatically. + + 5. Verify that the test verdict on the PTS is PASS. + + And I also tested the patched kernel with 2 bt headsets, 1 bt keyboard and + my mobile phone, all worked as well as before. + + [Where problems could occur] + This makes L2CAP implementation more conforming to the specification. + It has possibility to make some bt devices could not work with patched + kernel, but this possibility is very low, I tested the patched kernel + with 2 bt headsets, 1 bt keyboard and my Android mobile phone, all + worked as well as before. + + + [Impact] - In the qualification test the from the Bluetooth SIG i.e. the + In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: - 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection -over PSM 0x1011, which is the default PSM for l2test, the testing tool for -L2CAP layer provided by bluez. + 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection + over PSM 0x1011, which is the default PSM for l2test, the testing tool for + L2CAP layer provided by bluez. 2. Set device as connectable: - $ sudo btmgmt connectable on + $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: - $ sudo l2test -d + $ sudo l2test -d - 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate -L2CAP connection automatically. + 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate + L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. -- 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: New Status in linux source package in Noble: Fix Released Bug description: The patch is merged in mainline kernel v6.7-rc7, so Noble kernel already have this fix. And this patch is CCed to sta...@vger.kernel.org, M and L kernel will have this fix with the SRU update sooner or later. For Jammy kernel, an OEM customer is waiting for this patch to be merged to Jammy kernel and OEM kernel, here I submit the review reqeust for Jammy only. [Impact] An OEM customer want to do the bluetooth profile testing suite (PTS) test, and they found if sending 2 commands and one of them is "unknown comands", the bluetooth stack doesn't reply the ack as expected, this broke the customer's PTS test. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo
[Kernel-packages] [Bug 2047634] Re: Reject connection when malformed L2CAP signal packet is received
noble kernel will have this patch automatically since the version of noble kernel is v6.7 at least (Probably v6.8). ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu Jammy) 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Noble: New Bug description: [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2047634] Re: Reject connection when malformed L2CAP signal packet is received
The patch is merged to mainline kernel v6.7-rc7, and this patch is also CCed to sta...@vger.kernel.org, so in theory, this patch will be merged to ubuntu kernel (jammy & noble) automatically with the SRU update. ** Also affects: linux (Ubuntu Noble) 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Noble: New Bug description: [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+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 2046681] Re: jammy-oem-6.5: one more panel needs to disable psr2
Installed the proposed kernel on the machine in question, the graphic works well. verification done. ** 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/2046681 Title: jammy-oem-6.5: one more panel needs to disable psr2 Status in HWE Next: New Status in linux package in Ubuntu: Triaged 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 Committed Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Description changed: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking + This PR is just a workaround, the upstream bug is here: + https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 + + After the upstream fixe this bug with a real fix, I will revert the + workaround and backport the real fix to Noble and Jammy oem-kernel. + [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. - [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. ** Description changed: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 - After the upstream fixe this bug with a real fix, I will revert the + After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. -- 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/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Triaged Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Triaged Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2046681] Re: jammy-oem-6.5: one more panel needs to disable psr2
** Description changed: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly + + This PR is just a workaround, the upstream bug is here: + https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 + + After the upstream fix this bug with a real fix, I will revert the + workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. -- 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/2046681 Title: jammy-oem-6.5: one more panel needs to disable psr2 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+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 2046681] Re: jammy-oem-6.5: one more panel needs to disable psr2
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: High Assignee: Hui Wang (hui.wang) Status: Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: Invalid => Triaged ** Changed in: linux (Ubuntu Noble) Status: New => Triaged ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: Triaged => New ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High -- 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/2046681 Title: jammy-oem-6.5: one more panel needs to disable psr2 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Changed in: linux (Ubuntu Noble) Status: Invalid => Triaged ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: Invalid => Triaged ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High -- 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/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Triaged Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Triaged Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: High Assignee: Hui Wang (hui.wang) Status: Invalid -- 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/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux 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.5 source package in Jammy: In Progress Status in linux source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress -- 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/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux 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.5 source package in Jammy: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2046681] Re: jammy-oem-6.5: one more pannel needs to disable psr2
** Description changed: - tracking + BugLink: https://bugs.launchpad.net/bugs/2046681 + + [Impact] + The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly + + [Fix] + There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. + + [Test case] + + booting with the patched kernel, If the pannel's edid is in the qurik + list, the PSR2 will be disabled (checking + /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not + in the quirk list, the graphic driver will work as before. + + [Where problems could occur] + It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. -- 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/2046681 Title: jammy-oem-6.5: one more pannel needs to disable psr2 Status in HWE Next: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2046681 [Impact] The customer Dell provide the edid for one more panel, this panel also needs to disable the psr2, otherwise the display will not work correctly [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
ODM verify passed on Orchid Bay MLK2 FHD panel. So verification done forlinux-oem-6.5 ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid -- 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/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux 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.5 source package in Jammy: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2046681] [NEW] jammy-oem-6.5: one more pannel needs to disable psr2
Public bug reported: tracking ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: originate-from-2045640 ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-6.5 (Ubuntu) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Tags added: originate-from-2045640 ** Also affects: hwe-next Importance: Undecided Status: New -- 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/2046681 Title: jammy-oem-6.5: one more pannel needs to disable psr2 Status in HWE Next: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: tracking To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Description changed: - is for tracking purpose. + BugLink: https://bugs.launchpad.net/bugs/2046315 + + [Impact] + On serveral Dell laptops, the screen often displays garbage or the screen is flicking + + [Fix] + There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. + + + [Test case] + + booting with the patched kernel, If the pannel's edid is in the qurik + list, the PSR2 will be disabled (checking + /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not + in the quirk list, the graphic driver will work as before. + + [Where problems could occur] + It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. -- 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/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2046315] [NEW] oem-6.5: disable psr2 for some panels according to edid
Public bug reported: is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Tags: oem-priority originate-from-2045640 somerville ** Changed in: linux-oem-6.5 (Ubuntu) Importance: Undecided => High ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Tags added: oem-priority originate-from-2045640 somerville ** Summary changed: - oem-6.5: disable psr2 for some panels according edid + oem-6.5: disable psr2 for some panels according to edid -- 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/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: New Bug description: is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2045517] Re: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S
** Description changed: + [Impact] + To support HP stella's latest machine, we need to backport some new PCIIDs and corresponding drivers to our OEM kernel, the requirement is here: + https://docs.google.com/spreadsheets/d/1_usKzZDxjtqlUzdOUPXvzNzSzhjRqcaV/edit#gid=1748766508 + + This pull-request is to unitfy and add some audio controller's ID, but + to do so, need to apply some depending patches otherwise it will have + conflict to introduce the new ID and new driver to OEM kernel. + + unified PCIIDs: + PCI_DEVICE_ID_INTEL_HDA_ADL_N + PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 + PCI_DEVICE_ID_INTEL_HDA_ADL_P + PCI_DEVICE_ID_INTEL_HDA_RPL_S + PCI_DEVICE_ID_INTEL_HDA_MTL + + new added PCIID: + PCI_DEVICE_ID_INTEL_HDA_ARL_S + + [Fix] + This add the audio driver for machines with Intel Arrowlake. + + [Test case] + Boot the patched kernel on a Arrowlake machine, the audio function could work. Boot the patches kernel on non-Arrowlake machines, the audio function could work as well as before. + + [Where problems could occur] + Could lose some pciids and make the auido driver not work on those machines, and could not play sound or record sound. But this possibility is very low, I checked each patch carefully and I verify the patcheset on some lenovo an dell machines. + From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based on it, added new PCIID and audio support for arrowlake-s, need to backport them to oem-6.5, this is a preparation for supporting HP latest laptops: unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S -- 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/2045517 Title: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S Status in linux package in Ubuntu: New 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: New Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] To support HP stella's latest machine, we need to backport some new PCIIDs and corresponding drivers to our OEM kernel, the requirement is here: https://docs.google.com/spreadsheets/d/1_usKzZDxjtqlUzdOUPXvzNzSzhjRqcaV/edit#gid=1748766508 This pull-request is to unitfy and add some audio controller's ID, but to do so, need to apply some depending patches otherwise it will have conflict to introduce the new ID and new driver to OEM kernel. unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S [Fix] This add the audio driver for machines with Intel Arrowlake. [Test case] Boot the patched kernel on a Arrowlake machine, the audio function could work. Boot the patches kernel on non-Arrowlake machines, the audio function could work as well as before. [Where problems could occur] Could lose some pciids and make the auido driver not work on those machines, and could not play sound or record sound. But this possibility is very low, I checked each patch carefully and I verify the patcheset on some lenovo an dell machines. From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based on it, added new PCIID and audio support for arrowlake-s, need to backport them to oem-6.5, this is a preparation for supporting HP latest laptops: unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045517/+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 2045517] [NEW] Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S
Public bug reported: >From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based >on it, added new PCIID and audio support for arrowlake-s, need to backport >them to oem-6.5, this is a preparation for supporting HP latest laptops: unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S ** Affects: linux (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Tags: oem-priority ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-6.5 (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Tags added: oem-priority ** Description changed: - From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based on it, added new PCIID and audio support for arrowlake-s, need to backport them to oem-6.5: + From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based on it, added new PCIID and audio support for arrowlake-s, need to backport them to oem-6.5, this is a preparation for supporting HP latest laptops: unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S -- 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/2045517 Title: Unify some HDA contoller PCIIDs and add new ID for Arrowlake-S Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: From kernel v6.6, HDA controller PCIIDs are sorted out and unified, and based on it, added new PCIID and audio support for arrowlake-s, need to backport them to oem-6.5, this is a preparation for supporting HP latest laptops: unified PCIIDs: PCI_DEVICE_ID_INTEL_HDA_ADL_N PCI_DEVICE_ID_INTEL_HDA_RPL_P_0 PCI_DEVICE_ID_INTEL_HDA_ADL_P PCI_DEVICE_ID_INTEL_HDA_RPL_S PCI_DEVICE_ID_INTEL_HDA_MTL new added PCIID: PCI_DEVICE_ID_INTEL_HDA_ARL_S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045517/+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 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-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/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 1996121] Re: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-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/1996121 Title: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: The cs35l41 codec driver was backported to Jammy kernel a couple of months ago, recently the Jammy kernel was adopted as the hwe kernel for OEM machines and with this kernel the UBSAN calltrace was seen, need to backport these 2 patches. Kinetic kernel already has the patches, so this SRU is only for Jammy kernel. [Impact] Install the 5.15 hwe kernel on the machines with cs35l41 codec, after booting and check the dmesg, there is a UBSAN calltrace. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, check the dmesg, there is no UBSAN calltrace, and test the audio functions, all input and output devices coudl work as well as before. [Where problems could occur] The patch only affects the cirruslogic asoc codec driver, if it could introduce the regression, it will be on the machines with cs codec, and it will make the audio driver initialization fail and make the system lose the audio function. But this possibility is very low, we tested the patches on many oem machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996121/+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 1997946] Re: [SRU] Support soundwire speaker AMP-ALC1318 codec
** Summary changed: - Support soundwire speaker AMP-ALC1318 codec + [SRU] Support soundwire speaker AMP-ALC1318 codec -- 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/1997946 Title: [SRU] Support soundwire speaker AMP-ALC1318 codec Status in OEM Priority Project: Triaged Status in alsa-ucm-conf package in Ubuntu: Confirmed Bug description: [ Impact ] * Add ALC1318 speaker codec ucm file * Make internal speaker working on the platform with the codec [ Test Plan ] * On platform with the codec, the internal speaker should work after boot into Ubuntu [ Where problems could occur ] * The config only be executed on the platform with the codec exported * It needs add codec configuration to the machine driver to make the function work [ Other Info ] * Upstream commit soundwire speaker AMP-ALC1318 codec. https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1997946/+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 2000465] Re: [SRU]rt715-sdca codec cannot record audio with internal microphone
** Summary changed: - rt715-sdca codec cannot record audio with internal microphone + [SRU]rt715-sdca codec cannot record audio with internal microphone -- 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/2000465 Title: [SRU]rt715-sdca codec cannot record audio with internal microphone Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] rt715-sdca codec cannot record audio with internal microphone [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Internal microphone should work propoerly. [Where problems could occur] Only fix for DUT with rt715-sdca device [Other Info] Upstream bug: https://github.com/alsa-project/alsa-ucm-conf/issues/255 Fix: https://github.com/alsa-project/alsa-ucm-conf/commit/e395d7b743584cba60876b6356fb3bc7834992aa To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000465/+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 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
** Tags removed: verification-needed-jammy ** Tags added: verification-done-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/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 1996121] Re: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec
** Tags removed: verification-needed-jammy ** Tags added: verification-done-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/1996121 Title: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: The cs35l41 codec driver was backported to Jammy kernel a couple of months ago, recently the Jammy kernel was adopted as the hwe kernel for OEM machines and with this kernel the UBSAN calltrace was seen, need to backport these 2 patches. Kinetic kernel already has the patches, so this SRU is only for Jammy kernel. [Impact] Install the 5.15 hwe kernel on the machines with cs35l41 codec, after booting and check the dmesg, there is a UBSAN calltrace. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, check the dmesg, there is no UBSAN calltrace, and test the audio functions, all input and output devices coudl work as well as before. [Where problems could occur] The patch only affects the cirruslogic asoc codec driver, if it could introduce the regression, it will be on the machines with cs codec, and it will make the audio driver initialization fail and make the system lose the audio function. But this possibility is very low, we tested the patches on many oem machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996121/+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 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
** Tags removed: verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-focal verification-done-jammy verification-done-kinetic -- 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/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 1996121] Re: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec
** Tags removed: verification-needed-jammy ** Tags added: verification-done-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/1996121 Title: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: The cs35l41 codec driver was backported to Jammy kernel a couple of months ago, recently the Jammy kernel was adopted as the hwe kernel for OEM machines and with this kernel the UBSAN calltrace was seen, need to backport these 2 patches. Kinetic kernel already has the patches, so this SRU is only for Jammy kernel. [Impact] Install the 5.15 hwe kernel on the machines with cs35l41 codec, after booting and check the dmesg, there is a UBSAN calltrace. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, check the dmesg, there is no UBSAN calltrace, and test the audio functions, all input and output devices coudl work as well as before. [Where problems could occur] The patch only affects the cirruslogic asoc codec driver, if it could introduce the regression, it will be on the machines with cs codec, and it will make the audio driver initialization fail and make the system lose the audio function. But this possibility is very low, we tested the patches on many oem machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996121/+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 1993609] Re: linux-firmware: add sdio firmware for qca9377 wifi module
Enabled the focal-proposed repo in the setting, ran apt-get update, and ran apt install linux-firmware, the linux-firmware is updated to 187.35, check the folder /lib/firmware/ath10k/QCA9377/hw1.0/, the firmware- sdio-5.bin is in that folder. And the wifi could work with this firmware on the imx6ull board. Verification done. ** Tags added: verification-done-focal -- 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/1993609 Title: linux-firmware: add sdio firmware for qca9377 wifi module Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Bug description: This firmware is already in the linux-firmware of upstream and jammy [Impact] We have a UC20 project to enable the qca9377 sdio wifi on a imx6ull board, without this firmware the ath10k-sdio wifi driver will fail to initialize and the wifi can't work. [Fix] Backport 1 patch from upstream linux-firmware. [Test] Install the patched linux-firmware and boot the kernel on that board, the ath10k-sdio.ko could find and load the firmware successfully and the wifi function worked well. [Where problems could occur] The patch is from upstream and Jammy already has this patch, this patch just adds new files to existing firmware, the regression possibility is very low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993609/+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 1996121] Re: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec
** Description changed: - this bug is for tracking purpose. + The cs35l41 codec driver was backported to Jammy kernel a couple of + months ago, recently the Jammy kernel was adopted as the hwe kernel + for OEM machines and with this kernel the UBSAN calltrace was seen, + need to backport these 2 patches. Kinetic kernel already has the + patches, so this SRU is only for Jammy kernel. + + [Impact] + Install the 5.15 hwe kernel on the machines with cs35l41 + codec, after booting and check the dmesg, there is a UBSAN calltrace. + + [Fix] + Backport 2 patches from mainlie kernel to fix this problem. + + [Test] + boot the patched kernel on the machine, check the dmesg, there + is no UBSAN calltrace, and test the audio functions, all input + and output devices coudl work as well as before. + + + [Where problems could occur] + The patch only affects the cirruslogic asoc codec driver, if it + could introduce the regression, it will be on the machines with + cs codec, and it will make the audio driver initialization fail + and make the system lose the audio function. But this possibility + is very low, we tested the patches on many oem machines, all + worked well. -- 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/1996121 Title: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: The cs35l41 codec driver was backported to Jammy kernel a couple of months ago, recently the Jammy kernel was adopted as the hwe kernel for OEM machines and with this kernel the UBSAN calltrace was seen, need to backport these 2 patches. Kinetic kernel already has the patches, so this SRU is only for Jammy kernel. [Impact] Install the 5.15 hwe kernel on the machines with cs35l41 codec, after booting and check the dmesg, there is a UBSAN calltrace. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, check the dmesg, there is no UBSAN calltrace, and test the audio functions, all input and output devices coudl work as well as before. [Where problems could occur] The patch only affects the cirruslogic asoc codec driver, if it could introduce the regression, it will be on the machines with cs codec, and it will make the audio driver initialization fail and make the system lose the audio function. But this possibility is very low, we tested the patches on many oem machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996121/+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 1996121] [NEW] alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec
Public bug reported: this bug is for tracking purpose. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Medium Status: In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) 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/1996121 Title: alsa: soc: the kernel print UBSAN calltrace on the machine with cs35l41 codec Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: this bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996121/+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 1992714] Re: SoF for RPL platform support
Subscribed Sponsor team. Hi Sponsor-team, when you have time, please help review the SRU request and upload it. thx. ** Summary changed: - SoF for RPL platform support + [SRU] SoF for RPL platform support -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: New Status in firmware-sof package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+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 1993609] Re: linux-firmware: add sdio firmware for qca9377 wifi module
** Description changed: - This is for tracking purpose. + This firmware is already in the linux-firmware of upstream and jammy + + [Impact] + We have a UC20 project to enable the qca9377 sdio wifi on a imx6ull + board, without this firmware the ath10k-sdio wifi driver will fail to + initialize and the wifi can't work. + + [Fix] + Backport 1 patch from upstream linux-firmware. + + [Test] + Install the patched linux-firmware and boot the kernel on that board, + the ath10k-sdio.ko could find and load the firmware successfully and + the wifi function worked well. + + + [Where problems could occur] + The patch is from upstream and Jammy already has this patch, this patch + just adds new files to existing firmware, the regression possibility is + very low -- 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/1993609 Title: linux-firmware: add sdio firmware for qca9377 wifi module Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Focal: In Progress Bug description: This firmware is already in the linux-firmware of upstream and jammy [Impact] We have a UC20 project to enable the qca9377 sdio wifi on a imx6ull board, without this firmware the ath10k-sdio wifi driver will fail to initialize and the wifi can't work. [Fix] Backport 1 patch from upstream linux-firmware. [Test] Install the patched linux-firmware and boot the kernel on that board, the ath10k-sdio.ko could find and load the firmware successfully and the wifi function worked well. [Where problems could occur] The patch is from upstream and Jammy already has this patch, this patch just adds new files to existing firmware, the regression possibility is very low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993609/+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 1993609] [NEW] linux-firmware: add sdio firmware for qca9377 wifi module
Public bug reported: This is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: High Status: In Progress ** Affects: linux-firmware (Ubuntu Focal) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: oem-priority originate-from-1990944 tillamook ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu) Status: New => In Progress ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Tags added: oem-priority originate-from-1990944 tillamook -- 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/1993609 Title: linux-firmware: add sdio firmware for qca9377 wifi module Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Focal: In Progress Bug description: This is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993609/+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 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
** Summary changed: - input/keyboard: the keyboard on some ASUS laptops can't work + input/keyboard: the keyboard on some Asus laptops can't work -- 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/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 1992266] Re: input/keyboard: the keyboard on some ASUS laptops can't work
** Description changed: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 + + The bug originates from an upstream bug, and the ubuntu users request + me to do a SRU to make the ubuntu linux work on their Asus laptops, so + once the pathces are merge to mainline kernel, I start to prepare this + SRU. + + [Impact] + Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel + will override to a new configuration for that IRQ, this will make the + keyboard not work anymore under linux. + + [Fix] + Backport 2 patches from mainlie kernel to fix this problem. + + [Test] + boot the patched kernel on the machine, test the keyboard, all + regular keys could work. + + + [Where problems could occur] + The patches use the dmi table to match the machines, so only the + matched Asus laptops will be impacted by the patches, if there is + any regression, the regression only affects those matched Asus + laptops, and the regression possibility is very low since ubuntu + users already tested the patches on their own Asus laptops. -- 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/1992266 Title: input/keyboard: the keyboard on some ASUS laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 1992266] [NEW] input/keyboard: the keyboard on some ASUS laptops can't work
Public bug reported: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Medium Assignee: Hui Wang (hui.wang) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Medium Assignee: Hui Wang (hui.wang) Status: In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) 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/1992266 Title: input/keyboard: the keyboard on some ASUS laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 1989518] Re: AMD ACP 6.2 DMIC support
** Description changed: - This is for tracking purpose. + The patchset will be merged to upstream kernel v6.1, the unstable + kernel will have the patchset automatically after the v6.1 is ready. + + The oem-5.17 kernel doesn't support this AMD generation platform yet, + so this patchset is useless for oem-5.17 so far. + + [Impact] + On the AMD PS platforms, the internal mic can't be detected + and there is no internal mic for users to use. + + [Fix] + Backport 13 patches from linux-next kernel to fix this problem. + + [Test] + boot the patched kernel on the machine, after loging into the + desktop, open the gnome-sound-setting, there is + internal mic, and could record sound via internal mic. + + + [Where problems could occur] + This only impacts intenal mic support on AMD ps machines, it will + match the pci device revision and apply the driver according to + match result, in theory it will not bring regression on non-amd-ps + machines. -- 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/1989518 Title: AMD ACP 6.2 DMIC support Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: The patchset will be merged to upstream kernel v6.1, the unstable kernel will have the patchset automatically after the v6.1 is ready. The oem-5.17 kernel doesn't support this AMD generation platform yet, so this patchset is useless for oem-5.17 so far. [Impact] On the AMD PS platforms, the internal mic can't be detected and there is no internal mic for users to use. [Fix] Backport 13 patches from linux-next kernel to fix this problem. [Test] boot the patched kernel on the machine, after loging into the desktop, open the gnome-sound-setting, there is internal mic, and could record sound via internal mic. [Where problems could occur] This only impacts intenal mic support on AMD ps machines, it will match the pci device revision and apply the driver according to match result, in theory it will not bring regression on non-amd-ps machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989518/+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 1989518] [NEW] AMD ACP 6.2 DMIC support
Public bug reported: This is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Tags: amd oem-priority originate-from-1986008 ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Also affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Tags added: amd oem-priority originate-from-1986008 -- 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/1989518 Title: AMD ACP 6.2 DMIC support Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: This is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989518/+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 1959681] Re: mic not working on HP-EliteBook-830-G7
** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Incomplete -- 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/1959681 Title: mic not working on HP-EliteBook-830-G7 Status in linux-firmware package in Ubuntu: Incomplete Status in linux-firmware source package in Bionic: Incomplete Status in linux-firmware source package in Focal: Incomplete Bug description: There is no audio input from the built-in mic available on Bionic & Focal on certain intel audio hw (00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8]) despite trying different kernel cmdline options (snd_hda_intel.dmic_detect=0 or snd_intel_dspcfg.dsp_driver=1). The behavior was similar on Bionic and Focal - no mic listed in alsa/pulseaudio mixers. Additionally the following can be found in the kernel log: sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver sof-audio-pci :00:1f.3: enabling device ( -> 0002) sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found The situation is different on impish - on this release the mic is available out of the box. I made a simple test of overwriting sof files inside Focal's linux- firmware package with the contents of firmware-sof-signed package from impish finding it solved the issue without any trace of errors in the logs. The same approach did not work on Bionic (despite similar kernel versions used in both 5.4.0) - due to HWE). These are some excerpts from Bionic launching impish SOF firmware: sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:10:0 sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel sof-audio-pci :00:1f.3: firmware boot complete sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:10:0 sof-audio-pci :00:1f.3: warn: topology ABI is more recent than kernel sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp3 Tx not handled sof-audio-pci :00:1f.3: warning: widget type 0 name codec0_in not handled sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp2 Tx not handled sof-audio-pci :00:1f.3: warning: widget type 0 name codec1_in not handled sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp1 Tx not handled sof-audio-pci :00:1f.3: warning: widget type 1 name codec0_out not handled sof-audio-pci :00:1f.3: warning: widget type 7 name Analog CPU Playback not handled sof-audio-pci :00:1f.3: warning: widget type 1 name codec1_out not handled sof-audio-pci :00:1f.3: warning: widget type 7 name Digital CPU Playback not handled sof-audio-pci :00:1f.3: warning: widget type 0 name codec2_in not handled sof-audio-pci :00:1f.3: warning: widget type 7 name Alt Analog CPU Playback not handled sof-audio-pci :00:1f.3: warning: widget type 1 name codec2_out not handled sof-audio-pci :00:1f.3: warning: widget type 0 name Analog CPU Capture not handled sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp1_out not handled sof-audio-pci :00:1f.3: warning: widget type 0 name Digital CPU Capture not handled sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp2_out not handled sof-audio-pci :00:1f.3: warning: widget type 0 name Alt Analog CPU Capture not handled sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp3_out not handled [ Test Plan ] 1. Launch Ubuntu desktop on affected hardware. 2. Open audio mixer (e.g. pulsemixer). 3. Look for built-in audio input (e.g. Built-in Audio Analog Stereo). Expected result: Built-in mic is available for use. Actual result: Built-in mic is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1959681/+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 1980700] Re: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines
Installed the kernel 5.14.0-1046 oem kernel, open the gnome-sound- setting, there is a dmic in the input device list, and it could record the sound. Verification done on focal. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980700 Title: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: The fix is already in the upstream kernel v5.19-rc1, no need to send the patches to unstable kernel. And for Jammy kernel, this SRU depends on #1949245, after merging the patchset for #1949245, then could apply this SRU to jammy. [Impact] On the AMD YC platforms, the internal mic can't be detected and there is no internal mic for users to use. [Fix] Backport 2 patches from mainline kernel to fix this problem. [Test] boot the patched kernel on the machine which has updated BIOS, after loging into the desktop, open the gnome-sound-setting, there is internal mic, and could record sound via internal mic. [Where problems could occur] This only impacts intenal mic detection on AMD yc machines, it will check the acpi variable first, if not detected, it will check the acpi dmi table as before, so the regression possibility is very low, and we already tested these patches on a couple of Lenovo YC machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980700/+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 1980700] Re: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines
Installed the kernel 5.15.0-43.46, open the gnome-sound-setting, there is a dmic in the input device list, and it could record the sound. Verification done on jammy. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980700 Title: alsa: asoc: amd: the internal mic can't be dedected on yellow carp machines Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: The fix is already in the upstream kernel v5.19-rc1, no need to send the patches to unstable kernel. And for Jammy kernel, this SRU depends on #1949245, after merging the patchset for #1949245, then could apply this SRU to jammy. [Impact] On the AMD YC platforms, the internal mic can't be detected and there is no internal mic for users to use. [Fix] Backport 2 patches from mainline kernel to fix this problem. [Test] boot the patched kernel on the machine which has updated BIOS, after loging into the desktop, open the gnome-sound-setting, there is internal mic, and could record sound via internal mic. [Where problems could occur] This only impacts intenal mic detection on AMD yc machines, it will check the acpi variable first, if not detected, it will check the acpi dmi table as before, so the regression possibility is very low, and we already tested these patches on a couple of Lenovo YC machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980700/+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 1978915] Re: alsa/hda: mute led can't work on the lenovo machine with cs35l41 s-codec
** Description changed: - This bug is for tracking purpose. + The fix is already in the upstream kernel stable-v5.17, no need to + send this patch to oem-5.17 and unstable kernels. + + [Impact] + After we apply the cs35l41 s-codec patchset to the oem-5.14 and jammy + kernels, the mute led can't work anymore. + + [Fix] + Backport a patch from mainline kernel to fix this regression + + [Test] + boot the patched kernel, press mute hotkey, the speaker is muted + and the mute led is on, press the mute hotkey again, the speaker + is unmuted and the mute led is off. + + + [Where problems could occur] + After merging this patch, it is possible to affect the machines which + apply the ALC287_FIXUP_CS35L41_I2C_2, but the regression possibility + is very low since hda_fixup_thinkpad_acpi() could check if the quirk + is suitable for the running machine. And we did test, all machines + could work well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978915 Title: alsa/hda: mute led can't work on the lenovo machine with cs35l41 s-codec Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: The fix is already in the upstream kernel stable-v5.17, no need to send this patch to oem-5.17 and unstable kernels. [Impact] After we apply the cs35l41 s-codec patchset to the oem-5.14 and jammy kernels, the mute led can't work anymore. [Fix] Backport a patch from mainline kernel to fix this regression [Test] boot the patched kernel, press mute hotkey, the speaker is muted and the mute led is on, press the mute hotkey again, the speaker is unmuted and the mute led is off. [Where problems could occur] After merging this patch, it is possible to affect the machines which apply the ALC287_FIXUP_CS35L41_I2C_2, but the regression possibility is very low since hda_fixup_thinkpad_acpi() could check if the quirk is suitable for the running machine. And we did test, all machines could work well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978915/+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 1978915] [NEW] alsa/hda: mute led can't work on the lenovo machine with cs35l41 s-codec
Public bug reported: This bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1978898 sutton ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Tags added: oem-priority originate-from-1978898 sutton -- 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/1978915 Title: alsa/hda: mute led can't work on the lenovo machine with cs35l41 s-codec Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978915/+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 1974842] Re: Audio card [8086:9d71] does not work at all (input, output) on 22.04
Subcribe Chris, could you take a look at this bug? Is sth from lp:1915117 not upstreamed? -- 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/1974842 Title: Audio card [8086:9d71] does not work at all (input, output) on 22.04 Status in linux package in Ubuntu: Confirmed Bug description: A year ago, I filed lp:1915117 after an kernel update broke the audio on my Acer Swift SF314-54. The bug has been marked as fixed, but I just tried 22.04 this morning, using 5.15.0-25-generic, and I don't have any audio at all. Please check lp:1915117 for some background, and the attached logs from sosreport for more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Sat May 21 00:27:20 2022 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Acer Swift SF314-54 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2021 dmi.bios.release: 1.17 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd04/16/2021:br1.17:efr1.9:svnAcer:pnSwiftSF314-54:pvrV1.17:rvnKBL:rnStrongbow_KL:rvrV1.17:cvnAcer:ct10:cvrV1.17:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1974842/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
verification firmware-sof under Jammy: Install the jammy to that dell SNDW machine without internal mic, enable the -proposed ppa, run apt-get update; apt-get dist-upgrade; check the firmware-sof-signed version is 2.0-1ubuntu3 now. reboot. After booting up, check dmesg, the tplg sof-adl-rt711-l2-rt1316-l01.tplg is found and loaded successfully. check audio devices from gnome-sound-setting, all output and input devices works as expected. Verification done for firmware-sof for Jammy. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965496 Title: alsa: enable the cirrus-logic side-codec to make the speaker output sound Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] We have a couple of lenovo latops models which have cirrus-logic side codec between realtek codec and speaker, it plays a role as amplifier, we need to enable this side-codec, otherwise the speaker can't output sound. [Fix] Backport codec patches and some i2c and acpi detection patches from mainline kernel and linux-next [Test] boot the patched kernel, run speaker test, both left and right channel could work well. [Where problems could occur] If it could introduce regression, it will be on soc wm_adsp codec drivers, since most of patch are adding new codec drivers, it will not touch existing codec drivers. If a machine with wm_adsp codec can't output sound or record sound, it means this SRU introduce the regression on wm_adsp driver, but this possibility is very low, since all patches are picked from mainline kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965496/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in firmware-sof source package in Focal: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1861070] Re: Raspberry Pi 4B: USB OTG is not working
** Changed in: linux-raspi2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861070 Title: Raspberry Pi 4B: USB OTG is not working Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Fix Released Status in linux-raspi source package in Focal: Fix Released Bug description: [Impact] On the RPI4B board, the usb-c power port could also work as a USB OTG mode, but we set the dwc2 driver to the host mode unconditionally, now set it to dual_role mode, then it could work in host/otg/peripheal mode. [Fix] Set USB_DWC2_DUAL_ROLE=y, USB_DWC2_HOST=n [Test Case] set the dtoverlay=dwc2,dr_mode=[otg|peripheral] in the config.txt, and isnmod the g_ether or g_cdc, on the host machine, we could see RPI4B work as a usb device. Because physical port limitation, could test dr_mode=host. [Regression Risk] Low, our eoan kernel choose dwc_otg driver for this port by default, very very few users will choose dwc2 driver, and the dwc2 driver is not enabled by default in our kernel. And bug reporter and I already tested that the peripheral mode works after this change. I am using Raspberry Pi 4B (4GB) and want to make use of the OTG functionality (g_ether). I cross checked with Raspbian to make sure it is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with latest updates applied as of Jan 26th, 2020 via "apt-get update" and "apt-get full-upgrade": ... [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [1.517365] dwc_otg: FIQ enabled [1.517376] dwc_otg: NAK holdoff enabled [1.517386] dwc_otg: FIQ split-transaction FSM enabled [1.517399] Module dwc_common_port init ... [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host [6.409098] dwc2 fe98.usb: DWC OTG Controller [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98 ... [ 111.796714] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I think it is that "Configuration mismatch. dr_mode forced to host" log entry telling me that the port is acting as HOST mode instead of OTG mode. I have try putting these in usercfg.txt "dtoverlay=dwc2" "dtoverlay=dwc2,dr_mode=otg" "dtoverlay=dwc2,dr_mode=peripheral" and it will give the same result, no OTG functionality. On the same hardware running Raspbian Buster, it initialise successfully. Corresponding dmesg: ... [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [0.570391] dwc_otg: FIQ enabled [0.570400] dwc_otg: NAK holdoff enabled [0.570409] dwc_otg: FIQ split-transaction FSM enabled [0.570421] Module dwc_common_port init ... [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0 [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1 [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1 [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [2.752511] dwc2 fe98.usb: DWC OTG Controller [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98 ... [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [2.851601] g_ether gadget: g_ether ready [2.854580] dwc2 fe98.usb: bound driver g_ether [2.998525] dwc2 fe98.usb: new device is high-speed [3.075025] dwc2 fe98.usb: new device is high-speed [3.139338] dwc2 fe98.usb: new address 10 [3.154010] g_ether gadget: high-speed config #1: CDC Ethernet (ECM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1861070/+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 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
The SRU for oem-5.17 was sent out. ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965496 Title: alsa: enable the cirrus-logic side-codec to make the speaker output sound Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] We have a couple of lenovo latops models which have cirrus-logic side codec between realtek codec and speaker, it plays a role as amplifier, we need to enable this side-codec, otherwise the speaker can't output sound. [Fix] Backport codec patches and some i2c and acpi detection patches from mainline kernel and linux-next [Test] boot the patched kernel, run speaker test, both left and right channel could work well. [Where problems could occur] If it could introduce regression, it will be on soc wm_adsp codec drivers, since most of patch are adding new codec drivers, it will not touch existing codec drivers. If a machine with wm_adsp codec can't output sound or record sound, it means this SRU introduce the regression on wm_adsp driver, but this possibility is very low, since all patches are picked from mainline kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965496/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
Hi Sponsor team, To fix this bug for jammy, need to add a binary file to firmware-sof- signed package, but the quilt doesn't support binary file changes, I can't generate debdiff for this SRU. Here I referred to the Vicamo and Juerg's solution, add the file to the git repo directly and send a merge request: https://code.launchpad.net/~hui.wang/ubuntu/+source/firmware- sof/+git/firmware-sof/+merge/419359 Please help review it and merge it if no need to change sth in that MR. thx. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in firmware-sof source package in Focal: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
** Also affects: firmware-sof (Ubuntu) Importance: Undecided Status: New ** Changed in: firmware-sof (Ubuntu Focal) Status: New => Invalid ** Changed in: firmware-sof (Ubuntu Jammy) Importance: Undecided => High ** Changed in: firmware-sof (Ubuntu Jammy) Status: New => In Progress -- 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/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in firmware-sof package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in firmware-sof source package in Focal: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
Will check jammy today. I remember Juerg and Vicamo did sth on jammy several days ago. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
** Description changed: + SRU template for linux-firmware + [Impact] + we have a Dell ADL laptop which has sdw audio, but there is no camera + and no internal digital mic in this machine, the current asoc driver + can't work on this machine, the speaker and headset couldn't work. + + [Fix] + Backport a tplg file which is specific to this mahcine + + [Test] + Install the patched linux-firmware and boot the latest oem-5.14 kernel + on the machine, check dmesg, it loads the correct tplg, and + test speaker and headset, all work well. + + [Where problems could occur] + This SRU is adding a new tplg file, it has no chance to introduce + a regression. + + SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU template for linux-firmware [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current asoc driver can't work on this machine, the speaker and headset couldn't work. [Fix] Backport a tplg file which is specific to this mahcine [Test] Install the patched linux-firmware and boot the latest oem-5.14 kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] This SRU is adding a new tplg file, it has no chance to introduce a regression. SRU template for linux [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
** Also affects: linux-firmware (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/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
Thanks Andy, I am SRUing the tplg now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Fix Committed Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
Installed the linux-oem-5.14/5.14.0-1032.35 on the lenovo machine which has the cirrus-logic side codec, the speaker could output sound with the proposed kernel. Verification done. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965496 Title: alsa: enable the cirrus-logic side-codec to make the speaker output sound Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] We have a couple of lenovo latops models which have cirrus-logic side codec between realtek codec and speaker, it plays a role as amplifier, we need to enable this side-codec, otherwise the speaker can't output sound. [Fix] Backport codec patches and some i2c and acpi detection patches from mainline kernel and linux-next [Test] boot the patched kernel, run speaker test, both left and right channel could work well. [Where problems could occur] If it could introduce regression, it will be on soc wm_adsp codec drivers, since most of patch are adding new codec drivers, it will not touch existing codec drivers. If a machine with wm_adsp codec can't output sound or record sound, it means this SRU introduce the regression on wm_adsp driver, but this possibility is very low, since all patches are picked from mainline kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965496/+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 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic
** Description changed: - This bug is for tracking purpose. + [Impact] + we have a Dell ADL laptop which has sdw audio, but there is no camera + and no internal digital mic in this machine, the current soc driver + can't work on this machine, it will load a wrong tplg without this patch, + and the speaker and headset couldn't work. + + [Fix] + Backport one patch from upstream. + + [Test] + Boot the patched kernel on the machine, check dmesg, it loads the + correct tplg, and test speaker and headset, all work well. + + [Where problems could occur] + If it could introduce regression, it will be on the sdw codec matching + for adl machines, then it will make the driver load wrong tplg and make + output device and input device not work anymore. But this possibility + is very low, we already tested the patch on some dell adl machines, no + regression found. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] we have a Dell ADL laptop which has sdw audio, but there is no camera and no internal digital mic in this machine, the current soc driver can't work on this machine, it will load a wrong tplg without this patch, and the speaker and headset couldn't work. [Fix] Backport one patch from upstream. [Test] Boot the patched kernel on the machine, check dmesg, it loads the correct tplg, and test speaker and headset, all work well. [Where problems could occur] If it could introduce regression, it will be on the sdw codec matching for adl machines, then it will make the driver load wrong tplg and make output device and input device not work anymore. But this possibility is very low, we already tested the patch on some dell adl machines, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1966841] [NEW] alsa/sdw: Fix the audio issue on a Dell machine without internal mic
Public bug reported: This bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: High Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: High Status: Invalid ** Tags: oem-priority originate-from-1947673 somerville ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux-oem-5.14 (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Jammy) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: High Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Tags added: oem-priority originate-from-1947673 somerville ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) 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/1966841 Title: alsa/sdw: Fix the audio issue on a Dell machine without internal mic Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966841/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
** Changed in: pulseaudio (Ubuntu) Assignee: Hui Wang (hui.wang) => Kai-Heng Feng (kaihengfeng) -- 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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Confirmed Status in pulseaudio source package in Focal: Fix Released Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
** Description changed: - This bug is for tracking purpose. + [Impact] + We have a couple of lenovo latops models which have cirrus-logic side + codec between realtek codec and speaker, it plays a role as amplifier, + we need to enable this side-codec, otherwise the speaker can't output + sound. + + [Fix] + Backport codec patches and some i2c and acpi detection patches from + mainline kernel and linux-next + + [Test] + boot the patched kernel, run speaker test, both left and right channel + could work well. + + [Where problems could occur] + If it could introduce regression, it will be on soc wm_adsp codec + drivers, since most of patch are adding new codec drivers, it will + not touch existing codec drivers. If a machine with wm_adsp codec + can't output sound or record sound, it means this SRU introduce + the regression on wm_adsp driver, but this possibility is very + low, since all patches are picked from mainline kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965496 Title: alsa: enable the cirrus-logic side-codec to make the speaker output sound Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] We have a couple of lenovo latops models which have cirrus-logic side codec between realtek codec and speaker, it plays a role as amplifier, we need to enable this side-codec, otherwise the speaker can't output sound. [Fix] Backport codec patches and some i2c and acpi detection patches from mainline kernel and linux-next [Test] boot the patched kernel, run speaker test, both left and right channel could work well. [Where problems could occur] If it could introduce regression, it will be on soc wm_adsp codec drivers, since most of patch are adding new codec drivers, it will not touch existing codec drivers. If a machine with wm_adsp codec can't output sound or record sound, it means this SRU introduce the regression on wm_adsp driver, but this possibility is very low, since all patches are picked from mainline kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965496/+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