[Kernel-packages] [Bug 1960766] [NEW] Introduce 510 NVIDIA driver series
Public bug reported: The nvidia-settings packages is needed for the new Nvidia 510 series driver from 20.04 for OEM customer. ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Introduce Nvidia the 510 series + Introduce 510 NVIDIA driver series -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1960766 Title: Introduce 510 NVIDIA driver series Status in nvidia-settings package in Ubuntu: New Bug description: The nvidia-settings packages is needed for the new Nvidia 510 series driver from 20.04 for OEM customer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1960766/+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 1856077] Re: Fix latency issue on Realtek Bluetooth
This fix is required for a customer image release. Can we have the linux-firmware including the fix available before end of December 2019? Thank you. -- 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/1856077 Title: Fix latency issue on Realtek Bluetooth Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: New Bug description: [Impact] When multiple Bluetooth devices are connected to Realtek Bluetooth controller, the BT latency becomes really high, e.g. audio stutters, mouse lags. [Fix] The new Realtek Bluetooth firmware can fix the issue. [Test] Cold boot the system to reload the new firmware, and the issue is gone. [Regression Potential] Low. The firmware is already in Eoan. We also tested it on Bionic and haven't found any regression so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1856077/+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 1817518] Re: Bluetooth not working (Intel CyclonePeak)
There are couple of OEM images requires this fix and expected to be released next week. Can we expect the linux-firmware including this fix updated before May 15th, if possible? -- 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/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: In Progress Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+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 1381625] Re: Adjust brightness to lowest value caused screen whole black
@Timo, Original oem lp:1281379 was reported with Intel Haswell or Chief River platforms. We will verify with vivid in kittyhawk 2.0 and update result here. -- 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/1381625 Title: Adjust brightness to lowest value caused screen whole black Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Bug description: When using F2 hotkey to adjust screen brightness to lowest value, it truns screen backlight off. Steps: 1. Press F2 to adjust screen brightness to lowest value Expected results: There is still screen backlight Actual results: Sceen backlight is turned off To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1381625/+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
