 Show Posts
|
|
Pages: [1] 2 3 »
|
That kind of service is definitely worth its price, keeping the wife happy is invaluable anyways... I'll leave you a positive trust rating since I'm 100% sure that you're a trustworthy company and I know you've been in the hosting business for a long time  Thank you! Indeed we are already more then 10 years active in the hosting business and have even more years experience. Do you guys still host mining? How about GPU miners in 4U 19" chassis? (So no open air shit.) Thanks! |
|
|
|
b250 13 x RX5600XT Nitro+ Pentium or i3 4Gb ram couple Gb usb stick 3.x 2x platinum/titanium PSU (1800W combined) mmpos Here is why: https://bitcointalk.org/index.php?topic=5220105.msg53698799#msg53698799I have 5700's, not 5600's. But I'd gladly trade them + some cash in hand  The other components are literally what I use. Why not VII's? I'm assuming better Navi support in time, both driver as miner-wise. BTW, what's the deal with you guys putting threadrippers on a b250?! |
|
|
|
|
Disclaimer: Numbers may vary from card to card and miner to miner.
I'm using '5700' numbers applicable to me and '5600XT' numbers provided in the screenshot by the OP. Rounded.
Electricity $0.30 kW (This is much more than for most people.)
Stock bios.
The 111W used is my "worst" performing card. They can go 10% lower in some cases.
________________________________________________________________
5600XT
75W / 42Mh = 1.785714285714286 Watt per Mh
1.785WMh / 1000 = 0.001785 kW per Mh
0.001785 * $0.30 = $0.0005355 per Mh
Validation test
$0.00005355 * 42 = $0.0225 per hour
$0.30 * 0.075kW = $0.0225 per hour
--------------------------------------------------------
5700 non-XT
111W / 53Mh = 2.094339622641509 Watt per Mh
2.094WMh / 1000 = 0.002094 kW per Mh
0.002094 * $0.30 = $0.000628 per Mh
Validation test
$0.0006282 * 53Mh = $0.0333 per hour
$0.30 * 0.111kW = $0.0333 per hour
--------------------------------------------------------
--------------------------------------------------------
Result
5600XT: $0.0005355 per Mh running cost
5700 non-XT: $0.000628 per Mh running cost
If all these numbers leave you confused at this point, the 5600XT here is better performance. But mind the disclaimer!
________________________________________________________________
NOTE!
Something I didn't include in the calculation is the power used by the fans.
Why is this important?
A blower Fan will easily add another 23 Watt to the power consumption. (30W peak)
For the other fans you'd have to look it up. I personaly would add another 5 Watt per fan in the calculation on average.
If you want to do your own calculations:
Power_consumption / Mh = A
A / 1000 = B
B * Electricity_cost = X
|
|
|
|
Get out of here, you do not have to invest your money in this project - this is the worst project that is, the developers write a fairy tale for themselves and deceive people. Go and find better another project in which you will not lose money invest your money in monero and you will be happy!!! How are you losing money? The only reason I can think of is when you sell at a loss, which is not considered "investing". You just want to get rich quick and get burnt like all these "traders", you're probably also an XRP bagholder, am I rite? Crypto investors want low prices. And don't confuse that with worthless, like XRP. For all the crap this devteam gets, they are consistently bringing updates and progress, which can't be said of many tokens. |
|
|
|
you not see this: ? teamredminer.exe -a cn_haven
Sorry no, I didn't. It won't happen again!! ;-) |
|
|
|
 how this work properly for you? you have vega card.this setings have to small HR for vega. try this : 16+14:AAA or 15+15:CBB teamredminer.exe -a cn_haven -o stratum+tcp://YOURPOOL -u YOURWALLET -p YOURMINER --platform=0 --init_style=3 -d 0,1,2,3 (I have 4 GPUs) --cn_config 16+14:AAA,16+14:AAA,16+14:AAA,16+14:AAA Try 14*13 and 13*13 all my vega 56@64 do 2200+ h/s CNr. A Vega 56 with 64 bios still only has 56 CU's. 1200 clk, 1050 mem, 860mV (one card needs 875mV, so don't fixate too much on the exact number. I started tuning them all at 900mV (Samsung) If they are actual real 64's, then 16*14 should work fine. --cn_config=14*13 --auto_tune=SCAN --auto_tune_runs=2 I notice from your post you are using the + tweak, Vega work best with *
