I haven't been able to find a reason that I keep getting the GPU miner to keep closing after declaring a socket error. I've tried multiple pools, multiple ports, etc. I'm sure it's something silly as I'm new to this, and particularly have never used the XMR STAK miner. I'm used to using the Claymore miners and am doing so again successfully with the CPU version for ETN. I'm trying to use an NVIDIA GPU miner for ETN and unless I'm missing something, XMR STAK is the best option ... except that I can't get it to work.
I'm using my laptop for this as an experiment. My CPU is an i7-4720, and I have a lonely Nvidia GTX 950M that is completely unused. I know it's not going to do much for me, but my main mining rig is busy using it's 1070s for ETH. So I'm playing with ETN to figure out how to do it and maybe decide to do it and/or XMR in the long run.
I'm currently mining ETN on etn.proxpool.com as they have no fees through January, and it's working fine on my CPU Claymore miner.
PS, I'm running separate instances of miners. One .exe file for the Claymore CPU miner and one .exe file for the XMR GPU miner (that doesn't execute).
I've pasted the config.txt file here. Any ideas? Thank you!
/*
GPU configuration. You should play around with threads and blocks as the fastest settings will vary.
index - GPU index number usually starts from 0.
threads - Number of GPU threads (nothing to do with CPU threads).
blocks - Number of GPU blocks (nothing to do with CPU threads).
bfactor - Enables running the Cryptonight kernel in smaller pieces.
Increase if you want to reduce GPU lag. Recommended setting on GUI systems - 8
bsleep - Insert a delay of X microseconds between kernel launches.
Increase if you want to reduce GPU lag. Recommended setting on GUI systems - 100
affine_to_cpu - This will affine the thread to a CPU. This can make a GPU miner play along nicer with a CPU miner.
On the first run the miner will look at your system and suggest a basic configuration that will work,
you can try to tweak it from there to get the best performance.
If you need real security, make sure tls_secure_algo is enabled (otherwise MITM attack can downgrade encryption
to trivially breakable stuff like DES and MD5), and verify the server's fingerprint through a trusted channel.
use_tls - This option will make us connect using Transport Layer Security.
tls_secure_algo - Use only secure algorithms. This will make us quit with an error if we can't negotiate a secure algo.
tls_fingerprint - Server's SHA256 fingerprint. If this string is non-empty then we will check the server's cert against it.
*/
"use_tls" : false,
"tls_secure_algo" : false,
"tls_fingerprint" : "",
/*
pool_address - Pool address should be in the form "pool.supportxmr.com:3333". Only stratum pools are supported.
wallet_address - Your wallet, or pool login.
pool_password - Can be empty in most cases or "x".
*/
"pool_address" : "stratum+tcp://etn-pool.proxpool.com:443",
"wallet_address" : "MY ADDRESS IS REAL AND IS BEING REPORTED CORRECTLY ON THE CPU MINER",
"pool_password" : "x",
/*
Network timeouts.
Because of the way this client is written it doesn't need to constantly talk (keep-alive) to the server to make
sure it is there. We detect a buggy / overloaded server by the call timeout. The default values will be ok for
nearly all cases. If they aren't the pool has most likely overload issues. Low call timeout values are preferable -
long timeouts mean that we waste hashes on potentially stale jobs. Connection report will tell you how long the
server usually takes to process our calls.
call_timeout - How long should we wait for a response from the server before we assume it is dead and drop the connection.
retry_time - How long should we wait before another connection attempt.
Both values are in seconds.
giveup_limit - Limit how many times we try to reconnect to the pool. Zero means no limit. Note that stak miners
don't mine while the connection is lost, so your computer's power usage goes down to idle.
*/
"call_timeout" : 10,
"retry_time" : 10,
"giveup_limit" : 0,
/*
Output control.
Since most people are used to miners printing all the time, that's what we do by default too. This is suboptimal
really, since you cannot see errors under pages and pages of text and performance stats. Given that we have internal
performance monitors, there is very little reason to spew out pages of text instead of concise reports.
Press 'h' (hashrate), 'r' (results) or 'c' (connection) to print reports.
Hello all,
I haven't been able to find a reason that I keep getting the GPU miner to keep closing after declaring a socket error. I've tried multiple pools, multiple ports, etc. I'm sure it's something silly as I'm new to this, and particularly have never used the XMR STAK miner. I'm used to using the Claymore miners and am doing so again successfully with the CPU version for ETN. I'm trying to use an NVIDIA GPU miner for ETN and unless I'm missing something, XMR STAK is the best option ... except that I can't get it to work.
I'm using my laptop for this as an experiment. My CPU is an i7-4720, and I have a lonely Nvidia GTX 950M that is completely unused. I know it's not going to do much for me, but my main mining rig is busy using it's 1070s for ETH. So I'm playing with ETN to figure out how to do it and maybe decide to do it and/or XMR in the long run.
I'm currently mining ETN on etn.proxpool.com as they have no fees through January, and it's working fine on my CPU Claymore miner.
PS, I'm running separate instances of miners. One .exe file for the Claymore CPU miner and one .exe file for the XMR GPU miner (that doesn't execute).
I've pasted the config.txt file here. Any ideas? Thank you!
/*
], /*
/*
/*
/*
/*
/*
/*
*/ "output_file" : "",
/*
/*