will also donate some for the improved neoscrypt miner.
also, my miners are kept in an air conditioned room set to 80 deg. F. They don't seem to have any trouble, even overclocked, never getting above 63 C on the hottest card.
you must be running on free electricity, then :-) |
|
|
|
some progress on neoscrypt: ~850kH/s on gtx980
~500kh/s on gtx780ti
201kh/s on gtx750
Hope Djm34 will share his improvements.  +1 please :-) great improvement.Hope he'll share ) i'm ready to donate some bucks )) beer ready for djm34 ;-) |
|
|
|
some progress on neoscrypt: ~850kH/s on gtx980
~500kh/s on gtx780ti
201kh/s on gtx750
Hope Djm34 will share his improvements. +1 please :-) |
|
|
|
|
quark hashrate is about double that of x11, so it's still the most profitable for me, except when neoscrypt goes over 7 BTC/Gh/day.
this miner is extremely good mining neoscrypt, it uses less power than quark (it's the opposite on amd, afaik).
|
|
|
|
|
Is there a problem with bowscoin?
X11 profit should be good but when it mines that coin the return is very low.
|
|
|
|
|
wolf0's bins do work on 64 bit linux even though they are "l4".
|
|
|
|
I'm curious to see if it's good for the 750 as well.
no good for the 750ti. A drop of 400khash. I'm new to cuda: is there an ifdef or something we can put to enable the unroll for 9xx cards only? |
|
|
|
This little patch is giving quark +300 Kh/s on my 970:
diff --git a/groestl_functions_quad.cu b/groestl_functions_quad.cu
index c39e81d..3ac3c5d 100644
--- a/groestl_functions_quad.cu
+++ b/groestl_functions_quad.cu
@@ -285,7 +285,7 @@ __device__ __forceinline__ void G256_MixFunction_quad(uint32_t *r)
__device__ __forceinline__ void groestl512_perm_P_quad(uint32_t *const r)
{
-
+#pragma unroll
for(int round=0;round<14;round++)
{
G256_AddRoundConstantP_quad(r[7], r[6], r[5], r[4], r[3], r[2], r[1], r[0], round);
where does the patch go? ... #crysx "patch -p0" should work. If you wonna do it manually, the file name is at the start of the patch. I'm curious to see if it's good for the 750 as well. |
|
|
|
|
This little patch is giving quark +300 Kh/s on my 970:
diff --git a/groestl_functions_quad.cu b/groestl_functions_quad.cu
index c39e81d..3ac3c5d 100644
--- a/groestl_functions_quad.cu
+++ b/groestl_functions_quad.cu
@@ -285,7 +285,7 @@ __device__ __forceinline__ void G256_MixFunction_quad(uint32_t *r)
__device__ __forceinline__ void groestl512_perm_P_quad(uint32_t *const r)
{
-
+#pragma unroll
for(int round=0;round<14;round++)
{
G256_AddRoundConstantP_quad(r[7], r[6], r[5], r[4], r[3], r[2], r[1], r[0], round);
|
|
|
|
XMR (monero is actually the #14 largest altcoin on the cryptocoin chart. I think I will add my modded for free to ccminer sp-mod. Please donate some beers, I need some fuel for the weekend  While the quark clondike seems to pass, we need some new algos to play with. beer sent! :-) |
|
|
|
Submitted an optimalization in bmw512. My testrig is up from 44600KHASH to 45000KHASH @quark
A few khash gain in x11 as well.
Thanks, I'm trying it now but it's difficult to measure the hashrate difference because of the fan speed triggered throttling. |
|
|
|
Ok I tried X11 instead of lyra2E, and it started doing things. It couldn't connect to port 9050, but it's something.
So ccminer isn't recognizing the algo Lyra2E.
-a lyra2 works for me |
|
|
|
You're right, I just put user instead of rpcuser.
I changed my conf file and it's still not working.
try adding: server=1 listen=1 daemon=1 rpcallowip=localhost |
|
|
|
I changed the IP to my local IP. Same result, nothing happens.
you need to set user and pass in your conf file and use that instead: rpcuser=miner (or your username of choice) rpcpassword=miner1 (or your password of choice) |
|
|
|
|
I hope the fury will do groestl fast, but no tests I've seen yet.
Other algos are looking pretty bad, until someone optimizes for it. Yet, it might end up being a good or a bad miner, we still don't know. Time will tell.
For sure I wouldn't but a fury for mining now, and for surer not at the current price.
|
|
|
|
|
The current fee for quark is 5.1%.
I don't wonna sound cheap, but isn't that a bit too high?
|
|
|
|
|
The deb doesn't include the drivers but it depends on them, and a specific version. That was the problem.
|
|
|
|
I get 16.2 MHASH@quark with compute 5.2 build for x86 in the opensource version. (gigabyte windforce 970)
Compute 5.2 has bether launchconfigurations.
OMG I installed cuda 6.5 with support for compute 5.2, using the run files, what a pain! but now lyra works and I get about 700 Kh/s more on a single 970 :-) awesome ... where do you get the 5.2 patch for cuda 6.5? ... i still have to manually edit the Makefile.am to stop it trying to compile compute 5.2 ... great work though ... #crysx - tried the deb file and failed - downloaded the run file for cuda 6.5 9xx cards from nvidia website - had to manually install the latest driver using the run file, downloaded separately (the one provided in the toolkit isn't compatible with the latest kernels) - had to remove everything nvidia related on the system and other cleanups - had to install gcc-4.7 and modify the Makefile.am in order to use it and probably some other things I forgot.... |
|
|
|
I get 16.2 MHASH@quark with compute 5.2 build for x86 in the opensource version. (gigabyte windforce 970)
Compute 5.2 has bether launchconfigurations.
OMG I installed cuda 6.5 with support for compute 5.2, using the run files, what a pain! but now lyra works and I get about 700 Kh/s more on a single 970 :-) |
|
|
|
|
Show Posts
