Author

Topic: [ANN] cudaMiner & ccMiner CUDA based mining applications [Windows/Linux/MacOSX] - page 519. (Read 3426976 times)

sr. member
Activity: 350
Merit: 250
I hope so. I could do with being rich lmao
9.6MH/s has got my 65BTQ in 5 hours. So it isnt too bad but doesnt seem to be worth doing now the diff has shot up

Equals about 0.003BTC a day
full member
Activity: 238
Merit: 100
Medichain: The Medical Big-Data Platform
nomad give part of mine to bigjme & djm34, then i'll send an additional donation to bigjme from me Smiley

I will mine for 6 hours total and split it for you three equally.

Appreciate all the help, and already hit the first block... so you are all on the way to being wildly rich in the next few hours. Smiley
full member
Activity: 238
Merit: 100
Medichain: The Medical Big-Data Platform
right... that was that and some other things...  Grin

I copied over my original solo-mine from JPC and didn't realize to even look at the log/pass in the .conf file.

JPC was the first I had ever soloed... didn't realize the user/pass mattered on local mining.

Live and learn something new every day hanging around here.

I am not sure the localhost mattered, because that should resolve to 127.0.0.1 as long as the request goes through. I prefer localhost for exactly that reason as you will see it fail if you aren't getting out to the router.

I knew it was going to be something lame I was missing....

Thanks to all for the help though, it is appreciated.

I will break you off a few hours when he is done too djm. Smiley
sr. member
Activity: 350
Merit: 250
Do you guys want me to put my btq address in my sig aswell? Im fine with donations in anything in my sig
member
Activity: 76
Merit: 12
Yea!! that worked right away! thanks so much Bigjme Grin

nomad give part of mine to bigjme & djm34, then i'll send an additional donation to bigjme from me Smiley

ok lets resolve this issue quickly, bitquark.conf

Code:
rpcuser=user
rpcpassword=pass
rpcallowip=192.168.0.*
rpcallowip=127.0.0.1
rpcport=1447
listen=1
daemon=1
server=1
mintxfee=0.00001
mintxrelayfee=0.00000000
addnode=112.111.83.244:12256
addnode=103.24.88.5:50264
addnode=196.210.132.241:9596
addnode=220.166.171.10:9115
addnode=76.108.164.127:57864
addnode=81.154.205.63:55289
addnode=203.156.196.226:61682
addnode=69.8.51.75:35542
addnode=5.9.248.182:60084
addnode=124.234.48.148:14129
addnode=125.70.106.2:9596
addnode=91.67.71.178:9596
addnode=42.239.119.231:9596
addnode=64.53.248.79:9596
addnode=118.112.122.146:9596
addnode=98.119.203.187:9596
addnode=46.119.119.40:9596
addnode=114.66.195.170:9596
addnode=58.47.58.15:9596
addnode=62.210.123.27:9596
addnode=182.91.54.125:9596
addnode=122.192.218.120:9596
addnode=178.49.193.142:9596
addnode=174.107.145.6:9596
addnode=115.28.161.67:9596
addnode=210.195.183.143:9596
addnode=123.161.55.60:9596

bat file
Code:
ccminer.exe -s 1 -a quark -d 2 -o http://127.0.0.1:1447 -u user -p pass

update -d to your devices, thats what i run on mine and works. make sure you stop bitquark wallet before changing the config file and start it after the file is saved and closed
full member
Activity: 238
Merit: 100
Medichain: The Medical Big-Data Platform
~2800 Khash/s per 750ti seem about right? That is with no overclocking....

have it up and running for 6 cards right now, and will fiddle with OC settings later tonight when I am in front of the machine.

Thanks for the help guys.
legendary
Activity: 1400
Merit: 1050
For doing solo mining. For user does it have to be -u bitquark -p password, because that's what's in the .conf file?



BREADPUDDING GETS A COOKIE!!!

That was it...

Anything I find the next 4 hours is all yours.

Please post me an address to send it to Smiley

Thanks again
right... that was that and some other things...  Grin
full member
Activity: 238
Merit: 100
Medichain: The Medical Big-Data Platform
For doing solo mining. For user does it have to be -u bitquark -p password, because that's what's in the .conf file?



BREADPUDDING GETS A COOKIE!!!

That was it...

Anything I find the next 4 hours is all yours.

Please post me an address to send it to Smiley

Thanks again
sr. member
Activity: 350
Merit: 250
ok lets resolve this issue quickly, bitquark.conf

