[Kernel-packages] [Bug 1965496] Re: alsa: enable the cirrus-logic side-codec to make the speaker output sound
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1965496 Title: alsa: enable the cirrus-logic side-codec to make the speaker output sound Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] We have a couple of lenovo latops models which have cirrus-logic side codec between realtek codec and speaker, it plays a role as amplifier, we need to enable this side-codec, otherwise the speaker can't output sound. [Fix] Backport codec patches and some i2c and acpi detection patches from mainline kernel and linux-next [Test] boot the patched kernel, run speaker test, both left and right channel could work well. [Where problems could occur] If it could introduce regression, it will be on soc wm_adsp codec drivers, since most of patch are adding new codec drivers, it will not touch existing codec drivers. If a machine with wm_adsp codec can't output sound or record sound, it means this SRU introduce the regression on wm_adsp driver, but this possibility is very low, since all patches are picked from mainline kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1965496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Impish) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1975691 Title: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux-oem-6.1 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Invalid Status in linux source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] test_vxlan_under_vrf.sh should not be failing anymore with patches submitted to fix it in bug 1871015 (unless it's a kernel config related issue). With the regression-testing result hinting system available, we should remove the SAUCE patches that mark "underlay in a VRF" test failure as an expected failure to catch regressions in the future. This could reduce maintenance cost as well. [Fix] Revert the following patches: * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default VRF an expected failure * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail [Test] Patched test script tested with F/I/J/F-oem-5.14/J-oem-5.17. I have also modify the test case to fail it deliberately to verify this change, it works as expected. [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. We may see failures reported from this test in our SRU regression-testing report in the future, but it means we're doing the right thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025675] Re: Realtek Bluetooth Radio ID 6655:8771 cannot connect after update
** Tags added: kern-7321 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2025675 Title: Realtek Bluetooth Radio ID 6655:8771 cannot connect after update Status in linux-firmware package in Ubuntu: Incomplete Bug description: After updating my system this morning, about six hours ago, my Bluetooth radio (Model number: Insignia ns-pa3bt5a2b22) (Bus 001 Device 002: ID 6655:8771 Realtek Bluetooth Radio) stopped working entirely. ubuntu-version: Ubuntu 22.04.2 LTS linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.14 Expected behavior: Bluetooth should connect, scanning for new devices should complete and list all discoverable devices. Actual behavior: Bluetooth shows up in the settings interface as expected, but does not connect to or show any previously connected devices (Logitech MX Master 3s, k850, Bose QC35), and scans for new devices forever. Additional information: In initial debugging stages, sudo dmesg | grep -i 'blue' Gave: ... [ 85.034768] Bluetooth: hci0: Ignoring error of Inquiry Cancel command Following the steps given here before I found this bug: https://askubuntu.com/questions/1398873/bluetooth-5-0-adapter-help did not resolve the problem, but did cause the dmesg to go away, such that I now just get: [ 1827.904469] usb 1-1: Product: Bluetooth Radio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2025675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025675] Re: Realtek Bluetooth Radio ID 6655:8771 cannot connect after update
Please run 'apport-collect 2025675' on this system. ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2025675 Title: Realtek Bluetooth Radio ID 6655:8771 cannot connect after update Status in linux-firmware package in Ubuntu: Incomplete Bug description: After updating my system this morning, about six hours ago, my Bluetooth radio (Model number: Insignia ns-pa3bt5a2b22) (Bus 001 Device 002: ID 6655:8771 Realtek Bluetooth Radio) stopped working entirely. ubuntu-version: Ubuntu 22.04.2 LTS linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.14 Expected behavior: Bluetooth should connect, scanning for new devices should complete and list all discoverable devices. Actual behavior: Bluetooth shows up in the settings interface as expected, but does not connect to or show any previously connected devices (Logitech MX Master 3s, k850, Bose QC35), and scans for new devices forever. Additional information: In initial debugging stages, sudo dmesg | grep -i 'blue' Gave: ... [ 85.034768] Bluetooth: hci0: Ignoring error of Inquiry Cancel command Following the steps given here before I found this bug: https://askubuntu.com/questions/1398873/bluetooth-5-0-adapter-help did not resolve the problem, but did cause the dmesg to go away, such that I now just get: [ 1827.904469] usb 1-1: Product: Bluetooth Radio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2025675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 AMD64
This issue can be found on J-azure-6.2 AMD64 as well.
** Tags added: 6.2
** Tags added: sru-20230515
** Summary changed:
- test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 /
J-OEM-6.1 AMD64
+ test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 /
J-OEM-6.1 / J-6.2 AMD64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1983357
Title:
test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
K-5.19 / J-OEM-6.1 / J-6.2 AMD64
Status in QA Regression Testing:
New
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
New
Status in linux source package in Kinetic:
Incomplete
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Bug description:
Issue found on 5.19.0-9.9 Kinetic AMD64 systems
Test log:
Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel:
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0
SUDO_USER: 'ubuntu')
test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs ... (default libs native) (default libs native rekey) (default
libs COMPAT) FAIL
==
FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
ASLR of libs
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
self._test_aslr('libs', expected)
File "./test-kernel-security.py", line 1727, in _test_aslr
self._test_aslr_all(area, expected, "default %s" % area)
File "./test-kernel-security.py", line 1720, in _test_aslr_all
self._test_aslr_exec(area, expected, target, name)
File "./test-kernel-security.py", line 1703, in _test_aslr_exec
self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area,
"--verbose"], msg="%s:\n" % name)
File
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
line 1203, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: default libs COMPAT:
Got exit code 1, expected 0
Command: './aslr32', 'libs', '--verbose'
Output:
Checking ASLR of libs:
0xf7c81790
0xf7c81790
0xf7c81790
FAIL: ASLR not functional (libs always at 0xf7c81790)
--
Ran 1 test in 0.144s
FAILED (failures=1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI
Does the issue still present on mainline kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1976473] Re: [Dell G15 5515] Unable to change screen brightness in ubuntu desktop
Should be fixed by next OEM kernel 6.1 release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976473 Title: [Dell G15 5515] Unable to change screen brightness in ubuntu desktop Status in linux package in Ubuntu: Confirmed Bug description: I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics. In /sys/class/backlight directory, there are two directories amdgpu_bl0 and nvidia_wmi_ec_backlight. When I change the screen brightness via slider then it changes the brightness value of nvidia_wmi_ec_backlight but it doesn't work. When I manually changed the value of amdgpu_bl0 brightness file then my screen brightness changed. My BIOS is updated to the latest version and I have NVIDIA Driver with version 510.73.05. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: yorozuya 2677 F pulseaudio /dev/snd/controlC0: yorozuya 2677 F pulseaudio /dev/snd/controlC1: yorozuya 2677 F pulseaudio /dev/snd/controlC3: yorozuya 2677 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Dell G15 5515 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/14/2022 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.asset.tag: not specified dmi.board.name: 0TGD6F dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E: dmi.product.family: GSeries dmi.product.name: Dell G15 5515 dmi.product.sku: 0A6E dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024427] Re: potential S3 issue for amdgpu Navi 31/Navi33
@superm1, do you have the symptoms, reproducing steps? We'll need them to justify the need to SRU firmware changes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2024427 Title: potential S3 issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Triaged Status in linux-firmware source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995957] Re: Add cs35l41 firmware loading support
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1995957 Title: Add cs35l41 firmware loading support Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] Speakers on some laptops are rather quiet even with max volume. [Fix] Loading firmware to make cs35l41 speaker amplifier really work. [Test] With the fix applied, the speaker has become really loud as intended. [Where problems could occur] Most commits are refactoring codes on both ASoC and HDA parts, so things can be missed. Other than that, the change is strictly limited to cs35l41, so the regression scope is rather narrow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025686] Re: RM superseded by generic
Removing packages from mantic: linux-signed-kvm 6.2.0-1003.3 in mantic linux-image-6.2.0-1003-kvm 6.2.0-1003.3 in mantic amd64 Comment: kvm flavor merged into virtual; LP: #2025686 1 package successfully removed. ** Changed in: linux-signed-kvm (Ubuntu Mantic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2025686 Title: RM superseded by generic Status in linux-kvm package in Ubuntu: Fix Released Status in linux-meta-kvm package in Ubuntu: Fix Released Status in linux-signed-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Mantic: Fix Released Status in linux-meta-kvm source package in Mantic: Fix Released Status in linux-signed-kvm source package in Mantic: Fix Released Bug description: RM superseded by generic generic kernel now supports initrd-less boot on VIRTIO SCSI devices. all other features were also ported to the generic kernel and/or livecd-rootfs. please remove kvm kernel from mantic. transitional packages will remain in linux-meta until after next lts release. please remove above mentioned packages from mantic-proposed and mantic-release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2025686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025686] Re: RM superseded by generic
Removing packages from mantic: linux-kvm 6.2.0-1003.3 in mantic linux-buildinfo-6.2.0-1003-kvm 6.2.0-1003.3 in mantic amd64 linux-headers-6.2.0-1003-kvm 6.2.0-1003.3 in mantic amd64 linux-image-unsigned-6.2.0-1003-kvm 6.2.0-1003.3 in mantic amd64 linux-kvm-headers-6.2.0-1003 6.2.0-1003.3 in mantic amd64 linux-kvm-headers-6.2.0-1003 6.2.0-1003.3 in mantic arm64 linux-kvm-headers-6.2.0-1003 6.2.0-1003.3 in mantic armhf linux-kvm-headers-6.2.0-1003 6.2.0-1003.3 in mantic i386 linux-kvm-headers-6.2.0-1003 6.2.0-1003.3 in mantic ppc64el linux-kvm-headers-6.2.0-1003 6.2.0-1003.3 in mantic riscv64 linux-kvm-headers-6.2.0-1003 6.2.0-1003.3 in mantic s390x linux-kvm-tools-6.2.0-1003 6.2.0-1003.3 in mantic amd64 linux-modules-6.2.0-1003-kvm 6.2.0-1003.3 in mantic amd64 linux-tools-6.2.0-1003-kvm 6.2.0-1003.3 in mantic amd64 Comment: kvm flavor merged into virtual; LP: #2025686 1 package successfully removed. ** Changed in: linux-kvm (Ubuntu Mantic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2025686 Title: RM superseded by generic Status in linux-kvm package in Ubuntu: Fix Released Status in linux-meta-kvm package in Ubuntu: Fix Released Status in linux-signed-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Mantic: Fix Released Status in linux-meta-kvm source package in Mantic: Fix Released Status in linux-signed-kvm source package in Mantic: Fix Released Bug description: RM superseded by generic generic kernel now supports initrd-less boot on VIRTIO SCSI devices. all other features were also ported to the generic kernel and/or livecd-rootfs. please remove kvm kernel from mantic. transitional packages will remain in linux-meta until after next lts release. please remove above mentioned packages from mantic-proposed and mantic-release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2025686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025686] Re: RM superseded by generic
Removing packages from mantic: linux-meta-kvm 6.2.0.1003.4 in mantic Comment: Obsolete source package subsumed by linux-meta; LP: #2025686 1 package successfully removed. ** Changed in: linux-meta-kvm (Ubuntu Mantic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2025686 Title: RM superseded by generic Status in linux-kvm package in Ubuntu: Fix Released Status in linux-meta-kvm package in Ubuntu: Fix Released Status in linux-signed-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Mantic: Fix Released Status in linux-meta-kvm source package in Mantic: Fix Released Status in linux-signed-kvm source package in Mantic: Fix Released Bug description: RM superseded by generic generic kernel now supports initrd-less boot on VIRTIO SCSI devices. all other features were also ported to the generic kernel and/or livecd-rootfs. please remove kvm kernel from mantic. transitional packages will remain in linux-meta until after next lts release. please remove above mentioned packages from mantic-proposed and mantic-release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2025686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025398] Re: RM linux-allwinner integrated into linux-riscv
Removing packages from mantic: linux-allwinner 5.19.0-1009.9 in mantic linux-allwinner-headers-5.19.0-1009 5.19.0-1009.9 in mantic amd64 linux-allwinner-headers-5.19.0-1009 5.19.0-1009.9 in mantic arm64 linux-allwinner-headers-5.19.0-1009 5.19.0-1009.9 in mantic armhf linux-allwinner-headers-5.19.0-1009 5.19.0-1009.9 in mantic i386 linux-allwinner-headers-5.19.0-1009 5.19.0-1009.9 in mantic ppc64el linux-allwinner-headers-5.19.0-1009 5.19.0-1009.9 in mantic riscv64 linux-allwinner-headers-5.19.0-1009 5.19.0-1009.9 in mantic s390x linux-allwinner-tools-5.19.0-1009 5.19.0-1009.9 in mantic riscv64 linux-buildinfo-5.19.0-1009-allwinner 5.19.0-1009.9 in mantic riscv64 linux-headers-5.19.0-1009-allwinner 5.19.0-1009.9 in mantic riscv64 linux-image-5.19.0-1009-allwinner 5.19.0-1009.9 in mantic riscv64 linux-modules-5.19.0-1009-allwinner 5.19.0-1009.9 in mantic riscv64 linux-modules-extra-5.19.0-1009-allwinner 5.19.0-1009.9 in mantic riscv64 linux-tools-5.19.0-1009-allwinner 5.19.0-1009.9 in mantic riscv64 Comment: allwinner support merged into riscv64 generic; LP: #2025398 1 package successfully removed. ** Changed in: linux-allwinner (Ubuntu Mantic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/2025398 Title: RM linux-allwinner integrated into linux-riscv Status in linux-allwinner package in Ubuntu: Fix Released Status in linux-meta-allwinner package in Ubuntu: Fix Released Status in linux-allwinner source package in Mantic: Fix Released Status in linux-meta-allwinner source package in Mantic: Fix Released Bug description: In mantic, linux-allwinner is now integrated into linux-riscv (aka generic). Please RM linux-allwinner source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2025398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025398] Re: RM linux-allwinner integrated into linux-riscv
Removing packages from mantic: linux-meta-allwinner 5.19.0.1009.9 in mantic Comment: Obsolete source package subsumed by linux-riscv; LP: #2025398 1 package successfully removed. ** Changed in: linux-meta-allwinner (Ubuntu Mantic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/2025398 Title: RM linux-allwinner integrated into linux-riscv Status in linux-allwinner package in Ubuntu: Fix Released Status in linux-meta-allwinner package in Ubuntu: Fix Released Status in linux-allwinner source package in Mantic: Fix Released Status in linux-meta-allwinner source package in Mantic: Fix Released Bug description: In mantic, linux-allwinner is now integrated into linux-riscv (aka generic). Please RM linux-allwinner source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2025398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959525] Re: Occasional no display output on 6900XT or if been idle for too long
My problems only occur when running a KDE Wayland session, not with KDE X11 sessions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959525 Title: Occasional no display output on 6900XT or if been idle for too long Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: ## No output at boot The dmesg I attached is from when nothing showed at boot. Journal output: $ journalctl -r --grep amdgpu -- Journal begins at Thu 2022-01-27 05:36:17 EST, ends at Sun 2022-01-30 15:58:40 EST. -- Jan 30 15:50:24 Y4M1-II kernel: amdgpu: probe of :0c:00.0 failed with error -110 Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: ttm finalized Jan 30 15:50:24 Y4M1-II kernel: amdgpu_init+0x77/0x1000 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_pci_probe+0x12a/0x1b0 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_driver_load_kms.cold+0x46/0x83 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_driver_unload_kms+0x43/0x70 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_device_fini+0xc5/0x1e5 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_device_ip_fini.isra.0+0x206/0x2cd [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: gmc_v10_0_sw_fini+0x33/0x40 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_bo_fini+0x12/0x50 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_ttm_fini+0xab/0x100 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_vram_mgr_fini+0xe8/0x160 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: Modules linked in: hid_generic usbhid hid amdgpu(+) iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel sysimgblt fb_sys_fops cec aesni_intel rc_core crypto_simd cryptd drm nvme ahci xhci_pci i2c_piix4 nvme_core igc libahci xhci_pci_renesas wmi Jan 30 15:50:24 Y4M1-II kernel: [drm:psp_v11_0_ring_destroy [amdgpu]] *ERROR* Fail to stop psp ring Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu: finishing device. Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fatal error during GPU init Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu_device_ip_init failed Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* hw_init of IP block failed -110 Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_gfx_enable_kcq.cold [amdgpu]] *ERROR* KCQ enable failed Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU is initialized successfully! Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: use vbios provided pptable Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU driver if version not matched Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: smu driver if version = 0x003d, smu fw if version = 0x0040, smu fw version = 0x003a4700 (58.71.0) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Will use PSP to load VCN firmware Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of GTT memory ready. Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of VRAM memory ready Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: AGP: 267894784M 0x0084 - 0x Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: GART: 512M 0x - 0x1FFF Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: VRAM: 16368M 0x0080 - 0x0083FEFF (16368M used) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SRAM ECC is not presented. Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: MEM ECC is not presented. Jan 30 15:50:24 Y4M1-II kernel: amdgpu: ATOM BIOS: 113-EXT800216-L05 Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fetched VBIOS from VFCT Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: enabling device (0006 -> 0007) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: vgaarb: deactivate vga console Jan 30 15:50:24 Y4M1-II kernel: fb0: switching to amdgpudrmfb from EFI VGA Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Topology: Add CPU node Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Virtual CRAT table created for CPU Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Ignoring ACPI CRAT on non-APU system Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu kernel modesetting enabled. Jan 30 15:50:24 Y4M1-II kernel: Kernel command line:
[Kernel-packages] [Bug 2025398] Re: RM linux-allwinner integrated into linux-riscv
** Also affects: linux-allwinner (Ubuntu Mantic) Importance: Undecided Status: Triaged ** Also affects: linux-meta-allwinner (Ubuntu Mantic) Importance: Undecided Status: Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/2025398 Title: RM linux-allwinner integrated into linux-riscv Status in linux-allwinner package in Ubuntu: Triaged Status in linux-meta-allwinner package in Ubuntu: Triaged Status in linux-allwinner source package in Mantic: Triaged Status in linux-meta-allwinner source package in Mantic: Triaged Bug description: In mantic, linux-allwinner is now integrated into linux-riscv (aka generic). Please RM linux-allwinner source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2025398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025686] [NEW] RM superseded by generic
Public bug reported: RM superseded by generic generic kernel now supports initrd-less boot on VIRTIO SCSI devices. all other features were also ported to the generic kernel and/or livecd-rootfs. please remove kvm kernel from mantic. transitional packages will remain in linux-meta until after next lts release. please remove above mentioned packages from mantic-proposed and mantic- release. ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-meta-kvm (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-signed-kvm (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-kvm (Ubuntu Mantic) Importance: Undecided Status: Triaged ** Affects: linux-meta-kvm (Ubuntu Mantic) Importance: Undecided Status: Triaged ** Affects: linux-signed-kvm (Ubuntu Mantic) Importance: Undecided Status: Triaged ** Also affects: linux-meta-kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-signed-kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-meta-kvm (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-signed-kvm (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Mantic) Status: New => Triaged ** Changed in: linux-meta-kvm (Ubuntu Mantic) Status: New => Triaged ** Changed in: linux-signed-kvm (Ubuntu Mantic) Status: New => Triaged ** Description changed: RM superseded by generic generic kernel now supports initrd-less boot on VIRTIO SCSI devices. all other features were also ported to the generic kernel and/or livecd-rootfs. please remove kvm kernel from mantic. transitional packages will remain in linux-meta until after next lts release. + + please remove above mentioned packages from mantic-proposed and mantic- + release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2025686 Title: RM superseded by generic Status in linux-kvm package in Ubuntu: Triaged Status in linux-meta-kvm package in Ubuntu: Triaged Status in linux-signed-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Mantic: Triaged Status in linux-meta-kvm source package in Mantic: Triaged Status in linux-signed-kvm source package in Mantic: Triaged Bug description: RM superseded by generic generic kernel now supports initrd-less boot on VIRTIO SCSI devices. all other features were also ported to the generic kernel and/or livecd-rootfs. please remove kvm kernel from mantic. transitional packages will remain in linux-meta until after next lts release. please remove above mentioned packages from mantic-proposed and mantic-release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2025686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wireless-regdb (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/1958918 Title: dependency on crda obsolete according to Debian Status in crda package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws-5.19 package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-lowlatency package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in wireless-regdb package in Ubuntu: Confirmed Status in crda source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux-aws-5.19 source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-lowlatency source package in Jammy: Fix Released Status in linux-oracle source package in Jammy: Fix Released Status in linux-raspi source package in Jammy: Fix Released Status in wireless-regdb source package in Jammy: Confirmed Status in crda package in Debian: Fix Released Bug description: Debian has just removed the crda package from the archive, stating that it is obsolete with current kernels: https://bugs.debian.org/1003903 We need someone to determine if this is accurate for Ubuntu as well, and if so, update the kernel packaging to not depend on crda anymore so it can be removed. wireless-regdb should stop shipping /lib/crda files which only removed crda package used to use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1958918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wireless-regdb (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/1958918 Title: dependency on crda obsolete according to Debian Status in crda package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws-5.19 package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-lowlatency package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in wireless-regdb package in Ubuntu: Confirmed Status in crda source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux-aws-5.19 source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-lowlatency source package in Jammy: Fix Released Status in linux-oracle source package in Jammy: Fix Released Status in linux-raspi source package in Jammy: Fix Released Status in wireless-regdb source package in Jammy: Confirmed Status in crda package in Debian: Fix Released Bug description: Debian has just removed the crda package from the archive, stating that it is obsolete with current kernels: https://bugs.debian.org/1003903 We need someone to determine if this is accurate for Ubuntu as well, and if so, update the kernel packaging to not depend on crda anymore so it can be removed. wireless-regdb should stop shipping /lib/crda files which only removed crda package used to use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1958918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-aws-5.19 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/1958918 Title: dependency on crda obsolete according to Debian Status in crda package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws-5.19 package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-lowlatency package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in wireless-regdb package in Ubuntu: Confirmed Status in crda source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux-aws-5.19 source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-lowlatency source package in Jammy: Fix Released Status in linux-oracle source package in Jammy: Fix Released Status in linux-raspi source package in Jammy: Fix Released Status in wireless-regdb source package in Jammy: Confirmed Status in crda package in Debian: Fix Released Bug description: Debian has just removed the crda package from the archive, stating that it is obsolete with current kernels: https://bugs.debian.org/1003903 We need someone to determine if this is accurate for Ubuntu as well, and if so, update the kernel packaging to not depend on crda anymore so it can be removed. wireless-regdb should stop shipping /lib/crda files which only removed crda package used to use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1958918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
I did an check and can confirm that the chromium-browser as installed by the usual 22.04 package is *NOT* affected. But Google chrome well as google-chrome-beta installed by the PPA deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main do show the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006042] Re: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram
Got a similar issue with Asus K513. It happens every time I suspend with a type-C dock connected (the laptop does not support the HDMI out on type-C, so I'm only using it as a USB 3.0 hub). The power indicator starts blinking with a strange pattern: 0.1 sec of light every two seconds. And I have to press the POWER button for an unusually long time (10-15 seconds or more) to get the reboot. Other than that, this laptop tends to crash when resuming from the suspend much more often if you have the SATA SSD installed. Also, it might smth to have with the light-locker which switches the console when locking/unlocking the screen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006042 Title: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram Status in linux package in Ubuntu: Confirmed Bug description: Hi, After waking up from suspend to RAM, my computer actually wakes up but can sometimes then hang on a black screen (no prompt, nothing displayed, screen is active). This issue happens quite frequently but seems rather random. I think certain circumstances lower the frequency (I'll elaborate in the report). First of all, I'm not exactly sure when it started but I would say first notable frequent occurrences were around summer 2021 (yes, I'm late, sorry for that). When this happens, Algr+SysRQ+[usb] is unresponsive. Or at least that's what I used to believe as it used to be true as I always tried from the laptop integrated keyboard. Until I connected an USB-C mechanical keyboard, from which I'm *sometimes* able to use the magic keys (not always, and with a lot of lag, but still). If magic keys are unresponsive, I need to hard reset/long press power. There is nothing unusual before that in syslog nor kern.log, at least not that I know of. Except the ^@^@^@ characters when I had to hard reset the computer. If I leave the laptop like that for a while, it eventually reboots by itself and stays on the FDE passphrase prompt (which is not nice as the screen can then stay on for a very long like that if I did not notice). I'm running KDE/Plasma desktop, and this issue has happened regardless of the display manager. I used to run Xorg but now I'm on wayland flavor (mostly to alleviate firefox rendering/compositing issues). This also seems unrelated to external screen being connected or not, as it happened in the past regardless of that parameter. Although, it *seems* frequency has lowered a bit since I changed the way I wake up my laptop. Higher frequency (almost every day): - no external screen or external screen connected to HDMI port - waking up from integrated keyboard power button short press Lower frequency (one to multiple times a week, but somewhat irregular, since ~ 2 months ago): - external screen connected to USB-C port - mechanical keyboard connected to USB-C port of screen - waking up from the mechanical keyboard It also seems to happen more frequently if I wake up the computer, do some very fast task and send it to sleep in under a few minutes. It's not guaranteed to happen, but seems to highly increase the probability. Also, this might be related so I'm adding that bit: I had to disable shutting the screen Off in energy saving settings, as enabling that option would trigger a similar behavior after a break long enough for that setting to trigger. I would come back on a laptop having self-rebooted and waiting for my input on the FDE passphrase prompt. During ACPI options testing, I noticed that setting might cause the sleep order to get cancelled. From that, I suspect in that case the laptop would go to sleep, then wake up immediately, which could have been triggering the bug as I described previously that rapid state changes would increase probability. Then as I described earlier, if I do nothing when this happens, the computer eventually reboots. This is only speculation as I'm usually not here to observe the behavior (this mostly happened during lunch breaks, which are long enough for all of these steps to happen). I disabled screen turn-off energy saving option a long while ago and have taken the habit of manually suspending to RAM when I intend on going away from the computer for more than a few minutes. As I described above, I've tried a few changes to check for behavior but that was a few months ago and I don't clearly remember all scenario. What I remember is that changing any of these did not resolve my issue and some even prevented my computer to even suspend to RAM properly (waking up immediately after). Among the options I tried is: - booting with a previous kernel, but then it's been happening for so long this would obviously not work (just for the sake of completion) - booting on latest mainstream
[Kernel-packages] [Bug 2025538] Re: Unrequested kernel update
Today apt want's to update my nvidia driver from 510.108.03-0ubuntu0.22.04.1 to 525.125.06-0ubuntu0.22.04.1 Based on the bad experience of the unwanted kernel update I'm not sure whether I should take the risk. Hopefully one of the maintainers reacts to this bug soon and gives more advice about how to solve the issue and clean up the system -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025661] Re: Update Mantic package to OpenZFS 2.2.0-RC1
For the record, I personally ran into this specific issue with some moderate use of a ZFS pool: [Mon Jul 3 10:07:56 2023] RIP: 0010:__list_del_entry_valid+0x0/0x70 [Mon Jul 3 10:07:56 2023] Code: 39 c0 0f 85 89 cf 4b 00 48 39 d7 0f 84 69 cf 4b 00 4c 39 c7 0f 84 60 cf 4b 00 b8 01 00 00 00 c3 cc cc cc cc 66 0f 1f 44 00 00 <48> 8b 17 48 8b 4f 08 48 85 d2 0f 84 8d cf 4b 00 48 85 c9 0f 84 e2 [Mon Jul 3 10:07:56 2023] RSP: 0018:b517c1503d00 EFLAGS: 00010283 [Mon Jul 3 10:07:56 2023] RAX: 8000 RBX: 99a572c070d8 RCX: [Mon Jul 3 10:07:56 2023] RDX: 0001 RSI: 88fa639d RDI: dead0100 [Mon Jul 3 10:07:56 2023] RBP: 999f44344800 R08: R09: 80200011 [Mon Jul 3 10:07:56 2023] R10: 000a R11: 0001 R12: 99a4c3b867b0 [Mon Jul 3 10:07:56 2023] R13: 99a572c071e0 R14: dead0100 R15: dead0100 [Mon Jul 3 10:07:56 2023] FS: () GS:99ae8008() knlGS: [Mon Jul 3 10:07:56 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Jul 3 10:07:56 2023] CR2: 00c01ea77000 CR3: 0001283c8005 CR4: 003706e0 [Mon Jul 3 10:07:56 2023] DR0: DR1: DR2: [Mon Jul 3 10:07:56 2023] DR3: DR6: fffe0ff0 DR7: 0400 [Mon Jul 3 10:07:56 2023] Call Trace: [Mon Jul 3 10:07:56 2023] [Mon Jul 3 10:07:56 2023] zil_lwb_flush_vdevs_done+0xfe/0x2c0 [zfs] [Mon Jul 3 10:07:56 2023] zio_done+0x2c2/0x10f0 [zfs] [Mon Jul 3 10:07:56 2023] zio_execute+0x80/0x120 [zfs] [Mon Jul 3 10:07:56 2023] taskq_thread+0x2ba/0x4e0 [spl] [Mon Jul 3 10:07:56 2023] ? wake_up_q+0x90/0x90 [Mon Jul 3 10:07:56 2023] ? zio_ddt_child_write_done+0xd0/0xd0 [zfs] [Mon Jul 3 10:07:56 2023] ? taskq_thread_spawn+0x50/0x50 [spl] [Mon Jul 3 10:07:56 2023] kthread+0xe6/0x110 [Mon Jul 3 10:07:56 2023] ? kthread_complete_and_exit+0x20/0x20 [Mon Jul 3 10:07:56 2023] ret_from_fork+0x1f/0x30 [Mon Jul 3 10:07:56 2023] The bug has been fixed since commit 4f583a827e3b40f3bdfba78db75e1fe1feff122c via https://github.com/openzfs/zfs/commit/55b1842f92a24fe7192d129bca7b60882080d31a, which is present in RC1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2025661 Title: Update Mantic package to OpenZFS 2.2.0-RC1 Status in zfs-linux package in Ubuntu: New Bug description: Hello, OpenZFS 2.2.0-RC1 has been released a couple of days ago. Could you update the Mantic package to this version? I'm personally asking because I'm running into a bug which has been fixed since commit 4f583a827e3b40f3bdfba78db75e1fe1feff122c, which is the version currently packaged. Thanks a lot! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2025661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025616] Re: kernel Firmware Bug: TSC ADJUST differs failures during suspend
** Package changed: ubuntu => linux-nvidia (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2025616 Title: kernel Firmware Bug: TSC ADJUST differs failures during suspend Status in linux-nvidia package in Ubuntu: New Bug description: [Summary] Discoverd kernel error message during suspend stress test test case id: power-management/suspend_30_cycles_with_reboots collected log ~~~ High failures: s3: 180 failures HIGH Kernel message: [38779.612837] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5266754042. Restoring (x 3) HIGH Kernel message: [38839.622411] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5295340520. Restoring (x 3) HIGH Kernel message: [38868.467564] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5270514862. Restoring (x 3) HIGH Kernel message: [38897.419897] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5275834616. Restoring (x 3) HIGH Kernel message: [38926.135900] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5249511520. Restoring (x 3) HIGH Kernel message: [38955.114760] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5252454094. Restoring (x 3) HIGH Kernel message: [38983.860142] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5270474360. Restoring (x 3) HIGH Kernel message: [39012.819868] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5264045578. Restoring (x 3) ~~~ [Failure rate] 1/1 [Additional information] CID: 201711-25989 SKU: DGX-1 Station system-manufacturer: NVIDIA system-product-name: DGX Station bios-version: 0406 CPU: Intel(R) Xeon(R) CPU E5-2698 v4 @ 2.20GHz (40x) GPU: 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1db2] (rev a1) 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1db2] (rev a1) 0e:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1db2] (rev a1) 0f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1db2] (rev a1) nvidia-driver-version: 525.105.17 kernel-version: 5.15.0-1028-nvidia [Stage] Issue reported and logs collected at a later stage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2025616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Canonical has provided a signature for an exact set of bytes in the .ko file. The packaging needs to relink the object files into that exact set of bytes on the target system for the signature to match. The relinking is required for license compliance AIUI. binutils does the linking. If you use a different version of binutils, it may generate a different set of bytes that fails the signature check. Can you elaborate on what you think Ubuntu should be doing differently? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025675] [NEW] Realtek Bluetooth Radio ID 6655:8771 cannot connect after update
Public bug reported: After updating my system this morning, about six hours ago, my Bluetooth radio (Model number: Insignia ns-pa3bt5a2b22) (Bus 001 Device 002: ID 6655:8771 Realtek Bluetooth Radio) stopped working entirely. ubuntu-version: Ubuntu 22.04.2 LTS linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.14 Expected behavior: Bluetooth should connect, scanning for new devices should complete and list all discoverable devices. Actual behavior: Bluetooth shows up in the settings interface as expected, but does not connect to or show any previously connected devices (Logitech MX Master 3s, k850, Bose QC35), and scans for new devices forever. Additional information: In initial debugging stages, sudo dmesg | grep -i 'blue' Gave: ... [ 85.034768] Bluetooth: hci0: Ignoring error of Inquiry Cancel command Following the steps given here before I found this bug: https://askubuntu.com/questions/1398873/bluetooth-5-0-adapter-help did not resolve the problem, but did cause the dmesg to go away, such that I now just get: [ 1827.904469] usb 1-1: Product: Bluetooth Radio ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2025675 Title: Realtek Bluetooth Radio ID 6655:8771 cannot connect after update Status in linux-firmware package in Ubuntu: New Bug description: After updating my system this morning, about six hours ago, my Bluetooth radio (Model number: Insignia ns-pa3bt5a2b22) (Bus 001 Device 002: ID 6655:8771 Realtek Bluetooth Radio) stopped working entirely. ubuntu-version: Ubuntu 22.04.2 LTS linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.14 Expected behavior: Bluetooth should connect, scanning for new devices should complete and list all discoverable devices. Actual behavior: Bluetooth shows up in the settings interface as expected, but does not connect to or show any previously connected devices (Logitech MX Master 3s, k850, Bose QC35), and scans for new devices forever. Additional information: In initial debugging stages, sudo dmesg | grep -i 'blue' Gave: ... [ 85.034768] Bluetooth: hci0: Ignoring error of Inquiry Cancel command Following the steps given here before I found this bug: https://askubuntu.com/questions/1398873/bluetooth-5-0-adapter-help did not resolve the problem, but did cause the dmesg to go away, such that I now just get: [ 1827.904469] usb 1-1: Product: Bluetooth Radio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2025675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025672] Re: Support Realtek RTL8852CE WiFi 6E/BT Combo
Still figuring out potential upstream bluetooth firmware regression in https://lore.kernel.org/linux-firmware/20230703134824.7795b277@smeagol/ ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: oem-priority originate-from-2024125 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025672 Title: Support Realtek RTL8852CE WiFi 6E/BT Combo Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: WIFI Driver: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/log/drivers/net/wireless/realtek/rtw89 BT Driver: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/drivers/bluetooth/btrtl.c?id=8b1d66b50437b65ef109f32270bd936ca5437a83 (>= 5.18) https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/drivers/bluetooth/btrtl.c?id=9a24ce5e29b15c4c6b0c89c04f9df6ce14addefa (>= 6.4) WIFI FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/rtw89 BT FW: rtl_bt/rtl8852cu_fw.bin rtl_bt/rtl8852cu_config.bin To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025672] [NEW] Support Realtek RTL8852CE WiFi 6E/BT Combo
Public bug reported: WIFI Driver: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/log/drivers/net/wireless/realtek/rtw89 BT Driver: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/drivers/bluetooth/btrtl.c?id=8b1d66b50437b65ef109f32270bd936ca5437a83 (>= 5.18) https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/drivers/bluetooth/btrtl.c?id=9a24ce5e29b15c4c6b0c89c04f9df6ce14addefa (>= 6.4) WIFI FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/rtw89 BT FW: rtl_bt/rtl8852cu_fw.bin rtl_bt/rtl8852cu_config.bin ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: oem-priority originate-from-2024125 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025672 Title: Support Realtek RTL8852CE WiFi 6E/BT Combo Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: WIFI Driver: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/log/drivers/net/wireless/realtek/rtw89 BT Driver: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/drivers/bluetooth/btrtl.c?id=8b1d66b50437b65ef109f32270bd936ca5437a83 (>= 5.18) https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/drivers/bluetooth/btrtl.c?id=9a24ce5e29b15c4c6b0c89c04f9df6ce14addefa (>= 6.4) WIFI FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/rtw89 BT FW: rtl_bt/rtl8852cu_fw.bin rtl_bt/rtl8852cu_config.bin To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024774] Re: AMD Rembrandt / Phoenix PSR-SU related freezes
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu Lunar)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2024774
Title:
AMD Rembrandt / Phoenix PSR-SU related freezes
Status in Linux Firmware:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Confirmed
Status in linux-firmware source package in Lunar:
Confirmed
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[ Impact ]
When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU).
After a non-deterministic amount of time the system may hang with a message
like this in the logs:
"[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed
out]"
Affects users of laptops that contain:
* AMD Rembrandt (Yellow Carp) or AMD Phoenix (Pink Sardine) chips
* eDP panels with Parade TCONs (8-03 and 8-01 both reported to fail)
[ Test Plan ]
* Test an affected laptop with the newer firmware and ensure that PSR-SU
function can be enabled and system is stable.
* Ensure other functions such as hotplugging monitors and suspending
continue to work.
[ Where problems could occur ]
* Affected firmware only is loaded on Rembrandt and Phoenix laptops.
Problems would be localized to these machines.
[ Other Info ]
The minimum firmware needed to help these hangs:
* Rembrandt: 0x43a or later
* Phoenix: 0x8001000 or later
The following commit upgrades the firmware for Rembrandt
(amdgpu/yellow_carp_dmcub.bin) to 0x43c:
9dbd8ec2 ("amdgpu: DMCUB updates for various AMDGPU asics")
The following commit upgrades the firmware for Phoenix
(amdgpu/dcn_3_1_4_dmcub.bin) to 0x8001a00:
045b2136 ("amdgpu: update DMCUB to v0.0.172.0 for various AMDGPU ASICs")
The TCON in a given laptop can be identified from the DPCD with this script:
https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2024774/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024774] Re: AMD Rembrandt / Phoenix PSR-SU related freezes
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2024774
Title:
AMD Rembrandt / Phoenix PSR-SU related freezes
Status in Linux Firmware:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Confirmed
Status in linux-firmware source package in Lunar:
Confirmed
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[ Impact ]
When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU).
After a non-deterministic amount of time the system may hang with a message
like this in the logs:
"[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed
out]"
Affects users of laptops that contain:
* AMD Rembrandt (Yellow Carp) or AMD Phoenix (Pink Sardine) chips
* eDP panels with Parade TCONs (8-03 and 8-01 both reported to fail)
[ Test Plan ]
* Test an affected laptop with the newer firmware and ensure that PSR-SU
function can be enabled and system is stable.
* Ensure other functions such as hotplugging monitors and suspending
continue to work.
[ Where problems could occur ]
* Affected firmware only is loaded on Rembrandt and Phoenix laptops.
Problems would be localized to these machines.
[ Other Info ]
The minimum firmware needed to help these hangs:
* Rembrandt: 0x43a or later
* Phoenix: 0x8001000 or later
The following commit upgrades the firmware for Rembrandt
(amdgpu/yellow_carp_dmcub.bin) to 0x43c:
9dbd8ec2 ("amdgpu: DMCUB updates for various AMDGPU asics")
The following commit upgrades the firmware for Phoenix
(amdgpu/dcn_3_1_4_dmcub.bin) to 0x8001a00:
045b2136 ("amdgpu: update DMCUB to v0.0.172.0 for various AMDGPU ASICs")
The TCON in a given laptop can be identified from the DPCD with this script:
https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2024774/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025670] [NEW] amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged
Public bug reported: Upstream bugzilla https://bugzilla.kernel.org/show_bug.cgi?id=217571 This is specifically when a system advertises support for PMF, but doesn't support static power slider for any reason. Upstream fix in https://github.com/torvalds/linux/commit/146b6f6855e7656e8329910606595220c761daac, which has been backported to v6.1.36 (oem-6.1 in v6.1.34 now), v6.2.15 (linux/lunar in v6.2.13), v6.3.10 (linux/mantic in v6.3.8), v6.4. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025670 Title: amd_pmf: AMD 7840HS cpufreq locked at 400-544MHz after power unplugged Status in linux package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: New Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: Upstream bugzilla https://bugzilla.kernel.org/show_bug.cgi?id=217571 This is specifically when a system advertises support for PMF, but doesn't support static power slider for any reason. Upstream fix in https://github.com/torvalds/linux/commit/146b6f6855e7656e8329910606595220c761daac, which has been backported to v6.1.36 (oem-6.1 in v6.1.34 now), v6.2.15 (linux/lunar in v6.2.13), v6.3.10 (linux/mantic in v6.3.8), v6.4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025538] Re: Unrequested kernel update
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
The problem seems to come from a wrong suggestion of Nvidia proprietary driver packages, where Ubuntu logic (likely from the “ubuntu-drivers- common” package) hints towards drivers that depend on a kernel stack that’s not installed, which triggers those kernel installations as well, because dependencies. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018286] Re: amdgpu driver failing repeatedly
*** This bug is a duplicate of bug 1959525 *** https://bugs.launchpad.net/bugs/1959525 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018286 Title: amdgpu driver failing repeatedly Status in linux package in Ubuntu: Confirmed Bug description: From time to time my KDE desktop becomes unresponsive. In the kernel log I find errors like the following repeating incessantly: 03:34.977226 kernel: [ 8355.577322] [drm] PTB located at 0x00F400A0 03:34.977232 kernel: [ 8355.577356] [drm] PSP is resuming... 03:34.996756 kernel: [ 8355.597239] [drm] reserve 0x40 from 0xf47fc0 for PSP TMR 03:35.204496 kernel: [ 8355.805718] amdgpu :05:00.0: amdgpu: RAS: optional ras ta ucode is not available 03:35.236504 kernel: [ 8355.836957] amdgpu :05:00.0: amdgpu: RAP: optional rap ta ucode is not available 03:35.236523 kernel: [ 8355.836962] amdgpu :05:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available 03:35.876947 kernel: [ 8356.474483] [drm] kiq ring mec 2 pipe 1 q 0 03:36.168521 kernel: [ 8356.767847] amdgpu :05:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) 03:36.168545 kernel: [ 8356.768191] [drm:amdgpu_gfx_enable_kcq [amdgpu]] *ERROR* KCQ enable failed 03:36.168552 kernel: [ 8356.768542] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 03:36.168554 kernel: [ 8356.768895] amdgpu :05:00.0: amdgpu: GPU reset(179) failed 03:36.168559 kernel: [ 8356.769009] amdgpu :05:00.0: amdgpu: GPU reset end with ret = -110 03:36.168565 kernel: [ 8356.769017] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -110 03:46.328574 kernel: [ 8366.926277] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=19364, emitted seq=19366 03:46.328593 kernel: [ 8366.927059] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 03:46.328599 kernel: [ 8366.927731] amdgpu :05:00.0: amdgpu: GPU reset begin! 03:46.501074 kernel: [ 8367.098277] amdgpu :05:00.0: amdgpu: GPU reset succeeded, trying to resume 03:46.501094 kernel: [ 8367.098806] [drm] PCIE GART of 1024M enabled. 03:46.501099 kernel: [ 8367.098811] [drm] PTB located at 0x00F400A0 03:46.501109 kernel: [ 8367.098848] [drm] PSP is resuming... 03:46.521070 kernel: [ 8367.118736] [drm] reserve 0x40 from 0xf47fc0 for PSP TMR 03:46.728491 kernel: [ 8367.326740] amdgpu :05:00.0: amdgpu: RAS: optional ras ta ucode is not available 03:46.760475 kernel: [ 8367.358158] amdgpu :05:00.0: amdgpu: RAP: optional rap ta ucode is not available 03:46.760482 kernel: [ 8367.358161] amdgpu :05:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available 03:47.384498 kernel: [ 8367.985147] [drm] kiq ring mec 2 pipe 1 q 0 03:47.680540 kernel: [ 8368.279937] amdgpu :05:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) 03:47.680561 kernel: [ 8368.280273] [drm:amdgpu_gfx_enable_kcq [amdgpu]] *ERROR* KCQ enable failed 03:47.680565 kernel: [ 8368.280618] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 03:47.680570 kernel: [ 8368.280976] amdgpu :05:00.0: amdgpu: GPU reset(180) failed 03:47.680575 kernel: [ 8368.281055] amdgpu :05:00.0: amdgpu: GPU reset end with ret = -110 03:47.680580 kernel: [ 8368.281058] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -110 03:57.848521 kernel: [ 8378.446230] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=19366, emitted seq=19367 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.2.0-21-generic 6.2.0-21.21 ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6 Uname: Linux 6.2.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zfsdt 3122 F wireplumber /dev/snd/controlC0: zfsdt 3122 F wireplumber /dev/snd/seq:zfsdt 3115 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Tue May 2 11:13:11 2023 InstallationDate: Installed on 2021-07-01 (669 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated Camera (1280x720@30) Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root
[Kernel-packages] [Bug 2025661] [NEW] Update Mantic package to OpenZFS 2.2.0-RC1
Public bug reported: Hello, OpenZFS 2.2.0-RC1 has been released a couple of days ago. Could you update the Mantic package to this version? I'm personally asking because I'm running into a bug which has been fixed since commit 4f583a827e3b40f3bdfba78db75e1fe1feff122c, which is the version currently packaged. Thanks a lot! ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2025661 Title: Update Mantic package to OpenZFS 2.2.0-RC1 Status in zfs-linux package in Ubuntu: New Bug description: Hello, OpenZFS 2.2.0-RC1 has been released a couple of days ago. Could you update the Mantic package to this version? I'm personally asking because I'm running into a bug which has been fixed since commit 4f583a827e3b40f3bdfba78db75e1fe1feff122c, which is the version currently packaged. Thanks a lot! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2025661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025243] Re: Introduce the NVIDIA 535-server ERD driver series
** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** No longer affects: nvidia-graphics-drivers-535 (Ubuntu Jammy) ** No longer affects: nvidia-graphics-drivers-535 (Ubuntu Kinetic) ** No longer affects: nvidia-graphics-drivers-535 (Ubuntu Lunar) ** Also affects: fabric-manager-525 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: fabric-manager-525 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: fabric-manager-525 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-535 (Ubuntu) ** No longer affects: fabric-manager-525 (Ubuntu Bionic) ** No longer affects: fabric-manager-525 (Ubuntu Focal) ** No longer affects: nvidia-graphics-drivers-535 (Ubuntu Bionic) ** No longer affects: nvidia-graphics-drivers-535 (Ubuntu Focal) ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-525 (Ubuntu) Importance: Undecided Status: New ** Also affects: fabric-manager-525 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Introduce the NVIDIA 535-server ERD driver series + Introduce the NVIDIA 535-server ERD driver series, and enable arm64 for 535, 525, 525-server in Focal ** Description changed: Introduce the NVIDIA 535-server ERD driver series, enabling the -open kernel module. Release notes: https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-54-03/index.html + + + Changelogs for the drivers in focal: + + + nvidia-graphics-drivers-525 (525.125.06-0ubuntu0.20.04.3) focal; urgency=medium + + [ Dimitri John Ledkov ] + * debian: + - Enable arm64 builds (LP: #2025243). + * debian/templates: + - Encode amd64-only libraries and binaries. + + + nvidia-graphics-drivers-535 (535.54.03-0ubuntu0.20.04.4) focal; urgency=medium + + [ Dimitri John Ledkov ] + * templates: encode amd64-only libraries and binaries + * debian: Enable arm64 builds (LP: #2025243). + + -- Alberto Milone Mon, 03 Jul 2023 + 13:34:05 + + + + nvidia-graphics-drivers-525-server (525.125.06-0ubuntu0.20.04.2) focal; urgency=medium + + [ Alberto Milone ] + * debian/rules: + - Drop the unused generate-nvidia-icd-json target; + + [ Dimitri John Ledkov ] + * debian: + - Enable arm64 builds (LP: #2025243). + * debian/templates: + - Encode amd64-only libraries and binaries. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2025243 Title: Introduce the NVIDIA 535-server ERD driver series, and enable arm64 for 535, 525, 525-server in Focal Status in fabric-manager-525 package in Ubuntu: New Status in libnvidia-nscq-525 package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in nvidia-graphics-drivers-525-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-525 source package in Bionic: New Status in nvidia-graphics-drivers-525-server source package in Bionic: New Status in nvidia-graphics-drivers-525 source package in Focal: New Status in nvidia-graphics-drivers-525-server source package in Focal: In Progress Status in nvidia-graphics-drivers-525 source package in Jammy: New Status in nvidia-graphics-drivers-525-server source package in Jammy: In Progress Status in nvidia-graphics-drivers-525 source package in Kinetic: New Status in nvidia-graphics-drivers-525-server source package in Kinetic: In Progress Status in nvidia-graphics-drivers-525 source package in Lunar: New Status in nvidia-graphics-drivers-525-server source package in Lunar: In Progress Bug description: Introduce the NVIDIA 535-server ERD driver series, enabling the -open kernel module. Release notes: https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-54-03/index.html Changelogs for the drivers in focal: nvidia-graphics-drivers-525 (525.125.06-0ubuntu0.20.04.3) focal; urgency=medium [ Dimitri John Ledkov ] * debian: - Enable arm64 builds (LP: #2025243). * debian/templates: - Encode amd64-only libraries and binaries. nvidia-graphics-drivers-535 (535.54.03-0ubuntu0.20.04.4) focal; urgency=medium [ Dimitri John Ledkov ] * templates: encode amd64-only libraries and binaries * debian: Enable arm64 builds (LP: #2025243). --
[Kernel-packages] [Bug 2025640] Re: Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to 535.54.03 video input cuts out
1. You are not supposed to confirm your own bug reports 2. You are not running Ubuntu, but Linux Mint. Support for Linux Mint can be found at https://www.linuxmint.com/contactus.php and https://forums.linuxmint.com/ ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2025640 Title: Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to 535.54.03 video input cuts out Status in nvidia-graphics-drivers-535 package in Ubuntu: Invalid Bug description: https://forums.developer.nvidia.com/t/ubuntu-22-04-in-the-middle-of- updating-drivers-from-530-41-03-to-535-54-03-video-input-cuts- out/258588 https://forums.linuxmint.com/viewtopic.php?p=2344294 timeline 10:36 - 10:39 switch to TTY not helped, SSH not tested I don't have a keyboard shortcut to restart X. After emergency sync, reboot (sysrq) is all fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2025640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025530] Re: package linux-image-6.2.0-1005-oracle 6.2.0-1005.5 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Same Here, impossible to update using APt or ubuntu update: sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libnvidia-cfg1-515 libnvidia-common-515 libnvidia-compute-515 libnvidia-compute-515:i386 libnvidia-decode-515 libnvidia-decode-515:i386 libnvidia-encode-515 libnvidia-encode-515:i386 libnvidia-extra-515 libnvidia-fbc1-515 libnvidia-fbc1-515:i386 libnvidia-gl-515 libnvidia-gl-515:i386 linux-signatures-nvidia-6.2.0-1005-oracle nvidia-compute-utils-515 nvidia-kernel-source-515 nvidia-utils-515 xserver-xorg-video-nvidia-515 Use 'sudo apt autoremove' to remove them. The following packages have been kept back: linux-modules-nvidia-515-generic-hwe-22.04 linux-signatures-nvidia-6.2.0-24-generic The following packages will be upgraded: linux-firmware 1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 2 not fully installed or removed. Need to get 281 MB of archives. After this operation, 3.072 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://br.archive.ubuntu.com/ubuntu lunar-updates/main amd64 linux-firmware all 20230323.gitbcdcfbcf-0ubuntu1.2 [281 MB] Fetched 281 MB in 20s (14,3 MB/s) (Reading database ... 280370 files and directories currently installed.) Preparing to unpack .../linux-firmware_20230323.gitbcdcfbcf-0ubuntu1.2_all.deb ... Unpacking linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) over (20230323.gitbcdcfbcf-0ubuntu1.1) ... Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic Setting up linux-image-6.2.0-1007-lowlatency (6.2.0-1007.7) ... I: /boot/initrd.img is now a symlink to initrd.img-6.2.0-1007-lowlatency Setting up linux-image-6.2.0-1005-oracle (6.2.0-1005.5) ... I: /boot/initrd.img.old is now a symlink to initrd.img-6.2.0-1005-oracle Processing triggers for linux-image-6.2.0-1007-lowlatency (6.2.0-1007.7) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-1007-lowlatency Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Error! Your kernel headers for kernel 6.2.0-1007-lowlatency cannot be found at /lib/modules/6.2.0-1007-lowlatency/build or /lib/modules/6.2.0-1007-lowlatency/source. Please install the linux-headers-6.2.0-1007-lowlatency package or use the --kernelsourcedir option to tell DKMS where it's located. Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Error! Your kernel headers for kernel 6.2.0-1007-lowlatency cannot be found at /lib/modules/6.2.0-1007-lowlatency/build or /lib/modules/6.2.0-1007-lowlatency/source. Please install the linux-headers-6.2.0-1007-lowlatency package or use the --kernelsourcedir option to tell DKMS where it's located. dkms autoinstall on 6.2.0-1007-lowlatency/x86_64 failed for evdi(1) nvidia(1) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-1007-lowlatency (--configure): installed linux-image-6.2.0-1007-lowlatency package post-installation script subprocess returned error exit status 1 Processing triggers for linux-image-6.2.0-1005-oracle (6.2.0-1005.5) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-1005-oracle Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Error! Your kernel headers for kernel 6.2.0-1005-oracle cannot be found at /lib/modules/6.2.0-1005-oracle/build or /lib/modules/6.2.0-1005-oracle/source. Please install the linux-headers-6.2.0-1005-oracle package or use the --kernelsourcedir option to tell DKMS where it's located. Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Error! Your kernel headers for kernel 6.2.0-1005-oracle cannot be found at /lib/modules/6.2.0-1005-oracle/build or /lib/modules/6.2.0-1005-oracle/source. Please install the linux-headers-6.2.0-1005-oracle package or use the --kernelsourcedir option to tell DKMS where it's located. dkms autoinstall on 6.2.0-1005-oracle/x86_64 failed for evdi(1) nvidia(1) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package
[Kernel-packages] [Bug 2025640] [NEW] Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to 535.54.03 video input cuts out
Public bug reported: https://forums.developer.nvidia.com/t/ubuntu-22-04-in-the-middle-of- updating-drivers-from-530-41-03-to-535-54-03-video-input-cuts-out/258588 https://forums.linuxmint.com/viewtopic.php?p=2344294 timeline 10:36 - 10:39 switch to TTY not helped, SSH not tested After emergency sync, reboot (sysrq) is all fine. ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 22.04.03 530 535 driver nvidia output update video ** Tags removed: from to ** Tags added: 22.04.03 driver no signal ** Tags removed: no signal ** Tags added: output video ** Package changed: update-manager (Ubuntu) => nvidia-graphics- drivers-535 (Ubuntu) ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Confirmed ** Description changed: https://forums.developer.nvidia.com/t/ubuntu-22-04-in-the-middle-of- updating-drivers-from-530-41-03-to-535-54-03-video-input-cuts-out/258588 + + https://forums.linuxmint.com/viewtopic.php?p=2344294 timeline 10:36 - 10:39 switch to TTY not helped, SSH not tested After emergency sync, reboot (sysrq) is all fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2025640 Title: Ubuntu 22.04 in the middle of updating drivers from 530.41.03 to 535.54.03 video input cuts out Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: https://forums.developer.nvidia.com/t/ubuntu-22-04-in-the-middle-of- updating-drivers-from-530-41-03-to-535-54-03-video-input-cuts- out/258588 https://forums.linuxmint.com/viewtopic.php?p=2344294 timeline 10:36 - 10:39 switch to TTY not helped, SSH not tested After emergency sync, reboot (sysrq) is all fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2025640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025560] Re: lubuntu does not boot after upgrade
Kerjes thanks a lot for the info Worked for me as well! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025560 Title: lubuntu does not boot after upgrade Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 This morning upgrade installed a bunch of new kernels which made my computer unbootable. Manged to boot with old kernel: 5.15.0-76-generic, and none of new ones work. From /var/log/apt/history.log: Start-Date: 2023-07-02 12:06:38 Commandline: aptdaemon role='role-upgrade-system' sender=':1.69' Install: linux-modules-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1, automatic), linux-objects-nvidia-535-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-6.1.0-1015-oem:amd64 (6.1.0-1015.15+2, automatic), linux-image-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-signatures-nvidia-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), dctrl-tools:amd64 (2.24-3build2, automatic), linux-signatures-nvidia-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-modules-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-image- 5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic), linux-modules-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), nvidia-firmware-535-535.54.03:amd64 (535.54.03-0ubuntu0.22.04.1, automatic), linux-modules-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-objects-nvidia-535-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-image-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), linux-signatures-nvidia-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-objects-nvidia-535-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-objects-nvidia-535-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-6.1.0-1015-oem:amd64 (6.1.0-1015.15, automatic), linux-image-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), linux-image-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-image-5.19.0-1026-oracle:amd64 (5.19.0- 1026.29~22.04.1, automatic), linux-modules-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), linux-objects-nvidia-535-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-image-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-objects-nvidia-535-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-modules-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), dkms:amd64 (2.8.7-2ubuntu2.1, automatic), linux-modules-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-modules-5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic) Works to start in recovery mode on any kernel and guessing that the problem is related to the nvidia-driver, which is native: neofetch `-mddhddmss` kris@lubuntu ./mdhh. :mdhhhm` OS: Lubuntu 22.04.2 LTS x86_64 :ymhhhyyhy: Kernel: 5.15.0-76-generic `odhyyyhy+-./syo` Uptime: 22 mins `hhy..:oyhhhy-`:osso/..:/++oosyyyh`Packages: 2100 (dpkg), 13 (snap) dhhs .-/sys`shhhsShell: bash 5.1.16 :hhhy` yso/:+syhy/yhshh: Resolution: 1920x1080, 1920x1080, 1920x1080 ho. +hhhys++oyyyh-yhs DE: LXQt 0.17.1 hhs-`/syyssyy:-yh WM: Openbox
[Kernel-packages] [Bug 2025460] Re: night light stopped working
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2025460/+attachment/5683537/+files/journal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2025460 Title: night light stopped working Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Same as #1752680 but happening from cold boot and won't work again after disabling/re-enabling night light. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-76.83~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 30 10:25:21 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-24 (978 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2025460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025460] Re: night light stopped working
It's now working again without (known) action (update?). I attach the files anyway in case the problem is back in the future. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2025460/+attachment/5683536/+files/lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2025460 Title: night light stopped working Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Same as #1752680 but happening from cold boot and won't work again after disabling/re-enabling night light. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-76.83~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 30 10:25:21 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-24 (978 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2025460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968604] Re: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3.14 --- linux-firmware (20220329.git681281e4-0ubuntu3.14) jammy; urgency=medium * rtl8761b usb bluetooth doesn't work following reboot until unplug/replug (LP: #1968604) - rtl_bt: Update RTL8761B BT UART firmware to 0x9DC6_D922 - rtl_bt: Update RTL8761B BT USB firmware to 0xDFC6_D922 -- Juerg Haefliger Mon, 05 Jun 2023 09:32:37 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1968604 Title: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-firmware source package in Lunar: Fix Released Bug description: [Impact] I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip. 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio USB adapter very often stops working, can't connect or find other bluetooth devices. The adapter can't work even after reboots. The following entries appear in the log: апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout Firmware loaded correctly, but something is not working. апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814 1) I use: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) linux-firmware: 20220329.git681281e4-0ubuntu1 3) What you expected to happen? I expect a well working bluetooth adapter. 4) What happened instead? My bluetooth adapter may work, may not. The adapter may stop finding and connecting to other devices. I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1 I've downloaded Windows's archive http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted rtl8761bu_config.bin After I changed firmware my usb dongle work fine. Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other correct version? Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate packages. I will remove the RTL8761B firmware package and put them manually. bluetoothctl --version bluetoothctl: 5.64 hci0: Type: Primary Bus: USB BD Address: 00:E0:4C:FC:E2:03 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:5751 acl:49 sco:0 events:489 errors:0 TX bytes:219114 acl:398 sco:0 commands:83 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'desktop' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x97b LMP Version: 5.1 (0xa) Subversion: 0xec43 Manufacturer: Realtek Semiconductor Corporation (93) rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Realtek's worker updated these bad firmware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80 [Test Case] Connect to and use a bluetooth device connected to a RTL8761B base USB BT controller. [Fix] Use latest rtl8761bu firmware blobs updates from linux-firmware. [Where Problems Could Occur] These firmwares are specific for the rtl8671b chips. So users of USB or UART BT controllers based on that chip could see problems when trying to connect to and use bluetooth devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1968604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1968604] Re: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
This bug was fixed in the package linux-firmware - 20220923.gitf09bebf3-0ubuntu1.7 --- linux-firmware (20220923.gitf09bebf3-0ubuntu1.7) kinetic; urgency=medium * rtl8761b usb bluetooth doesn't work following reboot until unplug/replug (LP: #1968604) - rtl_bt: Update RTL8761B BT UART firmware to 0x9DC6_D922 - rtl_bt: Update RTL8761B BT USB firmware to 0xDFC6_D922 -- Juerg Haefliger Mon, 05 Jun 2023 09:29:22 +0200 ** Changed in: linux-firmware (Ubuntu Kinetic) Status: Fix Committed => Fix Released ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1968604 Title: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-firmware source package in Lunar: Fix Released Bug description: [Impact] I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip. 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio USB adapter very often stops working, can't connect or find other bluetooth devices. The adapter can't work even after reboots. The following entries appear in the log: апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout Firmware loaded correctly, but something is not working. апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814 1) I use: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) linux-firmware: 20220329.git681281e4-0ubuntu1 3) What you expected to happen? I expect a well working bluetooth adapter. 4) What happened instead? My bluetooth adapter may work, may not. The adapter may stop finding and connecting to other devices. I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1 I've downloaded Windows's archive http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted rtl8761bu_config.bin After I changed firmware my usb dongle work fine. Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other correct version? Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate packages. I will remove the RTL8761B firmware package and put them manually. bluetoothctl --version bluetoothctl: 5.64 hci0: Type: Primary Bus: USB BD Address: 00:E0:4C:FC:E2:03 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:5751 acl:49 sco:0 events:489 errors:0 TX bytes:219114 acl:398 sco:0 commands:83 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'desktop' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x97b LMP Version: 5.1 (0xa) Subversion: 0xec43 Manufacturer: Realtek Semiconductor Corporation (93) rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Realtek's worker updated these bad firmware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80 [Test Case] Connect to and use a bluetooth device connected to a RTL8761B base USB BT controller. [Fix] Use latest rtl8761bu firmware blobs updates from linux-firmware. [Where Problems Could Occur] These firmwares are specific for the rtl8671b chips. So users of USB or UART BT controllers based on that chip could see problems when trying to connect to and use bluetooth devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1968604/+subscriptions --
[Kernel-packages] [Bug 1968604] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1968604 Title: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-firmware source package in Lunar: Fix Released Bug description: [Impact] I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip. 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio USB adapter very often stops working, can't connect or find other bluetooth devices. The adapter can't work even after reboots. The following entries appear in the log: апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout Firmware loaded correctly, but something is not working. апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814 1) I use: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) linux-firmware: 20220329.git681281e4-0ubuntu1 3) What you expected to happen? I expect a well working bluetooth adapter. 4) What happened instead? My bluetooth adapter may work, may not. The adapter may stop finding and connecting to other devices. I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1 I've downloaded Windows's archive http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted rtl8761bu_config.bin After I changed firmware my usb dongle work fine. Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other correct version? Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate packages. I will remove the RTL8761B firmware package and put them manually. bluetoothctl --version bluetoothctl: 5.64 hci0: Type: Primary Bus: USB BD Address: 00:E0:4C:FC:E2:03 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:5751 acl:49 sco:0 events:489 errors:0 TX bytes:219114 acl:398 sco:0 commands:83 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'desktop' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x97b LMP Version: 5.1 (0xa) Subversion: 0xec43 Manufacturer: Realtek Semiconductor Corporation (93) rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Realtek's worker updated these bad firmware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80 [Test Case] Connect to and use a bluetooth device connected to a RTL8761B base USB BT controller. [Fix] Use latest rtl8761bu firmware blobs updates from linux-firmware. [Where Problems Could Occur] These firmwares are specific for the rtl8671b chips. So users of USB or UART BT controllers based on that chip could see problems when trying to connect to and use bluetooth devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1968604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1968604] Re: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
This bug was fixed in the package linux-firmware - 20230323.gitbcdcfbcf-0ubuntu1.2 --- linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) lunar; urgency=medium * rtl8761b usb bluetooth doesn't work following reboot until unplug/replug (LP: #1968604) - rtl_bt: Update RTL8761B BT UART firmware to 0x9DC6_D922 - rtl_bt: Update RTL8761B BT USB firmware to 0xDFC6_D922 -- Juerg Haefliger Mon, 05 Jun 2023 09:22:50 +0200 ** Changed in: linux-firmware (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1968604 Title: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-firmware source package in Lunar: Fix Released Bug description: [Impact] I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip. 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio USB adapter very often stops working, can't connect or find other bluetooth devices. The adapter can't work even after reboots. The following entries appear in the log: апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout Firmware loaded correctly, but something is not working. апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814 1) I use: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) linux-firmware: 20220329.git681281e4-0ubuntu1 3) What you expected to happen? I expect a well working bluetooth adapter. 4) What happened instead? My bluetooth adapter may work, may not. The adapter may stop finding and connecting to other devices. I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1 I've downloaded Windows's archive http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted rtl8761bu_config.bin After I changed firmware my usb dongle work fine. Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other correct version? Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate packages. I will remove the RTL8761B firmware package and put them manually. bluetoothctl --version bluetoothctl: 5.64 hci0: Type: Primary Bus: USB BD Address: 00:E0:4C:FC:E2:03 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:5751 acl:49 sco:0 events:489 errors:0 TX bytes:219114 acl:398 sco:0 commands:83 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'desktop' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x97b LMP Version: 5.1 (0xa) Subversion: 0xec43 Manufacturer: Realtek Semiconductor Corporation (93) rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Realtek's worker updated these bad firmware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80 [Test Case] Connect to and use a bluetooth device connected to a RTL8761B base USB BT controller. [Fix] Use latest rtl8761bu firmware blobs updates from linux-firmware. [Where Problems Could Occur] These firmwares are specific for the rtl8671b chips. So users of USB or UART BT controllers based on that chip could see problems when trying to connect to and use bluetooth devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1968604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
That sucks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024427] Re: potential S3 issue for amdgpu Navi 31/Navi33
In oem-6.1 6.1.0-1016.16 through stable updates bug 2021945. ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2024427 Title: potential S3 issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Triaged Status in linux-firmware source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
And we're back to the original problem. I'm out of ideas sorry, and would just be googling at this stage. Jul 03 16:45:29 khteh-p17-2i gdm3[3111]: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service Jul 03 16:45:29 khteh-p17-2i kernel: Loading of module with unavailable key is rejected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025538] Re: Unrequested kernel update
This just happened to me on Ubuntu 22.04.2 LTS. After installing updates in the last weeks, and a reboot today, I'm suddenly running kernel linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency. I guess I'm lucky that the machine still booted! When trying to remove the kernel, it tries to install another nvidia kernel instead: linux-image-unsigned-5.19.0-1010-nvidia-lowlatency should be installed. I can force removal of all nvidia kernels with: sudo apt purge linux-image-5.19.0-1010-nvidia-lowlatency linux-image- unsigned-5.19.0-1010-nvidia-lowlatency -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
/var/lib/dkms/nvidia/535.54.03/6.2.0-24-generic/x86_64/log/make.log ** Attachment added: "make.log" https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1921536/+attachment/5683512/+files/make.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
journalctl -b0 ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1921536/+attachment/5683511/+files/journal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
After rebooting, if it still doesn't work then please run: journalctl -b0 > journal.txt find /var/lib/dkms/nvidia -name make.log and attach both files here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Done but still doesn't work. $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025560] Re: lubuntu does not boot after upgrade
@guiverc, added output from "apport-collect 2025560". The question is why "aptdaemon role='role-upgrade-system' sender=':1.69'" picks up unsupported kernels as "22.04.2 LTS (Jammy Jellyfish)" only supports kernel v.5.19-x according to https://launchpad.net/ubuntu/+source/linux, why? I managed to clean up the mess by booting on working kernel "5.15.0-76-generic", and then do a "sudo apt-get autoremove", which uninstalled the "bad" kernels. ** Attachment added: "Output from apport-collect 2025560" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025560/+attachment/5683510/+files/apport.linux.pjpsgqs6.apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025560 Title: lubuntu does not boot after upgrade Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 This morning upgrade installed a bunch of new kernels which made my computer unbootable. Manged to boot with old kernel: 5.15.0-76-generic, and none of new ones work. From /var/log/apt/history.log: Start-Date: 2023-07-02 12:06:38 Commandline: aptdaemon role='role-upgrade-system' sender=':1.69' Install: linux-modules-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1, automatic), linux-objects-nvidia-535-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-6.1.0-1015-oem:amd64 (6.1.0-1015.15+2, automatic), linux-image-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-signatures-nvidia-6.0.0-1018-oem:amd64 (6.0.0-1018.18+2, automatic), linux-signatures-nvidia-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), dctrl-tools:amd64 (2.24-3build2, automatic), linux-signatures-nvidia-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-signatures-nvidia-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-modules-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28, automatic), linux-image- 5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic), linux-modules-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), nvidia-firmware-535-535.54.03:amd64 (535.54.03-0ubuntu0.22.04.1, automatic), linux-modules-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1, automatic), linux-objects-nvidia-535-5.15.0-1038-oracle:amd64 (5.15.0-1038.44+2, automatic), linux-objects-nvidia-535-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-image-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36, automatic), linux-signatures-nvidia-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-objects-nvidia-535-5.19.0-1026-oracle:amd64 (5.19.0-1026.29~22.04.1+2, automatic), linux-objects-nvidia-535-5.19.0-46-generic:amd64 (5.19.0-46.47~22.04.1+2, automatic), linux-image-6.1.0-1015-oem:amd64 (6.1.0-1015.15, automatic), linux-image-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), linux-image-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-image-5.19.0-1026-oracle:amd64 (5.19.0- 1026.29~22.04.1, automatic), linux-modules-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.17.0-1033-oem:amd64 (5.17.0-1033.34+2, automatic), linux-objects-nvidia-535-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1+2, automatic), linux-image-5.19.0-1028-lowlatency:amd64 (5.19.0-1028.29~22.04.1, automatic), linux-signatures-nvidia-5.15.0-1031-intel-iotg:amd64 (5.15.0-1031.36+3, automatic), linux-objects-nvidia-535-5.15.0-1028-nvidia:amd64 (5.15.0-1028.28+2, automatic), linux-modules-5.15.0-1038-oracle:amd64 (5.15.0-1038.44, automatic), dkms:amd64 (2.8.7-2ubuntu2.1, automatic), linux-modules-6.0.0-1018-oem:amd64 (6.0.0-1018.18, automatic), linux-modules-5.17.0-1033-oem:amd64 (5.17.0-1033.34, automatic) Works to start in recovery mode on any kernel and guessing that the problem is related to the nvidia-driver, which is native: neofetch `-mddhddmss` kris@lubuntu ./mdhh. :mdhhhm` OS: Lubuntu 22.04.2 LTS x86_64 :ymhhhyyhy: Kernel: 5.15.0-76-generic `odhyyyhy+-./syo` Uptime: 22 mins `hhy..:oyhhhy-`:osso/..:/++oosyyyh`Packages: 2100 (dpkg), 13 (snap)
[Kernel-packages] [Bug 2018275] Re: Fix the in-motion function does not work
@Raof, your understandings are correct. Then, "motion=1" isn't supported currently. For apct, the motion variant may not exist in each entries. so extra policy rules maybe hit. if these cause the problem, 1. the apct have the incorrect rules and table needs correction. 2. need fully support in "motion", need to enable the motion variant fully. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018275 Title: Fix the in-motion function does not work Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: In Progress Bug description: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] because motion is always 0, the rules with motion=1 wouldn't be hit. but motion=1 isn't supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
** Summary changed: - Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) + FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018275] Re: Fix the in-motion function does not work
** Description changed: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] because motion is always 0, the rules with motion=1 wouldn't be hit. + but motion=1 isn't supported. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018275 Title: Fix the in-motion function does not work Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: In Progress Bug description: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] because motion is always 0, the rules with motion=1 wouldn't be hit. but motion=1 isn't supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Or more generally install whichever one is listed as "tested". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
YES: nvidia-driver-535 NO: nvidia-driver-535-open -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
No, there are 2 535 drivers listed in the "Additional Drivers" gnome app. Which one should I install? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025599] [NEW] BlueZ release 5.68
Public bug reported: BlueZ release 5.68 is now available: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ ** Affects: bluez (Ubuntu) Importance: Wishlist Assignee: Daniel van Vugt (vanvugt) Status: Triaged ** Tags: mantic udeng-894 ** Tags added: udeng-894 ** Changed in: bluez (Ubuntu) Importance: Undecided => Wishlist ** Changed in: bluez (Ubuntu) Status: New => Triaged ** Changed in: bluez (Ubuntu) Milestone: None => ubuntu-23.10-feature-freeze -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2025599 Title: BlueZ release 5.68 Status in bluez package in Ubuntu: Triaged Bug description: BlueZ release 5.68 is now available: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2025599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970389] Re: [nvidia] Janky text entry and frames appear out of order in Xwayland apps
Sounds like: > Xwayland does not provide a suitable mechanism for our driver to synchronize > application > rendering with presentation, which can cause visual corruption in some > circumstances. from http://us.download.nvidia.com/XFree86/Linux-x86_64/535.54.03/README/wayland- issues.html ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/1970389 Title: [nvidia] Janky text entry and frames appear out of order in Xwayland apps Status in X.Org X server: New Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in xwayland package in Ubuntu: Confirmed Bug description: When writing into text fields in some applications (Firefox, VS Code) on Jammy in a GNOME / Wayland session, I can see an effect best described as the glyphs appearing / disappearing sometimes repeatedly. I have attached a recording from my phone (since attempting to record a screencast fails). This doesn't happen always, and it appear somehow sensitive to some environmental condition (load?) since for example when I'm on a video call, the effect seems to not be happening so often. I have also experienced a few instances of a currently not-focused window disappearing (seeing through to a window that is below that window), but cannot reproduce that reliably. I have the NVIDIA driver 510 in use, RTX3090-only 16-core Zen1 Threadripper system with no integrated GPU. No similar effects visible when in a GNOME / Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 12:17:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-08 (168 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-22 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1970389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024287] Re: Wayland session not working with nvidia-driver-530 (proprietary, tested) on high refresh rate monitors.
** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-530 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-530 in Ubuntu. https://bugs.launchpad.net/bugs/2024287 Title: Wayland session not working with nvidia-driver-530 (proprietary, tested) on high refresh rate monitors. Status in nvidia-graphics-drivers-530 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Bug description: The currently "tested" Nvidia driver 530 has a critical bug which causes Wayland sessions to crash during logon. It affects all desktop environments but apparently it only happens when the monitor refresh rate is more than 120hz. https://forums.developer.nvidia.com/t/cant-boot-into-kde-wayland- session-with-530-30-02/244559/42 https://forums.developer.nvidia.com/t/rtx4090-530-drivers-not-working- on-wayland-gnome-screen-turns-off-works-on-xorg/249204 Apparently it is solved in driver version 535.54.03 which is not yet available in the Ubuntu repos. Downgrading to nvidia-driver-525 solves the problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 17 14:03:10 2023 InstallationDate: Installed on 2021-08-24 (661 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: Upgraded to lunar on 2023-04-20 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2024287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
I also had this bug. The workaround posted in November helped fix it for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025460] Re: night light stopped working
Thanks for the bug report. Please run: lspci -k > lspci.txt journalctl -b0 > journal.txt and attach the resulting text files here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Package changed: gnome-shell (Ubuntu) => linux-hwe-5.15 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2025460 Title: night light stopped working Status in linux-hwe-5.15 package in Ubuntu: Incomplete Bug description: Same as #1752680 but happening from cold boot and won't work again after disabling/re-enabling night light. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-76.83~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 30 10:25:21 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-24 (978 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2025460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017980] Re: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Removing chromium-browser as affected package because this wasn't actually verified on Chromium. If it is verified on Chromium, please revert that. ** No longer affects: chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: Chrome crashes with FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
> Amd why are ALL the options disabled for me? It thinks you installed a driver manually from nvidia.com, which Ubuntu doesn't support. Try this: /usr/bin/nvidia-installer --uninstall # From http://us.download.nvidia.com/XFree86/Linux-x86_64/535.54.03/README/installdriver.html Also uninstall any packages from previous drivers, which you can find with: dpkg -l | grep nvidia | grep -e '\<[345][0-9][0-9]\.' and also delete any lingering kernel modules, which you can find with: find /usr/lib -name nvidia.ko then reboot and hopefully the 'Additional Drivers' app will behave better. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
nvidia-driver-535 should be best. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Which one of the two should I install? ** Attachment added: "Screenshot from 2023-07-03 14-52-48.png" https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1921536/+attachment/5683488/+files/Screenshot%20from%202023-07-03%2014-52-48.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Amd why are ALL the options disabled for me? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Which one of the two? ** Attachment added: "Screenshot from 2023-07-03 14-35-03.png" https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1921536/+attachment/5683487/+files/Screenshot%20from%202023-07-03%2014-35-03.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle
Verified,
~~~
$ uname -a
Linux u-Precision-5480 6.0.0-1019-oem #19-Ubuntu SMP PREEMPT_DYNAMIC Tue Jun 20
10:50:57 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
$ ubuntu-report show | grep -ie bios -a5
"BIOS": {
"Version": "1.3.0"
},
~~~
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2021949
Title:
Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to
type-C dongle
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
New
Status in linux-oem-6.0 source package in Jammy:
Fix Committed
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Committed
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.0 source package in Mantic:
Invalid
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[Impact]
Enabling CL1 (Controller Low Power) states during discovery of existing
tunnels established by the system firmware can interfere with the operation of
those tunnels.
The DisplayPort tunnel establishment timeout of 1.5 seconds can be
insufficient for some docking stations, leading to blank displays.
[Fix]
CL1 states are now not enabled during discovery of existing tunnels. The TMU
settings also remain unchanged.
The timeout is increased to 3 seconds to allow more time for the DisplayPort
connection manager handshake, fixing the issue of displays remaining blank.
[Test Cases]
1. plug docking station on the host
2. bring up the host and get into desktop.
3. flip docking station's cable.
4. check if the external monitor works well
[Where problems could occur]
Low, If the handshake actually requires even more than 3 seconds in some
cases, the timeout may still need to be increased further.
[Misc]
Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a
huge,
so skip Jammy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2021949/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Alternatively, just disable Secure Boot in the BIOS :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
At a guess: 1. sudo apt remove nvidia-driver-535 nvidia-dkms-535 2. sudo apt purge 3. Reboot. 4. Open the 'Additional Drivers' app in GNOME and use it to reinstall. 5. Reboot again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023638] Re: Various backlight issues with the 6.0/6.1 kernel
** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023638 Title: Various backlight issues with the 6.0/6.1 kernel Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] There are some new patches for new method to decide which backlight driver should be registered introduced since 6.1. And we backport some of them to 6.0-oem kernel which are not enough to solved all backlight issues. 1. dell_laptop created a non-working backlight driver before nvidia is loaded, that leads to the system can't adjust the display brightness. 2. acpi_backlight0 sometimes will be generated together with intel_backlight. [Fix] Below 2 commits from v6.3-rc6 prevent the acpi_backlight from being registered automatically(which have been included into ubuntu kernels through stable update) e506731c8f35 ACPI: video: Make acpi_backlight=video work independent from GPU driver 78dfc9d1d1ab ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type() Below patch prevents platform driver(dell_laptop) from creating backlight driver after win8. aa8a950a5d6b ACPI: video: Stop trying to use vendor backlight control on laptops from after ~2012 https://patchwork.kernel.org/project/linux-acpi/patch/20230608091258.7963-1-hdego...@redhat.com/ [Test] Verified on the dell platform which reports this issue. [Where problems could occur] The assumption of the not-yet-upstreamed commit regarding backlight control is that, after Windows 8, all laptop backlights are controlled either by ACPI or the native graphics driver. It impacts the laptops that do not follow the assumption and will lead to broken backlight interface. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Please provide complete reinstallation commands. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
>From bug 2014983: > Fixed by purging everything nvidia, libnvidia, or cuda, and reinstalling > through > the "additional drivers" interface. I also reinstalled linux-headers-$(uname > -r). ** Tags added: nvidia ** Tags added: lunar ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-restricted-modules (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023946] Re: Nvidia 530 kernel driver is not installed/built
*** This bug is a duplicate of bug 1921536 *** https://bugs.launchpad.net/bugs/1921536 Bug 2014983 has a suggestion for how to fix it. ** No longer affects: dkms (Ubuntu) ** This bug has been marked a duplicate of bug 1921536 "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2023946 Title: Nvidia 530 kernel driver is not installed/built Status in nvidia-graphics-drivers-530 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: ``` $ uname -a Linux khteh-p17-2i 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ``` ``` $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ``` ``` $ prime-select query on-demand ``` ``` $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd25B8sv17AAsd22DEbc03sc00i00 vendor : NVIDIA Corporation model: GA107GLM [RTX A2000 Mobile] driver : nvidia-driver-510 - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-515-open - distro non-free driver : nvidia-driver-515-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-530 - distro non-free recommended driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-530-open - distro non-free driver : nvidia-driver-515 - distro non-free driver : nvidia-driver-470 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin ``` ``` $ dpkg -l | grep -i nvidia ii libaccinj64-11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA ACCINJ Library (64-bit) ii libcu++-dev 1.8.1-2 all NVIDIA C++ Standard Library ii libcublas11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLAS Library ii libcublaslt11:amd64 11.11.3.6~11.8.0-3 amd64NVIDIA cuBLASLt Library ii libcudart11.0:amd64 11.8.89~11.8.0-3 amd64NVIDIA CUDA Runtime Library ii libcufft10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFT Library ii libcufftw10:amd64 11.1.1+~10.9.0.58~11.8.0-3 amd64NVIDIA cuFFTW Library ii libcuinj64-11.8:amd64 11.8.87~11.8.0-3 amd64NVIDIA CUINJ Library (64-bit) ii libcupti-dev:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface development files ii libcupti-doc 11.8.87~11.8.0-3 all NVIDIA CUDA Profiler Tools Interface documentation ii libcupti11.8:amd6411.8.87~11.8.0-3 amd64NVIDIA CUDA Profiler Tools Interface runtime library ii libcurand10:amd64 11.1.1+~10.3.0.86~11.8.0-3 amd64NVIDIA cuRAND Library ii libcusolver11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVER Library ii libcusolvermg11:amd64 11.4.1.48~11.8.0-3 amd64NVIDIA cuSOLVERmg Library ii libcusparse11:amd64 11.7.5.86~11.8.0-3 amd64NVIDIA cuSPARSE Library ii libnppc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives core runtime library ii libnppial11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Arithmetic and Logic ii libnppicc11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Color Conversion ii libnppidei11:amd6411.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Data Exchange and Initialization ii libnppif11:amd64 11.8.0.86~11.8.0-3 amd64NVIDIA Performance Primitives lib for Image Filters ii libnppig11:amd64 11.8.0.86~11.8.0-3 amd64
[Kernel-packages] [Bug 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982483]
options snd-hda-intel model=alc295-hp-x360 didn't help either. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982483 Title: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274) Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I have tried: options snd-hda-intel model=alc285-hp-amp-init options snd-hda-intel model=alc274-dell-aio and newer kernels up to 5.19-rc6. 21: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.2CriaNVEdN5 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Device Name: "Onboard - Sound" Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x7ad0 SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x89e9 Revision: 0x11 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x6105238000-0x610523bfff (rw,non-prefetchable) Memory Range: 0x610500-0x61050f (rw,non-prefetchable) IRQ: 161 (1098 events) Module Alias: "pci:v8086d7AD0sv103Csd89E9bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_tgl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl" Config Status: cfg=new, avail=yes, need=no, active=unknown <6>[3.582352] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC274: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker <6>[3.582359] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <6>[3.582362] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) <6>[3.582364] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 <6>[3.582366] snd_hda_codec_realtek hdaudioC0D0:inputs: <6>[3.582367] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 <6>[3.582369] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 Alsa-info: https://alsa- project.org/db/?f=ed6190cfc9d9eb1c758c6c3106dd236b150f5b31 Here is a kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=216139 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ernst 1560 F pulseaudio /dev/snd/controlC0: ernst 1560 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (143 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP Pavilion All-in-One Desktop 27-ca1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1006-oem root=UUID=72ea78e1-7744-4fcc-b63c-3aa577c86a80 ro quiet splash ibt=off mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1006.6-oem 6.0.0 RelatedPackageVersions: linux-restricted-modules-6.0.0-1006-oem N/A linux-backports-modules-6.0.0-1006-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy wayland-session Uname: Linux 6.0.0-1006-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/09/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.name: 89E9 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnAMI:bvrF.02:bd02/09/2022:br15.2:efr1.16:svnHP:pnHPPavilionAll-in-OneDesktop27-ca1xxx:pvr:rvnHP:rn89E9:rvr0100:cvnHP:ct13:cvr:sku661Q7EA#UUW: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion All-in-One Desktop 27-ca1xxx dmi.product.sku: 661Q7EA#UUW dmi.sys.vendor: HP modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-06-15T22:28:44.879144 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1982483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
