** Attachment added: "dmesg-5.13rc4-rtw88-aspm.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+attachment/5502051/+files/dmesg-5.13rc4-rtw88-aspm.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Setting /etc/modprobe.d/rtw88_pci.conf to contain
options rtw88_pci disable_aspm=1
seems to have worked: no freeze. To confirm the setting:
psz@ollee:~$ grep . /sys/module/rtw88_pci/parameters/*
/sys/module/rtw88_pci/parameters/disable_aspm:Y
** 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/1920180
Title:
Can't detect intel wifi 6235
Status in
Verified on 5.11.0-19 kernel.
replug typec after suspend, external monitor works fine.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: hwe-networking-wifi ihv-qualcomm
--
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/1930637
Title:
ath11k WIFI not working in proposed kernel 5.11.0-19-generic
Status in
All autopkgtests for the newly accepted linux-meta-hwe-5.8
(5.8.0.54.61~20.04.38) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (arm64, s390x, armhf, ppc64el)
Hi Chris,
Thanks for reporting! Looking at the difference between
4.15.0-142-generic and 4.15.0-143-generic, there is one commit:
ubuntu-bionic$ git log --grep "cifs"
Ubuntu-4.15.0-142.146..Ubuntu-4.15.0-143.147
commit 7dd995facbb57b35b10715a27e252c8af5a39a6c
Author: Shyam Prasad N
Date:
@Marian,
After read the https://github.com/thesofproject/linux/issues/2700, looks
like the kernel 5.11 couldn't work on your machine. So please use the
5.13 kernel built on your won, and wait for the mainline build kernel to
merge this kconfig fix.
And for the sof-firmware and alsa-ucm-conf,
Installed the proposed kernel on a TGL machine, the i915 driver doesn't
load, the analogue audio works as expected.
** 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
A big Thank You Hui Wang, it is working now!
--
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/1924685
Title:
No sound output/input available after installing 21.04
Status in OEM Priority
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
My propose method is to fix ASPM issue by driver instead.
So, don't apply "pcie_aspm=force pcie_aspm.policy=performance" to kernel
parameter, but
add a file /etc/modprobe.d/rtw88_pci.conf with below content
options rtw88_pci disable_aspm=1
(Sorry, disable_aspm=0 in #17 is typo)
Then,
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
P8 (node dryden) works with B-4.15 and F-5.4.
G-5.8 failed with bug 1930646
I think we can close this bug now.
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Do you mean to use disable_aspm=0 as kernel parameter, instead of
previous "pcie_aspm=force pcie_aspm.policy=performance"? OK, will try.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
To answer your question: My kernel was compiled 5.13-rc2.
I have a messed up system now. I enabled hirsute-proposed repository and
upgraded all the packages I could. Now even the kernel 5.13-rc2 does not work
for me with the audio on speakers (it works on audio jack headset). Non-kernel
Installed the proposed kernel on a lenovo TGL with 4k panel, the issue
is fixed.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
[Impact]
After hot-plug the Ethernet cable, the status of Ethernet is always down.
[Fix]
Because ASPM is enabled on RTL8106E, the link change interrupt can't be fired
immediately.
Need to wait a long time to get the link change interrupt.
Introduce a
Public bug reported:
[Impact]
After hot-plug the Ethernet cable, the status of Ethernet is always down.
[Fix]
Because ASPM is enabled on RTL8106E, the link change interrupt can't be fired
immediately.
Need to wait a long time to get the link change interrupt.
Introduce a polling method to watch
Thanks again. Next time the problem happens in 21.04 please don't reboot
yet, wait at least 10 seconds before rebooting. Then after rebooting,
run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
**
Installed the proposed kernel 5.11.0-19 on the Dell Latitude 9520, the
audio works.
[0.00] Linux version 5.11.0-19-generic (buildd@lcy01-amd64-025) (gcc
(Ubuntu 10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1)
#20-Ubuntu SMP Tue Jun 1 10:51:47 UTC 2021 (Ubuntu
@Marian,
You mentioned you built working kernel yourself, is it based on 5.11
kernel or 5.13 kernel? I guess your machine has the soundwire SDCA
design, we plan to support the soundwire SDCA audio design in the impish
(5.13) kernel.
--
You received this bug notification because you are a member
Finally I updated to 21.04 but the problem persists.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1930275
Title:
[nvidia] System does not wake up after suspend
Hi, the proposed kernel is ready, you could install the kernel of
5.11.0-19 to verify, this kernel merged the fix of this bug.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/comments/28
--
You received this bug notification because you are a member of Kernel
Packages, which is
ubuntu kernel hirsute-proposed 5.11.0-19 does not work. I believe
backporting patches to such an old kernel was a mistake. You should have
consulted Pierre-Louis Bossart https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/+attachment/5501988/+files/dmesg.5.11.0-19
--
You received this
Could you please try disable_aspm=0 when loading rtw88_pci.ko?
If it works, we may add a quirk in driver by vendor and product name.
--
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/1927808
@Eduard,
thanks for your verification.
@Marian Klein,
I will verify the proposed kernel. And about the fix in mainline build
kernel (like v5.13-rc4), need to wait for a while, the process is the
fix is merged in impish first, then the mainline build kernel will get
the fix from impish kernel.
ubuntu linux kernel 5.11.0-19 form hirsute-proposed branch did not work
for me for the audio
marian@HPSpectre:/boot$ cat
/etc/apt/sources.list.d/ubuntu-hirsute-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubuntu.com/ubuntu/ hirsute-proposed restricted main
multiverse
Problem is still not fixed for
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc4/
Config variable still does not appear for 5.13-rc4
marian@HPSpectre:/boot$ cat config-5.13.0-051300rc4-generic | grep
CONFIG_SND_SOC_INTEL_SOUNDWIRE
--
You received this bug notification because you are a
Public bug reported:
See these references for more information:
- https://bugzilla.kernel.org/show_bug.cgi?id=213055
- https://bugs.archlinux.org/task/70849
Can you please prevent this already fixed bug from being introduced any further
into Ubuntu.
Thanks.
** Affects: linux (Ubuntu)
Alright, I also tested the proposed 5.11.0-19-generic now.
SoundWire does work on this kernel.
So that part is OK.
BUT
Recently a new bug has been introduced with the ath11k driver, that my machine
also uses.
It seems that we are now going to introduce this same bug on Ubuntu if this
kernel
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
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/1920180
Title:
Can't detect intel wifi 6235
Status
Hi, I am lucky that I am reading the verification request now.
Yesterday I tried this one by manual dpkg-install:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc4/amd64/
Was this build supposed to have the fix included as well? Because for me
sound still did not work.
--
You received
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag
Who is supposed to test it? Is it me as a reporter?
I reported the problem to make ubuntu aware of it and I expected ubuntu to pick
it up and to sort it out by themselves. I do not accept any further
"responsibility" on this, including testing.
I compiled a kernel manually myself , so I have a
Public bug reported:
Microsoft would like to request inclusion of the following patch in the
5.4 and later kernels:
a81a38cc6dda ("scsi: storvsc: Parameterize number hardware queues")
Public bug reported:
My raspberry pi 4 running Ubuntu 20.04 server is constantly having trouble the
the usb controller.
I have 2 externally powered USB hubs connected that have a few HDDs plugged in.
After a seemingly random amount of time (between 1 minute and 2 days)
the usb controller will
** Package changed: 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/1930610
Title:
Upgrade fails to boot with kernel 5.4
Status in linux package in Ubuntu:
You have been subscribed to a public bug:
I tried to upgrade an Ubuntu 18.04 to 20.04 two weeks ago. The system is
a server type installation running as a virtual machine on Hyper-V,
primarily running letsencrypt and nginx.
Actually I tried twice, both upgrades left me with a system that doesn´t
Verified fixes work in Hirsute as well using above method.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1029.30
---
linux-oem-5.10 (5.10.0-1029.30) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1029.30 -proposed tracker (LP:
#1930076)
* CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
-
This bug was fixed in the package linux-kvm - 5.4.0-1040.41
---
linux-kvm (5.4.0-1040.41) focal; urgency=medium
* focal/linux-kvm: 5.4.0-1040.41 -proposed tracker (LP: #1927609)
* Make vfio-pci built-in or xhci_hcd optional (LP: #1770845)
- [Config]: kvm: CONFIG_VFIO=n
*
This bug was fixed in the package linux-raspi - 5.11.0-1009.10
---
linux-raspi (5.11.0-1009.10) hirsute; urgency=medium
* hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
* Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi:
This bug was fixed in the package linux-raspi - 5.11.0-1009.10
---
linux-raspi (5.11.0-1009.10) hirsute; urgency=medium
* hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
* Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi:
This bug was fixed in the package linux-kvm - 5.4.0-1040.41
---
linux-kvm (5.4.0-1040.41) focal; urgency=medium
* focal/linux-kvm: 5.4.0-1040.41 -proposed tracker (LP: #1927609)
* Make vfio-pci built-in or xhci_hcd optional (LP: #1770845)
- [Config]: kvm: CONFIG_VFIO=n
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1029.30
---
linux-oem-5.10 (5.10.0-1029.30) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1029.30 -proposed tracker (LP:
#1930076)
* CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1029.30
---
linux-oem-5.10 (5.10.0-1029.30) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1029.30 -proposed tracker (LP:
#1930076)
* CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1029.30
---
linux-oem-5.10 (5.10.0-1029.30) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1029.30 -proposed tracker (LP:
#1930076)
* CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
-
This bug was fixed in the package linux-raspi - 5.11.0-1009.10
---
linux-raspi (5.11.0-1009.10) hirsute; urgency=medium
* hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
* Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi:
This bug was fixed in the package linux-raspi - 5.11.0-1009.10
---
linux-raspi (5.11.0-1009.10) hirsute; urgency=medium
* hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
* Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi:
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1029.30
---
linux-oem-5.10 (5.10.0-1029.30) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1029.30 -proposed tracker (LP:
#1930076)
* CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1029.30
---
linux-oem-5.10 (5.10.0-1029.30) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1029.30 -proposed tracker (LP:
#1930076)
* CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1029.30
---
linux-oem-5.10 (5.10.0-1029.30) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1029.30 -proposed tracker (LP:
#1930076)
* CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1029.30
---
linux-oem-5.10 (5.10.0-1029.30) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1029.30 -proposed tracker (LP:
#1930076)
* CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
-
This bug was fixed in the package linux-raspi - 5.11.0-1009.10
---
linux-raspi (5.11.0-1009.10) hirsute; urgency=medium
* hirsute/linux-raspi: 5.11.0-1009.10 -proposed tracker (LP: #1927572)
* Hirsute update: v5.11.16 upstream stable release (LP: #1926999)
- [Config] raspi:
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1029.30
---
linux-oem-5.10 (5.10.0-1029.30) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1029.30 -proposed tracker (LP:
#1930076)
* CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1029.30
---
linux-oem-5.10 (5.10.0-1029.30) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1029.30 -proposed tracker (LP:
#1930076)
* CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1029.30
---
linux-oem-5.10 (5.10.0-1029.30) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1029.30 -proposed tracker (LP:
#1930076)
* CVE-2021-33200
- bpf: Wrap aux data inside bpf_sanitize_info container
-
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux - 5.4.0-74.83
---
linux (5.4.0-74.83) focal; urgency=medium
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions --
This bug was fixed in the package linux-gcp - 5.4.0-1044.47
---
linux-gcp (5.4.0-1044.47) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1044.47 -proposed tracker (LP: #1927603)
* Enable BLK_DEV_NVME =y to support "shielded VM minimal images"
(LP: #1927050)
- [config]
This bug was fixed in the package linux-azure - 5.4.0-1048.50
---
linux-azure (5.4.0-1048.50) focal; urgency=medium
* focal/linux-azure: 5.4.0-1048.50 -proposed tracker (LP: #1927598)
* Fix kdump failures (LP: #1927518)
- video: hyperv_fb: Add ratelimit on error message
This bug was fixed in the package linux-aws - 5.4.0-1049.51
---
linux-aws (5.4.0-1049.51) focal; urgency=medium
* focal/linux-aws: 5.4.0-1049.51 -proposed tracker (LP: #1927595)
* Packaging resync (LP: #1786013)
- update dkms package versions
* AWS: out of entropy on
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.80-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-460 (460.80-0ubuntu0.20.04.2) focal; urgency=medium
* debian/additional_card_ids:
- Add new IDs:
1FB1 (Nvidia T600)
2231 (Nvidia RTX A5000)
24B7
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.80-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-460 (460.80-0ubuntu0.20.04.2) focal; urgency=medium
* debian/additional_card_ids:
- Add new IDs:
1FB1 (Nvidia T600)
2231 (Nvidia RTX A5000)
24B7
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.119.04-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-450-server (450.119.04-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/templates/{dkms_nvidia.conf.in|dkms.conf.fragment.in}:
- Remove block on uvm
This bug was fixed in the package nvidia-graphics-drivers-465 -
465.27-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-465 (465.27-0ubuntu0.20.04.2) focal; urgency=medium
* debian/templates/dkms.conf.fragment.in:
- Install the nvidia-peermem module.
*
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
1 - 100 of 158 matches
Mail list logo
