Latest drivers (NVidia and ATI)

[msattler]

Kitties just found new 295.51 beta NV driver released today.....

[arkayn]

They have the links swapped on the page, the 32-bit points to the 64-bit driver and vice-versa.

[msattler]

Thanks for the heads up....
They may have that fixed before this weekend when I have a chance to play with it, but I'll keep any eye on it.

[TouchuvGrey]

it's fixed. Downloaded and installed.
Will play with it tonight if i have chance.

[Claggy]

Beware of the 295.51 drivers, once my Monitor connected to the DVI port went to Sleep, the Cuda device became unavailable,
they were O.K on my other host using the VGA port, your mileage may vary.

Claggy

[MarkJ]

Anything useful in cuda 4.1 for us? Does the optimizing compiler make any difference to earlier ones?

Decent performance gain on Fermis.  Older GPUs are seeing a slowdown over Cuda 3.2, which has been reported & apparently reproduced by nVidia.  I was hoping they'd fix that by release, as it means will probably have to support 2 builds next installer.

Jason

Was that cuda 3.2 apps on the beta driver?

Have you compiled a cuda 4.1 app to see how it goes?

MarkJ

[Claggy]

Anything useful in cuda 4.1 for us? Does the optimizing compiler make any difference to earlier ones?

Decent performance gain on Fermis.  Older GPUs are seeing a slowdown over Cuda 3.2, which has been reported & apparently reproduced by nVidia.  I was hoping they'd fix that by release, as it means will probably have to support 2 builds next installer.

Jason

Was that cuda 3.2 apps on the beta driver?

Have you compiled a cuda 4.1 app to see how it goes?

MarkJ

It was Cuda41rc2 and Cuda41 apps that were quite a bit slower than Cuda32 apps on Pre-Fermi GPUs (like my 9800GTX+) with the Cuda41 drivers, Fermi's have a performance increase with Cuda41rc2 and Cuda41 apps,

Claggy

[corsair]

roarming tarifs in data  (as usual very cheaps, nearly the whole salary) and can't test new drivers for my APU 

will see when arrive home for shore leaves in April, now in Rotterdam discharging.

[Claggy]

295.73 WHQL is out, downloading now.

Edit: the disappearing cuda devibe bug is still apparenin these drivers too.

Claggy

[PatrickV2]

295.73 WHQL is out, downloading now.

Claggy

I see NVidia promises some major improvements for several games, but how is the CUDA processing with these drivers?

I'd like to know before I convert my main gaming rig (which crunches WU's when not gaming) to these new drivers...

Regards,

Patrick.

[arkayn]

In other-words, skip this one as well.

I will stick with 290.53 for now.

[PatrickV2]

295.73 WHQL is out, downloading now.

Edit: the disappearing cuda device bug is still apparent in these drivers too.

Claggy

Damn. The performance increases for several of the games I play (or want to play) are very tempting.

IIRC the disappearing cuda device bug happens when the card switches off its output to blank the screen? So that's something that would happen to me after ~15 minutes of no activity. Is there a way to get around this?

Regards, Patrick.

[Claggy]

295.73 WHQL is out, downloading now.

Edit: the disappearing cuda device bug is still apparent in these drivers too.

Claggy

Damn. The performance increases for several of the games I play (or want to play) are very tempting.

IIRC the disappearing cuda device bug happens when the card switches off its output to blank the screen? So that's something that would happen to me after ~15 minutes of no activity. Is there a way to get around this?

Regards, Patrick.

My E8500/9800GTX+ machine had no problem with the 295.51 drivers when connected through the VGA port, not tried 295.73 on it yet,

Claggy

[PatrickV2]

295.73 WHQL is out, downloading now.

Edit: the disappearing cuda device bug is still apparent in these drivers too.

Claggy

Damn. The performance increases for several of the games I play (or want to play) are very tempting.

IIRC the disappearing cuda device bug happens when the card switches off its output to blank the screen? So that's something that would happen to me after ~15 minutes of no activity. Is there a way to get around this?

Regards, Patrick.

My E8500/9800GTX+ machine had no problem with the 295.51 drivers when connected through the VGA port, not tried 295.73 on it yet,

Claggy

Well, my 8800GTX is connected via DVI-D to my monitor. Will I run into this problem or not?

I suppose I could test this, but how can I detect this ASAP so that I don't trash too many WUs (if that happens)?

Regards, Patrick.

[arkayn]

When I noticed it, I saw a lot of this in my events.

1/31/2012 15:20:30 | SETI@home | Restarting task 04oc11ad.507.107123.6.10.252_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:20:38 | SETI@home | Restarting task 04oc11ad.507.90813.6.10.118_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:20:58 | SETI@home | Restarting task 04oc11ad.13433.885.8.10.85_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:21:06 | SETI@home | Restarting task 04oc11ad.13433.885.8.10.185_0 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:21:26 | SETI@home | Restarting task 02oc11ag.7971.6806.5.10.28_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:21:34 | SETI@home | Restarting task 04oc11ad.507.4566.6.10.54_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:21:54 | SETI@home | Restarting task 02oc11ag.7971.6806.5.10.26_0 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:22:03 | SETI@home | Restarting task 02oc11ag.7971.13303.5.10.138_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:22:22 | SETI@home | Restarting task 04oc11ad.507.87132.6.10.207_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:22:32 | SETI@home | Restarting task 02oc11ag.7971.13303.5.10.149_0 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:22:50 | SETI@home | Restarting task 02oc11ag.19404.4569.3.10.79_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:23:00 | SETI@home | Restarting task 02oc11ag.19404.4569.3.10.119_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:23:18 | SETI@home | Restarting task 25oc11ab.4355.134274.16.10.91_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:23:29 | SETI@home | Restarting task 02oc11ag.7971.13303.5.10.147_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:23:47 | SETI@home | Restarting task 25oc11ab.4355.140409.16.10.114_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:23:57 | SETI@home | Restarting task 04oc11ad.507.107123.6.10.254_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:24:14 | SETI@home | Restarting task 04oc11ad.507.90813.6.10.118_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:24:26 | SETI@home | Restarting task 04oc11ad.507.107123.6.10.252_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:24:43 | SETI@home | Restarting task 04oc11ad.13433.885.8.10.85_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:24:55 | SETI@home | Restarting task 04oc11ad.13433.885.8.10.185_0 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:25:11 | SETI@home | Restarting task 04oc11ad.507.4566.6.10.54_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:25:23 | SETI@home | Restarting task 02oc11ag.7971.6806.5.10.28_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:25:39 | SETI@home | Restarting task 02oc11ag.7971.6806.5.10.26_0 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:25:51 | SETI@home | Restarting task 04oc11ad.507.87132.6.10.207_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:26:07 | SETI@home | Restarting task 02oc11ag.7971.13303.5.10.149_0 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:26:23 | SETI@home | Restarting task 02oc11ag.19404.4569.3.10.79_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:26:36 | SETI@home | Restarting task 02oc11ag.19404.4569.3.10.119_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:26:52 | SETI@home | Restarting task 25oc11ab.4355.134274.16.10.91_1 using setiathome_enhanced version 610 (cuda_fermi)
1/31/2012 15:27:04 | SETI@home | Restarting task 02oc11ag.7971.13303.5.10.147_1 using setiathome_enhanced version 610 (cuda_fermi)

And we see this in the bench application when the DVI connected monitor goes to sleep.

setiathome_CUDA: cudaGetDeviceCount() call failed.
setiathome_CUDA: No CUDA devices found
setiathome_CUDA: Found 0 CUDA device(s):
setiathome_CUDA: No SETI@home capabale CUDA GPU found...