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

[ZerodayTrader]

    27m [2021-10-14 03:07:19.371] mining.submit: Pool reponded with error
    27m [2021-10-14 03:07:19.371] Error(950395421): Share accepted (stale)

Binance at its finest. Meh,... Will let it run 4 now and see how it goes on, otherwise test tomorrow/later with <1.1x~ and see how that works out. Its just weird that it runs for weeks smooth, and now...

[long2905]

so i got myself a 3080ti today. any plan to add LHR unlock support soon? for now i have to cut short my testing and go back to gminer, which nets aroun 84mh/s on the rog strix 3080ti.

[Ramsete2]

when linux version 1.14 will be released?

[ayiphelmy]

try v1.14..

need linux version

[sp_]

We have created an api v1.1 where you can extract both zil and eth mining stats.

[sp_]

Any plan to add LHR unlock support soon?

Not yet. Nvidia will probobly improve the LHR in the next versions. Instead we are optimizing the AMD 6800XT.
If we can get it up to 80MHASH it will be a gamechanger...

[swogerino]

Any plan to add LHR unlock support soon?

Not yet. Nvidia will probobly improve the LHR in the next versions. Instead we are optimizing the AMD 6800XT.
If we can get it up to 80MHASH it will be a gamechanger...

Wow,that would be impressive to do and it would be a game changer for me too as I own a couple of them currently limited to 64 Mhsh in Phoenix miner but if you make them to 80 Mhsh without using a Ryzen 9 processor which not everyone can afford that would truly be a game changer.

[dle378]

Been running TBM 1.14 with --xintensity 1408 for 17.8 hours now and here are my results below:

  1049m [2021-10-14 13:35:41.390] ID   BOARD   HASHRATE/W   HASHRATE           AVERAGE      SHARES
  1049m [2021-10-14 13:35:41.390] GPU0   3060Ti   425.56 kH/W   65.11 MH/s   65.11 MH/s   291/0/34 (100.00)
  1049m [2021-10-14 13:35:41.390] GPU1   3060Ti   350.15 kH/W   65.13 MH/s   65.13 MH/s   278/0/34 (100.00)
  1049m [2021-10-14 13:35:41.390] GPU2   3060Ti   425.68 kH/W   65.13 MH/s   65.13 MH/s   268/4/34 (98.53)
  1049m [2021-10-14 13:35:41.390] GPU3   3060Ti   353.95 kH/W   65.13 MH/s   65.13 MH/s   286/0/37 (100.00)
  1049m [2021-10-14 13:35:41.390] GPU4   3060Ti   425.66 kH/W   65.13 MH/s   65.13 MH/s   311/0/46 (100.00)
  1049m [2021-10-14 13:35:41.390] GPU5   3060Ti   425.58 kH/W   65.11 MH/s   65.12 MH/s   287/0/42 (100.00)
  1049m [2021-10-14 13:35:41.390]                       2406.58 kH/W   390.73 MH/s   390.74 MH/s   1721/4/227 (99.77)

Is it bad or good that 10% of the submitted shares are stales for miningpoolhub?

[sp_]

Is it bad or good that 10% of the submitted shares are stales for miningpoolhub?

MPH pay 100% for stales so it doesn't matter. But for other pools this intensity can be a problem. Some pools kick you off if the stale share count is more than 5% The stale estimate in the miner window is inaccurate, and poolside stale can vary. This is because every mining pool have their own stale evaluation.

[DrX]

Any plan to add LHR unlock support soon?

Not yet. Nvidia will probobly improve the LHR in the next versions. Instead we are optimizing the AMD 6800XT.
If we can get it up to 80MHASH it will be a gamechanger...

How about other 6000 series cards? 6600 should be quite efficient.

[KillrBee]

I just love how some sad little people on Imgur just go and downvote my mining stat images for TBM...  

Anyway,  here is a screenshot of my AMD rig running TBM 1.14b
https://imgur.com/gallery/dbmhQMR

There's not a lot of tweaking or controls in the Windows AMD driver to overclock these cards, but with the basics it seems to be running really well.

Here's the API results from MiningPoolHub:
   "getuserworkers" : {
      "data" : [
         {
            "difficulty" : 0,
            "hashrate" : 152113.425,
            "id" : 18417###,
            "monitor" : 1,
            "password" : "x",
            "username" : "KXXXX.JadeDragon"
         },
         {
            "difficulty" : 0,
            "hashrate" : 42949.673,
            "id" : 18412###,
            "monitor" : 1,
            "password" : "x",
            "username" : "KXXXX.Seriyu"
         },
         {
            "difficulty" : 0,
            "hashrate" : 356124.372,
            "id" : 18412###,
            "monitor" : 1,
            "password" : "x",
            "username" : "KXXXX.Smaug"
         }
      ],
      "runtime" : 86.09414100647,
      "version" : "1.0.0"
   }
//Smaug is the AMD rig

[sp_]

Are you running with --xintensity  -1? (default) We have improved it in 1.14b

[KillrBee]

Are you running with --xintensity  -1? (default) We have improved it in 1.14b

Yes, the AMD cards are -1 Dynamic

[sp_]

mph has 500 ping on the europe server now. Normally I get ~50 ping

d-dos or something...

How about other 6000 series cards? 6600 should be quite efficient.

The 6600 is already performing pretty good in v1.14b. Why don't you try it out.

[moderator's note: consecutive posts merged]

[KillrBee]

mph has 500 ping on the europe server now. Normally I get ~50 ping

d-dos or something...

It's 46ms for me on us-east.

[ZerodayTrader]

otherwise test tomorrow/later with <1.1x~ and see how that works out. Its just weird that it runs for weeks smooth, and now...

With 1.05 it seems all smooth. Even on my old Profile with Memclock on its absolute Limit.
https://i.imgur.com/cRpn8bw.png

Also funfact on 1.1x; When i let it run with Default Xintensity: less hashrate.

[sp_]

1.1x has a lower default intensity than 1.05 because of less rejected shares on some pools. If you set the --xintensity yourself multiply with 4 in 1.1x

Did you try 1.14b ?

[ZerodayTrader]

1.1x has a lower default intensity than 1.05 because of less rejected shares on some pools.

I know, still had it set to 224 - cuz never touch a running system.

Did you try 1.14b ?

Not yet.  

Edit; Nvm. It was the Beta version, sorry.

[sp_]

The 1.14 beta had  two ulpoads . Make sure you use the latest upload. v1.05 had a slightly different kernel, so might be faster on the old cards. Will check it.

[ZerodayTrader]

It was the "Reupload" version.