Hi,
we would like to update the ACEMD application with a newer version which is faster and offers some extra features for the science.

We will try to keep only 4 versions:
compiled for CUDA3.2 for windows and Linux
compiled for CUDA2.2 for windows and Linux

However, we are not sure that the app will compile for CUDA2.2. I will confirm in the next few days.

gdf

Confirmed.
We will start to come out next week with cuda2.2 applications for windows and linux in beta.

If all goes well we will go on with the cuda3.2. All cards will be able to receive cuda3.2 apps.

gdf

Couldn't help saying this, when crunching for SETI, MB tasks, CUDA 2.3 appeared to be much faster then CUDA 2.2, why choose for CUDA 2.2?
(Or is the app already compiled?) :)

Well maybe I'm compairing apples and oranges......

---

Knight Who Says Ni N!

For us it's the same speed.

By the way, we will deprecate cuda3.1 and 3.0 applications due to several bugs in the CUDA libs. So you need to change driver to the latest driver to keep receiving cuda3 applications. This will be done slowly and notified in the news.

gdf

For us it's the same speed.

By the way, we will deprecate cuda3.1 and 3.0 applications due to several bugs in the CUDA libs. So you need to change driver to the latest driver to keep receiving cuda3 applications. This will be done slowly and notified in the news.

gdf

What driver version do we need for CUDA 3.2? The v260.89 and v260.99 drivers are badly flawed.

GDF, can you confirm that the latest driver will only be needed for Fermi cards?

The v260.89 and v260.99 drivers are bad for the 200Series cards, and probably earlier cards - the frequency drops and stays low.

I have not noticed any drop in frequency for my GTX470's with the latest driver, so I expect 260.99 works for Fermis.

I assume that if you have a g200 cards then you are still using the cuda2.2 application at the moment. In this case, you don't need to change driver.
You will need to change driver to receive a CUDA3 application. A 3.1 driver will not be enough when we remove the 3.1 app.

gdf

Thanks.

I guess this might in itself bring Linux support to the GTX460, GTS450 and still unreleased GTX475 (basically just a GTX460 with a full complement of shaders and cores) as it needs the 260.99 driver, but I don’t know what is under the bonnet of the latest ACEMD tool, so we might still need to wait on the 3.2 dev app to move from RC to final version?

Whatever the case, if it improves reliability or increases speed it will be very welcome.

For us it's the same speed.

By the way, we will deprecate cuda3.1 and 3.0 applications due to several bugs in the CUDA libs. So you need to change driver to the latest driver to keep receiving cuda3 applications. This will be done slowly and notified in the news.

gdf

What driver version do we need for CUDA 3.2? The v260.89 and v260.99 drivers are badly flawed.

Still, no answer to the question. What driver level is needed for cuda 3.2 support?

What driver level is needed for cuda 3.2 support?

Since 3.2 is not yet released, that is an unanswerable question.

MJH

What driver level is needed for cuda 3.2 support?

Since 3.2 is not yet released, that is an unanswerable question.

MJH

Found out myself:

nVidia has released the Forceware 261.00 driver. This driver is a special release intended primarily for developers, providing support for the CUDA Toolkit 3.2 RC2, so it's best used for experimental purposes.

It seems the fist OFFICIAL cuda 3.2 drivers will be the 265.xx series...

Here's some info on cuda 3.2:

http://developer.nvidia.com/object/cuda_3_2_toolkit_rc.html

There was a link to the v261.00 drivers but it has been removed.

For CUDA 2.2 you don't need to update your driver.

For CUDA 3.2, who knows, but this only applies to Fermi's and you will need the latest driver - whatever that will be tomorrow?

I don't know why I am surprised NVidia said 265.xx, it's not as if they are conformists when it comes to time tables, design, testing, series... Still it is a bit of a curve ball. If they do manage to ship a GTX475 by the end of Nov, the driver scene will be very messy. Chaos looms if they inflict a GF110 upon us.

What driver level is needed for cuda 3.2 support?

