I'm not getting any shares after running the miner for more than 20 minutes. Can you let me know how to fix it?
PING is showing 0ms
Topic: Team Black Miner (ETHW ETC Vertcoin Ravencoin Zilliqa +dual +tripple mining ) - page 103. (Read 35049 times)
September 29, 2021, 11:06:47 PM
September 29, 2021, 09:17:24 PM
1.10 is soon ready with API support and improved poolside hashrate on some pools.
Testing on the https://hiveon.net/ pool
Will release tomorrow or Friday
Testing on the https://hiveon.net/ pool
Will release tomorrow or Friday
yes but still no possibility to put in panel, and the team hiveos seems not motivated ...
September 29, 2021, 02:52:35 PM
1.10 is soon ready with API support and improved poolside hashrate on some pools.
Testing on the https://hiveon.net/ pool
Will release tomorrow or Friday
We have moved the type column up to the other stats (mem/temp etc) in v1.10
[moderator's note: consecutive posts merged]
Testing on the https://hiveon.net/ pool
Will release tomorrow or Friday
Long line optimisation is needed. Are you sure "TYPE" column is really that useful? Everybody knows that AMD cards cant use CUDA and all Nvidia cards use CUDA for mining and not OpenCL.
We have moved the type column up to the other stats (mem/temp etc) in v1.10
[moderator's note: consecutive posts merged]
September 29, 2021, 08:43:47 AM
There is some stability problems with 1.09, restarting 2-3 times in 24h. Did not have that with previous versions, same drivers and settings.
432m [2021-09-29 16:35:42.830] Job 755f
432m [2021-09-29 16:35:46.658] Job 7560
432m [2021-09-29 16:35:46.986] Job 7561
432m [2021-09-29 16:35:50.814] Job 7563
432m [2021-09-29 16:35:54. 0m [2021-09-29 16:38:00.408] OpenCL driver version: 470.5
0m [2021-09-29 16:38:00.408] Cuda driver version: 11.3
0m [2021-09-29 16:38:00.408] Cuda runtime API version: 11.2
0m [2021-09-29 16:38:00.408]
0m [2021-09-29 16:38:00.408]
0m [2021-09-29 16:38:00.408]
0m [2021-09-29 16:38:00.408] Welcome to Team Black Miner 1.09
432m [2021-09-29 16:35:42.830] Job 755f
432m [2021-09-29 16:35:46.658] Job 7560
432m [2021-09-29 16:35:46.986] Job 7561
432m [2021-09-29 16:35:50.814] Job 7563
432m [2021-09-29 16:35:54. 0m [2021-09-29 16:38:00.408] OpenCL driver version: 470.5
0m [2021-09-29 16:38:00.408] Cuda driver version: 11.3
0m [2021-09-29 16:38:00.408] Cuda runtime API version: 11.2
0m [2021-09-29 16:38:00.408]
0m [2021-09-29 16:38:00.408]
0m [2021-09-29 16:38:00.408]
0m [2021-09-29 16:38:00.408] Welcome to Team Black Miner 1.09
September 28, 2021, 03:31:52 PM
Long line optimisation is needed. Are you sure "TYPE" column is really that useful? Everybody knows that AMD cards cant use CUDA and all Nvidia cards use CUDA for mining and not OpenCL.
September 28, 2021, 06:09:49 AM
I'm still testing , but this miner is giving me increased hashrates. Originally i also had alot more stale shares on ethermine.
Lowered xintensity to 48 and stale shares are almost non-existent now.
Lowered xintensity to 48 and stale shares are almost non-existent now.
Nice find. --xintensity 48 seems to be abit better on etheremine.
September 28, 2021, 05:20:25 AM
It is only possible for zil due to the small dag and 1/4th fitting into the on die cache.
The rx580 had an adjustable TLB cache that was modified when the card was in compute mode. Not sure about the 6800. We don't have that card yet.
he means the infinity cache from the new AMD series. But as i said, this infinity cache is not useable by any mining software (at the moment)
September 28, 2021, 05:14:09 AM
72mh is impressive if its possible.
Try --xintensity 850 on woolypooly.com. should give above 70MHASH
It is only possible for zil due to the small dag and 1/4th fitting into the on die cache.
The rx580 had an adjustable TLB cache that was modified when the card was in compute mode. Not sure about the 6800. We don't have that card yet.
[moderator's note: consecutive posts merged]
September 28, 2021, 04:02:55 AM
This mode is not available on newer AMD cards. Only the old ones have this option, RX570, RX470 and so on. But since vega56/vega64 this option is not available.
Good. Then 72 MHASH is possible with the Team Black Miner with a small code change.
72mh is impressive if its possible.
It is only possible for zil due to the small dag and 1/4th fitting into the on die cache.
Nothing to do with the cache, no mining software can use it, and no the AMD driver cannot split the dag and took 1/4 in cache and the rest in the normal vram. But you are right this happens with the Zil epoch 0.
September 28, 2021, 03:54:59 AM
This mode is not available on newer AMD cards. Only the old ones have this option, RX570, RX470 and so on. But since vega56/vega64 this option is not available.
Good. Then 72 MHASH is possible with the Team Black Miner with a small code change.
72mh is impressive if its possible.
It is only possible for zil due to the small dag and 1/4th fitting into the on die cache.
September 28, 2021, 03:51:49 AM
This mode is not available on newer AMD cards. Only the old ones have this option, RX570, RX470 and so on. But since vega56/vega64 this option is not available.
Good. Then 72 MHASH is possible with the Team Black Miner with a small code change.
72mh is impressive if its possible.
September 28, 2021, 03:29:56 AM
This mode is not available on newer AMD cards. Only the old ones have this option, RX570, RX470 and so on. But since vega56/vega64 this option is not available.
Good. Then 72 MHASH is possible with the Team Black Miner with a small code change.
September 28, 2021, 02:36:29 AM
My Rx 6800 clocked at 72 Mh / s when mining Zil and back to Eth they clocked at 65 Mh / s but the rigs were crashing.
Did you enable compute mode?This mode is not available on newer AMD cards. Only the old ones have this option, RX570, RX470 and so on. But since vega56/vega64 this option is not available.
September 28, 2021, 02:22:14 AM
My Rx 6800 clocked at 72 Mh / s when mining Zil and back to Eth they clocked at 65 Mh / s but the rigs were crashing.
Did you enable compute mode? September 28, 2021, 01:52:54 AM
We have done some test on pools and intensity. On many pools --xintensity 64 is too high. Hiveon pool gave 4-5% stale shares.
Lowering to --xintensity 32 increased the poolside hashrate around 3MHASH on the rig. v1.10 will have a new dynamic --xintensity wich will remove stales. prelimenary tests show +20mhash poolside. (On pools that don't accept stale shares.)
Lowering to --xintensity 32 increased the poolside hashrate around 3MHASH on the rig. v1.10 will have a new dynamic --xintensity wich will remove stales. prelimenary tests show +20mhash poolside. (On pools that don't accept stale shares.)
Greetings,
Trying again from v 1.06
My Rx 6800 clocked at 72 Mh / s when mining Zil and back to Eth they clocked at 65 Mh / s but the rigs were crashing.
This version v 1.09 is much more stable however I am only mining ETH and for some reason after hours the program closes and I really do not see a log file that allows me to determine what happened. This happens to me on all platforms.
I'm in Nanopool. Any ideas?
You must activate the log with --logfile or -l
September 27, 2021, 08:49:16 PM
We have done some test on pools and intensity. On many pools --xintensity 64 is too high. Hiveon pool gave 4-5% stale shares.
Lowering to --xintensity 32 increased the poolside hashrate around 3MHASH on the rig. v1.10 will have a new dynamic --xintensity wich will remove stales. prelimenary tests show +20mhash poolside. (On pools that don't accept stale shares.)
Lowering to --xintensity 32 increased the poolside hashrate around 3MHASH on the rig. v1.10 will have a new dynamic --xintensity wich will remove stales. prelimenary tests show +20mhash poolside. (On pools that don't accept stale shares.)
Greetings,
Trying again from v 1.06
My Rx 6800 clocked at 72 Mh / s when mining Zil and back to Eth they clocked at 65 Mh / s but the rigs were crashing.
This version v 1.09 is much more stable however I am only mining ETH and for some reason after hours the program closes and I really do not see a log file that allows me to determine what happened. This happens to me on all platforms.
I'm in Nanopool. Any ideas?
September 27, 2021, 08:47:51 PM
I'm still testing , but this miner is giving me increased hashrates. Originally i also had alot more stale shares on ethermine.
Lowered xintensity to 48 and stale shares are almost non-existent now.
I'm running 1.09 right now.
Lowered xintensity to 48 and stale shares are almost non-existent now.
I'm running 1.09 right now.
September 27, 2021, 08:27:19 AM
I have 5 rigs (+ 2.5Gh / s) on flexpool do you have a release date for your 1.10?
Congratulations on advancing your mining software
Congratulations on advancing your mining software
September 26, 2021, 01:24:11 PM
Unfortunately, the poolside effective hashrate (flexpool) was lower overall along with a higher number of stale shares overall so I'm not using
Nicehash, Flexpool, huobipool doesn't pay for stale shares, so you need to use a low --xintensity. We are working on an improved dynamic intensity for these pools. In the meantime you can checkout https://woolypooly.com/ . Small pool that pay for stale shares. The poolside hashrate is really good.
We have done some test on pools and intensity. On many pools --xintensity 64 is too high. Hiveon pool gave 4-5% stale shares.
Lowering to --xintensity 32 increased the poolside hashrate around 3MHASH on the rig. v1.10 will have a new dynamic --xintensity wich will remove stales. prelimenary tests show +20mhash poolside. (On pools that don't accept stale shares.)
[moderator's note: consecutive posts merged]
September 26, 2021, 01:15:50 PM
I am mining wit tbm for 2 days on huobipool with 1070s and 1070tis.On tbm hash rate is higher for 1mh on each gpu ,but on poolside is much ,much lover compared to gminer ,so my profit is much lover with tbm.I am back to gminer.
Jump to: