Forum > Linux
SETI MB CUDA for Linux
riofl:
--- Quote from: sunu on 02 Aug 2009, 06:19:55 pm ---@letni
Please 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.
--- End quote ---
i got them all the time with my 8600GT 256mb. cuda tried to use it when it was the only device but it turned every wu in with out of memory errors. that was when i added the tesla and then later replaced the gt with the gtx i now have.
for someone who uses a linux desktop seriously, i doubt 256mb vidram will work at all unless maybe you define only 1 or 2 desktops at most and keep all the bells and whistles disabled along with using a solid color background.., or it is a 2nd card not used for video at all then it can be used properly.
letni:
--- Quote from: letni on 31 Jul 2009, 01:14:06 pm ---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?
--- End quote ---
There is an option that is on by default to not run cuda tasks when pc is in use. Check global_prefs.xml for <run_gpu_if_user_active>0</run_gpu_if_user_active> and change that 0 to 1.
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
Kunin:
--- Quote from: sunu on 02 Aug 2009, 08:08:12 am ---
--- Quote from: Kunin on 02 Aug 2009, 07:52:03 am ---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.
--- End quote ---
Well if you miss a VLAR from the rebranding and it gets to your GPU, it will get aborted almost instantly by the client.
--- End quote ---
Ok, so it kills it as soon as it actually starts processing and no sooner?
sunu:
--- Quote from: letni on 02 Aug 2009, 08:17:26 pm ---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
--- End quote ---
letni the hosts that you've posted above are full of errors. Are you sure you've solved all your problems?
--- Quote from: Kunin on 02 Aug 2009, 08:19:47 pm ---Ok, so it kills it as soon as it actually starts processing and no sooner?
--- End quote ---
Yes. When it starts to crunch a wu, it checks if this wu is a VLAR and if it is, it aborts.
letni:
--- Quote from: sunu on 02 Aug 2009, 09:35:20 pm ---
--- Quote from: letni on 02 Aug 2009, 08:17:26 pm ---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
--- End quote ---
letni the hosts that you've posted above are full of errors. Are you sure you've solved all your problems?
--- End quote ---
I have the client running currently.. 2 threads on AK_V8_64bit_SSE3 (Pentium D) and one thread on cuda novlar 2.2 build.. The CUDA is extremly slow and I have noticed that the cuda thread is taking up 100% of one (out of 2) of my CPUs, slowing down my SSE3 CPU threads.. Here are the versions:
Nvidia Driver: 185.18.31
CUDA Toolkit: 2.2 (ldd reports proper libs - added to ld.so.conf) -also copied libs to project.. directory
SETI Version: 6.6.36
Environment: FC10_64bit - Runlevel 3 - no xwindows
Video Card - 8600 GTS 256MB
I have copied the CUDA binary to a system directory in the path as mentioned.
I even tried the new 190 driver and the 2.3 toolkit and same effect, just downgraded back to 2.2 toolkit and 185 driver.. Still same issue.. 100% cpu utilization.. This can't be efficient.. Any suggestions?
[attachment deleted by admin]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version