⛏Team Black Miner (ETHB3 ETHW ETC VTC KAWPOW FIROPOW EVRPROGPOW MEOWPOW +dual)

[KillrBee]

Not a huge issue or anything, but in version 1.31 I'm getting the message "GPU# XIntensity set to ####" twice for each AMD card.

[sp_]

Not a huge issue or anything, but in version 1.31 I'm getting the message "GPU# XIntensity set to ####" twice for each AMD card.

Fixed in v1.32.

I just recieved a 3070LHR today so will finetune abit before releasing 1.32. The LHR detection and reset device is working pretty good. The 3080ti almost never goto LHR mode, so our LHR code is stable even on the latest drivers.

[sxemini]

Is there a failure in the API? For my nvidia rig the API show me the realtime hashrate, but on my AMD test rig it shows the average hashrate. So AwesomeMiner show me the wrong hashrate -> we need the realtime hashrate.
Maybe you can add the average hashrate also to the API, to see both. Maybe it is better to ask patrike from AwesomeMiner.

[sp_]

Is there a failure in the API? For my nvidia rig the API show me the realtime hashrate, but on my AMD test rig it shows the average hashrate. So AwesomeMiner show me the wrong hashrate -> we need the realtime hashrate.
Maybe you can add the average hashrate also to the API, to see both. Maybe it is better to ask patrike from AwesomeMiner.

We report the hashrate in out API, currently the average hashrate. The realtime hashrate can be added later, but why do you need it?

[sxemini]

Is there a failure in the API? For my nvidia rig the API show me the realtime hashrate, but on my AMD test rig it shows the average hashrate. So AwesomeMiner show me the wrong hashrate -> we need the realtime hashrate.
Maybe you can add the average hashrate also to the API, to see both. Maybe it is better to ask patrike from AwesomeMiner.

We report the hashrate in out API, currently the average hashrate. The realtime hashrate can be added later, but why do you need it?

All other miners show the acutally hashrate and not the average hashrate. Example: the rig runs for 5 days with 120mh -> so average hashrate is 120mh, but for any reason, some cards begin to struggle and hash with the half hashrate, than it needs hours to see the hashrate drop. I hope you understand what i mean.
AwesomeMiner show realtime hashrate for all miners, and average only as an extra if available.

[sp_]

All other miners show the acutally hashrate and not the average hashrate. Example: the rig runs for 5 days with 120mh -> so average hashrate is 120mh, but for any reason, some cards begin to struggle and hash with the half hashrate, than it needs hours to see the hashrate drop. I hope you understand what i mean.
AwesomeMiner show realtime hashrate for all miners, and average only as an extra if available.

Yes, but our average hashtrate is not the average since the miner started, but the last 2000 jobs sendt to the gpu. We increased it because of the LHR mode which is fluctating alot.
But I see your point. Can reduce the samplerate in the next version,

[sxemini]

All other miners show the acutally hashrate and not the average hashrate. Example: the rig runs for 5 days with 120mh -> so average hashrate is 120mh, but for any reason, some cards begin to struggle and hash with the half hashrate, than it needs hours to see the hashrate drop. I hope you understand what i mean.
AwesomeMiner show realtime hashrate for all miners, and average only as an extra if available.

Yes, but our average hashtrate is not the average since the miner started, but the last 2000 jobs sendt to the gpu. We increased it because of the LHR mode which is fluctating alot.
But I see your point. Can reduce the samplerate in the next version,

Ok ok nice. Thanks for you support.

I will test your miner this days with my new RTX3070´s. I come back later with some hashrates 

[ekgd39]

All other miners show the acutally hashrate and not the average hashrate. Example: the rig runs for 5 days with 120mh -> so average hashrate is 120mh, but for any reason, some cards begin to struggle and hash with the half hashrate, than it needs hours to see the hashrate drop. I hope you understand what i mean.
AwesomeMiner show realtime hashrate for all miners, and average only as an extra if available.

Yes, but our average hashtrate is not the average since the miner started, but the last 2000 jobs sendt to the gpu. We increased it because of the LHR mode which is fluctating alot.
But I see your point. Can reduce the samplerate in the next version,

Ok ok nice. Thanks for you support.

I will test your miner this days with my new RTX3070´s. I come back later with some hashrates  

I use it on 3080 and 3070, but I have so much rejects,  use xint from - 1 to 284 on ezil pool, only eth without zil. Mining submite , pool responded with error

[sp_]

ezil.me standalone support was added in 1.31. Make sure you are on the latest version. For config look in the example bat file

[ekgd39]

ezil.me standalone support was added in 1.31. Make sure you are on the latest version. For config look in the example bat file

