As my computers are finishing WU's new units are NOT being sent.
Is there a problem as the server status suggests over 200 long WU's are ready to send.

Same here. It appears to have happened due to the development of the new ACEMD3 app.

My Win machines (Pascal GPU) with 3xx drivers can download ok, my Win Machines (Pascal GPU) with 4xx drivers cannot.

I have downgraded one Win machine from 4xx driver to 3xx driver, and it can now download tasks.

hopefully only a temporary glitch.

App 2.04 should support cuda10, if the scheduler collaborates.
Expect hiccups...

T

Ouch. It must be because of the conditions for offering cuda100 vs cuda80. I promote "new" hosts to cuda100 but there is no such app for acemd2 (there is for acemd3).

Will try to find a solution.

t

I see 844 tasks on server-status but nothing for the GPUs my computers on Windows 10 !?

Yes, new tasks ready to crunch !

Please check if solved

Yes, new tasks ready to crunch !

All hosts now with tasks.
Thanks everyone :)

It looks like cuda 6.5 is no longer available for Kepler cards, with Windows 7 and 3xx.xx drivers.


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


Is this by accident or intent?

Hi guys, I have Linux system with Nvidia Pascal graphics card, Driver 418.56
Can't get any new tasks when was trying to connect this week.

---

Update:
Apparently in Ubuntu 18.04 you have to install CUDA separately in addition to drivers.

Was able to install nvcc from default repository and after restart started to get tasks: "New version of ACEMD 2.04 (cuda100)".

It's not you -- the tasks you received are 'test tasks' testing a new version of the Linux application. The regular/long work units right now are only for Windows hosts until the new application is deployed. (The new app is for Linux hosts at the moment.)

http://www.gpugrid.net/forum_thread.php?id=4935

As my computers are finishing WU's new units are NOT being sent.
Is there a problem as the server status suggests over 200 long WU's are ready to send.

Might be fixed. Please check.

391 isn't that old.
Sometimes drivers get slower as they get bigger.

A GTX 690 is compute capability 3.0. Driver versions 391.xx are cuda 9 capable. Upgrading the driver to 4xx.xx will be cuda 10 capable.

Maybe I'm wrong, but I think Cuda 8,9 and 10 will work on CC 3.0 cards like the GTX 690 as along as you enable CC 3.x support in the makefile.

https://en.wikipedia.org/wiki/CUDA

Now I was getting this this on windows 10 machine with Maxwell cards:


06/08/2019 8:51:33 AM | GPUGRID | Requesting new tasks for CPU and NVIDIA GPU
06/08/2019 8:51:34 AM | GPUGRID | Scheduler request completed: got 0 new tasks
06/08/2019 8:51:34 AM | GPUGRID | No tasks sent
06/08/2019 8:51:34 AM | GPUGRID | No tasks are available for Long runs (8-12 hours on fastest card)

When long runs were still available.

Long runs (8-12 hours on fastest card) 24 2,468 2.78 (0.44 - 19.86) 663

But my Kelper card windows 7 machine, just received cuda 6.5 WUs.

Now I was getting this this on windows 10 machine with Maxwell cards:


06/08/2019 8:51:33 AM | GPUGRID | Requesting new tasks for CPU and NVIDIA GPU
06/08/2019 8:51:34 AM | GPUGRID | Scheduler request completed: got 0 new tasks
06/08/2019 8:51:34 AM | GPUGRID | No tasks sent
06/08/2019 8:51:34 AM | GPUGRID | No tasks are available for Long runs (8-12 hours on fastest card)

When long runs were still available.

Long runs (8-12 hours on fastest card) 24 2,468 2.78 (0.44 - 19.86) 663

But my Kelper card windows 7 machine, just received cuda 6.5 WUs.

I had raised the minimum driver version required for cuda80 in order to avoid the previous problem. Now I reverted the change. Still, this level of ad-hocness is not sustainable; the next app may need updated drivers.

.Just, tell us what we need to upgrade, and which cards will be supported and not supported.

Now I was getting this this on windows 10 machine with Maxwell cards:


06/08/2019 8:51:33 AM | GPUGRID | Requesting new tasks for CPU and NVIDIA GPU
06/08/2019 8:51:34 AM | GPUGRID | Scheduler request completed: got 0 new tasks
06/08/2019 8:51:34 AM | GPUGRID | No tasks sent
06/08/2019 8:51:34 AM | GPUGRID | No tasks are available for Long runs (8-12 hours on fastest card)

When long runs were still available.

Long runs (8-12 hours on fastest card) 24 2,468 2.78 (0.44 - 19.86) 663

But my Kelper card windows 7 machine, just received cuda 6.5 WUs.

I had raised the minimum driver version required for cuda80 in order to avoid the previous problem. Now I reverted the change. Still, this level of ad-hocness is not sustainable; the next app may need updated drivers.

418 has cuda 10.1 as well as support for Turing cards
____________

Thats nice but that doesn't change anything for a CUDA80 app or older cards like the 690 mentioned above.

Unless there is a specific CUDA10 command in the new version then drivers that are older should still be supported. It's like calling something an AVX512 app and limiting to only CPUs with AVX512 even though only SSE2 is used.

It's not like people are asking for pre Kepler drivers to be supported. Just last years.

The 390 series drivers are Legacy drivers now. Minimal support. But the 390 series is still the default repository version offered in many distros.

This Nvidia document shows the changes from CUDA backwards compatibility to CUDA forwards compatibility. It also shows CUDA level compatibility with the various generations of GeForce cards.

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

I agree it may be difficult to maintain support for the older hardware in the future.

Hi:

My laptop is eagerly awaiting for some more GPUGRID work units.

COME ON DOWN!!!

Clive

Hi:

My laptop is eagerly awaiting for some more GPUGRID work units.

COME ON DOWN!!!

Clive

Hi:
Thanks for your reply.
GPUGRID.net is the only Bonic project that runs on GPU cards that I am aware of. Are there other BONIC GPU projects that I can use as a plan B?
Clive

Are there other BONIC GPU projects that I can use as a plan B?

BOINC projects list

Here are the ones I like, somewhat in order of preference and if they have work.

Milkyway@home Physical Science Astronomy Rensselaer Polytechnic Institute

Einstein@home Physical Science Astrophysics University of Wisconsin - Milwaukee (USA), Max Planck Institute for Gravitational Physics - Hanover (Germany)

SETI@home Physical Science Astrophysics, astrobiology University of California, Berkeley

Enigma@Home Mathematics, computing, and games Cryptography Independent

in a way it's too bad that GPUGRID doesn't offer enough tasks for crunching by us volunteers.
The computational power interested in and available for GPUGRID is much higher than they make use of.
Which is a pitty.

in a way it's too bad that GPUGRID doesn't offer enough tasks for crunching by us volunteers.
The computational power interested in and available for GPUGRID is much higher than they make use of.
Which is a pitty.

Just a matter of time before they are in the gridcoin graylist. I could start a poll to see if they should be kicked out but it would cost me GRC to start it. I will let someone else initiate it.

The scientists at GPUGrid don't care about Gridcoin whitelist/greylist. They are operating on their schedule that produces science in a timely manner. Just because there are limited WUs doesn't mean they aren't pumping out studies. Changing GPUGrid to the greylist would accomplish nothing.

Just a matter of time before they are in the gridcoin graylist. I could start a poll to see if they should be kicked out but it would cost me GRC to start it. I will let someone else initiate it.

This is quite futile to threaten this project with putting it on the graylist at GridCoin. This wouldn't result in plenty of workunits. As of yet I would vote against that, though it would cost me some GRC. Please be patient.