hello,
can anyone share latest tpruvot/ccminer for 1070? thanks!
Topic: [ mining os ] nvoc - page 118. (Read 418542 times)
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
I already posted this question but it seems that beardens linuxians have no idea of my pb with Guake and some python and GTK libraries...
Please help because this problem blocks 3main just after the reboot at the first start.
this error is also not systematic
I will remove it (guake) if i have not any solutions.
LOG :
Every reboot i have this message and my miner stop minning because of this guake blocking error :-(
EDIT :
nothing to do with this shit program. it seems after some research on the web that these mistakes are common on guake.
I made a remove, a purge, a reisntall, an upgrade, with reboots every time, and nothing to do, each reboot sytematically I have these errors.
What I do not understand is that I did not do anything until it happened spontaneously. since I try to solve this problem but I think more and more that this problem is the program itself.
AH though, the only thing that has worked out is that I replaced my Kingston Travlestart 32Gb USB key with a USB HDD disk on which I replicated the operational config USB key with HDDRawcopy.
Would it be possible to do without this program to replace it with another more reliable, secure and stable like terminator console?
I noted on page 180 that kk003 had also encountered this problem but that by doing an update it solved the problem. Aptitude installs me the latest stable version of the repositories and its dependencies so it annoys me to reinstall the system.
Please help because this problem blocks 3main just after the reboot at the first start.
this error is also not systematic
I will remove it (guake) if i have not any solutions.
LOG :
Code:
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
(guake:2056): libglade-WARNING **: unknown attribute `swapped' for.
INFO:guake.guake_app:Logging configuration complete
/usr/lib/python2.7/dist-packages/guake/guake_app.py:1785: GtkWarning: gtk_box_pack: assertion 'child->parent == NULL' failed
self.mainframe.pack_start(self.notebook, expand=True, fill=True, padding=0)
** (guake:2056): WARNING **: Binding 'F12' failed!
Every reboot i have this message and my miner stop minning because of this guake blocking error :-(
EDIT :
nothing to do with this shit program. it seems after some research on the web that these mistakes are common on guake.
I made a remove, a purge, a reisntall, an upgrade, with reboots every time, and nothing to do, each reboot sytematically I have these errors.
What I do not understand is that I did not do anything until it happened spontaneously. since I try to solve this problem but I think more and more that this problem is the program itself.
AH though, the only thing that has worked out is that I replaced my Kingston Travlestart 32Gb USB key with a USB HDD disk on which I replicated the operational config USB key with HDDRawcopy.
Would it be possible to do without this program to replace it with another more reliable, secure and stable like terminator console?
I noted on page 180 that kk003 had also encountered this problem but that by doing an update it solved the problem. Aptitude installs me the latest stable version of the repositories and its dependencies so it annoys me to reinstall the system.
--SNIP--
What version of ccminer you using??
I was using the tpruvot version and getting very good hashrate with my 1060's compared to other ccminer forks.
If you don't have latest one, we have the instructions on how to build it too on the http://nvoc-mining-os.com/
It has the xeevan but instructions are same except the git location you use is tpruvot.
1//What version of ccminer you using??
=>> i'm using the ASccminer on /home/m1 taht was not compiled. So, i follow instructions for changing openssl file bn.h to copile it and replace the old bn.h that i backup before compiling.
In the log above, alexis ccminer indicate 1.0.0 version.
With this miner, i obtain 75 MH/s on lyra's algo instead of 65 MH/s with TP KT, KX, SP ccminer.
I return with TPccminer_2.2.2 for neoscrypt, and i obtain ~64.7 MH/s.
Alexis seems best on lyra but bad on neoscrypt.
Yes, you are right, for lyra alexis is the best, for neo, skunk and some other algos tpruvot is really good.
I would suggest you to lower your overclock a little and test it for couple of hours, if its stable then leave oc as is if not lower down a little more (go down by 2%).
Once you find stable play with intensity, because you have mixed some times its better not to change it, with intensity if its too much it fails straight away so it is in fact easy to find the stable value.
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
Try ASccminer,
I had problems with TP, SP, KT, KX, ...
Alexis ccminer gives much more hash rate, but it takes time to fully utilize all GPUs, you should raise sleep time in watchdog or you will get into restart miner loop.
On my 12 cards it takes over 2 minutes untill all cards get fully utilize
Also I think its better to lower watchdog threshold too, ccminers keep droping below 90 and it can cause restart miner too
Thanks. I'll give Alexis ccminer a shot. Btw, I'm running Stubo's modified watchdog script.I had problems with TP, SP, KT, KX, ...
Alexis ccminer gives much more hash rate, but it takes time to fully utilize all GPUs, you should raise sleep time in watchdog or you will get into restart miner loop.
On my 12 cards it takes over 2 minutes untill all cards get fully utilize
Also I think its better to lower watchdog threshold too, ccminers keep droping below 90 and it can cause restart miner too
If not raise it for AS
I don't think I'm running the watchdog with dynamic sleep time. If any of the rigs fall over, I'll raise the sleep time a bit.
Thanks!
I have somme erros with ASccminer for minning FTC neoscrypt. Did you have theses erros ?
Code:
*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)
*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. p roject
*** Include some of the work of djm34, sp, tsiv and klausT.
[2017-12-07 21:42:30] Starting on stratum+tcp://hub.miningpo olhub.com:20510
[2017-12-07 21:42:30] NVML GPU monitoring enabled.
[2017-12-07 21:42:30] 2 miner threads started, using 'neoscr ypt' algorithm.
[2017-12-07 21:42:30] Stratum difficulty set to 2048 (0.0312 5)
[2017-12-07 21:42:30] neoscrypt block 1995583, diff 56.347
[2017-12-07 21:42:33] GPU#0:Intensity set to 23, 8388608 cud a threads
[2017-12-07 21:42:33] GPU#1:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 947 : out of memory.
Cuda error in func 'neoscrypt_cpu_init' at line 947 : out of memory.
*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)
*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. p roject
*** Include some of the work of djm34, sp, tsiv and klausT.
[2017-12-07 21:43:29] Starting on stratum+tcp://hub.miningpo olhub.com:20510
[2017-12-07 21:43:30] NVML GPU monitoring enabled.
[2017-12-07 21:43:30] 2 miner threads started, using 'neoscr ypt' algorithm.
[2017-12-07 21:43:30] Stratum difficulty set to 2048 (0.0312 5)
[2017-12-07 21:43:30] GPU#1:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 947 : out of memory.
[2017-12-07 21:43:30] GPU#0:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 944 : driver shutting down.
*** Error in `/home/m1/ASccminer/ccminer': double free or co rruption (fasttop): 0x00000000049ca7d0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f288c6257e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f288c62e37a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f288c63253c]
/usr/local/cuda/lib64/libcudart.so.8.0(+0x1d2d7)*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)
*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. p roject
*** Include some of the work of djm34, sp, tsiv and klausT.
[2017-12-07 21:44:20] Starting on stratum+tcp://hub.miningpo olhub.com:20510
[2017-12-07 21:44:20] NVML GPU monitoring enabled.
[2017-12-07 21:44:20] 2 miner threads started, using 'neoscr ypt' algorithm.
[2017-12-07 21:44:21] Stratum difficulty set to 2048 (0.0312 5)
[2017-12-07 21:44:21] neoscrypt block 1995584, diff 57.303
[2017-12-07 21:44:21] GPU#0:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 947 : out of memory.
[2017-12-07 21:44:21] GPU#1:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 944 : driver shutting down.
on the other hand, on Lyra, Alexis's miner is more efficient and gives me 10 MH/s more than the others cited here.
What version of ccminer you using??
I was using the tpruvot version and getting very good hashrate with my 1060's compared to other ccminer forks.
If you don't have latest one, we have the instructions on how to build it too on the http://nvoc-mining-os.com/
It has the xeevan but instructions are same except the git location you use is tpruvot.
1//What version of ccminer you using??
=>> i'm using the ASccminer on /home/m1 that was not compiled. So, i follow instructions for changing openssl file bn.h to compile it and replace the old bn.h that i backup before compiling.
In the log above, alexis ccminer indicate 1.0.0 version.
With this miner, i obtain 75 MH/s on lyra's algo instead of 65 MH/s with TP KT, KX, SP ccminer.
I return with TPccminer_2.2.2 for neoscrypt, and i obtain ~64.7 MH/s.
Alexis seems best on lyra but bad on neoscrypt.
Im using V0019 and whenever I mine any coin with ccminer it will mine for a few mins and then I get an error and the miner restarts. The error is:
/home/m1/2unix line30: XXXX Terminated bash '/home/m1/3main'
Is there a way to fix this? Im going to try 19-1.3
Im running 5 Nvidea cards: 1x1080TI, 3x1080, 1x1060
Thanks in advance.
/home/m1/2unix line30: XXXX Terminated bash '/home/m1/3main'
Is there a way to fix this? Im going to try 19-1.3
Im running 5 Nvidea cards: 1x1080TI, 3x1080, 1x1060
Thanks in advance.
Try to change intensity
Thanks for your reply.
What should I change it to? Higher, lower??? Is there a way to know what to set it to?
Thanks
Generally you should lower it, but you getting that error when you mine any coin using ccminer, that maybe because of something else,probably over clock??
Also try to lower your memory and core clock a little, because you are using different cards you have to set OC individually based on the index you see.
every card, every algo, every memory type has different overclock settings.
EDIT : Please refer this website for some rough idea about different OC http://krypto-mining.blogspot.co.uk/
Im using V0019 and whenever I mine any coin with ccminer it will mine for a few mins and then I get an error and the miner restarts. The error is:
/home/m1/2unix line30: XXXX Terminated bash '/home/m1/3main'
Is there a way to fix this? Im going to try 19-1.3
Im running 5 Nvidea cards: 1x1080TI, 3x1080, 1x1060
Thanks in advance.
/home/m1/2unix line30: XXXX Terminated bash '/home/m1/3main'
Is there a way to fix this? Im going to try 19-1.3
Im running 5 Nvidea cards: 1x1080TI, 3x1080, 1x1060
Thanks in advance.
Try to change intensity
Thanks for your reply.
What should I change it to? Higher, lower??? Is there a way to know what to set it to?
Thanks
Try ASccminer,
I had problems with TP, SP, KT, KX, ...
Alexis ccminer gives much more hash rate, but it takes time to fully utilize all GPUs, you should raise sleep time in watchdog or you will get into restart miner loop.
On my 12 cards it takes over 2 minutes untill all cards get fully utilize
Also I think its better to lower watchdog threshold too, ccminers keep droping below 90 and it can cause restart miner too
I had problems with TP, SP, KT, KX, ...
Alexis ccminer gives much more hash rate, but it takes time to fully utilize all GPUs, you should raise sleep time in watchdog or you will get into restart miner loop.
On my 12 cards it takes over 2 minutes untill all cards get fully utilize
Also I think its better to lower watchdog threshold too, ccminers keep droping below 90 and it can cause restart miner too
Thanks. I'll give Alexis ccminer a shot. Btw, I'm running Stubo's modified watchdog script.
Is it the one with my dynamic sleep time?
If not raise it for AS
I switched all my rigs over to AS and they are now running stable! (once I lowered core clocks about 20 ticks from where they were). Even the 1060 3GB is running now. And I'm getting much better hashrates than with ccminer. So win win for sure.
I don't think I'm running the watchdog with dynamic sleep time. If any of the rigs fall over, I'll raise the sleep time a bit.
Thanks!
I have somme erros with ASccminer for minning FTC neoscrypt. Did you have theses erros ?
Code:
*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)
*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. p roject
*** Include some of the work of djm34, sp, tsiv and klausT.
[2017-12-07 21:42:30] Starting on stratum+tcp://hub.miningpo olhub.com:20510
[2017-12-07 21:42:30] NVML GPU monitoring enabled.
[2017-12-07 21:42:30] 2 miner threads started, using 'neoscr ypt' algorithm.
[2017-12-07 21:42:30] Stratum difficulty set to 2048 (0.0312 5)
[2017-12-07 21:42:30] neoscrypt block 1995583, diff 56.347
[2017-12-07 21:42:33] GPU#0:Intensity set to 23, 8388608 cud a threads
[2017-12-07 21:42:33] GPU#1:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 947 : out of memory.
Cuda error in func 'neoscrypt_cpu_init' at line 947 : out of memory.
*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)
*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. p roject
*** Include some of the work of djm34, sp, tsiv and klausT.
[2017-12-07 21:43:29] Starting on stratum+tcp://hub.miningpo olhub.com:20510
[2017-12-07 21:43:30] NVML GPU monitoring enabled.
[2017-12-07 21:43:30] 2 miner threads started, using 'neoscr ypt' algorithm.
[2017-12-07 21:43:30] Stratum difficulty set to 2048 (0.0312 5)
[2017-12-07 21:43:30] GPU#1:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 947 : out of memory.
[2017-12-07 21:43:30] GPU#0:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 944 : driver shutting down.
*** Error in `/home/m1/ASccminer/ccminer': double free or co rruption (fasttop): 0x00000000049ca7d0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f288c6257e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f288c62e37a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f288c63253c]
/usr/local/cuda/lib64/libcudart.so.8.0(+0x1d2d7)*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)
*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. p roject
*** Include some of the work of djm34, sp, tsiv and klausT.
[2017-12-07 21:44:20] Starting on stratum+tcp://hub.miningpo olhub.com:20510
[2017-12-07 21:44:20] NVML GPU monitoring enabled.
[2017-12-07 21:44:20] 2 miner threads started, using 'neoscr ypt' algorithm.
[2017-12-07 21:44:21] Stratum difficulty set to 2048 (0.0312 5)
[2017-12-07 21:44:21] neoscrypt block 1995584, diff 57.303
[2017-12-07 21:44:21] GPU#0:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 947 : out of memory.
[2017-12-07 21:44:21] GPU#1:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 944 : driver shutting down.
on the other hand, on Lyra, Alexis's miner is more efficient and gives me 10 MH/s more than the others cited here.
What version of ccminer you using??
I was using the tpruvot version and getting very good hashrate with my 1060's compared to other ccminer forks.
If you don't have latest one, we have the instructions on how to build it too on the http://nvoc-mining-os.com/
It has the xeevan but instructions are same except the git location you use is tpruvot.
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
Try ASccminer,
I had problems with TP, SP, KT, KX, ...
Alexis ccminer gives much more hash rate, but it takes time to fully utilize all GPUs, you should raise sleep time in watchdog or you will get into restart miner loop.
On my 12 cards it takes over 2 minutes untill all cards get fully utilize
Also I think its better to lower watchdog threshold too, ccminers keep droping below 90 and it can cause restart miner too
I had problems with TP, SP, KT, KX, ...
Alexis ccminer gives much more hash rate, but it takes time to fully utilize all GPUs, you should raise sleep time in watchdog or you will get into restart miner loop.
On my 12 cards it takes over 2 minutes untill all cards get fully utilize
Also I think its better to lower watchdog threshold too, ccminers keep droping below 90 and it can cause restart miner too
Thanks. I'll give Alexis ccminer a shot. Btw, I'm running Stubo's modified watchdog script.
Is it the one with my dynamic sleep time?
If not raise it for AS
I switched all my rigs over to AS and they are now running stable! (once I lowered core clocks about 20 ticks from where they were). Even the 1060 3GB is running now. And I'm getting much better hashrates than with ccminer. So win win for sure.
I don't think I'm running the watchdog with dynamic sleep time. If any of the rigs fall over, I'll raise the sleep time a bit.
Thanks!
I have somme erros with ASccminer for minning FTC neoscrypt. Did you have theses erros ?
Code:
*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)
*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. p roject
*** Include some of the work of djm34, sp, tsiv and klausT.
[2017-12-07 21:42:30] Starting on stratum+tcp://hub.miningpo olhub.com:20510
[2017-12-07 21:42:30] NVML GPU monitoring enabled.
[2017-12-07 21:42:30] 2 miner threads started, using 'neoscr ypt' algorithm.
[2017-12-07 21:42:30] Stratum difficulty set to 2048 (0.0312 5)
[2017-12-07 21:42:30] neoscrypt block 1995583, diff 56.347
[2017-12-07 21:42:33] GPU#0:Intensity set to 23, 8388608 cud a threads
[2017-12-07 21:42:33] GPU#1:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 947 : out of memory.
Cuda error in func 'neoscrypt_cpu_init' at line 947 : out of memory.
*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)
*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. p roject
*** Include some of the work of djm34, sp, tsiv and klausT.
[2017-12-07 21:43:29] Starting on stratum+tcp://hub.miningpo olhub.com:20510
[2017-12-07 21:43:30] NVML GPU monitoring enabled.
[2017-12-07 21:43:30] 2 miner threads started, using 'neoscr ypt' algorithm.
[2017-12-07 21:43:30] Stratum difficulty set to 2048 (0.0312 5)
[2017-12-07 21:43:30] GPU#1:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 947 : out of memory.
[2017-12-07 21:43:30] GPU#0:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 944 : driver shutting down.
*** Error in `/home/m1/ASccminer/ccminer': double free or co rruption (fasttop): 0x00000000049ca7d0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f288c6257e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f288c62e37a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f288c63253c]
/usr/local/cuda/lib64/libcudart.so.8.0(+0x1d2d7)*** ccminer alexis-1.0 for nVidia GPUs from alexis78@github ***
*** Built with the nVidia CUDA Toolkit 8.0 (Not recommended prefer 7.5)
*** Based on tpruvot@github ccminer
*** Originally based on Christian Buchner and Christian H. p roject
*** Include some of the work of djm34, sp, tsiv and klausT.
[2017-12-07 21:44:20] Starting on stratum+tcp://hub.miningpo olhub.com:20510
[2017-12-07 21:44:20] NVML GPU monitoring enabled.
[2017-12-07 21:44:20] 2 miner threads started, using 'neoscr ypt' algorithm.
[2017-12-07 21:44:21] Stratum difficulty set to 2048 (0.0312 5)
[2017-12-07 21:44:21] neoscrypt block 1995584, diff 57.303
[2017-12-07 21:44:21] GPU#0:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 947 : out of memory.
[2017-12-07 21:44:21] GPU#1:Intensity set to 23, 8388608 cud a threads
Cuda error in func 'neoscrypt_cpu_init' at line 944 : driver shutting down.
on the other hand, on Lyra, Alexis's miner is more efficient and gives me 10 MH/s more than the others cited here.
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
ComputerGenie, do we have to understand that you do not mine in pool?
As a general rule, I rarely mine in a public pool with ASICs and never do with my GPUs.Thus you mine alone with a big ASIC FARM, if not, i don't understand, and i'm curious about your gloabl profitability.
So, ASIC minning is less profitable because their power consumption are more expensive by TH than MH with graphics cards ? Is it what you conclude of your expérience ?
What about theses calculations with an antminer D3 that permit to hash X11 algo.
Are there any mining scripts like the one on MPH or WTM for the ASICS allowing to switch according to the profitability? If yes, do you use them? Do you have reliable software on which OS?
I saw on WTM that there is a tab ASICs for the mining compared to BTC in sha256. The JSON must also be exploitable and it seems to me that the bitmain ASICs are sold with a LAMP server remodeled for the mining spot, right?
Lots of questions and temptations with ASICs, but not décided yet. It's a huge investment and i'm afraid for the ROI time.
ComputerGenie, do we have to understand that you do not mine in pool?
As a general rule, I rarely mine in a public pool with ASICs and never do with my GPUs.Thus you mine alone with a big ASIC FARM, if not, i don't understand, and i'm curious about your gloabl profitability.
Can someone share good Lyra2Rev2 settings for 1060 6gb please? No matter what I set up, miner screen gets restarted all the time and some times even the whole rig reboots. when rig reboots logfile says utilitation too low but all cards perform at least at 75%.
tried settings:
76-90w
100-120
-1200-100
tried settings:
76-90w
100-120
-1200-100
@leenoox
I tried what you suggested but unfortunately still see the same behavior as before. Within 60 seconds, some GPU's goes to P0 and the miner restarts.
I tried what you suggested but unfortunately still see the same behavior as before. Within 60 seconds, some GPU's goes to P0 and the miner restarts.
Try ASccminer,
I had problems with TP, SP, KT, KX, ...
Alexis ccminer gives much more hash rate, but it takes time to fully utilize all GPUs, you should raise sleep time in watchdog or you will get into restart miner loop.
On my 12 cards it takes over 2 minutes untill all cards get fully utilize
Also I think its better to lower watchdog threshold too, ccminers keep droping below 90 and it can cause restart miner too
I had problems with TP, SP, KT, KX, ...
Alexis ccminer gives much more hash rate, but it takes time to fully utilize all GPUs, you should raise sleep time in watchdog or you will get into restart miner loop.
On my 12 cards it takes over 2 minutes untill all cards get fully utilize
Also I think its better to lower watchdog threshold too, ccminers keep droping below 90 and it can cause restart miner too
Thanks. I'll give Alexis ccminer a shot. Btw, I'm running Stubo's modified watchdog script.
Is it the one with my dynamic sleep time?
If not raise it for AS
I switched all my rigs over to AS and they are now running stable! (once I lowered core clocks about 20 ticks from where they were). Even the 1060 3GB is running now. And I'm getting much better hashrates than with ccminer. So win win for sure.
I don't think I'm running the watchdog with dynamic sleep time. If any of the rigs fall over, I'll raise the sleep time a bit.
Thanks!
Hey crazydane, I understan you solved the problem you had by switching the miner but if you have some spare time could you please check this and report back to help the development:
1. Revert back to your original setup that was breaking, use the same original miner
2. Add this code to 3main on the second line
Code:
sudo nvidia-smi pm 1
3. Save and restart
4. Report back
* If it doesn't resolve the problem, just delete the new line from 3main and revert back to the working miner
I'm having some trouble setting up the papampi_WTM_Auto_Switch with something like zpool. I want it to switch to a profitable coin, but only use pools that pay in BTC. Should I just set individual coin pools to a zpool equivalent, or is there a more elegant method?
You can set your coin pools to what ever you like, then when it switches it uses those pools
I use MPH for all my switch coins and auto exchange to btc in MPH settings page.
You can use zpool for your coin pools and then it switches between them.
Right, I guess what I meant is that the papampi switcher doesn't seem to support zpool's settings format. MPH switcher doesn't seem to support lyra2rev. I'm sure with some modifications to 3main they could support those, but I was hoping for a simpler solution. I used to use salfter's nicehash switcher, but with NICEHASH down I'm just looking to recreate that setup with different pools.
Also, what exactly does the papampi switcher do differently than the salfter switchers? I only just updated from v19 to 19.4 last night so I haven't really figured out the differences yet.
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
Hey guys,
because of nicehash hack, I just switched over to salfters MPH switcher.
I just dont get one thing: ATM on whattomine.com it says most profitable Coin for 8x 1060 rig is Vertcoin, about 25usd/day
In my rig under current-profit it says: feathercoin(neoscrypt): 6.68usd/day is most profitable
Am I doing it wrong??
because of nicehash hack, I just switched over to salfters MPH switcher.
I just dont get one thing: ATM on whattomine.com it says most profitable Coin for 8x 1060 rig is Vertcoin, about 25usd/day
In my rig under current-profit it says: feathercoin(neoscrypt): 6.68usd/day is most profitable
Am I doing it wrong??
You don't have choices on MPH that you can have with papampi WTM_Switcher. it is precisely the interest of the WTM_Switcher
Moreover, if MPH is honest, I still prefer to place myself my sales orders on Bittrex. self-selling or selling on threshold depending on the value of the coins I chose to mine.
I strongly recommend WTM_SWITCHER instead of Scott Alfter's script.
This script was used by Papampi and damnmad to develop theirs, by the way.
Of course, WTM does not allow to undermine every coins we want but I think it would be the same with Coinwarz for example. Except that CoinWarz charges the query package according to the intensity of them (minutes, 5 min, or hours if i remember correctly).
I think it does not take much to papamapi and damnmad scripts so that it also works on coinwarz, but of course we would have to pay coinwarz for it to work well and so, we must also have some computing power has available for this to be profitable.
Remember, WTM lists the most profitable areas to mine compared to ETH mining.
And then, Fredeq who happens to read from time to time this thread, and responsible / creator of the WTM project, regularly adds platforms and coins to his site.
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
ComputerGenie, do we have to understand that you do not mine in pool?
As a general rule, I rarely mine in a public pool with ASICs and never do with my GPUs.Thus you mine alone with a big ASIC FARM, if not, i don't understand, and i'm curious about your gloabl profitability.
ComputerGenie, do we have to understand that you do not mine in pool?
As a general rule, I rarely mine in a public pool with ASICs and never do with my GPUs.
Hey guys,
because of nicehash hack, I just switched over to salfters MPH switcher.
I just dont get one thing: ATM on whattomine.com it says most profitable Coin for 8x 1060 rig is Vertcoin, about 25usd/day
In my rig under current-profit it says: feathercoin(neoscrypt): 6.68usd/day is most profitable
Am I doing it wrong??
because of nicehash hack, I just switched over to salfters MPH switcher.
I just dont get one thing: ATM on whattomine.com it says most profitable Coin for 8x 1060 rig is Vertcoin, about 25usd/day
In my rig under current-profit it says: feathercoin(neoscrypt): 6.68usd/day is most profitable
Am I doing it wrong??
full member
Activity: 340
Merit: 103
It is easier to break an atom than partialities AE
No, WE, the miners lost millions.
Every reason to add as few middlemen between your rigs and the blockchain as possible.Solo-mining increases time-specific payout variability, but decreases the chance of such loss.
ComputerGenie, do we have to understand that you do not mine in pool?
No, WE, the miners lost millions.
Every reason to add as few middlemen between your rigs and the blockchain as possible.Solo-mining increases time-specific payout variability, but decreases the chance of such loss.
Jump to: