hi Crunchers

Just to let you know that there'll be a new app coming to support the ascal GPUs just as soon as Nvidia make a public release of CUDA 8.

Matt

Will it help out the Maxwell cards?

The drivers ever since 361.43, released on December 21, 2015 are said to have included CUDA 8, for whatever that is worth. But as posted elsewhere, the earlier CUDA 7.5 driver are faster on the old app, so I wonder whether it would be useful to upgrade to a recent driver for the Maxwell cards.

hi Crunchers

Just to let you know that there'll be a new app coming to support the ascal GPUs just as soon as Nvidia make a public release of CUDA 8.

Matt

Thank you.

Eagerly awaiting !!!

+1 My Geforce 1070 can't await it... :-)

Anythoughts if this will incress GPU load percentage? I find that the GPU load is quite low compared to Folding@home.

Anythoughts if this will incress GPU load percentage? I find that the GPU load is quite low compared to Folding@home.

If you go back to the 359.6 driver your gpu load will rise by between 4% to 5%

hi Crunchers

Just to let you know that there will be a new app coming to support the Pascal GPUs just as soon as NVIDIA make a public release of CUDA 8.

Matt

27 May 2016
https://www.phoronix.com/scan.php?page=news_item&px=CUDA-8-Release-Candidate

https://developer.nvidia.com/cuda-toolkit

---

1 Corinthians 9:16 "For though I preach the gospel, I have nothing to glory of: for necessity is laid upon me; yea, woe is unto me, if I preach not the gospel!"
Ephesians 6:18-20, please ;-)
http://tbc-pa.org

Yeah, the Release Candidate has been around for some time, but you can't legally use it in publicly available apps...

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Yeah, the Release Candidate has been around for some time, but you can't legally use it in publicly available apps...

Judging by the time went by since then it's probably had a couple bugs to fix.
I recall that there were issues even with the CUDA subsystem of released drivers in the past.

It could still be used for building the code and working out some bugs in house then release the full product with very minimal testing once a bug free final CUDA 8 is released. I just don't want to see us waiting til a public official release comes out before touching it at all, which I assume is not happening anyway.

That has been happening. If there were no bugs then the Cuda 8 dev kit would have already been released for public use.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Bulletin for crunchers with Pascal GPU's and XP:

Microsoft Windows XP/Windows XP 64-bit driver support for GeForce GPUs has been deprecated with driver branch R370_00 and onward. Driver 368.81 is the last driver to support Windows XP/Windows XP 64-bit.

http://us.download.nvidia.com/Windows/372.54/372.54-win10-win8-win7-desktop-release-notes.pdf

https://forums.geforce.com/default/topic/957568/geforce-drivers/official-372-54-game-ready-whql-display-driver-feedback-thread-released-8-15-16-/1/

Can we crunch with today nvidia drivers on win10 on pascal gpu ? are short run available to test ? Or only long run ?

Not yet, but I'd like to ask pretty much the same thing: today driver 372.54 was released, including official CUDA 8 support. Is that enough yet?

MrS

---

Scanning for our furry friends since Jan 2002

Bulletin for crunchers with Pascal GPU's and XP:

Microsoft Windows XP/Windows XP 64-bit driver support for GeForce GPUs has been deprecated with driver branch R370_00 and onward. Driver 368.81 is the last driver to support Windows XP/Windows XP 64-bit.

I thought that this will happen. It's time for me to install Linux on one of my hosts.

Still failing with 372.54 Nvidia drivers and gtx 1070/1060

