Topic: [Mining OS] SimpleMining.net - Manage Your GPU farm the easy way! (30 days free) - page 329. (Read 835509 times)
October 03, 2017, 01:05:09 AM
Hi, how can i add a previously deleted rig?
October 02, 2017, 07:05:55 PM
Edit. I just paid the fee. And for the default rig thing, I figured that out.
Finally today was my first try at Simplemining OS. But I did not get a free fee balance to try it out. All I got was a minus $0.28. Why, don't you get to try it first? I did send a email to them.
One other thing when I was trying to set it up. In the console there is a default rig dual mining eth/sia with a claymore miner. Why is that? I just started using simplemining. I create a new group and used set EWBF miner up to mine zcash. And set it to default, but it kept mining eth, why? Is it because of the negative fee balance? I am new to this OS but I do know my computers.
Finally today was my first try at Simplemining OS. But I did not get a free fee balance to try it out. All I got was a minus $0.28. Why, don't you get to try it first? I did send a email to them.
One other thing when I was trying to set it up. In the console there is a default rig dual mining eth/sia with a claymore miner. Why is that? I just started using simplemining. I create a new group and used set EWBF miner up to mine zcash. And set it to default, but it kept mining eth, why? Is it because of the negative fee balance? I am new to this OS but I do know my computers.
October 02, 2017, 04:32:17 PM
Can you please tell if this OS works with RX Vega cards? And how are the hashrate on them?
October 02, 2017, 03:52:40 PM
There is no problem with Rx series ISO ..
But whenever I tried whicever dagfix iso file versions , i get a message like this ?
What is the solution to this ?
""Gave up waiting for root device......."""
https://pasteboard.co/GMXefCV.jpg
But whenever I tried whicever dagfix iso file versions , i get a message like this ?
What is the solution to this ?
""Gave up waiting for root device......."""
https://pasteboard.co/GMXefCV.jpg
October 02, 2017, 03:16:48 PM
The issue with the constant reboots of systems with a lot of GPUs seems to be related to single cards. As overclock apply to whole machine you could have a single card/cards that can't handle the clock and hung means reboot of machine. Here is a screenshot of two 1:1 machines with same HW, 1st one reboot every 1hr, 2nd one is not. So my suggestion to keep the logs files "current minus 1" will help to see which card to underclock. Can we put clock values with commas to separate for different GPU: like 100,150,80,200,100.... ?
October 02, 2017, 12:53:09 PM
@Tytanick:
Maybe i overread something but when minign zec, agpu makes about 300khs, so 6x300 = 1.8khs ;-)
On the dashboard its MH/s
Maybe i overread something but when minign zec, agpu makes about 300khs, so 6x300 = 1.8khs ;-)
On the dashboard its MH/s
October 02, 2017, 07:11:21 AM
@tytanik - i experience the same issue issue like most of users with NV and more cards.
H110+ 13 x P106 setup, found everything from the start, have the following problems:
1. Overclocking works pretty strange, to clock the memory of the P106 from 4000 to 4900 i needed to put 1600 as parameter. Steps that increase the MHz are really not relevant. Putting 900 clock to 4400 something.
2. Finally stabilized the machine to 325MH and runs well but it reboots without reason 14 times for 10 hours. Temperatures are under 65C, target is 76C.
So how to fix those nonsense reboots ?
H110+ 13 x P106 setup, found everything from the start, have the following problems:
1. Overclocking works pretty strange, to clock the memory of the P106 from 4000 to 4900 i needed to put 1600 as parameter. Steps that increase the MHz are really not relevant. Putting 900 clock to 4400 something.
2. Finally stabilized the machine to 325MH and runs well but it reboots without reason 14 times for 10 hours. Temperatures are under 65C, target is 76C.
So how to fix those nonsense reboots ?
Yes, please do let us know how to fix these constant reboots on H110+ 13 x 1070 setups. Thank you.
one more think - i have accessed the claymore 10 directory in order to see what is the error causing the system to reboot but you probably have sanity script that remove log files because after reboot it's deleted. Can you let me know how to stop it for some time to check or at least change it to keep current minus 1 log files ?
October 01, 2017, 03:16:43 PM
Can you please implement tpruvot's newest CCminer to make use of theTRIBUS algo?
October 01, 2017, 03:08:51 PM
There is no problem with Rx series ISO ..
But whenever I tried whicever dagfix iso file versions , i get a message like this ?
What is the solution to this ?
https://pasteboard.co/GMXefCV.jpg
But whenever I tried whicever dagfix iso file versions , i get a message like this ?
What is the solution to this ?
https://pasteboard.co/GMXefCV.jpg
October 01, 2017, 02:49:54 PM
Hi all, just built my first rig (Asrock H110 Pro BTC+, i3, 6 x ASUS Strix GTX1070 08G)...it started at 160Mh/s... then I lost some Mh/s somehow, now running at 134. Not sure what caused it. Original Core numbers were 1974, 2025, 2025, 2025, 1999, 1974 (10)
And Mem were 3802, 3802, 3802, 3802, 3802, 3802
Current Core numbers are 417, 455, 468, 430, 430, 417 (10)
(no change to Mem)
any suggestions welcome and appreciated.
And Mem were 3802, 3802, 3802, 3802, 3802, 3802
Current Core numbers are 417, 455, 468, 430, 430, 417 (10)
(no change to Mem)
any suggestions welcome and appreciated.
October 01, 2017, 02:36:47 PM
Need a miner for BTX please Timetravel10 algo. unless I missed something.
October 01, 2017, 02:24:22 PM
@tytanik - i experience the same issue issue like most of users with NV and more cards.
H110+ 13 x P106 setup, found everything from the start, have the following problems:
1. Overclocking works pretty strange, to clock the memory of the P106 from 4000 to 4900 i needed to put 1600 as parameter. Steps that increase the MHz are really not relevant. Putting 900 clock to 4400 something.
2. Finally stabilized the machine to 325MH and runs well but it reboots without reason 14 times for 10 hours. Temperatures are under 65C, target is 76C.
So how to fix those nonsense reboots ?
H110+ 13 x P106 setup, found everything from the start, have the following problems:
1. Overclocking works pretty strange, to clock the memory of the P106 from 4000 to 4900 i needed to put 1600 as parameter. Steps that increase the MHz are really not relevant. Putting 900 clock to 4400 something.
2. Finally stabilized the machine to 325MH and runs well but it reboots without reason 14 times for 10 hours. Temperatures are under 65C, target is 76C.
So how to fix those nonsense reboots ?
Yes, please do let us know how to fix these constant reboots on H110+ 13 x 1070 setups. Thank you.
October 01, 2017, 02:11:21 PM
911 949 961 (6)
3802 3802 3802
These are my current core/mem stats. The one in the middle is 1070, the other two are 1060s. Also the power limit on overclocking panel is set at Power Limit (watt):6
The core and memory is obviously underclocked. What should be my new settings in xxx,xxx,xxx order for core and memory. I don't need very high overclocking. Just a safe clock is fine. But these are obviously underclocked. I'm mining ethereum and the 1060s are mining at about 14mh, 1070 at 22mh.
3802 3802 3802
These are my current core/mem stats. The one in the middle is 1070, the other two are 1060s. Also the power limit on overclocking panel is set at Power Limit (watt):6
The core and memory is obviously underclocked. What should be my new settings in xxx,xxx,xxx order for core and memory. I don't need very high overclocking. Just a safe clock is fine. But these are obviously underclocked. I'm mining ethereum and the 1060s are mining at about 14mh, 1070 at 22mh.
October 01, 2017, 01:37:59 PM
I have 1080ti ..best setting without reboot is 160w and 120 core this is optimal 3x strix 1080ti rog=2080 sol
200w and 100 core is more energy consuptiom 2170 sol ;-)
200w and 100 core is more energy consuptiom 2170 sol ;-)
October 01, 2017, 10:50:39 AM
Does anyone know why gpu ignores overclock and memory apples normally?
October 01, 2017, 08:56:54 AM
Hey guys, im having troubles with this one rig in particular ( some other rigs did the same but they are now working somehow ) and im hoping someone could help me with this... I have flashed already 4 new pens for this rig in particular, cleared smos and flashed MOBO bios and still get the same problems...
Everytime i start a new fresh pen ( after the described method above ) i get the OS stuck on this part:
https://imgur.com/26RAMPS
It just hangs there everytime and does nothing... After i reboot the rig i get this another error:
https://imgur.com/Tuag7ly
Did anyone ever had the same problem or can help me to fix it?
Much apreciated
EDIT Everytime one rig reboots the OS gets stuck on the 2 image i posted... Clearly its out of my hands, now i have 4 rigs down instead of 1... im switching back to win if no one can help me fix the problem...
Everytime i start a new fresh pen ( after the described method above ) i get the OS stuck on this part:
https://imgur.com/26RAMPS
It just hangs there everytime and does nothing... After i reboot the rig i get this another error:
https://imgur.com/Tuag7ly
Did anyone ever had the same problem or can help me to fix it?
Much apreciated
EDIT Everytime one rig reboots the OS gets stuck on the 2 image i posted... Clearly its out of my hands, now i have 4 rigs down instead of 1... im switching back to win if no one can help me fix the problem...
October 01, 2017, 08:23:23 AM
Hello all, I can not handle the problem of starting mining with VTC Vertcoin on ccminer below I present my settings:
-a lyra2v2 -o stratum + tcp: //hub.miningpoolhub.com: 12018 -u xxxx.rig1 -p x
OC is set to 10,200,200 and the system keeps returning me the following error (of course the OC settings are testable, because I tried everything and always the same, sometimes it happens that it will start mining but after a restart) does anyone have an idea? The cards are GTX 1060,1070 and P106-6g total 12GPU:
Applying CoreOffset: 10 MemoryOffset: 200 for GPU 10 with GPU Type: 3
Available power limit for GPU 10 is 78.00 W, 182.00 W
Applying PowerLimit: 182 watt for GPU 10
Applying CoreOffset: 10 MemoryOffset: 200 for GPU 11 with GPU Type: 3
Available power limit for GPU 11 is 78.00 W, 182.00 W
Applying PowerLimit: 182 watt for GPU 11
============ Starting Miner ===============
*** ccminer 2.2 for nVidia GPUs by tpruvot@github config.json Built with the nVidia CUDA Toolkit 8.0 64-bits
Originally based on Christian Buchner and Christian H. project
Include some algos from alexis78, djm34, sp, tsiv and klausT.
BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)
[2017-10-01 13:19:42] Starting on stratum tcp://hub.miningpoolhub.com:12018
[2017-10-01 13:19:43] NVML GPU monitoring enabled.
[2017-10-01 13:19:43] 12 miner threads started, using 'lyra2v2' algorithm.
[2017-10-01 13:19:43] Stratum difficulty set to 16 (0.06250)
[2017-10-01 13:19:43] GPU #2: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #3: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #8: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #6: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #10: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #4: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #7: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #5: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #0: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #1: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #9: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #11: Intensity set to 20, 1048576 cuda threads
/root/xminer.sh: line 49: 3510 Segmentation fault $MINER_PATH $MINER_OPTIONS
Miner ended/crashed. Restarting miner in 10 seconds --------------
-a lyra2v2 -o stratum + tcp: //hub.miningpoolhub.com: 12018 -u xxxx.rig1 -p x
OC is set to 10,200,200 and the system keeps returning me the following error (of course the OC settings are testable, because I tried everything and always the same, sometimes it happens that it will start mining but after a restart) does anyone have an idea? The cards are GTX 1060,1070 and P106-6g total 12GPU:
Applying CoreOffset: 10 MemoryOffset: 200 for GPU 10 with GPU Type: 3
Available power limit for GPU 10 is 78.00 W, 182.00 W
Applying PowerLimit: 182 watt for GPU 10
Applying CoreOffset: 10 MemoryOffset: 200 for GPU 11 with GPU Type: 3
Available power limit for GPU 11 is 78.00 W, 182.00 W
Applying PowerLimit: 182 watt for GPU 11
============ Starting Miner ===============
*** ccminer 2.2 for nVidia GPUs by tpruvot@github config.json Built with the nVidia CUDA Toolkit 8.0 64-bits
Originally based on Christian Buchner and Christian H. project
Include some algos from alexis78, djm34, sp, tsiv and klausT.
BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)
[2017-10-01 13:19:42] Starting on stratum tcp://hub.miningpoolhub.com:12018
[2017-10-01 13:19:43] NVML GPU monitoring enabled.
[2017-10-01 13:19:43] 12 miner threads started, using 'lyra2v2' algorithm.
[2017-10-01 13:19:43] Stratum difficulty set to 16 (0.06250)
[2017-10-01 13:19:43] GPU #2: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #3: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #8: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #6: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #10: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #4: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #7: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #5: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #0: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #1: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #9: Intensity set to 20, 1048576 cuda threads
[2017-10-01 13:19:43] GPU #11: Intensity set to 20, 1048576 cuda threads
/root/xminer.sh: line 49: 3510 Segmentation fault $MINER_PATH $MINER_OPTIONS
Miner ended/crashed. Restarting miner in 10 seconds --------------
October 01, 2017, 06:28:02 AM
On 1070 cards oc don't work like it should, very little difference on ZEC EWBF miner between core clock 190 and 250, only 10sol but when rising power from 102 to 115 same clock, sols go by 30. Please check/fix the behaviour of the NV cards on OC and power limit.
October 01, 2017, 03:08:10 AM
question
when using this OS with nvidia cards, and the NV build.. we are only limited to ewbf or skunk/eth based mining programs right?
because my 1080TI's on ewbf seem to get half of what they should be hashing at
the claymore zec miner is not working with the NV build... why is this?
when using this OS with nvidia cards, and the NV build.. we are only limited to ewbf or skunk/eth based mining programs right?
because my 1080TI's on ewbf seem to get half of what they should be hashing at
the claymore zec miner is not working with the NV build... why is this?
... Because Claymores miner is AMD ONLY ... it literally there in the name "Claymore's ZCash AMD GPU Miner", and if that doesn't clear it up for you, it helps to go through the Readme file occasionally.
claymore-zec-v12.6
damn you are right... my bad
i just need to mess with overclock settings on ewbf, figured stock settings 1080ti would get 600 sol at least
October 01, 2017, 02:41:22 AM
question
when using this OS with nvidia cards, and the NV build.. we are only limited to ewbf or skunk/eth based mining programs right?
because my 1080TI's on ewbf seem to get half of what they should be hashing at
the claymore zec miner is not working with the NV build... why is this?
when using this OS with nvidia cards, and the NV build.. we are only limited to ewbf or skunk/eth based mining programs right?
because my 1080TI's on ewbf seem to get half of what they should be hashing at
the claymore zec miner is not working with the NV build... why is this?
... Because Claymores miner is AMD ONLY ... it literally there in the name "Claymore's ZCash AMD GPU Miner", and if that doesn't clear it up for you, it helps to go through the Readme file occasionally.
Jump to: