turbokrist - The first ever GPU accelerated Krist miner!

At long last, I am releasing my latest project, turbokrist, to the public! It is a GPU accelerated Krist miner - the first one ever, to my knowledge. It uses OpenCL to mine at incredibly high speeds on graphics cards.


This screenshot is from mining on a XFX R9 390 - double dissipation edition

The code is all open source, available on GitHub under the GNU GPL v3.

Before you go and try to use turbokrist, there's a few things you should know.

Firstly, turbokrist is still very much in beta. It is for the most part stable, but is somewhat buggy and can cause driver crashes or worse if you push it too far.

Secondly, you will need mildly good equipment to mine. The work value is going down, making it more difficult to mine. If you have old hardware, turbokrist won't magically make it easy to mine again.

Finally, turbokrist is not very easy to use right now. It will take some trial and error to find the best configuration for mining.

With this in mind, you can follow the build instructions to compile the source code. I am not currently providing compiled releases for a couple reasons.

If you enjoy turbokrist, please tip me by sending Krist to apemanzilla.kst - it wasn't easy to create this!

Credits
apemanzilla (Myself) - Started the project, wrote most of the code, and tested.
Lignum - Helped some with development, helped test and debug.
sci4me - A good portion of my hashing/mining code is ported from sci4me's SKristMiner, and I used some of his utility code. Also helped with testing.
Yevano, Lemmy, 1lann, Justyn - Helped test and find bugs.
Taras (3d6) - Created Krist.

I am getting disappointing speeds on my 970 (11-13 MH/s)

minizbot2012, on 15 February 2016 - 10:56 PM said:

I am getting disappointing speeds on my 970 (11-13 MH/s)

Chances are you're not setting the worksize high enough. Keep increasing the work size by powers of two. I was able to hit 160 MH/s on Windows on a GTX 760 using a work size of 2^20 (1048576).

apemanzilla, on 15 February 2016 - 11:02 PM said:

minizbot2012, on 15 February 2016 - 10:56 PM said:

I am getting disappointing speeds on my 970 (11-13 MH/s)

Chances are you're not setting the worksize high enough. Keep increasing the work size by powers of two. I was able to hit 160 MH/s on Windows on a GTX 760 using a work size of 2^20 (1048576).

Thar she blows 920 MH/s
edit double that number and 980 MH/s
edit I hit the GH/s

minizbot2012, on 15 February 2016 - 11:03 PM said:

apemanzilla, on 15 February 2016 - 11:02 PM said:

minizbot2012, on 15 February 2016 - 10:56 PM said:

I am getting disappointing speeds on my 970 (11-13 MH/s)

Chances are you're not setting the worksize high enough. Keep increasing the work size by powers of two. I was able to hit 160 MH/s on Windows on a GTX 760 using a work size of 2^20 (1048576).

At that number I am getting 12-13 MH/s

Let me guess, you have an Intel CPU with integrated graphics?

Try adding the -a option.

Well I run a dual gpu setup with one of those and a GTX 970, I got to to work in the GH/s

What speeds are you getting now that it's working?

~1.01-1.05 GH/s

minizbot2012, on 15 February 2016 - 11:11 PM said:

~1.01-1.05 GH/s

That's really good, you should be able to get 3+ blocks per minute with those speeds. Make sure you watch your GPU temps though - you don't want to push them beyond their limits.

temp is around 77C while its only at 38% fan speed
edit : 2^20 is about right for the GTX 970

I'm unable to compile correctly, I get a java error at the :test phase.
I reinstalled the latest Java8 version, still no go.
Here's the output of gradlew –stacktrace build 2> crashlog http://pastebin.com/DjJwzeDD

Anavrins, on 15 February 2016 - 11:53 PM said:

I'm unable to compile correctly, I get a java error at the :test phase.
I reinstalled the latest Java8 version, still no go.
Here's the output of gradlew –stacktrace build 2> crashlog http://pastebin.com/DjJwzeDD

That actually looks like a firewall error getting the test output, never seen that before… Try building with this command instead:

gradlew build -x test

This will skip the test phase, which I usually wouldn't recommend, but it will at least output a usable jar.

I got the building working, but now the jar is giving me the same error.
At this point I'll blame it on the fact that I haven't got to bake my GPU yet and I should probably do that soon :P/>.

Anavrins, on 16 February 2016 - 12:59 AM said:

I got the building working, but now the jar is giving me the same error.
At this point I'll blame it on the fact that I haven't got to bake my GPU yet and I should probably do that soon :P/>.

Wait, what? The jar should be giving you a very different exception as the exception you posted earlier is a gradle exception - and the compiled jar doesn't have anything to do with gradle. Can you post the error from running the jar?

Not compiling… Could not determine the dependencies of task ':test'

nayrnayr1, on 16 February 2016 - 02:20 AM said:

Not compiling… Could not determine the dependencies of task ':test'

Sounds like you didn't clone recursively.

Can you post the full output?

apemanzilla, on 16 February 2016 - 02:26 AM said:

nayrnayr1, on 16 February 2016 - 02:20 AM said:

Not compiling… Could not determine the dependencies of task ':test'

Sounds like you didn't clone recursively.

Can you post the full output?

Another problem.. PMed you…

apemanzilla, on 16 February 2016 - 01:04 AM said:

Anavrins, on 16 February 2016 - 12:59 AM said:

I got the building working, but now the jar is giving me the same error.
At this point I'll blame it on the fact that I haven't got to bake my GPU yet and I should probably do that soon :P/>.

Wait, what? The jar should be giving you a very different exception as the exception you posted earlier is a gradle exception - and the compiled jar doesn't have anything to do with gradle. Can you post the error from running the jar?

It actually does not give any stacktrace in the console, it basically opens a new windows saying Java as stopped working, which also happened when I was having problem with :test.
And again, I have the feeling it's something about my driver, since I don't have my usual gpu plugged in, I only have Intel's integrated graphics.

Anavrins, on 16 February 2016 - 04:02 AM said:

apemanzilla, on 16 February 2016 - 01:04 AM said:

Anavrins, on 16 February 2016 - 12:59 AM said:

I got the building working, but now the jar is giving me the same error.
At this point I'll blame it on the fact that I haven't got to bake my GPU yet and I should probably do that soon :P/>.

Wait, what? The jar should be giving you a very different exception as the exception you posted earlier is a gradle exception - and the compiled jar doesn't have anything to do with gradle. Can you post the error from running the jar?

It actually does not give any stacktrace in the console, it basically opens a new windows saying Java as stopped working, which also happened when I was having problem with :test.
And again, I have the feeling it's something about my driver, since I don't have my usual gpu plugged in, I only have Intel's integrated graphics.

Yeah, that could be why. Can you try again with a regular GPU? Also make sure your drivers are all up-to-date.

It is telling me "No main manifest attribute, in turbokrist.jar"

cyanisaac, on 16 February 2016 - 06:58 AM said:

It is telling me "No main manifest attribute, in turbokrist.jar"

That's because you're using the wrong jar. If you read the instructions, it tells you to get the jar from turbokrist-cli/build/libs/turbokrist-cli.jar. That '-cli' part is important.

My build also fails the test, the log is here: http://pastebin.com/gxp0sTPa
It works when bypassing tests, I'm getting 8 MH/s at max, i doubt that i will get much mined my first block using gpu, your are great.

Hey,

When building, it is also not working for me. When I ignore the tests, however, it sdeems to build fine. But, when I try to run the newly made .jar, it still errors. Here is the error from building:

Spoiler

com.nativelibs4java.opencl.CLBuildException: Compilation failure :  (devices: [GeForce GTX 970 (NVIDIA CUDA)])
Error in processing command line: Don't understand command line argument "Gunner\.javacl\includes\includes5942413840869230431"!
	at com.nativelibs4java.opencl.CLProgram.build(CLProgram.java:846)
	at me.apemanzilla.krist.turbokrist.opencl.ProgramBuilder.build(ProgramBuilder.java:104)
	at me.apemanzilla.jclminer.tests.OpenCLTest.setUp(OpenCLTest.java:31)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
	at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
	at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
	at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
	at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

bauen1, on 16 February 2016 - 01:20 PM said:

My build also fails the test, the log is here: http://pastebin.com/gxp0sTPa
It works when bypassing tests, I'm getting 8 MH/s at max, i doubt that i will get much mined my first block using gpu, your are great.

You need to set the work sizes and select the right devices to mine on.

SGunner2014, on 16 February 2016 - 02:05 PM said:

Hey,

When building, it is also not working for me. When I ignore the tests, however, it sdeems to build fine. But, when I try to run the newly made .jar, it still errors. Here is the error from building:

Spoiler

com.nativelibs4java.opencl.CLBuildException: Compilation failure :  (devices: [GeForce GTX 970 (NVIDIA CUDA)])
Error in processing command line: Don't understand command line argument "Gunner\.javacl\includes\includes5942413840869230431"!
	at com.nativelibs4java.opencl.CLProgram.build(CLProgram.java:846)
	at me.apemanzilla.krist.turbokrist.opencl.ProgramBuilder.build(ProgramBuilder.java:104)
	at me.apemanzilla.jclminer.tests.OpenCLTest.setUp(OpenCLTest.java:31)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
	at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
	at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
	at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
	at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Can you double check that your drivers are updated?

Thanks! Now I'm mining at ~120 MH/s on my GTX 760 :D/>

How fast is this on integrated chips?

Creator, on 16 February 2016 - 06:43 PM said:

How fast is this on integrated chips?

Don't expect much. Around 70 MH/s at most.

apemanzilla, on 16 February 2016 - 05:20 PM said:

bauen1, on 16 February 2016 - 01:20 PM said:

My build also fails the test, the log is here: http://pastebin.com/gxp0sTPa
It works when bypassing tests, I'm getting 8 MH/s at max, i doubt that i will get much mined my first block using gpu, your are great.

You need to set the work sizes and select the right devices to mine on.

SGunner2014, on 16 February 2016 - 02:05 PM said:

Hey,

When building, it is also not working for me. When I ignore the tests, however, it sdeems to build fine. But, when I try to run the newly made .jar, it still errors. Here is the error from building:

Spoiler

com.nativelibs4java.opencl.CLBuildException: Compilation failure :  (devices: [GeForce GTX 970 (NVIDIA CUDA)])
Error in processing command line: Don't understand command line argument "Gunner\.javacl\includes\includes5942413840869230431"!
	at com.nativelibs4java.opencl.CLProgram.build(CLProgram.java:846)
	at me.apemanzilla.krist.turbokrist.opencl.ProgramBuilder.build(ProgramBuilder.java:104)
	at me.apemanzilla.jclminer.tests.OpenCLTest.setUp(OpenCLTest.java:31)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
	at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
	at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
	at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
	at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Can you double check that your drivers are updated?

My drivers are currently at the latest version (361.91), running two GTX 970s in SLI.

Having trouble while building it:
> gradlew build
Fehler: Hauptklasse org.gradle.wrapper.GradleWrapperMain konnte nicht gefunden oder geladen werden

Which means the following(translated):
Error: Main class org.gradlew.wrapper.GradleWrapperMain couldn't be found or loaded.

SGunner2014, on 16 February 2016 - 07:49 PM said:

apemanzilla, on 16 February 2016 - 05:20 PM said:

bauen1, on 16 February 2016 - 01:20 PM said:

My build also fails the test, the log is here: http://pastebin.com/gxp0sTPa
It works when bypassing tests, I'm getting 8 MH/s at max, i doubt that i will get much mined my first block using gpu, your are great.

You need to set the work sizes and select the right devices to mine on.

SGunner2014, on 16 February 2016 - 02:05 PM said:

Hey,

When building, it is also not working for me. When I ignore the tests, however, it sdeems to build fine. But, when I try to run the newly made .jar, it still errors. Here is the error from building:

Spoiler

com.nativelibs4java.opencl.CLBuildException: Compilation failure :  (devices: [GeForce GTX 970 (NVIDIA CUDA)])
Error in processing command line: Don't understand command line argument "Gunner\.javacl\includes\includes5942413840869230431"!
	at com.nativelibs4java.opencl.CLProgram.build(CLProgram.java:846)
	at me.apemanzilla.krist.turbokrist.opencl.ProgramBuilder.build(ProgramBuilder.java:104)
	at me.apemanzilla.jclminer.tests.OpenCLTest.setUp(OpenCLTest.java:31)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
	at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
	at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
	at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
	at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Can you double check that your drivers are updated?

My drivers are currently at the latest version (361.91), running two GTX 970s in SLI.

What operating system and Java version?

Luca_S, on 16 February 2016 - 08:33 PM said:

Having trouble while building it:
> gradlew build
Fehler: Hauptklasse org.gradle.wrapper.GradleWrapperMain konnte nicht gefunden oder geladen werden

Which means the following(translated):
Error: Main class org.gradlew.wrapper.GradleWrapperMain couldn't be found or loaded.

Do you happen to be using a bash implementation on Windows, like cygwin? If so, please try regular command prompt instead.

apemanzilla, on 16 February 2016 - 08:53 PM said:

Do you happen to be using a bash implementation on Windows, like cygwin? If so, please try regular command prompt instead.

Just used regular command prompt. Anavrins sent me a compiled version, so the problem is solved for me.

apemanzilla, on 16 February 2016 - 08:53 PM said:

SGunner2014, on 16 February 2016 - 07:49 PM said:

apemanzilla, on 16 February 2016 - 05:20 PM said:

bauen1, on 16 February 2016 - 01:20 PM said:

My build also fails the test, the log is here: http://pastebin.com/gxp0sTPa
It works when bypassing tests, I'm getting 8 MH/s at max, i doubt that i will get much mined my first block using gpu, your are great.

You need to set the work sizes and select the right devices to mine on.

SGunner2014, on 16 February 2016 - 02:05 PM said:

Hey,

When building, it is also not working for me. When I ignore the tests, however, it sdeems to build fine. But, when I try to run the newly made .jar, it still errors. Here is the error from building:

Spoiler

com.nativelibs4java.opencl.CLBuildException: Compilation failure :  (devices: [GeForce GTX 970 (NVIDIA CUDA)])
Error in processing command line: Don't understand command line argument "Gunner\.javacl\includes\includes5942413840869230431"!
	at com.nativelibs4java.opencl.CLProgram.build(CLProgram.java:846)
	at me.apemanzilla.krist.turbokrist.opencl.ProgramBuilder.build(ProgramBuilder.java:104)
	at me.apemanzilla.jclminer.tests.OpenCLTest.setUp(OpenCLTest.java:31)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
	at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
	at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
	at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
	at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
	at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
	at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Can you double check that your drivers are updated?

My drivers are currently at the latest version (361.91), running two GTX 970s in SLI.

What operating system and Java version?

Luca_S, on 16 February 2016 - 08:33 PM said:

Having trouble while building it:
> gradlew build
Fehler: Hauptklasse org.gradle.wrapper.GradleWrapperMain konnte nicht gefunden oder geladen werden

Which means the following(translated):
Error: Main class org.gradlew.wrapper.GradleWrapperMain couldn't be found or loaded.

Do you happen to be using a bash implementation on Windows, like cygwin? If so, please try regular command prompt instead.

Windows 10, and my Java version is Java 8 Update 73

Thanks,
- Sam

SGunner2014, on 16 February 2016 - 10:20 PM said:

Windows 10, and my Java version is Java 8 Update 73

Thanks,
- Sam

Can you send me the complete output of the tests? You can find it in build/reports/tests.

Unable to set work size

Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 1
at me.apemanzilla.krist.turbokrist.cli.Launcher.main(Launcher.java:117)

PixelToast, on 17 February 2016 - 04:45 AM said:

Unable to set work size

Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 1
at me.apemanzilla.krist.turbokrist.cli.Launcher.main(Launcher.java:117)

Sorry for the cryptic error, but your -w parameters should be in the format of <deviceSignature>:<worksize> - the signature, a colon, and then the worksize. If you use multiple devices with different signatures, use semicolons to separate pairs, so it would look like <signature_one>:<worksize_one>;<signature_two>:<worksize_two>

Getting around 100MH/s with my GTX660SC. I'm actually able to get some Krist now. Thank you for making this miner!

cyanisaac, on 18 February 2016 - 04:47 AM said:

Getting around 100MH/s with my GTX660SC. I'm actually able to get some Krist now. Thank you for making this miner!

No problem! With the new changes to the work algorithm, almost everyone should be able to mine now.

May I ask why you use a custom string to byte[] function when such a function is already part of the normal string functions. I have no problem doing this:

byte[] byteArray = "Hello, World".getBytes()

superaxander, on 18 February 2016 - 06:27 AM said:

May I ask why you use a custom string to byte[] function when such a function is already part of the normal string functions. I have no problem doing this:

byte[] byteArray = "Hello, World".getBytes()

Java's String.getBytes method deals with different locales and encodings, whereas I just needed a basic, universal function. That method was actually written by sci4me as part of his Krist miner.

hmm updating my drivers to 361.91 (not while mining) and running the miner causes it to crash on start with out of resources.

minizbot2012, on 18 February 2016 - 04:31 PM said:

hmm updating my drivers to 361.91 (not while mining) and running the miner causes it to crash on start with out of resources.

Note that updating the divers will change the device signature. Run it with -l and fix the -w argument to use the new signature.

Well I already have updated the device sig, it still doesn't launch properly. (I don't launch with a batch file)

minizbot2012, on 18 February 2016 - 06:18 PM said:

Well I already have updated the device sig, it still doesn't launch properly. (I don't launch with a batch file)

Have you rebooted since the driver installation?

yes, just did, and I don't leave my computer running overnight, and I updated the driver yesterday.

minizbot2012, on 18 February 2016 - 07:47 PM said:

yes, just did, and I don't leave my computer running overnight, and I updated the driver yesterday.

Can you try decreasing the worksize a bit? Having it too high will use up all of the video memory.

value of 8 still crashes at startup, and I highly doubt VRAM would be an issue (its a 4GB card)
Adding -Xmx2G to the options of the jvm fixed this.

minizbot2012, on 19 February 2016 - 07:14 PM said:

value of 8 still crashes at startup, and I highly doubt VRAM would be an issue (its a 4GB card)
Adding -Xmx2G to the options of the jvm fixed this.

Ah, alright - I thought the error you were talking about was the video card running out of memory, not JVM :P/>

It could've gone either way the error from the JVM was indeed an OutOfResources exception, however, it is also java 8 so the old OutOfMemory could've been swapped to OutOfResources :P/>

minizbot2012, on 20 February 2016 - 12:27 AM said:

It could've gone either way the error from the JVM was indeed an OutOfResources exception, however, it is also java 8 so the old OutOfMemory could've been swapped to OutOfResources :P/>

Yeah, usually you'd see an OpenCL exception with a message similar to 'Out of resources' which is why I thought you were talking about the GPU.

I have something to tell you - And that is if you make a program please make it accessible to all users. This "turbokrist" program i cant use. Do you want to know why? Because it gave me an error when i tried to build it. Please just give me plain old .exe files and not whatever this is.

Dude, a .jar is a java exceutable. An .exe is windows only. Just run "java -jar turbokrist-cli.jar" (without the quotes of course)

FoxData, on 24 February 2016 - 04:29 PM said:

I have something to tell you - And that is if you make a program please make it accessible to all users. This "turbokrist" program i cant use. Do you want to know why? Because it gave me an error when i tried to build it. Please just give me plain old .exe files and not whatever this is.

I am not giving out binaries specifically BECAUSE it will not work on many systems and I need to know why before I can fix it. Tell me what the specific error is, and send me the logs, and I can help you.

apemanzilla, on 24 February 2016 - 09:53 PM said:

FoxData, on 24 February 2016 - 04:29 PM said:

I have something to tell you - And that is if you make a program please make it accessible to all users. This "turbokrist" program i cant use. Do you want to know why? Because it gave me an error when i tried to build it. Please just give me plain old .exe files and not whatever this is.

I am not giving out binaries specifically BECAUSE it will not work on many systems and I need to know why before I can fix it. Tell me what the specific error is, and send me the logs, and I can help you.

Hi. Here is a picture of the error i get.

Does it mean anything??

Starting Build
Settings evaluated using settings file 'C:\Users\ollies pc\Downloads\turbokrist-master\turbokrist-master\settings.gradle'.
Projects loaded. Root project using build file 'C:\Users\ollies pc\Downloads\turbokrist-master\turbokrist-master\build.gradle'.
Included projects: [root project 'turbokrist', project ':KristAPI', project ':turbokrist-cli']
Evaluating root project 'turbokrist' using build file 'C:\Users\ollies pc\Downloads\turbokrist-master\turbokrist-master\build.gradle'.
Evaluating project ':KristAPI' using build file 'C:\Users\ollies pc\Downloads\turbokrist-master\turbokrist-master\KristAPI\build.gradle'.
Evaluating project ':turbokrist-cli' using build file 'C:\Users\ollies pc\Downloads\turbokrist-master\turbokrist-master\turbokrist-cli\build.gradle'.
All projects evaluated.
Selected primary task 'build' from project :

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':compileJava'.
> Configuration with name 'default' not found.

* Try:
Run with –stacktrace option to get the stack trace. Run with –debug option to get more log output.

BUILD FAILED

Total time: 3.134 secs
Stopped 0 compiler daemon(s).

And here is the stacktrace:

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':compileJava'.
> Configuration with name 'default' not found.

* Try:
Run with –info or –debug option to get more log output.

