Update NVIDIA the 430 series and introduce the 435 series
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers-430 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Medium
|
Alberto Milone | ||
nvidia-graphics-drivers-435 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Medium
|
Alberto Milone | ||
nvidia-settings (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
In Progress
|
Undecided
|
Unassigned |
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:/
Certification test suite must pass on a range of hardware:
https:/
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-
power management information.
- Improved nvidia-
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
PFNVIDSEQ
- 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.
Changed in nvidia-graphics-drivers-430 (Ubuntu): | |
status: | New → Fix Released |
Changed in nvidia-graphics-drivers-430 (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in nvidia-graphics-drivers-435 (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in nvidia-graphics-drivers-435 (Ubuntu): | |
status: | New → Fix Released |
Changed in nvidia-graphics-drivers-430 (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Changed in nvidia-graphics-drivers-435 (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Changed in nvidia-graphics-drivers-430 (Ubuntu Bionic): | |
assignee: | nobody → Alberto Milone (albertomilone) |
Changed in nvidia-graphics-drivers-435 (Ubuntu Bionic): | |
assignee: | nobody → Alberto Milone (albertomilone) |
description: | updated |
description: | updated |
Changed in nvidia-settings (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in nvidia-settings (Ubuntu): | |
status: | New → Fix Released |
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
tags: |
added: verification-done removed: verification-needed |
Hello Alberto, or anyone else affected,
Accepted nvidia- graphics- drivers- 430 into bionic-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ nvidia- graphics- drivers- 430/430. 50-0ubuntu0. 18.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification- needed- bionic to verification- done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- bionic. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.