do you mean this one? crunched in 6 or 7 minutes.

http://www.gpugrid.net/result.php?resultid=20962989

but i cann't see which gpu is used to crunch this task

How to select work for the new app? "New version of ACEMD" app is not a choice under project preferences. The current choices are only these:

ACEMD short runs (2-3 hours on fastest card)
ACEMD long runs (8-12 hours on fastest GPU)
ACEMD Beta
Quantum Chemistry (CPU)
Quantum Chemistry (CPU, beta)
Python Runtime

"ACEMD Beta" looks likely, but the name doesn't match "New version of ACEMD", which is how it is being reported over on wuprop. And also it does not match the name on the app page. In fact, the app page indicates that "ACEMD Beta" and "New version of ACEMD" are completely different apps.
____________
Reno, NV
Team: SETI.USA

So far we got one success, i.e. 20962989.

How to select work for the new app? "New version of ACEMD" app is not a choice under project preferences. The current choices are only these:

ACEMD short runs (2-3 hours on fastest card)
ACEMD long runs (8-12 hours on fastest GPU)
ACEMD Beta
Quantum Chemistry (CPU)
Quantum Chemistry (CPU, beta)
Python Runtime

"ACEMD Beta" looks likely, but the name doesn't match "New version of ACEMD", which is how it is being reported over on wuprop. And also it does not match the name on the app page. In fact, the app page indicates that "ACEMD Beta" and "New version of ACEMD" are completely different apps.

probably my next build (in 6-10months) will be 4, 5 or 6 rtx cards. hopefully is the app then mature enough for investing couple of thousand euro for gpugrid

Try sending out more experimental WUs and see if it is one driver version

Errored WUs on multiple different drivers and OS's

http://www.gpugrid.net/results.php?userid=306281

Multiple failures of this task on both windows and linux

http://www.gpugrid.net/workunit.php?wuid=16517304

My host 43404 got one of WU 16517259.

Like all the others, it failed within one second:

Recent changes:
* sent 100 more test wus
* deprecated the windows "acemd3" app
* made acemd3 as beta
* fixed its name in prefs

Can you please explain which app we have to select in our project preferences to get these tasks? The app name "New version of ACEMD" is not a an option in the project preferences.