* Exception is:
org.gradle.api.GradleException: Could not determine the dependencies of task ':compileJava'.
at org.gradle.api.internal.tasks.CachingTaskDependencyResolveContext.resolve(CachingTaskDependencyResolveContext.java:67)
at org.gradle.api.internal.tasks.CachingTaskDependencyResolveContext.getDependencies(CachingTaskDependencyResolveContext.java:55)
at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.addToTaskGraph(DefaultTaskExecutionPlan.java:139)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.addTasks(DefaultTaskGraphExecuter.java:98)
at org.gradle.execution.TaskNameResolvingBuildConfigurationAction.configure(TaskNameResolvingBuildConfigurationAction.java:47)
at org.gradle.execution.DefaultBuildConfigurationActionExecuter.configure(DefaultBuildConfigurationActionExecuter.java:48)
at org.gradle.execution.DefaultBuildConfigurationActionExecuter.access$000(DefaultBuildConfigurationActionExecuter.java:25)
at org.gradle.execution.DefaultBuildConfigurationActionExecuter$1.proceed(DefaultBuildConfigurationActionExecuter.java:54)
at org.gradle.execution.DefaultTasksBuildExecutionAction.configure(DefaultTasksBuildExecutionAction.java:44)
at org.gradle.execution.DefaultBuildConfigurationActionExecuter.configure(DefaultBuildConfigurationActionExecuter.java:48)
at org.gradle.execution.DefaultBuildConfigurationActionExecuter.access$000(DefaultBuildConfigurationActionExecuter.java:25)
at org.gradle.execution.DefaultBuildConfigurationActionExecuter$1.proceed(DefaultBuildConfigurationActionExecuter.java:54)
at org.gradle.execution.ExcludedTaskFilteringBuildConfigurationAction.configure(ExcludedTaskFilteringBuildConfigurationAction.java:47)
at org.gradle.execution.DefaultBuildConfigurationActionExecuter.configure(DefaultBuildConfigurationActionExecuter.java:48)
at org.gradle.execution.DefaultBuildConfigurationActionExecuter.select(DefaultBuildConfigurationActionExecuter.java:36)
at org.gradle.initialization.DefaultGradleLauncher$3.run(DefaultGradleLauncher.java:143)
at org.gradle.internal.Factories$1.create(Factories.java:22)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:52)
at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:140)
at org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:32)
at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:99)
at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:93)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:62)
at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:93)
at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:82)
at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:94)
at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)
at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:43)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:28)
at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:78)
at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:48)
at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:51)
at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:28)
at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:43)
at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:170)
at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:237)
at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:210)
at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)
at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:206)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
at org.gradle.launcher.Main.doAction(Main.java:33)
at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:54)
at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:35)
at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:30)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:129)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
Caused by: org.gradle.api.artifacts.UnknownConfigurationException: Configuration with name 'default' not found.
at org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.createNotFoundException(DefaultConfigurationContainer.java:88)
at org.gradle.api.internal.DefaultNamedDomainObjectCollection.getByName(DefaultNamedDomainObjectCollection.java:210)
at org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.getByName(DefaultConfigurationContainer.java:78)
at org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.getByName(DefaultConfigurationContainer.java:36)
at org.gradle.api.internal.artifacts.dependencies.DefaultProjectDependency.getProjectConfiguration(DefaultProjectDependency.java:69)
at org.gradle.api.internal.artifacts.dependencies.DefaultProjectDependency_Decorated.getProjectConfiguration(Unknown Source)
at org.gradle.api.internal.artifacts.dependencies.DefaultProjectDependency$TaskDependencyImpl.visitDependencies(DefaultProjectDependency.java:165)
at org.gradle.api.internal.tasks.CachingTaskDependencyResolveContext$TaskGraphImpl.getNodeValues(CachingTaskDependencyResolveContext.java:88)
at org.gradle.internal.graph.CachingDirectedGraphWalker$GraphWithEmpyEdges.getNodeValues(CachingDirectedGraphWalker.java:202)
at org.gradle.internal.graph.CachingDirectedGraphWalker.doSearch(CachingDirectedGraphWalker.java:112)
at org.gradle.internal.graph.CachingDirectedGraphWalker.findValues(CachingDirectedGraphWalker.java:64)
at org.gradle.api.internal.tasks.CachingTaskDependencyResolveContext.doResolve(CachingTaskDependencyResolveContext.java:76)
at org.gradle.api.internal.tasks.CachingTaskDependencyResolveContext.resolve(CachingTaskDependencyResolveContext.java:65)
… 53 more


BUILD FAILED

Total time: 3.121 secs

Install the JDK.

Quartz101, on 24 February 2016 - 11:14 PM said:

Install the JDK.

