** Description changed: Update NVIDIA the 430 series and introduce the 435 series from 19.10. [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 - <TODO Document any QA done, automated and manual> + 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. - <TODO: attach nvidia-proposed test artifacts for every SRU release, not - a link as links expire> - [Discussion] 430.50: - * New upstream release (LP: #1844126): - - Fixed display color range handling on pre-Turing GPUs, such - that when limited color range is selected through the display - controls page in nvidia-settings, output pixel values will be - correctly clamped to Consumer Technology Association (CTA) - range. + * New upstream release (LP: #1844126): + - Fixed display color range handling on pre-Turing GPUs, such + that when limited color range is selected through the display + controls page in nvidia-settings, output pixel values will be + correctly clamped to Consumer Technology Association (CTA) + range. 435.21: - - * New upstream release: - - Fixed a bug that caused the X server to crash when using - HardDPMS with an NVIDIA-driven GPU Screen. - - Fixed a bug which caused the kernel to panic when exiting a - single X server when multiple X servers were active and in an - SLI configuration. - - Fixed a regression introduced in the 430.* series of releases - that caused a segmentation fault in libnvcuvid.so while using - Video Codec SDK APIs on certain graphics boards. - - Added initial experimental support for runtime D3 (RTD3) power - management on Turing notebook GPUs. - - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3) - power management information. - - Improved nvidia-bug-report.sh to collect ACPI tables when the - acpidump tool is available. - - Added Vulkan and OpenGL+GLX support for PRIME render offload. - Please see the PRIME Render Offload chapter in the README for - system requirements and configuration details. - - Added support for changing Digital Vibrance in the display - controls section of nvidia-settings on Turing hardware. - - Fixed the cuvidParseVideoData API in the NVCUVID driver to - correctly propagate errors returned by the - PFNVIDSEQUENCECALLBACK callback function to the application. - - Fixed a bug that caused the NVIDIA X driver to behave - incorrectly or crash when a client queried Xinerama information - on X servers with a non-NVIDIA X screen as screen 0. - - Fixed the "Image Settings" options in the "OpenGL Settings" - page of nvidia-settings for Quadro GPUs. Previously, OpenGL - rendering on Quadro would behave as if the "High Quality" - option were selected regardless of the selection. Now, the - setting will default to "High Quality" for Quadro but selecting - a lower option will affect rendering accordingly. (Other GPUs - are unchanged: the default remains "Quality", but other options - can be selected if desired.) - - Fixed a bug that could cause Vulkan applications to generate - spurious warning messages about a missing NV-GLX extension. - - Fixed a bug that prevented nvidia-drm from marking preferred - modes properly when reporting display information via the DRM- - KMS API. - - Fixed the NvEncodeAPI driver to correctly reject the encoding - of sequences with resolutions smaller than what the NVENC - supports. - - Fixed display color range handling on pre-Turing GPUs, such - that when limited color range is selected through the display - controls page in nvidia-settings, output pixel values will be - correctly clamped to Consumer Technology Association (CTA) - range. + + * New upstream release: + - Fixed a bug that caused the X server to crash when using + HardDPMS with an NVIDIA-driven GPU Screen. + - Fixed a bug which caused the kernel to panic when exiting a + single X server when multiple X servers were active and in an + SLI configuration. + - Fixed a regression introduced in the 430.* series of releases + that caused a segmentation fault in libnvcuvid.so while using + Video Codec SDK APIs on certain graphics boards. + - Added initial experimental support for runtime D3 (RTD3) power + management on Turing notebook GPUs. + - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3) + power management information. + - Improved nvidia-bug-report.sh to collect ACPI tables when the + acpidump tool is available. + - Added Vulkan and OpenGL+GLX support for PRIME render offload. + Please see the PRIME Render Offload chapter in the README for + system requirements and configuration details. + - Added support for changing Digital Vibrance in the display + controls section of nvidia-settings on Turing hardware. + - Fixed the cuvidParseVideoData API in the NVCUVID driver to + correctly propagate errors returned by the + PFNVIDSEQUENCECALLBACK callback function to the application. + - Fixed a bug that caused the NVIDIA X driver to behave + incorrectly or crash when a client queried Xinerama information + on X servers with a non-NVIDIA X screen as screen 0. + - Fixed the "Image Settings" options in the "OpenGL Settings" + page of nvidia-settings for Quadro GPUs. Previously, OpenGL + rendering on Quadro would behave as if the "High Quality" + option were selected regardless of the selection. Now, the + setting will default to "High Quality" for Quadro but selecting + a lower option will affect rendering accordingly. (Other GPUs + are unchanged: the default remains "Quality", but other options + can be selected if desired.) + - Fixed a bug that could cause Vulkan applications to generate + spurious warning messages about a missing NV-GLX extension. + - Fixed a bug that prevented nvidia-drm from marking preferred + modes properly when reporting display information via the DRM- + KMS API. + - Fixed the NvEncodeAPI driver to correctly reject the encoding + of sequences with resolutions smaller than what the NVENC + supports. + - Fixed display color range handling on pre-Turing GPUs, such + that when limited color range is selected through the display + controls page in nvidia-settings, output pixel values will be + correctly clamped to Consumer Technology Association (CTA) + range.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1844126 Title: Update NVIDIA the 430 series and introduce the 435 series Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 source package in Bionic: In Progress Status in nvidia-graphics-drivers-435 source package in Bionic: In Progress Bug description: Update NVIDIA the 430 series and introduce the 435 series from 19.10. [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] 430.50: * New upstream release (LP: #1844126): - Fixed display color range handling on pre-Turing GPUs, such that when limited color range is selected through the display controls page in nvidia-settings, output pixel values will be correctly clamped to Consumer Technology Association (CTA) range. 435.21: * New upstream release: - Fixed a bug that caused the X server to crash when using HardDPMS with an NVIDIA-driven GPU Screen. - Fixed a bug which caused the kernel to panic when exiting a single X server when multiple X servers were active and in an SLI configuration. - Fixed a regression introduced in the 430.* series of releases that caused a segmentation fault in libnvcuvid.so while using Video Codec SDK APIs on certain graphics boards. - Added initial experimental support for runtime D3 (RTD3) power management on Turing notebook GPUs. - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3) power management information. - Improved nvidia-bug-report.sh to collect ACPI tables when the acpidump tool is available. - Added Vulkan and OpenGL+GLX support for PRIME render offload. Please see the PRIME Render Offload chapter in the README for system requirements and configuration details. - Added support for changing Digital Vibrance in the display controls section of nvidia-settings on Turing hardware. - Fixed the cuvidParseVideoData API in the NVCUVID driver to correctly propagate errors returned by the PFNVIDSEQUENCECALLBACK callback function to the application. - Fixed a bug that caused the NVIDIA X driver to behave incorrectly or crash when a client queried Xinerama information on X servers with a non-NVIDIA X screen as screen 0. - Fixed the "Image Settings" options in the "OpenGL Settings" page of nvidia-settings for Quadro GPUs. Previously, OpenGL rendering on Quadro would behave as if the "High Quality" option were selected regardless of the selection. Now, the setting will default to "High Quality" for Quadro but selecting a lower option will affect rendering accordingly. (Other GPUs are unchanged: the default remains "Quality", but other options can be selected if desired.) - Fixed a bug that could cause Vulkan applications to generate spurious warning messages about a missing NV-GLX extension. - Fixed a bug that prevented nvidia-drm from marking preferred modes properly when reporting display information via the DRM- KMS API. - Fixed the NvEncodeAPI driver to correctly reject the encoding of sequences with resolutions smaller than what the NVENC supports. - Fixed display color range handling on pre-Turing GPUs, such that when limited color range is selected through the display controls page in nvidia-settings, output pixel values will be correctly clamped to Consumer Technology Association (CTA) range. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1844126/+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
