Message boards : Number crunching : No WU's being sent
Author | Message |
---|---|
As my computers are finishing WU's new units are NOT being sent. | |
ID: 52031 | Rating: 0 | rate:
![]() ![]() ![]() | |
Same here. It appears to have happened due to the development of the new ACEMD3 app. | |
ID: 52035 | Rating: 0 | rate:
![]() ![]() ![]() | |
App 2.04 should support cuda10, if the scheduler collaborates. | |
ID: 52036 | Rating: 0 | rate:
![]() ![]() ![]() | |
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). | |
ID: 52037 | Rating: 0 | rate:
![]() ![]() ![]() | |
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). That's easy: create a CUDA10 Windows app. :) | |
ID: 52038 | Rating: 0 | rate:
![]() ![]() ![]() | |
Please check if solved | |
ID: 52039 | Rating: 0 | rate:
![]() ![]() ![]() | |
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). We'll probably do it, but for acemd3. In the meantime, acemd2 should not stop working. | |
ID: 52040 | Rating: 0 | rate:
![]() ![]() ![]() | |
I see 844 tasks on server-status but nothing for the GPUs my computers on Windows 10 !? | |
ID: 52041 | Rating: 0 | rate:
![]() ![]() ![]() | |
Please check if solved | |
ID: 52042 | Rating: 0 | rate:
![]() ![]() ![]() | |
Yes, new tasks ready to crunch ! | |
ID: 52043 | Rating: 0 | rate:
![]() ![]() ![]() | |
My CUDA10/Windows 10 host received 2 CUDA8.0 tasks at 10:08 CET (08:08 UTC)Please check if solvedYes, new tasks ready to crunch ! | |
ID: 52044 | Rating: 0 | rate:
![]() ![]() ![]() | |
:) | |
ID: 52045 | Rating: 0 | rate:
![]() ![]() ![]() | |
All hosts now with tasks. | |
ID: 52046 | Rating: 0 | rate:
![]() ![]() ![]() | |
It looks like cuda 6.5 is no longer available for Kepler cards, with Windows 7 and 3xx.xx drivers. | |
ID: 52047 | Rating: 0 | rate:
![]() ![]() ![]() | |
Might be fixed. Please check. | |
ID: 52048 | Rating: 0 | rate:
![]() ![]() ![]() | |
Hi guys, I have Linux system with Nvidia Pascal graphics card, Driver 418.56 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 Hope to get some long runs too --- Update2 It didn't last for long, got only 6 tasks and silence again, it's really confusing to figure out if something wrong on user side or the project is just being picky :) | |
ID: 52049 | Rating: 0 | rate:
![]() ![]() ![]() | |
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.) | |
ID: 52050 | Rating: 0 | rate:
![]() ![]() ![]() | |
As my computers are finishing WU's new units are NOT being sent. ok, thanks for clarification ! | |
ID: 52052 | Rating: 0 | rate:
![]() ![]() ![]() | |
Might be fixed. Please check. It's not fixed. http://www.gpugrid.net/result.php?resultid=20990388 | |
ID: 52055 | Rating: 0 | rate:
![]() ![]() ![]() | |
Might be fixed. Please check. Made yet another attempt. Is there a reason for not upgrading the driver? Supporting old versions is really a problem. | |
ID: 52056 | Rating: 0 | rate:
![]() ![]() ![]() | |
391 isn't that old. | |
ID: 52057 | Rating: 0 | rate:
![]() ![]() ![]() | |
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. CUDA SDK 6.5 support for compute capability 1.1 – 5.x (Tesla, Fermi, Kepler, Maxwell). Last version with support for compute capability 1.x (Tesla)
CUDA SDK 7.0 – 7.5 support for compute capability 2.0 – 5.x (Fermi, Kepler, Maxwell)
CUDA SDK 8.0 support for compute capability 2.0 – 6.x (Fermi, Kepler, Maxwell, Pascal). Last version with support for compute capability 2.x (Fermi)
CUDA SDK 9.0 – 9.2 support for compute capability 3.0 – 7.2 (Kepler, Maxwell, Pascal, Volta)
CUDA SDK 10.0 – 10.1 support for compute capability 3.0 – 7.5 (Kepler, Maxwell, Pascal, Volta, Turing) | |
ID: 52058 | Rating: 0 | rate:
![]() ![]() ![]() | |
Now I was getting this this on windows 10 machine with Maxwell cards: | |
ID: 52059 | Rating: 0 | rate:
![]() ![]() ![]() | |
Now I was getting this this on windows 10 machine with Maxwell cards: 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. | |
ID: 52060 | Rating: 0 | rate:
![]() ![]() ![]() | |
Now I was getting this this on windows 10 machine with Maxwell cards: It seems to be working well, right now. Both my machines received WUs. Just, tell us what we need to upgrade, and which cards will be supported and not supported. | |
ID: 52061 | Rating: 0 | rate:
![]() ![]() ![]() | |
.Just, tell us what we need to upgrade, and which cards will be supported and not supported. Yes please. I have 2 machines I converted back to windows after the linux issue. But I haven't updated the drivers as they were working. If there is a minimum driver version that you would require please let us know and we can make that happen. On my linux machines I run the latest drivers as my other project requires cuda 10.1 to run on them. ____________ ![]() ![]() | |
ID: 52064 | Rating: 0 | rate:
![]() ![]() ![]() | |
Now I was getting this this on windows 10 machine with Maxwell cards: What is special with 4xx drivers? | |
ID: 52065 | Rating: 0 | rate:
![]() ![]() ![]() | |
418 has cuda 10.1 as well as support for Turing cards | |
ID: 52068 | Rating: 0 | rate:
![]() ![]() ![]() | |
Thats nice but that doesn't change anything for a CUDA80 app or older cards like the 690 mentioned above. | |
ID: 52069 | Rating: 0 | rate:
![]() ![]() ![]() | |
The 390 series drivers are Legacy drivers now. Minimal support. But the 390 series is still the default repository version offered in many distros. | |
ID: 52070 | Rating: 0 | rate:
![]() ![]() ![]() | |
Hi: | |
ID: 52781 | Rating: 0 | rate:
![]() ![]() ![]() | |
Hi: Hi, as a lot of us, you need an alternative project (plane B) to satisfy your Nvidia gpu cards. Be patient. K. ____________ Dreams do not always come true. But not because they are too big or impossible. Why did we stop believing. (Martin Luther King) | |
ID: 52788 | Rating: 0 | rate:
![]() ![]() ![]() | |
Hi: | |
ID: 52789 | Rating: 0 | rate:
![]() ![]() ![]() | |
Are there other BONIC GPU projects that I can use as a plan B? yes, there are. Seti@Home, MooWrapper, Einstein, and several more. Just look up the BOINC projects list, there is the pertinent information for each of the projects. | |
ID: 52790 | Rating: 0 | rate:
![]() ![]() ![]() | |
ID: 52791 | Rating: 0 | rate:
![]() ![]() ![]() | |
Here are the ones I like, somewhat in order of preference and if they have work. | |
ID: 52805 | Rating: 0 | rate:
![]() ![]() ![]() | |
in a way it's too bad that GPUGRID doesn't offer enough tasks for crunching by us volunteers. | |
ID: 52806 | Rating: 0 | rate:
![]() ![]() ![]() | |
in a way it's too bad that GPUGRID doesn't offer enough tasks for crunching by us volunteers. I used to have one and occasionally two waiting work units for every long or short gpugrid WU. Now all I have are Einstein. 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. | |
ID: 52809 | Rating: 0 | rate:
![]() ![]() ![]() | |
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. | |
ID: 52811 | Rating: 0 | rate:
![]() ![]() ![]() | |
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. | |
ID: 52812 | Rating: 0 | rate:
![]() ![]() ![]() | |
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. Squeaky wheel is the one that gets greased. I now have every GPU running a long work unit and another long one in the queue and no Einstein anywhere. | |
ID: 52813 | Rating: 0 | rate:
![]() ![]() ![]() | |
Message boards : Number crunching : No WU's being sent