Thanks for this info, GDF.
Actually, I test on two machines the 190.32 nvidia linux driver.
It gives me useful information about gpu fan speed and I can modify it.
Very handy to avoid hot temperatures on my gpu.

I thought you guys switched back in August to CUDA 2.2....

Mike D
____________

i'm using 190.18 beta and CUDA 2.3, works fine for me.

After running two applications in cuda 2.2 in Linux, the main difference seems to be that the cuda 2.2 application uses less CPU time. The overall speed of work unit completion seems about the same as is the credit granted. I don't know if the new application is any more stable or has any other advantages.

I'm curious. The Linux version of the client has been bumped to require CUDA 2.2, but still downloads v2.1 of the libs? Is that to be expected?

Erm.... You might want to re-think that... ;)

Is this supposed to be a 'in-place' runtime upgrade or should we need to detach and re-attach to the project to avoid issues?

You should not need to do anything.
gdf

For me, the Linux 2.2 applications are not only running well on my GTX 260 but they are running faster and producing more credit per day. For my system, this has been a real bonus. My system is Ubuntu 9.04 64bit running the Nvidia 190.32 drivers.
The best suggestion that I would have for the gentleman who is having trouble installing the 185 drivers is this.
1) Uninstall the 180.44 drivers via Synaptic
2) Edit your xorg.conf file to change the driver file to nv from nvidia in the "Driver" section
3) reboot
4) Install the 190.32 drivers from Nvidia in console mode. You can install also with a no x check option in a console window. This should remove the 185 driver files.
Hopefully this helps. It is sometimes easier to install the Nvidia drivers with a new clean install of the operating system. I never installed the binary drivers to begin with. I just started with the Nvidia drivers.
Good luck.

For me, the Linux 2.2 applications are not only running well on my GTX 260 but they are running faster and producing more credit per day. For my system, this has been a real bonus. My system is Ubuntu 9.04 64bit running the Nvidia 190.32 drivers.
The best suggestion that I would have for the gentleman who is having trouble installing the 185 drivers is this.
1) Uninstall the 180.44 drivers via Synaptic
2) Edit your xorg.conf file to change the driver file to nv from nvidia in the "Driver" section
3) reboot
4) Install the 190.32 drivers from Nvidia in console mode. You can install also with a no x check option in a console window. This should remove the 185 driver files.
Hopefully this helps. It is sometimes easier to install the Nvidia drivers with a new clean install of the operating system. I never installed the binary drivers to begin with. I just started with the Nvidia drivers.
Good luck.

If I were you, I would skip over the 185 drivers in the other machines and go straight to the 190.32 drivers. There seems to be no downside in using them and they will handle cuda 2.3 when the project gradually moves to that application.
I have been very pleased with the 190 drivers in both the Linux and Windows installations.

If I were you, I would skip over the 185 drivers in the other machines and go straight to the 190.32 drivers. There seems to be no downside in using them and they will handle cuda 2.3 when the project gradually moves to that application.
I have been very pleased with the 190 drivers in both the Linux and Windows installations.

Which version of nvclock are you running? Version 0.8 beta 4 should report correctly. You may also like to use nvidia-settings to look at temperature and overclocking. This is available in the Ubuntu repositories. nvclock-gtk is also available and should give you a more graphical look at your settings.

The 3D clock speeds are higher and this is what your card is using.

As for getting work, check the following
1) Look at your local settings in BOINC manager.
Advanced - Preferences Make sure that Use GPU while computer is in use is checked.
2) You may prefer to use the latest version of BOINC manager 6.10.4 which sometimes does a better job of requesting work.
3) Have you had any work units fail and with repeated requests are you over 9 work units requested and failed in the last 24 hours on the total number of machines on your account? If so, you may have to wait a day for more work to be sent. If this is the case, the problem will fix itself.

Which version of nvclock are you running? Version 0.8 beta 4 should report correctly.

You may also like to use nvidia-settings to look at temperature and overclocking. This is available in the Ubuntu repositories.

nvclock-gtk is also available and should give you a more graphical look at your settings.

The 3D clock speeds are higher and this is what your card is using.

As for getting work, check the following
1) Look at your local settings in BOINC manager.
Advanced - Preferences Make sure that Use GPU while computer is in use is checked.

2) You may prefer to use the latest version of BOINC manager 6.10.4 which sometimes does a better job of requesting work.

3) Have you had any work units fail and with repeated requests are you over 9 work units requested and failed in the last 24 hours on the total number of machines on your account? If so, you may have to wait a day for more work to be sent. If this is the case, the problem will fix itself.

BTW, nvclock-gtk that I'd tried some months ago... if you type it right... nvclock_gtk in a terminal... amazing the difference... LOL.
____________
- da shu @ HeliOS,
"A child's exposure to technology should never be predicated on an ability to afford it."

There can a lot of difference from machine to machine on work unit times. For comparison here are some typical run times on recent work units on my GTX 260 with Ubuntu 9.04 64bit.
1292656 795179 23 Sep 2009 7:27:35 UTC 23 Sep 2009 23:48:19 UTC Completed and validated 11,743.41 3,977.21 4,971.51
1291799 767517 23 Sep 2009 17:32:29 UTC 24 Sep 2009 6:40:57 UTC Completed and validated 12,396.47 3,977.21 4,971.51
1291407 793698 22 Sep 2009 23:09:53 UTC 23 Sep 2009 17:32:29 UTC Completed and validated 16,220.24 6,369.13 7,961.41
1289971 798031 22 Sep 2009 16:26:22 UTC 23 Sep 2009 7:27:35 UTC Completed and validated 15,640.62 4,531.91 5,664.89
1287757 796794 22 Sep 2009 3:37:20 UTC 22 Sep 2009 16:26:22 UTC Completed and validated 8,288.68 4,557.74 5,697.18
1286336 795917 21 Sep 2009 19:10:51 UTC 22 Sep 2009 10:02:12 UTC Completed and validated 10,728.99 3,977.21 4,971.51
1283707 792337 21 Sep 2009 8:54:10 UTC 22 Sep 2009 3:37:20 UTC Completed and validated 16,509.19 4,531.91 5,664.89
1282429 793682 21 Sep 2009 0:20:45 UTC 21 Sep 2009 19:10:51 UTC Completed and validated 16,386.30 6,369.13 7,961.41
1281296 780076 20 Sep 2009 17:34:52 UTC 21 Sep 2009 8:54:10 UTC Completed and validated 16,613.05 4,428.01 5,535.01
1279114 767733 22 Sep 2009 10:02:12 UTC 22 Sep 2009 23:09:53 UTC Completed and validated 12,969.97 3,977.21 4,971.51
1277818 790782 20 Sep 2009 0:21:12 UTC 20 Sep 2009 17:34:52 UTC Completed and validated 16,753.47 4,531.91 5,664.89

My run times will vary slightly if I go into Gnome System Monitor as root and upgrade the priority of the CPU time for the Gpugrid application.
My video card is overclocked to 729 mhz for the gpu clock and 1224 mhz for the memory clock. My stock speed is 620 mhz gpu clock and 1066 mhz for the memory clock.
I can only do this consistently if I run the IceWM desktop which puts fewer demands on the desktop. If I was running Gnome or KDE, I would overclock at a lower level. My card is an EVGA GTX 260 Superclocked.
Overclocking can be touchy. I find that after I boot up, I have to start the application at stock speed; let it run for 20 minutes; suspend it; start the overclock and then resume the application. If I don't do this, I tend to get computation errors.

For the clock speeds with the GTX 260, I meant that the 3D clock numbers will be higher than the 2D clock numbers that you are currently looking at. Sorry for the confusion.