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

[snoby67]

thanks!  this is very good news!  I promote TBM among the Russian miners community.  already have satisfied users.  

Thanks for your support. v1.22 has been added to hiveos.

Can you try v1.22?. Should work now.

I will try it when it will be added to HiveOS (:

Added to hiveos now.

Yep, I try with my bug on mixed rig... AMD cards still not work.
My AMD devices are 5, 6 and 7 (see the picture hereafter)
https://ibb.co/F5RncyJ
-Y [5,6,7] : no device are set
No problem on nvidia cards.

Only -b is working, so the nvidia cards should stay on other miner :-(

[KillrBee]

I'm noticing a significant drop in share /poolside-hash rate with the Windows 1.22 build over 1.20 with the same settings on my 3090.

1.20 was running at around 132MH/s on the poolside over 24+ hours, while 1.22 over the same time period was running at around 122 MH/s.  Client side the Hashrates are the same, but the time per share is much longer, and there are bigger and deeper drop-out periods (where I might not get a single share in 5 minutes).  Has anything significant changed between the two versions for Nvidia cards?

[sp_]

no. But you should check the pool. The hiveon pool just reduces the stales payout from 80% to 50%, so perhaps 2miners is doing something similar. There was a few hours downtime yesterday on the www frontend, perhaps the pool was under attack or something.

[DmKa]

AMD RX 580 still doesn't work. In Riga there are 5700 and one 580. So, because of the leapfrog with the numbering, I can't even transfer 580 to another miner.

A completely raw product.

[KillrBee]

no. But you should check the pool. The hiveon pool just reduces the stales payout from 80% to 50%, so perhaps 2miners is doing something similar. There was a few hours downtime yesterday on the www frontend, perhaps the pool was under attack or something.

I'm running instances for 30 minutes of 1.20 vs 1.22 against the same pool and during every run I see about 25 shares / 30 mins on 1.22 and 32 shares / 30 mins on 1.20, so there's something in the miner that is functioning differently with the 3090...  Might it have something to do with the LHR code being applied to a non-LHR GPU?

[sp_]

which kernel are you on? Perhaps the autotune is selecting a different one in v1.22?

[KillrBee]

which kernel are you on? Perhaps the autotune is selecting a different one in v1.22?

I have it manually set to 8

[sp_]

Ok.I will check it. LHR unlock code should not run, and if it's running it will hurt the performance.


All my testrigs are running stable on v1.22 without any issue. The only thing I could find was that the first few rounds are not running on kernel 8 but kernel 0. This shouldn't be a problem, but I have corrected this in v1.23.

We did a stratum change in v1.22, and I will test some more with only one card.

[moderator's note: consecutive posts merged]

[KillrBee]

All my testrigs are running stable on v1.22 without any issue. The only thing I could find was that the first few rounds are not running on kernel 8 but kernel 0. This shouldn't be a problem, but I have corrected this in v1.23.

We did a stratum change in v1.22, and I will test some more with only one card.

Okay, what I'll do is run another set of longer tests with the 1.20 and 1.22 versions and correlate the 2Miner API output to see if it was just a luck issue that happened to be apparent when I was running 1.22. (such is the world of crypto and continuous probability - good thing I wound up finally liking and learning probability theory after I left university!)

I'll send you the details of both runs when I get the data.

[daz31]

Hi guys,

I've set TBM on my first RIG and everything is good. On my 2nd RIG, i've got this error message: Cuda error out of memory.

Both RIG are running HiveOS, with 4Gb RAM.

Do you know how to solve this problem ?

[sp_]

What cards are you running in the rig?

[daz31]

7 x 3070
4 x 3060Ti
1 x 3080

No LHR cards  

[sp_]

what is your launch config? The gpu is out of memory, not the computer

[daz31]

what is your launch config? The gpu is out of memory, not the computer

Standard config for Ethermine pool (ETH), GPU 4 and 6 disabled as they're mining other crypto.

[sp_]

GPU 4 and 6 disabled as they're mining other crypto.

The device order might be different that on other miners

use

tbminer --list-devices

to list the correct id's

and

--cu-devices [0,1,2,3...]  to select the devices you want to mine with.

make sure --auto-select is not set.

[daz31]

With --cuda-devices [0,1,2,3...]  to select the devices i want to mine with, it's working perfectly ! So the option Disable GPU in HiveOS configuration panel seems to not work.

Thanks sp_   

[snoby67]

What about the bugged command --cl-devices or -Y? Do you have a deadline to find an issue ?

[XyeetmanX]

What about the bugged command --cl-devices or -Y? Do you have a deadline to find an issue ?

Yeah this is issue I'm having

Like first rig amd gpu are gpu0-1 then on rig2 gpu0 is nvidia and when loading miner to get correct settings on first rig will give rig2 incorrect settings so it's difficult to used mixed rigs

[sp_]

What about the bugged command --cl-devices or -Y? Do you have a deadline to find an issue ?

Like first rig amd gpu are gpu0-1 then on rig2 gpu0 is nvidia and when loading miner to get correct settings on first rig will give rig2 incorrect settings so it's difficult to used mixed rigs

This was fixed in v1.22. Working fine here...

If you have a opencl and a cuda selection in the same launch config the Opencl devices will be selected first.

In the picture I am running with  --cu-devices[1] --cl-devices [5]


gpu0: rx 580 AMD (cl-device #5)
gpu1: gtx 2060  (cuda device #1)

-Y [5,6,7] : no device are set

Are you sure you are using the correct version?

[ZerodayTrader]

Still same with unmineable.

https://i.imgur.com/Gcvq3SL.png

Thats just weird as hell... Give it a try on your own, maybe its same issue. I dunno.

Will test now with "ETC" and check if the GPU is shown there.

Edit; Not showing up under ETC either as expected.