 Show Posts
|
|
Pages: [1]
|
Hi guys, I have 2 exactly the same rig, one of them is stable as rock, the other is freezing 0.5 - 2 a day I don't know why. Please help me to find a soultion. I have tried what you wrote before but nothing changed. I set up the reboot script but in this situation it is not working. Thank you in advance! http://ballai.hu/image1.jpghttp://ballai.hu/image2.png |
|
|
|
Hi guys, While I use v18, I get this error.  The vga params are the same as in v17 (7x1070, power limit 100, proc: -200, mem: +1100). In v17 it was stable as rock for weeks. The problems: - I use watchdog param but it is not restarting - once restart after 8 hours - ctrl+c does not work - in the first 10 minutes I can reboot from console - I can not use teamviewer Please help me to find a solution. Thank you ind advance! |
|
|
|
Okay, so you are using the autotemp, but did set INDIVIDUAL_POWERLIMIT="NO" ?
This can give a problem, to set autotemp correctly it needs this set to YES.
I set the temp control to set in line 51 and set the individual to yes in line 145 I set all the lines below to 100. I set all the target temp to 60 (this is the old v17 measured value) nand set restore to 20 in line 237. Question: what does orginal power limit means? The card's default 125? Or powerlimit_watts in line 74? Thank you! |
|
|
|
|
I continue the above: if I set it with my hand, it is ok BUT just for 1-2 minutes and anything changes it back to 125!
|
|
|
|
Are you using the new V0018? Did you made a new img, or just used a new oneBash? What version did you have before? If you used V0017 or before, perhaps you did not change the autotemp file? The first version had it's own power limits set at 125W. Can you please try the following: SSH into your rig or open a guake terminal, and enter: nvidia-smi will give you output, probably telling that the power limits are now set to 60 W. If that's the case, at least you know that setting powerlimits is possible, and it's perhaps the above. Thank you for the fast reply! Yes I use the newest v18 with the new 1bash. If I set what you mentioned before, it works well. (I set it to 100 because I use 1070 cards.) My experience: if I set it in the 1bash - and monitor it in another terminal - it works UNTIL the dag reading's end! And after this, it is changing to 125. In the 1bash it is in the line 522 and (as I see well) there is no setting after this line ith this parameter. I set the all of the individual card settints to 100 too but set no to induvidual_powerlimit on line 133 and all power limit started from 243 to 100 too (form nicehash but now I do not use it yet). I try to set on/off the temperature control in line 51 but it is not changing the problem. What is yor next idea? Thank you! |
|
|
|
Hi guys, Is there a solution for this? I got it too (8x1070 and 125W) and can not do anything. Love the v0018 release and all the functionality!
However, POWERLIMIT NIGHTMARES!
I have one major issue, I cannot lower the POWERLIMIT. I run 8 rigs of 1050Ti and 125W is just way to high. I have tried adjusting the base line and the individual POWERLIMIT settings and I am still seeing maximum power being utilized in NVIDIA-SMI and TEMP CONTROL. I thought maybe the TEMP CONTROL was trumping the setting, but I don't think that is the case (at least based on what my 46 year old brain and eye balls looking at the 1bash code understands). I thought maybe it was the correction in line 527, but that didn't change anything.
I tried "NO" for both WATCHDOG and TEMP CONTROL with POWERLIMIT set below MAX for the 1050Ti and I still see max power output.
I did notice during startup, of the three terminal screens that pop-up during startup that the second terminal session has the POWERLIMIT set correctly at 60. However, something happens after the third terminal screen initiates (miner starting) that pushes the POWER back to MAX.
I added another rig of 1050Tis tonight and I saw more unusual behavior from POWER settings again where GPU0 goes to 125W as the max power limit and the rest of the GPUs all complied with my setting of 65Watts. I have no idea what is causing this inconsistency in power limit settings.
I also noticed in the Guake terminal that the TEMP CONTROL module is displaying continuous notifications that 125W is not a valid power limit (even after changing the settings in the module to 60-65).
I normally run all my rigs at 60W, which keeps the current draw low enough to run 3 rigs of 8 GPUs on each 15 AMP circuit. Also, extremely efficient.
I am still hunting for what is causing the forced 125W power setting.
|
|
|
|
|
Some pool, for example nanopool and dwarfpool need e-mail for sending alert with this format: address.worker/email. I would like to ask you to take it to params in the next version. Thank you!
|
|
|
|
|
Pls anybody explain me the difference between MANUAL_FAN="YES" + FAN_SPEED=75 and MANUAL_FAN="NO". Stability? Consumption? Because I have used both of them and did no see difference in hash and consumption too.
I can not find the optimized setup for 1070. Do you have suggested setup? Or the newest oneBash is the suggested?
Thank you!
|
|
|
|
Hi Guys,
I continue the trying to switch to dwarfpool from nanopool. v17 nvOC, same hw and other sw params, just the pool is the different.
claymore:
ETH - Total Speed: 211.976 Mh/s, Total Shares: 832, Rejected: 0, Time: 02:11
ETH: GPU0 30.360 Mh/s, GPU1 30.396 Mh/s, GPU2 30.362 Mh/s, GPU3 30.394 Mh/s, GPU4 30.543 Mh/s, GPU5 29.973 Mh/s, GPU6 29.947 Mh/s
genoil:
m 03:45:20|ethminer Mining on PoWhash #7a75ced3 : 182.44MH/s [A3+0:R0+0:F0]
m 03:45:21|ethminer Mining on PoWhash #7a75ced3 : 190.81MH/s [A3+0:R0+0:F0]
m 03:45:21|ethminer Mining on PoWhash #7a75ced3 : 185.98MH/s [A3+0:R0+0:F0]
m 03:45:22|ethminer Mining on PoWhash #7a75ced3 : 189.03MH/s [A3+0:R0+0:F0]
m 03:45:22|ethminer Mining on PoWhash #7a75ced3 : 182.75MH/s [A3+0:R0+0:F0]
m 03:45:23|ethminer Mining on PoWhash #7a75ced3 : 186.61MH/s [A3+0:R0+0:F0]
m 03:45:24|ethminer Mining on PoWhash #7a75ced3 : 178.26MH/s [A3+0:R0+0:F0]
m 03:45:24|ethminer Mining on PoWhash #7a75ced3 : 187.75MH/s [A3+0:R0+0:F0]
m 03:45:25|ethminer Mining on PoWhash #7a75ced3 : 183.28MH/s [A3+0:R0+0:F0]
m 03:45:25|ethminer Mining on PoWhash #7a75ced3 : 189.52MH/s [A3+0:R0+0:F0]
m 03:45:26|ethminer Mining on PoWhash #7a75ced3 : 183.68MH/s [A3+0:R0+0:F0]
Can anybody explain the difference? The genoil is the worse, I dont know why.
I use an other rig exactly the same hw and sw just genoil and nanopool. Here I got 216 MH/s.
Any idea or suggession?
Thank you!
What are your settings? for 1070s with genoil I would use: POWERLIMIT="YES"
POWERLIMIT_WATTS=110
__CORE_OVERCLOCK=-200
MEMORY_OVERCLOCK=900
MANUAL_FAN="YES"
FAN_SPEED=75 or higher note the core clock is negative: -200 power limit: 100 core: 110 mem: 1300 I tried your settings and nothing changed. :-( nanopool + genoil: 216, dwarfpool + genoil: 180 I have written to dwarfpool admin but have not got solution. Any new idea? I like the nanopool's web admin page but do not like the 1% fee. I would like to switch only for this. What your favourite pool and why? Thanks! |
|
|
|
|
I use the teamviewer=yes param but it does not start automaticaly, I have to click it on terminal. Can anybody help me?
|
|
|
|
MSI Z170A GAMING M5 is in the fully supported list, this mobo has 7x pcie and 2x M.2 slots, so it might support 9 cards. I tried and found that only the 1st M.2 slot(near CPU) worked with M.2 to pcie adapter, so I can run only 8 cards. Any body tried 9 cards?
I use Asus Prime Z270-a. In its bios you can change the function of the m.2 slots. Now I use it with 7 card because the m.2 pcie adapters have not arrived yet, so when they will arrive maybe next week, I will referee to you is you need it. |
|
|
|
|
Hi Guys,
I continue the trying to switch to dwarfpool from nanopool. v17 nvOC, same hw and other sw params, just the pool is the different.
claymore:
ETH - Total Speed: 211.976 Mh/s, Total Shares: 832, Rejected: 0, Time: 02:11
ETH: GPU0 30.360 Mh/s, GPU1 30.396 Mh/s, GPU2 30.362 Mh/s, GPU3 30.394 Mh/s, GPU4 30.543 Mh/s, GPU5 29.973 Mh/s, GPU6 29.947 Mh/s
genoil:
m 03:45:20|ethminer Mining on PoWhash #7a75ced3 : 182.44MH/s [A3+0:R0+0:F0]
m 03:45:21|ethminer Mining on PoWhash #7a75ced3 : 190.81MH/s [A3+0:R0+0:F0]
m 03:45:21|ethminer Mining on PoWhash #7a75ced3 : 185.98MH/s [A3+0:R0+0:F0]
m 03:45:22|ethminer Mining on PoWhash #7a75ced3 : 189.03MH/s [A3+0:R0+0:F0]
m 03:45:22|ethminer Mining on PoWhash #7a75ced3 : 182.75MH/s [A3+0:R0+0:F0]
m 03:45:23|ethminer Mining on PoWhash #7a75ced3 : 186.61MH/s [A3+0:R0+0:F0]
m 03:45:24|ethminer Mining on PoWhash #7a75ced3 : 178.26MH/s [A3+0:R0+0:F0]
m 03:45:24|ethminer Mining on PoWhash #7a75ced3 : 187.75MH/s [A3+0:R0+0:F0]
m 03:45:25|ethminer Mining on PoWhash #7a75ced3 : 183.28MH/s [A3+0:R0+0:F0]
m 03:45:25|ethminer Mining on PoWhash #7a75ced3 : 189.52MH/s [A3+0:R0+0:F0]
m 03:45:26|ethminer Mining on PoWhash #7a75ced3 : 183.68MH/s [A3+0:R0+0:F0]
Can anybody explain the difference? The genoil is the worse, I dont know why.
I use an other rig exactly the same hw and sw just genoil and nanopool. Here I got 216 MH/s.
Any idea or suggession?
Thank you!
|
|
|
|
Genoil uses a different implementation of the CUDA cores; this is almost like mining a different algorithm. OC which works with Claymore is not expected to work with Genoil-NC. You will most likely need to use lower clocks to achieve stability when using Genoil; however it will likely still have a higher hashrate than Claymore.
Seems better, thank you! Can you check genoil + eth single + dwarfpool? I use this setup but got error mentioned before. ETH_WORKER="" ETH_ADDRESS="0x5095F783a926d*D8121.p*2/gy*@*t.hu" ETH_POOL="eth-eu.dwarfpool.com:8008" ETH_EXTENTION_ARGUMENTS="" # add any additional claymore arguments desired here error: [CUDA]:Using grid size 8192, block size 128 ℹ 08:01:59|ethminer Connecting to stratum server eth-eu.dwarfpool.com:8008 ℹ 08:01:59|stratum Connected to stratum server eth-eu.dwarfpool.com : 8008 ℹ 08:01:59|stratum Starting farm ℹ 08:01:59|stratum Subscribed to stratum server terminate called after throwing an instance of 'Json::LogicError' what(): Value is not convertible to bool. /media/m1/1263-A96E/oneBash: line 1551: 3990 Aborted $HCD -S $ETH_POOL -O $ETHADDR:x -U FAILURE; reinit in 5 Thank you! |
|
|
|
|
Next problem with genoil (claymore is stable as rock):
m 11:24:39|ethminer Mining on PoWhash #d720ded7 : 218.93MH/s [A160+0:R0+0:F0]
m 11:24:41|ethminer Mining on PoWhash #d720ded7 : 220.73MH/s [A160+0:R0+0:F0]
m 11:24:43|ethminer Mining on PoWhash #d720ded7 : 220.73MH/s [A160+0:R0+0:F0]
CUDA error in func 'search' at line 346 : unspecified launch failure.
✘ 11:24:43|cudaminer1 Error CUDA mining: unspecified launch failure
CUDA error in func 'search' at line 346 : unspecified launch failure.
✘ 11:24:43|cudaminer0 Error CUDA mining: unspecified launch failure
CUDA error in func 'search' at line 346 : unspecified launch failure.
✘ 11:24:43|cudaminer2 Error CUDA mining: unspecified launch failure
CUDA error in func 'search' at line 346 : unspecified launch failure.
✘ 11:24:43|cudaminer6 Error CUDA mining: unspecified launch failure
CUDA error in func 'search' at line 346 : unspecified launch failure.
✘ 11:24:43|cudaminer4 Error CUDA mining: unspecified launch failure
CUDA error in func 'search' at line 346 : unspecified launch failure.
✘ 11:24:43|cudaminer5 Error CUDA mining: unspecified launch failure
CUDA error in func 'search' at line 346 : unspecified launch failure.
✘ 11:24:43|cudaminer3 Error CUDA mining: unspecified launch failure
m 11:24:45|ethminer Mining on PoWhash #d720ded7 : 57.67MH/s [A160+0:R0+0:F0]
m 11:24:47|ethminer Mining on PoWhash #d720ded7 : 0.00MH/s [A160+0:R0+0:F0]
m 11:24:49|ethminer Mining on PoWhash #d720ded7 : 0.00MH/s [A160+0:R0+0:F0]
m 11:24:51|ethminer Mining on PoWhash #d720ded7 : 0.00MH/s [A160+0:R0+0:F0]
m 11:24:53|ethminer Mining on PoWhash #d720ded7 : 0.00MH/s [A160+0:R0+0:F0]
m 11:24:55|ethminer Mining on PoWhash #d720ded7 : 0.00MH/s [A160+0:R0+0:F0]
m 11:24:57|ethminer Mining on PoWhash #d720ded7 : 0.00MH/s [A160+0:R0+0:F0]
m 11:24:59|ethminer Mining on PoWhash #d720ded7 : 0.00MH/s [A160+0:R0+0:F0]
Has anybody a good idea?
|
|
|
|
|
I have an other rig, where I use nanopool. This works well. The dwarfpool is not working with genoil only claymore. Why? :-)
|
|
|
|
|
Hi All,
I'm a newbie here but like the nvOC! :-)
I updated to v17 and it works with claymore but I like to try genoil. Just changed only this param. Got this error. Is it my fault? Anybody got this message? Pls help me!
[CUDA]:Using grid size 8192, block size 128
ℹ 08:01:59|ethminer Connecting to stratum server eth-eu.dwarfpool.com:8008
ℹ 08:01:59|stratum Connected to stratum server eth-eu.dwarfpool.com : 8008
ℹ 08:01:59|stratum Starting farm
ℹ 08:01:59|stratum Subscribed to stratum server
terminate called after throwing an instance of 'Json::LogicError'
what(): Value is not convertible to bool.
/media/m1/1263-A96E/oneBash: line 1551: 3990 Aborted $HCD -S $ETH_POOL -O $ETHADDR:x -U
FAILURE; reinit in 5
|
|
|
|
|