I got 1 task but it failed.:-(

http://www.gpugrid.net/result.php?resultid=20974689

linux mint 19.1
GTX 1080
Driver: 390.116
Cuda version 9.1

All but 2 of the libraries that were downloaded are marked as executable. Should libgcc and libOpenCL also be executable?

regarding the error on my task:

# Engine failed: Error launching CUDA compiler: 32512
sh: 1: : Permission denied

Is this solution relevant?

https://github.com/pandegroup/openmm/issues/1352

http://www.gpugrid.net/result.php?resultid=20974104

fail on msi gtx 1070, 8gb itx card, windows 10

Hi Toni

are you explicitly naming the path to libnvrtc-builtins.so when compiling?

perhaps include boinc project folder in LD_LIBRARY_PATH

name a11-TONI_TEST3-0-1-RND0663
https://www.gpugrid.net/workunit.php?wuid=16517242
Failure on all machines.

My result here:https://www.gpugrid.net/result.php?resultid=20976177

My log:
50 GPUGRID 6/4/2019 2:44:30 AM Started download of acemd3.119.exe
51 GPUGRID 6/4/2019 2:44:30 AM Started download of boost_filesystem-vc140-mt-1_65_1.119.dll
52 GPUGRID 6/4/2019 2:44:32 AM Finished download of acemd3.119.exe
53 GPUGRID 6/4/2019 2:44:32 AM Started download of boost_system-vc140-mt-1_65_1.119.dll
54 GPUGRID 6/4/2019 2:44:33 AM Finished download of boost_filesystem-vc140-mt-1_65_1.119.dll
55 GPUGRID 6/4/2019 2:44:33 AM Finished download of boost_system-vc140-mt-1_65_1.119.dll
56 GPUGRID 6/4/2019 2:44:33 AM Started download of cufft64_80.119.dll
57 GPUGRID 6/4/2019 2:44:33 AM Started download of msvcp140.119.dll
58 GPUGRID 6/4/2019 2:44:38 AM Finished download of msvcp140.119.dll
59 GPUGRID 6/4/2019 2:44:38 AM Started download of nvrtc64_80.119.dll
60 GPUGRID 6/4/2019 2:45:06 AM Finished download of nvrtc64_80.119.dll
61 GPUGRID 6/4/2019 2:45:06 AM Started download of nvrtc-builtins64_80.119.dll
62 GPUGRID 6/4/2019 2:45:28 AM Finished download of nvrtc-builtins64_80.119.dll
63 GPUGRID 6/4/2019 2:45:28 AM Started download of OpenMMCPU.119.dll
64 GPUGRID 6/4/2019 2:45:30 AM Finished download of OpenMMCPU.119.dll
65 GPUGRID 6/4/2019 2:45:30 AM Started download of OpenMMCudaCompiler.119.dll
66 GPUGRID 6/4/2019 2:45:32 AM Finished download of OpenMMCudaCompiler.119.dll
67 GPUGRID 6/4/2019 2:45:32 AM Started download of OpenMMCUDA.119.dll
68 GPUGRID 6/4/2019 2:45:39 AM Finished download of OpenMMCUDA.119.dll
69 GPUGRID 6/4/2019 2:45:39 AM Started download of OpenMM.119.dll
70 GPUGRID 6/4/2019 2:45:48 AM Finished download of OpenMM.119.dll
71 GPUGRID 6/4/2019 2:45:48 AM Started download of OpenMMOpenCL.119.dll
72 GPUGRID 6/4/2019 2:45:54 AM Finished download of OpenMMOpenCL.119.dll
73 GPUGRID 6/4/2019 2:45:54 AM Started download of OpenMMPME.119.dll
74 GPUGRID 6/4/2019 2:45:58 AM Finished download of OpenMMPME.119.dll
75 GPUGRID 6/4/2019 2:45:58 AM Started download of psprolib.119.dll
76 GPUGRID 6/4/2019 2:46:00 AM Finished download of psprolib.119.dll
77 GPUGRID 6/4/2019 2:46:00 AM Started download of vcruntime140.119.dll
78 GPUGRID 6/4/2019 2:46:01 AM Finished download of vcruntime140.119.dll
79 GPUGRID 6/4/2019 2:46:01 AM Started download of a11-TONI_TEST3-0-conf_file_enc
80 GPUGRID 6/4/2019 2:46:02 AM Finished download of a11-TONI_TEST3-0-conf_file_enc
81 GPUGRID 6/4/2019 2:46:02 AM Started download of a11-TONI_TEST3-0-coor_file
82 GPUGRID 6/4/2019 2:46:03 AM Finished download of a11-TONI_TEST3-0-coor_file
83 GPUGRID 6/4/2019 2:46:03 AM Started download of a11-TONI_TEST3-0-vel_file
84 GPUGRID 6/4/2019 2:46:04 AM Finished download of a11-TONI_TEST3-0-vel_file
85 GPUGRID 6/4/2019 2:46:04 AM Started download of a11-TONI_TEST3-0-idx_file
86 GPUGRID 6/4/2019 2:46:05 AM Finished download of a11-TONI_TEST3-0-idx_file
87 GPUGRID 6/4/2019 2:46:05 AM Started download of a11-TONI_TEST3-0-xsc_file
88 GPUGRID 6/4/2019 2:46:06 AM Finished download of a11-TONI_TEST3-0-xsc_file
89 GPUGRID 6/4/2019 2:46:06 AM Started download of a11-TONI_TEST3-0-pdb_file
90 GPUGRID 6/4/2019 2:46:11 AM Finished download of a11-TONI_TEST3-0-pdb_file
91 GPUGRID 6/4/2019 2:46:11 AM Started download of a11-TONI_TEST3-0-psf_file
92 GPUGRID 6/4/2019 2:46:24 AM Finished download of a11-TONI_TEST3-0-psf_file
93 GPUGRID 6/4/2019 2:46:24 AM Started download of a11-TONI_TEST3-0-par_file
94 GPUGRID 6/4/2019 2:46:26 AM Finished download of a11-TONI_TEST3-0-par_file
95 GPUGRID 6/4/2019 2:46:26 AM Started download of a11-TONI_TEST3-0-prmtop_file
96 GPUGRID 6/4/2019 2:46:27 AM Finished download of a11-TONI_TEST3-0-prmtop_file
97 GPUGRID 6/4/2019 2:49:48 AM Finished download of cufft64_80.119.dll
98 GPUGRID 6/4/2019 2:49:49 AM Starting task a11-TONI_TEST3-0-1-RND0663_5
99 GPUGRID 6/4/2019 2:49:50 AM Computation for task a11-TONI_TEST3-0-1-RND0663_5 finished
100 GPUGRID 6/4/2019 2:49:50 AM Output file a11-TONI_TEST3-0-1-RND0663_5_0 for task a11-TONI_TEST3-0-1-RND0663_5 absent
101 GPUGRID 6/4/2019 2:49:50 AM Output file a11-TONI_TEST3-0-1-RND0663_5_9 for task a11-TONI_TEST3-0-1-RND0663_5 absent
____________
Team USA forum | Team USA page
Join us and #crunchforcures. We are now also folding:join team ID 236370!

There are many more successes now.

Edit.

The reason for failures is not really clear. Question for anybody who has seen a success: do you have the CUDA Toolkit installed?

This is the list of the successful tasks: http://www.gpugrid.net/results.php?userid=306281

This is the list of the successful tasks: http://www.gpugrid.net/results.php?userid=306281

access denied :-(

I have 2 machines. Both have linux mint 19.1 installed, same nvidia driver (390.116), cuda toolkit release 9.1 (both tested as functional), same boinc version 7.14.2.

The hardware is different:

dual GTX 1080's on 2700X: All tasks are failing.

http://www.gpugrid.net/results.php?hostid=482792

dual GTX 1080 Ti's on E5-2690 v2: All tasks are completing successfully!

http://www.gpugrid.net/results.php?hostid=464987


There must be a clue here. Any ideas?

Question for anybody who has seen a success: do you have the CUDA Toolkit installed?

I have 2 machines. Both have linux mint 19.1 installed, same nvidia driver (390.116), cuda toolkit release 9.1 (both tested as functional), same boinc version 7.14.2.

The hardware is different:

dual GTX 1080's on 2700X: All tasks are failing.

http://www.gpugrid.net/results.php?hostid=482792

dual GTX 1080 Ti's on E5-2690 v2: All tasks are completing successfully!

http://www.gpugrid.net/results.php?hostid=464987


There must be a clue here. Any ideas?

There are many more successes now.

Edit.

The reason for failures is not really clear. Question for anybody who has seen a success: do you have the CUDA Toolkit installed?

Hello Toni, I have received many successes and when I typed "nvcc -V" to verify the CUDA Toolkit version, it says "The program 'nvcc' is currently not installed. You can install it by typing:

sudo apt install nvidia-cuda-toolkit"

My system seems to not have it installed.

This is the list of the successful tasks: http://www.gpugrid.net/results.php?userid=306281

I completed one while 5 others had errors.
https://www.gpugrid.net/workunit.php?wuid=16520276

nvcc -V results
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2017 NVIDIA Corporation
Built on Fri_Nov__3_21:07:56_CDT_2017
Cuda compilation tools, release 9.1, V9.1.85

But as soon as I rebooted, nvcc could not be found. So I ended up adding the library directory as an export in .bashrc and then I could find nvcc after reboots.

But as soon as I rebooted, nvcc could not be found. So I ended up adding the library directory as an export in .bashrc and then I could find nvcc after reboots.

Another option is to place the cuda library path in a file in /etc/ld.so.conf.d.

you could name the file cuda.conf

then:

sudo ldconfig

Well, I see I attempted to run a task that failed on one host. I looked over all the downloaded files and thought to do a sanity check on the executable. This is what ldd showed.

keith@Numbskull:~/Desktop/BOINC/projects/www.gpugrid.net$ ldd '/home/keith/Desktop/BOINC/projects/www.gpugrid.net/acemd.919-80.bin' linux-vdso.so.1 (0x00007ffdf14d5000)
libcuda.so.1 => /usr/lib/x86_64-linux-gnu/libcuda.so.1 (0x00007fa630a0c000)
libcudart.so.8.0 => not found
libcufft.so.8.0 => not found
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa630808000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fa6305e9000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fa630260000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa62fec2000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa62fcaa000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa62f8b9000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fa62f6b1000)
libnvidia-fatbinaryloader.so.418.56 => /usr/lib/x86_64-linux-gnu/libnvidia-fatbinaryloader.so.418.56 (0x00007fa62f463000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa631b63000)
keith@Numbskull:~/Desktop/BOINC/projects/www.gpugrid.net$


So right off the bat, the app had no chance of succeeding when it can't find its own downloaded libcudart.so.8.0 and libcufft.so.8.0 files in the project directory.

I don't think it would make any difference if/when all the files and work unit get copied into a slot.

libcudart.so.8.0 => not found
libcufft.so.8.0 => not found

So right off the bat, the app had no chance of succeeding when it can't find its own downloaded libcudart.so.8.0 and libcufft.so.8.0 files in the project directory.

Hi all, thanks for the reports.

@biodoc, can you see other obvious differences between the two machines? E.g.

- boinc installation method
- presence of the gcc package

I did find a "messy" install of the nvidia driver on the offending machine. There seems to be remnants of a driver installed via download directly from nvidia. I'll clean that up.

'sudo apt search nvidia' showed significant differences between the 2 machines.

From what I know, "apt search" does not look at the packages installed in your system but those "accessible" online. So, the difference may be in the repository configurations.

Toni
host:
CUDA: NVIDIA GPU 0: GeForce GTX 1080 (driver version 418.56, CUDA version 10.1, compute capability 6.1, 4096MB, 3968MB available, 9718 GFLOPS peak)
OpenCL: NVIDIA GPU 0: GeForce GTX 1080 (driver version 418.56, device version OpenCL 1.2 CUDA, 8112MB, 3968MB available, 9718 GFLOPS peak)

Progress.log from a vaild task:

#
# ACEMD version 3.2.0rc0-65-gdb8d7f8[/code]
#
# Copyright (C) 2017-2019 Acellera (www.acellera.com)
#
# When publishing, please cite:
# ACEMD: Accelerating Biomolecular Dynamics in the Microsecond Time Scale
# M. J. Harvey, G. Giupponi and G. De Fabritiis,
# J Chem. Theory. Comput. 2009 5(6), pp1632-1639
# DOI: 10.1021/ct9000685
#
# ACEMD is running in Boinc mode!
#
# Read input file: input
# Parse input file
# WARNING: Keyword "hydrogenscale" is deprecated: Hydrogen mass scaling enabled when timestep > 2.0
# WARNING: Keyword "rigidbonds" is deprecated: Rigid bonds set when timestep > 1.0
# WARNING: Keyword "exclude" is deprecated: 1-4 exclusion automatically set by force-field
# WARNING: Keyword "1-4scaling" is deprecated: 1-4 scaling automatically set by force-field
# WARNING: Keyword "pmegridsizex" is deprecated: Feature not supported
# WARNING: Keyword "pmegridsizey" is deprecated: Feature not supported
# WARNING: Keyword "pmegridsizez" is deprecated: Feature not supported
# WARNING: Keyword "pmefreq" is deprecated: MTS not supported
# WARNING: Deprecated keyword "langevin" is replaced with "thermostat"
# WARNING: Deprecated keyword "langevindamping" is replaced with "thermostatDamping"
# WARNING: Keyword "energyfreq" is deprecated: Energies are now output every trajectoryFreq steps
$
$# Forcefield configuration
$
$ parameters parameters
$
$# Initial State
$
$ structure structure.psf
$ coordinates structure.pdb
$ temperature 300.00 # K
$ celldimension 62.230000 62.230000 62.230000 # A
$
$# Output
$
$ trajectoryFile output.xtc
$ trajectoryFreq 25000
$
$# Electrostatics
$
$ PME on
$ cutoff 9.00 # A
$ switching on
$ switchDist 7.50 # A
$ implicit off
$
$# Temperature Control
$
$ thermostat on
$ thermostatTemp 298.15 # K
$ thermostatDamping 1.00 # /ps
$
$# Pressure Control
$
$ barostat off
$ barostatPressure 1.0000 # bar
$ useFlexibleCell off
$ useConstantArea off
$ useConstantRatio off
$
$# Integration
$
$ timestep 4.00 # fs
$
$# External forces
$
$
$# Restraints
$
$
$# Run Configuration
$
$ restart off
$ run 250000
# Topology reports 23558 atoms
# Initializing engine
# Version: 7.3.1
# WARNING: overriding the plugin path to /var/lib/boinc-client/slots/40 with ACEMD_PLUGIN_DIR
# Plugin directory: /var/lib/boinc-client/slots/40
# Loaded plugins
# libOpenMMCUDA
# libOpenMMPME
# libOpenMMOpenCL
# libOpenMMCPU
# libOpenMMCudaCompiler
# Available platforms
# CUDA
# OpenCL
# CPU
#
# Bonded interactions
# Harmonic bond interactions
# Number of terms: 16569
# Harmonic angle interactions
# Number of terms: 11584
# Urey-Bradley interactions
# Number of terms: 2117
# Proper dihedral interations
# Number of terms: 5621
# Number of skipped terms: 1379
# NOTE: the skipped terms have zero force constants
# Improper dihedral interations
# Number of terms: 408
# Number of skipped terms: 10
# NOTE: the skipped terms have zero force constants
# CMAP interactions
# Number of terms: 0
# NOTE: CMAP interations skipped
#
# Non-bonded interactions
# Number of exclusions: 34709
# Lennard-Jones terms
# Cutoff distance: 9.000 A
# Switching distance: 7.500 A
# Coulombic (PME) term
# Ewald tolerance: 0.000500
# No NBFIX
# No implicit solvent
#
# Constraining hydrogen (X-H) bonds
# Number of constrained bonds: 15267
# Making water molecules rigid
# Number of water molecules: 7023
# Number of constraints: 22290
#
# Repartitioning hydrogen atom mass
# New hydrogen mass: 4.032 au
# Number of hydrogen atoms: 15267
#
# Creating simulation system
# Number of particles: 23558
# Number of degrees of freedom 48381
# Periodic box size: 62.230 62.230 62.230 A
#
# Using Langevin integrator (with temperature control)
# Thermostat target temperature: 298.15 K
# Thermostat friction coeficient: 1.00 ps^-1
#

If somebody can post or upload the three components of a test workunit specification:

* <app_version>
* <workunit>
* <result>

all from client_state.xml - make sure you get the right (latest) version of <app_version>, there will be several of them - I can proofread that there are no bugs in the BOINC deployment of the app files. This one could be a problem with the version renaming or copying.

Thanks. The context was

libcudart.so.8.0 => not found
libcufft.so.8.0 => not found

So right off the bat, the app had no chance of succeeding when it can't find its own downloaded libcudart.so.8.0 and libcufft.so.8.0 files in the project directory.

If anybody is so inclined, can they try to run the boinc client manually with the --exit_after_finish flag, so the slot directory is preserved on failure?


Thanks

I thought that all the tasks I had downloaded had failed but I see I have one host that has been successfully processing the acemd3 tasks.

But I just aborted the cache thinking all the hosts were unsuccessful. Oops.

Now to try and compare what is different about that machine compared to the rest.

I believe the difference is that at one time I had installed the cuda toolkit on that host and then removed it long in the past.

Anybody successfully run the new acemd3 app on a Turing card yet? I just realized that I still had a gpu_exclude for my Turing card on the host that had been successfully processing tasks. I somehow had skipped over removing the exclusion from that machine while I had done so on all the other hosts with Turing cards.

Could this be the reason that app fails?

I see that there is a new version 2.02, which I just tried on my GTX 1070 (Ubuntu 16.04.6). I just use the Ubuntu repository driver, which is 396.54 (proprietary), without any toolbox that I know of.

It failed immediately.

GPUGRID 2.02 New version of ACEMD (cuda80) a67-TONI_TEST8-2-3-RND3156_0 00:00:03 (-) 0.00 100.000 - 6/10/2019 2:42:16 PM 0.985C + 1NV Computation error 0.00 MB i7-4790-G

Anybody successfully run the new acemd3 app on a Turing card yet? I just realized that I still had a gpu_exclude for my Turing card on the host that had been successfully processing tasks. I somehow had skipped over removing the exclusion from that machine while I had done so on all the other hosts with Turing cards.

Could this be the reason that app fails?

I am also seeing failures due to the acemd binary not finding some libs:

Anybody successfully run the new acemd3 app on a Turing card yet? I just realized that I still had a gpu_exclude for my Turing card on the host that had been successfully processing tasks. I somehow had skipped over removing the exclusion from that machine while I had done so on all the other hosts with Turing cards.

Could this be the reason that app fails?

I think the plan is to get a stable acemd3 app running on legacy hardware and then release a beta for turing cards.

@jim1348, I get the same error on one of my machines with dual GTX 1080 cards.

Anybody successfully run the new acemd3 app on a Turing card yet? I just realized that I still had a gpu_exclude for my Turing card on the host that had been successfully processing tasks. I somehow had skipped over removing the exclusion from that machine while I had done so on all the other hosts with Turing cards.

Could this be the reason that app fails?

I think the plan is to get a stable acemd3 app running on legacy hardware and then release a beta for turing cards.

@jim1348, I get the same error on one of my machines with dual GTX 1080 cards.

OK, that is a very different comprehension that I have for the wrapper app. I thought it was to allow use of the Turing cards.

I guess I should put the gpu_exclude back in play for the hosts that failed the tasks.

Thanks for the edification.

[Edit]This is the error for trying to run on a Turing card.

<core_client_version>7.15.0</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
12:04:16 (22587): wrapper (7.7.26016): starting
12:04:16 (22587): wrapper (7.7.26016): starting
12:04:16 (22587): wrapper: running acemd3 (--boinc input --device 0)
# Engine failed: Error compiling program: nvrtc: error: invalid value for --gpu-architecture (-arch)

12:04:17 (22587): acemd3 exited; CPU time 0.164594
12:04:17 (22587): app exit status: 0x1
12:04:17 (22587): called boinc_finish(195)

</stderr_txt>
]]>

