Stderr output
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -59 (0xffffffc5)</message>
<stderr_txt>
# GPU [GeForce RTX 2080 Ti] Platform [Windows] Rev [3212] VERSION [80]
# SWAN Device 0 :
# Name : GeForce RTX 2080 Ti
# ECC : Disabled
# Global mem : 11264MB
# Capability : 7.5
# PCI ID : 0000:42:00.0
# Device clock : 1650MHz
# Memory clock : 7000MHz
# Memory width : 352bit
# Driver version : r431_31 : 43136
#SWAN: FATAL: cannot find image for module [.nonbonded.cu.] for device version 750

</stderr_txt>
]]>

Not supported yet

That would explain it, such a new card out eh

They are working on new software right now, the Linux users are all down too because of an expired license, so I would imagine it wouldn't be to long (that's a big portion of crunchers).

2080ti relase September 27, 2018
[url]https://en.wikipedia.org/wiki/GeForce_20_series
"new" ))
on milkyway boinc project is still best price/day rac 2012 year, old 7970 ati/amd gf card
detto einstein home, only amd card are reliable make some progress on project
nvidia hw tech is from another space ,humans dont know use ))))
[/url]

We Linux users are being held back by the Windows users. Our Turing compatible science application has been ready to use for months. We don't have access to it because we assume the scientists won't release it till they have figured out how to make and release an equivalent Windows application so there will be parity.

I'm getting tired of the wait. They should just release the Linux application so that 38% of the GPUGrid.net user base can start producing work again. Let the Windows users spin their wheels for a change for a couple of months like we have had to do since February.

They should have just renewed the license and worked on this in the background.

They should have just renewed the license and worked on this in the background.

+ 1

We Linux users are being held back by the Windows users. Our Turing compatible science application has been ready to use for months. We don't have access to it because we assume the scientists won't release it till they have figured out how to make and release an equivalent Windows application so there will be parity.

I'm getting tired of the wait. They should just release the Linux application so that 38% of the GPUGrid.net user base can start producing work again. Let the Windows users spin their wheels for a change for a couple of months like we have had to do since February.

While I would like to use my Turing cards crunching for GPUGrid instead of SETI@home (under Linux) just like you, I think this is not as easily done from the project's side as you imply: The new app needs a wrapper, while the old app doesn't. That means the work generated for (and done by) the old app (most probably) won't work with the new app. So not just a different queue is required for the new app, but it should be managed separately which requires manpower which this project is lacking of.

A wrapper is just that. A wrapper around the science app. The wrapper does not and should not affect the workings of the science app. It is the same science app we have used in the past only rewritten to recognize the Turing cards. The result files for the old expired license Linux app should be exactly the same as the new wrapped app.

One of the reasons for going with the wrapper app is to get away from the micro-management of the science app for things like having to renew the license every year. It is also easier to deploy across platforms according to the wrapper documentation.

It is the same science app we have used in the past only rewritten to recognize the Turing cards.

No, it's a completely different app. See this post.

Not a good time to be picked as Formula Boinc Sprint then, no AMD and not even any cpu tasks :(

It is the same science app we have used in the past only rewritten to recognize the Turing cards.

No, it's a completely different app. See this post.

OK, conceded. I thought the previous app was acemd3 also.