Would the updated application solve the problem regarding on the 65nm GTC260s?

Even the current cuda3.1 one should. Please test.

gdf

I also picked up 6.11 tasks on both of my GTX 260 cards with 258.96 drivers.

The 6.11 app so far is running about the same speed on the GTX 260, but all 3 of my GT 240 cards have slowed down about 60%. GPU usage is still above 90% but the WUs are running so slow that it's not worth keeping them on the project with the 6.11 app. Can we PLEASE go back to 6.05?

I hope GPUGRID will have also in future a CUDA V2.2 app for Windows.
I need to stay at nVIDIA driver 190.38, the fastest driver for/on my systems.


(I tested with app_info.xml file, CUDA V2.3 .dll's the GPUGRID CUDA V2.2 app.
It's look like it was little bit slower then (but wasn't a real bench-WU test). But maybe because of the app wasn't compiled with CUDA V2.3 ..)


But I have from time to time probs:
Number crunching : No progress change during calculation?

Where is the prob?

This are manufacturer OCed GTX260-216 55nm graphic cards. 4x EVGA SSC.
To now the other one, a GIGABYTE SOC (also GTX260-216 55nm) had no probs. But maybe because of too less WUs crunched.

I read now here, the old 65nm card have probs? Which kind of?

---

I also picked up 6.11 tasks on both of my GTX 260 cards with 258.96 drivers.

The 6.11 app so far is running about the same speed on the GTX 260, but all 3 of my GT 240 cards have slowed down about 60%. GPU usage is still above 90% but the WUs are running so slow that it's not worth keeping them on the project with the 6.11 app. Can we PLEASE go back to 6.05?

Yes, move back to a CUDA2.2 driver.

gdf

Yes, there will be a CUDA2.2 app for Windows. In fact, there is already one as long as you have a cuda2.2 driver.

gdf

I hope GPUGRID will have also in future a CUDA V2.2 app for Windows.
I need to stay at nVIDIA driver 190.38, the fastest driver for/on my systems.


(I tested with app_info.xml file, CUDA V2.3 .dll's the GPUGRID CUDA V2.2 app.
It's look like it was little bit slower then (but wasn't a real bench-WU test). But maybe because of the app wasn't compiled with CUDA V2.3 ..)


But I have from time to time probs:
Number crunching : No progress change during calculation?

Where is the prob?

This are manufacturer OCed GTX260-216 55nm graphic cards. 4x EVGA SSC.
To now the other one, a GIGABYTE SOC (also GTX260-216 55nm) had no probs. But maybe because of too less WUs crunched.

I read now here, the old 65nm card have probs? Which kind of?

I also picked up 6.11 tasks on both of my GTX 260 cards with 258.96 drivers.

The 6.11 app so far is running about the same speed on the GTX 260, but all 3 of my GT 240 cards have slowed down about 60%. GPU usage is still above 90% but the WUs are running so slow that it's not worth keeping them on the project with the 6.11 app. Can we PLEASE go back to 6.05?

Yes, move back to a CUDA2.2 driver.

gdf

You mean I have to downgrade the video drivers to go back to 6.05? Arg. What version do I have to downgrade to in order to avoid 6.11?

You can choose any driver before cuda3. Look at the suggested driver here.
http://developer.nvidia.com/object/cuda_archive.html

190 would be fine.

gdf

Would the updated application solve the problem regarding on the 65nm GTC260s?

Even the current cuda3.1 one should. Please test.

gdf

I don't really understand this, please clarify. If I want to test it, do I just check the "Run test applications" box on the preferences?

lkiller123, if you have a GTX260-192 you could test it with the CUDA 3.1 application on XP using the 258.96 driver, still available from NVidia (achieved drivers).

I actually have the 65nm of the GTX260-216. I have been trying to get them to work for two months already. I will try to test it again ASAP.

To run the CUDA 2.2 app on Windows you need a driver between 185.85 and 197.57 (inclusive).

To run the CUDA 3.1 app drivers from 257.21 through to 258.96 are required.

To run the CUDA 3.2 app (not presently in use, but soon to be tested) only the 260.89 or 260.99 drivers can be used.

http://www.nvidia.com/Download/Find.aspx

I have Win7 64bit, does it make any difference?

To run the CUDA 2.2 app on Windows you need a driver between 185.85 and 197.57 (inclusive).

To run the CUDA 3.1 app drivers from 257.21 through to 258.96 are required.

To run the CUDA 3.2 app (not presently in use, but soon to be tested) only the 260.89 or 260.99 drivers can be used.

http://www.nvidia.com/Download/Find.aspx

I see your GT 240 cards are also performing horribly with 6.11. Things here were running so well lately, I was wondering when the other shoe would drop. To make matters worse the GT 240 cards under 6.11 are so slow that they also miss the 1 day bonus. What reason was there to make this change? Are you rolling back to earlier drivers?

Use the Win7 64bit driver version. There are some differences between W7 and XP drivers but the app would really be what you are testing rather than the driver.

I'm still testing 260.99 but it's a messy picture, at least for the GT240's.

It seems to work on the Win7 x64 system and on one of two Vista systems, however on the Vista x64 system I have with 4 GPU's three of the cards are running at the correct speed, but one card is much slower, 405MHz rather than 579MHz and worse, the shaders on that card seem to be synced to the core at 810Mhz. The strange thing is that the card that dropped in frequency is identical to two other cards that did not drop in frequency.
I might try to install EVGA precision again but after I try a restart; I was able to change power management to maximum power, but it made no immediate impact.

It also looks like the 3.1 performance may not be as good as with 2.2 app for the 200series, but it will take a few more tasks to come in before I can be sure of that, and only for GT240’s.

For now I will leave the 260.99 on but if it's not as fast I may have go back to 197.57 - cant remember if I need dummy plugs for that one or not, but I have a spare omnicube.

In my view, after seen as Nvidia works, once a new architecture is out they don't care anymore about the older one. This happened for the g80 when the g200 came out, and to the g200 now that the fermi are out. The best driver is the one just before the change in GPU core: For g200 is the cuda2.2/2.3, and for fermi usually the latest.

That's why we give two applications out. We would like to support at least two generations, the G200 and Fermi now.

gdf

This is why I don’t think that the latest app and driver will fix the bug for the 60nm GTX260-192; they don't make a GTX260-192 any more.

After changing the power management to maximum power, I restarted the quad GT240 system and the card is now at the desired frequency (579MHz core and 1600MHz shaders). It has stayed at that for 2h 25min, so it looks good.

This GTX295 on XP x86 seems to be doing well with the 260.99 drivers; task completion times are the same for 3.1 as for 2.2, so the frequency can't be dropping off.

On my system wuid=2028574 ended in calculation error.
But on an old GTX260-192 it was fine.

If I look to the tasks overview of hostid=62699, I guess he found the trick.. ;-) (Win7 64bit, nVIDIA driver 260.63)
6.05 and 6.11 app, all WUs fine.

---

A bit sad to announce that 6.11 is still not working for the 65nm GTX260-216, it works, however, on the 55nm version.

Driver is 258.96
WUs that errored:
http://www.gpugrid.net/result.php?resultid=3220894
http://www.gpugrid.net/result.php?resultid=3220882

There is another 55nm 260-216 running in the same rig which works fine.

Am I doing something wrong here?

I don't see any differences in performance of my 9800GT between CUDA2.2 and CUDA3.1. KASHIF tasks are going well with new app, thanks.

---

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"