I completed one while 5 others had errors.
https://www.gpugrid.net/workunit.php?wuid=16520276

nvcc -V results
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2017 NVIDIA Corporation
Built on Fri_Nov__3_21:07:56_CDT_2017
Cuda compilation tools, release 9.1, V9.1.85

I think I should take one of the hosts that fail the app and install the cuda toolkit and see if it changes anything.

I know that Toni said the toolkit is unnecessary supposedly, but it might show something.

It won't hurt. One PC of mine with 1070/1070Ti works and another with 1080Ti doesn't. Both have the same nvcc -V results.

v2.03 works on both my computers!

What was the change between v2.02 and v2.03 if you don't mind me asking. :)

The progress bar works.
I didn't try pause/resume.

My host that failed on 2.02 now works with 2.03.

Great work

Well done Toni!

Much appreciated!

Toni Tests looking good on my machines, even on the 2080Ti!

Two hosts have received 2.04 and processed on the 2080 along with a 1070 successfully.

The other host is still on 2.03 I assume because I had the gpu_exclude running on it for the 2080 card. Removing the gpu_exclude for all hosts now.

It looks like we have a winner.

App 2.04 should support cuda10, if the scheduler collaborates.

From what we've seen over at Seti with our special app, the CUDA9 application running the 410 series driver is fastest for Pascal cards. Of course if you have a Turing card, you are forced into using the 418 series drivers with CUDA10.

