Is the problem whit GTX 260, OK now?? And if that the case, what drivers and boinc version is recomanded??

Please have it as an option not as default. Not all is affected by this bug.
____________

Please have it as an option not as default. Not all is affected by this bug.

Yes, I would also prefer that my working gtx260 gets the "normal" work. You could just add an option to the preferences that says: "if your gtx260 doesn't work, check this!"

Like you can check/uncheck astropulse or gpuwork at seti.

I really would want to have such an option available!!

Yes, I would also prefer that my working gtx260 gets the "normal" work. You could just add an option to the preferences that says: "if your gtx260 doesn't work, check this!"

Like you can check/uncheck astropulse or gpuwork at seti.

I really would want to have such an option available!!

It would not matter if you GTX260 works, then it will also work with the second application. It is just more work for us, that we need to maintain two queues.

Clearly only some workunits can run there, but at least we move on without waiting.

We are implementing a workaround, which is quite drastic. We will make an application just for 260 which does not use PME. Clearly only some workunits can run there, but at least we move on without waiting.
When in place, it will be advertised from the news.

gdf

I keep seeing references to this problem, but have never seen is on my own MSI 260. There's other people I know that are also running MSI without a problem. So does this bug only affect certain brands? Is it a problem with EVGA or are other brands affected?

We are implementing a workaround, which is quite drastic. We will make an application just for 260 which does not use PME. Clearly only some workunits can run there, but at least we move on without waiting.
When in place, it will be advertised from the news.

gdf

I have 2 EVGA GTX 260 216 that are 55nm and run flawless.
I had 1 EVGA GTX 260 192 65nm that would not, RMA'd.
The 1 EVGA GTX 260 192 65 that I got from RMA also does not run without error.

Is it the older 260's with problems? My newer ones are great.

This could happens, I have similar experience. Was trying several times to add 4th card to perfect working trinity of ASUS GTX 260's (216C, 55 nm). 4th card was reference Nvidia (192's , 65nm).
Windows was seeing it, GPU-Z was seeing it (4th card added). Starting GPUGRID resulting of immediate crash with BSOD, with routines of memory dumps & system restart. System records say's that the reason was graphic driver. Pulling out old style reference card from the system & restarting it returns it to the normal functionality. Thinking, that the problem is flying somewhere around old 192's Core reference design card.
____________

I have a GTX260/216 (55nm) (MSI) that runs GPUGrid with no problems and a GTX260/216 (65nm)(EVGA) that will not run either GPUGrid or Collative without an error. Both run 190.38 drivers.

6 BFG 260 216 and 2 EVGA 260 216 without any issues.

____________

Looks like most 260 216s mentioned in this thread work, but not the 192s.

Does anyone have a 260 192 that works on GPUGrid?

Has anyone had success running a 192 core 260 on Linux? Mine were on Vista64, thinking about trying Linux.

Looks like most 260 216s mentioned in this thread work, but not the 192s.

Does anyone have a 260 192 that works on GPUGrid?

I have 2x BFG GTX260-216, both running linux

1 works, 1 fails

I have a 260 216 and it does not work under vistea 64 and win7 64. So I changed as many others to collatz.

I have a ASUS GTX 260 216sp and it does not work under win7 64. So I changed as many others to collatz.

Can we get a refound for a broken card or what?

Please tell us GDF?

Please tell us NVIDIA or ASUS?

I have got an ASUS GTX 260/216 Top (factory OC) 65nm, worked fine using 182.06 drivers. After upgrading to 185.xx, 186.xx, 190.xx and 191.xx drivers doesn't work with GPUgrid. Crunching Seti CUDA VLARkillv12, Collatz, MW and Folding works fine.
Win XP x_64.

I have a 260 216 and it does not work under vistea 64 and win7 64. So I changed as many others to collatz.

What brand is the card, possibly EVGA?

We are implementing a workaround, which is quite drastic. We will make an application just for 260 which does not use PME. Clearly only some workunits can run there, but at least we move on without waiting.
When in place, it will be advertised from the news.

gdf

i WAS getting errors with my GTX260 until i STOPPED overclocking my CPU
since then no errors at all!

Our experience with gainward was very bad. The one we tried had a different dissipation system which were working very poorly with temperatures above of 100 degrees. These were GTX275.

With temperatures up to 92 degrees on other cards we had no problems.

For the 260, we have not done anything yet as there are people which can run on it.

gdf

Waiting as yet!

Is there any progress? :-)
____________
From Siberia with love!

