** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2099914
[Impact]
This is CVE-2025-2312, where namespace confusion by cifs.upcall may lead to
disclosing sensitive data from the host or container Kerberos credentials
cache
by accessing the wrong credential cache tha
Verified on MCU13X-PV-SKU3x which has ALC3315 + CS amplifier with linux-
oem-6.11/6.11.0-1019.19 , the LED/Mic Mute LED works as expected.
** Tags removed: verification-needed-noble-linux-oem-6.11
** Tags added: verification-done-noble-linux-oem-6.11
--
You received this bug notification because
It might have been OK because usually shorter is better. Shorter cables
have less signal degradation and maintain higher bandwidth more
reliably.
I recently experimented with a 4K@240Hz monitor and found [a very short
cable](https://www.amazon.com.au/dp/B0D815GV9K) was able to maintain a
stable hi
** Summary changed:
- cifs.upcall program in cifs-utils package incorrectly makes an upcall to
different namespace in case of container environments
+ CVE-2025-2312 cifs.upcall could access incorrect kerberos credentials cache
** Description changed:
- In some cases, the cifs.upcall program fro
** Description changed:
[Impact]
No audio input/output for cs42l43 and cs35l56 on Intel LNL of ThinkPad.
[Fix]
Add the firmware of cs35l56 and sof-lnl-cs42l43-l0-2ch.tplg
to enable audio support;
update alsa-ucm-conf to gain the control of mic/speaker mute LED.
linux-fimware co
** Tags added: delta jira-delta-195 oem-priority
--
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/2103480
Title:
System could not hit hardware sleep state with specific panel with AMD
KR
Public bug reported:
I have an Epyc Genoa system that won't boot with either the 6.14.0 or
6.14.1 kernels without mce=off. The system is only a few months old, and
has run without issue on all kernels up to the most recent 6.13.10
release. Starting with kernel 6.14.0, the system is unable to boot,
Tested following intel recommandation to run Qwen/Qwen2-7B model in LNL based
on
https://docs.openvino.ai/2024/learn-openvino/llm_inference_guide/genai-guide-npu.html
using latest Linux NPU driver -
https://github.com/intel/linux-npu-driver/releases/tag/v1.10.1
:
$ uname -a
Linux tucano-806928
Public bug reported:
[Impact]
[Fix]
[Test]
[Where problems could occur]
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Assigne
** Changed in: linux-nvidia-tegra (Ubuntu)
Status: New => Fix Released
** Changed in: linux-nvidia-tegra (Ubuntu Noble)
Status: New => Fix Released
** Tags removed: verification-needed-noble-linux-nvidia-tegra
** Tags added: verification-done-noble-linux-nvidia-tegra
--
You receiv
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe-6.11 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.11 in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870335/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870336/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launch
** Changed in: linux-nvidia-tegra (Ubuntu)
Status: New => Fix Released
** Changed in: linux-nvidia-tegra (Ubuntu Noble)
Status: New => Fix Released
** Tags removed: verification-needed-noble-linux-nvidia-tegra
** Tags added: verification-done-noble-linux-nvidia-tegra
--
You receiv
I see a similar error with noble:linux-nvidia-tegra 6.8.0-1004.4 and
noble:linux-nvidia-tegra-pvw 6.8.0-1005.5 on Jetson AGX Orin. I've
attached the serial log with noble:linux-nvidia-tegra 6.8.0-1004.4
** Attachment added: "agx_noble-nvidia-tegra_rtnetlink-panic.log"
https://bugs.launchpad.ne
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870333/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/
So the files are there but you're still seeing errors?
Try to `rmmod amdxdna` and `modprobe amdxdna`.
If that works I suspect that what's going on is it got loaded into the
initramfs but was missing firmware in the initramfs.
Maybe this commit is missing in your kernel.
https://github.com/torva
Will mark is verification done but this kernel does not have the coresight
module that is needed for this issue.
root@localhost:~# uname -r
6.8.0-1014-azure-nvidia
root@localhost:~# modprobe coresight_etm4x
modprobe: FATAL: Module coresight_etm4x not found in directory
/lib/modules/6.8.0-1014-az
fixed upstream in 2.2, which is in noble and up
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1718761
Title
Sorry about that, here's some more info:
The regression from LP #2096979 [1] only appears on Noble and later, so
there is no new package version for Jammy and lower.
[Tested versions (0ubuntu1)]
trusty 2024.10.07-0ubuntu1~14.04.1
xenial 2024.10.07-0ubuntu1~16.04.1
bionic 2024.10.07-0ubuntu1~18.0
Verified:
root@localhost:~# dmesg | grep realloc
[0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[5.402889] DMA: preallocated 131072 KiB GFP_KERNEL pool for atomic
allocations
[5.411821] DMA: preallocated 131072 KiB GFP_KERNEL|GFP_DMA pool for atomic
allocations
[5.42156
fixed in plucky
** Changed in: zfs-linux (Ubuntu)
Status: Triaged => Fix Released
--
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/2089324
Title:
memcpy: detected field-spanning wr
Note to others facing issues with install auto-gptq for NPU hardware:
BUILD_CUDA_EXT=0 pip install auto-gptq
** Tags removed: verification-needed-noble-linux
verification-needed-oracular-linux
** Tags added: verification-done-noble-linux verification-done-oracular-linux
--
You received this bu
Apologies for forgetting the version for the verification here, here's
what I did:
[Tested versions]
noble 2024.10.07-0ubuntu2~24.04.1
oracular 2024.10.07-0ubuntu2~24.10.1
plucky 2024.10.07-0ubuntu2
Installed package without errors on a baremetal device running the
classic release. iw reg get/se
Should this be going into Plucky (25.04) too ?
That has 20250317.git1d4c88ee-0ubuntu1 which you'd think is more recent,
but I do not see the files in /usr/lib/firmware/amdgpu, and my Framework
13" AMD also errors
```
Apr 06 07:42:44 frame kernel: amdxdna :c2:00.1: Direct firmware load for
am
Public bug reported:
Description of the problem
While in the middle of a copy the network interface (which uses the r8169
driver) went offline. Downing and then upping the interface restored
connectivity.
Steps to reproduce:
1. Check out a large subversion repository over HTTPS?
Expected resul
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870341/+files/WifiSyslog.txt
** No longer affects: linux-oem-6.11 (Ubuntu)
** Also affects: vision-drivers (Ubuntu Plucky)
Importance: Undecided
Status: New
** Changed in:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870338/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870340/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870332/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870339/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870328/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.laun
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870331/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870329/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870326/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870330/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
kernel: PM: suspend entry (s2idle)
kernel: Filesystems sync: 0.007 seconds
kernel: Freezing user space processes
kernel: Freezing user space processes completed (elapsed 0.001 seconds)
kernel: OOM killer disabled.
kernel: Freezing remaining freezable tasks
kernel: Freezing rem
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/2106502/+attachment/5870327/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/21
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
I was wrong that the issue only affects the nvidia kernel. The recent
kernel linux-image-6.8.0-58 brought it up on the other machine as well.
The last generic kernel was linux-image-6.8.0-52 and it worked OK.
** Also affects: linux-hwe-6.8 (Ubuntu)
Importance: Undecided
Status: New
--
Same issue also on fresh installed Ubuntu 25.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/2091864
Title:
Cannot enter luks password at boot after kernel 6.8.0-50 upgrade
Stat
Sorry, the first affected generic version linux-image-6.8.0-57, not 58.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-nvidia-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2106326
Title:
ip6tables option --set-mark not wo
a new kernel for 25.04 is currently being built in kernel team's
unstable ppa:
--
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/2064321
Title:
Power guest secure boot with key management:
If one of the monitors remains black, you may have to tell it to change
input (to HDMI).
If one of the monitors is flashing, that usually means you've run out of
bandwidth but it was noticed too late. So try fewer monitors or a
different cable.
--
You received this bug notification because you a
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
** Changed in: linux-firmware (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-firmware (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: linux-firmware (Ubuntu Oracular)
Status: In Progress => Fix Committed
** Changed in: linux-firmw
This bug was fixed in the package linux-base - 4.5ubuntu9+24.04.1
---
linux-base (4.5ubuntu9+24.04.1) noble; urgency=medium
* Add missing Apport links for kernel packages (LP: #2018128)
-- Juerg Haefliger Wed, 05 Mar 2025
12:07:36 +0100
** Changed in: linux-base (Ubuntu Noble)
Hi Nayna,
a new kernel for 25.04 is currently being built in kernel team's unstable ppa:
ppa:canonical-kernel-team/unstable
Once the build is complete it will there also be signed with a test/dev key.
It will just take some hours to get it build and signed.
I'll lave another comment when it's com
Public bug reported:
Trying to upgrade from oracular to plucky on zfs root, ended up in an
unhappy place:
```
$ sudo dmesg | grep RIP
[3.457744] ISO 9660 Extensions: RRIP_1991A
[ 13.044222] ISO 9660 Extensions: RRIP_1991A
[ 536.010520] RIP: 0010:zfs_log_remove+0x138/0x150 [zfs]
[ 536.0125
Hi Sitsofe,
The update just released late last week, and should start showing up in
kernel updates in the 2025.04.14 SRU cycle, releasing the week of
12-May.
If you need something sooner than that, you can install the DKMS
package. Assuming you're running the 6.11 HWE kernel on Noble, that
might
Public bug reported:
[SRU Justification]
[Impact]
When migrating to a new hwe kernel or introduced a oem kernel of a newer
version, the firmware blobs might not match the expectation of the new
kernel.
[Fix]
For linux-oem-6.14/noble:
$ debian/scripts/list-lts-update-files \
launchpad/noble
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But
I've just run into this with Ubuntu 24.04.2. As previously mentioned it
was initially fixed in OpenZFS 2.3.0 (the commit that went in for that
tag is
https://github.com/openzfs/zfs/commit/6f50f8e16b7c4a3f1925b41e3d47b479cd7b2d9f
). The fix was also backported to OpenZFS 2.2.7 (the commit for that i
OpenZFS 2.2.7 backport patch to fix "memcpy: detected field-spanning
write" warning.
** Patch added: "zil-flex-2.2.7.patch"
https://bugs.launchpad.net/zfs/+bug/2089324/+attachment/5870271/+files/zil-flex-2.2.7.patch
--
You received this bug notification because you are a member of Kernel
Pac
There are three follow-up fixes for a89c82249c37:
a89c82249c37 PCI: Work around PCIe link training failures
712e49c96706 PCI: Correct error reporting with PCIe failed link retraining
8037ac08c2bb PCI: Clear the LBMS bit after a link retrain
f68dea13405c PCI: Revert to the original speed afte
Thanks for your (once again) detailed answer! Yesterday it worked but this
morning is got even worse! I tried what you said:
- first plugged the hdmi directly on my laptop which apparently didn't
help. Or if I am more explicit: the G9 was well detected and I could select
there right resolution (wit
Hi Daniel van Vugt,
Thanks for pointing out the log.
We have been attempting to load the Mesa [v22.3.5] dependencies provided
by the Imagination team which includes the hardware support changes for
mesa. However, after installing Imagination provided Mesa, GNOME fails
to launch, and we are encoun
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 enco
Adding i915 to /etc/initramfs-tools/modules solved it for me.
--
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/2091864
Title:
Cannot enter luks password at boot after kernel 6.8.0-50 upgra
I fear that might not be enough because your monitor requires closer to
"4K@120Hz" than "4K@60Hz". The 1.8m version has such higher specs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.11 in Ubuntu.
https://bugs.launchpad.net
This bug is awaiting verification that the linux-azure-
nvidia/6.8.0-1014.15 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-noble-linux-azure-nvidia' to
'verification-done-noble-linux
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2106352/+attachment/5870070/+files/Lsusb-t.txt
--
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/2106
Okay I hesitated tbh! I'll change that right now, thanks!
Le mar. 8 avr. 2025, 13:25, Daniel van Vugt <2106...@bugs.launchpad.net> a
écrit :
> I fear that might not be enough because your monitor requires closer to
> "4K@120Hz" than "4K@60Hz". The 1.8m version has such higher specs.
>
> --
> You
There is a third option and it really is what this "ubuntu" bug is meant
to track: Enable Imagination/PVR support for Mesa version 25.x in Ubuntu
25.10.
I can see we have the source code already:
https://salsa.debian.org/xorg-team/lib/mesa/-/tree/ubuntu/src/imagination
So it might just be a matte
Private bug reported:
Description: Netplan static IP configs resetting to default, post reboot
in ubuntu 22.04.5
Version-Release
ubuntu 24.04.5
Error:
-
Netplan static IP configs resetting to default, post reboot in ubuntu 22.04.5
Expected: Netplan static IP configs should retain across
Thank you for your suggestions.
It sounds like you are still using Ubuntu 22.04.
Ans: Yes, logs which we sent from Ubuntu 22.04, also we have verified in 24.04
same error we are getting from GNOME.
Mesa version:
libegl-mesa0/noble-updates,now 24.2.8-1ubuntu1~24.04.1 riscv64
[installed,automati
USB-C to DP bought! I will receive it tomorrow and I'll let you know how it
goes!
=> Here is the one I chose:
https://www.amazon.fr/dp/B0B97GVTN4?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1
I hope I chose well though 😅
On Tue, Apr 8, 2025 at 11:03 AM Lucas Garcia
wrote:
> I will try everything you s
It sounds like you are still using Ubuntu 22.04. Although we would
rather you used Ubuntu 24.04, the very old version of Mesa they are
offering may not work in 24.04.
I think you have two options:
(a) Use Ubuntu 22.04 and force install ALL the Mesa 22.3.5 packages from
Imagination (at the same ti
This SRU just removes the unused code but turn out it doesn't affect the NIC
renaming.
NIC name is usually set by netplan or cloud init, we can safely pick this patch.
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
--
You received this bug notifica
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.11
---
linux-firmware (20240318.git3b128b60-0ubuntu2.11) noble; urgency=medium
* Update new FW for AMD ISP (LP: #2097336)
- amdgpu: Update ISP FW for isp v4.1.1
- amdgpu: Update ISP FW for isp v
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 enco
** Patch added:
"https://lore.kernel.org/all/20250325210450.358506-1-hdego...@redhat.com/";
https://lore.kernel.org/all/20250325210450.358506-1-hdego...@redhat.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.11
---
linux-firmware (20240318.git3b128b60-0ubuntu2.11) noble; urgency=medium
* Update new FW for AMD ISP (LP: #2097336)
- amdgpu: Update ISP FW for isp v4.1.1
- amdgpu: Update ISP FW for isp v
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.11
---
linux-firmware (20240318.git3b128b60-0ubuntu2.11) noble; urgency=medium
* Update new FW for AMD ISP (LP: #2097336)
- amdgpu: Update ISP FW for isp v4.1.1
- amdgpu: Update ISP FW for isp v
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.11
---
linux-firmware (20240318.git3b128b60-0ubuntu2.11) noble; urgency=medium
* Update new FW for AMD ISP (LP: #2097336)
- amdgpu: Update ISP FW for isp v4.1.1
- amdgpu: Update ISP FW for isp v
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.11
---
linux-firmware (20240318.git3b128b60-0ubuntu2.11) noble; urgency=medium
* Update new FW for AMD ISP (LP: #2097336)
- amdgpu: Update ISP FW for isp v4.1.1
- amdgpu: Update ISP FW for isp v
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.11
---
linux-firmware (20240318.git3b128b60-0ubuntu2.11) noble; urgency=medium
* Update new FW for AMD ISP (LP: #2097336)
- amdgpu: Update ISP FW for isp v4.1.1
- amdgpu: Update ISP FW for isp v
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 enco
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 enco
This bug was fixed in the package linux-firmware -
20240913.gita34e7a5f-0ubuntu2.6
---
linux-firmware (20240913.gita34e7a5f-0ubuntu2.6) oracular; urgency=medium
* Update new FW for AMD ISP (LP: #2097336)
- amdgpu: Update ISP FW for isp v4.1.1
* Prevent MT7920 from waking up to
This bug was fixed in the package linux-firmware -
20240913.gita34e7a5f-0ubuntu2.6
---
linux-firmware (20240913.gita34e7a5f-0ubuntu2.6) oracular; urgency=medium
* Update new FW for AMD ISP (LP: #2097336)
- amdgpu: Update ISP FW for isp v4.1.1
* Prevent MT7920 from waking up to
This bug was fixed in the package linux-firmware -
20240913.gita34e7a5f-0ubuntu2.6
---
linux-firmware (20240913.gita34e7a5f-0ubuntu2.6) oracular; urgency=medium
* Update new FW for AMD ISP (LP: #2097336)
- amdgpu: Update ISP FW for isp v4.1.1
* Prevent MT7920 from waking up to
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 enco
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 enco
anson, you should always report the version it was tested with
--
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/2100769
Title:
Update amdgpu FW for GC 11.5.1
Status in HWE Next:
This bug was fixed in the package linux-firmware -
20240913.gita34e7a5f-0ubuntu2.6
---
linux-firmware (20240913.gita34e7a5f-0ubuntu2.6) oracular; urgency=medium
* Update new FW for AMD ISP (LP: #2097336)
- amdgpu: Update ISP FW for isp v4.1.1
* Prevent MT7920 from waking up to
This bug was fixed in the package linux-firmware -
20240913.gita34e7a5f-0ubuntu2.6
---
linux-firmware (20240913.gita34e7a5f-0ubuntu2.6) oracular; urgency=medium
* Update new FW for AMD ISP (LP: #2097336)
- amdgpu: Update ISP FW for isp v4.1.1
* Prevent MT7920 from waking up to
I will try everything you said, thanks for your patience with me on this
frustrating issue!
I'll first try a better DP cable with direct USB-C to DP.
On Tue, Apr 8, 2025 at 11:00 AM Daniel van Vugt <2106...@bugs.launchpad.net>
wrote:
> I understand the frustration with how random the issue is, I'
And I didn't change the cable when it came back
On Tue, Apr 8, 2025 at 10:48 AM Lucas Garcia
wrote:
> The monitor that remained black was the G9, with the DP. Are you telling
> me to switch back to an HDMI cable?
>
> I get that with the monitor flashing but the weird thing is that it
> happened
Public bug reported:
[Impact]
Commit e42aa2100e022 ("ACPI: button: Install notifier for system
events as well") in OEM-6.11 modified the ACPI button behavior to
send `ACPI_BUTTON_NOTIFY_WAKE` events.
This caused a regression on Dell Optiplex 3040 sending `KEY_POWER`
randomly at runtime.
[Fix]
Th
I understand the frustration with how random the issue is, I've been
there before. I can only recommend:
* Avoid docks if you need to drive high bandwidth displays.
* Have other brands of cables on hand to try. Including a direct USB-C to
DisplayPort cable.
* Try fewer monitors.
You should be ab
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Oracular)
Status: New => In Progress
** Changed in: linux (Ubuntu Plucky)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages
There is a followup fix commit
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.11/+bug/2106468
--
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/2101931
Title:
Dell machine cannot wak
The monitor that remained black was the G9, with the DP. Are you telling me
to switch back to an HDMI cable?
I get that with the monitor flashing but the weird thing is that it
happened when there was just one other monitor and it stopped flashing when
I plugged in more monitors (2 instead of only
And now I just turned off my computer for let's say 5min. I turned it on
with only the DP plugged in:
- black screen on the G9
- integrated display flashing
=> I plugged back the hdmi into the dock:
- the G9 now works once more
- the secondary monitor (with hdmi) was being detected but disabled
=
** Description changed:
[ Impact ]
- * For QAT Gen5 (available on Intel GraniteRapids-D Kaseyville platform), the
driver qat_420xx
-fails to load the firmware and this causes QAT device to not work properly
+ * For QAT Gen5 (available on Intel GraniteRapids-D Kaseyville platform), the
** Changed in: linux-firmware (Ubuntu)
Status: New => Fix Released
** Changed in: linux-firmware (Ubuntu Noble)
Status: New => Triaged
** Changed in: linux-firmware (Ubuntu Oracular)
Status: New => Triaged
** Changed in: linux-firmware (Ubuntu)
Status: Fix Released =>
The verification also needs to be re-done, "unblocking proposed since
the fix is in proposed" is not an acceptable way to verify that the bug
is fixed. It needs to include which version was tested and that the
test plan was being followed.
--
You received this bug notification because you are a
All autopkgtests for the newly accepted linux-meta-azure-nvidia (6.8.0-1014.15)
for noble have finished running.
The following regressions have been reported in tests triggered by the package:
dpdk-kmods/unknown (arm64)
Please visit the excuses page listed below and investigate the failures,
p
"BOOT_IMAGE=/boot/vmlinuz-6.14.0-11-generic"
Try update OS. Out is long time 6.14.0-13.
Personally, I haven't had anything like this happen to me even on kernel
version 6.14.0-11 or on 6.11 line.
Or with drivers. Im was using 570.86.x and im using 570.133.07 for now.
But I have an old Nvidia GPU
1 - 100 of 105 matches
Mail list logo