Nonetheless, SCAN will go through every possible tweak for you.
You MUST use cn_config= , without = your custom settings don't apply and the miner will just do a quick short tune with default settings.
The helpfiles that come with TRM are currently somewhat outdated.
Also, if all your cards use the exact same tweak, you don't have set it for every device.
Make sure to set the runs to 2, else it's gonna take a whole day of tuning (6 runs default) at values below optimal.My RX460 2G do, with TRM 0.5.6 + mmpOS over 500h/s(Hynix and Samsung mem, 1000mV, lower than that they all at some point fail. Straps copy/pasted ofcourse.) 4+3 for 16CU and 3+3 for 14CU 4G cards could try 5+4 and 4+4 :BAB is a good default tweak on these cards. |
|
|
|
Is this still a thing or is it already abandoned?
Abandoned thanks! |
|
|
|
|
Is this still a thing or is it already abandoned?
|
|
|
|
Thanks mmpOS! (RX470 8Gb @ 31Mh/s , 76W)  (RX570 4Gb @ 28Mh/s , 82W) 
|
|
|
|
|
Can't update wallet :/
No peers.
|
|
|
|
|
First find out what the power limit on the battery is (19kW/h doesn't tell me if that's the capacity or power delivery. Usually it means the capacity))
Volt x Ampèere(max) = Watt/hour. (deduct at least 10% of that)
Do you even get 500Watt?
Do you need a step-up / step-down to deliver the right amount of Volt to the PSU?
If so, buy or build one.
|
|
|
|
|
With great power comes great OS!
|
|
|
|
Hi! Just curious, did you have time to test 0.5.2 yet? It has a first wave of changes that only aim to stabilize the miner. No real guarantees, only some changes that theoretically should be nicer to the hardware. Otherwise, I agree, we’re dealing with some very delicate issues, and the software/driver/hardware interaction here is not all hunky dory.
Still running!  edit: 1d 4hours on 5.2 and still no dead GPU. I guess we can call it fixed! (?) |
|
|
|
I have the same problem on 4 rigs with 4 various Vega 56 cards (ref with samsun g and asus/powercolor with hynix, with timings and without timings ). The card runs for an hour or two and then the hash rate drops to zero or to 1400 h/s with a DEAD message. I have observed in several rigs, but for some reason problems always with the first PCI slot (PCIe 3:0.0). If you do not stick the card into the first PCI slot (PCI 16x), then the problem disappears. Now I just do not use 16x pci slot  Hi, interesting... for me it is GPU4 and it is located at PCIex16 slot too. LnkSta: Speed 8GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- I have the same problem on 4 rigs with 4 various Vega 56 cards (ref with samsun g and asus/powercolor with hynix, with timings and without timings ). The card runs for an hour or two and then the hash rate drops to zero or to 1400 h/s with a DEAD message. I have observed in several rigs, but for some reason problems always with the first PCI slot (PCIe 3:0.0). If you do not stick the card into the first PCI slot (PCI 16x), then the problem disappears. Now I just do not use 16x pci slot All primary x16 slots on any motherboard always are uplink. What hardware do you guys have? (only for the vega rigs) H110 3da with latest bios (F25), Celeron G3900 (Skylake) all (2) cores enabled. igfx enabled as primary. and a vega 56 in every pcie slot (stock bios, but we've already established bios, settings and algo don't matter). Single channel & single bank 4Gb memstick Crucial. For most of us TRM 4.4 seems to work normally although a teeny tiny bit slower, but it's still better than a whole card not running . 5.2 only just released, so can't say yet. |
|
|
|
Well, it should really only happen when we restart our servers, which isn't often at all. So, there's something else cutting the connection for you. In some cases there are home routers that cut connections, in other cases many countries/jurisdictions don't like neither SSL traffic nor mining traffic. May I ask where you're located? You can PM me if you want to. Also, I'd love to know what version of TRM you're running? We have noticed a higher degree of short-lived inbound connections lately, but can't explain why.
people start autotune, notice they didn't set their own wallet and stop the miner? Just a thought. There's an easy way to test if this is the case. set a minername in the batchfiles that come with the miner. If they forgot to change the wallet, likely they didn't change the miner id either. |
|
|
|
Before the swap
[2019-06-12 11:43:48] GPU 5 [55C, fan 62%] cnr: 1.986kh/s, avg 1.981kh/s, pool 1.887kh/s a:90 r:3 hw:0
[2019-06-12 11:44:18] GPU 5 [55C, fan 62%] cnr: 1.986kh/s, avg 1.981kh/s, pool 1.884kh/s a:90 r:3 hw:0
[2019-06-12 11:44:48] GPU 5 [55C, fan 62%] cnr: 1.986kh/s, avg 1.981kh/s, pool 1.882kh/s a:90 r:3 hw:0
[2019-06-12 11:45:18] GPU 5 [55C, fan 62%] cnr: 1.986kh/s, avg 1.981kh/s, pool 1.880kh/s a:90 r:3 hw:0
[2019-06-12 11:45:48] GPU 5 [54C, fan 58%] cnr: 2.359kh/s, avg 1.980kh/s, pool 1.877kh/s a:90 r:3 hw:0
[2019-06-12 11:45:51] GPU 5: detected DEAD (03:00.0), no restart script configured, will continue mining.
After the swap:
[2019-06-12 18:58:31] GPU 2 [56C, fan 66%] cnr: 1.987kh/s, avg 1.984kh/s, pool 3.603kh/s a:17 r:0 hw:0
[2019-06-12 18:59:01] GPU 2 [56C, fan 62%] cnr: 1.987kh/s, avg 1.984kh/s, pool 3.555kh/s a:17 r:0 hw:0
[2019-06-12 18:59:31] GPU 2 [57C, fan 66%] cnr: 1.987kh/s, avg 1.984kh/s, pool 3.509kh/s a:17 r:0 hw:0
[2019-06-12 19:00:01] GPU 2 [49C, fan 62%] cnr: 2.125kh/s, avg 1.967kh/s, pool 3.463kh/s a:17 r:0 hw:0
[2019-06-12 19:00:03] GPU 2: detected DEAD (13:00.0), no restart script configured, will continue mining.
[2019-06-12 19:24:23] GPU 2 [58C, fan 66%] cnr: 1.987kh/s, avg 1.980kh/s, pool 1.667kh/s a:5 r:0 hw:0
[2019-06-12 19:24:53] GPU 2 [58C, fan 66%] cnr: 1.987kh/s, avg 1.980kh/s, pool 1.601kh/s a:5 r:0 hw:0
[2019-06-12 19:25:23] GPU 2 [57C, fan 66%] cnr: 1.987kh/s, avg 1.980kh/s, pool 1.539kh/s a:5 r:0 hw:0
[2019-06-12 19:25:53] GPU 2 [56C, fan 66%] cnr: 1.987kh/s, avg 1.979kh/s, pool 1.482kh/s a:5 r:0 hw:0
[2019-06-12 19:26:23] GPU 2 [55C, fan 60%] cnr: 2.293kh/s, avg 1.973kh/s, pool 1.429kh/s a:5 r:0 hw:0
[2019-06-12 19:26:34] GPU 2: detected DEAD (13:00.0), no restart script configured, will continue mining.
So this time something a little different happened, but still conforms to my mem clockspeed theory. [2019-06-12 21:08:46] GPU 2 [55C, fan 62%] cnr: 1.988kh/s, avg 1.985kh/s, pool 2.857kh/s a:22 r:1 hw:0 [2019-06-12 21:09:16] GPU 2 [57C, fan 60%] cnr: 1.987kh/s, avg 1.986kh/s, pool 2.838kh/s a:22 r:1 hw:0 [2019-06-12 21:09:46] GPU 2 [56C, fan 62%] cnr: 2.150kh/s, avg 1.985kh/s, pool 2.820kh/s a:22 r:1 hw:0 [2019-06-12 21:10:16] GPU 2 [54C, fan 54%] cnr: 1.550kh/s, avg 1.982kh/s, pool 2.802kh/s a:22 r:1 hw:0 [2019-06-12 21:10:46] GPU 2 [54C, fan 60%] cnr: 1.549kh/s, avg 1.979kh/s, pool 2.784kh/s a:22 r:1 hw:0 ... [2019-06-12 21:14:16] GPU 2 [52C, fan 53%] cnr: 1.549kh/s, avg 1.961kh/s, pool 2.666kh/s a:22 r:1 hw:0 [2019-06-12 21:14:46] GPU 2 [ 47C, fan 43%] cnr: 1.551kh/s, avg 1.950kh/s, pool 2.650kh/s a:22 r:1 hw:0 [2019-06-12 21:14:51] GPU 2: detected DEAD (13:00.0), no restart script configured, will continue mining. Instead of crashing immediatly, it seems the clockspeed got reset to the bios default first. Now I'm gonna swap the 2 cards back to their original place. |
|
|
|
GPU 2: detected DEAD (13:00.0)
completely different card & bus now :/
I'm still using the stock bios btw. Different clockspeeds or voltages don't seem to impact it.
Timing level don't seem to matter either (driver setting, no mod) But I havn't tested for that specifically yet.
Hi! Even though I’m not replying to every message I’m always reading everything. I’m currently testing a few things and have gone through our full commit history from 0.4.4 and forward. We have a few small bug fixes on the way out, but it’s impossible to tell if any of those are the underlying issue here. I’ll reach out to a few of you in pm to see if you can run some test builds. Would love to nail this, if possible. oh hi! I often edit my posts with more info, like I just did now. (So to not spam the thread, I talk a lot.) I added some hashing speed data from the logs. I don't have the logs from before, I deleted them while testing my start_template.bat But I did see the same thing. While copying some of the log data i also noticed there seems to be a temp drop. (below 55C ramp up?) Afterburner is controlling the fans. But i find 3 examples a bit small to go on atm. Although, in migo's log data I see 55C or less too on his crashing card, but no rampup, prolly because he alread is at 2.2k+? I'm gonna do another run, and after that swap the cards back to their origal order. I have no idea how long it will take though. It ran for hours overnight just fine. |
|
|
|
|
GPU 2: detected DEAD (13:00.0)
completely different card & bus now :/
I'm still using the stock bios btw. Different clockspeeds or voltages don't seem to impact it.
Timing level don't seem to matter either (driver setting, no mod) But I havn't tested for that specifically yet.
2nd run since switching the GPU's, And although it's not the same card or bus as before, it is again the one on bus 13
(bus 3 prior to swapping 2 cards.)
The card that is about to fail also always seem to spike in hasrate (by about 200-300h/s) right before crashing.
Before the swap
[2019-06-12 11:43:48] GPU 5 [55C, fan 62%] cnr: 1.986kh/s, avg 1.981kh/s, pool 1.887kh/s a:90 r:3 hw:0
[2019-06-12 11:44:18] GPU 5 [55C, fan 62%] cnr: 1.986kh/s, avg 1.981kh/s, pool 1.884kh/s a:90 r:3 hw:0
[2019-06-12 11:44:48] GPU 5 [55C, fan 62%] cnr: 1.986kh/s, avg 1.981kh/s, pool 1.882kh/s a:90 r:3 hw:0
[2019-06-12 11:45:18] GPU 5 [55C, fan 62%] cnr: 1.986kh/s, avg 1.981kh/s, pool 1.880kh/s a:90 r:3 hw:0
[2019-06-12 11:45:48] GPU 5 [54C, fan 58%] cnr: 2.359kh/s, avg 1.980kh/s, pool 1.877kh/s a:90 r:3 hw:0
[2019-06-12 11:45:51] GPU 5: detected DEAD (03:00.0), no restart script configured, will continue mining.
After the swap:
[2019-06-12 18:58:31] GPU 2 [56C, fan 66%] cnr: 1.987kh/s, avg 1.984kh/s, pool 3.603kh/s a:17 r:0 hw:0
[2019-06-12 18:59:01] GPU 2 [56C, fan 62%] cnr: 1.987kh/s, avg 1.984kh/s, pool 3.555kh/s a:17 r:0 hw:0
[2019-06-12 18:59:31] GPU 2 [57C, fan 66%] cnr: 1.987kh/s, avg 1.984kh/s, pool 3.509kh/s a:17 r:0 hw:0
[2019-06-12 19:00:01] GPU 2 [49C, fan 62%] cnr: 2.125kh/s, avg 1.967kh/s, pool 3.463kh/s a:17 r:0 hw:0
[2019-06-12 19:00:03] GPU 2: detected DEAD (13:00.0), no restart script configured, will continue mining.
[2019-06-12 19:24:23] GPU 2 [58C, fan 66%] cnr: 1.987kh/s, avg 1.980kh/s, pool 1.667kh/s a:5 r:0 hw:0
[2019-06-12 19:24:53] GPU 2 [58C, fan 66%] cnr: 1.987kh/s, avg 1.980kh/s, pool 1.601kh/s a:5 r:0 hw:0
[2019-06-12 19:25:23] GPU 2 [57C, fan 66%] cnr: 1.987kh/s, avg 1.980kh/s, pool 1.539kh/s a:5 r:0 hw:0
[2019-06-12 19:25:53] GPU 2 [56C, fan 66%] cnr: 1.987kh/s, avg 1.979kh/s, pool 1.482kh/s a:5 r:0 hw:0
[2019-06-12 19:26:23] GPU 2 [55C, fan 60%] cnr: 2.293kh/s, avg 1.973kh/s, pool 1.429kh/s a:5 r:0 hw:0
[2019-06-12 19:26:34] GPU 2: detected DEAD (13:00.0), no restart script configured, will continue mining.
Spikes like these first of all make me think the mem clockspeed boosted somehow. Is there a way to track that? (with logging, I'm not gonna watch a graph all day)
|
|
|
|
I think i have same issue (0.5.1). 6 x vega56 with timmings run maybe hour and then crach.
Watchdog GPU 0: stuck in enqueue, reporting.
GPU 0: detected DEAD (03:00.0), will execute restart script watchdog.bat
[2019-06-12 11:45:51] GPU 5: detected DEAD (03:00.0), no restart script configured, will continue mining. Bus 3? What about the others with same problem? H110 d3a mobo, bus 3 is the x16 slot on this mobo. igfx is turned on as primary display adapter. it's always the same card/bus. I'll try switching it around with another vega and see what happens. BTW where can i find some info about setting up a watchdog script (bat)? Like how to send runtime commands to teamredminer. Or the id of the open/running miner? I got bored last night and wrote this if any one wants a setup template @echo off
set ALGO=
set POOL=
set PORT=
set WALLET=
set PASSWORD=x
set DEVICES=
set INTENSITY=
:: !! optional: create logfile(s)? set LOG=YES
set LOG=YES
:: !! optional: reorder GPU's according to bus number. set REORDER=YES
:: !! NOTE! Intensity and Devices will correspond to reorder.
set REORDER=
:: !! optional: works only for cryptonote algos and if pool allows! Otherwise leave blank. (soesn't work with Nicehash)
set RIGNAME=
set DIFFICULTY=
:: !! optional: name of mining pool. (for logfile purposes only. Can be left blank.)
set POOLNAME=
:: !! optional: pause for error message? set PAUSE=YES (Prevents the command window from closing if you have a problem launching the miner.)
set PAUSE=
:: --------------------Change below settings at own risk!--------------------------
set GPU_MAX_ALLOC_PERCENT=100
set GPU_SINGLE_ALLOC_PERCENT=100
set GPU_MAX_HEAP_SIZE=100
set GPU_USE_SYNC_OBJECTS=1
set CUR_YYYY=%date:~10,4%
set CUR_MM=%date:~4,2%
set CUR_DD=%date:~7,2%
if defined PORT set PORT=:%PORT%
if defined DEVICES set DEVICES=-d %DEVICES%
if defined RIGNAME set RIGNAME=--rig_id %RIGNAME%
if defined DIFFICULTY set DIFFICULTY=.%DIFFICULTY%
if not exist LOGS\%POOLNAME% mkdir LOGS\%POOLNAME%
if "%LOG%"=="YES" set LOG=--log_file=LOGS\%POOLNAME%\LOG_%POOLNAME%_%CUR_YYYY%.%CUR_MM%.%CUR_DD%_%ALGO%.txt
if "%REORDER%"=="YES" set REORDER=--bus_reorder
@echo on
teamredminer.exe -a %ALGO% -o %POOL%%PORT%%DIFFICULTY% -u %WALLET% -p %PASSWORD% %REORDER% %DEVICES% --cn_config=%INTENSITY% %LOG% %RIGNAME%
@if "%PAUSE%"=="YES" pause (
) else (
@exit
)
I actually just wanted some structure in my logfiles for troubleshooting these dead GPU issues but ended up with this  |
|
|
|
I managed to solve today "one card crashing issue" on windows 10 Looks like compute mode switch is broken either by script and by swiching it manually in amd "control center" give me same result. So too gets cards too work i need to be in "graphic mode"... But in registry editor : Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318} You can see your cards 0001 0002 etc... and there is "blokchain support setting" or something like that " with "0 value" I think that it is new name of "compute mode" after swichng it to "1 value" everefing still works fine im on 19.6.1 driver I just uninstalled all the AMD software and kept the drivers + a tool that can enable/disable compute mode. Card behaves now. IMO it's wattman causing much of system instabilities. Even if you never 'turned it on', it is still being used. CRAP! It happened again! Guess uninstalling the AMD software didn't fix diddly squat. drivers 19.4.1 TRM versions 4.5 and up. Actually, I came here for the 5.x version yesterday to try and fix the problem. Meanwhile I changed my other rigs to 5.1 too for the autotune, but I only have this problem on my vega rig. Sweet! Don't worry, I'll get there |
|
|
|
|