Not sure if the same observation applies here at GPUGrid with its apps.

My guess and suggestion would be to just stand pat until somebody runs both the 2.03 and 2.04 apps against the same tasks in the benchmark utilities and proves otherwise.

I assume all the kit 'n kaboodle of files needed for the wrapper would have to be put into the benchmark tool. Not as simple as testing on Seti tasks.

Yes, it is a bit premature. I will await for the final app. Thanks for the input.

Yes, it is a bit premature. I will await for the final app. Thanks for the input.

On one host with both a 2080 and 1070, the 2080 ran the test WU in 125 seconds versus 230 seconds with the 1070. Both on the 2.04 app.

I might be a little bit confused: Any time line when real production task of the 2.04 app will be supplied to Linux hosts? In the next days, weeks, months? I changed my BOINC settings to accommodate and give GPUGRID tasks the preference, however if there are no tasks available in the near future, I would like to change the settings again to better serve other projects.

Toni please answer as soon and as specific as possible. Thanks!

We'll be transitioning gradually.

Toni, did you discover a cutoff limit for driver version you should not go below or you will increase your errors?

The most recent driver in the linux mint 19.1 repository is 390.116 (cuda 9).

You can get 4xx.xx proprietary drivers that support cuda 10 at this site by adding the PPA to your system. https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