17/08/2016 07:02:51 | | Starting BOINC client version 7.6.22 for windows_x86_64
17/08/2016 07:02:51 | | log flags: file_xfer, sched_ops, task, sched_op_debug
17/08/2016 07:02:51 | | Libraries: libcurl/7.45.0 OpenSSL/1.0.2d zlib/1.2.8
17/08/2016 07:02:51 | | Data directory: C:\boinc_data
17/08/2016 07:02:51 | | Running under account lee_l
17/08/2016 07:02:52 | | CUDA: NVIDIA GPU 0: GeForce GTX 1070 (driver version 372.54, CUDA version 8.0, compute capability 6.1, 4096MB, 3562MB available, 6998 GFLOPS peak)
17/08/2016 07:02:52 | | CUDA: NVIDIA GPU 1: GeForce GTX 1060 6GB (driver version 372.54, CUDA version 8.0, compute capability 6.1, 4096MB, 3566MB available, 4374 GFLOPS peak)
17/08/2016 07:02:52 | | CUDA: NVIDIA GPU 2: GeForce GTX 1070 (driver version 372.54, CUDA version 8.0, compute capability 6.1, 4096MB, 3562MB available, 6998 GFLOPS peak)
17/08/2016 07:02:52 | | OpenCL: NVIDIA GPU 0: GeForce GTX 1070 (driver version 372.54, device version OpenCL 1.2 CUDA, 8192MB, 3562MB available, 6998 GFLOPS peak)
17/08/2016 07:02:52 | | OpenCL: NVIDIA GPU 1: GeForce GTX 1060 6GB (driver version 372.54, device version OpenCL 1.2 CUDA, 6144MB, 3566MB available, 4374 GFLOPS peak)
17/08/2016 07:02:52 | | OpenCL: NVIDIA GPU 2: GeForce GTX 1070 (driver version 372.54, device version OpenCL 1.2 CUDA, 8192MB, 3562MB available, 6998 GFLOPS peak)
17/08/2016 07:02:52 | | Host name: xixou-win10
17/08/2016 07:02:52 | | Processor: 6 GenuineIntel Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz [Family 6 Model 63 Stepping 2]
17/08/2016 07:02:52 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 vmx tm2 dca pbe fsgsbase bmi1 smep bmi2
17/08/2016 07:02:52 | | OS: Microsoft Windows 10: x64 Edition, (10.00.10586.00)
17/08/2016 07:02:52 | | Memory: 31.91 GB physical, 32.01 GB virtual
17/08/2016 07:02:52 | | Disk: 465.21 GB total, 41.05 GB free
17/08/2016 07:02:52 | | Local time is UTC +2 hours
17/08/2016 07:02:52 | | VirtualBox version: 5.0.12

17/08/2016 07:02:55 | GPUGRID | Starting task e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0
17/08/2016 07:02:55 | pogs | Starting task J010727.2+321911_area31916982_0
17/08/2016 07:02:57 | GPUGRID | [sched_op] Deferring communication for 00:01:27
17/08/2016 07:02:57 | GPUGRID | [sched_op] Reason: Unrecoverable error for task e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0
17/08/2016 07:02:57 | GPUGRID | Computation for task e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0 finished
17/08/2016 07:02:57 | GPUGRID | Output file e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0_1 for task e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0 absent
17/08/2016 07:02:57 | GPUGRID | Output file e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0_2 for task e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0 absent
17/08/2016 07:02:57 | GPUGRID | Output file e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0_3 for task e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0 absent

17/08/2016 07:03:00 | GPUGRID | Started upload of e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0_0
17/08/2016 07:03:00 | GPUGRID | Started upload of e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0_7
17/08/2016 07:03:01 | GPUGRID | Finished upload of e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0_0
17/08/2016 07:03:01 | GPUGRID | Finished upload of e39s6_e28s20p0f482-GERARD_FXCXCL12RX_1153966_1-0-1-RND9279_0_7

Still failing with 372.54 Nvidia drivers and gtx 1070/1060

Yes, it is not the drivers on your computer that counts at this point. It is the programing of the tasks to be done on that new driver (CUDA version) needed for the new cards. NVIDIA has to complete, test, and release a bug free version (a gold version) of the CUDA SDK for GPUGRID to make the code in the project work with your card and driver. The ball on this is in the NVIDIA court currently to release that after making a version that they feel confident in releasing.

Really, most companies that make an actual product makes the drivers and the SDK available to manufacturers of the products that work with their product and software companies that make software to work with that product before releasing the product and its user end drivers. In the case of this whole line of products NVIDIA seems to have done this backwards and released the product, the user drivers and not the toolkit to make products and software to use the GTX10 line of cards and the CUDA 8 platform.

So until NVIDIA releases that, the tasks coming out of GPUGRID will continue to fail on these new cards. That is unless GPUGRID uses the buggy/non-gold SDK available to compile new tasks risking more failed tasks for the sake of the processing power going untapped. I would think that unless they actually release the amount of work that surpasses the need for that extra unused power in the installed cards that want to crunch GPUGRID, they should not take that risk and should just let the NVIDIA timeline dictate the use of the cards. If they can release enough work to surpass the user's current non-GTX10 cards and actually need the GTX10 cards in production, then I would say there is even a discussion to be had on the matter of taking that risk.

We have received information that one important bug for us has been fixed.

You should expect new applications compatible with pascal soon after (a day) cuda8 is released. Initially for Linux and then for Windows (maybe a week later depending on how easy was the Linux release).

gdf

We have received information that one important bug for us has been fixed.

You should expect new applications compatible with pascal soon after (a day) cuda8 is released. Initially for Linux and then for Windows (maybe a week later depending on how easy was the Linux release).

gdf

great ! hoppefully long runs are not flagged as error as it was sometime the case on titan x maxwell. short runs were always ok.

We have received information that one important bug for us has been fixed.

You should expect new applications compatible with pascal soon after (a day) cuda8 is released. Initially for Linux and then for Windows (maybe a week later depending on how easy was the Linux release).

gdf

Hi Gianni,
How went the linux port ?