Woke up this morning to find that the machine with the 260 card had errored out 3 WU..First at 6.5 hours and the other two in one -2 minutes..
The machine with the 9600 card is doing ok but showing almost 20 hours total to complete a WU..

Woke up this morning to find that the machine with the 260 card had errored out 3 WU..First at 6.5 hours and the other two in one -2 minutes..
The machine with the 9600 card is doing ok but showing almost 20 hours total to complete a WU..

You are running the beta app aren't you? The "stock" app (acemd 6.64) we know doesn't work with later drivers.

---

BOINC blog

Woke up this morning to find that the machine with the 260 card had errored out 3 WU..First at 6.5 hours and the other two in one -2 minutes..
The machine with the 9600 card is doing ok but showing almost 20 hours total to complete a WU..

You are running the beta app aren't you? The "stock" app (acemd 6.64) we know doesn't work with later drivers.

Duh, uh no.. I'm running the "stock" app..
Ok, what driver should I be using with XP Pro 64 and a EVGA 260GTX?
Sign me,
Dave the clueless n00b..:)

Woke up this morning to find that the machine with the 260 card had errored out 3 WU..First at 6.5 hours and the other two in one -2 minutes..
The machine with the 9600 card is doing ok but showing almost 20 hours total to complete a WU..

You are running the beta app aren't you? The "stock" app (acemd 6.64) we know doesn't work with later drivers.

I've been helping Movieman on another forum. He's running 6.6.36 and 186.18. Things seem to be working ok now, so it's wait-n-see atm. Hopefully everything will continue ticking away....

Hi Guys,

Looking for some advice re good Boinc/Driver combinations.

My current system is Win XP64, Boinc 6.6.28 and 186.18 drivers on an i7 with 3 GTX295's

The system runs one instance of GPUGRID (6.64) fine but subsequent units fail with a computation error almost straight away when they run on the other GPU's. All the GPU's are recognised by Boinc and work fine on Seti so I am a bit stumped with this problem.

Cheers, Simon.

Hi Guys,

Looking for some advice re good Boinc/Driver combinations.

My current system is Win XP64, Boinc 6.6.28 and 186.18 drivers on an i7 with 3 GTX295's

The system runs one instance of GPUGRID (6.64) fine but subsequent units fail with a computation error almost straight away when they run on the other GPU's. All the GPU's are recognised by Boinc and work fine on Seti so I am a bit stumped with this problem.

Cheers, Simon.

I don't have any experience with XP64 as I run the 32 bit version of XP on my rigs. I run the 182.50 drivers which seem to be stable with GPUgrid.

You might want to upgrade your BOINC client to 6.6.36 or 6.6.37 as they did a couple of cuda fixes (to release video ram) in later versions, which may be part of your issues. I have 6.6.37 running on all my machines.

As for Seti, yes it seems a more forgiving cuda app (it was ported by nvidia). It doesn't seem to care what version drivers you run. GPUgrid are more particular, hence the attempt to get to a cuda 2.2 app that runs with "current" drivers.

---

BOINC blog

I am having problems with GPUGRID with drivers 185.18.08 in Linux. Is there anyway I could contribute to getting this issue fixed? I have experience developing CUDA programs and cross platform compiling.

nvidia is on it now.


gdf

So it is a problem with the drivers? Is there any information about what is happening with the driver that is causing this problem? It could be useful to know as I am having problems with one of CUDA programs and it could be related.

Yes, the 185.X series does not work with GPUGrid. Revert to the 180.X series drivers until there's a fix.

Anyone tried the 190.X series yet? I'm going to try cranking out this last WU before I try it myself. Talking to the guys at forums.nvidia.com they said the 190.X initial release still had the bug, but I'll try it anyways just to see.

The frustrating part of all this is Nvidia initially kept blaming my configuration until someone else said they were having a problem. They never did get it through their thick skulls that the 180.X series work, and the 185.X series does not work regardless of the configuration. Only when I asked them what the results of THEIR OWN TESTING was did I get a responce that it was in fact a bug in the 185.X series, but they still blamed the GPUGrid programming as part of the problem.

Makes me long for and ATI card....Oh wait, not really......:-/

Mike D

---

It does not work for gpugrid because we are the only project on Linux.
Even substituting the application with a bogus cuda_malloc causes the problem.

They try to optimize resources, if it clear that there is a problem they will try to fix it. So, your posting on their forum is quite useful. Keep doing it.

Actually where you posted exactly? Let's write it here.:)

gdf

Here's the post on the Nvidia forms where they admit there's a problem.....from "Netllama" @ Nvidia Corp. I keep asking about progress, but so far, they just keep releasing more crap. Also, in the reply is my original bug reports I posted on NVNews boards. Go ahead, pile on and pester them, maybe it'll get done quicker....

185.X Series doesn't work with GPUGrid Thread

Mike Doerner

---

I didn't read this thread before I joined, so just went ahead and attached anyway. Had been running driver 185.85 so I could use the CUDA 2.2 DLLs (rt and fft) at SETI: no problems here at all.

Yesterday I upgraded to drivers 190.38, and CUDA 2.3 DLLs for SETI. Task 1006526 was run with the 190.38 drivers from start to finish.

Hosts are Windows XP SP3, 32-bit, with BOINC regularly upgraded to test new releases - I'm at v6.6.37 at the moment.

We had many reports of "driver errors" in the optimisation community at SETI - most of them were resolved when the hardware was returned under RMA. If the hardware and cooling are up to scratch, the new drivers work fine, even here.

Of course, that's not to say there aren't problems with the Linux drivers - but let's keep the two issues separate.

What happened on your Linux box? That been the issue.

Mike Doerner

---

Is the move to CUDA 2.2 going to work for Linux? The 185 and 190 series drivers do not work with GPUGrid on Linux. Are we just "out" until NVIDIA gets off their rear ends?

Mike D

---

You should install driver for CUDA2.1 as suggested in join page. Those work fine.
gdf

It seems that we were able to hack it. I have just upgraded a new Linux application. It's an incompatibility between the driver and the way boinc execute the application. Setting the PATH fixes it.

gdf

OK, here's an important update....I was able to get the 190.18 driver to start crunching successfully under openSUSE. Just not under any incarnation of the release openSUSE 11.1. I am now testing release 11.2 Milestone 4 from http://software.opensuse.org/developer. You will need to install the kernel packages listed on this openSUSE/NVIDIA page to get the 190.18 driver to sucessfully compile,however, I am now running the CUDA 2.3 version on openSUSE, so at least I won't be left behind after this weekend's swiutch.....;-).

Let me know if you have any other questions.

Mike Doerner

---

Is your success related to the new app?

MrS

---

Scanning for our furry friends since Jan 2002

No, I tried 190.18 on SUSE 11.1 before I decided to try Gentoo Linux. After that failed abysmally (yes, I'm a linux-lite person ;-) ), I tried Fedora 11, after I couldn't log into that installation as root, I downloaded openSUSE 11.2 Milestone 4 because I really didn't feel like reinstalling 11.1, which I knew was a problem, and then having to re-install KDE 4.2.4.

So far, my 9600 GSO is up to 14.573% and the task should be complete by tomorrow.

I would have really liked to try Fedora 11 a little more, but the restrictions through the GUI were killin' me.

Mike D

---