[Kernel-packages] [Bug 2044600] Re: package linux-hwe-5.15-headers-5.15.0-89 5.15.0-89.99~20.04.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/src/linux-hwe-5.15-head
[Expired for linux-hwe-5.15 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-hwe-5.15 (Ubuntu) Status: Incomplete => Expired -- 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/2044600 Title: package linux-hwe-5.15-headers-5.15.0-89 5.15.0-89.99~20.04.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/src/linux-hwe-5.15-headers-5.15.0-89/lib/Kconfig.debug' a '/usr/src/linux-hwe-5.15-headers-5.15.0-89/lib/Kconfig.debug.dpkg- new': fin de fichero o de flujo inesperado Status in linux-hwe-5.15 package in Ubuntu: Expired Bug description: i tried to repai with simantec by reinstalling broken packges bit the error continues ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-hwe-5.15-headers-5.15.0-89 5.15.0-89.99~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-89.99~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-89-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 23 20:04:57 2023 ErrorMessage: no se pudieron copiar los datos extraídos de './usr/src/linux-hwe-5.15-headers-5.15.0-89/lib/Kconfig.debug' a '/usr/src/linux-hwe-5.15-headers-5.15.0-89/lib/Kconfig.debug.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2023-09-12 (73 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: linux-hwe-5.15 Title: package linux-hwe-5.15-headers-5.15.0-89 5.15.0-89.99~20.04.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/src/linux-hwe-5.15-headers-5.15.0-89/lib/Kconfig.debug' a '/usr/src/linux-hwe-5.15-headers-5.15.0-89/lib/Kconfig.debug.dpkg-new': fin de fichero o de flujo inesperado 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/2044600/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
I was bothered by the fact that we only sometimes see the double partition rescan in dmesg. If udev always rescans the partitions of a full block devices, shouldn't we always see those messages twice? It turns out that udev doesn't rescan partitions just because a new block device appears. When it gets a uevent for a full block device, it registers an inotify watch on the device file for any process closing a file that was open in write mode. Presumably that process could've changed the partitions so, when that inotify event fires, it requests a partition rescan. In our case, losetup has opened /dev/loop0 in write mode. When it calls into the LOOP_CONFIGURE ioctl(), a uevent will fire for /dev/loop0. If udev processes that event and adds the inotify watch before losetup closes the device, then closing the device will trigger the inotify event and udev will rescan. I don't see a way to order operations to prevent this race. And I don't think we can "settle" our way out of it, because its not a uevent we're racing with, its the inotify event. But it looks like systemd may already have a solution for that: https://systemd.io/BLOCK_DEVICE_LOCKING/ I think as long as we run all of our commands that access the partition device files under `udevadm lock -d `, then systemd should not trigger a partition reread underneath us. Here's what I'm thinking: https://code.launchpad.net/~dannf/livecd-rootfs/+git/livecd- rootfs/+merge/459549 Of course, udevadm lock didn't exist until after jammy. And all versions that do have it, including the one in v255 in noble-proposed, are broken and need this patch backport: https://github.com/systemd/systemd/commit/ba340e2a75a0a16031fcb7efa05cfd250e859f17 -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2049688] Re: nvidia stoped working, , package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subp
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 Ubuntu 23.04 has officially reached EOL (End of Life) support status. Users should upgrade to Ubuntu 23.10. There is a version of Nvidia 390 in the 23.10 proposed repository that should work. ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049688 Title: nvidia stoped working,, package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia- dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: after latest update on 22.04 nvidia driver stoped working, gpu not found, cannot reinstall, even after upgrade I get : package nvidia- dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10. I also had errors with dependencies, when trying to reinstall and with kernel headers. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: nvidia-dkms-390 390.157-0ubuntu5.23.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 22:54:39 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-11-28 (50 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to lunar on 2024-01-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049688/+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 2047658] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błęd
*** This bug is a duplicate of bug 2051436 *** https://bugs.launchpad.net/bugs/2051436 ** This bug has been marked a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2047658 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błędu 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I want to check if my nvidia is going well, so i use nvidia-smi and got error, then I processed to reinstall my nvidia drivers and got this error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Dec 28 21:10:15 2023 ErrorMessage: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błędu 10 InstallationDate: Installed on 2022-09-13 (470 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/local/bin/python3.10, Python 3.10.7, unpackaged PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błędu 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2047658/+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 2049086] Re: General upgrade to 22.04 leads to second monitor not being recognised package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: usr/src/nvidia-390.157/dkms.conf]
*** This bug is a duplicate of bug 2051436 *** https://bugs.launchpad.net/bugs/2051436 ** This bug has been marked a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049086 Title: General upgrade to 22.04 leads to second monitor not being recognised package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: usr/src/nvidia-390.157/dkms.conf] failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Upgraded using sudo apt upgrade Description: Ubuntu 22.04.3 LTS Release: 22.04 system fails to boot - blank screen - no activity recovery mode coaxed system to startup but error happens with nvidia drivers system has two monitors, one works (DVI) the second (VGA) does not. suspect ancient video card (geforce 610) and issues with compatibility ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: usr/src/nvidia-390.157/dkms.conf] ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: nvidia-kernel-source-390:amd64: Install nvidia-kernel-common-390:amd64: Install nvidia-dkms-390:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jan 11 15:20:51 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-07-30 (529 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: usr/src/nvidia-390.157/dkms.conf] failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049086/+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 2049198] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-390, o script post-installation retornou
*** This bug is a duplicate of bug 2051436 *** https://bugs.launchpad.net/bugs/2051436 ** This bug has been marked a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049198 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-390, o script post-installation retornou erro do status de saída 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: doesnt work ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 12 09:28:59 2024 ErrorMessage: o subprocesso instalado, do pacote nvidia-dkms-390, o script post-installation retornou erro do status de saída 10 InstallationDate: Installed on 2023-08-31 (134 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-390, o script post-installation retornou erro do status de saída 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049198/+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 2048934] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab de
*** This bug is a duplicate of bug 2051436 *** https://bugs.launchpad.net/bugs/2051436 ** This bug has been marked a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2048934 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: driver bug while update ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: nvidia-kernel-source-390:amd64: Install nvidia-kernel-common-390:amd64: Install nvidia-dkms-390:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 10 21:00:05 2024 ErrorMessage: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück InstallationDate: Installed on 2023-04-21 (263 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2048934/+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 2049226] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
*** This bug is a duplicate of bug 2051436 *** https://bugs.launchpad.net/bugs/2051436 ** This bug has been marked a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049226 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After software update only one screen is working with reduced resolution ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 12 18:55:09 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-04-23 (628 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049226/+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 2049199] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un
*** This bug is a duplicate of bug 2051436 *** https://bugs.launchpad.net/bugs/2051436 ** This bug has been marked a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049199 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: le sous-processus paquet nvidia-dkms-390 script post- installation installé a renvoyé un état de sortie d'erreur 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Occurs first time during an update of Ubuntu. After that I was unable to boot ubuntu and gnome. I booted in recovery mode and desintalled all nvidia drivers with sudo apt remove '^nvidia'; apt autoremove And then reboot: ok (defaut driver nouveau for GPU Nvidia Quadro K610M) After that successfull reboot, I tried ubuntu-drivers autoinstall and got this error again. So I conclude that this package is in some way corrupted or no mode compatible whith that HW. Waiting for a solution, i desinstalled again nvidia* Thanks for your help. Daniel ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jan 12 13:40:53 2024 ErrorMessage: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 InstallationDate: Installed on 2021-10-27 (806 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 UpgradeStatus: Upgraded to jammy on 2022-05-02 (620 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049199/+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 2049665] Re: A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU)
*** This bug is a duplicate of bug 2051436 *** https://bugs.launchpad.net/bugs/2051436 ** This bug has been marked a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049665 Title: A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU) Status in linux-hwe-6.5 package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: A recent Ubuntu update is keeping the GPU software of Folding at Home (Folding@Home) from working. Past updates have not interfered with it. Expected result: An updated nvidia (proprietary) driver would be installed with the update that continues to work smoothly, provides OpenCL, etc. Actual result: The update caused FAH to disable its GPU processing capabilities. OpenCL is mentioned in the error message, so there may be something wrong with the OpenCL installation in the nVidia v390 package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 12:18:33 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.5.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] [10de:0fe9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 750M Mac Edition] [106b:011e] InstallationDate: Installed on 2024-01-16 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05ac:828d Apple, Inc. Bluetooth USB Host Controller Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 002: ID 05ac:8511 Apple, Inc. FaceTime HD Camera (Built-in) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. iMac14,3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=567a07dc-70f9-441e-a456-151c0da1e7ea ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 433.140.2.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-77EB7D7DAF985301 dmi.board.vendor: Apple Inc. dmi.board.version: iMac14,3 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-77EB7D7DAF985301 dmi.modalias: dmi:bvnAppleInc.:bvr433.140.2.0.0:bd04/18/2022:br0.1:svnAppleInc.:pniMac14,3:pvr1.0:rvnAppleInc.:rnMac-77EB7D7DAF985301:rvriMac14,3:cvnAppleInc.:ct13:cvrMac-77EB7D7DAF985301:skuSystemSKU#: dmi.product.family: iMac dmi.product.name: iMac14,3 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2049665/+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 2049548] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код
*** This bug is a duplicate of bug 2051436 *** https://bugs.launchpad.net/bugs/2051436 ** This bug has been marked a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049548 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 01:43:33 2024 ErrorMessage: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 InstallationDate: Installed on 2024-01-16 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049548/+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 2049245] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
*** This bug is a duplicate of bug 2051436 *** https://bugs.launchpad.net/bugs/2051436 ** This bug has been marked a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049245 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: cannot select screen resolution other then 1024 X 768 after implementing the latest ubuntu update. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: nvidia-kernel-source-390:amd64: Install nvidia-kernel-common-390:amd64: Install nvidia-dkms-390:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jan 13 15:29:03 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-05-04 (253 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049245/+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 2051436] Re: Nvidia 390 Needs Patched for Kernel 6.5+
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2051436 Title: Nvidia 390 Needs Patched for Kernel 6.5+ Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Supposedly, this was solved in Ubuntu 23.10, but the package never made it out of the mantic-proposed repository: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16 Nor was it backported to Ubuntu 22.04 As a temporary measure, I uploaded a patched version to a PPA for Ubuntu 22.04 (and added a patch for 6.6/6.7): https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+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 2049945] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код
*** This bug is a duplicate of bug 2051436 *** https://bugs.launchpad.net/bugs/2051436 ** This bug has been marked a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049945 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: After installing the kernel update to version 6.5, the screen resolution was disrupted. When I try to switch to the open nouveau driver, an error occurs. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 19 21:49:11 2024 ErrorMessage: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 InstallationDate: Installed on 2024-01-19 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049945/+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 2051149] Re: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problèmes de dépendances - laissé non configuré
*** This bug is a duplicate of bug 2051436 *** https://bugs.launchpad.net/bugs/2051436 ** This bug has been marked a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2051149 Title: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Il m'est impossible d'installer le package nvidia-driver-390 390.157-0ubuntu0.22.04.2 Code retour: Failed to install/upgrade: problèmes de dépendances - laissé non configuré Je rencontre désormais un problème d'affichage de l'écran Cette erreur me bloque donc d'autres installations de package Cordialement ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-driver-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: libgnutls30:amd64: Install libgnutls30:amd64: Configure NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jan 24 17:22:05 2024 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2023-05-02 (266 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051149/+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 2051436] [NEW] Nvidia 390 Needs Patched for Kernel 6.5+
Public bug reported: Supposedly, this was solved in Ubuntu 23.10, but the package never made it out of the mantic-proposed repository: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16 Nor was it backported to Ubuntu 22.04 As a temporary measure, I uploaded a patched version to a PPA for Ubuntu 22.04 (and added a patch for 6.6/6.7): https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2051436 Title: Nvidia 390 Needs Patched for Kernel 6.5+ Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Supposedly, this was solved in Ubuntu 23.10, but the package never made it out of the mantic-proposed repository: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16 Nor was it backported to Ubuntu 22.04 As a temporary measure, I uploaded a patched version to a PPA for Ubuntu 22.04 (and added a patch for 6.6/6.7): https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+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 2049976] Re: Analog VGA goes black on resume
** Changed in: linux (Ubuntu) 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/2049976 Title: Analog VGA goes black on resume Status in linux package in Ubuntu: Invalid Bug description: Starting a few weeks ago after applying regular maintenance to 22.04.3 LTS one of my two displays, an LG 22MP47HQ-P connected to my tower by a D-Sub cable, blinked multiple times immediately on resume from suspend. My second display which is connected using HDMI works normally. This, of course, was merely a mild annoyance because after a few seconds it stopped. However in the past week that same display flashes on, and then goes black. I power the display off and back on and again it flashes on for a fraction of a second and then goes black. After several power cycles of the display it stays on, so again this is only a mild annoyance. Is this a known issue with a recent update? Specifically this is after a deep suspend, one where on unlock you need to press a key to get the login prompt. I tried updating to 23.10 but the problem is there as well. This bug tool does not permit reporting a problem against Wayland. lshw -C video *-display description: VGA compatible controller product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 resolution=1920,1080 resources: irq:31 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) memory:c-d /var/log/apt/history.log taken immediately after encountering the issue on 22.04 Start-Date: 2024-01-02 16:01:30 Commandline: aptdaemon role='role-commit-packages' sender=':1.7295' Upgrade: thunderbird:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en-gb:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-gnome-support:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1) End-Date: 2024-01-02 16:01:33 Start-Date: 2024-01-03 16:57:04 Commandline: /usr/bin/unattended-upgrade Upgrade: libsqlite3-dev:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), libsqlite3-0:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), sqlite3:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3) End-Date: 2024-01-03 16:57:05 Start-Date: 2024-01-03 16:57:08 Commandline: /usr/bin/unattended-upgrade Upgrade: openssh-client:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), openssh-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), openssh-sftp-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6) End-Date: 2024-01-03 16:57:10 Start-Date: 2024-01-03 16:57:13 Commandline: /usr/bin/unattended-upgrade Upgrade: libnode72:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), nodejs:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), libnode-dev:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3) End-Date: 2024-01-03 16:57:14 Start-Date: 2024-01-03 16:57:16 Commandline: /usr/bin/unattended-upgrade Upgrade: nodejs-doc:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3) End-Date: 2024-01-03 16:57:17 Start-Date: 2024-01-09 20:43:19 Commandline: aptdaemon role='role-commit-packages' sender=':1.9514' Install: php8.3-xml:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), php8.3-mbstring:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), php8.3-common:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), php8.3-intl:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic) Upgrade: php-common:amd64 (2:93+ubuntu22.04.1+deb.sury.org+3, 2:94+ubuntu22.04.1+deb.sury.org+1), software-properties-common:amd64 (0.99.22.8, 0.99.22.9), python3-software-properties:amd64 (0.99.22.8, 0.99.22.9), php-intl:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), php-mbstring:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), software-properties-gtk:amd64 (0.99.22.8, 0.99.22.9), python3-distro-info:amd64 (1.1ubuntu0.1, 1.1ubuntu0.2), distro-info-data:amd64 (0.52ubuntu0.5, 0.52ubuntu0.6), linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.23, 20220329.git681281e4-0ubuntu3.24), php-xml:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), distro-info:amd64 (1.1ubuntu0.1, 1.1ubuntu0.2) End-Date: 2024-01-09 20:45:50 Start-Date: 2024-01-10 21:58:10 Commandline:
[Kernel-packages] [Bug 2051342] Re: Enable lowlatency settings in the generic kernel
I found this bug report by accident, while searching for something else. I pretty much only use mainline kernels and only 1000 Hertz. I support this proposed default Ubuntu kernel configuration change. The tick ISR is incredibly efficient (less than 2 uSec on my test system), and I do not understand your test results as I would have expected a lot less difference. Using mainline kernel 6.8-rc1 and limiting my test system max CPU frequency so that I get similar bogo op/s as you I get: - CONFIG_HZ=250 : 14853.14 bogo ops/s - CONFIG_HZ=1000 : 14714.01 bogo ops/s (0.94% worse) - CONFIG_HZ=1000+nohz_full : 15100 bogo ops/s (1.6% better) There is no power or thermal or active cores throttling on my test system. Note: with my CPU frequency limited for this test, the tick ISR takes about 4 uSec. The difference between the 250 and 1000 Hz kernel tests is 750 tick interrupts per second or 3 milliseconds or about 0.3% If I do not limit my max CPU frequency I get: - CONFIG_HZ=250 : 38518.64 bogo ops/s - CONFIG_HZ=1000 : 37765.55 bogo ops/s (2.0% worse) - CONFIG_HZ=1000+nohz_full : 39391.32 bogo ops/s (2.3% better) There was no power or thermal or active cores throttling for this test. However I did have to raise my processor max temperature limit from 75 to 80 degrees C for this test. Also the power is very close to the limit at 122 watts, where it will throttle at 125 watts. -- 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/2051342 Title: Enable lowlatency settings in the generic kernel Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: [Impact] Ubuntu provides the "lowlatency" kernel: a kernel optimized for applications that have special "low latency" requirements. Currently, this kernel does not include any specific UBUNTU SAUCE patches to improve the extra "low latency" requirements, but the only difference is a small subset of .config options. Almost all these options are now configurable either at boot-time or even at run-time, with the only exception of CONFIG_HZ (250 in the generic kernel vs 1000 in the lowlatency kernel). Maintaining a separate kernel for a single config option seems a bit overkill and it is a significant cost of engineering hours, build time, regression testing time and resources. Not to mention the risk of the low-latency kernel falling behind and not being perfectly in sync with the latest generic kernel. Enabling the low-latency settings in the generic kernel has been evaluated before, but it has been never finalized due to the potential risk of performance regressions in CPU-intensive applications (increasing HZ from 250 to 1000 may introduce more kernel jitter in number crunching workloads). The outcome of the original proposal resulted in a re-classification of the lowlatency kernel as a desktop- oriented kernel, enabling additional low latency features (LP: #2023007). As we are approaching the release of the new Ubuntu 24.04 we may want to re-consider merging the low-latency settings in the generic kernel again. Following a detailed analysis of the specific low-latency features: - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown clock tick when possible across all the enabled CPUs if they are either idle or running 1 task - reduce kernel jitter of running tasks due to the periodic clock tick, must be enabled at boot time passing `nohz_full=`); this can actually help CPU-intensive workloads and it could provide much more benefits than the CONFIG_HZ difference (since it can potentially shutdown any kernel jitter on specific CPUs), this one should really be enabled anyway, considering that it is configurable at boot time - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to kthread context (reduce time spent in softirqs with preemption disabled to improve the overall system responsiveness, at the cost of introducing a potential performance penalty, because RCU callbacks are not processed by kernel threads); this should be enabled as well, since it is configurable at boot time (via the rcu_nocbs= parameter) - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a timed delay instead of executing them immediately (c'an provide 5~10% power-savings for idle or lightly-loaded systems, this is extremely useful for laptops / portable devices - https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/); this has the potential to introduce significant performance regressions, but in the Noble kernel we already have a SAUCE patch that allows to enable/disable this option at boot time (see LP: #2045492), and by default it will be disabled (CONFIG_RCU_LAZY_DEFAULT_OFF=y) - CONFIG_HZ=1000 last but not least, the only option that is *only*
[Kernel-packages] [Bug 2047022] Re: WiFi is not work after upgrade Kernel to 6.5.0-14-generic
Same issue as J. Antonio (#25) describes. Update from jammy 6.2 to 6.5.0-15 causing wifi to be highly unstable. Will drop connection repeatedly (every few seconds), hangs when it is connected. Turning off/on wifi sometimes corrects the issue for a short time. ASUS GA15 Zephyrus AMD Ryzen 9 6900HS MB GA503RM NW Mediatek 7922 -- 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/2047022 Title: WiFi is not work after upgrade Kernel to 6.5.0-14-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in The Mantic Minotaur: Confirmed Status in linux source package in Mantic: Confirmed Bug description: [Summary] WiFi does not work after upgrade Kernel to linux-generic-hwe-22.04-edge [Steps to reproduce] 1. Install Ubuntu 22.04.04 Desktop image to the system 2. sudo apt-get update 3. sudo apt-get dist-upgrade 4. sudo apt install linux-generic-hwe-22.04-edge 5. Reboot system [Expected result] WiFi is working after upgrade Kernel [Actual result] WiFi is not work. Could not find WiFi interface from GUI. [Failure rate] 1/5 [Additional information] CID:202112-29800 SKU: TRBA-DVT2-C6 system-manufacturer: Dell Inc. system-product-name: XPS 9320 bios-version: 1.7.1 CPU: 12th Gen Intel(R) Core(TM) i7-1270P (16x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:46a6] (rev 08) kernel-version: 6.5.0-14-generic [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2047022/+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 2047022] Re: WiFi is not work after upgrade Kernel to 6.5.0-14-generic
Same issue as J. Antonio (#25) describes. Update from jammy 6.2 to 6.5.0-15 causing wifi to be highly unstable. Will drop connection repeatedly (every few seconds), hangs when it is connected. Turning off/on wifi sometimes corrects the issue for a short time. Also happened with 6.5.0-14 - was hoping update to 6.5.0-15 would fix it but it persists. ASUS GA15 Zephyrus AMD Ryzen 9 6900HS MB GA503RM NW Mediatek 7922 -- 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/2047022 Title: WiFi is not work after upgrade Kernel to 6.5.0-14-generic Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in The Mantic Minotaur: Confirmed Status in linux source package in Mantic: Confirmed Bug description: [Summary] WiFi does not work after upgrade Kernel to linux-generic-hwe-22.04-edge [Steps to reproduce] 1. Install Ubuntu 22.04.04 Desktop image to the system 2. sudo apt-get update 3. sudo apt-get dist-upgrade 4. sudo apt install linux-generic-hwe-22.04-edge 5. Reboot system [Expected result] WiFi is working after upgrade Kernel [Actual result] WiFi is not work. Could not find WiFi interface from GUI. [Failure rate] 1/5 [Additional information] CID:202112-29800 SKU: TRBA-DVT2-C6 system-manufacturer: Dell Inc. system-product-name: XPS 9320 bios-version: 1.7.1 CPU: 12th Gen Intel(R) Core(TM) i7-1270P (16x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:46a6] (rev 08) kernel-version: 6.5.0-14-generic [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2047022/+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 1970069] Re: Annoying boot messages interfering with splash screen
I'm not sure where you posted that to, I didn't see it dri-devel. But I think this is the first use of "splash" from the kernel command line within the kernel. I think it needs to be documented. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1990052] Re: fwupdtool reports an error (KERNEL BUG) when refreshing
AFAICT those kernel commits are now landed in Ubuntu's kernel. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990052 Title: fwupdtool reports an error (KERNEL BUG) when refreshing Status in Linux: Fix Released Status in fwupd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: when running the "refresh" command I get the following message $ sudo fwupdtool refresh Loading… [** ]07:43:19:0893 FuBiosSettings KERNEL BUG: 'type' attribute not exported: (failed to load type: Failed to open file “/sys/class/firmware-attributes/thinklmi/attributes/TotalMemoryEncryption/type”: No such file or directory) Loading… [- ] Downloading… [***] Downloading… [***] Downloading… [** ] Not sure if it's just a warning or an actual error. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: fwupd 1.8.4-2 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Sep 18 09:43:50 2022 InstallationDate: Installed on 2022-09-11 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-11 (7 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) MachineType: LENOVO 21AHCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-16-generic root=UUID=77d67dcd-a70a-4ee7-be9d-00c2cf6248c2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-16-generic N/A linux-backports-modules-5.19.0-16-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/13/2022 dmi.bios.release: 1.5 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET08W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrN3MET08W(1.05):bd09/13/2022:br1.5:efr1.3:svnLENOVO:pn21AHCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21AHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21AH_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21AHCTO1WW dmi.product.sku: LENOVO_MT_21AH_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1990052/+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 2007055] Re: cifs/samba mount not preserving file timestamps
Interesting. Can you run "apt-get -s install cifs-utils" on your client to see what version of cifs-utils you have installed? -- 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/2007055 Title: cifs/samba mount not preserving file timestamps Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Incomplete Bug description: I think I've found a bug or regression in something when trying to mount a remote samba share. Modified/Created times are not properly preserved in newer versions of Ubuntu. Because of this, rsync thinks files are different based on their modified times and keeps re-syncing them. I have a NAS on my network, running samba. I have two devices, a desktop and laptop. Both are running Ubuntu, and set up the exact same way. The desktop is running ubuntu 20.04, the laptop 22.04. I have mounted the NAS on both devices the exact same way. I attempt to copy a file (rsync) the exact same way. On the 20.04 desktop, this works perfectly fine. On the 22.04 laptop, the modified times are not preserved and set to the current time, preventing things like rsync -t from working. The only difference i can find is that between the two systems, the newer laptop 22.04 mount adds a few more options than the older system to the cifs mount options. These are added automatically without being specified explicitly (see the mount -v output below): * 'forceuid'/'forcegid' are changed to 'noforceuid'/'noforcegid * iocharset=utf8 added * serverino added desktop: $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.9-1ubuntu0.2 Candidate: 2:6.9-1ubuntu0.2 Version table: *** 2:6.9-1ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:6.9-1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ uname -a Linux desktop 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) laptop: $ lsb_release -rd Description:KDE neon 5.26 Release:22.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.14-1ubuntu0.1 Candidate: 2:6.14-1ubuntu0.1 Version table: *** 2:6.14-1ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:6.14-1build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ uname -a Linux laptop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) the remote NAS is a synology appliance, running Samba version 4.10.18. SMB version 3 Steps to reproduce: 1. Similar setup, 1 device running 20.04, another running 22.04, otherwise up to date. 2. mount the NAS on both devices the exact same way $ sudo mount -t cifs -o vers=3.0,credentials=/etc/samba/smbcreds,iocharset=utf8,rw,uid=1000,gid=1000,dir_mode=0775,file_mode=0664 //nas/backup /media/scratch 3. on the 20.04 older desktop, create a test file and show the modify time $ fallocate -l 1M test1.txt $ stat test1.txt File: test1.txt Size: 1048576 Blocks: 2048 IO Block: 4096 regular file Device: 801h/2049d Inode: 13634663Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/desktop_user) Gid: ( 1000/desktop_user) Access: 2023-02-12 18:35:48.978743377 -0700 Modify: 2023-02-12 18:35:48.978743377 -0700 Change: 2023-02-12 18:35:48.978743377 -0700 Birth: - 4. rsync the test file to the mount, stat the file and see the modify/change are preserved $ rsync -avh test1.txt /media/scratch/ sending incremental file list test1.txt sent 1.05M bytes received 35 bytes 2.10M bytes/sec total size is 1.05M speedup is 1.00 $ stat /media/scratch/test1.txt File: /media/scratch/test1.txt Size: 1048576 Blocks: 2064 IO Block: 1048576 regular file Device: 52h/82d Inode: 321811 Links: 1
[Kernel-packages] [Bug 2051424] [NEW] libnvidia-common-535: packaging problem
Public bug reported: I'm on jammy, all available upgrades installed. My sources: deb http://archive.ubuntu.com/ubuntu/ jammy main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted universe multiverse deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse There are two problems with libnvidia-common-535 packaging: 1. Outdated versions are still offered 2. It is phasing all the time, at %0, even though not listed as a phasing one at https://ubuntu-archive-team.ubuntu.com/phased-updates.html Compare this > apt-cache policy libnvidia-cfg1-535 libnvidia-cfg1-535: Installed: 535.154.05-0ubuntu0.22.04.1 Candidate: 535.154.05-0ubuntu0.22.04.1 Version table: *** 535.154.05-0ubuntu0.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages 100 /var/lib/dpkg/status to this > apt-cache policy libnvidia-common-535 libnvidia-common-535: Installed: 535.154.05-0ubuntu0.22.04.1 Candidate: 535.154.05-0ubuntu0.22.04.1 Version table: *** 535.154.05-0ubuntu0.22.04.1 500 (phased 0%) 500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages 100 /var/lib/dpkg/status 535.146.02-0ubuntu0.22.04.1 500 (phased 0%) 500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages 535.129.03-0ubuntu0.22.04.1 500 (phased 0%) 500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages 535.113.01-0ubuntu0.22.04.3 500 (phased 0%) 500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages 535.104.05-0ubuntu0.22.04.4 500 (phased 0%) 500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages 535.86.05-0ubuntu0.22.04.1 500 (phased 0%) 500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages 535.54.03-0ubuntu0.22.04.1 500 (phased 0%) 500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages Out of the whole set of nvidia-driver-535 packages it is the only one of the kind. Demo script: #!/usr/bin/env bash nv_pkgs=( libnvidia-cfg1-535 libnvidia-common-535 libnvidia-compute-535 libnvidia-decode-535 libnvidia-encode-535 libnvidia-extra-535 libnvidia-fbc1-535 libnvidia-gl-535 nvidia-compute-utils-535 nvidia-dkms-535 nvidia-driver-535 nvidia-kernel-common-535 nvidia-kernel-source-535 nvidia-utils-535 xserver-xorg-video-nvidia-535 ) print_count () { printf '== %s ==\n' "$1" for pkg in "${nv_pkgs[@]}"; do n=$(apt-cache policy "$pkg" | grep -Ec "$2") printf '%s %s\n' "$n" "$pkg" done echo } print_count 'Available versions' '^.535' print_count 'Phasing' 'phased' Run result: == Available versions == 1 libnvidia-cfg1-535 7 libnvidia-common-535 1 libnvidia-compute-535 1 libnvidia-decode-535 1 libnvidia-encode-535 1 libnvidia-extra-535 1 libnvidia-fbc1-535 1 libnvidia-gl-535 1 nvidia-compute-utils-535 1 nvidia-dkms-535 1 nvidia-driver-535 1 nvidia-kernel-common-535 1 nvidia-kernel-source-535 1 nvidia-utils-535 1 xserver-xorg-video-nvidia-535 == Phasing == 0 libnvidia-cfg1-535 7 libnvidia-common-535 0 libnvidia-compute-535 0 libnvidia-decode-535 0 libnvidia-encode-535 0 libnvidia-extra-535 0 libnvidia-fbc1-535 0 libnvidia-gl-535 0 nvidia-compute-utils-535 0 nvidia-dkms-535 0 nvidia-driver-535 0 nvidia-kernel-common-535 0 nvidia-kernel-source-535 0 nvidia-utils-535 0 xserver-xorg-video-nvidia-535 Demo script to see all phasing packages: #!/usr/bin/env bash cat /var/lib/apt/lists/*_Packages | grep -E '^(Package|Version|Phased)' | grep -B2 --no-group-separator ^Phased | while read -r _ pkg; do IFS=- read -r pkg1 pkg2 <<< "$pkg" read -r _ vers
[Kernel-packages] [Bug 1815752] Re: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
** This bug is no longer a duplicate of bug 1573508 SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1815752 Title: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: I installed new kernel from xenial-proposed and this happened. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.104-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 318706/1281120 files, 2426738/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.4.0-143-generic Date: Wed Feb 13 12:18:21 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.104/build/nv-linux.h:2161:9: error: too many arguments to function ‘get_user_pages’ GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1179 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal PackageVersion: 340.104-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 13 12:57:38 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1815752/+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