Seems that volunteer's questions are remaining without response here... It's OK, we are still waiting...
____________
From Siberia with love!

Still waiting too........

I sold my problem GTX 260 192 core 65nm. Kept the 2 55nm that do fine. The older 65nm cards are a problem for all but games. When new cards come out, like Fermi, and are available the prices will drop so the GTX 260 will be worth less. So sell while it is still worth a decent price.

Well, I have tried to run a couple WUS without overclocking, without using PC at all and with speedup videocard's fan from 90 to 100% (note, that usually it rotates at 40% of maximum speed), so as with maximum air flow through my PC's case (3R Systems Air 400, Hiper PS). But there was always the same famous fft-error.

By the way, now I am trying to see the destiny of another 2 WUs (downloaded because I have upgraded my videodriver a couple days ago (190.42, Linux x64)). In "NVidia X Server Settings" it shows that GPU is on 80-81 C, will see what happen...
____________
From Siberia with love!

There are still errors...
____________
From Siberia with love!

Would it be reasonable to ask the BOINC developers to add code to report more details about what specific type of chip the GPU board uses, in order to help gather more information about which GTX260 boards work with GPUGRID? Or would it be more reasonable to add such code to your application instead, so that even most failed workunits would be able to send back such information?

Also, since the GTX260 boards work better with the CUDA 2.1 drivers, would it be reasonable to try a GTX260-specific version of the application that was compiled using the CUDA 2.1 SDK, but without many other changes? If such a version works well, you could even make the same application available for some of any other Nvidia boards that work well with CUDA 2.1 drivers, but not with the more recent drivers.

An idea to consider to eliminate some of the separate queues: Put more than one version of the application code into each workunit, along with a program that does little more than select which of the application versions to use.

I still got 80 percent errors on my 260s. Maybe the developers should have a quiet talk with the guys from collatz? After wasting some time here i am again back to collatz. Will check again in 30 days.

regards

It would not matter if you GTX260 works, then it will also work with the second application. It is just more work for us, that we need to maintain two queues.

gdf

Does new 6.15 beta application for Linux solve the bug?
____________
From Siberia with love!

Any progress on the GTX 260 issue? Resolved? Still working on it? Not going to be fixed?

Nvidia told us that the problem is solved with CUDA3, but we did not check it.

gdf

Sorry, short test 3.0 tasks you have sent to GTX260 a weeks ago are deleted. I haven´t noticed it. Thanks for explaining of using 3.0 for Fermi cards only.

so is this problem fixed yet? i have two gtx260's, one is working fine, the other one is a 65nm core216 and doesn't work. please let me know if there's hope in holding on to this card for a future fix, or if i should just sell this card because there won't be any plans to problem.

The reason is that Fermi require 3.0 tasks, while for other cards the code compiled with 3.0 is slower.
I can change the server to deliver also to GTX260.

gdf[/quote]

Yes please, better a bit too slow than nothing at all.

kind regards

Alain

The reason is that Fermi require 3.0 tasks, while for other cards the code compiled with 3.0 is slower.
I can change the server to deliver also to GTX260.

gdf

so are these updated to accept fermi WU's yet?

I am Ubuntu 32 bit with 260-216--does it not run on 32 bit??

gpugrid is 64 bit only on Linux. Time to upgrade anyways. 64 bit is where its at.

The reason is that Fermi require 3.0 tasks, while for other cards the code compiled with 3.0 is slower.
I can change the server to deliver also to GTX260.
gdf

I would like to buy the new gtx460 to use on gpugrid.. will it work?


does anyone have the gtx460 card working without errors on gpugrid?

i have a gtx260 that always failed the tasks..
1. i've installed the newest nvidia driver
2. installed cuda 3.1
3. installed the newest Boinc manager

it still gives errors and doesn't complete the task
suggestions?

You are using Windows 7 Ultimate x64. I found that almost all tasks failed on my GTX260 when I used it with Windows 7 x64, so I installed Win XP x86 and now almost all tasks complete successfully. I also ran FatPuppy Linux on the card for abou 10days, and again virtually all tasks completed.

Is the project working along to solve this??

6.11 tasks (CUDA 3.1) errored out on GTX 260 65nm - rev. A. Win XP x_64, driver 2650.99

Is there a way to update the firmware? My limping GTX260 is unusable here and I'm willing to try everything to get it working here.

Here are the GPU-Z shots of both cards:

65nm:

55nm:

Thanks for the video. I will give it a shot sometime soon.