Code:
rpcuser=user
rpcpassword=pass
rpcallowip=192.168.0.*
rpcallowip=127.0.0.1
rpcport=1447
listen=1
daemon=1
server=1
mintxfee=0.00001
mintxrelayfee=0.00000000
addnode=112.111.83.244:12256
addnode=103.24.88.5:50264
addnode=196.210.132.241:9596
addnode=220.166.171.10:9115
addnode=76.108.164.127:57864
addnode=81.154.205.63:55289
addnode=203.156.196.226:61682
addnode=69.8.51.75:35542
addnode=5.9.248.182:60084
addnode=124.234.48.148:14129
addnode=125.70.106.2:9596
addnode=91.67.71.178:9596
addnode=42.239.119.231:9596
addnode=64.53.248.79:9596
addnode=118.112.122.146:9596
addnode=98.119.203.187:9596
addnode=46.119.119.40:9596
addnode=114.66.195.170:9596
addnode=58.47.58.15:9596
addnode=62.210.123.27:9596
addnode=182.91.54.125:9596
addnode=122.192.218.120:9596
addnode=178.49.193.142:9596
addnode=174.107.145.6:9596
addnode=115.28.161.67:9596
addnode=210.195.183.143:9596
addnode=123.161.55.60:9596

bat file
Code:
ccminer.exe -s 1 -a quark -d 2 -o http://127.0.0.1:1447 -u user -p pass

update -d to your devices, thats what i run on mine and works. make sure you stop bitquark wallet before changing the config file and start it after the file is saved and closed
member
Activity: 76
Merit: 12
For doing solo mining. For user does it have to be -u bitquark -p password, because that's what's in the .conf file?

full member
Activity: 238
Merit: 100
Medichain: The Medical Big-Data Platform
This will sound very stupid to you guys but change localhost to 127.0.0.1
Their different

Also dont tick the mining enabled button. That is cpu mining thats built into the wallet

Just tried that... also didn't work.

Code:
C:\mining\ccminer-v0.9\compute 3.5\maxwell\x86>ccminer.exe -a quark -o 127.0.0.1:9108
 -u user -p pass -s 1
     *** ccMiner for nVidia GPUs by Christian Buchner and Christian H. ***
                     This is version 0.9 (beta)
          based on pooler-cpuminer 2.3.2 (c) 2010 Jeff Garzik, 2012 pooler
          based on pooler-cpuminer extension for HVC from
               https://github.com/heavycoin/cpuminer-heavycoin
                        and
               http://hvc.1gh.com/
        Cuda additions Copyright 2014 Christian Buchner, Christian H.
          LTC donation address: LKS1WDKGED647msBQfLBHV3Ls8sveGncnm
          BTC donation address: 16hJF5mceSojnTD3ZTUDqdRhDyPJzoRakM
          YAC donation address: Y87sptDEcpLkLeAuex6qZioDbvy1qXZEj4
[2014-05-06 14:35:45] Binding thread 1 to cpu 1
[2014-05-06 14:35:45] 6 miner threads started, using 'quark' algorithm.
[2014-05-06 14:35:45] Binding thread 4 to cpu 4
[2014-05-06 14:35:45] Binding thread 0 to cpu 0
[2014-05-06 14:35:45] Binding thread 2 to cpu 2
[2014-05-06 14:35:45] Binding thread 3 to cpu 3
[2014-05-06 14:35:45] Binding thread 5 to cpu 5
[2014-05-06 14:35:45] HTTP request failed: The requested URL returned error: 401
[2014-05-06 14:35:45] json_rpc_call failed, retry after 30 seconds

Thanks for all the suggestions though! Keep em coming if you have any other ideas! Smiley
sr. member
Activity: 350
Merit: 250
It wont. Your error is stating localhost istead of 127.0.0.1

They mean the same thing but the number version is allowed in the wallet
full member
Activity: 238
Merit: 100
Medichain: The Medical Big-Data Platform
nomad, i'm trying to set up solo mining also.

I'm getting the same error as you.

I get the same error if I check the 'mining enabled' in the options mining tab.

It was not checked, but I tried it again with it checked and unchecked and it didn't make any change to that error.

Sad
sr. member
Activity: 350
Merit: 250
This will sound very stupid to you guys but change localhost to 127.0.0.1
Their different

Also dont tick the mining enabled button. That is cpu mining thats built into the wallet
full member
Activity: 238
Merit: 100
Medichain: The Medical Big-Data Platform
your rpcport (local port) is 9108 and does match the one in ccminer. it should be localhost:9108 and not localhost:9596 (9596 is the distant port)

So I switched that to 9108...

Code:
[2014-05-06 14:27:03] 6 miner threads started, using 'quark' algorithm.
[2014-05-06 14:27:03] Binding thread 1 to cpu 1
[2014-05-06 14:27:03] Binding thread 5 to cpu 5
[2014-05-06 14:27:03] Binding thread 2 to cpu 2
[2014-05-06 14:27:03] Binding thread 3 to cpu 3
[2014-05-06 14:27:03] Binding thread 0 to cpu 0
[2014-05-06 14:27:03] Binding thread 4 to cpu 4
[2014-05-06 14:27:03] HTTP request failed: The requested URL returned error: 401
[2014-05-06 14:27:03] json_rpc_call failed, retry after 30 seconds

It is such a basic config, and everything is working fine mining JPC, so I am just not sure where the problem is...

This was the string that was from

ccminer.exe -a quark -o localhost:9108 -u user -p pass -s 1
member
Activity: 76
Merit: 12
nomad, i'm trying to set up solo mining also.

I'm getting the same error as you.

I get the same error if I check the 'mining enabled' in the options mining tab.
legendary
Activity: 1400
Merit: 1050
most likely a problem with the conf file your the coin you are mining
did you put server=1 in it ? (or wrong rpcport)

Here is what my bitquark.conf file contains...

rpcuser=bitquark
rpcpassword=password
rpcallowip=127.0.0.1
rpcallowip=192.168.*.*
rpcport=9108
port=9596
addnode=112.111.83.244:12256
addnode=103.24.88.5:50264
addnode=196.210.132.241:9596
addnode=220.166.171.10:9115
addnode=76.108.164.127:57864
addnode=81.154.205.63:55289
addnode=203.156.196.226:61682
addnode=69.8.51.75:35542
addnode=5.9.248.182:60084
addnode=124.234.48.148:14129
gen=0
server=1
listen=1
mintxfee=0.00001
mintxrelayfee=0.00000000
your rpcport (local port) is 9108 and does not match the one in ccminer. it should be localhost:9108 and not localhost:9596 (9596 is the distant port)
legendary
Activity: 1400
Merit: 1050
Oh bummer sorry about your loss  Sad

Does your message mean that I should put in my payment (wallet) address?

I had the same problem, now I'm over at https://cpu-pool.net/btq/ and able to submit a lot more  Smiley

I can barely even get a thread accepted over at btq.ext-pool.net....
careful though you might get banned without any payment... I think that pool was doing this on qubitcoin when the first gpu miner were out (lost around 1000qubit... )
by the way, do you have qubit in the queue with ccminer (not worth a lot though, but could very well resurface, also used for myriad)
I got over it long time ago...
was thinking to that, but it seems that for some quark pool, they use a new feature in sgminer to change the difficulty so they can mine it. may-be it is something like that which affect ccminer on certain pools (?)
full member
Activity: 238
Merit: 100
Medichain: The Medical Big-Data Platform
most likely a problem with the conf file your the coin you are mining
did you put server=1 in it ? (or wrong rpcport)

Here is what my bitquark.conf file contains...

rpcuser=bitquark
rpcpassword=password
rpcallowip=127.0.0.1
rpcallowip=192.168.*.*
rpcport=9108
port=9596
addnode=112.111.83.244:12256
addnode=103.24.88.5:50264
addnode=196.210.132.241:9596
addnode=220.166.171.10:9115
addnode=76.108.164.127:57864
addnode=81.154.205.63:55289
addnode=203.156.196.226:61682
addnode=69.8.51.75:35542
addnode=5.9.248.182:60084
addnode=124.234.48.148:14129
gen=0
server=1
listen=1
mintxfee=0.00001
mintxrelayfee=0.00000000
legendary
Activity: 1400
Merit: 1050
Code:
[2014-05-06 14:09:16] 6 miner threads started, using 'quark' algorithm.
[2014-05-06 14:09:16] Binding thread 0 to cpu 0
[2014-05-06 14:09:16] Binding thread 2 to cpu 2
[2014-05-06 14:09:16] Binding thread 1 to cpu 1
[2014-05-06 14:09:16] Binding thread 5 to cpu 5
[2014-05-06 14:09:16] Binding thread 3 to cpu 3
[2014-05-06 14:09:16] Binding thread 4 to cpu 4
[2014-05-06 14:09:16] HTTP request failed: Empty reply from server
[2014-05-06 14:09:16] json_rpc_call failed, retry after 30 seconds

I am getting this HTTP error trying to set up bitquark mining....

Anyone have an example of the config they are using to solo mine?

I fed in...

ccminer.exe -a quark -o localhost:9596 -u user -p pass -s 1

Am I missing something? Thanks in advance.
most likely a problem with the conf file your the coin you are mining
did you put server=1 in it ? (or wrong rpcport)
Jump to: