I deployed the new app, which now requires cuda 11.2 and hopefully support all the latest cards. Touching the cuda versions is always a nightmare in boinc scheduler so expect problems.

YES! Thank you so much!

---

I noticed the plan class is listed as "cuda1121" on the Applications page. is this a typo? will it cause any issues with getting work or running the application?

also you might need to put a cap (maybe compute capability or something) on the project server side to prevent the CUDA10.0 app from being sent to Ampere hosts. currently we saw many errors because the CUDA10.0 app was still sent to Ampere hosts. there should be a way to make sure Ampere hosts only get the 11.2 app and not try to use the cuda 10 app.

---

Great news! So far it's only Linux, right?

MrS

---

Scanning for our furry friends since Jan 2002

So far.

Just so people are aware, CUDA 11.2 (I assume the "1121" means CUDA 11.2.1 "update 1") means you need at least driver 460.32 on Linux.

---

Can someone confirm that the Linux cuda100 app is still sent out (and likely fail)?

T

Can someone confirm that the Linux cuda100 app is still sent out (and likely fail)?

T

is this the reason that the Linux tasks have been failing recently? they need this new app? did you remove the Linux cuda100 app?

---

I just got a couple tasks on my RTX 3080 Ti host, it got the new app. it failed in 2 seconds. it looks like you're missing a file, or you forgot to statically link boost into the app:

16:50:34 (15968): wrapper (7.7.26016): starting
16:50:34 (15968): wrapper (7.7.26016): starting
16:50:34 (15968): wrapper: running acemd3 (--boinc input --device 0)
acemd3: error while loading shared libraries: libboost_filesystem.so.1.74.0: cannot open shared object file: No such file or directory
16:50:35 (15968): acemd3 exited; CPU time 0.000360
16:50:35 (15968): app exit status: 0x7f
16:50:35 (15968): called boinc_finish(195)

https://www.gpugrid.net/result.php?resultid=32631384

but it's promising that I didnt get the "invalid architecture" error

---

Looks like Ubuntu 20.04.2 LTS has libboost-all-dev 1.71 installed.

I remember that Gridcoin needs libboost-all-dev 1.74 installed now also when building.

That is in 21.04.

[Edit]
Theoretically yes AFAIK anything about wrapper containers.

I just wonder if you installed the latest 1.74 libboost-all-dev environment that the tasks wouldn't fail.

https://www.boost.org/users/history/version_1_74_0.html

i think these are sandboxed in the wrapper. so packages on the system in theory shouldnt matter right?

---

Just failed a couple more acemd3 tasks. What a waste . . . . as hard as they are to snag.

Just failed a couple more acemd3 tasks. What a waste . . . . as hard as they are to snag.

did you get the new app? do you have that newer version of boost installed?

---

No I just have the normal CUDA 10.0 app installed. I am just investigating what would be needed to install the missing libraries.

Great to see this progress as prices of GPUs are beginning to fall and Ampere GPUs are currently dominating the market availability. I hope China's Ban on mining becomes a budgetary boon for crunchers and gamers worldwide.

The Amperes should eventually expedite this project considerably.

---

"Together we crunch
To check out a hunch
And wish all our credit
Could just buy us lunch"

Piasa Tribe - Illini Nation

No I just have the normal CUDA 10.0 app installed. I am just investigating what would be needed to install the missing libraries.

looks like you're actually getting the new app now: http://www.gpugrid.net/result.php?resultid=32631755

---

No I just have the normal CUDA 10.0 app installed. I am just investigating what would be needed to install the missing libraries.

looks like you're actually getting the new app now: http://www.gpugrid.net/result.php?resultid=32631755

Huh, hadn't noticed.

So maybe the New version of ACEMD v2.12 (cuda1121) is going to be the default app even for the older cards.

I think you’ll only get 11.2 app if you have a driver that’s compatible. Greater than 460.32. Just my guess. I’ll need to see if systems with and older driver will still get the cuda 100 app

Edit: answering my own question. I guess the driver being reported doesn’t factor into the app selection anymore. My systems reporting an older driver still received the new app. So it won’t prevent the app from being send to someone without a new enough driver.

---

I'm still trying to figure out the best way to distribute the app. The current way has hard-coded minimum-maximum driver versions for each CUDA version and it's too cumbersome to maintain.

Suggestions are welcome. The server knows the client's CUDA version and driver version, as well as the app's CUDA plan class.

I'm still trying to figure out the best way to distribute the app. The current way has hard-coded minimum-maximum driver versions for each CUDA version and it's too cumbersome to maintain.

Suggestions are welcome. The server knows the client's CUDA version and driver version, as well as the app's CUDA plan class.

Here is an idea:

How about distribution by card type? That would exclude the really slow cards, like 740M.

BTW: What driver version do we need for this?