| Summary: | stabilize =x11-drivers/nvidia-drivers-302.17 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Doug Goldstein (RETIRED) <cardoe> |
| Component: | [OLD] Keywording and Stabilization | Assignee: | Doug Goldstein (RETIRED) <cardoe> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | amd64, nvinson234, sven.koehler, x86 |
| Priority: | Normal | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Doug Goldstein (RETIRED)
2012-07-14 20:18:16 UTC
Just to let you know: on my Laptop (Dell E6410), nvidia-drivers 302.17 resultet in a black screen after wakeup from suspend to ram. This is fixed in the 304.22 beta driver. Some people might be surprised after the update to 302.17. (In reply to comment #1) > Just to let you know: on my Laptop (Dell E6410), nvidia-drivers 302.17 > resultet in a black screen after wakeup from suspend to ram. This is fixed > in the 304.22 beta driver. > > Some people might be surprised after the update to 302.17. Some people are always surprised because not ever driver release works 100% for every piece of hardware and configuration. I would ask that this version not be stabalized. The issue Sven brings up is widespread and is even mentioned in the 304.22 changelog. From the changelog: Fixed a bug that could cause G8x, G9x, and GT2xx GPUs to display a black screen or corruption after waking up from suspend. For what it's worth, I'm using a Thinkpad T510 that is also affected by this issue. If this doesn't fix important bugs over previous version, I also think we shouldn't stabilize a version known to break things for so many cards Version is masked and the table request is closed. |