Or you can download and install the drivers from nvidia directly. The latter is a little more adventurous for linux users.

I was mainly asking if it was necessary to run the latest drivers like the 430 series. You have to run at least the 418 series to be compatible with Turing.

I have used the graphics-drivers ppa for years now. I always recommend that method for installing Nvidia drivers to Linux noobs as easiest.

The most recent driver in the linux mint 19.1 repository is 390.116 (cuda 9).

I agree, best to avoid the toolkit unless you need it to develop apps. They recently changed the way the toolkit handles the video drivers. You can get yourself in trouble with the toolkit installing its version of the graphics drivers alongside your runtime version of CUDA with the usual graphics drivers installation.

I have been reading this document which I just discovered.

https://docs.nvidia.com/deploy/cuda-compatibility/

Lots of good info about driver versions and CUDA version support among the various generations of cards.

To summarize: acemd3 cuda80 and cuda100 are very satisfactory for linux. Very few failures, fast, blazing on rtx 2080. The win app will need work though.

There is definitely NO NEED TO install the CUDA toolkit for GPUGRID. It's not required, so don't complicate your set-up unnecessarily.

You just will want to have not-too-old drivers, however.

My guess not until Toni can figure out how to get the acemd3 Windows app working.

I hope the CUDA 9.2 drivers are good enough. When I tried to update to the latest CUDA 10.x drivers for my GTX 1070 from the Nvidia repository (Ubuntu 16.04.6), it blanked out the desktop. BOINC still worked, but I had to reload the OS to get the desktop back. I suppose something in the X.Org server (if that is what they use) does not like the latest drivers, though the Linux experts will need to fix it.

I hope the CUDA 9.2 drivers are good enough. When I tried to update to the latest CUDA 10.x drivers for my GTX 1070 from the Nvidia repository (Ubuntu 16.04.6), it blanked out the desktop. BOINC still worked, but I had to reload the OS to get the desktop back. I suppose something in the X.Org server (if that is what they use) does not like the latest drivers, though the Linux experts will need to fix it.

I still think using the graphics-drivers ppa is the easiest solution for obtaining and installing the drivers. As long as you have a debian distro newer than 14, you are good to go with the drivers right up to the current 430 series.

Just add the ppa to your sources and make your choice of which driver you want. Either install from the command line or install from the Software Updater.

https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

I have a task that appears to be misbehaving.



Application
Long runs (8-12 hours on fastest card) 9.22 (cuda80)
Name
e82s77_e68s28p1f217-PABLO_v3Q9UM73_MOR_14_IDP-0-2-RND6181
State
Running
Received
6/9/2019 3:14:13 AM
Report deadline
6/14/2019 3:14:14 AM
Resources
0.991 CPUs + 1 NVIDIA GPU
Estimated computation size
5,000,000 GFLOPs
CPU time
00:54:04
CPU time since checkpoint
00:00:01
Elapsed time
20:13:55
Estimated time remaining
---
Fraction done
73.853%
Virtual memory size
1.11 GB
Working set size
359.47 MB
Directory
slots/0
Process ID
3684
Progress rate
3.600% per hour
Executable
acemd-922-80.exe

