This bug was fixed in the package linux-restricted-modules - 5.3.0-51.44 --------------- linux-restricted-modules (5.3.0-51.44) eoan; urgency=medium
* Master version: 5.3.0-51.44 -- Thadeu Lima de Souza Cascardo <casca...@canonical.com> Wed, 22 Apr 2020 18:17:10 -0300 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux-restricted-modules source package in Eoan: Fix Released Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: Fix Committed Status in nvidia-settings source package in Eoan: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Enabled parallel GLSL shader linking by default; i.e., allow GL_ARB_parallel_shader_compile to work without first calling glMaxShaderCompilerThreadsARB(). - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC Compatible monitors on supported GPUs.For more details, see "Configuring Multiple Display Devices on One X Screen" in the README. Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast extensions.For more details, see the "Configuring SLI and Multi-GPU FrameRendering" chapter of the README, and the extension specifications: https://www.khronos.org/registry/OpenGL/extensions/NV/GLX_NV_multigpu_context.txt https://www.khronos.org/registry/OpenGL/extensions/NV/NV_gpu_multicast.txt - Fixed a bug that prevented Vulkan applications running on systems configured for SLI. Vulkan applications can now run while SLI is enabled; however, they will only be able to use a single GPU. - Simplified the nvidia-sleep.sh sample script to no longer depend on unreliable detection of the current VT through X server logs. - Added EGL support for PRIME render offload. Please see the PRIME Render Offload chapter in the README for configuration details. - Fixed a regression introduced in 435.19.02 that would cause some applications which use the VK_KHR_DISPLAY extension to result in a segmentation fault. - Enabled HardDPMS by default. See the README entry on the X configuration option "HardDPMS" for more information. - Fixed a bug which caused corruption in the following DXVK titles: Saints Row IV Saints Row: The Third - Added VP9 decode support to the NVIDIA VDPAU driver. See the VDPAU Support appendix in the README for supported VP9 decoder profiles. - Fixed a bug that could cause heapUsage values reported by VK_EXT_memory_budget to not immediately update after vkFreeMemory was called. - Changed GPU clock management strategy to more quickly ramp down clocks after a drop in GPU utilization. - Added X configuration option, "SidebandSocketPath", which controls the directory in which the X driver will create a pathname UNIX domain socket used to communicate with the NVIDIA OpenGL, Vulkan and VDPAU driver components. - The X driver will now create a fallback pathname UNIX domain socket in the directory specified by the "SidebandSocketPath" option, or /var/run by default, which will be used by other NVIDIA driver components if they are unable to connect to the default abstract socket.This fixes a bug where graphics applications run within a network namespace (which prevents the use of abstract sockets) were unable to take advantage of some driver features, such as G-Sync. - Fall back to system memory when video memory is full for some driver-internal allocations. This can help fix Xid 13 and Xid 31 cases in Vulkan applications when video memory is full. - Fixed a bug that could cause a blank screen on some DisplayPort monitors when logging in to GNOME, if the nvidia-drm kernel module parameter modeset=1 is specified. - Fixed a bug that prevented NVIDIA GPUs from entering the low-power D3 state when entering suspend-to-idle (s2idle). Note that on some systems this may expose an existing timing issue in the Linux kernel; see the "Known Issues and Workarounds" section of the "Configuring Power Management Support" chapter of the README for more details. 390.132: * New upstream release (LP: #1854485): - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/do-not-call-pci_save_state.patch, debian/dkms_nvidia/patches/disable_fstack-clash-protection_fcf-protection.patch: - Do not call pci_save_state (as the more recent driver series do). - Fall back on /usr/bin/gcc when cc is not available. - Detect and disable the fstack-clash-protection fcf-protection flags. - Drop buildfix_kernel_5.2.patch and buildfix_kernel_5.3.patch (now in the upstream release). * debian/templates/libnvidia-common-flavour.install.in, debian/templates/libnvidia-gl-flavour-dev.install.in, debian/templates/libnvidia-gl-flavour.install.in, debian/templates/nvidia-compute-utils-flavour.install.in, debian/templates/nvidia-compute-utils-flavour.nvidia-persistenced.service.in, debian/templates/nvidia-driver-flavour.docs.in, debian/templates/nvidia-utils-flavour.install.in: - Remove final / from installation paths (to match the manifest file). - Add the StopWhenUnneeded=true field to nvidia-persistenced. * debian/templates/control: - Update to dpkg-dev (>= 1.17.11~). - Rearrange the cuda dependencies, and add a needed dependency on libnvidia-cfg1. 340.108: * New upstream release (LP: #1854485): - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Updated nvidia-bug-report.sh to search the systemd journal for gdm-x-session logs. - Fixed a bug that could prevent nvidia-xconfig from disabling the X Composite extension on version 1.20 of the X.org X server. - Fixed a build failure, "too many arguments to function 'get_user_pages'", when building the NVIDIA kernel module for Linux kernel v4.4.168. - Fixed a build failure, "implicit declaration of function do_gettimeofday", when building the NVIDIA kernel module for Linux kernel 5.0 release candidates. * debian/templates/dkms_nvidia.conf.in: - Drop the following patches (no longer needed in 340.108): buildfix_kernel_5.0.patch, buildfix_kernel_5.3.patch. - Fall back on /usr/bin/gcc when cc is not available. * debian/dkms_nvidia/patches/buildfix_kernel_4.11.patch, debian/dkms_nvidia/patches/do-not-call-pci_save_state.patch, debian/dkms_nvidia/patches/use-kmem_cache_create_usercopy-on-4.16.patch, debian/dkms_nvidia/patches/buildfix_kernel_5.2.patch: - Refresh patches. * debian/dkms_nvidia/patches/disable_fstack-clash-protection_fcf-protection.patch, debian/dkms_nvidia/patches/do-not-call-pci_save_state.patch: - Do not call pci_save_state (as the more recent driver series do). - Detect and disable the fstack-clash-protection fcf-protection flags. nvidia-settings (440.44-0ubuntu0.18.04.1): * New upstream release. * debian/patches/13_libxnvctrl_so_0.patch: - Add -fPIC to the XNVCTRL_CFLAGS. This seems to be needed only in 18.04. * debian/patches/08_add_prime_support.patch: - Refresh and make on-demand mode optional. This makes the same patch work on systems where on-demand mode is not available yet. * debian/patches/05_add_polkit_support.patch, debian/patches/06_remove_local_prefix.patch, debian/patches/07_remove_features_for_legacy.patch, debian/patches/08_add_prime_support.patch, debian/patches/10_legacy_vdpau.patch, debian/patches/11_link_as-needed.patch, debian/patches/12_nostrip.patch, debian/patches/13_libxnvctrl_so_0.patch, debian/patches/15_clean.patch, debian/patches/16_gzip-n.patch, debian/patches/link-order.diff: - Refresh patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