Since 3.2 is not yet released, that is an unanswerable question.

MJH

Found out myself:

nVidia has released the Forceware 261.00 driver. This driver is a special release intended primarily for developers, providing support for the CUDA Toolkit 3.2 RC2, so it's best used for experimental purposes.

It seems the fist OFFICIAL cuda 3.2 drivers will be the 265.xx series...

Here's some info on cuda 3.2:

http://developer.nvidia.com/object/cuda_3_2_toolkit_rc.html

There was a link to the v261.00 drivers but it has been removed.

The 260.89 onwards support cuda 3.2. It was released as whql so i'd call it "official". It has since been superceeded by 260.99 which is also whql. Both have the down-clocking issue on non-Fermi cards though, so you might want to wait.

---

BOINC blog

Developer Drivers for WinXP (261.00) <Coming Soon!>
Developer Drivers for WinVista and Win7 (261.00) <Coming Soon!>
Saw it listed here

I have changed the server policy.
Now all cards with the appropriate driver should be able to get the CUDA3.1 application. G200 cards installed together with Fermi cards will not work properly until we will release a cuda3.2 app.

This allows many old cuda2.2 bugs to be fixed on g200 cards if you just update the driver to a recent one. Change only if you have problems with the cuda2.2 app.

gdf

To test if this frequency bug effects all 200series cards or just some I installed 260.99 for a GT240 (DDR3 1GB version) on a W7x64 system.
Boinc downloaded the CUDA3.1 app and is now running a 6.11 TONI_KKi4 task.

It's possible it will not cause problems on the 40nm GT240s and may only cause problems on specific makes of cards, depending on their Firmware.

GPU details:
Core Clock at 597MHz,
Shaders at 1595MHz,
RAM at 800MHz (x2)
Fan speed 60%
GPU temp 49 deg C.
GPU usage 89 to 94 %, mostly 91%.

No problems so far; the GT240 has not slowed any after 1h.

Picked up a 6.11 CUDA 3010 task on another GT240 with the 258.96 driver, so we dont need to use the 260.99 driver for 200 series cards.

I installed 260.99 for a GT240 (DDR3 1GB version) on a W7x64 system.
Boinc downloaded the CUDA3.1 app and is now running a 6.11 TONI_KKi4 task.
No problems so far, but I want to test if this frequency bug effects all 200series cards or just some; it's possible it will not cause problems on the GT240s and may only cause problems on specific makes of cards, depending on their Firmware.

GPU details:
Core Clock at 597MHz,
Shaders at 1595MHz,
RAM at 800MHz (x2)
Fan speed 60%
GPU temp 49 deg C.
GPU usage 89 to 94 %, mostly 91%.

The GT240 did not slow down after 40min.

Picked up a 6.11 CUDA 3010 task on another GT240 with the 258.96 driver, so we dont need to use the 260.99 driver for 200 series cards.

The slowdown occurred in XP64 with both v260.89 & v460.99 on 5 cards. Two were GTX 260 and three were GT 240. Win7 uses a different driver so your experience may be better, but then you have to put up with the ~ 20% Win7 penalty...

I also picked up 6.11 tasks on both of my GTX 260 cards with 258.96 drivers. So far running OK but appear to be a little slower than the 6.05 app.

Thanks Beyond, that paints a clearer picture.
It looks like the 260.89 and 260.99 drivers may work for 200series cards on Win7 and Vista, but not on XP. I suggest people only use the 260.99 driver, if they must, but we really need a better driver before going to CUDA 3.2 only, if that is the plan. Hopefully NVidia will bring out a fully functional 261.xx soon.

I will update to the 260.99 driver on my Vista system this evening (UK) and give it a go. It has 4 GT240's.
For some still unknown reason my GTX260 failed all tasks on Vista and W7 the last time I tried, but I may try it on XP X86 in a day or so (if no new drivers turn up). It's sitting on my desk awaiting a test system.

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

It might, but other updates did not, so I'm not holding out much hope. Give it a go in a few days and see.