From http://www.nvnews.net/vbulletin/showthread.php?t=122606: Current official release: 185.18.29 Changelog indicates most changes are to cuda and vdpau bugfixes. Not tested it yet myself. Reproducible: Always
re-assigned to first developer in list of 4. Others are CC'd, feel free to modify further :).
Just copied 185.18.14 ebuild from portage, it compiled, rebooted and played openarena fine on ~amd64 system with vanilla-sources-2.6.31-rc4.
Added to CVS, thanks for reporting the new version.
after upgrade to 185.18.29, i can't start my x server, so i mask it, and downgrade to 185.29.14, everything works find. 01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1) x11-base/xorg-server-1.6.2.901
http://www.nvnews.net/vbulletin/showthread.php?t=136564 Says the newest version is broken on an Quadro NVS 140M. That forum is the place to watch for official response from nVidia. Can the ebuild be conditional on PCI id of the card? Or at least explicitly code an error on detecting the card? If not, at least add text that displays for everyone that says it doesn't work with those GPUs.
I can confirm the problems with 185.18.29 on a Quadro NVS 140M. Starting X causes a kernel OOPS in the nvidia driver. Reverting to .14 fixed it.
Confirm problem starting X on HP Pavilion tx2010eo (GF-6150Go). Xorg.log ends with (no further lines): (II) NVIDIA(0): ACPI display change hotkey events enabled: the X server is new (II) NVIDIA(0): enough to receive ACPI display change hotkey events. blank screen, unable to switch terminals. Reproducible for xorg-server 1.6.2.901 and 1.6.2-r1, vanilla-sources 2.6.30.3, amd64 and x86. Revert to 185.18.14 fixes the problem
(In reply to comment #6) > I can confirm the problems with 185.18.29 on a Quadro NVS 140M. Starting X > causes a kernel OOPS in the nvidia driver. Reverting to .14 fixed it. /me too. So can .29 please be masked.
Same problem here with Quadro NVS 140M (rev a1), see Bug 279588
BTW: This thread indicates that the problem may also occur with 190.16: http://www.nvnews.net/vbulletin/showthread.php?t=136143
oficial 185.18.31 is out now
same problem with Quadro NVS 140M :( (In reply to comment #11) > oficial 185.18.31 is out now >
I just added a device compatibility check for Quadro NVS 140M to .29 and .31. If you try to emerge the ebuilds, you will be warned about the incompatibility. Hope that helps.
re: comment #12 Did you post an nvidia-bug-report.log on their forums like they ask in: http://www.nvnews.net/vbulletin/showthread.php?t=46678 ? This bad QA on the stable branch is surprising. They should at least be able to not cause regressions that are easy to reproduce. re: comment #13 Thanks a lot!
the Quadro NVS 140 issue is being tracked on bug #279588 When I get further info from NVIDIA I'll attach it there.