Questions and Answers :
GPU applications :
When will Kepler be supported?
Message board moderation
Author | Message |
---|---|
TheInternal Send message Joined: 3 Sep 06 Posts: 4 Credit: 29,145,970 RAC: 0 |
Running Windows 8 Pro 64-bit, Core i5 at 4.4GHz, and two Geforce 670 GTX cards. I'd like to lend my spare cycles to BOINC (SETI@home and world community grid in particular), but kepler still isn't supported. It's really frustrating, having been BOINCing for years, to not be able to easily boinc now that I have access to a faster system. I am greatly concerned that by having a whole series of popular graphics cards not work with SETI@home, that you'll risk turning off a lot of potential volunteers / alienate a number of existing ones. I sincerely hope a fix is in the works to allow individuals to easily contribute once again. Some questions regarding the FAQ: "Solution/workround: a) Use an optimised Cuda application, where available. b) Downgrade to the 301.42 driver - only possible on GTX 670/680/690 cards, not on newer releases like the 650/660 or their Ti variants. c) Set an environment variable, as shown below." a) what the hell is an optimised Cuda application? b) Um, no. I use my computer for games regularly, so this is not an option. Is this part an absolute must? c) Confusing... step b said use 301.42 driver... step c wants us to use 306 driver? I figured out how to do this in Windows 8, but the FAQ is rather lacking in a few of the steps for the more novice computer users who would like to contribute. creating the environment variable doesn't seem to fix the problem. No matter what I try, SETI keeps erroring out. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
a) what the hell is an optimised Cuda application? The options are Either, Or, Or, not Option, And, And. So for a), the Lunatics offer optimized applications, for CPU and GPU. But not so much for Windows for the time being, as they have a copyright issue with using one of the Intel compilers. Which means that this is no option for you for the time being. Which then moves on to option b), use a driver lower than the first one having the problem. In you case this can be the 301.42 driver at http://www.nvidia.com/object/win7-winvista-64bit-301.42-whql-driver.html. But you claim you can't do that as it interferes with your gaming. Tried the older drivers yet? Which leaves us with c), you wanting to use drivers 306 or higher, then you'll have to fill in the environment variable. Which in Windows 8 goes like this: http://www.technoon.com/how-to-add-environment-variables-in-windows-8.html All you have to do is add the variable named "CUDA_GRID_SIZE_COMPAT" and give it the value "1". |
Jorge Alberto Ramos Oliveira Send message Joined: 10 Sep 01 Posts: 5 Credit: 1,765,875 RAC: 0 |
My case. I tried creating the environment variable but still had errors. That was 15 days or so and don't remember when did they occur. I only remember that without the environmetn variable, fermi tasks ended after 11 seconds of crunching. The new variable solved this issue but either there where errors at the final stages of crunching or the validations where always inconclusive (or something like that. Sorry but cant give more info on the subject because I no longer have acces to my failed tasks on my profile). I have decided to stop work for SETI now because of this (currently crunching astropulse only, but my client only gets about 4 tasks per day, maybe 2 hours of activity each day) and give this resource to other projects. Will return for SETI work when this is fixed. cheers! |
©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.