⛏Team Black Miner (ETHB3 ETHW ETC VTC KAWPOW FIROPOW ZIL +dual +tripple mining )

[sp_]

Same problem for me.

You can try to run with --xintensity 284 (the default in 1.28)

[dle378]

v1.29
1. Display difficulty change in the miner window.
2. Use ETH+ZIL shares when calculating pool speed and shares per minute.
3. Stratum change to avoid rejected shares on ezil.me and hiveon.net pools.
4. The default --xintensity changed to 144 on NVIDIA to reduce stale/rejected on hiveon, crazypool, flexpool, etheremine and binance pools.

https://github.com/sp-hash/TeamBlackMiner/releases/tag/

TeamBlackMiner_1_29_cuda_11_5.7z
https://www.virustotal.com/gui/file/652cbdb1ba76f4a1364eaaa0141e01da0a93b52f39999ff99f43995dc2a8070b?nocache=1

TeamBlackMiner_1_29_cuda_11_4.7z
https://www.virustotal.com/gui/file/3a58add075188ff9bb4a8eddb7e4f108967484b49f2cb239ccde4fedc4a90767?nocache=1

TeamBlackMiner_1_29_cuda_11_2.7z
https://www.virustotal.com/gui/file/b38b349cf8068f5615e322609bbb0c4a885741ccd6b0bc4172f927098171d74d?nocache=1

TeamBlackMiner_1_29_Ubuntu_18_04_Cuda_11_5.tar.gz
https://www.virustotal.com/gui/file/127a3958d0965fa93d70fef4ec525cae05546aa2ebcbfe7a52a064f99c078d72?nocache=1

TeamBlackMiner_1_29_Ubuntu_18_04_Cuda_11_5.tar.gz
https://www.virustotal.com/gui/file/cae029810937a5c53af1943cac0b15ae297e2e46937f9b71b6e016872d6ea97a?nocache=1

Currently seeing VARDIFF instead of DIFF for Difficulty value in 1.29.



Is this correct?

[symplink]

And still crashing on 6800 xt on 1.29 on hive.
crash_report file:
miner run time: 0                                                                                                                             
pool reply time: 0ms                                                                                                                           
miner_device_number: 0                                                                                                                         
board_name: gfx1030                                                                                                                           
memory: 17 GB                                                                                                                                 
pcie_id: 24                                                                                                                                   
cl_device_index: 0                                                                                                                             
cl_platform_id: 0                                                                                                                             
cl_platform_type: 2                                                                                                                           
cl_platform_version: OpenCL 2.1 AMD-APP (3180.7)                                                                                               
cl_platform_version_major: 2                                                                                                                   
cl_platform_version_minor: 1                                                                                                                   
cl_device_version: OpenCL 2.0 AMD-APP (3180.7)                                                                                                 
cl_device_version_major: 2                                                                                                                     
cl_device_version_minor: 0                                                                                                                     
cl_nv_compute:                                                                                                                                 
cl_nv_compute_major: 0                                                                                                                         
cl_nv_compute_minor: 0                                                                                                                         
cl_sm_count: 36                                                                                                                               
board: gfx1030                                                                                                                                 
temp: 36                                                                                                                                       
fan: 0                                                                                                                                         
core: 0                                                                                                                                       
mem: 0                                                                                                                                         
power: 28                                                                                                                                     
hashrate: 0.00 H/s                                                                                                                             
hashrate (avg): 0.00 H/s                                                                                                                       
accepted: 0                                                                                                                                   
rejected: 0                                                                                                                                   
send buffer: ''                                                                                                                               
send buffer length: 0                                                                                                                         
recv buffer: '{"id":3,"result":true,"error":null}                                                                                             
'                                                                                                                                             
recv buffer length: 75                                                                                                                         
recv buffer more data flag: 527881048   

[sp_]

Currently seeing VARDIFF instead of DIFF for Difficulty value in 1.29.
Is this correct?

No This might be a small bug. I think MPH have a static diff. Will check it.

Same problem for me.
Windows 10, 496.79, 3080 No LHR, ethermine.

So I reproduced this on etheremine when testing the new LHR unlock for 3080ti on maximum oc. I reverted a change in the code and it seems towork now. Will include the fix in 1.30.

The LHR2 unlock with the latest drivers (windows 497.09) will have 3 or more modes.

3080ti

LHR1: 72MHASH
LHR2: 75MHASH
LHR3; 78MHASH
LHR4: not yet stable.

The current beta version will reset the unlock every 5 minutes. Because we haven't made a way to detect LHR yet.

Enable with --lhr-unlock [0,2,3,0]

Power around 230 watt.

Will be released in v1.30. Note that older drivers can give better results, but we want to try to do it on the latest driver.

[wasarianta]

no... it's windows 10

Which pool? AMD or nvidia?

All our testrigs run fine all night with 1.29.

2miners and nvidia

Same here.. working fine now.. mayb just 1 rare case... i try to look more on logs and windows event but found nothing.. this 1.29 version a lot better now... hope more improve for the next release ..diff (varr/static) are incorrect, adding share diff check or made diff number in common read.., more human read on job...
Hashrate more realistic now somewhere between GM and TX.... i find out hashrate/w sometime up and down even the hashrate are stable... mayb it just the way miner calculate from the average hashrate..

