Tried latest desktop image[1]. USB-dw3 is enabled.
Here is the log:
u@tgl:~$ dmesg | grep 3fe
[ 21.103681] pci :00:0d.1: [8086:9a15] type 00 class 0x0c03fe
[ 21.199707] pci :00:14.1: [8086:43ee] type 00 class 0x0c03fe
u@tgl:~$ sudo modprobe dwc3_pci
u@tgl:~$ lspci -v
...
00:0d.1 USB
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/linux-firmware-
staging starting from version 1.187.16+staging.12
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ Qualcomm WCN6856 not supported yet.
+
+ [Fix]
+
+ Upstream fixes in thread
+
No hardware to verify yet, but probably we'll also need this from linux-
firmware:
4adb20b4 QCA: Add Bluetooth firmware for WCN685x
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu Focal)
Importance: Undecided =>
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Impish)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => High
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Importance:
verified on 5.11.0-33-generic
** 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-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1930645
Title:
** Tags added: originate-from-1931664
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1940204
Title:
AMDGPU: Fix System hang after resume from suspend
Status in HWE Next:
New
** 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-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1936296
Title:
Fix display output on HP
The nouveau driver has never been well supported. It remains buggy for
years even for old hardware so the outlook is not great there. If you
would like to debug the nouveau driver then it lives in the Linux kernel
at:
** Description changed:
This report is related to a problem reported in IRC #ubuntu whereby
(Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot
time but can later.
Appears to be a race condition between the wifi chipset setting up the
device and enabling the
Public bug reported:
This report is related to a problem reported in IRC #ubuntu whereby
(Intel 8260 Wifi) Bluetooth device cannot load its firmware file at boot
time but can later.
Appears to be a race condition between the wifi chipset setting up the
device and enabling the attached USB
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
** Package changed: zfs-linux (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/1940083
Title:
zfs send encrypt causes kernel NULL pointer dereference
Status in
Attaching the "make.log" from the first error message.
** Attachment added: "make.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939460/+attachment/5518597/+files/make.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Thanks for the response. Executed the command "sudo dpkg -i *.deb" again
to follow any issues with the module install. There seamse to be some
issue with the installation related to the nvidia? Any sugestions?
Adding a screenshot from running the command above.
** Attachment added: "Error
What about Hiruse?
Bluetooth does not work for me, I'm using Hirsute + linux 5.14 RC6.
mario@Asus-Ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 21.04
Release: 21.04
Codename: hirsute
mario@Asus-Ubuntu:~$
Can we get a fix after over a year now? I think we have enough people
suffering to deserve a fix for this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe in Ubuntu.
https://bugs.launchpad.net/bugs/1878279
Title:
Bluetooth does not work for me, I'm using Hirsute + linux 5.14 RC6.
mario@Asus-Ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 21.04
Release:21.04
Codename: hirsute
mario@Asus-Ubuntu:~$
Hi Daniel, thanks for your quick reply. Do you mean the nouveau driver
is abandoned, or just doesn't have much activity lately?
Rolling back to an old kernel version (and Ubuntu distro) really feels
like a failure. I'd be happy to try to debug the nouveau driver,
although it sounds like I'm on my
I no longer have access to the hardware. So, I - the original reporter -
cannot verify the fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1934557
Title:
Backlight (screen
Hi Marcelo,
Thank you for following up on this.
Unfortunately, even with the 5.11 kernel the problem still exists.
--
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/1933388
Title:
Public bug reported:
Hello,
the touchpad of the Toshiba Portege z10t-a is not detected at all by the linux
kernel (linux 5.11).
It can't be found in /proc/bus/input/devices nor trough xinput.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-25-generic 5.11.0-25.27
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450 in
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Thx 'fran...@de.ibm.com' for the verification!
--
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/1933173
Title:
[21.10 FEAT] KVM: Provide a secure guest indication
Status in Ubuntu on IBM
--- Comment From fran...@de.ibm.com 2021-08-17 11:34 EDT---
Enabled proposed on a 21.04 host and updated the kernel to "5.11.0-33-generic
#35-Ubuntu"
If PV is disabled both prot_virt_* files show 0.
If PV is enabled prot_virt_host shows 1 and prot_virt_guest shows 0.
If queried on a
@65
tbh I haven't analyzed what you've offered, but a quick glance over your post
*and* knowing what *I've* done to get it working tells me that no, it's not the
same. What I've done barely breaks into the usual workflow of installing the
image/headers from mainline and building the out-of-tree
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 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 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 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 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
I started seeing the issues that Sergio mentioned lately as well. I
think this was caused by the recent automatic move from 5.8 to 5.11. I
had the oem kernel installed (20.04 install) but then apt recently moved
me to the hwe-5.8 kernel. More recently apt pulled in hwe-5.11 and I
believe that is
Does the problem happen when using the 5.11 provided by linux-azure-
edge? This kernel can be installed with `apt-get install linux-azure-
edge`.
The 5.11 kernel is scheduled to become the default linux-azure kernel
soon.
--
You received this bug notification because you are a member of Kernel
** Changed in: linux-azure (Ubuntu)
Status: New => Invalid
--
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/1904632
Title:
Ubuntu 18.04 Azure VM host kernel panic
Status in
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1937056
Title:
Touchpad not working with
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1934557
Title:
Backlight (screen brightness) on
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1936708
Title:
Wobbly graphics on built-in
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1940085
Title:
Sync drivers/gpu/drm from v5.14
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Groovy)
Status: New => Invalid
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
** Changed in: linux-azure (Ubuntu)
Status: New => Fix Released
--
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/1927438
Title:
Commits To Fix Kdump Failures
Status in
** Changed in: linux-oem-5.13 (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1921345
Title:
Support MIPI camera
>From the warnings, this seems to be happening again on 20.04 with the
latest HWE kernel (5.11) and i915 related firmware files.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
the pci-id is included by bug 1940085, but further fixes are still
necessary
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939844
Title:
Intel GT2 ID[8086:46A0] is required
** Changed in: linux-oem-5.13 (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.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1940204
Title:
AMDGPU: Fix System hang
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
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/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks
Hi,
I am having the same issue, with a TP Link Archer Tx50e (which uses
Intel AX200). On boot logs:
[8.084096] Bluetooth: hci0: command 0xfc05 tx timeout
[8.084101] Bluetooth: hci0: Reading Intel version information failed (-110)
[8.084110] Bluetooth: hci0: Intel Read version failed
** Tags added: hirsute impish patch
--
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/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load
As per our discussion, this is fixed in LP: #1939673
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: New => Fix Committed
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in:
The suspend/resume does not seem to make any difference, and I cannot see
the device listed in dmesg. The BIOS for this device doesn't appear to have
an advanced mode, but if it helps the device is only capable of UEFI
booting, so ubermix has been installed as UEFI.
Attached is the output of the
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1940285
Title:
Laptop screen flickering on kernels above 5.4 (not included)
I should especifice also that my laptop (Teclast F7) uses an Intel
Celeron n3450
--
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/1940285
Title:
Laptop screen flickering on kernels above
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1940285
When reporting bugs in the future please use apport by using 'ubuntu-
I had to select a package. Since I have read that problems regarding the
kernel should be listed as "linux" (and I think this is the case), that
is why I selected that package.
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
You have been subscribed to a public bug:
Recently, I installed Ubuntu 21.04 on my laptop and I was having the
same problem I had like with others distros such as Fedora; for some
reason, the screen just ramdonly and briefly turns off, (more like a
flickering) and it also "autoregulates" a the
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1940204
Title:
AMDGPU: Fix System hang after resume from
** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1940134
Title:
fails to launch linux L2 guests on AMD
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: linux-oem-5.6 (Ubuntu Focal)
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-5.13
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1929027
Title:
drm/i915: Drop
Hi @chaoqin,
I can't find the device "8086:4b7e", I have also tried the mainline
kernel v5.14-rc6 but no luck.
I also tried to boot into the UEFI shell and use the 'pci' command to
list the devices, but still no luck. [1]
Do I need to enable some settings in BIOS so that I can see the device
** Tags added: xe
--
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/1866591
Title:
vmx_pending_event_test failed in ubuntu_kvm_unit_tests
Status in ubuntu-kernel-tests:
Triaged
Status
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-oracle (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/1866591
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/1917616
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/1923284
** Tags added: hinted
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1853797
Title:
pmu in ubuntu_kvm_unit_tests fails
Status in ubuntu-kernel-tests:
Triaged
Status in
Found on xenial/linux-oracle/4.15.0-1079.87~16.04.1 and xenial/linux-
oracle/4.15.0-1077.85~16.04.1 (Oracle instances).
** Tags added: 4.15 sru-20210719 xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
** Attachment added: "Full log"
https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1940261/+attachment/5518481/+files/sru-oracle-oracle-VM.Standard2.1-ubuntu_seccomp-log.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The attachment is what I got from nvidia-driver-[460,470], please see
the diff[1].
[1]
$ diff nvidia-4*
1,1345c1
< Modaliases: nvidia(pci:v10DEd0FD2sv*sd*bc03sc*i*
< pci:v10DEd1028sv*sd*bc03sc*i*
< pci:v10DEd0595sv*sd*bc03sc*i*
< pci:v10DEd0FD2sv*sd*bc03sc*i*
<
** Attachment added: "nvidia-460-modalias"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1940262/+attachment/5518462/+files/nvidia-460-modalias
** Tags added: oem-priority originate-from-1940264 sutton
** Changed in: oem-priority
Assignee: (unassigned) =>
Public bug reported:
There are many modalias be removed from 470 those supporting in 460.
If 470 is a LTS version and 460 will be transited to 470 then the driver
installing will have different behavior between both version.
** Affects: oem-priority
Importance: High
Assignee:
Public bug reported:
Xenial/Oracle 4.15.0-1079.87~16.04.1 fails 11-basic-basic_errors test
from ubuntu_seccomp on all Oracle cloud instances:
batch name: 11-basic-basic_errors
test mode: c
test type: basic
Test 11-basic-basic_errors%%001-1 result: FAILURE 11-basic-basic_errors
rc=255
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.57.02-0ubuntu0.18.04.3
---
nvidia-graphics-drivers-470-server (470.57.02-0ubuntu0.18.04.3) bionic;
urgency=medium
* debian/nvidia_supported,
debian/rules (LP: #1939673):
- Use the json database file
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.57.02-0ubuntu0.20.04.3
---
nvidia-graphics-drivers-470-server (470.57.02-0ubuntu0.20.04.3) focal;
urgency=medium
* debian/nvidia_supported,
debian/rules (LP: #1939673):
- Use the json database file
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.57.02-0ubuntu0.21.04.3
---
nvidia-graphics-drivers-470-server (470.57.02-0ubuntu0.21.04.3) hirsute;
urgency=medium
* debian/nvidia_supported,
debian/rules (LP: #1939673):
- Use the json database
** Description changed:
[Impact]
We need to support new hardware from AMD and Intel, but backporting support
to oem-5.13 is very laborous and prone to errors.
[Fix]
- There only sane way to add a better base for the new hw is by syncing the
whole drivers/gpu/drm directory from current
Possible duplicate of this bug:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1934652
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1927211
Title:
Public bug reported:
Here is a kernel bug. I attached the error log.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
** Attachment added: "error1.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1940225/+attachment/5518381/+files/error1.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package linux-firmware - 1.187.16
---
linux-firmware (1.187.16) focal; urgency=medium
* Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi
firmware crash under iperf stress tests: Microcode SW error detected.
Restarting 0x0
This bug was fixed in the package linux-firmware - 1.187.16
---
linux-firmware (1.187.16) focal; urgency=medium
* Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi
firmware crash under iperf stress tests: Microcode SW error detected.
Restarting 0x0
This bug was fixed in the package linux-firmware - 1.187.16
---
linux-firmware (1.187.16) focal; urgency=medium
* Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi
firmware crash under iperf stress tests: Microcode SW error detected.
Restarting 0x0
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package linux-firmware - 1.187.16
---
linux-firmware (1.187.16) focal; urgency=medium
* Intel Killer(R) Wi-Fi 6 AX1650i [8086:a0f0] Subsystem [1a56:1651]: iwlwifi
firmware crash under iperf stress tests: Microcode SW error detected.
Restarting 0x0
1 - 100 of 111 matches
Mail list logo
