 Show Posts
|
|
Pages: [1]
|
but the problem its in 4 rigs, all GPU0 with diferent set in core and mem, its not the core
try v1.60. Which pool, and which intensity? 2 rigs in 2miners xintensity 4096, 1 flex xintensity 512 , 1 flex xintensity default I will try v1.60 next weakend |
|
|
|
hi, i have this question, in 4 rigs of rtx 3090 have this, drop in hash always GPU 0, screen of two, this if from comicion of miner?
Try to increase the coreclock to above 1500. 1580?. Higher core gives a slightly higher voltage and stable hashrates on the rtx 3090. ------------- The rejected shares on the hiveon.com pool seems to finally been fixed in this version. Does anyone get rejects there in 1.60? but the problem its in 4 rigs, all GPU0 with diferent set in core and mem, its not the core |
|
|
|
Here's another example
I fail to reproduce this on my testrigs. Tried --xintensity 4096 to force the timeout, and the first timeout will appear but no crash after the gpu reset.It's probobly only reproducable on the 2miners.com pool. In debug I see that 2miners don't like to have the fee mining thread open, so it keeps restarting. Perhaps a workaround would be to mine the devfee on another pool. hi, i have this question, in 4 rigs of rtx 3090 have this, drop in hash always GPU 0, screen of two, this if from comicion of miner?   |
|
|
|
Can someone explain to me the process behind tbm devfee? I understand the interval system, the mining soft stops the user's mining for a few seconds to mine himself for the dev. But, tbm takes fees continuously and I don't really understand the process behind it. How do you charge fees when the user is mining? Sorry, if it's a dumb question  I believe TBM takes hashes during startup of the miner during DAG validation. There might be something that happens around 3 hours that splits the hashrate for a bit as I am noticing a consistent but transient drop-off in performance about every 3 - 3.5 hours of mining. But they don't switch pools like other miners do (and lots of users abuse that payment by either stopping and restarting the miner, or blocking the IP that the miner will switch to), and since I have spent a lot of time (and continue to spend time as TBM gets updated so often) tuning TBM my profits are significantly higher than any other green or red mining software -- especially on my 3090 which gets a consistent 133+ MH/s and I could probably push it to 137+ if I wanted to get close to bumping up against thermal throttling. For example, the following is a current screenshot of the miner output for my 3090 card: 15.5 hours of mining on 2Miners.com which calculates shares to hashrate as 145.4 MH/s for 1 share / min.  870 shares in 936 minutes = 0.9355 shares / minute => 145.4*0.9355 == 136 MH/s average Sorry mate but this not the calculation for your mining speed  Show us your poolside hashrate, this is important. Why no one in this thread show us his poolside hashrate? mysterious 2Miners has vardiff in my opinion - so countshare is senseless  And i tested this dump miner also - show 8% higher hashrate - poolhashrate was 5% lower than any other miner. And nothing more is important. @sp__ very strong arguments or proofs - not the usage numbers of your miner show us how good your miner is. hash in hiveos and pool hiveos rtx x6 3090 asus rog  2min (average varie from 740mh to 780, some days more some less)  |
|
|
|
If you give me some of that hashrate I'll throw you a couple of hints! :-)
But because I'm a nice guy here's a couple quick ones for free:
Increase your clock to 1600 ~ 1750, it's the only way to mess around with voltages on Linux
Don't use Cuda 1.15 on linux, for whatever reason it performs much worse than 1.14 -- but in windows 1.15 works much better apparently.
Lower your intensity a bit, try 3800
there is no place for a lot of heat in the room, 3 x6 rtx 3090 rigs and another x7 rtx 3070 non lhr, thanks for the advice, I will try intensity 3800 |
|
|
|
 Second -- Check out that 3090 hashrate for almost 6 hours of mining! Nice hashrate. I think the 2060S needs to be clocked lower because you have some rejected shares there. It's the cuda code that is crashing, not the AMD code. I think the 2060S is clocked to high. try 7900 or 7800 memclock. I could perhaps include a GPU # in the error message that will track wich of the gpu's that crashed the rig. any advice to improve is welcome   and this rig run v1.50 hiveos, only set --xintensity 4096  whats its the diference v1.54 an v1.54cuda115 ? |
|
|
|
The following (minus the obvious) command: ./TBMiner --algo ethash ... -Y 3 --xintensity 1000 --log, resulted in:
Use brackets around the gpu selector -Y [3] ------------------------------------- Can somebody please share setup multiple 3070 (I have 8x3070 (original ones) and Afterburner clocks, as Im still getting lots of dag errors and stales.
One of the cards in the rig needs to be clocked lower than the others so that the dag buffer is created without errors and loaded onto all of the other gpus without errors. My 3070 LHR can run with up to 8300 Memclock if the dag is created on the 3080ti. (T-rex is crashing at 8100) But if your rig is only 3070 cards, let one of them run at 7800 to create the dag buffer. Stale shares can be removed by lowering the --xintensity or switching the pool. This image was created in p2 mode. But after set my cards in P0 mode, I could clock it even higher  -------------------- new fixed build with working lhr-unlock for linux uploaded https://github.com/sp-hash/TeamBlackMiner/releasesTeamBlackMiner_1_50_Ubuntu_18_04_Cuda_11_4_fixed.tar.xz https://www.virustotal.com/gui/file/3af45ac62fc80c2b214152424ffdfc690c7e3117689ada1bf4dc96713277c4e0?nocache=1i have rig of x7 rtx 3070 vulcan, non lhr , use for this gminer 441mh, with tbm have problem dag failed, i try 1.28 at 1.35v, now try last version 1.50, same problem dag failed , i try --dagintensity 1 |
|
|
|
What do you recommand for a 3080FE and 3090Fe on miningpoolhub ? (xintensity/tweak/kernel) Thanks
rtx 3090 --xintensity 3000 --kernel 1 or 12. Run the autotune a few times to verify. The best kernel depends on your power settings. rtx 3080 --xintensity 2500? --kernel 1 or 12. Run the autotune a few times to verify. The best kernel depends on your power settings. try without tweak first, if you get stale shares incease the tweak to 4 or more can you add dual mining toncoin + eth, same as lolminer? |
|
|
|
autotune will help so...... much and will you make autotune kernels be dynamic something like --xintensity [-1] or at least at periodic time or epoch change or whatever haha no idea..
what now --dagintensity in v1.35 are have effect .. well i will find out..
The problem with the current autotune is that it runs for a too short time. Ideally it should run for minutes and not seconds. The problem is that the hashrate is reduced abit when trying out bad configurations. We don't have all the cards and models, so our solution is to create a program that will try to calcuate the best settings automaticly, or let you configure it yourself. Nothing beats Human testing. V1.35 have 4 tuning options. Different cards have different optimal settings. Different power settings have different optimal settings. Different pools have different optimal settings. --kernel (0-9) --xintensity (0-10000) / (0-2500 amd) --tweak (0-8) --dagintensity (0-9) / (0-8 amd) So tune and be rewarded  testing v1.35 now in 2miners(2 days run), get more hash average 760mh, 778reported (rtx3090x6), but get les reward vs flexpool(get more ETH), in flex average 740mh 2% stales, runing same config same oc, only run --xintensity 4096, Any recommendation? |
|
|
|
try with --dag-intensity 1 --lock-cclock [[1200,1200],[1200,1200]]
hi, first thanks for the miner, really good, now testing x6 rtx 3090 in flexpool 133mh to 135 best card, only runing --xintensity 512 , less than 2% stales, with its the best kernel and dag for last version of the miner? thanks |
|
|
|
|
