This bug is awaiting verification that the linux-nvidia/6.8.0-1048.51
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-nvidia' to 'verification-done-
noble-linux-nvidia'. If the problem still exists, change the tag
'verification-needed-noble-linux-nvidia' to 'verification-failed-noble-
linux-nvidia'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-nvidia-v2 verification-needed-noble-linux-nvidia
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142337
Title:
Coresight fails to build on 6.8.0-102 due to missing function and arg
definitions
Status in linux package in Ubuntu:
New
Status in linux-nvidia package in Ubuntu:
Invalid
Status in linux-nvidia-6.8 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-nvidia source package in Jammy:
Invalid
Status in linux-nvidia-6.8 source package in Jammy:
Fix Committed
Status in linux source package in Noble:
Fix Committed
Status in linux-nvidia source package in Noble:
Fix Committed
Status in linux-nvidia-6.8 source package in Noble:
Invalid
Bug description:
SRU Justification:
[Impact]
When CONFIG_CORESIGHT is enabled, noble 6.8.0-102 fails to build with
the following errors:
```
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_init':
drivers/hwtracing/coresight/coresight-catu.c:728:15: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
728 | ret = coresight_init_driver("catu", &catu_driver, &catu_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_exit':
drivers/hwtracing/coresight/coresight-catu.c:736:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
736 | coresight_remove_driver(&catu_driver, &catu_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~~~
| coresight_remove_links
...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function '__tmc_probe':
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: error: 'id' undeclared (first use in this function); did you mean 'fd'?
500 | coresight_get_uci_data(id));
| ^~
| fd
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: note: each undeclared identifier is reported only once for each function it appears in
...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_init':
drivers/hwtracing/coresight/coresight-tmc-core.c:728:16: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
728 | return coresight_init_driver("tmc", &tmc_driver, &tmc_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_exit':
drivers/hwtracing/coresight/coresight-tmc-core.c:733:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
733 | coresight_remove_driver(&tmc_driver, &tmc_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~~~
| coresight_remove_links
...
drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_enable':
drivers/hwtracing/coresight/coresight-tpdm.c:299:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
299 | if (!coresight_take_mode(csdev, mode)) {
| ^~~~~~~~~~~~~~~~~~~
| coresight_make_links
drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_disable':
drivers/hwtracing/coresight/coresight-tpdm.c:345:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
345 | coresight_set_mode(csdev, CS_MODE_DISABLED);
| ^~~~~~~~~~~~~~~~~~
| coresight_get_pid
drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_enable':
drivers/hwtracing/coresight/coresight-dummy.c:26:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
26 | if (!coresight_take_mode(csdev, mode))
| ^~~~~~~~~~~~~~~~~~~
| coresight_make_links
drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_disable':
drivers/hwtracing/coresight/coresight-dummy.c:37:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
37 | coresight_set_mode(csdev, CS_MODE_DISABLED);
| ^~~~~~~~~~~~~~~~~~
| coresight_get_pid
```
These errors are a result of including the following patches in
upstream stable updates, but missing some dependencies from the
original patch sets:
Error description: __tmc_probe:id not defined
Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
Missing commit: 852e9a32058a ("coresight: stm: Extract device name from AMBA pid based table lookup")
3ab210297c31 ("coresight: tmc: Extract device properties from AMBA pid based table lookup")
Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
(https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
Error description: catu,tmc: coresight_{init,remove}_driver not defined
Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
n/linux cf08211db65c ("coresight: catu: Move ACPI support from AMBA driver to platform driver")
Missing commit: 075b7cd7ad7d ("coresight: Add helpers registering/removing both AMBA and platform drivers")
Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
(https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)
Error description: tpdm,dummy: coresight_{set,take}_mode not defined
Break commit: n/linux f30974e15e66 ("Coresight: Set correct cs_mode for TPDM to fix disable issue")
n/linux e76e67682488 ("Coresight: Set correct cs_mode for dummy source to fix disable issue")
Missing commit: d724f65218b9 ("coresight: Add helper for atomically taking the device")
Patch series: "coresight: Separate sysfs and Perf usage and some other cleanups"
(https://lists.infradead.org/pipermail/linux-arm-kernel/2024-January/899269.html)
[Fix]
Revert the break commits.
[Test Plan]
Ensure CONFIG_CORESIGHT and CONFIG_CORESIGHT_CATU are enabled, then
compile test.
[Where problems could occur]
These reverts are technically removing fixes from the tree, which have the
potential to cause behaviour changes or regressions. However, the generic
kernel has never been able to build these coresight features, and thus we have
not observed any examples of the issue the patches intended to fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142337/+subscriptions
пятница
[Bug 2143480] Re: Questing: Failed to query NVIDIA devices
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143480
Title:
Questing: Failed to query NVIDIA devices
Status in linux package in Ubuntu:
New
Bug description:
Nova modules are enabled for questing with the following patchset.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139960
Because of this we nvidia cards are not being recognized. We need to
disable nove_core module.
nvidia-persistenced[9541]: Started (9541)
nvidia-persistenced[9537]: nvidia-persistenced failed to initialize. Check syslog for more details.
nvidia-persistenced[9541]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 122 has read and write permissions for those files.
systemd[1]: nvidia-persistenced.service: Control process exited, code=exited, status=1/FAILURE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143480/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143480
Title:
Questing: Failed to query NVIDIA devices
Status in linux package in Ubuntu:
New
Bug description:
Nova modules are enabled for questing with the following patchset.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139960
Because of this we nvidia cards are not being recognized. We need to
disable nove_core module.
nvidia-persistenced[9541]: Started (9541)
nvidia-persistenced[9537]: nvidia-persistenced failed to initialize. Check syslog for more details.
nvidia-persistenced[9541]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 122 has read and write permissions for those files.
systemd[1]: nvidia-persistenced.service: Control process exited, code=exited, status=1/FAILURE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143480/+subscriptions
[Bug 2131046] Re: CAP_PERFMON insufficient to get perf data
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1107.116~20.04.1 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-linux-
azure-5.15' to 'verification-done-focal-linux-azure-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
azure-5.15' to 'verification-failed-focal-linux-azure-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-azure-5.15-v2 verification-needed-focal-linux-azure-5.15
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2131046
Title:
CAP_PERFMON insufficient to get perf data
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Plucky:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux source package in Resolute:
Fix Released
Bug description:
[ Impact ]
The Ubuntu-specific perf_event_paranoid level 4 introduces an additional
capability check that requires CAP_SYS_ADMIN to access perf events.
However, this check was implemented before CAP_PERFMON was introduced,
and was never updated to recognize the new capability.
CAP_PERFMON was specifically designed to allow performance monitoring
operations without granting the broad privileges of CAP_SYS_ADMIN. The
current implementation forces users to grant CAP_SYS_ADMIN even when
CAP_PERFMON would be sufficient, violating the principle of least
privilege.
The perfmon_capable() helper function checks for either CAP_PERFMON or
CAP_SYS_ADMIN, providing the intended functionality while maintaining
backward compatibility with systems that use CAP_SYS_ADMIN.
This change allows processes with CAP_PERFMON to access perf events when
perf_event_paranoid is set to 4, while still requiring explicit grants
as intended by the stricter paranoid level. Processes with CAP_SYS_ADMIN
continue to work as before.
[ Test Plan ]
Use the following reproducer (with CAP_PERFMON file capabilities) to check
if CAP_SYS_ADMIN is still required.
```
#include <stdio.h>
#include <string.h>
#include <unistd.h>
#include <sys/capability.h>
#include <sys/syscall.h>
#include <sys/types.h>
#include <linux/perf_event.h>
static long perf_event_open(struct perf_event_attr *hw_event, pid_t pid, int cpu, int group_fd, unsigned long flags) {
return syscall(__NR_perf_event_open, hw_event, pid, cpu, group_fd, flags);
}
void print_capabilities(void) {
cap_t capabilities;
char *capabilities_text;
capabilities = cap_get_proc();
if (capabilities == NULL) {
printf("[!] Impossbile to get process capabilities.\n");
return;
}
capabilities_text = cap_to_text(capabilities, NULL);
if (capabilities_text == NULL) {
printf("[!] Impossbile to convert process capabilities.\n");
cap_free(capabilities);
return;
}
printf("[*] Current capabilities: %s\n", capabilities_text);
cap_free(capabilities_text);
cap_free(capabilities);
}
int check_perf_access(const char *event_name, int event_type, int event_config) {
struct perf_event_attr pe;
int fd;
memset(&pe, 0, sizeof(struct perf_event_attr));
pe.type = event_type;
pe.size = sizeof(struct perf_event_attr);
pe.config = event_config;
pe.disabled = 1;
pe.exclude_kernel = 0;
pe.exclude_hv = 1;
fd = perf_event_open(&pe, 0, -1, -1, 0);
if (fd == -1) {
printf("[!] %s: Impossible to open perf event\n", event_name);
return -1;
} else {
printf("[*] %s: Successfully opened perf event\n", event_name);
close(fd);
return 0;
}
}
int main(int argc, char *argv[]) {
int result = 0;
FILE *fp;
int paranoid_level = -2;
fp = fopen("/proc/sys/kernel/perf_event_paranoid", "r");
if (fp) {
if (fscanf(fp, "%d", ¶noid_level) == 1) {
printf("[*] Current perf_event_paranoid level: %d.\n", paranoid_level);
if (paranoid_level == 4) {
printf("[*] This is a custom Ubuntu paranoid level.\n");
}
}
fclose(fp);
} else {
printf("[!] Impossible to perf_event_paranoid level.\n");
}
printf("\n");
print_capabilities();
printf("\n");
result += check_perf_access("CPU_CYCLES", PERF_TYPE_HARDWARE, PERF_COUNT_HW_CPU_CYCLES);
result += check_perf_access("INSTRUCTIONS", PERF_TYPE_HARDWARE, PERF_COUNT_HW_INSTRUCTIONS);
result += check_perf_access("CACHE_REFERENCES", PERF_TYPE_HARDWARE, PERF_COUNT_HW_CACHE_REFERENCES);
printf("\n");
if (result == 0) {
printf("All perf events accessible with current capabilities\n");
} else {
printf("Some events were not accessible with current capabilities\n");
}
}
```
Before the patch:
```
$ ./perf_repro
[*] Current perf_event_paranoid level: 4.
[*] This is a custom Ubuntu paranoid level.
[*] Current capabilities: cap_perfmon=ep
[!] CPU_CYCLES: Impossible to open perf event
[!] INSTRUCTIONS: Impossible to open perf event
[!] CACHE_REFERENCES: Impossible to open perf event
Some events were not accessible with current capabilities
```
After the patch:
```
$ ./perf_repro
[*] Current perf_event_paranoid level: 4.
[*] This is a custom Ubuntu paranoid level.
[*] Current capabilities: cap_perfmon=ep
[*] CPU_CYCLES: Successfully opened perf event
[*] INSTRUCTIONS: Successfully opened perf event
[*] CACHE_REFERENCES: Successfully opened perf event
All perf events accessible with current capabilities
```
[ Regression Potential ]
The regression potential is minimal.
The fix maintains backward compatibility as perfmon_capable() accepts both
CAP_SYS_ADMIN and CAP_PERFMON, ensuring all curently working systems are not impacted by the fix.
No security weakening occurs since CAP_PERFMON was designed for performance monitoring and provides fewer privileges than CAP_SYS_ADMIN.
---
I am trying to run node_exporter without root, with cap_perfmon and --collector.perf as well as --collector.perf.hardware-profilers=CpuCycles,CpuInstr.
Expected behavior: node_exporter exports instructions and cpu cycle metrics
Actual behavior: no perf metrics
version: Ubuntu 6.8.0-87.88-generic 6.8.12
Ubuntu carries a patch that introduces a new security level for perf events: perf_event_paranoid=4
This patch limits calling the perf open syscall to processes with CAP_SYS_ADMIN. This patch is from ~2016.
Example commit for resolute: https://git.launchpad.net/~canonical-
kernel/ubuntu/+source/linux-
aws/+git/resolute/commit/kernel/events/core.c?id=eaa91347f6f8112c5c567f93123bfe3b82bd1593
In 2020 a new capability was introduced, CAP_PERFMON, that should be sufficient for using perf.
The code now checks with perfmon_capable() if the process has CAP_SYS_ADMIN _or_ CAP_PERFMON. I am trying to get cpu hardware metrics with CAP_PERFMON but can't.
Looking at the commit message, timing and effect I think the introduction of CAP_PERFMON was missed
The patch
> + if (perf_paranoid_any() && !capable(CAP_SYS_ADMIN))
> + return -EACCES;
should probably be
> + if (perf_paranoid_any() && !perfmon_capable())
> + return -EACCES;
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-87-generic 6.8.0-87.88
ProcVersionSignature: Ubuntu 6.8.0-87.88-generic 6.8.12
Uname: Linux 6.8.0-87-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: rtreffer 2521 F.... wireplumber
/dev/snd/seq: rtreffer 2519 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Nov 10 21:46:59 2025
InstallationDate: Installed on 2025-11-08 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
IwConfig:
lo no wireless extensions.
enp1s0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 001: Dev 002, If 0, Class=Chip/SmartCard, Driver=[none], 12M
|__ Port 002: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 5000M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 virtio_gpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-87-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
linux-restricted-modules-6.8.0-87-generic N/A
linux-backports-modules-6.8.0-87-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.19
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2025
dmi.bios.release: 0.0
dmi.bios.vendor: Ubuntu distribution of EDK II
dmi.bios.version: 2025.02-8ubuntu3
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-10.1
dmi.modalias: dmi:bvnUbuntudistributionofEDKII:bvr2025.02-8ubuntu3:bd10/08/2025:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-10.1:cvnQEMU:ct1:cvrpc-q35-10.1:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-10.1
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2131046/+subscriptions
azure-5.15/5.15.0-1107.116~20.04.1 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-linux-
azure-5.15' to 'verification-done-focal-linux-azure-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
azure-5.15' to 'verification-failed-focal-linux-azure-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-azure-5.15-v2 verification-needed-focal-linux-azure-5.15
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2131046
Title:
CAP_PERFMON insufficient to get perf data
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Plucky:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux source package in Resolute:
Fix Released
Bug description:
[ Impact ]
The Ubuntu-specific perf_event_paranoid level 4 introduces an additional
capability check that requires CAP_SYS_ADMIN to access perf events.
However, this check was implemented before CAP_PERFMON was introduced,
and was never updated to recognize the new capability.
CAP_PERFMON was specifically designed to allow performance monitoring
operations without granting the broad privileges of CAP_SYS_ADMIN. The
current implementation forces users to grant CAP_SYS_ADMIN even when
CAP_PERFMON would be sufficient, violating the principle of least
privilege.
The perfmon_capable() helper function checks for either CAP_PERFMON or
CAP_SYS_ADMIN, providing the intended functionality while maintaining
backward compatibility with systems that use CAP_SYS_ADMIN.
This change allows processes with CAP_PERFMON to access perf events when
perf_event_paranoid is set to 4, while still requiring explicit grants
as intended by the stricter paranoid level. Processes with CAP_SYS_ADMIN
continue to work as before.
[ Test Plan ]
Use the following reproducer (with CAP_PERFMON file capabilities) to check
if CAP_SYS_ADMIN is still required.
```
#include <stdio.h>
#include <string.h>
#include <unistd.h>
#include <sys/capability.h>
#include <sys/syscall.h>
#include <sys/types.h>
#include <linux/perf_event.h>
static long perf_event_open(struct perf_event_attr *hw_event, pid_t pid, int cpu, int group_fd, unsigned long flags) {
return syscall(__NR_perf_event_open, hw_event, pid, cpu, group_fd, flags);
}
void print_capabilities(void) {
cap_t capabilities;
char *capabilities_text;
capabilities = cap_get_proc();
if (capabilities == NULL) {
printf("[!] Impossbile to get process capabilities.\n");
return;
}
capabilities_text = cap_to_text(capabilities, NULL);
if (capabilities_text == NULL) {
printf("[!] Impossbile to convert process capabilities.\n");
cap_free(capabilities);
return;
}
printf("[*] Current capabilities: %s\n", capabilities_text);
cap_free(capabilities_text);
cap_free(capabilities);
}
int check_perf_access(const char *event_name, int event_type, int event_config) {
struct perf_event_attr pe;
int fd;
memset(&pe, 0, sizeof(struct perf_event_attr));
pe.type = event_type;
pe.size = sizeof(struct perf_event_attr);
pe.config = event_config;
pe.disabled = 1;
pe.exclude_kernel = 0;
pe.exclude_hv = 1;
fd = perf_event_open(&pe, 0, -1, -1, 0);
if (fd == -1) {
printf("[!] %s: Impossible to open perf event\n", event_name);
return -1;
} else {
printf("[*] %s: Successfully opened perf event\n", event_name);
close(fd);
return 0;
}
}
int main(int argc, char *argv[]) {
int result = 0;
FILE *fp;
int paranoid_level = -2;
fp = fopen("/proc/sys/kernel/perf_event_paranoid", "r");
if (fp) {
if (fscanf(fp, "%d", ¶noid_level) == 1) {
printf("[*] Current perf_event_paranoid level: %d.\n", paranoid_level);
if (paranoid_level == 4) {
printf("[*] This is a custom Ubuntu paranoid level.\n");
}
}
fclose(fp);
} else {
printf("[!] Impossible to perf_event_paranoid level.\n");
}
printf("\n");
print_capabilities();
printf("\n");
result += check_perf_access("CPU_CYCLES", PERF_TYPE_HARDWARE, PERF_COUNT_HW_CPU_CYCLES);
result += check_perf_access("INSTRUCTIONS", PERF_TYPE_HARDWARE, PERF_COUNT_HW_INSTRUCTIONS);
result += check_perf_access("CACHE_REFERENCES", PERF_TYPE_HARDWARE, PERF_COUNT_HW_CACHE_REFERENCES);
printf("\n");
if (result == 0) {
printf("All perf events accessible with current capabilities\n");
} else {
printf("Some events were not accessible with current capabilities\n");
}
}
```
Before the patch:
```
$ ./perf_repro
[*] Current perf_event_paranoid level: 4.
[*] This is a custom Ubuntu paranoid level.
[*] Current capabilities: cap_perfmon=ep
[!] CPU_CYCLES: Impossible to open perf event
[!] INSTRUCTIONS: Impossible to open perf event
[!] CACHE_REFERENCES: Impossible to open perf event
Some events were not accessible with current capabilities
```
After the patch:
```
$ ./perf_repro
[*] Current perf_event_paranoid level: 4.
[*] This is a custom Ubuntu paranoid level.
[*] Current capabilities: cap_perfmon=ep
[*] CPU_CYCLES: Successfully opened perf event
[*] INSTRUCTIONS: Successfully opened perf event
[*] CACHE_REFERENCES: Successfully opened perf event
All perf events accessible with current capabilities
```
[ Regression Potential ]
The regression potential is minimal.
The fix maintains backward compatibility as perfmon_capable() accepts both
CAP_SYS_ADMIN and CAP_PERFMON, ensuring all curently working systems are not impacted by the fix.
No security weakening occurs since CAP_PERFMON was designed for performance monitoring and provides fewer privileges than CAP_SYS_ADMIN.
---
I am trying to run node_exporter without root, with cap_perfmon and --collector.perf as well as --collector.perf.hardware-profilers=CpuCycles,CpuInstr.
Expected behavior: node_exporter exports instructions and cpu cycle metrics
Actual behavior: no perf metrics
version: Ubuntu 6.8.0-87.88-generic 6.8.12
Ubuntu carries a patch that introduces a new security level for perf events: perf_event_paranoid=4
This patch limits calling the perf open syscall to processes with CAP_SYS_ADMIN. This patch is from ~2016.
Example commit for resolute: https://git.launchpad.net/~canonical-
kernel/ubuntu/+source/linux-
aws/+git/resolute/commit/kernel/events/core.c?id=eaa91347f6f8112c5c567f93123bfe3b82bd1593
In 2020 a new capability was introduced, CAP_PERFMON, that should be sufficient for using perf.
The code now checks with perfmon_capable() if the process has CAP_SYS_ADMIN _or_ CAP_PERFMON. I am trying to get cpu hardware metrics with CAP_PERFMON but can't.
Looking at the commit message, timing and effect I think the introduction of CAP_PERFMON was missed
The patch
> + if (perf_paranoid_any() && !capable(CAP_SYS_ADMIN))
> + return -EACCES;
should probably be
> + if (perf_paranoid_any() && !perfmon_capable())
> + return -EACCES;
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-87-generic 6.8.0-87.88
ProcVersionSignature: Ubuntu 6.8.0-87.88-generic 6.8.12
Uname: Linux 6.8.0-87-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: rtreffer 2521 F.... wireplumber
/dev/snd/seq: rtreffer 2519 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Nov 10 21:46:59 2025
InstallationDate: Installed on 2025-11-08 (2 days ago)
InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
IwConfig:
lo no wireless extensions.
enp1s0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap
Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 001: Dev 002, If 0, Class=Chip/SmartCard, Driver=[none], 12M
|__ Port 002: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 5000M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 virtio_gpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-87-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
RelatedPackageVersions:
linux-restricted-modules-6.8.0-87-generic N/A
linux-backports-modules-6.8.0-87-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.19
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2025
dmi.bios.release: 0.0
dmi.bios.vendor: Ubuntu distribution of EDK II
dmi.bios.version: 2025.02-8ubuntu3
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-10.1
dmi.modalias: dmi:bvnUbuntudistributionofEDKII:bvr2025.02-8ubuntu3:bd10/08/2025:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-10.1:cvnQEMU:ct1:cvrpc-q35-10.1:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-10.1
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2131046/+subscriptions
[Bug 2136820] Re: ubuntu_kselftests:_net/net:gre_gso.sh failing
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1107.116~20.04.1 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-linux-
azure-5.15' to 'verification-done-focal-linux-azure-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
azure-5.15' to 'verification-failed-focal-linux-azure-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-azure-5.15-v2 verification-needed-focal-linux-azure-5.15
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2136820
Title:
ubuntu_kselftests:_net/net:gre_gso.sh failing
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Plucky:
Won't Fix
Status in linux source package in Questing:
Fix Released
Status in linux source package in Resolute:
New
Bug description:
SRU Justification:
[Impact]
rarely gre_gso.sh fails with socat getting killed by signal 15. Note
that in the log below two "exiting on signal 15" are ok. The first one
should not be there.
1002773 01:08:59 DEBUG| Running 'make run_tests -C net TEST_PROGS=gre_gso.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
1002774 01:08:59 DEBUG| [stdout] make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net'
1002775 01:08:59 DEBUG| [stdout] TAP version 13
1002776 01:08:59 DEBUG| [stdout] 1..1
1002777 01:08:59 DEBUG| [stdout] # timeout set to 0
1002778 01:08:59 DEBUG| [stdout] # selftests: net: gre_gso.sh
1002779 01:09:02 DEBUG| [stdout] # 2025/11/28 01:09:02 socat[689576] W exiting on signal 15
1002780 01:09:02 DEBUG| [stdout] # TEST: GREv6/v4 - copy file w/ TSO [FAIL]
1002781 01:09:02 DEBUG| [stdout] # TEST: GREv6/v4 - copy file w/ GSO [ OK ]
1002782 01:09:02 DEBUG| [stdout] # 2025/11/28 01:09:02 socat[689568] W exiting on signal 15
1002783 01:09:03 DEBUG| [stdout] # TEST: GREv6/v6 - copy file w/ TSO [ OK ]
1002784 01:09:03 DEBUG| [stdout] # TEST: GREv6/v6 - copy file w/ GSO [ OK ]
1002785 01:09:03 DEBUG| [stdout] # 2025/11/28 01:09:03 socat[689583] W exiting on signal 15
1002786 01:09:03 DEBUG| [stdout] #
1002787 01:09:03 DEBUG| [stdout] # Tests passed: 3
1002788 01:09:03 DEBUG| [stdout] # Tests failed: 1
1002789 01:09:03 DEBUG| [stdout] not ok 1 selftests: net: gre_gso.sh # exit=1
This is most likely timing issue.
[Fix]
This can be mitigated by increasing timeout for socat from 1 to 3
seconds.
[Test Plan]
Run the test in a loop many times
[What could go wrong]
This is not a change to the kernel code but tests. The timeout does
not increase test duration when everything is fine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2136820/+subscriptions
azure-5.15/5.15.0-1107.116~20.04.1 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-linux-
azure-5.15' to 'verification-done-focal-linux-azure-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
azure-5.15' to 'verification-failed-focal-linux-azure-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-azure-5.15-v2 verification-needed-focal-linux-azure-5.15
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2136820
Title:
ubuntu_kselftests:_net/net:gre_gso.sh failing
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Plucky:
Won't Fix
Status in linux source package in Questing:
Fix Released
Status in linux source package in Resolute:
New
Bug description:
SRU Justification:
[Impact]
rarely gre_gso.sh fails with socat getting killed by signal 15. Note
that in the log below two "exiting on signal 15" are ok. The first one
should not be there.
1002773 01:08:59 DEBUG| Running 'make run_tests -C net TEST_PROGS=gre_gso.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
1002774 01:08:59 DEBUG| [stdout] make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net'
1002775 01:08:59 DEBUG| [stdout] TAP version 13
1002776 01:08:59 DEBUG| [stdout] 1..1
1002777 01:08:59 DEBUG| [stdout] # timeout set to 0
1002778 01:08:59 DEBUG| [stdout] # selftests: net: gre_gso.sh
1002779 01:09:02 DEBUG| [stdout] # 2025/11/28 01:09:02 socat[689576] W exiting on signal 15
1002780 01:09:02 DEBUG| [stdout] # TEST: GREv6/v4 - copy file w/ TSO [FAIL]
1002781 01:09:02 DEBUG| [stdout] # TEST: GREv6/v4 - copy file w/ GSO [ OK ]
1002782 01:09:02 DEBUG| [stdout] # 2025/11/28 01:09:02 socat[689568] W exiting on signal 15
1002783 01:09:03 DEBUG| [stdout] # TEST: GREv6/v6 - copy file w/ TSO [ OK ]
1002784 01:09:03 DEBUG| [stdout] # TEST: GREv6/v6 - copy file w/ GSO [ OK ]
1002785 01:09:03 DEBUG| [stdout] # 2025/11/28 01:09:03 socat[689583] W exiting on signal 15
1002786 01:09:03 DEBUG| [stdout] #
1002787 01:09:03 DEBUG| [stdout] # Tests passed: 3
1002788 01:09:03 DEBUG| [stdout] # Tests failed: 1
1002789 01:09:03 DEBUG| [stdout] not ok 1 selftests: net: gre_gso.sh # exit=1
This is most likely timing issue.
[Fix]
This can be mitigated by increasing timeout for socat from 1 to 3
seconds.
[Test Plan]
Run the test in a loop many times
[What could go wrong]
This is not a change to the kernel code but tests. The timeout does
not increase test duration when everything is fine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2136820/+subscriptions
[Bug 2128729] Re: Black screen when booting 5.15.0-160 (on AMD Lucienne / Cezanne / Navi / Renoir / Rembrandt)
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1107.116~20.04.1 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-linux-
azure-5.15' to 'verification-done-focal-linux-azure-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
azure-5.15' to 'verification-failed-focal-linux-azure-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-azure-5.15-v2 verification-needed-focal-linux-azure-5.15
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2128729
Title:
Black screen when booting 5.15.0-160 (on AMD Lucienne / Cezanne / Navi
/ Renoir / Rembrandt)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
[Impact]
The Ubuntu backport of e6a7df96facdc ("drm/amd/display: Fix MST Null Ptr
for RV") to fix CVE-2024-26700 does not consider that
compute_mst_dsc_configs_for_state() returns a boolean to
indicate success or failure in 5.15, while it returns an integer
in later kernel versions with 0 indicating success. This means
we need to flip the error condition when checking whether the
call succeeded when backporting this to 5.15 and older.
Currently, the error path is taken even though the call to
compute_mst_dsc_configs_for_state() succeeds which causes some systems
to have no video output or a black screen while the system is running.
This is causing loss of video output to screens on affected amdgpu
hardware.
[Fix]
Check the return value of compute_mst_dsc_configs_for_state() in
amdgpu_dm_atomic_check() correctly.
[Test Plan]
Without the fix, there will be no video output to the screen and the
following messages can be found in the kernel log if the kernel is
booted with drm.debug=0x2:
kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] compute_mst_dsc_configs_for_state() failed
kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] Atomic check failed with err: -22
With the fix applied, video output should return to normal and the
kernel warnings will disappear from the log.
[Where problems could occur]
Problems would be observed in odd behavior of the amdgpu driver,
particularly for hardware with DSC support.
[Original Bug Report]
Updated to Kernel 5.15.0-160 from Kernel 5.15.0-157, System seemed to boot but I never got the usual splash logo while booting. Eventually the fans stop and the system sits idle with no video output. I updated the kernel using the system update tool. This system is down stream on Mint, so I can't use the instructions as written in the submission form. But I will do my best. I had to roll back to -157 to write this report. Hope this helps. Logs attached.
_____
[code]
System:
Kernel: 5.15.0-157-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
base: Ubuntu 22.04 jammy
Machine:
Type: Desktop System: Gigabyte product: X570S AERO G v: -CF serial: <superuser required>
Mobo: Gigabyte model: X570S AERO G v: x.x serial: <superuser required>
UEFI: American Megatrends LLC. v: F3 date: 01/04/2022
CPU:
Info: 8-core model: AMD Ryzen 7 5800X bits: 64 type: MT MCP smt: enabled arch: Zen 3 rev: 0
cache: L1: 512 KiB L2: 4 MiB L3: 32 MiB
Speed (MHz): avg: 4017 high: 4850 min/max: 2200/3800 boost: enabled cores: 1: 4850 2: 3879
3: 3884 4: 3876 5: 3879 6: 3879 7: 3879 8: 3878 9: 4840 10: 3880 11: 3900 12: 3879 13: 3878
14: 3880 15: 3878 16: 4140 bogomips: 121593
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Sapphire driver: amdgpu
v: kernel pcie: speed: 16 GT/s lanes: 16 ports: active: DP-2 empty: DP-1,DP-3,HDMI-A-1
bus-ID: 0f:00.0 chip-ID: 1002:73bf class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1080 s-dpi: 96 s-size: 677x285mm (26.7x11.2") s-diag: 735mm (28.9")
Monitor-1: DisplayPort-1 mapped: DP-2 model: LG (GoldStar) 34UC89G serial: <filter>
res: 2560x1080 dpi: 81 size: 798x335mm (31.4x13.2") diag: 865mm (34.1") modes: max: 2560x1080
min: 640x480
OpenGL: renderer: AMD Radeon RX 6900 XT (navi21 LLVM 15.0.7 DRM 3.42 5.15.0-157-generic)
v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.3 direct render: Yes
Audio:
Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT] driver: snd_hda_intel
v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 0f:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie:
speed: 16 GT/s lanes: 16 bus-ID: 11:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: HP HyperX Cloud Alpha Wireless type: USB
driver: cdc_acm,hid-generic,snd-usb-audio,usbhid bus-ID: 5-2:2 chip-ID: 03f0:098d class-ID: 0a00
serial: <filter>
Sound Server-1: ALSA v: k5.15.0-157-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1
bus-ID: 08:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp8s0 state: up mac: <filter>
Device-2: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel pcie: speed: 5 GT/s
lanes: 1 port: N/A bus-ID: 09:00.0 chip-ID: 8086:15f3 class-ID: 0200
IF: enp9s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 5-5:3 chip-ID: 8087:0029
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 2184 hci-v: 5.2 rev: 2184
Drives:
Local Storage: total: 3.18 TiB used: 1.77 TiB (55.5%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 1B4QFXO7 temp: 34.9 C scheme: GPT
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 3B4QFXO7 temp: 35.9 C scheme: GPT
ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 37.9 C
ID-4: /dev/nvme3n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 52.9 C scheme: GPT
Partition:
ID-1: / size: 915.32 GiB used: 640.68 GiB (70.0%) fs: ext4 dev: /dev/nvme3n1p2
ID-2: /boot/efi size: 96 MiB used: 31.4 MiB (32.7%) fs: vfat dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Hub-2: 2-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 20 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 3-1:2 info: Integrated Express ITE Device type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 048d:5702 class-ID: 0300
Hub-4: 3-5:3 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0610 class-ID: 0900
Device-1: 3-5.1:5 info: Mad Catz Catz C.A.T. 9 type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 400mA chip-ID: 0738:0309 class-ID: 0300
Hub-5: 3-6:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 3-6.1:6 info: DEXIN MADCATZ R.A.T. 8+ gaming mouse type: Mouse,Keyboard
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 50mA chip-ID: 12cf:0c05
class-ID: 0300
Hub-6: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-7: 4-3:2 info: Genesys Logic USB3.1 Hub ports: 4 rev: 3.2 speed: 5 Gb/s chip-ID: 05e3:0626
class-ID: 0900
Hub-8: 5-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 5-2:2 info: HP HyperX Cloud Alpha Wireless
type: Audio,Keyboard,Abstract (modem),CDC-Data driver: cdc_acm,hid-generic,snd-usb-audio,usbhid
interfaces: 6 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 03f0:098d class-ID: 0a00
serial: <filter>
Device-2: 5-5:3 info: Intel AX200 Bluetooth type: Bluetooth driver: btusb interfaces: 2
rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 8087:0029 class-ID: e001
Hub-9: 5-6:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 5-6.1:5 info: Logitech G910 Orion Spark Mechanical Keyboard type: Keyboard,HID
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 046d:c32b
class-ID: 0300 serial: <filter>
Hub-10: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-11: 7-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 7-1:2 info: Elan Micro Gaming KB type: Keyboard driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 100mA chip-ID: 04f3:152e class-ID: 0301
Device-2: 7-2:3 info: SiGma Micro USB HANDLE type: Keyboard,HID driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 1c4f:007c class-ID: 0300
serial: <filter>
Hub-12: 8-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Device-1: 8-4:2 info: Pioneer Blu-ray Drive type: Mass Storage driver: usb-storage
interfaces: 1 rev: 3.0 speed: 5 Gb/s power: 8mA chip-ID: 08e4:017a class-ID: 0802
serial: <filter>
Sensors:
System Temperatures: cpu: 16.8 C mobo: 16.8 C gpu: amdgpu temp: 43.0 C mem: 46.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
Packages: 3131 apt: 3092 flatpak: 39
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https: //brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com virginia main upstream import backport
2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
Processes: 456 Uptime: 24m wakeups: 0 Memory: 62.69 GiB used: 4.52 GiB (7.2%) Init: systemd
v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client
inxi: 3.3.13
[/code]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2128729/+subscriptions
azure-5.15/5.15.0-1107.116~20.04.1 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-linux-
azure-5.15' to 'verification-done-focal-linux-azure-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
azure-5.15' to 'verification-failed-focal-linux-azure-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-azure-5.15-v2 verification-needed-focal-linux-azure-5.15
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2128729
Title:
Black screen when booting 5.15.0-160 (on AMD Lucienne / Cezanne / Navi
/ Renoir / Rembrandt)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
[Impact]
The Ubuntu backport of e6a7df96facdc ("drm/amd/display: Fix MST Null Ptr
for RV") to fix CVE-2024-26700 does not consider that
compute_mst_dsc_configs_for_state() returns a boolean to
indicate success or failure in 5.15, while it returns an integer
in later kernel versions with 0 indicating success. This means
we need to flip the error condition when checking whether the
call succeeded when backporting this to 5.15 and older.
Currently, the error path is taken even though the call to
compute_mst_dsc_configs_for_state() succeeds which causes some systems
to have no video output or a black screen while the system is running.
This is causing loss of video output to screens on affected amdgpu
hardware.
[Fix]
Check the return value of compute_mst_dsc_configs_for_state() in
amdgpu_dm_atomic_check() correctly.
[Test Plan]
Without the fix, there will be no video output to the screen and the
following messages can be found in the kernel log if the kernel is
booted with drm.debug=0x2:
kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] compute_mst_dsc_configs_for_state() failed
kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] Atomic check failed with err: -22
With the fix applied, video output should return to normal and the
kernel warnings will disappear from the log.
[Where problems could occur]
Problems would be observed in odd behavior of the amdgpu driver,
particularly for hardware with DSC support.
[Original Bug Report]
Updated to Kernel 5.15.0-160 from Kernel 5.15.0-157, System seemed to boot but I never got the usual splash logo while booting. Eventually the fans stop and the system sits idle with no video output. I updated the kernel using the system update tool. This system is down stream on Mint, so I can't use the instructions as written in the submission form. But I will do my best. I had to roll back to -157 to write this report. Hope this helps. Logs attached.
_____
[code]
System:
Kernel: 5.15.0-157-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
base: Ubuntu 22.04 jammy
Machine:
Type: Desktop System: Gigabyte product: X570S AERO G v: -CF serial: <superuser required>
Mobo: Gigabyte model: X570S AERO G v: x.x serial: <superuser required>
UEFI: American Megatrends LLC. v: F3 date: 01/04/2022
CPU:
Info: 8-core model: AMD Ryzen 7 5800X bits: 64 type: MT MCP smt: enabled arch: Zen 3 rev: 0
cache: L1: 512 KiB L2: 4 MiB L3: 32 MiB
Speed (MHz): avg: 4017 high: 4850 min/max: 2200/3800 boost: enabled cores: 1: 4850 2: 3879
3: 3884 4: 3876 5: 3879 6: 3879 7: 3879 8: 3878 9: 4840 10: 3880 11: 3900 12: 3879 13: 3878
14: 3880 15: 3878 16: 4140 bogomips: 121593
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Sapphire driver: amdgpu
v: kernel pcie: speed: 16 GT/s lanes: 16 ports: active: DP-2 empty: DP-1,DP-3,HDMI-A-1
bus-ID: 0f:00.0 chip-ID: 1002:73bf class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1080 s-dpi: 96 s-size: 677x285mm (26.7x11.2") s-diag: 735mm (28.9")
Monitor-1: DisplayPort-1 mapped: DP-2 model: LG (GoldStar) 34UC89G serial: <filter>
res: 2560x1080 dpi: 81 size: 798x335mm (31.4x13.2") diag: 865mm (34.1") modes: max: 2560x1080
min: 640x480
OpenGL: renderer: AMD Radeon RX 6900 XT (navi21 LLVM 15.0.7 DRM 3.42 5.15.0-157-generic)
v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.3 direct render: Yes
Audio:
Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT] driver: snd_hda_intel
v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 0f:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie:
speed: 16 GT/s lanes: 16 bus-ID: 11:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: HP HyperX Cloud Alpha Wireless type: USB
driver: cdc_acm,hid-generic,snd-usb-audio,usbhid bus-ID: 5-2:2 chip-ID: 03f0:098d class-ID: 0a00
serial: <filter>
Sound Server-1: ALSA v: k5.15.0-157-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1
bus-ID: 08:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp8s0 state: up mac: <filter>
Device-2: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel pcie: speed: 5 GT/s
lanes: 1 port: N/A bus-ID: 09:00.0 chip-ID: 8086:15f3 class-ID: 0200
IF: enp9s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 5-5:3 chip-ID: 8087:0029
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 2184 hci-v: 5.2 rev: 2184
Drives:
Local Storage: total: 3.18 TiB used: 1.77 TiB (55.5%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 1B4QFXO7 temp: 34.9 C scheme: GPT
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 3B4QFXO7 temp: 35.9 C scheme: GPT
ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 37.9 C
ID-4: /dev/nvme3n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 52.9 C scheme: GPT
Partition:
ID-1: / size: 915.32 GiB used: 640.68 GiB (70.0%) fs: ext4 dev: /dev/nvme3n1p2
ID-2: /boot/efi size: 96 MiB used: 31.4 MiB (32.7%) fs: vfat dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Hub-2: 2-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 20 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 3-1:2 info: Integrated Express ITE Device type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 048d:5702 class-ID: 0300
Hub-4: 3-5:3 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0610 class-ID: 0900
Device-1: 3-5.1:5 info: Mad Catz Catz C.A.T. 9 type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 400mA chip-ID: 0738:0309 class-ID: 0300
Hub-5: 3-6:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 3-6.1:6 info: DEXIN MADCATZ R.A.T. 8+ gaming mouse type: Mouse,Keyboard
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 50mA chip-ID: 12cf:0c05
class-ID: 0300
Hub-6: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-7: 4-3:2 info: Genesys Logic USB3.1 Hub ports: 4 rev: 3.2 speed: 5 Gb/s chip-ID: 05e3:0626
class-ID: 0900
Hub-8: 5-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 5-2:2 info: HP HyperX Cloud Alpha Wireless
type: Audio,Keyboard,Abstract (modem),CDC-Data driver: cdc_acm,hid-generic,snd-usb-audio,usbhid
interfaces: 6 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 03f0:098d class-ID: 0a00
serial: <filter>
Device-2: 5-5:3 info: Intel AX200 Bluetooth type: Bluetooth driver: btusb interfaces: 2
rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 8087:0029 class-ID: e001
Hub-9: 5-6:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 5-6.1:5 info: Logitech G910 Orion Spark Mechanical Keyboard type: Keyboard,HID
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 046d:c32b
class-ID: 0300 serial: <filter>
Hub-10: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-11: 7-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 7-1:2 info: Elan Micro Gaming KB type: Keyboard driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 100mA chip-ID: 04f3:152e class-ID: 0301
Device-2: 7-2:3 info: SiGma Micro USB HANDLE type: Keyboard,HID driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 1c4f:007c class-ID: 0300
serial: <filter>
Hub-12: 8-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Device-1: 8-4:2 info: Pioneer Blu-ray Drive type: Mass Storage driver: usb-storage
interfaces: 1 rev: 3.0 speed: 5 Gb/s power: 8mA chip-ID: 08e4:017a class-ID: 0802
serial: <filter>
Sensors:
System Temperatures: cpu: 16.8 C mobo: 16.8 C gpu: amdgpu temp: 43.0 C mem: 46.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
Packages: 3131 apt: 3092 flatpak: 39
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https: //brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com virginia main upstream import backport
2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
Processes: 456 Uptime: 24m wakeups: 0 Memory: 62.69 GiB used: 4.52 GiB (7.2%) Init: systemd
v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client
inxi: 3.3.13
[/code]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2128729/+subscriptions
[Bug 2130553] Re: Jammy Linux: Introduced Warning with CVE-2024-53090 fix
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1107.116~20.04.1 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-linux-
azure-5.15' to 'verification-done-focal-linux-azure-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
azure-5.15' to 'verification-failed-focal-linux-azure-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-azure-5.15-v2 verification-needed-focal-linux-azure-5.15
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2130553
Title:
Jammy Linux: Introduced Warning with CVE-2024-53090 fix
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
[ Impact ]
While fixing CVE-2024-53090 (https://lists.ubuntu.com/archives/kernel-team/2025-October/164082.html) a warning has been introduced in the kernel by adding a superfluous line of code.
This has no impact on the stability or the functionality of the code, just a new warning that shows up at compile time.
[ Fix ]
To fix this, a SAUCE patch will be sent to the Kernel mailing list to
remove the unnecessary line.
[ Test plan ]
To be compile tested
[ Regression potential ]
None
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2130553/+subscriptions
azure-5.15/5.15.0-1107.116~20.04.1 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-linux-
azure-5.15' to 'verification-done-focal-linux-azure-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
azure-5.15' to 'verification-failed-focal-linux-azure-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-azure-5.15-v2 verification-needed-focal-linux-azure-5.15
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2130553
Title:
Jammy Linux: Introduced Warning with CVE-2024-53090 fix
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
[ Impact ]
While fixing CVE-2024-53090 (https://lists.ubuntu.com/archives/kernel-team/2025-October/164082.html) a warning has been introduced in the kernel by adding a superfluous line of code.
This has no impact on the stability or the functionality of the code, just a new warning that shows up at compile time.
[ Fix ]
To fix this, a SAUCE patch will be sent to the Kernel mailing list to
remove the unnecessary line.
[ Test plan ]
To be compile tested
[ Regression potential ]
None
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2130553/+subscriptions
[Bug 2136734] Re: selftests: net: veth: fix compatibility with older ethtool versions
This bug is awaiting verification that the linux-
azure-5.15/5.15.0-1107.116~20.04.1 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-linux-
azure-5.15' to 'verification-done-focal-linux-azure-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
azure-5.15' to 'verification-failed-focal-linux-azure-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-azure-5.15-v2 verification-needed-focal-linux-azure-5.15
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2136734
Title:
selftests: net: veth: fix compatibility with older ethtool versions
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
[ Impact ]
The veth.sh selftest fails on Focal systems running 5.15 hwe kernel
due to incompatibilities with older ethtool version shipped in Focal.
Two specific failures occur:
1. The test command "ethtool -K veth$DST generic-receive-offload on"
fails with "ethtool: bad command line argument(s)" because ethtool 5.4
does not recognize the long form feature name with the -K option.
2. The chk_channels() function incorrectly reports failures for combined
channels because ethtool 5.4 outputs '0' for unsupported channels while
the test expects 'n/a'.
These failures occur even when the underlying kernel functionality being
tested works correctly, causing false negatives in the test suite.
[ Fix ]
Use the short form 'gro' instead of 'generic-receive-offload' when
setting features with ethtool -K. The short form is compatible with
both old and new ethtool versions, while the long form only works with
newer versions for the -K operation.
Modify the chk_channels() function to accept both 'n/a' and '0' as valid
values for unsupported combined channels. This accommodates the
different output formats between ethtool versions while maintaining the
correct validation logic.
Both fixes are purely compatibility changes that do not alter the test
logic or the kernel functionality being tested.
[ Test Plan ]
Test ubuntu_kselftest_net net:veth.sh on both Jammy 5.15 and Focal 5.15 kernels.
The expected output is the following:
# selftests: net: veth.sh
# default - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - aggregation ok
# - aggregation with TSO off ok
# with gro on - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - aggregation with TSO off ok
# gro vs xdp while down - gro flag on ok
# - after down ok
# - after xdp off ok
# - after up ok
# - after peer xdp ok
# default channels ok
# with gro enabled on link down - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - aggregation with TSO off ok
# setting tx channels ok
# setting both rx and tx channels ok
# bad setting: combined channels ok
# setting invalid channels nr ok
# bad setting: XDP with RX nr less than TX ok
# bad setting: reducing RX nr below peer TX with XDP set ok
# bad setting: increasing peer TX nr above RX with XDP set ok
# setting invalid channels nr ok
# with xdp attached - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - no aggregation ok
# - gro flag with GRO on ok
# - aggregation ok
# - after dev off, flag ok
# - peer flag ok
# - after gro on xdp off, gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# decreasing tx channels with device down ok
# - aggregation ok
# increasing tx channels with device down ok
# aggregation again with default and TSO off ok
ok 7 selftests: net: veth.sh
[ Regression Potential ]
The patchset only modify the selftest script and do not change any
kernel code. The changes improve compatibility with different ethtool
versions by using universally supported feature names and accepting
multiple valid output formats. In case of a regression, it would only
affect test execution, not kernel functionality.
[ Other Info ]
The bug affects all Focal's 5.15 kernels.
In order to fix them all the patchset has been submitted for Jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2136734/+subscriptions
azure-5.15/5.15.0-1107.116~20.04.1 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-linux-
azure-5.15' to 'verification-done-focal-linux-azure-5.15'. If the
problem still exists, change the tag 'verification-needed-focal-linux-
azure-5.15' to 'verification-failed-focal-linux-azure-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-azure-5.15-v2 verification-needed-focal-linux-azure-5.15
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2136734
Title:
selftests: net: veth: fix compatibility with older ethtool versions
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
[ Impact ]
The veth.sh selftest fails on Focal systems running 5.15 hwe kernel
due to incompatibilities with older ethtool version shipped in Focal.
Two specific failures occur:
1. The test command "ethtool -K veth$DST generic-receive-offload on"
fails with "ethtool: bad command line argument(s)" because ethtool 5.4
does not recognize the long form feature name with the -K option.
2. The chk_channels() function incorrectly reports failures for combined
channels because ethtool 5.4 outputs '0' for unsupported channels while
the test expects 'n/a'.
These failures occur even when the underlying kernel functionality being
tested works correctly, causing false negatives in the test suite.
[ Fix ]
Use the short form 'gro' instead of 'generic-receive-offload' when
setting features with ethtool -K. The short form is compatible with
both old and new ethtool versions, while the long form only works with
newer versions for the -K operation.
Modify the chk_channels() function to accept both 'n/a' and '0' as valid
values for unsupported combined channels. This accommodates the
different output formats between ethtool versions while maintaining the
correct validation logic.
Both fixes are purely compatibility changes that do not alter the test
logic or the kernel functionality being tested.
[ Test Plan ]
Test ubuntu_kselftest_net net:veth.sh on both Jammy 5.15 and Focal 5.15 kernels.
The expected output is the following:
# selftests: net: veth.sh
# default - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - aggregation ok
# - aggregation with TSO off ok
# with gro on - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - aggregation with TSO off ok
# gro vs xdp while down - gro flag on ok
# - after down ok
# - after xdp off ok
# - after up ok
# - after peer xdp ok
# default channels ok
# with gro enabled on link down - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - aggregation with TSO off ok
# setting tx channels ok
# setting both rx and tx channels ok
# bad setting: combined channels ok
# setting invalid channels nr ok
# bad setting: XDP with RX nr less than TX ok
# bad setting: reducing RX nr below peer TX with XDP set ok
# bad setting: increasing peer TX nr above RX with XDP set ok
# setting invalid channels nr ok
# with xdp attached - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - no aggregation ok
# - gro flag with GRO on ok
# - aggregation ok
# - after dev off, flag ok
# - peer flag ok
# - after gro on xdp off, gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# decreasing tx channels with device down ok
# - aggregation ok
# increasing tx channels with device down ok
# aggregation again with default and TSO off ok
ok 7 selftests: net: veth.sh
[ Regression Potential ]
The patchset only modify the selftest script and do not change any
kernel code. The changes improve compatibility with different ethtool
versions by using universally supported feature names and accepting
multiple valid output formats. In case of a regression, it would only
affect test execution, not kernel functionality.
[ Other Info ]
The bug affects all Focal's 5.15 kernels.
In order to fix them all the patchset has been submitted for Jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2136734/+subscriptions
[Bug 2142443] Please test proposed package
Hello Daniel, or anyone else affected,
Accepted nvidia-graphics-drivers-590 into questing-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-590/590.48.01-0ubuntu0.25.10.4 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Tags added: verification-needed-noble
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
New
Status in nvidia-graphics-drivers-535-server source package in Noble:
New
Status in nvidia-graphics-drivers-570 source package in Noble:
New
Status in nvidia-graphics-drivers-570-server source package in Noble:
New
Status in nvidia-graphics-drivers-580 source package in Noble:
New
Status in nvidia-graphics-drivers-580-server source package in Noble:
New
Status in nvidia-graphics-drivers-590 source package in Noble:
New
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-580-server source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-590 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-590-server source package in Questing:
Fix Committed
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
Accepted nvidia-graphics-drivers-590 into questing-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-590/590.48.01-0ubuntu0.25.10.4 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Tags added: verification-needed-noble
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
New
Status in nvidia-graphics-drivers-535-server source package in Noble:
New
Status in nvidia-graphics-drivers-570 source package in Noble:
New
Status in nvidia-graphics-drivers-570-server source package in Noble:
New
Status in nvidia-graphics-drivers-580 source package in Noble:
New
Status in nvidia-graphics-drivers-580-server source package in Noble:
New
Status in nvidia-graphics-drivers-590 source package in Noble:
New
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-580-server source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-590 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-590-server source package in Questing:
Fix Committed
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
[Bug 2142443] Please test proposed package
Hello Daniel, or anyone else affected,
Accepted nvidia-graphics-drivers-590-server into questing-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-590-server/590.48.01-0ubuntu0.25.10.4 in a few hours, and then
in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: nvidia-graphics-drivers-590 (Ubuntu Questing)
Status: New => Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
New
Status in nvidia-graphics-drivers-535-server source package in Noble:
New
Status in nvidia-graphics-drivers-570 source package in Noble:
New
Status in nvidia-graphics-drivers-570-server source package in Noble:
New
Status in nvidia-graphics-drivers-580 source package in Noble:
New
Status in nvidia-graphics-drivers-580-server source package in Noble:
New
Status in nvidia-graphics-drivers-590 source package in Noble:
New
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-580-server source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-590 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-590-server source package in Questing:
Fix Committed
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
Accepted nvidia-graphics-drivers-590-server into questing-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-590-server/590.48.01-0ubuntu0.25.10.4 in a few hours, and then
in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: nvidia-graphics-drivers-590 (Ubuntu Questing)
Status: New => Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
New
Status in nvidia-graphics-drivers-535-server source package in Noble:
New
Status in nvidia-graphics-drivers-570 source package in Noble:
New
Status in nvidia-graphics-drivers-570-server source package in Noble:
New
Status in nvidia-graphics-drivers-580 source package in Noble:
New
Status in nvidia-graphics-drivers-580-server source package in Noble:
New
Status in nvidia-graphics-drivers-590 source package in Noble:
New
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-580-server source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-590 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-590-server source package in Questing:
Fix Committed
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
[Bug 2142443] Re: [resolute] Installed an Nvidia driver and now booting to a frozen black screen
Hello Daniel, or anyone else affected,
Accepted nvidia-graphics-drivers-580-server into questing-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-580-server/580.126.09-0ubuntu0.25.10.2 in a few hours, and then
in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: nvidia-graphics-drivers-580-server (Ubuntu Questing)
Status: New => Fix Committed
** Changed in: nvidia-graphics-drivers-590-server (Ubuntu Questing)
Status: New => Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
New
Status in nvidia-graphics-drivers-535-server source package in Noble:
New
Status in nvidia-graphics-drivers-570 source package in Noble:
New
Status in nvidia-graphics-drivers-570-server source package in Noble:
New
Status in nvidia-graphics-drivers-580 source package in Noble:
New
Status in nvidia-graphics-drivers-580-server source package in Noble:
New
Status in nvidia-graphics-drivers-590 source package in Noble:
New
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-580-server source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-590 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-590-server source package in Questing:
Fix Committed
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
Accepted nvidia-graphics-drivers-580-server into questing-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-580-server/580.126.09-0ubuntu0.25.10.2 in a few hours, and then
in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: nvidia-graphics-drivers-580-server (Ubuntu Questing)
Status: New => Fix Committed
** Changed in: nvidia-graphics-drivers-590-server (Ubuntu Questing)
Status: New => Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
New
Status in nvidia-graphics-drivers-535-server source package in Noble:
New
Status in nvidia-graphics-drivers-570 source package in Noble:
New
Status in nvidia-graphics-drivers-570-server source package in Noble:
New
Status in nvidia-graphics-drivers-580 source package in Noble:
New
Status in nvidia-graphics-drivers-580-server source package in Noble:
New
Status in nvidia-graphics-drivers-590 source package in Noble:
New
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-580-server source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-590 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-590-server source package in Questing:
Fix Committed
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
[Bug 2142443] Re: [resolute] Installed an Nvidia driver and now booting to a frozen black screen
Hello Daniel, or anyone else affected,
Accepted nvidia-graphics-drivers-580 into questing-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-580/580.126.09-0ubuntu0.25.10.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Also affects: linux (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-580 (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-580-server (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-590 (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-590-server (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-580 (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-580-server (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-590 (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-590-server (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-580 (Ubuntu)
Status: In Progress => Fix Released
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-535-server (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-570 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-570-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-570-server (Ubuntu)
Status: New => Invalid
** Changed in: nvidia-graphics-drivers-570 (Ubuntu)
Status: New => Invalid
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
Status: New => Invalid
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Noble)
Status: New => Invalid
** Changed in: linux (Ubuntu Questing)
Status: New => Invalid
** Description changed:
+ [Impact]
+
+ nova driver conflicts with the nvidia proprietary driver, and a 6.17
+ stable update in proposed enables nova_core module, which finally makes
+ nova usable resulting in it taking over.
+
+ Nova and nova_core need to be blacklisted in the nvidia driver(s) just
+ like nouveau.
+
+ [Test case]
+
+ Install the updated nvidia driver, reboot the machine. Nvidia should be
+ used and working.
+
+ [Where problems could happen]
+
+ we should have covered all the drivers, but if for instance the
+ blacklist file does not get updated for whatever the reason, then the
+ update has no effect
+
+ --
+
I installed the latest Nvidia driver in Resolute:
- ubuntu-drivers list
- sudo ubuntu-drivers install nvidia-driver-590-open
- sudo reboot
+ ubuntu-drivers list
+ sudo ubuntu-drivers install nvidia-driver-590-open
+ sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
- Subsystem: Gigabyte Technology Co., Ltd Device 4131
- Kernel driver in use: NovaCore
- Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
+ Subsystem: Gigabyte Technology Co., Ltd Device 4131
+ Kernel driver in use: NovaCore
+ Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
** Changed in: nvidia-graphics-drivers-580 (Ubuntu Questing)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-questing
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
New
Status in nvidia-graphics-drivers-535-server source package in Noble:
New
Status in nvidia-graphics-drivers-570 source package in Noble:
New
Status in nvidia-graphics-drivers-570-server source package in Noble:
New
Status in nvidia-graphics-drivers-580 source package in Noble:
New
Status in nvidia-graphics-drivers-580-server source package in Noble:
New
Status in nvidia-graphics-drivers-590 source package in Noble:
New
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-580-server source package in Questing:
New
Status in nvidia-graphics-drivers-590 source package in Questing:
New
Status in nvidia-graphics-drivers-590-server source package in Questing:
New
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
Accepted nvidia-graphics-drivers-580 into questing-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-580/580.126.09-0ubuntu0.25.10.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
questing to verification-done-questing. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-questing. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Also affects: linux (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-580 (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-580-server (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-590 (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-590-server (Ubuntu Questing)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-580 (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-580-server (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-590 (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-590-server (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-580 (Ubuntu)
Status: In Progress => Fix Released
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-535-server (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-570 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-570-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-570-server (Ubuntu)
Status: New => Invalid
** Changed in: nvidia-graphics-drivers-570 (Ubuntu)
Status: New => Invalid
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
Status: New => Invalid
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Noble)
Status: New => Invalid
** Changed in: linux (Ubuntu Questing)
Status: New => Invalid
** Description changed:
+ [Impact]
+
+ nova driver conflicts with the nvidia proprietary driver, and a 6.17
+ stable update in proposed enables nova_core module, which finally makes
+ nova usable resulting in it taking over.
+
+ Nova and nova_core need to be blacklisted in the nvidia driver(s) just
+ like nouveau.
+
+ [Test case]
+
+ Install the updated nvidia driver, reboot the machine. Nvidia should be
+ used and working.
+
+ [Where problems could happen]
+
+ we should have covered all the drivers, but if for instance the
+ blacklist file does not get updated for whatever the reason, then the
+ update has no effect
+
+ --
+
I installed the latest Nvidia driver in Resolute:
- ubuntu-drivers list
- sudo ubuntu-drivers install nvidia-driver-590-open
- sudo reboot
+ ubuntu-drivers list
+ sudo ubuntu-drivers install nvidia-driver-590-open
+ sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
- Subsystem: Gigabyte Technology Co., Ltd Device 4131
- Kernel driver in use: NovaCore
- Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
+ Subsystem: Gigabyte Technology Co., Ltd Device 4131
+ Kernel driver in use: NovaCore
+ Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
** Changed in: nvidia-graphics-drivers-580 (Ubuntu Questing)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-questing
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-570-server package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-580-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-590-server package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Invalid
Status in nvidia-graphics-drivers-535 source package in Noble:
New
Status in nvidia-graphics-drivers-535-server source package in Noble:
New
Status in nvidia-graphics-drivers-570 source package in Noble:
New
Status in nvidia-graphics-drivers-570-server source package in Noble:
New
Status in nvidia-graphics-drivers-580 source package in Noble:
New
Status in nvidia-graphics-drivers-580-server source package in Noble:
New
Status in nvidia-graphics-drivers-590 source package in Noble:
New
Status in nvidia-graphics-drivers-590-server source package in Noble:
New
Status in linux source package in Questing:
Invalid
Status in nvidia-graphics-drivers-535 source package in Questing:
New
Status in nvidia-graphics-drivers-535-server source package in Questing:
New
Status in nvidia-graphics-drivers-570 source package in Questing:
New
Status in nvidia-graphics-drivers-570-server source package in Questing:
New
Status in nvidia-graphics-drivers-580 source package in Questing:
Fix Committed
Status in nvidia-graphics-drivers-580-server source package in Questing:
New
Status in nvidia-graphics-drivers-590 source package in Questing:
New
Status in nvidia-graphics-drivers-590-server source package in Questing:
New
Bug description:
[Impact]
nova driver conflicts with the nvidia proprietary driver, and a 6.17
stable update in proposed enables nova_core module, which finally
makes nova usable resulting in it taking over.
Nova and nova_core need to be blacklisted in the nvidia driver(s) just
like nouveau.
[Test case]
Install the updated nvidia driver, reboot the machine. Nvidia should
be used and working.
[Where problems could happen]
we should have covered all the drivers, but if for instance the
blacklist file does not get updated for whatever the reason, then the
update has no effect
--
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
[Bug 2143104] Please test proposed package
Hello Chris, or anyone else affected,
Accepted linux-firmware into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20240318.git3b128b60-0ubuntu2.26 in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143104
Title:
Enable CirrusLogic audio solution CS42L45+CS35L63
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Questing:
Won't Fix
Status in linux-firmware source package in Questing:
Fix Committed
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Incomplete
Status in linux-firmware source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
SRU Justification:
[Impact]
New Dell Yukon platform with CirrusLogic audio solution CS42L45+CS35L63 will have no basic audio functions w/o AMD ACP Driver Support.
================ Linux Kernel ========================
[Fix]
Backport new AMD ACP drivers of the following
ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts
ASoC: amd: acp: Sort Cirrus Logic match entries
ASoC: amd: acp: Rename Cirrus Logic component match entries to include link a...
ASoC: amd: acp: Sort match table into most specific first
ASoC: amd: amd_sdw: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: ps: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: acp: Add ACP7.0 match entries for cs35l56 and cs42l43
And patches https://lore.kernel.org/linux-
sound/20260205164539.892403-1-Vijendar.Mukunda@amd.com/T/#t which are
still under review.
<=============== linux-firmware ========================
[Fix]
Backport the patch firmware from CirrusLogic
8ca12d638 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
53ec87319 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Lenovo laptops
4aaa9c557 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
[Test Case]
1. Boot up the machine of new Dell Yukon platform with CirrusLogic CS42L45+CS35L63
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
[Where problems could occur]
It adds the support for new CirrusLogic CS42L45+CS35L63. No regression expected at the current stage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2143104/+subscriptions
Accepted linux-firmware into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20240318.git3b128b60-0ubuntu2.26 in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143104
Title:
Enable CirrusLogic audio solution CS42L45+CS35L63
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Questing:
Won't Fix
Status in linux-firmware source package in Questing:
Fix Committed
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Incomplete
Status in linux-firmware source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
SRU Justification:
[Impact]
New Dell Yukon platform with CirrusLogic audio solution CS42L45+CS35L63 will have no basic audio functions w/o AMD ACP Driver Support.
================ Linux Kernel ========================
[Fix]
Backport new AMD ACP drivers of the following
ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts
ASoC: amd: acp: Sort Cirrus Logic match entries
ASoC: amd: acp: Rename Cirrus Logic component match entries to include link a...
ASoC: amd: acp: Sort match table into most specific first
ASoC: amd: amd_sdw: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: ps: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: acp: Add ACP7.0 match entries for cs35l56 and cs42l43
And patches https://lore.kernel.org/linux-
sound/20260205164539.892403-1-Vijendar.Mukunda@amd.com/T/#t which are
still under review.
<=============== linux-firmware ========================
[Fix]
Backport the patch firmware from CirrusLogic
8ca12d638 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
53ec87319 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Lenovo laptops
4aaa9c557 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
[Test Case]
1. Boot up the machine of new Dell Yukon platform with CirrusLogic CS42L45+CS35L63
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
[Where problems could occur]
It adds the support for new CirrusLogic CS42L45+CS35L63. No regression expected at the current stage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2143104/+subscriptions
[Bug 2139391] Please test proposed package
Hello Chris, or anyone else affected,
Accepted linux-firmware into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20240318.git3b128b60-0ubuntu2.26 in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139391
Title:
Support for Cirrus Logic audio solution CS42L43+CS35L56A on new Dell
PTL Bolan platform
Status in HWE Next:
New
Status in alsa-ucm-conf package in Ubuntu:
New
Status in firmware-sof package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in alsa-ucm-conf source package in Noble:
New
Status in firmware-sof source package in Noble:
New
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in alsa-ucm-conf source package in Questing:
New
Status in firmware-sof source package in Questing:
New
Status in linux source package in Questing:
New
Status in linux-firmware source package in Questing:
Fix Committed
Status in linux-oem-6.17 source package in Questing:
New
Status in alsa-ucm-conf source package in Resolute:
New
Status in firmware-sof source package in Resolute:
New
Status in linux source package in Resolute:
Incomplete
Status in linux-firmware source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
SRU Justification:
[Impact]
New Dell Bolan platform with CirrusLogic audio solution CS42L43+CS35L56A powered by Intel PantherLake will have no basic audio functions w/o Soundwire Driver Support.
================ Linux Kernel ========================
[Fix]
Backport new Intel soundwire drivers of the following
ASoC: Intel: sof_sdw: Add new quirks for PTL on Dell with CS42L43 - kernel/git/broonie/sound.git - ASoC - (Upstreamed)
ASoC: soc-acpi / SOF: Add best_effort flag to get_function_tplg_files op - kernel/git/broonie/sound… - (Upstreamed)
ASoC: cs35l56: Use vendor-specific qualifier in firmware file search
ASoC: cs-amp-lib: Support Dell SSIDExV2 UEFI variable
<=============== linux-firmware ========================
[Fix]
Backport the patch firmware from CirrusLogic
cirrus: cs35l56 cs35l57: Add and update firmware for some Dell laptops - kernel/git/firmware/linux-firmware.git - Repository of firmware blobs for use with the Linux kernel
<=============== alsa-ucm-conf ========================
Backport the patch firmware from CirrusLogic
https://github.com/alsa-project/alsa-ucm-conf/commit/06a2ef880c524319ea6bd0e2688573a002badecb
https://github.com/alsa-project/alsa-ucm-conf/commit/46f30b3f9f7468d6f1286d296faf6bf6bd6c3235
<=============== firmware-sof ========================
Add 2.14 tools and topology binaries for Intel MTL and newer targets · thesofproject/sof-bin@cdd3c8f
[Test Case]
1. Boot up the machine of new Dell Intel PTL Bolan platform with CirrusLogic CS42L43+CS35L56A
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
[Where problems could occur]
It adds the support for new CirrusLogic CS42L43+CS35L56A on PTL platform. No regression expected at the current stage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2139391/+subscriptions
Accepted linux-firmware into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20240318.git3b128b60-0ubuntu2.26 in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139391
Title:
Support for Cirrus Logic audio solution CS42L43+CS35L56A on new Dell
PTL Bolan platform
Status in HWE Next:
New
Status in alsa-ucm-conf package in Ubuntu:
New
Status in firmware-sof package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in alsa-ucm-conf source package in Noble:
New
Status in firmware-sof source package in Noble:
New
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in alsa-ucm-conf source package in Questing:
New
Status in firmware-sof source package in Questing:
New
Status in linux source package in Questing:
New
Status in linux-firmware source package in Questing:
Fix Committed
Status in linux-oem-6.17 source package in Questing:
New
Status in alsa-ucm-conf source package in Resolute:
New
Status in firmware-sof source package in Resolute:
New
Status in linux source package in Resolute:
Incomplete
Status in linux-firmware source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
SRU Justification:
[Impact]
New Dell Bolan platform with CirrusLogic audio solution CS42L43+CS35L56A powered by Intel PantherLake will have no basic audio functions w/o Soundwire Driver Support.
================ Linux Kernel ========================
[Fix]
Backport new Intel soundwire drivers of the following
ASoC: Intel: sof_sdw: Add new quirks for PTL on Dell with CS42L43 - kernel/git/broonie/sound.git - ASoC - (Upstreamed)
ASoC: soc-acpi / SOF: Add best_effort flag to get_function_tplg_files op - kernel/git/broonie/sound… - (Upstreamed)
ASoC: cs35l56: Use vendor-specific qualifier in firmware file search
ASoC: cs-amp-lib: Support Dell SSIDExV2 UEFI variable
<=============== linux-firmware ========================
[Fix]
Backport the patch firmware from CirrusLogic
cirrus: cs35l56 cs35l57: Add and update firmware for some Dell laptops - kernel/git/firmware/linux-firmware.git - Repository of firmware blobs for use with the Linux kernel
<=============== alsa-ucm-conf ========================
Backport the patch firmware from CirrusLogic
https://github.com/alsa-project/alsa-ucm-conf/commit/06a2ef880c524319ea6bd0e2688573a002badecb
https://github.com/alsa-project/alsa-ucm-conf/commit/46f30b3f9f7468d6f1286d296faf6bf6bd6c3235
<=============== firmware-sof ========================
Add 2.14 tools and topology binaries for Intel MTL and newer targets · thesofproject/sof-bin@cdd3c8f
[Test Case]
1. Boot up the machine of new Dell Intel PTL Bolan platform with CirrusLogic CS42L43+CS35L56A
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
[Where problems could occur]
It adds the support for new CirrusLogic CS42L43+CS35L56A on PTL platform. No regression expected at the current stage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2139391/+subscriptions
Подписаться на:
Комментарии (Atom)