Message boards :
Number crunching :
Not getting work
Message board moderation
Author | Message |
---|---|
Send message Joined: 13 Sep 11 Posts: 17 Credit: 3,263,835 RAC: 0 |
Until recently I was crunching with this setup:
Nvidia GTX260 with driver 260.19.44, specifically selected for Milkyway because of the excessive CPU usage in later versions BOINC 6.12.34 Everything was running fine, but then I started to get MilkyWay@Home v1.00 jobs. Yes, I got those without any tricks, but they all crashed with what I think were OpenCL errors. So I decided to try a later GPU driver, first 275.43, now 290.10. But I don't get work any more. The log says Rejecting newer opencl_nvidia application due to older Nvidia drivers Right, BOINC doesn't seem to recognize the driver: NVIDIA GPU 0: GeForce GTX 260 (driver version unknown, CUDA version 4010, compute capability 1.3, 895MB, 560 GFLOPS peak) And sched_request_milkyway.cs.rpi.edu_milkyway.xml contains this line in the coproc_cuda section: <drvVersion>0</drvVersion> So how do I get GPU work from Milkyway again? If you'd like to make any suggestions, please keep this in mind:
I don't do babysitting (app_info.xml) I can't afford to burn a full CPU core just to keep the GPU busy so I'd like to revert to the 260.19.44 driver Perhaps you could drop the version check? Oh, and Nvidia's recommended Linux driver is still a v275. You shouldn't require more than that if you really need a minimum version, but from the announcement I got the impression that the old drivers should still work. |
Send message Joined: 8 May 10 Posts: 576 Credit: 15,979,383 RAC: 0 |
I can't afford to burn a full CPU core just to keep the GPU busy so I'd like to revert to the 260.19.44 driverThe new version has a workaround for it. By default it isn't particularly aggressive about trying to reduce it, but for me it keeps around 50%. Right, BOINC doesn't seem to recognize the driver:I added the fallback version check against the CUDA version which is still reported. Perhaps you could drop the version check?A bug showed up in the older drivers. I'm not sure which ones but I knew that 280.xx+ was OK. I'll loosen the version restrictions as I know more about which versions are bad. 1.02 possibly avoids the issue but I'm not sure yet. |
Send message Joined: 8 May 10 Posts: 576 Credit: 15,979,383 RAC: 0 |
It looks like my workaround did work on a variety of drivers so I dropped the limit back to what it was before. |
Send message Joined: 13 Sep 11 Posts: 17 Credit: 3,263,835 RAC: 0 |
I can't afford to burn a full CPU core just to keep the GPU busy so I'd like to revert to the 260.19.44 driverThe new version has a workaround for it. By default it isn't particularly aggressive about trying to reduce it, but for me it keeps around 50%. Thanks Matt, I got a batch of 1.02 work units and right now I am watching the first ones run. The numbers look excellent. With the 290.10 driver CPU load is about 2%, just as good as the 0.90 application with the 260 driver. So there's no need to go back to that. I'll try Nvidia's stable 275 driver though, no doubt that will work, too. |
Send message Joined: 13 Sep 11 Posts: 17 Credit: 3,263,835 RAC: 0 |
I'll try Nvidia's stable 275 driver though, no doubt that will work, too. Well, it does work, but with 40% load. Back to 290 then. |
©2024 Astroinformatics Group