I use 1.31 ((( use 7 kern on 3080 and 3070 , what xint I can use ?(( hive os 470.86 drivers
This only on ezil pool, on hive it's ok

[sp_]

ezil.me standalone support was added in 1.31. Make sure you are on the latest version. For config look in the example bat file

I use 1.31 ((( use 7 kern on 3080 and 3070 , what xint I can use ?(( hive os 470.86 drivers
This only on ezil pool, on hive it's ok

xintensity is pool dependent. on f2pool,2miners, miningpoolhub and nanopool you can use up to 4096 without rejects. (Nvidia) For amd divide by 4. (1024)

[fluffier]

Hello,

With a rx 6800 and a rx 590 i get plenty of invalid shares on 1.31. Hashrate has also gone down with latest versions. I am back to version 1.27.

Other miners have the -d command to choose which gpus you want to use with mining. How do i choose which ones to use with this miner? Lets say i have gpu0, gpu1 and gpu2 and i want to use only gpu1 and gpu2.

By the way you miner is the only one that stable with my rx 6800. Thank you for that.

[ekgd39]

ezil.me standalone support was added in 1.31. Make sure you are on the latest version. For config look in the example bat file

I use 1.31 ((( use 7 kern on 3080 and 3070 , what xint I can use ?(( hive os 470.86 drivers
This only on ezil pool, on hive it's ok

xintensity is pool dependent. on f2pool,2miners, miningpoolhub and nanopool you can use up to 4096 without rejects. (Nvidia) For amd divide by 4. (1024)

you have to work on stability and compatibility, in particular with ezil.me, there are a lot of rejections. Plus, I noticed that from the start the miner shows excellent results, but then slides significantly below the declared hash rate in the miner. The idea is good, but we have to work, good luck to the developers, and I have to use LOL miner or Gminer.

[ayiphelmy]

baby steps. keep it up. i noticed that for trex, lhr unlock performance is not as good on the latest driver. it stays at 73 stable while it could get up to 76 on previous drivers. the number here is the LHR unlock %

I get 72.5 after a while with the latest t-rex on the latest driver with autotune. This might not be the optimal settings t-rex, but I do use the same settings in TBM and get a hashincrease.

3080ti;

core: 0 default
mem: (+1000) 10500mhz
pl: 70% power

lhr-unlock [1] = 81 MHASH stable for 1  hour.
lhr-unlock [1]  --tweak [1] = 85 MHASH stable for 8-15 minutes.

Been running rock stable all night with  -lhr-unlock [1]. We will do a linux build and release today. In the next version we probobly will add
a LHR detector, and reset the device automaticly. Then we migth be able to do 85 (90 with 11000 mem) stable. on the latest driver.

need more improvment.... 88-90 mhs on t-rex

[sp_]

need more improvment.... 88-90 mhs on t-rex

Not on the latest driver. I only get 72.5 when running t-rex on windows with autotune in (497.09)
v1.32 will have LHR detection and reset device when the gpu goes into LHR mode. Then it's easier for the miner to find the optimal tweak / lhr value.
Next up is autotune.

you have to work on stability and compatibility, in particular with ezil.me, there are a lot of rejections.

ezil.me worked good in earlier versions, but after doing small modifications to fix the hiveon pool it seems to break ezil. Will take another look

But you might consider changing the pool to get the most out of your cards with TBM...

here from a happy user:

pool: 2miners.com

--xintensity 6144 (without poolside stale shares and 100% accepted) (10 hours of running) ~90watt

[ayiphelmy]

need more improvment.... 88-90 mhs on t-rex

Not on the latest driver. I only get 72.5 when running t-rex on windows with autotune in (497.09)
v1.32 will have LHR detection and reset device when the gpu goes into LHR mode. Then it's easier for the miner to find the optimal tweak / lhr value.
Next up is autotune.

this is what i get from t-rex

[sp_]

this is what i get from t-rex

Slow.. Why isn't it 100++?. We do the unlock different than t-rex and will probobly end up over 100 when the code is done.

My comment from 10 days ago..

Getting closer to a 90-100MHASH unlock on 3080ti LHR2
Hashrates fluctate, but stable without triggering the LHR for ~5 minutes at 100% tdp.

[ayiphelmy]

this is what i get from t-rex

Slow.. Why isn't it 100++?. We do the unlock different than t-rex and will probobly end up over 100 when the code is done.

My comment from 10 days ago..

Getting closer to a 90-100MHASH unlock on 3080ti LHR2
Hashrates fluctate, but stable without triggering the LHR for ~5 minutes at 100% tdp.

in 5 minute i got more than 100 mhs with t-rex , i hope u ca do better than t-rex bro, so far u have a good job!!!

[fluffier]

Can gpu's be chosen with this miner or not?

[sp_]

Can gpu's be chosen with this miner or not?

--cuda-devices [0,1,2,3] or short option -U
--cl-devices [0,1,2,3] or short option -Y

hiveos use the short option.

to see the correct index, run tbminer --list-devices