[XMR] Monero Mining

[GingerAle]

Anyone mining XMR with a nVidia GPU on Windows 10? It was working great for me (using tsiv's miner) on previous drivers but when I upgraded to 355.78 I keep getting "result for nonce does not validate" error messages while mining. Now obviously the smart thing to do is roll back drivers which I've done and it works again, but, does anyone have any insight as to why this is happening? I'm not running overclocked on my GPU, it's properly cooled and seems to be an issue with the drivers and nothing more. Perhaps it's a driver/Win10 incompatibility. Is everyone still using tsiv's miner on Windows? It was last updated over a year ago so if anyone can recommend me another nVidia GPU miner to try and see if that fixes my problem, that would be great!

Just an FYI for everyone... I've updated to 358.78 and it seems the validate errors are gone. I'll keep an eye on it but whatever changes nVidia made they've either fixed or reverted.

fwiw, i'e found that the 331 drivers give about ~3 h/s higher than the newer ones (352 etc)

[superresistant]

fwiw, i'e found that the 331 drivers give about ~3 h/s higher than the newer ones (352 etc)

3 hash/s seems to small to make a real difference IMO.
Have you tested it for at least 24 hours ?

[GingerAle]

fwiw, i'e found that the 331 drivers give about ~3 h/s higher than the newer ones (352 etc)

3 hash/s seems to small to make a real difference IMO.
Have you tested it for at least 24 hours ?

yeah. literally, my 750 tis get 247 h/s on newer stuff, and 250 on old stuff

[GingerAle]

it just so happens that I have one machine with the 33x and one with the 35x

[smooth]

I'm not denying that its probably difficult to manage a botnet. I would just argue that the "resources" used to mine skew some of the assumptions made that underlie the purpose of POW.

Probably not skewing the assumptions too much considering that satoshi wrote about botnets and said they make the network more secure.

He may have been more interested in security functions than price action though.
 

[c789]

I had been running a private Monero pool using zone117x (https://github.com/zone117x/node-cryptonote-pool) for the pool server and 0.8.8.6 monerod on Ubuntu 14.04. Then I pulled the latest Monero from github about a month ago to replace the 0.8.8.6 monerod. Now none of my mining computers can connect to the pool (all on a wireless LAN, no problems before). Did anyone else experience this? How can it be fixed?

No apparent problems when starting node:

Code:

sudo node init.js                                                                                                                 
[sudo] password for mike: 
2015-10-29 23:29:03 [master] Pool spawned on 2 thread(s)
2015-10-29 23:29:04 [unlocker] Started
2015-10-29 23:29:04 [charts] Started
2015-10-29 23:29:04 [chartsDataCollector] Started
2015-10-29 23:29:04 [unlocker] No blocks candidates in redis
2015-10-29 23:29:04 [charts] Started
2015-10-29 23:29:04 [api] API started & listening on port 8117
2015-10-29 23:29:04 [api] Stat collection finished: 41 ms redis, 48 ms daemon
2015-10-29 23:29:04 [api] Broadcasting to 0 visitors and 0 address lookups
2015-10-29 23:29:04 [pool] (Thread 2) New block to mine at height 803840 w/ difficulty of 673327508
2015-10-29 23:29:04 [pool] (Thread 1) New block to mine at height 803840 w/ difficulty of 673327508
2015-10-29 23:29:04 [pool] (Thread 2) Started server listening on port 3333
2015-10-29 23:29:04 [pool] (Thread 1) Started server listening on port 3333

Miner can't connect to pool:

Code:

sudo ./minerd -a cryptonight -o stratum+tcp://10.0.0.25:3333 -u 4moneroaddressthisismymonerowalletaddressthisismymonerowalletaddressthisismymonerowalletaddress -p x -t 3
[sudo] password for mike: 
[2015-10-29 23:27:41] Using JSON-RPC 2.0
[2015-10-29 23:27:41] Starting Stratum on stratum+tcp://10.0.0.25:3333
[2015-10-29 23:27:41] 3 miner threads started, using 'cryptonight' algorithm.
[2015-10-29 23:27:41] Stratum connection failed: Failed to connect to 10.0.0.25 port 3333: Connection refused
[2015-10-29 23:27:41] ...retry after 10 seconds

[OrientA]

I'm not denying that its probably difficult to manage a botnet. I would just argue that the "resources" used to mine skew some of the assumptions made that underlie the purpose of POW.

Probably not skewing the assumptions too much considering that satoshi wrote about botnets and said they make the network more secure.

He may have been more interested in security functions than price action though.
 

Even though Satosh did not think botnet is bad for bitcoin, I think botnet is bad for Monero. One reason for the low and dropping price of Monero is that the existence of botnet on Monero network. Botnet is too large proportion of Monero hashing power. If they want to evil things to Monero, then Monero is in trouble.

[nioc]

I'm not denying that its probably difficult to manage a botnet. I would just argue that the "resources" used to mine skew some of the assumptions made that underlie the purpose of POW.

Probably not skewing the assumptions too much considering that satoshi wrote about botnets and said they make the network more secure.

He may have been more interested in security functions than price action though.
 

Even though Satosh did not think botnet is bad for bitcoin, I think botnet is bad for Monero. One reason for the low and dropping price of Monero is that the existence of botnet on Monero network. Botnet is too large proportion of Monero hashing power. If they want to evil things to Monero, then Monero is in trouble.

Botnet or botnets?  It seems to me that the motivation of botnets is the same as virtually any miner which is greed.  I say virtually because some miners mine in order to obtain coins without going through an exchange and some mine to support the network.  Greed is ofc the prime motivating factor for any coin including Satoshi's.

[GingerAle]

I had been running a private Monero pool using zone117x (https://github.com/zone117x/node-cryptonote-pool) for the pool server and 0.8.8.6 monerod on Ubuntu 14.04. Then I pulled the latest Monero from github about a month ago to replace the 0.8.8.6 monerod. Now none of my mining computers can connect to the pool (all on a wireless LAN, no problems before). Did anyone else experience this? How can it be fixed?

No apparent problems when starting node:

Code:

sudo node init.js                                                                                                                 
snp code
ed to connect to 10.0.0.25 port 3333: Connection refused
[2015-10-29 23:27:41] ...retry after 10 seconds

I was running a private pool fine with the new code... so its not the new code. Its something with your configuration. For the record, i've been using both sammy_007s branch and zone's.

[c789]

I was running a private pool fine with the new code... so its not the new code. Its something with your configuration. For the record, i've been using both sammy_007s branch and zone's.

It helps to know that the new code for monerod works well since that will narrow my troubleshooting. So now it looks like node is the problem. I didn't change config.json (below). Does this look ok to you? What other settings should I check?

config.json (wallet addr changed)

Code:

{
    "coin": "Monero",
    "symbol": "XMR",
    "logging": {
        "files": {
            "level": "info",
            "directory": "logs",
            "flushInterval": 5
        },
        "console": {
            "level": "info",
            "colors": true
        }
    },

    "poolServer": {
        "enabled": true,
        "clusterForks": "auto",
        "poolAddress": "4mymonerowalletaddress4mymonerowalletaddress4mymonerowalletaddress4mymonerowalletaddress",
        "blockRefreshInterval": 1000,
        "minerTimeout": 900,
        "ports": [
            {
                "port": 3333,
                "difficulty": 100,
                "desc": "Low end hardware"
            }
        ],
        "varDiff": {
            "minDiff": 2,
            "maxDiff": 120000,
            "targetTime": 100,
            "retargetTime": 30,
            "variancePercent": 30,
            "maxJump": 100
        },
        "shareTrust": {
            "enabled": true,
            "min": 10,
            "stepDown": 3,
            "threshold": 10,
            "penalty": 30
        },
        "banning": {
            "enabled": true,
            "time": 600,
            "invalidPercent": 25,
            "checkThreshold": 30
        }
    },

    "payments": {
        "enabled": false,
        "interval": 600,
        "maxAddresses": 50,
        "mixin": 3,
        "transferFee": 50000000,
        "minPayment": 1000000000,
        "maxTransactionAmount": 0,
        "denomination": 1000000000
    },

    "blockUnlocker": {
        "enabled": true,
        "interval": 30,
        "depth": 10,
        "poolFee": 0.0,
        "devDonation": 0.0,
        "coreDevDonation": 0.0
    },

    "api": {
        "enabled": true,
        "hashrateWindow": 600,
        "updateInterval": 15,
        "port": 8117,
        "blocks": 30,
        "payments": 30,
        "password": "xxxx"
    },

    "daemon": {
        "host": "127.0.0.1",
        "port": 18081
    },

    "wallet": {
        "host": "127.0.0.1",
        "port": 8082
    },

    "redis": {
        "host": "127.0.0.1",
        "port": 6379
    },

    "monitoring": {
        "daemon": {
            "checkInterval": 60,
            "rpcMethod": "getblockcount"
        },
        "wallet": {
            "checkInterval": 60,
            "rpcMethod": "getbalance"
        }
    },

    "charts": {
        "pool": {
            "hashrate": {
                "enabled": true,
                "updateInterval": 60,
                "stepInterval": 1800,
                "maximumPeriod": 86400
            },
            "workers": {
                "enabled": true,
                "updateInterval": 60,
                "stepInterval": 1800,
                "maximumPeriod": 86400
            },
            "difficulty": {
                "enabled": true,
                "updateInterval": 1800,
                "stepInterval": 10800,
                "maximumPeriod": 604800
            },
            "price": {
                "enabled": true,
                "updateInterval": 1800,
                "stepInterval": 10800,
                "maximumPeriod": 604800
            },
            "profit": {
                "enabled": true,
                "updateInterval": 1800,
                "stepInterval": 10800,
                "maximumPeriod": 604800
            }
        },
        "user": {
            "hashrate": {
                "enabled": true,
                "updateInterval": 180,
                "stepInterval": 1800,
                "maximumPeriod": 86400
            },
            "payments": {
                "enabled": false
            }
        }
    }
}

[Livesms]

Can I as for really working and stable Monero mining pools ?

[GingerAle]

Can I as for really working and stable Monero mining pools ?

monerohash.com is stable and the op is great. though I dunno what continent you're on.

[Livesms]

Can I as for really working and stable Monero mining pools ?

monerohash.com is stable and the op is great. though I dunno what continent you're on.

Europe. Ukraine.

[GingerAle]

Can I as for really working and stable Monero mining pools ?

monerohash.com is stable and the op is great. though I dunno what continent you're on.

Europe. Ukraine.

check this list

https://monerohash.com/#network

[superresistant]

Can I as for really working and stable Monero mining pools ?

monerohash.com is stable and the op is great. though I dunno what continent you're on.

Europe. Ukraine.

check this list
https://monerohash.com/#network

I didn't realize that the unknown part became so huge.

[c789]

Hello,

I'm running Ubuntu 14.04 64-bit and cloned the latest Wolf GPU AMD miner code from Github. I tried "sudo make" and got the following output. Any ideas?

Code:

gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c crypto/aesb.c -o crypto/aesb.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c crypto/aesb-x86-impl.c -o crypto/aesb-x86-impl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c crypto/c_blake256.c -o crypto/c_blake256.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c crypto/c_groestl.c -o crypto/c_groestl.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c crypto/c_keccak.c -o crypto/c_keccak.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c crypto/c_jh.c -o crypto/c_jh.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c crypto/c_skein.c -o crypto/c_skein.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c crypto/oaes_lib.c -o crypto/oaes_lib.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c cryptonight.c -o cryptonight.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c log.c -o log.o
log.c: In function ‘Log’:
log.c:25:3: warning: format not a string literal and no format arguments [-Wformat-security]
   printf(timebuf);
   ^
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c net.c -o net.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c minerutils.c -o minerutils.o
gcc -D_POSIX_SOURCE -D_GNU_SOURCE -O0 -ggdb3 -std=c11 -pthread -c gpu.c -o gpu.o
gpu.c:6:19: fatal error: CL/cl.h: No such file or directory
 #include <CL/cl.h>
                   ^
compilation terminated.
make: *** [all] Error 1

[smooth]

I'm not an expert on GPU miners but it looks like you don't have the OpenCL SDK installed or properly configured.

[c789]

Thanks! I was afraid of that, but that is very helpful info and I should be able to be mining in a few days. My GPU has other uses and it took me days to get it configured correctly. Since I don't want to mess with those settings, my solution to this situation will be to put a separate hard drive with Ubuntu in the computer to be used for mining/other purposes. I'd just use a different partition on the existing HD but the HD is getting full and I have a few spare HDs. That sounds like the long way to a solution but it'll be fun for me and will allow me to preserve my existing GPU settings.

[GingerAle]

Thanks! I was afraid of that, but that is very helpful info and I should be able to be mining in a few days. My GPU has other uses and it took me days to get it configured correctly. Since I don't want to mess with those settings, my solution to this situation will be to put a separate hard drive with Ubuntu in the computer to be used for mining/other purposes. I'd just use a different partition on the existing HD but the HD is getting full and I have a few spare HDs. That sounds like the long way to a solution but it'll be fun for me and will allow me to preserve my existing GPU settings.

Thanks for checking out the new miner. If you get it working, can you post screenshots? What kind of GPU do you have?

[c789]

Yes, I'll post screenshots. Unfortunately it will be in about a week since work just heated up. It's an older card, Radeon HD 6770.