Please update precise nvidia drivers to support 3.13 trusty backport kernel

Bug #1294163 reported by Mark Russell
54
This bug affects 9 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-304 (Ubuntu)
Invalid
Undecided
Unassigned
Precise
Fix Released
Medium
Alberto Milone
nvidia-graphics-drivers-304-updates (Ubuntu)
Invalid
Undecided
Unassigned
Precise
Fix Released
Medium
Alberto Milone
nvidia-graphics-drivers-331 (Ubuntu)
Invalid
Medium
Alberto Milone
Precise
Fix Released
Medium
Alberto Milone
nvidia-graphics-drivers-331-updates (Ubuntu)
Invalid
Medium
Alberto Milone
Precise
Fix Released
Medium
Alberto Milone

Bug Description

[Impact]

* The 3.13 trusty backport kernel for 12.04 will be released fairly soon. Some people have started testing the daily builds out the the Kernel Team PPA. However the NVIDIA binary drivers in precise need patches to support the 3.13 kernel.

[Test Case]

 * The latest Nvidia binary driver series in 12.04 should work with the upcomping 3.13 backport kernel; it currently does not.

[Regression Potential]

 * Low. The patches enable compatibility with newer kernels but do not affect installations on older kernels.

Changed in nvidia-graphics-drivers-331 (Ubuntu):
assignee: nobody → Alberto Milone (albertomilone)
Changed in nvidia-graphics-drivers-331-updates (Ubuntu):
assignee: nobody → Alberto Milone (albertomilone)
Changed in nvidia-graphics-drivers-331 (Ubuntu):
importance: Undecided → Medium
Changed in nvidia-graphics-drivers-331-updates (Ubuntu):
importance: Undecided → Medium
Changed in nvidia-graphics-drivers-331 (Ubuntu):
status: New → Triaged
Changed in nvidia-graphics-drivers-331-updates (Ubuntu):
status: New → Triaged
Changed in nvidia-graphics-drivers-331 (Ubuntu Precise):
assignee: nobody → Alberto Milone (albertomilone)
importance: Undecided → Medium
status: New → In Progress
Changed in nvidia-graphics-drivers-331-updates (Ubuntu Precise):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Alberto Milone (albertomilone)
Changed in nvidia-graphics-drivers-331 (Ubuntu):
status: Triaged → Invalid
Changed in nvidia-graphics-drivers-331-updates (Ubuntu):
status: Triaged → Invalid
Changed in nvidia-graphics-drivers-331 (Ubuntu Precise):
milestone: none → precise-updates
Changed in nvidia-graphics-drivers-331-updates (Ubuntu Precise):
milestone: none → precise-updates
Revision history for this message
Alberto Milone (albertomilone) wrote :

Please accept nvidia-graphics-drivers-331-updates (331.38-0ubuntu0.0.1) and nvidia-graphics-drivers-331 (331.20-0ubuntu0.0.2) into precise-proposed.

Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello Mark, or anyone else affected,

Accepted nvidia-graphics-drivers-331 into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/331.20-0ubuntu0.0.2 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in nvidia-graphics-drivers-331 (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
stargazer (stargazer05) wrote :

Unfortunately, the new nvidia driver 331.20-0ubuntu0.0.2 is not working with KDE.
Logging-in is possible but then a black screen is shown, but the xserver is not crashed.

In Xorg.log there is an error with acpi; log attached

[ 11.962] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 11.962] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 11.962] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 11.962] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 11.962] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 11.962] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 11.962] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 11.962] (II) NVIDIA(0): Config Options in the README.

Using the old nvidia 304 driver, I'm getting the following error at loading the nvidia module;

[ 5.543571] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 5.544024] nvidia: Unknown symbol acpi_os_wait_events_complete (err 0)

Maybe there is an incompatibility with the acpid or with the acpi kernel functions?

Best regards, Bernhard

Revision history for this message
stargazer (stargazer05) wrote :

Where can I download/find package nvidia-graphics-drivers-331-updates (331.38-0ubuntu0.0.1) to test this version?

Revision history for this message
Alberto Milone (albertomilone) wrote :

@Bernard: please type the following command:

sudo nvidia-bug-report.sh

 and attach the resulting nvidia-bug-report.log.gz

Revision history for this message
stargazer (stargazer05) wrote :

Log is attached;

Kernels 3.11.0-20-generic and 3.13.0-24 are both affected with this "black screen"-error in KDE.

It seems that KDE without effects works and Ubuntu/Unity with effects too.
Other OpenGL apps too.

Revision history for this message
Alberto Milone (albertomilone) wrote :

331 works fine here, even with hybrid graphics.

Please attach the following files:

1) the output of "apt-cache policy nvidia-331"
2) the output of "apt-cache policy acpid"

As for 304, I haven't fixed it to 3.13 yet.

The following line in your X log is very suspicious:
[ 10.975] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)

Revision history for this message
stargazer (stargazer05) wrote :

nvidia-331:
  Installed: 331.20-0ubuntu0.0.2
  Candidate: 331.20-0ubuntu0.0.2
  Version table:
 *** 331.20-0ubuntu0.0.2 0
        100 /var/lib/dpkg/status
     331.20-0ubuntu0.0.1 0
        500 http://at.archive.ubuntu.com/ubuntu/ precise-updates/restricted amd64 Packages

acpid:
  Installed: 1:2.0.10-1ubuntu3
  Candidate: 1:2.0.10-1ubuntu3
  Version table:
 *** 1:2.0.10-1ubuntu3 0
        500 http://at.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

Nvidia driver 304 works fine without problems, but after installing nvidia-331 also on older kernels (3.8, 3.11) the problem in KDE occurs.

For what purpose is package nvidia-331-uvm (NVIDIA Unified Memory kernel module)?

Revision history for this message
stargazer (stargazer05) wrote :

I have tried the following tasks, but without success;

- Reinstalling nvidia-331 driver (with purge)

- Installing nvidia-331-uvm together with nvidia-331

- Disable OpenGL2-Shader in kde-effects

The maximum working setup I get is two times KDE Logging-in (with reboot between) is working with effects, but a third time the black screen shows up;

Can you please provide another latest nvidia-driver 331.38-0ubuntu for e.g. with package nvidia-331-updates in precise-proposed?

Thanks, Bernhard

=> messages in .xsession-errors

OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 430/PCIe/SSE2
OpenGL version string: 4.4.0 NVIDIA 331.20
OpenGL shading language version string: 4.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 331.20
GPU class: GF100
OpenGL version: 4.4
GLSL version: 4.40
X server version: 1.14.5
Linux kernel version: 3.13
Direct rendering: yes
Requires strict binding: no
GLSL shaders: yes
Texture NPOT support: yes
kwin(3490): ""fsrestore1" - conversion of "0,0,0,0" to QRect failed"
kwin(3490): ""restore2" - conversion of "0,0,0,0" to QRect failed"
kwin(3490): ""fsrestore2" - conversion of "0,0,0,0" to QRect failed"

X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id: 0x2000247
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id: 0x200023e
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id: 0x2000235
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id: 0x200022c
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id: 0x2000223
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id: 0x200021a
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id: 0x2000211
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id: 0x2000208

X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 25 (X_SendEvent)
  Resource id: 0x20001cf
kwalletd: Fatal IO error: client killed
kglobalaccel: Fatal IO error: client killed
kded4: Fatal IO error: client killed
kactivitymanagerd: Fatal IO error: client killed
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
klauncher: Exiting on signal 1
kdeinit4: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
Unexpected response from KInit (response = 0).
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.

tags: added: kde
Revision history for this message
stargazer (stargazer05) wrote :

Or latest: nvidia 331.67
http://www.nvidia.com/download/driverResults.aspx/75019/en-us

Version: 331.67
Release Date: 2014.4.9

- Fixed a bug that could lead to crashes when running Left 4 Dead 2 with threaded optimizations enabled.
- Updated the makefile for the NVIDIA kernel module to work around a bug in older versions of GNU Make that prevented the NVIDIA kernel module from building correctly. This bug was fixed in version 3.81 of GNU Make.
- Fixed a bug that causes some X clients to be disconnected from the X server when the screen is resized while RandR 1.4 display offloading is in use.
- Fixed a bug that could cause display corruption when resuming from suspend on systems using RandR 1.4 display offloading with recent Linux kernels.
- Added support for Tridelity SL stereo mode.
- Fixed a bug that could cause nvidia-settings to crash or display incorrect information after switching virtual terminals while a color correction confirmation countdown was active.
- Added a missing 32-bit compatibility library for libnvidia-fbc.so to the x86_64 Linux installer package.

Revision history for this message
Alberto Milone (albertomilone) wrote :

Unfortunately releases >= 331.49 break hybrid graphics, and we're waiting for NVIDIA to fix the issue before we update the driver in Ubuntu.

You can still install an updated driver from the xorg-edgers PPA.

Can you reproduce the problem if you enter an Xfce session or a Unity session?

Revision history for this message
stargazer (stargazer05) wrote :

version 331.38:
Working; Gnome/Unity, KDE *without* effects
Not Working: KDE *with* effects => blackscreen

It seems like that it is a KDE issue with this nvidia driver version.

Tested from xorg-edgers ppa
331.67:
All sessions working, but with acpi failed message in Xorg.0.log
Hibernate is not working (freeze after resume)=> This is a NoGo, because I use this feature daily!

304.121:
All working fine, but with acpi failed message in Xorg.0.log and hibernate is working too :-) .

I'll stay at version 304.121 from xorg-edgers until a fixed version is available in precise repos.

Revision history for this message
stargazer (stargazer05) wrote :

The new package nvidia-331-updates 331.38-0ubuntu0.0.1 from precise-proposed is working fine now with KDE and hibernate.
=> no black screen in KDE and no acpid failed messages in Xorg.log anymore !

kernel: 3.13.0-27-generic , xserver: 1.14.6-0ubuntu1~precise1

Thanks, Bernhard

Revision history for this message
Bartosz Kosiorek (gang65) wrote :

nvidia-graphics-drivers-331-updates (331.38-0ubuntu0.0.1) package from proposed is working perfectly for me (Precise)

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nvidia-graphics-drivers-331 - 331.20-0ubuntu0.0.2

---------------
nvidia-graphics-drivers-331 (331.20-0ubuntu0.0.2) precise-proposed; urgency=medium

  [ Shih-Yuan Lee (FourDollars) ]
  * debian/nvidia_supported,
    debian/rules:
    - Add subsystem ID parsing support for LP: #1255813.

  [ Alberto Milone ]
  * debian/dkms_nvidia/patches/register-VT-switch-requirements.patch:
    - Make sure to call pm_vt_switch_{required,unregister}(), so that
      the kernel knows that the driver requires a vt switch at
      suspend/resume time. This resolves a corruption issue on resume
      from S3 (LP: #1210077).
      Thanks to NVIDIA for the patch.
  * debian/dkms_nvidia_uvm/patches/buildfix_kernel_3.12.patch,
    debian/dkms_nvidia/patches/buildfix_kernel_3.13.patch:
    - Add support for Linux 3.13 (LP: #1294163).
 -- Alberto Milone <email address hidden> Thu, 20 Mar 2014 11:50:12 +0100

Changed in nvidia-graphics-drivers-331 (Ubuntu Precise):
status: Fix Committed → Fix Released
Revision history for this message
Scott Kitterman (kitterman) wrote : Update Released

The verification of the Stable Release Update for nvidia-graphics-drivers-331 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (3.6 KiB)

This bug was fixed in the package nvidia-graphics-drivers-331-updates - 331.38-0ubuntu0.0.1

---------------
nvidia-graphics-drivers-331-updates (331.38-0ubuntu0.0.1) precise-proposed; urgency=medium

  [ Shih-Yuan Lee (FourDollars) ]
  * debian/nvidia_supported,
    debian/rules:
    - Add subsystem ID parsing support for LP: #1255813.

  [ Alberto Milone ]
  * debian/dkms_nvidia/patches/register-VT-switch-requirements.patch:
    - Make sure to call pm_vt_switch_{required,unregister}(), so that
      the kernel knows that the driver requires a vt switch at
      suspend/resume time. This resolves a corruption issue on resume
      from S3 (LP: #1210077).
      Thanks to NVIDIA for the patch.
  * debian/dkms_nvidia_uvm/patches/buildfix_kernel_3.12.patch,
    debian/dkms_nvidia/patches/buildfix_kernel_3.13.patch:
    - Add support for Linux 3.13 (LP: #1294163).
  * debian/substvars:
    - Add support for X ABI 15 and lts-trusty.
  * New upstream release:
    - Added support for X.org xserver ABI 15 (xorg-server 1.15).
    - Fixed a bug that caused the X server to crash if video memory
      is exhausted and the GPU does not support rendering to system
      memory.
    - Updated nvidia-installer to make the --multiple-kernel-modules
      option imply the --no-unified-memory option: Unified memory is
      incompatible with multiple kernel modules.
    - Updated the behavior of the nvidia-settings PowerMizer
      Preferred Mode drop-down menu, to make the setting apply
      consistently across all GPUs in an SLI group.
    - Improved the robustness of the NVIDIA X driver in scenarios
      where GPU-accessible memory for allocating pixmaps was
      exhausted.
    - Added NV-CONTROL attributes to control the brightness of the
      illuminated logos on certain graphics boards.For example, to
      turn off the illumination of the
      GEFORCE GTX
      lettering on the GeForce GTX 780, use
      nvidia-settings --assign GPULogoBrightness=0
    - Fixed a bug that prevented screen transformations from being
      applied properly when starting X.
    - GLX protocol for the following OpenGL extensions from OpenGL
      2.1 and OpenGL 3.0 have been promoted from unofficial to ARB
      approved official status:
        GL_ARB_pixel_buffer_object
        GL_NV_conditional_render
        GL_ARB_map_buffer_range
        GL_EXT_texture_integer
        GL_ARB_vertex_array_object
      GL_ARB_pixel_buffer_object was the last piece of protocol
      needed to have official support for indirect rendering with all
      OpenGL 2.1 commands.
    - GLX Protocol for the miscellaneous OpenGL 3.0 commands not
      associated with specific extensions has also been promoted from
      unofficial to ARB approved status.
    - Deprecated display mask related configuration of display
      devices via NV-CONTROL and nvidia-settings.Display target
      specifications should be used instead - A display target is one
      of the display's valid names, with an optional GPU or X screen
      qualifier.
    - Deprecated the following NV-CONTROL attributes:
        NV_CTRL_CONNECTED_DISPLAYS
        NV_CTRL_ENABLED_DISPLAYS
        NV_CTRL_ASSOCIATED_DISPLAYS
       ...

Read more...

Changed in nvidia-graphics-drivers-331-updates (Ubuntu Precise):
status: In Progress → Fix Released
Revision history for this message
Ryan Tandy (rtandy) wrote :

Hi Alberto,

You wrote: "As for 304, I haven't fixed it to 3.13 yet." That appears to still be the case in precise.

I applied the patch from http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/nvidia-graphics-drivers-304/trusty/revision/21 to nvidia-304 from precise, and it works for me. Would you accept a merge proposal with that change?

(I guess we also need 304.117 in order to support the lts-trusty X server...)

Can you please add nvidia-304{,-updates} tasks for Precise to this bug for tracking? (If you prefer I can open a separate bug.)

Changed in nvidia-graphics-drivers-304 (Ubuntu):
status: New → Invalid
Changed in nvidia-graphics-drivers-304-updates (Ubuntu):
status: New → Invalid
Changed in nvidia-graphics-drivers-304-updates (Ubuntu Precise):
status: New → Triaged
Changed in nvidia-graphics-drivers-304 (Ubuntu Precise):
status: New → Triaged
importance: Undecided → Medium
Changed in nvidia-graphics-drivers-304-updates (Ubuntu Precise):
importance: Undecided → Medium
assignee: nobody → Alberto Milone (albertomilone)
Changed in nvidia-graphics-drivers-304 (Ubuntu Precise):
assignee: nobody → Alberto Milone (albertomilone)
Revision history for this message
stargazer (stargazer05) wrote :

After installing the trusty xstack too, I ran into the black screen issue, which many people suffer from;
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283938

apt-get install -V libglapi-mesa-lts-trusty libgl1-mesa-glx-lts-trusty xserver-xorg-lts-trusty xserver-xorg-input-all-lts-trusty xserver-xorg-video-all-lts-trusty libgl1-mesa-dri-lts-trusty x11-xserver-utils-lts-trusty libglapi-mesa-lts-trusty:i386 libgl1-mesa-dri-lts-trusty:i386 libgl1-mesa-glx-lts-trusty:i386 libgles2-mesa-lts-trusty libglapi-mesa-lts-trusty mesa-vdpau-drivers-lts-trusty

kernel 3.13.0-30-generic #54~precise2, nvidia-331-updates 331.38-0ubuntu0.0.1
Xorg message after black screen: (after wake up from hibernate)

(EE) NVIDIA(GPU-0): WAIT: (E, 0, 0x857d)

It seems to be a combination of kernel, Xorg-server, X-components, which triggers this bug, because without the trusty Xstack there was no black screen issue with this kernel version.

Revision history for this message
stargazer (stargazer05) wrote :

Supplement to this black screen issue with nvidia-331-updates 331.38-0ubuntu0.0.1;

I've found a workaround for my config/setup
(12.04 with kernel and Xstack from trusty with nvidia driver, lightdm with kde, and only hibernate used);

Boot your system to lightdm, then login to your Desktop Environment (KDE) , let it finish ...
After that logout back to lightdm screen and login again !
=> Now try to hibernate, after the resume there is no black screen anymore and you can unlock the screen and use your desktop!!

My résumé after testing is that maybe there is a race condition in the services/daemons (acpid, dbus, lightdm) or different bugs are playing together (Kernel, X, drivers, daemons).

There are also no acpi messages in /var/log/Xorg.0.log anymore (also no acpi failed messages).

Any suggestions?

Are there news about the HWE of the nvidia 304 driver for kernel 3.13?
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/nvidia-graphics-drivers-304/trusty/revision/21

Revision history for this message
stargazer (stargazer05) wrote :

Adding HIBERNATE_RESUME_POST_VIDEO="no" to /etc/pm/config.d/hibernate solved for me the problem.

Now the resume from hibernate is working without a black screen/freeze.

Revision history for this message
stargazer (stargazer05) wrote :

Correction:
The workaround, described above, does not solve the problem, black screens after resume from hibernate again.

Adding pci=nomsi to /etc/default/grub at GRUB_CMDLINE_LINUX="pci=nomsi" seems to help, no black screens so far.
I'm testing this at the moment.

Furthermore I've tested driver nvidia-331_331.89-0ubuntu0.0.1~xedgers12.04.1_amd64 from ppa xorg-edgers, but no success without pci=nomsi.

Changed in nvidia-graphics-drivers-304 (Ubuntu Precise):
status: Triaged → In Progress
Changed in nvidia-graphics-drivers-304-updates (Ubuntu Precise):
status: Triaged → In Progress
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Mark, or anyone else affected,

Accepted nvidia-graphics-drivers-304-updates into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/304.123-0ubuntu0.0.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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in nvidia-graphics-drivers-304-updates (Ubuntu Precise):
status: In Progress → Fix Committed
tags: removed: verification-done
tags: added: verification-needed
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello Mark, or anyone else affected,

Accepted nvidia-graphics-drivers-304 into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/304.123-0ubuntu0.0.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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in nvidia-graphics-drivers-304 (Ubuntu Precise):
status: In Progress → Fix Committed
Revision history for this message
Ryan Tandy (rtandy) wrote :

nvidia-304 from proposed boots and runs on my test hardware (6150SE and 210). I can't comment on the problems reported earlier in this thread since I haven't experienced any of them.

I will put some users on this tomorrow and see how it goes. Thanks for preparing this update!

Revision history for this message
stargazer (stargazer05) wrote :

Update to the black-screen-issue after hibernate;

Since kernel update 3.13.0-37.64 I can use MSI-interrupts with the nvidia module again and the black-screen-issue after hibernate is gone.

Thanks!

Revision history for this message
Ryan Tandy (rtandy) wrote :

No problems reported with nvidia-304 in my environment. Marking verified.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nvidia-graphics-drivers-304-updates - 304.123-0ubuntu0.0.1

---------------
nvidia-graphics-drivers-304-updates (304.123-0ubuntu0.0.1) precise-proposed; urgency=medium

  * debian/substvars:
    - Add support for X ABIs 15 and 18 and for lts-trusty (LP: #1294163).
  * New upstream release:
    - Improved compatibility with recent Linux kernels (LP: #1294163).
    - Fixed a bug that could result in system instability while
      restoring the VGA console.
    - Fixed an interaction problem with xserver 1.15 that
      occasionally caused OpenGL applications to continue rendering
      when they are minimized or unmapped.
    - Updated nvidia-bug-report.sh to search the systemd journal for
      X server logs and messages from the NVIDIA kernel module.
    - Added support for X.org xserver ABI 18 (xorg-server 1.16).
    - Fixed a bug that caused corruption or blank screens on monitors
      that use EDID version 1.3 or older when they are connected via
      DisplayPort on graphics boards that use external DisplayPort
      encoders, such as the Quadro FX 4800.
 -- Alberto Milone <email address hidden> Mon, 15 Sep 2014 16:21:35 +0200

Changed in nvidia-graphics-drivers-304-updates (Ubuntu Precise):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nvidia-graphics-drivers-304 - 304.123-0ubuntu0.0.1

---------------
nvidia-graphics-drivers-304 (304.123-0ubuntu0.0.1) precise-proposed; urgency=medium

  * debian/substvars:
    - Add support for X ABIs 15 and 18 and for lts-trusty (LP: #1294163).
  * New upstream release:
    - Improved compatibility with recent Linux kernels (LP: #1294163).
    - Fixed a bug that could result in system instability while
      restoring the VGA console.
    - Fixed an interaction problem with xserver 1.15 that
      occasionally caused OpenGL applications to continue rendering
      when they are minimized or unmapped.
    - Updated nvidia-bug-report.sh to search the systemd journal for
      X server logs and messages from the NVIDIA kernel module.
    - Added support for X.org xserver ABI 18 (xorg-server 1.16).
    - Fixed a bug that caused corruption or blank screens on monitors
      that use EDID version 1.3 or older when they are connected via
      DisplayPort on graphics boards that use external DisplayPort
      encoders, such as the Quadro FX 4800.
 -- Alberto Milone <email address hidden> Mon, 15 Sep 2014 16:17:18 +0200

Changed in nvidia-graphics-drivers-304 (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.