Next week we will update the linux application to CUDA2.2 which should require a driver version 185.xx.
It might be that your current driver works with it also.
So you might wait and test or just go on and install a newer driver.

gdf

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

---

only for windows

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?

21-Sep-2009 15:18:43 [http://www.gpugrid.net/] Master file download succeeded
21-Sep-2009 15:18:48 [http://www.gpugrid.net/] Sending scheduler request: Project initialization.
21-Sep-2009 15:18:48 [http://www.gpugrid.net/] Requesting new tasks for CPU and GPU
21-Sep-2009 15:18:53 [GPUGRID] Scheduler request completed: got 1 new tasks
21-Sep-2009 15:18:55 [GPUGRID] Started download of acemd_6.66_x86_64-pc-linux-gnu__cuda
21-Sep-2009 15:18:55 [GPUGRID] Started download of libcufft.so.2.1
21-Sep-2009 15:18:58 [GPUGRID] Finished download of libcufft.so.2.1
21-Sep-2009 15:18:58 [GPUGRID] Started download of libcudart.so.2.1
21-Sep-2009 15:18:59 [GPUGRID] Finished download of libcudart.so.2.1

We have just uploaded the new Linux app version 2.2.

gdf

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

21-Sep-2009 16:20:21 [GPUGRID] Scheduler request completed: got 2 new tasks
21-Sep-2009 16:20:23 [GPUGRID] Started download of acemd_6.68_x86_64-pc-linux-gnu__cuda
21-Sep-2009 16:20:23 [GPUGRID] Started download of libcufft.so.2.2
21-Sep-2009 16:20:27 [GPUGRID] Finished download of libcufft.so.2.2
21-Sep-2009 16:20:27 [GPUGRID] Started download of libcudart.so.2.2
21-Sep-2009 16:20:28 [GPUGRID] Finished download of libcudart.so.2.2
...
21-Sep-2009 16:20:47 [GPUGRID] Starting task p740000-IBUCH_2_pYEEI_2109-0-20-RND0599_0 using acemd version 668
21-Sep-2009 16:21:01 [GPUGRID] Computation for task p740000-IBUCH_2_pYEEI_2109-0-20-RND0599_0 finished

<core_client_version>6.10.6</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce 8800 GS"
# Clock rate: 1.45 GHz
# Total amount of global memory:                 401932288 bytes
# Number of multiprocessors:                     12
# Number of cores:                               96
# Driver version                                  2020
# Runtime version                                 2020
MDIO ERROR: cannot open file "restart.coor"
Cuda error: Kernel [mshake_position] failed in file 'mshake.cu' in line 99 : out of memory.

</stderr_txt>
]]>

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.
Just monitor if all is well with your system.
I have 4 Wus running on my machine (4x 275) and is all fine so far.

gdf

You should not need to do anything.
gdf

This is ASSUMING you can get the 185.xx or later driver to load right?

Four of my machines are crashing all GPUgrid WUs (using 180.44 driver) and the others are just a WU or two away.

I've been trying to get 185.xx built but so far no luck. The NVIDIA...pkg#2.run install goes OK, says it can't find a kernel and builds one. But after a reboot the first thing loaded is still 180.44 and then things go bad.

Obviously I'm missing something... The machine is dual boot... Do I need to do something to update grub so he points to the 'rebuilt' kernel from the .run installation?

Anybody have 185.xx or better installed on Ubuntu Jaunty (v9.04) 64b using the 2.6.28 kernel?

Sep 22 17:15:48 c17-desktop avahi-daemon[3321]: Server startup complete. Host name is c17-desktop.local. Local service cookie is 2274955198.
Sep 22 17:15:48 c17-desktop kernel: [ 17.607019] nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Sep 22 17:15:48 c17-desktop kernel: [ 17.607026] nvidia 0000:01:00.0: setting latency timer to 64
Sep 22 17:15:48 c17-desktop kernel: [ 17.607169] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 180.44 Tue Mar 24 05:46:32 PST 2009
Sep 22 17:15:48 c17-desktop anacron[3448]: Normal exit (0 jobs run)
Sep 22 17:15:48 c17-desktop /usr/sbin/cron[3492]: (CRON) INFO (pidfile fd = 3)
Sep 22 17:15:48 c17-desktop /usr/sbin/cron[3493]: (CRON) STARTUP (fork ok)
Sep 22 17:15:48 c17-desktop kernel: [ 17.695658] NVRM: API mismatch: the client has the version 185.18.36, but
Sep 22 17:15:48 c17-desktop kernel: [ 17.695659] NVRM: this kernel module has the version 180.44. Please
Sep 22 17:15:48 c17-desktop kernel: [ 17.695659] NVRM: make sure that this kernel module and all NVIDIA driver
Sep 22 17:15:48 c17-desktop kernel: [ 17.695660] NVRM: components have the same version.
Sep 22 17:15:48 c17-desktop /usr/sbin/cron[3493]: (CRON) INFO (Running @reboot jobs)
Sep 22 17:15:49 c17-desktop kernel: [ 18.315167] NVRM: API mismatch: the client has the version 185.18.36, but
Sep 22 17:15:49 c17-desktop kernel: [ 18.315168] NVRM: this kernel module has the version 180.44. Please
Sep 22 17:15:49 c17-desktop kernel: [ 18.315168] NVRM: make sure that this kernel module and all NVIDIA driver
Sep 22 17:15:49 c17-desktop kernel: [ 18.315169] NVRM: components have the same version.
Sep 22 17:15:51 c17-desktop acpid: client 3182[0:0] has disconnected
Sep 22 17:15:51 c17-desktop acpid: client connected from 3570[0:0]
Sep 22 17:15:51 c17-desktop kernel: [ 20.786084] NVRM: API mismatch: the client has the version 185.18.36, but
Sep 22 17:15:51 c17-desktop kernel: [ 20.786085] NVRM: this kernel module has the version 180.44. Please
Sep 22 17:15:51 c17-desktop kernel: [ 20.786086] NVRM: make sure that this kernel module and all NVIDIA driver
Sep 22 17:15:51 c17-desktop kernel: [ 20.786086] NVRM: components have the same version.
Sep 22 17:15:51 c17-desktop ntpdate[3259]: adjust time server 206.212.242.132 offset -0.213516 sec
Sep 22 17:15:51 c17-desktop ntpd[3609]: ntpd 4.2.4p4@1.1520-o Wed May 13 21:10:45 UTC 2009 (1)
Sep 22 17:15:51 c17-desktop ntpd[3610]: precision = 1.000 usec
Sep 22 17:15:51 c17-desktop ntpd[3610]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
Sep 22 17:15:51 c17-desktop ntpd[3610]: Listening on interface #1 wildcard, ::#123 Disabled
Sep 22 17:15:51 c17-desktop ntpd[3610]: Listening on interface #2 lo, ::1#123 Enabled
Sep 22 17:15:51 c17-desktop ntpd[3610]: Listening on interface #3 eth1, fe80::21f:d0ff:fed4:8037#123 Enabled
Sep 22 17:15:51 c17-desktop ntpd[3610]: Listening on interface #4 lo, 127.0.0.1#123 Enabled
Sep 22 17:15:51 c17-desktop ntpd[3610]: Listening on interface #5 eth1, 192.168.218.17#123 Enabled
Sep 22 17:15:51 c17-desktop ntpd[3610]: kernel time sync status 0040
Sep 22 17:15:51 c17-desktop ntpd[3610]: frequency initialized -27.498 PPM from /var/lib/ntp/ntp.drift
Sep 22 17:15:53 c17-desktop kernel: [ 22.977509] eth1: no IPv6 routers present
Sep 22 17:15:54 c17-desktop acpid: client 3570[0:0] has disconnected
Sep 22 17:15:54 c17-desktop acpid: client connected from 3614[0:0]
Sep 22 17:15:54 c17-desktop kernel: [ 23.879093] NVRM: API mismatch: the client has the version 185.18.36, but
Sep 22 17:15:54 c17-desktop kernel: [ 23.879094] NVRM: this kernel module has the version 180.44. Please
Sep 22 17:15:54 c17-desktop kernel: [ 23.879094] NVRM: make sure that this kernel module and all NVIDIA driver
Sep 22 17:15:54 c17-desktop kernel: [ 23.879095] NVRM: components have the same version.
Sep 22 17:15:54 c17-desktop gdm[3174]: CRITICAL: gdm_config_value_get_bool: assertion `value->type == GDM_CONFIG_VALUE_BOOL' failed
Sep 22 17:15:57 c17-desktop acpid: client 3614[0:0] has disconnected
Sep 22 17:15:57 c17-desktop acpid: client connected from 3670[0:0]
Sep 22 17:16:03 c17-desktop kernel: [ 32.713652] mtrr: base(0xe5000000) is not aligned on a size(0xe00000) boundary
Sep 22 17:16:57 c17-desktop console-kit-daemon[2947]: WARNING: Couldn't read /proc/2946/environ: Failed to open file '/proc/2946/environ': No such file or directory
Sep 22 17:17:01 c17-desktop /USR/SBIN/CRON[3900]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Sep 22 17:17:33 c17-desktop init: tty4 main process (2547) killed by TERM signal
Sep 22 17:17:33 c17-desktop init: tty5 main process (2548) killed by TERM signal
Sep 22 17:17:33 c17-desktop init: tty1 main process (3557) killed by TERM signal
Sep 22 17:17:33 c17-desktop init: tty2 main process (2551) killed by TERM signal
Sep 22 17:17:33 c17-desktop init: tty3 main process (2553) killed by TERM signal
Sep 22 17:17:33 c17-desktop init: tty6 main process (2555) killed by TERM signal
Sep 22 17:17:33 c17-desktop console-kit-daemon[2947]: WARNING: Unable to activate console: No such device or address
Sep 22 17:17:52 c17-desktop exiting on signal 15

---

- da shu @ HeliOS,
"A child's exposure to technology should never be predicated on an ability to afford it."

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.

Turns out the problem was that after "disabling" the 180.44 I needed to reboot back to the desktop w/o that driver BEFORE I started the terminal install of the Nvidia drivers. This pretty much got me thru your step #3.

190.32 now installed and at least I got my desktop back. I un-suspended the not-yet-started 6.68 WUs and the 1st one started up. Just checked back on it and the first got errors about 30 minutes into it. A 669-GIANNI... is running now. We'll see how it does. I've got a couple other machines with GTS-250s in them I need to go do. I think I'll try the 185.xx in the next one.

H<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
# Using CUDA device 0
# Device 0: "GeForce GTX 260"
# Clock rate: 1.24 GHz
# Total amount of global memory: 938803200 bytes
# Number of multiprocessors: 27
# Number of cores: 216
# Driver version 2030
# Runtime version 2020
MDIO ERROR: cannot open file "restart.coor"
Cuda error: Kernel [PmeRealSpace_compute_forces] failed in file 'PmeRealSpace.cu' in line 172 : the launch timed out and was terminated.

</stderr_txt>
]]>

---

- da shu @ HeliOS,
"A child's exposure to technology should never be predicated on an ability to afford it."

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.

One thing I noticed on 190.32... nvclock -s reports the 'current' GPU clock at the 2D setting. This is on the GTX-260. I don't think it's really running at 300MHz as it seems to be clicking along too fast for that but not sure.

On the 2nd machine.. GTS-250 with 185.18.36 nvclock -s reports the proper stuff...not sure where the discrepancy is yet. But now I can't get work on this machine :-(

Wed 23 Sep 2009 12:28:22 AM CDT|GPUGRID|Sending scheduler request: Requested by user. Requesting 259203 seconds of work, reporting 0 completed tasks
Wed 23 Sep 2009 12:28:27 AM CDT|GPUGRID|Scheduler request completed: got 0 new tasks
Wed 23 Sep 2009 12:28:27 AM CDT|GPUGRID|Message from server: No work sent
Wed 23 Sep 2009 12:28:27 AM CDT|GPUGRID|Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.

Any thoughts on how to make it get work other than coming up off of BOINC 6.4.5. I've already detached and re-attached.

---

- da shu @ HeliOS,
"A child's exposure to technology should never be predicated on an ability to afford it."

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.

That's what I'm using, from the Ubuntu Repositories.
I have "nvclock -n 650 -m 1050 -f" embedded in the start function of the /etc/init.d/boinc-client script. This seems to work fine as nvclock -s reports the "Coolbits" 2D and 3D settings as 650 1050. However "Current" is right now showing 324 & 1053. This occurs ONLY on my main desktop with the GTX-260. Some of the other machines are also Ubuntu Jaunty 64b with the same boinc version and same 190.32 driver but with GTS-250 or 8800GT or 9600GSO cards. There is also a machine with the 185.18 driver and a 9800GT. And two machines with GTS-250s & boinc 6.4.5 from getdeb. None of the other machines show this anomaly. For now I'm assuming it's really running at 650MHz while crunching the WU. It's this WU that's running now. I think this is the last app version 6.68 WU I have. What sort of reported run time in seconds should I expect assuming the card was running at the default 3D clocks? Although I'm not sure I trust that number because I see the last valid WU I see with two machines doing it says that the other guy's GTS-250 took 1/16th the time my GTX-260 did!?? But my GTX-260 has a higher average (FreeDC) and RAC than any of my GTS-250s (by about 50%, as it should). Maybe I'll just reinstall nvclock and see if that does anything.

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

Installed and using it also.

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

Have never figured out to invoke it, have it installed. Any tips? I guess I expected it to show up in a menu. It's been awhile.

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

Sorry, but to this one I gotta say "no duh". ;-)

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.

Local Prefs do not have "use GPU" checked but they have been cleared. I changed from using CPDN to GPUgrid for my preferences so I could make sure "use GPU" was on. It is and the machine (C17) with the funny nvclock is crunching the WU at what seems a normal rate.

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

Also upgraded boinc to 6.10.6 today on a few machines. Did the 190.32 driver last night.

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.

It appears it was this what caused the other two machines to not get work last night. They both got work sometime earlier today.


Anway, Thanx for your continued support.

---

- da shu @ HeliOS,
"A child's exposure to technology should never be predicated on an ability to afford it."

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.