@letniPlease see my big post above, I'm talking about cuda with no X server. Are you sure you've set it up all correctly? Also make sure you use compatible nvidia drivers and cuda libraries.Also see my post http://lunatics.kwsn.net/linux/seti-mb-cuda-for-linux.msg19014.html#msg19014 and follow it to the letter.Your card with 256 MB is borderline. You might get some out of memory messages here and there.
2. I have modified my app_info.xml to allow both AK_V8_SSE3 (32bit) and the cuda to run simultaneously (included .xml file).. I have 3 active tasks being worked on, two (for my dual CPU) say setiathome_enhanced 6.03 and run just fine. The third is the CUDA which setiathome_enhanced 6.08 (cuda), and the status NEVER goes past Ready to start. It will eventuall error out with Computation error.Anyone have any thoughts or advice on how to debug this?
Quote from: Kunin on 02 Aug 2009, 07:52:03 amThanks, but before I use it how does the VLAR kill work? I rebrand all of my VLAR to the CPU as soon as I can, and prefer to work whatever units I get since I have the 8 cores just sitting there most of the time.Well if you miss a VLAR from the rebranding and it gets to your GPU, it will get aborted almost instantly by the client.
Thanks, but before I use it how does the VLAR kill work? I rebrand all of my VLAR to the CPU as soon as I can, and prefer to work whatever units I get since I have the 8 cores just sitting there most of the time.
That was the issue the whole time.. I guess I figured just cause I am not uxing XWINDOWs on a headless machine that I technically wasn't using the video card. Enabling that let it do its thing Thanks everyone for all your help.letni
Ok, so it kills it as soon as it actually starts processing and no sooner?
Quote from: letni on 02 Aug 2009, 08:17:26 pmThat was the issue the whole time.. I guess I figured just cause I am not uxing XWINDOWs on a headless machine that I technically wasn't using the video card. Enabling that let it do its thing Thanks everyone for all your help.letniletni the hosts that you've posted above are full of errors. Are you sure you've solved all your problems?
latni can you give us a link of a wu done by the gpu?I'm suspecting that you get an out of memory error and the wu is then done in cpu, that's why you get 100% cpu utilization by the cuda app.
That is absoutly the case.. my first WU was finally finished by "GPU" and the error messages say MALLOC out of memory errors.. Looks like time for a better video card!
Quote from: letni on 03 Aug 2009, 08:55:31 amThat is absoutly the case.. my first WU was finally finished by "GPU" and the error messages say MALLOC out of memory errors.. Looks like time for a better video card!letni, what cuda app do you use? The 2.2 one or the one from the first post of this thread? The 2.2 one is very memory hungry. Try using the one from the first post of this thread and see if it helps. Mind you that it has a different name so you'll have to edit your app_info.xml accordingly.
That did the trick.. No 100% CPU usage anymore with the older binary.. Chugging away very fast now!! Hopefully no more computation errors!
if i were to build a machine with 4 GTX295 cards, will boinc see and use all 8 cuda processors properly and efficiently, or would i be better off using 4 GTX285 single gpu cards?
And if it doesn't work you can send that machine to me...
Quote from: pp on 04 Aug 2009, 11:43:48 amAnd if it doesn't work you can send that machine to me... Well, probably, first, he's going to bring that machine down on my head hard for making him blow his money away, but I'll take it anyway.