Good job dev..

[PsKminer]

Same problem for me.

You can try to run with --xintensity 284 (the default in 1.28)

It works. 

I will try the lhr-unlock again in the next version.

[long2905]

cant wait to try it out. 100mh unlock on 3080ti would be insane

[sp_]

cant wait to try it out. 100mh unlock on 3080ti would be insane

Not 100 in v1.30, but stable ~80-85 on all drivers. The problem left is that each rig need manual tuning to get it right. Our code is also missing detect LHR, so our only option is to reset the device every 10-30minutes or more, and hope the unlock will stay unlocked.

[ayiphelmy]

what is the meaning of gpu range.. i see in red color?

[sp_]

Just some debug output we forgot to remove. Don't worry about it.

[sp_]

It works. 

I will try the lhr-unlock again in the next version.

LHR cards are a pain. Take forever to find the perfect settings, but here is a preview of v1.30

[ayiphelmy]

Just some debug output we forgot to remove. Don't worry about it.

ok thank you

[hashatharias]

I'm testing v1.29 on HiveOS with two rigs on 2Miners

one with Nvidia Only, all good, whether I use Xintensity 448, 1024 or 3108
and another with one RX5700XT and this one will only mine consistently if I use Xintensity 448 or below.
Above 448, it ends up crashing and upon restarting, the Dag is reported corrupted, and it enters a miner restart loop.

Would there be a way to allow my AMD card to mine consistently with a high intensity ?

Thanks


00:00:00 [2021-12-03 07:50:47.141] GPU4 DAG generated in 2.52 seconds (4792317kb)
00:00:00 [2021-12-03 07:50:47.141] GPU4 Autoselect kernel activated
00:00:00 [2021-12-03 07:50:47.141] GPU4 XIntensity set to 2048
00:00:00 [2021-12-03 07:50:47.141] GPU5 DAG generated in 2.52 seconds (4792317kb)
00:00:00 [2021-12-03 07:50:47.141] GPU5 Autoselect kernel activated
00:00:00 [2021-12-03 07:50:47.141] GPU5 XIntensity set to 2048
00:00:00 [2021-12-03 07:50:47.142] GPU3 DAG generated in 2.52 seconds (4792317kb)
00:00:00 [2021-12-03 07:50:47.142] GPU3 Autoselect kernel activated
00:00:00 [2021-12-03 07:50:47.142] GPU3 XIntensity set to 2048
00:00:00 [2021-12-03 07:50:53.925] GPU0 DAG generated in 10.22 seconds (4792317kb)
00:00:00 [2021-12-03 07:50:53.926] Job 5578
00:00:00 [2021-12-03 07:50:53.926] GPU0 XIntensity set to 2048
00:00:00 [2021-12-03 07:50:53.926] GPU0 XIntensity set to 2048
00:00:00 [2021-12-03 07:50:53.967] Difficulty changed to 2.03
00:00:00 [2021-12-03 07:50:55.474] GPU5 Dag buffer verified ok!
00:00:00 [2021-12-03 07:50:55.567] GPU2 Dag buffer verified ok!
00:00:00 [2021-12-03 07:50:56.036] GPU4 Dag buffer verified ok!
00:00:00 [2021-12-03 07:50:58.294] GPU3 Dag verification failed. Exiting...

My OC is set to begin after 30 sec, but I assume this is only at boot time ?

[sp_]

and another with one RX5700XT and this one will only mine consistently if I use Xintensity 448 or below.
Above 448, it ends up crashing and upon restarting, the Dag is reported corrupted, and it enters a miner restart loop.

The AMD intensity needs to be 1/4th of the nvidia intensity. so 448 is the same as 1792.

To reduce dag validation error you can try --dagintensity 1 ,  or with a low number. This will slow down the dag memory buffer creation, but is stable on higher clocks

 

[hashatharias]

I'll try that, thanks for the swift reply.
Can I specify an intensity of say 4000 for my NVidia and 1000 for my AMD ? or do I need to create two miners configurations?

[sp_]

No you can keep them in the same config. f.ex rig with 4 cards,  Amd in device 0 and 3 nvidia cards --xintensity [1024,4096,4096,4096]

Run with --list-devices to see the correct order.

[long2905]

It works.  

I will try the lhr-unlock again in the next version.

LHR cards are a pain. Take forever to find the perfect settings, but here is a preview of v1.30

https://i.ibb.co/cTcLddy/unlock-tbm1-30.png

nice job! please keep it up and unlock more if possible. currently with trex i can get up to 94 and fluctuate between 91-94.
https://i.imgur.com/FEWEe26.png

[sp_]

nice job! please keep it up and unlock more if possible. currently with trex i can get up to 94 and fluctuate between 91-94.

Not on the 497.09 driver. T-rex is only doing 40MHASH  

[long2905]

admittedly this is on 496.49. i just added a 1060 into the mix and it was quite a pain. finally got everything optimized for now so too lazy to try the latest driver. but its not 40mhs bad. you gotta tune your oc in that case.

[sp_]

The T-Rex unlocker isn't working on the latest driver for the 3080ti





Tbm is +80% faster on the 3080ti with the latest drivers. LOL