Can you give me a link to the jdk? I think i might of installed the wrong one :(/>

FoxData, on 25 February 2016 - 12:04 AM said:

Quartz101, on 24 February 2016 - 11:14 PM said:

Install the JDK.

Can you give me a link to the jdk? I think i might of installed the wrong one :(/>

First make sure you cloned the repository recursively. If you check the KristAPI folder, there should be a bunch of files there. If not, you messed up and need to reclone the repository.

If that doesn't fix it, you can download JDK here.

apemanzilla, on 25 February 2016 - 02:52 AM said:

FoxData, on 25 February 2016 - 12:04 AM said:

Quartz101, on 24 February 2016 - 11:14 PM said:

Install the JDK.

Can you give me a link to the jdk? I think i might of installed the wrong one :(/>

First make sure you cloned the repository recursively. If you check the KristAPI folder, there should be a bunch of files there. If not, you messed up and need to reclone the repository.

If that doesn't fix it, you can download JDK here.

Now i just get this error:

5 tests completed, 5 failed
:test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':test'.
> There were failing tests. See the report at: file:///C:/Users/ollies%20pc/Downloads/turbokrist/build/reports/tests/index.html

* Try:
Run with –stacktrace option to get the stack trace. Run with –info or –debug option to get more log output.

BUILD FAILED

Total time: 5.157 secs

FoxData, on 25 February 2016 - 12:04 AM said:

Quartz101, on 24 February 2016 - 11:14 PM said:

Install the JDK.

Can you give me a link to the jdk? I think i might of installed the wrong one :(/>

Just gonna come in here and say this (Sorry, someone had to!): *Might have

FoxData, on 25 February 2016 - 12:52 PM said:

apemanzilla, on 25 February 2016 - 02:52 AM said:

FoxData, on 25 February 2016 - 12:04 AM said:

Quartz101, on 24 February 2016 - 11:14 PM said:

Install the JDK.

Can you give me a link to the jdk? I think i might of installed the wrong one :(/>

First make sure you cloned the repository recursively. If you check the KristAPI folder, there should be a bunch of files there. If not, you messed up and need to reclone the repository.

If that doesn't fix it, you can download JDK here.

Now i just get this error:

5 tests completed, 5 failed
:test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':test'.
> There were failing tests. See the report at: file:///C:/Users/ollies%20pc/Downloads/turbokrist/build/reports/tests/index.html

* Try:
Run with –stacktrace option to get the stack trace. Run with –info or –debug option to get more log output.

BUILD FAILED

Total time: 5.157 secs

This is why I ask people to build the code - I need to know why the tests fail :P/>

Anyways, zip up the files in build/reports/tests and send it to me via PM please. Also include your OS, GPU model, and driver version.

does this run on mac?

Edit: just using my windows computer for now, and i'm having problems with the build setup.

:KristAPI:compileJava FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':KristAPI:compileJava'.
> Could not find tools.java
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

I'm mining!
With a work-size of 2^22, i'm getting amazing results on my PC.

I sent Apeman 2 KST, then I immediately mined a block afterwards.

I have officially broken 100 KST! Yay!

Waitdev_, on 26 February 2016 - 09:53 AM said:

does this run on mac?

Edit: just using my windows computer for now, and i'm having problems with the build setup.

:KristAPI:compileJava FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':KristAPI:compileJava'.
> Could not find tools.java
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Assuming you have a working installation of OpenCL and JDK, this program should run on any operating system. I've personally used it on Linux and Windows.

One of two things is wrong.
1. You don't have JDK installed. Download it here.
2. You do have JDK installed, but your JAVA_HOME environment variable is incorrect. Set it to the base path of your JDK installation - eg: C:\Program Files\Java\jdk1.8.0_73\

ry00000, on 26 February 2016 - 07:08 PM said:

I'm mining!
With a work-size of 2^22, i'm getting amazing results on my PC.

I sent Apeman 2 KST, then I immediately mined a block afterwards.

I have officially broken 100 KST! Yay!

Can you send me the output from running it with -l, and the hashrate you're getting? I'm collecting a list of mining speed on different hardware.

i've tried updating jdk with the right path, but still the same error.

Waitdev_, on 27 February 2016 - 08:58 AM said:

i've tried updating jdk with the right path, but still the same error.

So you set the JAVA_HOME variable to the home path of the JDK?

Quartz101, on 27 February 2016 - 01:03 PM said:

Anyone know the proper setup for an Intel Core i3-4170 (haswell) w/ intergrated graphics?

You'll have to figure it out yourself with trial and error. There's a wiki page that explains how to do this.

apemanzilla, on 29 February 2016 - 12:12 AM said:

Waitdev_, on 27 February 2016 - 08:58 AM said:

i've tried updating jdk with the right path, but still the same error.

So you set the JAVA_HOME variable to the home path of the JDK?

Yep, but I'm still getting the exact same error.

Waitdev_, on 08 March 2016 - 10:27 AM said:

Yep, but I'm still getting the exact same error.

And you're sure it's the JDK and not the JRE? Because the latter does not contain tools.jar. If you're sure, try uninstalling any JDKs and JREs you have installed and then install the latest JDK from Oracle's website. You'll probably have to set JAVA_HOME again if you do this.

Waitdev_, on 08 March 2016 - 10:27 AM said:

apemanzilla, on 29 February 2016 - 12:12 AM said:

Waitdev_, on 27 February 2016 - 08:58 AM said:

i've tried updating jdk with the right path, but still the same error.

So you set the JAVA_HOME variable to the home path of the JDK?

Yep, but I'm still getting the exact same error.

Im also gettin the exact same error too.

It works now. I didnt have JDE :P/>

minizbot2012, on 15 February 2016 - 10:56 PM said:

I am getting disappointing speeds on my 970 (11-13 MH/s)

:I Im disappointed with my 0.5MH/S

This is truly amazing. 11 blocks/minute on a gtx 970.

Creator, on 20 May 2016 - 07:48 PM said:

This is truly amazing. 11 blocks/minute on a gtx 970.

Hashrate tells more than blocks/minute. The server attempts to adjust the work to be at around 1 block per minute globally.

My R9 390 can reach speeds of 1.45 GH/s, and from other reports the GTX 970 hits 900-950 MH/s.

970 MH/s on GTX 970. Awesome!

R7 260X getting 300-500 MH/S, hit the final spot on the Econ top addresses because of this XD

Just solved my first block while I was just configuring the settings and playing with my bat file. :)/> Pleasant surprise! Thanks for publishing this.

I get this when doing 'gradlew build'

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':KristAPI:compileJava'.
> Could not find tools.jar

Incinirate, on 12 June 2016 - 03:15 AM said:

I get this when doing 'gradlew build'

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':KristAPI:compileJava'.
> Could not find tools.jar

That usually happens when you either don't have JDK installed properly, or don't have your JAVA_HOME environment variable set to the JDK. Could you try that?

apemanzilla, on 12 June 2016 - 04:52 AM said:

Incinirate, on 12 June 2016 - 03:15 AM said:

I get this when doing 'gradlew build'

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':KristAPI:compileJava'.
> Could not find tools.jar

That usually happens when you either don't have JDK installed properly, or don't have your JAVA_HOME environment variable set to the JDK. Could you try that?

Ahh, my JAVA_HOME was set to my JRE for some reason. All good now, thanks!

Incinirate, on 12 June 2016 - 04:56 AM said:

apemanzilla, on 12 June 2016 - 04:52 AM said:

Incinirate, on 12 June 2016 - 03:15 AM said:

I get this when doing 'gradlew build'

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':KristAPI:compileJava'.
> Could not find tools.jar

That usually happens when you either don't have JDK installed properly, or don't have your JAVA_HOME environment variable set to the JDK. Could you try that?

Ahh, my JAVA_HOME was set to my JRE for some reason. All good now, thanks!

Glad to hear it!

Wow this works good, I got 14 blocks in one minute o.o
Great tool!

My avg speed is 1.6 GH/s

Incinirate, on 12 June 2016 - 05:08 AM said:

Wow this works good, I got 14 blocks in one minute o.o
Great tool!

My avg speed is 1.6 GH/s

Wow, that's higher than my max of 1.5 GH/s. What hardware are you using?

apemanzilla, on 12 June 2016 - 02:41 PM said:

Incinirate, on 12 June 2016 - 05:08 AM said:

Wow this works good, I got 14 blocks in one minute o.o
Great tool!

My avg speed is 1.6 GH/s

Wow, that's higher than my max of 1.5 GH/s. What hardware are you using?

Two GTX 980s running in SLI

Incinirate, on 12 June 2016 - 05:16 PM said:

apemanzilla, on 12 June 2016 - 02:41 PM said:

Incinirate, on 12 June 2016 - 05:08 AM said:

Wow this works good, I got 14 blocks in one minute o.o
Great tool!

My avg speed is 1.6 GH/s

Wow, that's higher than my max of 1.5 GH/s. What hardware are you using?

Two GTX 980s running in SLI

Ahh, that would do it. Chances are only one is being used though, try using the -a argument if you're not already.

Incinirate, on 12 June 2016 - 05:16 PM said:

apemanzilla, on 12 June 2016 - 02:41 PM said:

Incinirate, on 12 June 2016 - 05:08 AM said:

Wow this works good, I got 14 blocks in one minute o.o
Great tool!

My avg speed is 1.6 GH/s

Wow, that's higher than my max of 1.5 GH/s. What hardware are you using?

Two GTX 980s running in SLI

That must've cost an arm and a leg! Other people prefer to spend these limbs on automail. :P/>

You should be able to get more out of these GPU's, as apeman stated.

Creator, on 12 June 2016 - 07:57 PM said:

You should be able to get more out of these GPU's, as apeman stated.

We've found that AMD GPUs perform significantly better than NVIDIA when running turbokrist, so it is possible that he's already using -a, since apemanzilla uses an AMD R9 390.

Lignum, on 12 June 2016 - 08:58 PM said:

Creator, on 12 June 2016 - 07:57 PM said:

You should be able to get more out of these GPU's, as apeman stated.

We've found that AMD GPUs perform significantly better than NVIDIA when running turbokrist, so it is possible that he's already using -a, since apemanzilla uses an AMD R9 390.

Not likely. The 980 has about 30-40% better compute performance compared to the R9 390, which would make up for the gap in performance between AMD and Nvidia.

apemanzilla, on 12 June 2016 - 10:45 PM said:

Not likely. The 980 has about 30-40% better compute performance compared to the R9 390, which would make up for the gap in performance between AMD and Nvidia.

Oh, nvm then. :P/>

I'm currently using AMD Radeon HD 8500M to mine krist and i get ~100 MH/s using work size "2097152". Do you guys think i can get faster? (~2 blocks/minute)

EDIT: I'm getting ~115 MH/s now with a slight overclock (same work size).
EDIT 2: Dropped work size to 1048576 and it's still at same speeds. (also with -a, intel helping too) Will probably use this as 3145728 crashed on me.
EDIT 3: Crashed my computer two times because of high work size, i think it's worth it.

Admicos, on 27 July 2016 - 10:41 PM said:

I'm currently using AMD Radeon HD 8500M to mine krist and i get ~100 MH/s using work size "2097152". Do you guys think i can get faster? (~2 blocks/minute)

EDIT: I'm getting ~115 MH/s now with a slight overclock (same work size).
EDIT 2: Dropped work size to 1048576 and it's still at same speeds. (also with -a, intel helping too) Will probably use this as 3145728 crashed on me.
EDIT 3: Crashed my computer two times because of high work size, i think it's worth it.

You should keep the worksize at 1048576 then, if it changes barely anything. Even if you gain 1-5MH/s by doubling it, those hashes would be pretty insignificant and a waste of energy. Same goes for -a, if it changes nothing, remove it. 115 MH/s sounds pretty okay for a HD 8500M to me. Also consider mining on Linux (if you're not already), it's slightly faster there for whatever reason.

1.6MH/s sounds good for intergrated graphics (not)

B)/>

Lignum, on 28 July 2016 - 12:43 PM said:

Admicos, on 27 July 2016 - 10:41 PM said:

I'm currently using AMD Radeon HD 8500M to mine krist and i get ~100 MH/s using work size "2097152". Do you guys think i can get faster? (~2 blocks/minute)

EDIT: I'm getting ~115 MH/s now with a slight overclock (same work size).
EDIT 2: Dropped work size to 1048576 and it's still at same speeds. (also with -a, intel helping too) Will probably use this as 3145728 crashed on me.
EDIT 3: Crashed my computer two times because of high work size, i think it's worth it.

You should keep the worksize at 1048576 then, if it changes barely anything. Even if you gain 1-5MH/s by doubling it, those hashes would be pretty insignificant and a waste of energy. Same goes for -a, if it changes nothing, remove it. 115 MH/s sounds pretty okay for a HD 8500M to me. Also consider mining on Linux (if you're not already), it's slightly faster there for whatever reason.

I tried minng on linux, but the open source drivers on Arch currently doesn't work with OpenCL 1.2 (i think. It's giving me errors about "static")
If it didn't, that would be great.

(Also, fglrx isn't even compatible, unless i use a old version of Ubuntu, but no thanks i like my up-to-date software)

Admicos, on 28 July 2016 - 05:38 PM said:

I tried minng on linux, but the open source drivers on Arch currently doesn't work with OpenCL 1.2 (i think. It's giving me errors about "static")
If it didn't, that would be great.

(Also, fglrx isn't even compatible, unless i use a old version of Ubuntu, but no thanks i like my up-to-date software)

I'm not surprised mesa messes it up, it's really not suitable for anything beyond basic graphics (yet). Have you tried AMD GPU-PRO?

Lignum, on 28 July 2016 - 07:26 PM said:

Admicos, on 28 July 2016 - 05:38 PM said:

I tried minng on linux, but the open source drivers on Arch currently doesn't work with OpenCL 1.2 (i think. It's giving me errors about "static")
If it didn't, that would be great.

(Also, fglrx isn't even compatible, unless i use a old version of Ubuntu, but no thanks i like my up-to-date software)

I'm not surprised mesa messes it up, it's really not suitable for anything beyond basic graphics (yet). Have you tried AMD GPU-PRO?

(IIRC) AMDGPU is still experimental for GCN 1.0 yet. But when it gets stable enough, I'm gonna remove my Windows partition immidiately.
for the PRO extension, i have no clue.

Anyways.

Admicos, on 28 July 2016 - 05:38 PM said:

I tried minng on linux, but the open source drivers on Arch currently doesn't work with OpenCL 1.2 (i think. It's giving me errors about "static")
If it didn't, that would be great.

(Also, fglrx isn't even compatible, unless i use a old version of Ubuntu, but no thanks i like my up-to-date software)

The only success I've had at all with Linux was mining with proprietary Nvidia drivers on Ubuntu 14.04 (for nvidia cards obviously) and mining with the community AMD drivers on Ubuntu 14.04. (although with less than half the hashrate of Windows) I've had zero luck getting anything to work with AMD on Arch and haven't tried Nvidia, so unfortunately I can't really help you much.

Execution failed for task ':test'

AndreWalia, on 03 August 2016 - 02:19 AM said:

Execution failed for task ':test'

Need more info, can you send me the test reports? Should be in build/reports or something.

My GPU shows some very interesting behaviour after mining for 20 minutes:

CrazedProgrammer, on 01 October 2016 - 09:08 PM said:

My GPU shows some very interesting behaviour after mining for 20 minutes:

And that's what we call turbolag, now it'll go super fast! But yeah, that's pretty odd, just a couple decimal places off…

I could not build this :(/> :
:JKrist:compileJava UP-TO-DATE
:JKrist:processResources UP-TO-DATE
:JKrist:classes UP-TO-DATE
:JKrist:jar UP-TO-DATE
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:jar
:assemble
:compileTestJava
warning: [options] bootstrap class path not set in conjunction with -source 1.6
1 warning
:processTestResources
:testClasses
:test

me.apemanzilla.jclminer.tests.TestCLHashing > testHashing_digest FAILED
java.lang.UnsatisfiedLinkError
java.lang.NullPointerException

me.apemanzilla.jclminer.tests.TestCLMacros > testMacro_PAD FAILED
java.lang.NoClassDefFoundError
java.lang.NullPointerException

me.apemanzilla.jclminer.tests.TestCLMacros > testMacro_RR FAILED
java.lang.NoClassDefFoundError
java.lang.NullPointerException

me.apemanzilla.jclminer.tests.TestCLMining > testMining_hashToLong FAILED
java.lang.NoClassDefFoundError
java.lang.NullPointerException

# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
me.apemanzilla.jclminer.tests.TestCLConstants > testConstant_K FAILED
java.lang.NoClassDefFoundError
java.lang.NullPointerException

5 tests completed, 5 failed
:test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':test'.
> There were failing tests. See the report at: file:///home/a*****/Desktop/turbokrist/build/reports/tests/index.html

* Try:
Run with –stacktrace option to get the stack trace. Run with –info or –debug option to get more log output.

BUILD FAILED

With stacktrace:
:JKrist:compileJava UP-TO-DATE
:JKrist:processResources UP-TO-DATE
:JKrist:classes UP-TO-DATE
:JKrist:jar UP-TO-DATE
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:jar UP-TO-DATE
:assemble UP-TO-DATE
:compileTestJava UP-TO-DATE
:processTestResources UP-TO-DATE
:testClasses UP-TO-DATE
:test

me.apemanzilla.jclminer.tests.TestCLHashing > testHashing_digest FAILED
java.lang.UnsatisfiedLinkError
java.lang.NullPointerException

me.apemanzilla.jclminer.tests.TestCLMacros > testMacro_PAD FAILED
java.lang.NoClassDefFoundError
java.lang.NullPointerException

me.apemanzilla.jclminer.tests.TestCLMacros > testMacro_RR FAILED
java.lang.NoClassDefFoundError
java.lang.NullPointerException

me.apemanzilla.jclminer.tests.TestCLMining > testMining_hashToLong FAILED
java.lang.NoClassDefFoundError
java.lang.NullPointerException

me.apemanzilla.jclminer.tests.TestCLConstants > testConstant_K FAILED
java.lang.NoClassDefFoundError
java.lang.NullPointerException
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type
# BridJ: dlopen error when loading OpenCLProbe : OpenCLProbe: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type

5 tests completed, 5 failed
:test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':test'.
> There were failing tests. See the report at: file:///home/alexis/Desktop/turbokrist/build/reports/tests/index.html

* Try:
Run with –info or –debug option to get more log output.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':test'.
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46)
at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35)
at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:64)
at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:52)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53)
at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:203)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:185)
at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:66)
at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:50)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process(DefaultTaskPlanExecutor.java:25)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:110)
at org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:37)
at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)
at org.gradle.execution.DefaultBuildExecuter.access$000(DefaultBuildExecuter.java:23)
at org.gradle.execution.DefaultBuildExecuter$1.proceed(DefaultBuildExecuter.java:43)
at org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:32)
at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:37)
at org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:30)
at org.gradle.initialization.DefaultGradleLauncher$4.run(DefaultGradleLauncher.java:154)
at org.gradle.internal.Factories$1.create(Factories.java:22)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:52)
at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:151)
at org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:32)
at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:99)
at org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:93)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:62)
at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:93)
at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:82)
at org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:94)
at org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)
at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:43)
at org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:28)
at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:78)
at org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:48)
at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:51)
at org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:28)
at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:43)
at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:170)
at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:237)
at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:210)
at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35)
at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:206)
at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
at org.gradle.launcher.Main.doAction(Main.java:33)
at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:54)
at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:35)
at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
Caused by: org.gradle.api.GradleException: There were failing tests. See the report at: file:///home/alexis/Desktop/turbokrist/build/reports/tests/index.html
at org.gradle.api.tasks.testing.Test.handleTestFailures(Test.java:1157)
at org.gradle.api.tasks.testing.Test.executeTests(Test.java:570)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:227)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:220)
at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:209)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:585)
at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:568)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)
… 57 more


