So, as said a couple of weeks ago we would like to upgrade in the near future to CUDA2.2.

This has the effect that only the most recent driver (above 185.xx) would then work.

Any problem with that?

gdf

So, as said a couple of weeks ago we would like to upgrade in the near future to CUDA2.2.

This has the effect that only the most recent driver (above 185.xx) would then work.

Any problem with that?

gdf

I need a couple of days warning to flush the cache and upgrade the driver. If you can pick a date and let us know when please. Also what will the minimum driver version be? 185.50?

---

BOINC blog

Sure, we can fix a date. Let's wait some more comments.

I have tried with 186.xx under windows xp 32 and it works. We will do some more tests on other drivers.

gdf

We will probably go to CUDA2.1 fully (compilation and libraries). For limitation of the BOINC client it was not so yet.

Tests show that it runs on new drivers 186.xx and old drivers newer than 180/181 at least.

This should be the safer move for now.

gdf

Two remarks from my side.

1. It is now summer holiday season in the northern hemisphere, so many take 2 to 4 weeks off, away from home and their PCs. So the switch date needs to be some weeks ahead of now.

2. More importantly, there is the Linux users. The standard Ubuntu 9.04 driver is still 180.44, not good enough for CUDA 2.2. However, from what I have been reading the 185 and 186 series for Linux seem to create quite some trouble, meaning that Linux arguably is not ready yet for the transfer to CUDA 2.2. Also, changing non standard drivers under Linux is a bit more difficult than under Windows.

My recommendation would therefore be to consider to holdoff the switchover till Ubuntu is ready to switch to a 185 or better series standard driver.

Switching too soon or too abruptly might lead to a significant loss of contributing PCs and therefore defy the benefit of the upgraded app.

Hint - a possible workaround to not loose the users with older "outdated" drivers would be to have 2 apps available with an opt-in preference box for the new CUDA 2.2 capable app. Variations on this theme are possible.

For your consideration.

Kind regards

Alain

PS - and already tomorrow my GPUGRID cruncher will be out of physical reach for me :). Happy holidays.

As we are just moving to cuda2.1, we will probably upgrade this week.

If you have driver newer than 180.xx for Linux and 181.xx for Windows, there should be nothing you need to do. Of course keep an eye on it if you can.
(These have been already the suggested driver version of gpugrid for months now).

The advantage is that the new application will run on 186 driver too.

[EDIT: In fact it does not. GRRRRR]
gdf

I would suggest a news saying "We will switch to blablabla in the next 2 days".

I think more people see news than read forums...

I try to test newer version of nvidia drivers.
With 185.18.14 and boinc 6.4.5 linux version, all my work units left in errors.
Actually, I use 180.29 version of nvidia drivers.

We are still testing cuda version and driver issues.
Is anybody able to run now on 185.xx?

gdf

The problem seems to be more serious. It seems that there is an incompatibility between the BOINC client and drivers 185.xx. We have submitted a bug report to Anderson.

All stopped until further notice.

gdf

i'm able to run on 185.86 no problems..... i have cuda toolkit 2.2 installed.

186.18 was a problem for me though..


q6600, gtx 260, vista 32-bit. running 6.6.28 but did run 6.6.36 and it works fine under that boinc release version, but i like 6.6.28 more as it's a little more stable and doesn't throw me a crazy error in messages.

---

I recommend Secunia PSI: http://secunia.com/vulnerability_scanning/personal/

Running 6.5.0 and 185.66 on Vista 64 without problems.

MrS

---

Scanning for our furry friends since Jan 2002

Boinc 6.6.36 Nvidia 186.18 Win XP64, 2 evga 260s with NO problems at all.

I run on a GTX 285 with cudadriver_2.2_vista_64_185.85_general,
BOINC-Manager 6.4.7 without any problems.

---

Greetings from TJ

It might not matter all that much for a while -- the server has been out of disk space for 6 hours or so -- not seen any notice that folks who handle the project are in the loop of this though, which is kind of disappointing.

same here latest driver on a 9800gtx and 8500gt no issue.

It might not matter all that much for a while -- the server has been out of disk space for 6 hours or so -- not seen any notice that folks who handle the project are in the loop of this though, which is kind of disappointing.

Men, it was night over here. Fixed.

gdf

Coming back to the problems with the driver. We can reproduce on all of our machines Linux64 and Windows Vista 32.
It happens on any version of the BOINC client with the new driver.

I could add a beta application compiled with CUDA2.2 for you guys to check.

gdf

What, you mean you don't hover over the server 24/7? <smile>

I figured as much, and noted it on a couple of other threads.

And yes it looks to be fixed. Thanks for that.

Men, it was night over here. Fixed.

gdf

Actually, it isn't quite fixed:

7/8/2009 12:55:46 AM|GPUGRID|Sending scheduler request: Requested by project. Requesting 0 seconds of work, reporting 1 completed tasks
7/8/2009 12:55:51 AM|GPUGRID|Scheduler request completed: got 0 new tasks
7/8/2009 12:55:51 AM|GPUGRID|Message from server: Project is temporarily shut down for maintenance

But it is clear it is getting worked on.

Men, it was night over here. Fixed.

gdf