|
joshuajones02
|
 |
October 13, 2017, 05:40:57 PM |
|
Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login
anyone? trying to mine ZEN on suprnova |
|
|
|
|
Temporel
|
|
October 13, 2017, 05:44:28 PM |
|
Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login
anyone? trying to mine ZEN on suprnova yes and it works just fine. |
|
|
|
|
papampi
Full Member
 Offline
Activity: 686
Merit: 140
Linux FOREVER! Resistance is futile!!!
|
|
October 13, 2017, 05:46:09 PM |
|
Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login
anyone? trying to mine ZEN on suprnova You dont need suprnova password to mine |
|
|
|
|
Temporel
|
|
October 13, 2017, 05:47:23 PM |
|
Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login
anyone? trying to mine ZEN on suprnova You dont need suprnova password to mine isnt the option available in 3main anyway ? |
|
|
|
|
|
joshuajones02
|
|
October 13, 2017, 05:51:20 PM |
|
Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login
anyone? trying to mine ZEN on suprnova You dont need suprnova password to mine isnt the option available in 3main anyway ? found it in 3main, pass is "z" not x... thanks |
|
|
|
hurvajs77
Newbie
Offline
Activity: 46
Merit: 0
|
|
October 13, 2017, 05:51:55 PM |
|
Hi papampi, I'm using your telegram messages. Excellent! I've a small improvement for miner uptime (I got always empty), so I check command. There is used unknown option -p and failed The universal solution is: ps -eo comm,etime | grep -i miner | grep -vi cpu | awk '{print $2}'Other infos are empty too, I check later Thanks mate I'm aware of some problems thats why we call beta version:) Some info and hash rate on web has not completed yet , will try to add them all for next version. you're welcome. Maybe better solution is: ps -eo comm,etime | grep -vi cpu | grep -i miner | awk '{print $2}'So, first time gets all processes without CPU miner, than we got correct info about GPUs miner... Sorry ;-) But, I don't know how much from us use CPU mining... |
|
|
|
|
hurvajs77
Newbie
Offline
Activity: 46
Merit: 0
|
|
October 13, 2017, 06:03:30 PM |
|
I am mining Mona with ASccminer and intensity 21 with no problem and great hash rate on suprnova
are you sure you made your worker in suprnova settings?
suprnova dont creat worker automatically , you should make them manually
Excellent! I switched now without any problems and hash rate encreased from 680MHz to 770 - same OC... Thanks for notification papampi :-) |
|
|
|
|
hurvajs77
Newbie
Offline
Activity: 46
Merit: 0
|
|
October 13, 2017, 06:06:40 PM |
|
Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login
anyone? trying to mine ZEN on suprnova You dont need suprnova password to mine isnt the option available in 3main anyway ? found it in 3main, pass is "z" not x... thanks password isn't checked, so you can use z or modify 3main and fill correct password. Result is same :-) |
|
|
|
|
|
joshuajones02
|
|
October 13, 2017, 06:38:46 PM |
|
Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login
anyone? trying to mine ZEN on suprnova You dont need suprnova password to mine isnt the option available in 3main anyway ? found it in 3main, pass is "z" not x... thanks password isn't checked, so you can use z or modify 3main and fill correct password. Result is same :-) lol thanks, thats strange though.. I changed my pass in suprnova from x to z and rebooted and it worked fine, no issues. Every time I booted previously, it would show fan speed and then going in a loop to []Screen is terminating.. Oh well, working good now |
|
|
|
|
Temporel
|
|
October 13, 2017, 06:49:40 PM |
|
Where do I insert the password for suprnova login info in the miner blocks? I've tried everything I could possibly think of including using the password x for my miner login
anyone? trying to mine ZEN on suprnova You dont need suprnova password to mine isnt the option available in 3main anyway ? found it in 3main, pass is "z" not x... thanks password isn't checked, so you can use z or modify 3main and fill correct password. Result is same :-) well I had to change my password on suprnova recently because I made a mistake when I created a worker, so yeah, it does matter |
|
|
|
|
jlbaseball11
Newbie
Offline
Activity: 66
Merit: 0
|
|
October 13, 2017, 08:31:29 PM |
|
I built djm34's ccminer with Cuda9 and found that it was faster than tp ccminer on ZCOIN. If you can confirm that, use djm34's as default zcoin miner.
Would you be willing to share how you compiled? I got a bunch of "BIGNUM" errors when I tried to use -make. How do we upgrade to CUDA9? The instructions on their website didn't work for me: Installation Instructions: `sudo dpkg -i cuda-repo-ubuntu1604_9.0.176-1_amd64.deb` `sudo apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/7fa2af80.pub` `sudo apt-get update` `sudo apt-get install cuda` Thanks for your help. |
|
|
|
|
|
Temporel
|
|
October 13, 2017, 08:44:07 PM |
|
I built djm34's ccminer with Cuda9 and found that it was faster than tp ccminer on ZCOIN. If you can confirm that, use djm34's as default zcoin miner.
Would you be willing to share how you compiled? I got a bunch of "BIGNUM" errors when I tried to use -make. How do we upgrade to CUDA9? The instructions on their website didn't work for me: Installation Instructions: `sudo dpkg -i cuda-repo-ubuntu1604_9.0.176-1_amd64.deb` `sudo apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/7fa2af80.pub` `sudo apt-get update` `sudo apt-get install cuda` Thanks for your help. download openssl v1.0.2f from the offical website (look archive) then copy the file bn.h (from crypto directory) to /usr/local/include/openssl then try your last command (make or build) again. |
|
|
|
|
|
123sss
|
|
October 13, 2017, 09:05:12 PM |
|
0d:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0e:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
0f:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
Fri Oct 13 14:02:57 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.90 Driver Version: 384.90 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 106... Off | 00000000:01:00.0 On | N/A |
| 25% 36C P0 26W / 120W | 117MiB / 3009MiB | 7% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 106... Off | 00000000:02:00.0 Off | N/A |
| 25% 31C P8 6W / 120W | 9MiB / 3013MiB | 2% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 106... Off | 00000000:03:00.0 Off | N/A |
| 25% 35C P8 6W / 120W | 9MiB / 3013MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 106... Off | 00000000:04:00.0 Off | N/A |
| 25% 34C P8 7W / 120W | 9MiB / 3013MiB | 4% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 106... Off | 00000000:05:00.0 Off | N/A |
| 25% 36C P8 7W / 120W | 9MiB / 3013MiB | 4% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 106... Off | 00000000:06:00.0 Off | N/A |
| 25% 29C P8 7W / 120W | 9MiB / 3013MiB | 4% Default |
+-------------------------------+----------------------+----------------------+
| 6 GeForce GTX 106... Off | 00000000:09:00.0 Off | N/A |
| 25% 32C P8 7W / 120W | 9MiB / 3013MiB | 3% Default |
+-------------------------------+----------------------+----------------------+
| 7 GeForce GTX 106... Off | 00000000:0A:00.0 Off | N/A |
| 25% 32C P8 7W / 120W | 9MiB / 3013MiB | 3% Default |
+-------------------------------+----------------------+----------------------+
| 8 GeForce GTX 106... Off | 00000000:0B:00.0 Off | N/A |
| 25% 26C P8 6W / 120W | 9MiB / 3013MiB | 3% Default |
+-------------------------------+----------------------+----------------------+
| 9 GeForce GTX 106... Off | 00000000:0C:00.0 Off | N/A |
| 25% 31C P8 7W / 120W | 9MiB / 3013MiB | 5% Default |
+-------------------------------+----------------------+----------------------+
| 10 GeForce GTX 106... Off | 00000000:0D:00.0 Off | N/A |
| 25% 31C P8 7W / 120W | 9MiB / 3013MiB | 2% Default |
+-------------------------------+----------------------+----------------------+
| 11 GeForce GTX 106... Off | 00000000:0E:00.0 Off | N/A |
| 25% 33C P8 6W / 120W | 9MiB / 3013MiB | 2% Default |
+-------------------------------+----------------------+----------------------+
| 12 GeForce GTX 106... Off | 00000000:0F:00.0 Off | N/A |
| 25% 40C P8 7W / 120W | 9MiB / 3013MiB | 3% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 1111 G /usr/lib/xorg/Xorg 91MiB |
| 0 2202 G compiz 28MiB |
| 1 1111 G /usr/lib/xorg/Xorg 7MiB |
| 2 1111 G /usr/lib/xorg/Xorg 7MiB |
| 3 1111 G /usr/lib/xorg/Xorg 7MiB |
| 4 1111 G /usr/lib/xorg/Xorg 7MiB |
| 5 1111 G /usr/lib/xorg/Xorg 7MiB |
| 6 1111 G /usr/lib/xorg/Xorg 7MiB |
| 7 1111 G /usr/lib/xorg/Xorg 7MiB |
| 8 1111 G /usr/lib/xorg/Xorg 7MiB |
| 9 1111 G /usr/lib/xorg/Xorg 7MiB |
| 10 1111 G /usr/lib/xorg/Xorg 7MiB |
| 11 1111 G /usr/lib/xorg/Xorg 7MiB |
| 12 1111 G /usr/lib/xorg/Xorg 7MiB |
+-----------------------------------------------------------------------------+
Power limit for GPU 00000000:01:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:02:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:03:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:04:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:05:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:06:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:09:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:0A:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:0B:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:0C:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:0D:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:0E:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
Power limit for GPU 00000000:0F:00.0 was set to 100.00 W from 120.00 W.
Warning: persistence mode is disabled on this device. This settings will go back to default as soon as driver unloads (e.g. last application like nvidia-smi or cuda application terminates). Run with [--help | -h] switch to get more information on how to enable persistence mode.
All done.
LAUNCHING: IAmNotAJeep_and_Maxximus007_WATCHDOG
process in guake terminal Tab (f12)
LAUNCHING: Maxximus007_AUTO_TEMPERATURE_CONTROL
process in guake terminal Tab (f12)
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value 300.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:1]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:1]) assigned value 300.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:2]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:2]) assigned value 300.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:3]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:3]) assigned value 300.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:4]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:4]) assigned value 300.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:5]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:5]) assigned value 300.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:6]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:6]) assigned value 300.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:7]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:7]) assigned value 300.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:8]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:8]) assigned value 300.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:9]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:9]) assigned value 300.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:10]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:10]) assigned value 300.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:11]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:11]) assigned value 300.
Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:12]) assigned value 100.
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:12]) assigned value 300.
[screen is terminating]
What a problem??? ver v0019-1.3
|
|
|
|
|
|
123sss
|
|
October 13, 2017, 09:05:53 PM |
|
miner not started
|
|
|
|
|
|
123sss
|
|
October 13, 2017, 09:07:03 PM |
|
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:12]) assigned value 300.
There is no screen to be resumed matching miner.
|
|
|
|
|
|
car1999
|
|
October 13, 2017, 11:09:35 PM |
|
I built djm34's ccminer with Cuda9 and found that it was faster than tp ccminer on ZCOIN. If you can confirm that, use djm34's as default zcoin miner.
Would you be willing to share how you compiled? I got a bunch of "BIGNUM" errors when I tried to use -make. How do we upgrade to CUDA9? The instructions on their website didn't work for me: Installation Instructions: `sudo dpkg -i cuda-repo-ubuntu1604_9.0.176-1_amd64.deb` `sudo apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/7fa2af80.pub` `sudo apt-get update` `sudo apt-get install cuda` Thanks for your help. download openssl v1.0.2f from the offical website (look archive) then copy the file bn.h (from crypto directory) to /usr/local/include/openssl then try your last command (make or build) again. yes, fix bignum issue this way. for upgradibg to cuda9, I followed the guide in nvidia official website, it worked well, but took very long times. you also need to modify Makefile.am by hand, replace _20 and _21 with _30. |
|
|
|
|
dbolivar
Member
Offline
Activity: 119
Merit: 10
|
|
October 13, 2017, 11:35:42 PM |
|
Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:12]) assigned value 300.
There is no screen to be resumed matching miner.
What coin are you trying to mine, with which miner? In v0019-1.3, the ZM miner (ZEC) points to an invalid path in 3main. I manually fixed that in the script (or you can fix the actual path). Or switch to EWBF which works out of the box. |
|
|
|
|
damNmad
Full Member
Offline
Activity: 378
Merit: 104
nvOC forever
|
|
October 14, 2017, 12:06:47 AM |
|
Some ideas for WTM Auto Switch :
WTM AUTO SWITCH is best to set for current profit and current difficulty in whattomine.com as the other 3 whattomine.com options are only show what was in the past.
It is looking for top profitable coin at the moment which usually is the coin with most drop in difficulty.
First of all dont use too many coins as it will make too many switches and you lose time,
WTM auto switch has the option to compare the top coin with current mining coin with the given difference in percent to avoid too many switches for small profits shown.
switching to better coin is good but too many switches means too many miner restarts and each miner get some time to get to optimum speed some thing from 10 to 30 seconds.
So We have some options here.
I tried these 3 combos, each has their own pros and cons, you should try and see which one you like more.
1- Two top coins with no jumpers (10-15 % difference)
This one is the most stable option with least switches as top 10 coins usually dont change too much.
2- Two top coins with 1 jumper (10-15 % difference)
In this strategy jumper is use as a helper to switch between the 2 top coins, because usually those 2 dont get more than 10% difference
so when jumper goes to top from buttom it helps switcher pick the higher coin with less than 10% difference
3- One top coin with 1, 2 or 3 jumpers (20-40% difference)
In this scenario you mine your favorite top coin but when a jumper coin goes hot and drop big difficulty your miner start mining it until its difficulty goes high and become no more profitable
the high difference percent is to avoid jumpers to switch with each other too many times.
I'm sure there are lots of more combos to use, so please share with us your strategies and thoughts .
P.S: Latest WTM Auto Switch does not support multi algo specific overclock (damNmad awesome work) For Now, I'm Workin on to find a workaround for it.
So set damNmad_ALGO_SPECIFIC_OC="NO" and find a mid level OC to cover all the coins you chose to mine.
In the early days of my mining, I always thought that having a WTM switch kind of thing will be suffice to get better yield, but the trouble is WTM json covers only very minimum (probably the famous) on their site when you request for json result. If the whole purpose is to mine coins at low difficulty (or when difficulty dropped)! why can't we just mine and gamble the very new coins? HODL them until they get big? (don't need to completely mine them for days, a day or two should be fine). For eg; PIRL is another ethash coin where the yield by the time of writing this message is 130 odd coins per 100 MH (nearly $10 in fiat currency) B2B is another upcoming coin based on cryptonight, which is also a underrated coin! I know these may get famous or may be scrapped, but my point is even ETH/BTC/XMR also started just like the new coins, if we mine new coins for a day or two and hodl them, i think it would be a best bet on its day. This is just my opinion guys, please feel free to add your thoughts  I have already added almost more than 10 coins after 19.1 update, if anyone thing there is a new coin in the market which is worth of mining for a day or two please do let me know, i will add it to 1bash as well. |
|
|
|
jlbaseball11
Newbie
Offline
Activity: 66
Merit: 0
|
|
October 14, 2017, 12:10:49 AM |
|
Some ideas for WTM Auto Switch :
WTM AUTO SWITCH is best to set for current profit and current difficulty in whattomine.com as the other 3 whattomine.com options are only show what was in the past.
It is looking for top profitable coin at the moment which usually is the coin with most drop in difficulty.
First of all dont use too many coins as it will make too many switches and you lose time,
WTM auto switch has the option to compare the top coin with current mining coin with the given difference in percent to avoid too many switches for small profits shown.
switching to better coin is good but too many switches means too many miner restarts and each miner get some time to get to optimum speed some thing from 10 to 30 seconds.
So We have some options here.
I tried these 3 combos, each has their own pros and cons, you should try and see which one you like more.
1- Two top coins with no jumpers (10-15 % difference)
This one is the most stable option with least switches as top 10 coins usually dont change too much.
2- Two top coins with 1 jumper (10-15 % difference)
In this strategy jumper is use as a helper to switch between the 2 top coins, because usually those 2 dont get more than 10% difference
so when jumper goes to top from buttom it helps switcher pick the higher coin with less than 10% difference
3- One top coin with 1, 2 or 3 jumpers (20-40% difference)
In this scenario you mine your favorite top coin but when a jumper coin goes hot and drop big difficulty your miner start mining it until its difficulty goes high and become no more profitable
the high difference percent is to avoid jumpers to switch with each other too many times.
I'm sure there are lots of more combos to use, so please share with us your strategies and thoughts .
P.S: Latest WTM Auto Switch does not support multi algo specific overclock (damNmad awesome work) For Now, I'm Workin on to find a workaround for it.
So set damNmad_ALGO_SPECIFIC_OC="NO" and find a mid level OC to cover all the coins you chose to mine.
In the early days of my mining, I always thought that having a WTM switch kind of thing will be suffice to get better yield, but the trouble is WTM json covers only very minimum (probably the famous) on their site when you request for json result. If the whole purpose is to mine coins at low difficulty (or when difficulty dropped)! why can't we just mine and gamble the very new coins? HODL them until they get big? (don't need to completely mine them for days, a day or two should be fine). For eg; PIRL is another ethash coin where the yield by the time of writing this message is 130 odd coins per 100 MH (nearly $10 in fiat currency) B2B is another upcoming coin based on cryptonight, which is also a underrated coin! I know these may get famous or may be scrapped, but my point is even ETH/BTC/XMR also started just like the new coins, if we mine new coins for a day or two and hodl them, i think it would be a best bet on its day. This is just my opinion guys, please feel free to add your thoughts I would like to agree, but I'm feeling a little burned by SIGT right now. I am the proud owner of 10,000 SIGT, and they are not worth anything right now. Hope they come back some how. |
|
|
|
|
jlbaseball11
Newbie
Offline
Activity: 66
Merit: 0
|
|
October 14, 2017, 01:01:39 AM |
|
I built djm34's ccminer with Cuda9 and found that it was faster than tp ccminer on ZCOIN. If you can confirm that, use djm34's as default zcoin miner.
Would you be willing to share how you compiled? I got a bunch of "BIGNUM" errors when I tried to use -make. How do we upgrade to CUDA9? The instructions on their website didn't work for me: Installation Instructions: `sudo dpkg -i cuda-repo-ubuntu1604_9.0.176-1_amd64.deb` `sudo apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/7fa2af80.pub` `sudo apt-get update` `sudo apt-get install cuda` Thanks for your help. download openssl v1.0.2f from the offical website (look archive) then copy the file bn.h (from crypto directory) to /usr/local/include/openssl then try your last command (make or build) again. yes, fix bignum issue this way. for upgradibg to cuda9, I followed the guide in nvidia official website, it worked well, but took very long times. you also need to modify Makefile.am by hand, replace _20 and _21 with _30. Thanks that fixed the bignum error. I'm still getting errors though: nvcc fatal : Unsupported gpu architecture 'compute_60' Is that because of not having Cuda9? |
|
|
|
|
|
