This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux - 5.4.0-91.102
---
linux (5.4.0-91.102) focal; urgency=medium
* focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux-azure - 5.13.0-1008.9
---
linux-azure (5.13.0-1008.9) impish; urgency=medium
* impish/linux-azure: 5.13.0-1008.9 -proposed tracker (LP: #1949734)
* linux-azure: make mana.ko built-in (LP: #1949357)
- [Config] CONFIG_MICROSOFT_MANA=y
This bug was fixed in the package linux-raspi - 5.13.0-1011.13
---
linux-raspi (5.13.0-1011.13) impish; urgency=medium
* impish/linux-raspi: 5.13.0-1011.13 -proposed tracker (LP: #1949737)
* Cannot start docker container on ubuntu 21.10 server for raspberry pi
(LP: #1947601)
This bug was fixed in the package linux - 4.15.0-163.171
---
linux (4.15.0-163.171) bionic; urgency=medium
* bionic/linux: 4.15.0-163.171 -proposed tracker (LP: #1949874)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update
This bug was fixed in the package linux-azure - 5.4.0-1064.67
---
linux-azure (5.4.0-1064.67) focal; urgency=medium
* focal/linux-azure: 5.4.0-1064.67 -proposed tracker (LP: #1949816)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
* Drivers: hv: vmbus:
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux-raspi - 5.13.0-1011.13
---
linux-raspi (5.13.0-1011.13) impish; urgency=medium
* impish/linux-raspi: 5.13.0-1011.13 -proposed tracker (LP: #1949737)
* Cannot start docker container on ubuntu 21.10 server for raspberry pi
(LP: #1947601)
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux-raspi - 5.13.0-1011.13
---
linux-raspi (5.13.0-1011.13) impish; urgency=medium
* impish/linux-raspi: 5.13.0-1011.13 -proposed tracker (LP: #1949737)
* Cannot start docker container on ubuntu 21.10 server for raspberry pi
(LP: #1947601)
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux - 4.15.0-163.171
---
linux (4.15.0-163.171) bionic; urgency=medium
* bionic/linux: 4.15.0-163.171 -proposed tracker (LP: #1949874)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux - 5.4.0-91.102
---
linux (5.4.0-91.102) focal; urgency=medium
* focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.4.0-91.102
---
linux (5.4.0-91.102) focal; urgency=medium
* focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1020.24
---
linux-oem-5.13 (5.13.0-1020.24) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1020.24 -proposed tracker (LP:
#1949739)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1020.24
---
linux-oem-5.13 (5.13.0-1020.24) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1020.24 -proposed tracker (LP:
#1949739)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.11.0-41.45
---
linux (5.11.0-41.45) hirsute; urgency=medium
* hirsute/linux: 5.11.0-41.45 -proposed tracker (LP: #1949801)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.13.0-22.22
---
linux (5.13.0-22.22) impish; urgency=medium
* impish/linux: 5.13.0-22.22 -proposed tracker (LP: #1949740)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
*
This bug was fixed in the package linux-azure - 5.4.0-1064.67
---
linux-azure (5.4.0-1064.67) focal; urgency=medium
* focal/linux-azure: 5.4.0-1064.67 -proposed tracker (LP: #1949816)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
* Drivers: hv: vmbus:
This bug was fixed in the package linux - 5.4.0-91.102
---
linux (5.4.0-91.102) focal; urgency=medium
* focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.4.0-91.102
---
linux (5.4.0-91.102) focal; urgency=medium
* focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.4.0-91.102
---
linux (5.4.0-91.102) focal; urgency=medium
* focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.4.0-91.102
---
linux (5.4.0-91.102) focal; urgency=medium
* focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 4.15.0-163.171
---
linux (4.15.0-163.171) bionic; urgency=medium
* bionic/linux: 4.15.0-163.171 -proposed tracker (LP: #1949874)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update
This bug was fixed in the package linux - 5.4.0-91.102
---
linux (5.4.0-91.102) focal; urgency=medium
* focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.4.0-91.102
---
linux (5.4.0-91.102) focal; urgency=medium
* focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.4.0-91.102
---
linux (5.4.0-91.102) focal; urgency=medium
* focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 5.4.0-91.102
---
linux (5.4.0-91.102) focal; urgency=medium
* focal/linux: 5.4.0-91.102 -proposed tracker (LP: #1949840)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from
This bug was fixed in the package linux - 4.15.0-163.171
---
linux (4.15.0-163.171) bionic; urgency=medium
* bionic/linux: 4.15.0-163.171 -proposed tracker (LP: #1949874)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update
This bug was fixed in the package linux - 4.15.0-163.171
---
linux (4.15.0-163.171) bionic; urgency=medium
* bionic/linux: 4.15.0-163.171 -proposed tracker (LP: #1949874)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update
This bug was fixed in the package linux - 4.15.0-163.171
---
linux (4.15.0-163.171) bionic; urgency=medium
* bionic/linux: 4.15.0-163.171 -proposed tracker (LP: #1949874)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update
This bug was fixed in the package linux - 4.15.0-163.171
---
linux (4.15.0-163.171) bionic; urgency=medium
* bionic/linux: 4.15.0-163.171 -proposed tracker (LP: #1949874)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update
This bug was fixed in the package linux-aws - 5.4.0-1060.63
---
linux-aws (5.4.0-1060.63) focal; urgency=medium
* focal/linux-aws: 5.4.0-1060.63 -proposed tracker (LP: #1949811)
* linux-aws: Fix backport of RDMA/efa: Expose maximum TX doorbell batch
(LP: #1949882)
-
This bug was fixed in the package linux - 4.15.0-163.171
---
linux (4.15.0-163.171) bionic; urgency=medium
* bionic/linux: 4.15.0-163.171 -proposed tracker (LP: #1949874)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update
This bug was fixed in the package linux - 4.15.0-163.171
---
linux (4.15.0-163.171) bionic; urgency=medium
* bionic/linux: 4.15.0-163.171 -proposed tracker (LP: #1949874)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update
This bug was fixed in the package linux - 4.15.0-163.171
---
linux (4.15.0-163.171) bionic; urgency=medium
* bionic/linux: 4.15.0-163.171 -proposed tracker (LP: #1949874)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update
This bug was fixed in the package linux - 4.15.0-163.171
---
linux (4.15.0-163.171) bionic; urgency=medium
* bionic/linux: 4.15.0-163.171 -proposed tracker (LP: #1949874)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-oem-5.10 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
This bug was fixed in the package nvidia-graphics-drivers-470 -
470.86-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1950665):
- Fixed a regression which prevented DisplayPort and HDMI 2.1
This bug was fixed in the package nvidia-graphics-drivers-470 -
470.86-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-470 (470.86-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1950665):
- Fixed a regression which prevented DisplayPort and HDMI 2.1
This bug was fixed in the package nvidia-graphics-drivers-470 -
470.86-0ubuntu0.21.04.1
---
nvidia-graphics-drivers-470 (470.86-0ubuntu0.21.04.1) hirsute; urgency=medium
* New upstream release (LP: #1950665):
- Fixed a regression which prevented DisplayPort and HDMI 2.1
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-oem-5.10 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
This bug was fixed in the package nvidia-graphics-drivers-470 -
470.86-0ubuntu0.21.10.1
---
nvidia-graphics-drivers-470 (470.86-0ubuntu0.21.10.1) impish; urgency=medium
* New upstream release (LP: #1950665):
- Fixed a regression which prevented DisplayPort and HDMI 2.1
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1952385
Title:
Fix missing external
** Also affects: linux-azure-5.4 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure-5.4 (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-azure-5.4 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-azure-5.4 (Ubuntu Bionic)
The verification of the Stable Release Update for nvidia-graphics-
drivers-470 has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
Public bug reported:
SRU Justification
[Impact]
During large scale deployment testing, we found below call trace when
provisioning Ubuntu 18.04 VM with size Standard_NV24. Engineer deployed
instance 10 times and encountered once.
It looks like a race condition when probe device, but finally
Works fine on 5.10.0-1052-oem.
Cascardo.
** 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/1950239
** Also affects: linux-azure (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: linux-azure
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu.
Working as expected on 5.4.0-91-generic and 5.10.0-1052-oem.
$ ldattach HCI /dev/tty
ldattach: cannot set line discipline: Operation not permitted
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member
** Changed in: linux-azure (Ubuntu Hirsute)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1950336
Title:
hirsute/linux-azure: Backport more
The firmware of your device is already at the latest upstream version
(API 46). Can you install the 5.15 kernel from jammy-proposed to see if
things behave more stable? 5.15 will be the release kernel for jammy.
$ apt-add-repository -p proposed
$ apt install linux-generic
$ apt-add-repository -r
Idea: move the strict `nvidia-kernel-common-N (<= N)` from the `linux-
modules-nvidia-N-ABI` package to the meta packages `linux-modules-
nvidia-N-kernelflavour`
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in
The dependencies are intentionally very strict, to ensure that kernel /
nvidia drivers / nvidia userspace are all installed and are compatible
with each other.
However, it was intended to be upgradable unattended. And since one can
have up to three kernel ABIs on disk, one should in theory be
@antonio-petricca, What series? What kernel?
I can produce a hirsute linux-firmware package with the reverted sdma
firmware but need someone to verify it on hirsute with the hirsute
kernel. Any takers? Or have you all moved on to impish?
--
You received this bug notification because you are a
This bug was fixed in the package linux-intel-5.13 - 5.13.0-1008.8
---
linux-intel-5.13 (5.13.0-1008.8) focal; urgency=medium
* focal/linux-intel-5.13: 5.13.0-1008.8 -proposed tracker (LP:
#1951371)
* Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config]
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1952411
Title:
Lenovo 14W Gen2 - Touchpad
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1952606
and then change the status of the bug to 'Confirmed'.
If, due to the
Looks like I made a mistake in subject.
This bug is incidentally fixed by revert the amdgpu firmware, bug
#1945565
** Summary changed:
- [SRU][H] linux-firmware miss amdgpu/renoir_ta.bin
+ [SRU][F] linux-firmware miss amdgpu/renoir_ta.bin
** Changed in: linux-firmware (Ubuntu Focal)
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1952411
Title:
Lenovo 14W Gen2 - Touchpad don't work
Status in linux
With latest firmare
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/snapshot/linux-firmware-20211027.tar.gz is much more
stable.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Public bug reported:
After installing Ubuntu 20.04.3 (Kernel 5.11.0-38-generic) on PXIe controller
with I225-IT Ethernet Controller, running dmesg message output the following
error thrown by igc driver module:
[0.882371] igc: probe of :6d:00.0 failed with error -2
[0.914344] igc:
** Also affects: mesa (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Hirsute)
Importance: Undecided
Status: New
** No longer affects: mesa (Ubuntu Hirsute)
** Changed in: mesa (Ubuntu)
Status: Confirmed => Invalid
**
@antonio-petricca, sorry but 5.15.2 is not a supported Ubuntu kernel and
especially not on Bionic with (old) Bionic firmware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Ok, thanks for the update. Interestingly, AFAIK the iwlwifi driver
specifies a max API number (50 in case of the focal 5.4 kernel) and
tries to load that firmware and then walks down until it succeeds:
[9.458673] iwlwifi :52:00.0: Direct firmware load for
iwlwifi-cc-a0-50.ucode failed
apport-collect fails with 401, so no logs available.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1952425
Title:
amdgpu/renoir_ta.bin was added in upstream commit:
commit 9f46d48ead48c33bccfd54ce22646478faea7cb1
Author: Alex Deucher
Date: Wed Sep 30 11:05:26 2020 -0400
amdgpu: update renoir firmware for 20.40
From internal git commit:
fd5448a9b0baaa538a1785f33d1a728d62cf869a
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1952581
Title:
ACPI Error: No handler for
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
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/1952581
Title:
ACPI Error: No handler for Region [VRTC]
Status in linux package in
You have been subscribed to a public bug:
>From sniffing around seems to be something Kernal related specific to the
>recent Razor Blade laptops with GPUs.
https://bugzilla.kernel.org/show_bug.cgi?id=205665
I don't think its Xorg but its graphic related? Fully documented here with
screen shot
101 - 192 of 192 matches
Mail list logo