The progess percentage has been frozen, or at least nearly frozen, for at least the last 10 hours.

The estimated remaining time has been --- for at least the last 10 hours.

How long should I let it run before aborting it? Is there anything else I should do to make it run properly?

http://www.gpugrid.net/workunit.php?wuid=16519044

Try to suspend and restart it. Or kill it.

Any plans of sending out more beta tasks for Linux? I'm eager to try it on my 2070 and 1660 Ti.

This thread has been very quiet since the last posting by Toni. I should hope that means he is quietly working hard on polishing off the new apps for both Linux and Windows. And soon that new work with new apps will become available.

to make a bootable win10 disk i use wintousb software, with win10 iso image.
then unplug internal disk, setup the bios in a proper way to boot from usb disk and you go.

or you can use ultraiso, write image disk and then usb hdd+ option to install iso-image on disk or usb

Below is a link to a step by step guide with screenshots and links to the appropriate software to make the USB.
You will need an educational or enterprise license of Win10 to run it.

https://au.pcmag.com/windows-10-1/46896/how-to-run-windows-10-from-a-usb-drive

I would consider purchasing a 250 GB SSD drive and setting up a Win/linux dual boot option using grub on one of your linux workstations. You'd still have a buy a license for Win10 pro. Building a "cheap" dedicated Win10 system would be even better. I would think Win10 on a USB stick would a be painful experience (slow).

