Is Myriad-Groestl and Groestl the same? If my mining method can only mine Myriad-groestl can I also mine Groestl
Thx
Topic: DGB DigiByte Qubit and Myriad-Groestl Suprnova Pools (Read 10013 times)
I used another miner. Krauslt one and my hashrate went up drastically.
Pool payouts are way lower recently cause the price spike that happened recently, more miners wanted to mine DGB.
DGB payouts should be higher soon enough since the price is going down a bit.
Pool payouts are way lower recently cause the price spike that happened recently, more miners wanted to mine DGB.
DGB payouts should be higher soon enough since the price is going down a bit.
May I have a link with this Krauslt miner ?
Thanks !
Ccminer.org , go to kraustl version.
Add -i 25 in batfile. Should be ok.
I used another miner. Krauslt one and my hashrate went up drastically.
Pool payouts are way lower recently cause the price spike that happened recently, more miners wanted to mine DGB.
DGB payouts should be higher soon enough since the price is going down a bit.
Pool payouts are way lower recently cause the price spike that happened recently, more miners wanted to mine DGB.
DGB payouts should be higher soon enough since the price is going down a bit.
May I have a link with this Krauslt miner ?
Thanks !
I used another miner. Krauslt one and my hashrate went up drastically.
Pool payouts are way lower recently cause the price spike that happened recently, more miners wanted to mine DGB.
DGB payouts should be higher soon enough since the price is going down a bit.
Pool payouts are way lower recently cause the price spike that happened recently, more miners wanted to mine DGB.
DGB payouts should be higher soon enough since the price is going down a bit.
It was indeed a streak of bad luck.... founding blocks again now
Is it something wrong with DGB Skein pool?
It's almost two hour that we found last block... average is otherwise 15min... are we having big bad luck time?
It's almost two hour that we found last block... average is otherwise 15min... are we having big bad luck time?
Picture of my 5 gpu rig, check the first worker.
CCMiner :
Pool hashrate :
CCMiner :
Pool hashrate :
Hi.
Last days, I had a normal hashrate for my 6 gpu rigs :
CCminer hashrate - Around 275 Mh/s
Pool hashrate - Around 235 Mh/s
------
Today, I have the usual CCminer hashrate, but my pool effective hashrate is around 35-40 Mh/s.
How can I fix that ?
Main post : https://bitcointalksearch.org/topic/gtx-1060-6gb-x-6-myriad-groestl-pools-hashrate-problems-2074862
Last days, I had a normal hashrate for my 6 gpu rigs :
CCminer hashrate - Around 275 Mh/s
Pool hashrate - Around 235 Mh/s
------
Today, I have the usual CCminer hashrate, but my pool effective hashrate is around 35-40 Mh/s.
How can I fix that ?
Main post : https://bitcointalksearch.org/topic/gtx-1060-6gb-x-6-myriad-groestl-pools-hashrate-problems-2074862
Can I check my 24 hours average hashrate?
From what i see the hashrate and shares reported / submitted by some ccminer versions are fake and therefore those versions are all not working on suprnova.
Ok, good to know. What I see is, I tried sending shares to dgbg.suprnova with 4 different versions of ccminer, all of them showed ~75% of reported hash rate disappearing somewhere. I tried sending shares to theblocksfactory with 2 versions of ccminer, and 1 of them worked as expected with miner reported hash rate and pool reported average effective hash rate being a close match. I'm new to mining with NVidia GPUs and all the information I've found so far about Myriad-Groestl mining software for NVidia GPUs recommends some version of ccminer. Can you recommend a version of ccminer that is known to work with dgbg.suprnova? Or alternatively, can you recommend some other non-ccminer Myriad-Groestl mining software for NVidia GPUs that you know works with dgbg.suprnova?
with the static diff setting you could effectively circumvent the check and "steal" from the other miners - thats why its permanently disabled
I don't run a pool, so I won't pretend I understand what check a static diff can circumvent, or how using a static diff could lead to stolen shares. I'll take your word for it. Good to know that static diff is permanently disabled on dgbg.suprnova. For me, static diff simplifies tuning, benchmarking, comparing mining rigs, or comparing different mining software. The rest of the time, I'm happy to let vardiff change the diff as needed.
I do have a couple of suggestions for improvements to the dgbg.suprnova dashboard.
- If static diff is permanently disabled, please remove the text above the example code and the text in the -p field of the example code that tells/shows how to enable static diff. Otherwise you risk confusing and frustrating miners who are interested in using a static diff.
- Since there are problems with at least 4 versions of ccminer when sending shares to dgbg.suprnova, you could help miners using NVidia GPUs who want to send shares to dgbg.suprnova by changing the beginning of the example code from ./ccminer... to ./[foldername-for-ccminer-version-known-to-work-with-dgbg.suprnova]/ccminer... or ./[non-ccminer-that-works-with-dgbg.suprnova]/[suprminer]...
- It would be easier to see how workers are doing if values in the Difficulty column of the workers table matched the values that suprnova is telling the mining software to use.
I'll be back to dgbg.suprnova if/when I find software that solves Myriad-Groestl shares on NVidia GPUs in a way that dgbg.suprnova accepts/recognizes. Till then, I'll have to submit those shares to a different pool.
From what i see the hashrate and shares reported / submitted by some ccminer versions are fake and therefore those versions are all not working on suprnova.
with the static diff setting you could effectively circumvent the check and "steal" from the other miners - thats why its permanently disabled
with the static diff setting you could effectively circumvent the check and "steal" from the other miners - thats why its permanently disabled
use theblockfactory.. I 'll be happy to comeback to suprnova... with my gtxs.. For a while I used 0.1 static diff and was ok. I tried 1 week ago still pool not usable for gtx. (ccminer)
Pointed my miners at theblocksfactory. Initially I was disappointed, effective hash rate for myr-gr with ccminer v8.11-klausT was the same 25% of the miner reported hashrate I had seen on suprnova. After changing the bat file to use ccminer v2.1-tribus instead of v8.11-klausT, I'm seeing an average effective hash rate that matches the miner reported hash rate, yes!
I'll be back to dgbg.suprnova.cc if/when it and some version of ccminer myr-gr interact as expected.
Also, something appears to be wrong with the myr-gr algorithm in ccminer v8.11-klausT. If I let theblocksfactory vardiff do it's thing, sgminer, reporting 115MH/s, switches between diffs of .128 and .256. v2.1, reporting 152MH/s, switches between diffs of .128, .256, and .512. v8.11-klausT, running on the same two cards as v2.1 and reporting 163MH/s, switches between diffs of .032 and .064. Even at this lower diff, v8.11 submits many fewer shares in the same time and has an average effective hash rate of 25% of what is reported by the miner. This probably isn't a pool problem as it happens on more than one pool.
Thank you for recommending theblocksfactory.
use theblockfactory.. I 'll be happy to comeback to suprnova... with my gtxs.. For a while I used 0.1 static diff and was ok. I tried 1 week ago still pool not usable for gtx. (ccminer)
Can dgbg.suprnova.cc be fixed to correctly reward work being done with ccminer?
I have a rig with 3 older AMD cards and 2 new 1070s. I'm mining on the AMD cards with sgminer-x11mod, and on the NVidia cards with ccminer-8.11-KlausT. I have a separate worker on suprnova for each of the two sets of cards.
sgminer reports a hash rate of 115 MH/s. ccminer reports a hash rate of 160 MH/s. Both miners are running at difficulty 0.139 (sgminer reports accepted shares with Diff 0.201/0.139, ccminer's last line showing stratum diff change says "Stratum difficulty set to 0.139063") and diff appears to be stable once the miners reach 0.139. ccminer and sgminer get to this diff in about the same amount of time regardless of whether I use the worker password or the "d=0.139" diff setting in place of the password.
After both miners run for 30 minutes, the AMD cards have found 318 shares, 315 accepted, 3 rejected. The NVidia cards have only found 163 shares, 160 accpeted, 3 rejected. In other words, ccminer is hashing 140% faster than sgminer, and only finding half the shares at the same difficulty in the same length of time.
Worker stats on the dashboard look like this:
Worker Hashrate Difficulty
****.***AMD 123,253.49 35.6
****.***CUDA 45,790.61 35.6
I have no idea how the dashboard difficulty of 35.6 relates to the miner reported difficulty of 0.139, at least the dashboard shows difficulty is the same for both miners.
The effective hashrate for the CUDA worker is the main problem on the dashboard. The AMD worker hash rate appears to be correct, it is most often centered around the miner hash rate of 115, + or - 10, with rare outliers as low as 75 or as high as 155. The CUDA worker hash rate is never close to the miner reported hash rate, it is most often centered around 42 (26% of the miner reported hash rate!), + or - 10 with rare outliers as low as 22 or as high as 62.
This degraded hash rate shows up on the suprnova pool when using any of the following versions of ccminer, v2.0-x86, v2.0-x64, v2.1-tribus, and v8.11-KlausT. Playing with ccminer's -f and -m options range from no effect with settings close to 1, an even lower acceptance rate with -m 2, or a >50% rejection rate with -f 2.
Until the problem with ccminer on dgbc.suprnova.cc can be fixed, what other pools are people pointing their miners to for DGB Myriad-Groestl?
I have a rig with 3 older AMD cards and 2 new 1070s. I'm mining on the AMD cards with sgminer-x11mod, and on the NVidia cards with ccminer-8.11-KlausT. I have a separate worker on suprnova for each of the two sets of cards.
sgminer reports a hash rate of 115 MH/s. ccminer reports a hash rate of 160 MH/s. Both miners are running at difficulty 0.139 (sgminer reports accepted shares with Diff 0.201/0.139, ccminer's last line showing stratum diff change says "Stratum difficulty set to 0.139063") and diff appears to be stable once the miners reach 0.139. ccminer and sgminer get to this diff in about the same amount of time regardless of whether I use the worker password or the "d=0.139" diff setting in place of the password.
After both miners run for 30 minutes, the AMD cards have found 318 shares, 315 accepted, 3 rejected. The NVidia cards have only found 163 shares, 160 accpeted, 3 rejected. In other words, ccminer is hashing 140% faster than sgminer, and only finding half the shares at the same difficulty in the same length of time.
Worker stats on the dashboard look like this:
Worker Hashrate Difficulty
****.***AMD 123,253.49 35.6
****.***CUDA 45,790.61 35.6
I have no idea how the dashboard difficulty of 35.6 relates to the miner reported difficulty of 0.139, at least the dashboard shows difficulty is the same for both miners.
The effective hashrate for the CUDA worker is the main problem on the dashboard. The AMD worker hash rate appears to be correct, it is most often centered around the miner hash rate of 115, + or - 10, with rare outliers as low as 75 or as high as 155. The CUDA worker hash rate is never close to the miner reported hash rate, it is most often centered around 42 (26% of the miner reported hash rate!), + or - 10 with rare outliers as low as 22 or as high as 62.
This degraded hash rate shows up on the suprnova pool when using any of the following versions of ccminer, v2.0-x86, v2.0-x64, v2.1-tribus, and v8.11-KlausT. Playing with ccminer's -f and -m options range from no effect with settings close to 1, an even lower acceptance rate with -m 2, or a >50% rejection rate with -f 2.
Until the problem with ccminer on dgbc.suprnova.cc can be fixed, what other pools are people pointing their miners to for DGB Myriad-Groestl?
This pool really sucks with dgb, unbelievable diff bounces like a crazy , hashrate is irrelevant, you get no valuable statistics to check whether it does fairplay.
I am pointing a 5X1070 to this pool for hours, desperately trying to figure out some reasonable index to compare my shares with my reported hashpower it goes down to 24 Mh/s from 185 or so while the miner reports up to 308 it is not luck.
Plus, the interface sucks, you need to log-in to see your worker and for example you can not prove your income to a share holder unless you disclose your password to her, I think the designer doesn't have a clue of what a miner needs in terms of statistics and monitoring or it is just a scam: you point your miner to this horrible server and get what they want to give which is far less than half of the work that your miner is actually doing for them. I will cut this slavery relationship forever.
I am pointing a 5X1070 to this pool for hours, desperately trying to figure out some reasonable index to compare my shares with my reported hashpower it goes down to 24 Mh/s from 185 or so while the miner reports up to 308 it is not luck.
Plus, the interface sucks, you need to log-in to see your worker and for example you can not prove your income to a share holder unless you disclose your password to her, I think the designer doesn't have a clue of what a miner needs in terms of statistics and monitoring or it is just a scam: you point your miner to this horrible server and get what they want to give which is far less than half of the work that your miner is actually doing for them. I will cut this slavery relationship forever.
Whats going on with this pool? Something wrong?
@ocminer: can you check everything is right? just in case... from my side the earnings dropped pretty bad...
@ocminer: can you check everything is right? just in case... from my side the earnings dropped pretty bad...
Hey guys, I need some help.
I'm trying to get SGminer 5.6.1 (windows) to work with Digibyte Myriad-Groestl Suprnova Pool.
I created a bat file that I put into the SGminer folder and here's the contents of it:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
sgminer.exe -I 20 -g 4 -w 128 -k myriadcoin-groestl --no-submit-stale -o stratum+tcp://dgbg.suprnova.cc:7978 -u worker.01 -p workerpw
However I get a few failure notices when I try to start it:
"
error: Clang front-end compilation failed!
Frontend phase failed compilation.
Error: Compiling CL to IR
Failed to init GPU thread 0, disabling device 0
Restarting the GPU from the menu will not fix this.
Re-check your configuration and try restarting.
"
Other notes:
I'm running 3 R9 Fury's and 1 Radeon Pro Duo with driver 16.32 on windows 7
I'm trying to get SGminer 5.6.1 (windows) to work with Digibyte Myriad-Groestl Suprnova Pool.
I created a bat file that I put into the SGminer folder and here's the contents of it:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
sgminer.exe -I 20 -g 4 -w 128 -k myriadcoin-groestl --no-submit-stale -o stratum+tcp://dgbg.suprnova.cc:7978 -u worker.01 -p workerpw
However I get a few failure notices when I try to start it:
"
error: Clang front-end compilation failed!
Frontend phase failed compilation.
Error: Compiling CL to IR
Failed to init GPU thread 0, disabling device 0
Restarting the GPU from the menu will not fix this.
Re-check your configuration and try restarting.
"
Other notes:
I'm running 3 R9 Fury's and 1 Radeon Pro Duo with driver 16.32 on windows 7
I've got also having problem with my rig using rx480, rx570 AORUS 4GB and Nitro+ rx 570 8gb, my rig got BSOD but my other rig with 4x rx480 run smoothly have you guys a solution for this? thanks
Sad to say but suprnova pools have turned to shit lately. I've a lot of miners and it happens more often than not that when I switch coin half of the workers can't get work from the pool. I had to switch to another dgb pool because of this crap and now mona has the same problem. Thank god it's been mostly zcash lately.
I don't know what's going on with the pools, overloaded servers or what but not very excited to point my workers to suprnova pools anymore.
I don't know what's going on with the pools, overloaded servers or what but not very excited to point my workers to suprnova pools anymore.
Hey guys, I need some help.
I'm trying to get SGminer 5.6.1 (windows) to work with Digibyte Myriad-Groestl Suprnova Pool.
I created a bat file that I put into the SGminer folder and here's the contents of it:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
sgminer.exe -I 20 -g 4 -w 128 -k myriadcoin-groestl --no-submit-stale -o stratum+tcp://dgbg.suprnova.cc:7978 -u worker.01 -p workerpw
However I get a few failure notices when I try to start it:
"
error: Clang front-end compilation failed!
Frontend phase failed compilation.
Error: Compiling CL to IR
Failed to init GPU thread 0, disabling device 0
Restarting the GPU from the menu will not fix this.
Re-check your configuration and try restarting.
"
Other notes:
I'm running 3 R9 Fury's and 1 Radeon Pro Duo with driver 16.32 on windows 7
I'm trying to get SGminer 5.6.1 (windows) to work with Digibyte Myriad-Groestl Suprnova Pool.
I created a bat file that I put into the SGminer folder and here's the contents of it:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
sgminer.exe -I 20 -g 4 -w 128 -k myriadcoin-groestl --no-submit-stale -o stratum+tcp://dgbg.suprnova.cc:7978 -u worker.01 -p workerpw
However I get a few failure notices when I try to start it:
"
error: Clang front-end compilation failed!
Frontend phase failed compilation.
Error: Compiling CL to IR
Failed to init GPU thread 0, disabling device 0
Restarting the GPU from the menu will not fix this.
Re-check your configuration and try restarting.
"
Other notes:
I'm running 3 R9 Fury's and 1 Radeon Pro Duo with driver 16.32 on windows 7
Ok, through some trial and error I got pass this stage, however I'm still having issues, on suprnova it does not show a hash rating, nor is it getting any coins.
This is what my .bat files looks like now:
sgminer.exe -I 13 -w 128 -k myr-gr --no-submit-stale -o stratum+tcp://dgbg.suprnova.cc:7978 -u worker.01 -p workerpw
This executes and runs, and everything as far as I can tell looks ok, but I'm not getting a hashrate on my pool(ran it for like 15 minutes), nor is it getting any coins, indicating that it's not mining for the pool.
Any ideas on what I might be doing wrong? Anything stand out that may be missing for my script? Anyone running SGminer w/AMD cards successfully on Suprnova pool? Also, what does the "-w 128" specify??
Hey guys, I need some help.
I'm trying to get SGminer 5.6.1 (windows) to work with Digibyte Myriad-Groestl Suprnova Pool.
I created a bat file that I put into the SGminer folder and here's the contents of it:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
sgminer.exe -I 20 -g 4 -w 128 -k myriadcoin-groestl --no-submit-stale -o stratum+tcp://dgbg.suprnova.cc:7978 -u worker.01 -p workerpw
However I get a few failure notices when I try to start it:
"
error: Clang front-end compilation failed!
Frontend phase failed compilation.
Error: Compiling CL to IR
Failed to init GPU thread 0, disabling device 0
Restarting the GPU from the menu will not fix this.
Re-check your configuration and try restarting.
"
Other notes:
I'm running 3 R9 Fury's and 1 Radeon Pro Duo with driver 16.32 on windows 7
I'm trying to get SGminer 5.6.1 (windows) to work with Digibyte Myriad-Groestl Suprnova Pool.
I created a bat file that I put into the SGminer folder and here's the contents of it:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
sgminer.exe -I 20 -g 4 -w 128 -k myriadcoin-groestl --no-submit-stale -o stratum+tcp://dgbg.suprnova.cc:7978 -u worker.01 -p workerpw
However I get a few failure notices when I try to start it:
"
error: Clang front-end compilation failed!
Frontend phase failed compilation.
Error: Compiling CL to IR
Failed to init GPU thread 0, disabling device 0
Restarting the GPU from the menu will not fix this.
Re-check your configuration and try restarting.
"
Other notes:
I'm running 3 R9 Fury's and 1 Radeon Pro Duo with driver 16.32 on windows 7
Jump to: