[DismorphiC]

So I've been happily folding away on my Gentoo box with my OCForums contest-winner GTX 260 (Thank you, by the way!!) when I got this new message (not sure if it has to do with my recent updated NVIDIA drivers or not...).

Anybody have any experience with this? It's running the stock timings, and it's been working fine for weeks prior.

Code:

[22:09:57] - Preparing to get new work unit...

[22:09:57] + Attempting to get work packet

[22:09:57] - Connecting to assignment server

[22:09:57] - Successful: assigned to (171.64.65.106).

[22:09:57] + News From Folding@Home: Welcome to Folding@Home

[22:09:57] Loaded queue successfully.

[22:09:58] + Closed connections

[22:10:03] 

[22:10:03] + Processing work unit

[22:10:03] Core required: FahCore_11.exe

[22:10:03] Core found.

[22:10:03] Working on queue slot 04 [August 31 22:10:03 UTC]

[22:10:03] + Working ...

[22:10:03] 

[22:10:03] *------------------------------*

[22:10:03] Folding@Home GPU Core - Beta

[22:10:03] Version 1.19 (Mon Nov 3 09:34:13 PST 2008)

[22:10:03] 

[22:10:03] Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86 

[22:10:03] Build host: amoeba

[22:10:03] Board Type: Nvidia

[22:10:03] Core      : 

[22:10:03] Preparing to commence simulation

[22:10:03] - Assembly optimizations manually forced on.

[22:10:03] - Not checking prior termination.

[22:10:03] - Expanded 67314 -> 350744 (decompressed 521.0 percent)

[22:10:03] Called DecompressByteArray: compressed_data_size=67314 data_size=350744, decompressed_data_size=350744 diff=0

[22:10:03] - Digital signature verified

[22:10:03] 

[22:10:03] Project: 5789 (Run 19, Clone 11, Gen 1)

[22:10:03] 

[22:10:03] Assembly optimizations on if available.

[22:10:03] Entering M.D.

[22:10:09] Run: exception thrown during GuardedRun

[22:10:09] Run: exception thrown in GuardedRun -- Gromacs cannot continue further.

[22:10:09] Going to send back what have done -- stepsTotalG=0

[22:10:09] Work fraction=0.0000 steps=0.

[22:10:14] logfile size=4993 infoLength=4993 edr=0 trr=23

[22:10:14] - Writing 5529 bytes of core data to disk...

[22:10:14] Done: 5017 -> 1890 (compressed to 37.6 percent)

[22:10:14]   ... Done.

[22:10:14] 

[22:10:14] Folding@home Core Shutdown: UNSTABLE_MACHINE

[Zerix01]

Yes I'm still on drivers 180.44 (I think 180.56 is fine though). Every time I update to the 185's or 190's I get the same error. Downgrade and it works fine again. Make sure your running the latest CUDA toolkit but if that does not fix anything then your will need to downgrade your driver.

Let me know if the newer toolkit helps.

I think Shelnutt and I will need to figure out a solution to this, maybe Nvidia changed something in CUDA and now the wrapper is no longer CUDA compliant.

[GeneralMac]

Originally Posted by Zerix01

Yes I'm still on drivers 180.44 (I think 180.56 is fine though). Every time I update to the 185's or 190's I get the same error. Downgrade and it works fine again. Make sure your running the latest CUDA toolkit but if that does not fix anything then your will need to downgrade your driver.

Let me know if the newer toolkit helps.

I think Shelnutt and I will need to figure out a solution to this, maybe Nvidia changed something in CUDA and now the wrapper is no longer CUDA compliant.

+1 Zerix01
deffinately use 180 drivers Im using 180.56

[DismorphiC]

Newer cuda toolkit installed.
180.60 installed. Still same problem.

BAH!

[Shelnutt2]

It seems the big change was with the first 185 driver they added support for cuda 2.2. It's a known issue for the 185 and 190 series. I just checked the folding forums, and apparently even on xp/vista/win 7 they don't want you using 185 or newer drivers yet because of some errors that cause incomplete workunits to be sent in as if they are finished,

[Zerix01]

Originally Posted by DismorphiC

Newer cuda toolkit installed.
180.60 installed. Still same problem.

BAH!

Odd, I'm definitely on a 2.2 cuda toolkit with my older drivers. Did you download the 32 bit toolkit or the 64? You need the 32 bit version regardless of the driver being used.

I looked at the change log for 180.60 and I don't see anything about cuda mentioned so I don't think they added any 2.2 support.

I see they have a 2.3 toolkit now. Let me know how this works out for you, if needed I'll get permission to put the 2.2 toolkit up on the GPU2 wiki server, the file is 27 MB's and I don't know if this will cause bandwidth problems if too many people suddenly need it.

It seems the big change was with the first 185 driver they added support for cuda 2.2. It's a known issue for the 185 and 190 series. I just checked the folding forums, and apparently even on xp/vista/win 7 they don't want you using 185 or newer drivers yet because of some errors that cause incomplete workunits to be sent in as if they are finished,

As much as that sucks, that is also a good to here on our side. At least it isn't an isolated issue with us.

[Zerix01]

Originally Posted by Shelnutt2

It seems the big change was with the first 185 driver they added support for cuda 2.2. It's a known issue for the 185 and 190 series. I just checked the folding forums, and apparently even on xp/vista/win 7 they don't want you using 185 or newer drivers yet because of some errors that cause incomplete workunits to be sent in as if they are finished,

I've been reading through a lot of those links on the folding forums (crap there is a lot of info spread out everywhere). It looks like the Vista Xp issue was on F@H's end and they released a new core to fix the issue, this should have been transparent to everyone.

There is however a problem with GPUGrid on BOINC in Linux with the 185's but not the 180 drivers. One branched off thread from that one mentions some versions of OpenSUSE work then newer ones don't with the 185's and someone says there is an issue in the kernel that is known to cause problems for SUSE and CUDA. Now I known most of us over here are using Ubuntu. I don't think any of us have tried 9.10 Karmic Koala with the 2.6.30 kernel. Maybe Nvidia made kernel specific changes and as far as they are concerned the driver works with the latest stable release. A lot of these posts date back to the end of July, so either it was resolved or people gave up.

I've been playing with Karmic on my netbook but I'm not sure if I dare install it on my desktop yet (mainly due to some issues I've read about GRUB 2).