Message boards :
Number crunching :
@Pre-FERMI nVidia GPU users: Important warning
Message board moderation
Previous · 1 . . . 5 · 6 · 7 · 8 · 9 · 10 · 11 . . . 13 · Next
Author | Message |
---|---|
mrchips Send message Joined: 12 Dec 04 Posts: 17 Credit: 26,590,842 RAC: 8 |
Thanks Richard, I downloaded an older driver 337.88, I just got 90 WU's for the gpu. I'm running on all cylinders now. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Thanks Richard, I downloaded an older driver 337.88, I just got 90 WU's for the gpu. I'm running on all cylinders now. No problem. It's interesting, though, because it does imply that the project's pre-emptive measures to block the faulty driver may have been applied rather too liberally. |
Jacob Klein Send message Joined: 15 Apr 11 Posts: 149 Credit: 9,783,406 RAC: 9 |
I have another minor update from NVIDIA. 5 November 2014 9:32 pm -- Kevin Kang 12 November 2014 11:28 am -- JacobKlein 14 November 2014 1:21 am -- Kevin Kang 5 December 2014 8:40 pm -- JacobKlein [NEW] 10 December 2015 2:54 am |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
I have another minor update from NVIDIA. I presume you've volunteered your rig for the test programme? Give me a shout if you see a GeForce (9800GT) version being tested. |
Jacob Klein Send message Joined: 15 Apr 11 Posts: 149 Credit: 9,783,406 RAC: 9 |
My main rig is always a test ground for everything :) But yes, if NVIDIA requests me to test anything, I'll see if I can get you access to test against your 9800GT. Thanks for volunteering. |
Jacob Klein Send message Joined: 15 Apr 11 Posts: 149 Credit: 9,783,406 RAC: 9 |
I have another update (significant) from NVIDIA. 5 November 2014 9:32 pm -- Kevin Kang 12 November 2014 11:28 am -- JacobKlein 14 November 2014 1:21 am -- Kevin Kang 5 December 2014 8:40 pm -- JacobKlein 10 December 2015 2:54 am [NEW] The following items have been modified for this Bug: [NEW] Last comment from NVIDIA (12/12/2014 6:07 AM): |
Jacob Klein Send message Joined: 15 Apr 11 Posts: 149 Credit: 9,783,406 RAC: 9 |
and more... 5 November 2014 9:32 pm -- Kevin Kang 12 November 2014 11:28 am -- JacobKlein 14 November 2014 1:21 am -- Kevin Kang 5 December 2014 8:40 pm -- JacobKlein 10 December 2015 2:54 am [NEW] The following items have been modified for this Bug: [NEW] Last comment from NVIDIA (12/12/2014 6:07 AM): [NEW] 12 December 2014 6:11 am JacobKlein [NEW] 12 December 2014 6:22 am Kevin Kang [NEW] 12 December 2014 7:26 am JacobKlein |
Wedge009 Send message Joined: 3 Apr 99 Posts: 451 Credit: 431,396,357 RAC: 553 |
Wonderful news, thanks for your persistence. From what I understand, this means that driver revisions up to and including 340.x will allow pre-Fermi generation NV GPUs to correctly process the OpenCL applications, is that correct? Future revisions drop pre-Fermi support altogether, so this should avoid broken NV AP results in the future, right? Soli Deo Gloria |
Jacob Klein Send message Joined: 15 Apr 11 Posts: 149 Credit: 9,783,406 RAC: 9 |
Well... let's not jump to conclusions. What it means is: - R337 drivers were processing OpenCL correctly for pre-Fermi GPUs. - R340 drivers up to and including 341.21 were processing come OpenCL incorrectly for pre-Fermi GPUs. - The next R340 driver after 341.21 will correct some (maybe all? not sure.) of the OpenCL problems. - The solution may or may not fix the SETI AstroPulse problems that were identified - If the solution does fix the SETI AstroPulse problems, then the admins can change the scheduler and the validator to start sending/accepting results from R340 driver that is later than a certain version. |
Wedge009 Send message Joined: 3 Apr 99 Posts: 451 Credit: 431,396,357 RAC: 553 |
I see. Well, still, it is progress in the right direction, no? Soli Deo Gloria |
Jacob Klein Send message Joined: 15 Apr 11 Posts: 149 Credit: 9,783,406 RAC: 9 |
Oh hell yeah, definitely the right direction! People were worried NVIDIA wouldn't do a single thing. I spent several hours going through API testing to figure out a way to delicately show NVIDIA the problem, and now they claim to have fixed it. I have my fingers crossed that it fixes the AstroPulse issues. No guarantees on that, but I do have hope. |
RottenMutt Send message Joined: 15 Mar 01 Posts: 1011 Credit: 230,314,058 RAC: 0 |
Version 347.09 - BETA Release Date Wed Dec 17, 2014 Operating System Windows 7 64-bit Windows 8.1 64-bit Windows 8 64-bit Windows Vista 64-bit Language English (US) File Size 293.12 MB anyone try the beta |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Version 347.09 - BETA Won't help anyone in this thread. No new release for either GeForce or Quadro FX pre-Fermi models. |
Jacob Klein Send message Joined: 15 Apr 11 Posts: 149 Credit: 9,783,406 RAC: 9 |
To clarify, the driver version 347.09 is an R346 (Release 346) driver. It is applicable to GeForce GPUs that are Fermi or later. The problem in this thread deals with pre-Fermi GPUs and some/all Quadro series GPUs, which NVIDIA has stopped developing new-feature-drivers for, meaning there will never be an R343 or R346 driver. However, NVIDIA has pledged to continue to support pre-Fermi devices by issuing bug-fixes to the R340 (Release 340) drivers. The current R340 driver for my Quadro FX3800M GPU, is 341.21, dated 12/5/2014. And it does not solve the OpenCL problems. NVIDIA says that the next R340 release should have the OpenCL fixes to make at least the OpenCL SDK examples work correctly. Happy holidays! Jacob PS: I've had no problems with the new 347.09 driver on my Kepler GPUs. BOINC reports it as Cuda 7.0, and GPUGrid works great with them. |
Greg Tippitt Send message Joined: 19 Apr 04 Posts: 24 Credit: 20,455,837 RAC: 39 |
TBar, When you say driver version 340.xx do you mean only 340.52 on Windows or does this apply to 340.32 on Linux as well? I have Telsa M1060 GPU cards on several Ubuntu Linux systems. I got the systems running just before the SETI work unit shortage, so I aborted all the SETI tasks in my work queues so others could have them, since I run work for several projects. I've been running Einstein and GPUGrid task on my GPUs and have just started them working on SETI again today. These systems each have 24 CPU cores which have started running SETI work again as well. I have gotten a couple of SETI BETA AP work units for CUDA, but have not gotten any production CUDA tasks yet. Should I only run only CPU tasks for SETI or will my GPUs work correctly? When you make this type of "Chicken Little - The sky is falling" statement in huge fonts, it would be helpful if you were a bit more specific where the sky is falling. Greg That's probably still too vague for most people. Let's see, how about; |
Wedge009 Send message Joined: 3 Apr 99 Posts: 451 Credit: 431,396,357 RAC: 553 |
This is a problem at the driver level - it is universal, not operating system specific. ie Yes, this warning applies to Linux as well as Windows systems. Your M1060 GPUs are pre-Fermi generation and so they will be affected by the OpenCL bug in the 340+ drivers. I believe you should be able to run MultiBeam tasks on them, just not AstroPulse tasks. At least, not without producing erroneous results. Also, I'm quite sure there are no CUDA applications for AstroPulse, only MultiBeam. The plan class may have CUDA in the name but I believe they still run the OpenCL programs. Soli Deo Gloria |
Wiggo Send message Joined: 24 Jan 00 Posts: 34748 Credit: 261,360,520 RAC: 489 |
This is a problem at the driver level - it is universal, not operating system specific. ie Yes, this warning applies to Linux as well as Windows systems. If you have any pre-Fermi GPU with any current 34x.xx drivers you will not get any GPU tasks and that includes Multibeam also, so you must revert to a pre-34x.xx driver to get work. ;-) Cheers. |
Wedge009 Send message Joined: 3 Apr 99 Posts: 451 Credit: 431,396,357 RAC: 553 |
Ah, so the server restriction is still in place (my oldest NV GPU in use is Fermi generation, so I haven't been keeping track). But it is still the case that MultiBeam applications are not affected by the bug, correct? Soli Deo Gloria |
Wiggo Send message Joined: 24 Jan 00 Posts: 34748 Credit: 261,360,520 RAC: 489 |
Ah, so the server restriction is still in place (my oldest NV GPU in use is Fermi generation, so I haven't been keeping track). But it is still the case that MultiBeam applications are not affected by the bug, correct? No it doesn't effect Cuda processing, only OpenCL processing, but the servers' restriction is a blanket job by "pre-Fermi GPU + driver version" only on whether you get any type of GPU work or not. Cheers. |
Jacob Klein Send message Joined: 15 Apr 11 Posts: 149 Credit: 9,783,406 RAC: 9 |
Hmm... When searching for my Quadro FX3800M drivers today on NVIDIA's website, it returned that R346 v347.09 was available. http://www.nvidia.com/download/driverResults.aspx/81137/en-us My GPU is even on the "Supported Products" listing, too. However, the Release Notes say: Quadro FX 3800M: Not supported I guess NVIDIA is doing a not-so-great job of filtering out applicable drivers when the user is trying to download them. Nevertheless, I will attempt installation of this driver over the next week, but I don't expect it to work. Still waiting on the next R340 release to hopefully fix those OpenCL woes... :) |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.