Erik was referring to Win 10 installation from USB. Supposedly Win 10 can also boot from a stick - however, this requires certified sticks. I don't have any further experience with that.

MrS

I would think Win10 on a USB stick would a be painful experience (slow).

consider purchasing a 250 GB SSD drive and setting up a Win/linux dual boot option

I would think Win10 on a USB stick would a be painful experience (slow).

Agreed.

consider purchasing a 250 GB SSD drive and setting up a Win/linux dual boot option

+1
Due to the Win10 licensing model, the USB stick would not be portable between host PCs. It would go to setup mode every time it is plugged into a different host PC, and another Win 10 license would be needed.

it is portabke between all host machines.

I am not sure if this was an anomaly or not but I did get a "usb windows 10" stick to boot and be activated.

Background: I bought several used HPZ-400 motherboards on eBay. They are all licensed for windows 7 due to having an SLIC2.1 in the bios. The activation code for windows 7 pro is the same generic HP windows 7 pro key so all these systems can legally run win7pro as the license is bound to the system and the key is listed all over the internet.

I installed windows 7 on 2 mombos and did that still free upgrade to 10. According to one of the Microsoft MVP'ers it was not necessary to activate on windows 7, I could have put in 10 and simply used my windows 7 HP key. While I did not try that I did install 7 pro and upgraded to 10 pro using a USB stick on mombo #2. I then put that USB stick in the 3rd HPZ-400 mombo and was able to activate it. However, I had named the 3rd system the same name as the 2nd and I had registered the 2nd one on Microsoft's web site as one of my devices. Later I changed the name of that 2nd one and all three were working just fine wind10pro.

I suspect if the motherboard has an SLIC2.1 license then a USB win10 stick can boot and be activated using the generic win7pro license from the original vendor (dell, hp, etc)

Just a guess.

Any word on the status of acemd3? Last I saw there was a hold up due to a Windows (10?) issue.

Haven't heard a peep either. Still waiting on Windows app I guess.

Toni is trying out a new acemd3 application. 2.04 works as well as the previous 2.03 version. Still having issues getting the Windows app to work consistently.

He has a new thread. https://www.gpugrid.net/forum_thread.php?id=4955

We are still dreaming of Linux app :з

We are still dreaming of Linux app :з

We have an application working to new application but forced to wait on win. Not fair when our old application expired.

Backup project very happy but my goal with gpus are lost.
(linux user)

Hi,

Will the new version support Titan V CUDA 7.0?

Thanks

Hi,

Will the new version support Titan V CUDA 7.0?

Thanks

I setup for some acemd3 if any WU drop then I'll see what happens