BUILD FAILED

Redall, on 19 November 2016 - 11:02 AM said:

I could not build this :(/> :
…

From your crash report, it seems like you're using Linux, so there's a few possibilities:

• You're using Mesa as your graphics driver, which does not have support for OpenCL. If you have glxinfo installed, you can check this with "glxinfo | grep version". Use proprietary drivers instead.
• Your graphics drivers are outdated. Update them.
• You don't have your vendor's OpenCL library installed (which may or may not come with the graphics driver).
• You have an Intel graphics card. No solution to this, turbokrist simply doesn't work on them because they don't play nice with OpenCL (on Linux).

The exact solutions to all of these depend on your graphics vendor and distro, of course, so you're on your own.

Lignum, on 19 November 2016 - 01:14 PM said:

Redall, on 19 November 2016 - 11:02 AM said:

I could not build this :(/>/&amp;gt; :
…

From your crash report, it seems like you're using Linux, so there's a few possibilities:

• You're using Mesa as your graphics driver, which does not have support for OpenCL. If you have glxinfo installed, you can check this with "glxinfo | grep version". Use proprietary drivers instead.
• Your graphics drivers are outdated. Update them.
• You don't have your vendor's OpenCL library installed (which may or may not come with the graphics driver).
• You have an Intel graphics card. No solution to this, turbokrist simply doesn't work on them because they don't play nice with OpenCL (on Linux).

The exact solutions to all of these depend on your graphics vendor and distro, of course, so you're on your own.

• Not using Mesa.
• Already updated.
• Will try to install nVidia drivers for Linux.
• Not using a Intel HD Graphics card (using nVidia GeForce GT [do not know the number])

EDIT: I use Ubuntu 16.04 LTS, graphic card detected by the distribution: Gallium 0.4 on NV96 - which is incorrect.
EDIT2: The driver is not supported by my graphics card, because of the kernel which is not compatible with the driver from Ubuntu default repository.

Redall, on 19 November 2016 - 04:49 PM said:

EDIT: I use Ubuntu 16.04 LTS, graphic card detected by the distribution: Gallium 0.4 on NV96 - which is incorrect.

Gallium is part of Mesa. You'll have to install the NVIDIA proprietary drivers as well as the nvidia-opencl-dev package from apt.

Lignum, on 19 November 2016 - 05:12 PM said:

Redall, on 19 November 2016 - 04:49 PM said:

EDIT: I use Ubuntu 16.04 LTS, graphic card detected by the distribution: Gallium 0.4 on NV96 - which is incorrect.

Gallium is part of Mesa. You'll have to install the NVIDIA proprietary drivers as well as the nvidia-opencl-dev package from apt.

No more need to help me, I switched to Windows (because the computer I have is multiboot). And worked without any problems.
But thanks for your help :)/>

So what sort of speeds is everyone getting. im hitting around 2.55 GH/s with my dual 980s. is there better performance with or without SLI enabled.

I'm hitting 1.41GH/s with my MSI Radeon RX480 Gaming X 8GB

Mine, unfortunately, appears to cap out at 1.28 GH/s with 2^23 on my GTX 980. Could attempt to go higher but the increase mostly stabilized at 2^24, giving me only about 1.29 GH/s.

Also, I'm always very wary about my temps on my PC. :P/>

http://prnt.sc/dcfkaa

TR1T0N_, on 26 November 2016 - 09:20 PM said:

So what sort of speeds is everyone getting. im hitting around 2.55 GH/s with my dual 980s. is there better performance with or without SLI enabled.

…

Turbokrist doesn't care about your SLI settings, as long as you have -a set, it will make use of all of your GPUs.

My build is stuck at 33% "test" on macOS. Any fixes? I'm stuck during the building phase.

PLKids, on 30 December 2016 - 12:11 AM said:

My build is stuck at 33% "test" on macOS. Any fixes? I'm stuck during the building phase.

Turbokrist doesn't work on macOS due to a bug in Apple's graphics drivers.

Dang… Any other way to mine? I have a multiboot. I'll try that.

PLKids, on 30 December 2016 - 02:40 PM said:

Dang… Any other way to mine? I have a multiboot. I'll try that.

Sure, on Windows or Linux it should work. However, some Intel HD cards have similar driver trouble (you wouldn't get much perf out of them anyway). If you're on AMD or NVIDIA, you're good to go.

Hmm. Is there another way to mine? I have an Intel Mac. Any other programs or fixes?

EDIT: The reason I ask is because my dual-boot is also on an Intel Mac. <_</>

PLKids, on 30 December 2016 - 07:19 PM said:

Hmm. Is there another way to mine? I have an Intel Mac. Any other programs or fixes?

EDIT: The reason I ask is because my dual-boot is also on an Intel Mac. <_</>

There are other programs, but only CPU miners, which are basically useless with the current mining difficulty. But if you insist, there is SKristMinster and ytci-krist-miner.

I've tried both. Not sure how to make them work. (I'm new to this type of thing.) :(/> Thanks though!

Hey everyone,

I decided to make a python (2.7) script to run and find the best worksize for my GPU

autowork.py

Just put the script in the same folder as turbokrist-cli.jar and run "python autowork.py -h <address> -s <starting worksize>



Also here is a compiled jar for x64: turbokrist-cli.jar

If anyone likes the script or the jar please either donate some krist or mine for me by running the script with no -h flag

To OP, please let me know if you would prefer me to not distribute the jar. Compiling it was a pain, so I thought I'd save other's the trouble…

Any suggestions or comments are welcome,
edggy
kl40y80hci

PLKids, on 30 December 2016 - 09:50 PM said:

I've tried both. Not sure how to make them work. (I'm new to this type of thing.) :(/> Thanks though!

This is probably the best CPU miner available. https://github.com/1lann/krist-miner/releases

edggy, on 12 January 2017 - 02:30 AM said:

Hey everyone,

I decided to make a python (2.7) script to run and find the best worksize for my GPU

autowork.py

Just put the script in the same folder as turbokrist-cli.jar and run "python autowork.py -h <address> -s <starting worksize>



Also here is a compiled jar for x64: turbokrist-cli.jar

If anyone likes the script or the jar please either donate some krist or mine for me by running the script with no -h flag

To OP, please let me know if you would prefer me to not distribute the jar. Compiling it was a pain, so I thought I'd save other's the trouble…

Any suggestions or comments are welcome,
edggy
kl40y80hci

Just a warning, the reason turbokrist doesn't have a built-in profiler is because running high work sizes on lower end hardware often causes issues ranging from crashes to BSODs.

I'm fine with you distributing the jar, the main reason that I don't provide one myself is because the output from the build logs is much more useful when trying to figure out why it inevitably won't run for someone else.

apemanzilla, on 12 January 2017 - 09:00 PM said:

edggy, on 12 January 2017 - 02:30 AM said:

Hey everyone,
…

Just a warning, the reason turbokrist doesn't have a built-in profiler is because running high work sizes on lower end hardware often causes issues ranging from crashes to BSODs.

I'm fine with you distributing the jar, the main reason that I don't provide one myself is because the output from the build logs is much more useful when trying to figure out why it inevitably won't run for someone else.

The idea here is that you let it sit for a bit and check what it ended up at. Then you just use that number in the future.

I have an old usb ASIC for mining Bitcoins from way back when just sitting around. By any chance do you know how to interface with it?

Thanks,
edggy
kl40y80hci

edggy, on 13 January 2017 - 01:20 AM said:

apemanzilla, on 12 January 2017 - 09:00 PM said:

edggy, on 12 January 2017 - 02:30 AM said:

Hey everyone,
…

Just a warning, the reason turbokrist doesn't have a built-in profiler is because running high work sizes on lower end hardware often causes issues ranging from crashes to BSODs.

I'm fine with you distributing the jar, the main reason that I don't provide one myself is because the output from the build logs is much more useful when trying to figure out why it inevitably won't run for someone else.

The idea here is that you let it sit for a bit and check what it ended up at. Then you just use that number in the future.

I have an old usb ASIC for mining Bitcoins from way back when just sitting around. By any chance do you know how to interface with it?

Thanks,
edggy
kl40y80hci

ASICs won't work as they are designed to do effectively sha256(sha256(nonce)) rather than krist, which uses sha256(nonce)

I am trying to make it running, but I am getting this error:

https://pastebin.com/DGL7yeQd

I want to try my nvidia GTX 1080

Windows 10

any help please?

Saddamo, on 11 August 2017 - 07:49 PM said:

I am trying to make it running, but I am getting this error:

https://pastebin.com/DGL7yeQd

I want to try my nvidia GTX 1080

Windows 10

any help please?

Seems like turbokrist doesn't detect your graphics card. Try updating your graphics drivers. If that doesn't work, try installing the CUDA SDK.

got latest drivers available, got right java, installed CUDA SDK, got this error:

https://pastebin.com/QT9yjgVS

Saddamo, on 14 August 2017 - 11:23 PM said:

got latest drivers available, got right java, installed CUDA SDK, got this error:

https://pastebin.com/QT9yjgVS

Hm, that's essentially the same error. You wouldn't have an integrated GPU along with your GTX 1080, would you? It might be trying to use that instead, which would most likely result in weirdness like this.

I got Alienware 17 laptop, which has 2 GPUs.

Intel HD Graphics 530
Nvidia GTX 1080

Saddamo, on 15 August 2017 - 08:19 PM said:

I got Alienware 17 laptop, which has 2 GPUs.

Intel HD Graphics 530
Nvidia GTX 1080

That would be the issue then. I have no experience with NVIDIA Optimus, so I can't help you much, but I found this article for Autodesk Infraworks. You should be able to follow those same steps, but select turbokrist (java.exe, it should show up when you click "Add" if you started it recently) instead of Infraworks.

after fidling with nVidia for 2 hours, nothing has changed, I am going to try it on a desktop with GTX 1080

if somebody can send me 1 Krist, my address is: kvl02hyp32

I am still trying to make it run on ComputerCraft but my wallet is empty :D/>

If I will get it working, I will pay back asap

maybe I do just something wrong, I am using this command:

in this directory

\Krist_Miners\turbokrist\turbokrist-cli\build\libs

java -jar turbokrist-cli.jar -h mykristaddress

Saddamo, on 16 August 2017 - 02:31 PM said:

after fidling with nVidia for 2 hours, nothing has changed, I am going to try it on a desktop with GTX 1080

if somebody can send me 1 Krist, my address is: kvl02hyp32

I am still trying to make it run on ComputerCraft but my wallet is empty :D/>

If I will get it working, I will pay back asap

Hm, it might be an issue with turbokrist itself, then. But it should definitely work on your desktop. Either way, I've sent you 1 KST, don't worry about paying back, I've got way too much of the stuff.

khugepoopy, thank you very much!

my CC wallet is very secured :D/> I mean, the computer in server room :D/>

http://imgur.com/a/UGGGc

Lignum, on 16 August 2017 - 02:41 PM said:

Saddamo, on 16 August 2017 - 02:31 PM said:

after fidling with nVidia for 2 hours, nothing has changed, I am going to try it on a desktop with GTX 1080

if somebody can send me 1 Krist, my address is: kvl02hyp32

I am still trying to make it run on ComputerCraft but my wallet is empty :D/>

If I will get it working, I will pay back asap

Hm, it might be an issue with turbokrist itself, then. But it should definitely work on your desktop. Either way, I've sent you 1 KST, don't worry about paying back, I've got way too much of the stuff.

thank you very much one more time

the question is, how could be Krist currency used for a server bank?

believe me or not:

http://imgur.com/a/d3jZB

started from the scratch…

updated windows, drivers, JAVA and everything else…

and miner started to work :D/>

thank you very much for help


my new balance is 78KST

my command:

java -jar turbokrist-cli.jar -h krist_name -d 2 -w -423801227:16777216

it gets me around 2,05GH/s on nvidia gtx 1080 on a laptop


installed on a desktop with gtx 1080 too on a first try, there is no secondary GPU

just updated Windows 10 + latest 64 bit java, not even SDK java and works like a charm

yo everybody, again

was something changed with Krist mining?

http://imgur.com/a/4yu9V

Saddamo, on 18 August 2017 - 05:41 PM said:

yo everybody, again

was something changed with Krist mining?

http://imgur.com/a/4yu9V

The work value is self-adjusting. The node tries to maintain a one-block-per-minute difficulty level, which means if no one mines for a while, it's easier to mine.

apemanzilla, on 18 August 2017 - 06:37 PM said:

Saddamo, on 18 August 2017 - 05:41 PM said:

yo everybody, again

was something changed with Krist mining?

http://imgur.com/a/4yu9V

The work value is self-adjusting. The node tries to maintain a one-block-per-minute difficulty level, which means if no one mines for a while, it's easier to mine.

thank you for info

I was thinking something like that