PPC solo mining?

[mech]

I run a server ppcoind
Connect GUIminer in solo mode
Connection is successfully established, but the rate of a thousand times smaller than it should be - 300 kHash!
What am I doing wrong?

[Vuxil]

Start hashing away at ppcpool.bitparking.com so you don't lose time. Minimum payout there is low, so you can quickly stop hashing there when you figure out what problem you are having and switch back to solo mining.

In the mean time, can you tell us more about your setup? Can you tell us how you have configured your server? ppc config file?

[mech]

Start hashing javascript:void(0);away at ppcpool.bitparking.com so you don't lose time. Minimum payout there is low, so you can quickly stop hashing there when you figure out what problem you are having and switch back to solo mining.

In the mean time, can you tell us more about your setup? Can you tell us how you have configured your server? ppc config file?

Oк. ppcoin.conf:

Code:

# ppcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=0

# Connect via a socks4 proxy - default none
#proxy=127.0.0.1:9050
# Accepting incoming connections
listen=1
# UPnP
#upnp=1

##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# ... or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Maximum number of inbound+outbound connections.
maxconnections=64


# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

# server=1 tells Bitcoin-QT to accept JSON-RPC commands.
server=1

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
rpcuser=x
rpcpassword=x

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
rpctimeout=30

# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
rpcallowip=127.0.0.1
rpcallowip=192.168.2.*

# Listen for RPC connections on this TCP port:
rpcport=9902

# You can use ppcoind to send commands to ppcoind
# running on another host using this option:
rpcconnect=127.0.0.1

# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with ppcoind
#rpcssl=1

# OpenSSL settings used when rpcssl=1
#rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
#rpcsslcertificatechainfile=server.cert
#rpcsslprivatekeyfile=server.pem

# Miscellaneous options

# Set gen=1 to attempt to generate ppcoins using built-in CPU mining
#gen=1

# Use SSE instructions to try to generate bitcoins faster.
#4way=1

# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
#keypool=100

# Pay transaction fee amount per kilo-byte. Default 0.01 (1 cent)
# Minimum required 0.01 (1 cent)
#paytxfee=0.01

# Allow direct connections for the 'pay via IP address' feature.
allowreceivebyip=1

ppcoind getinfo result:

Code:

C:\Program Files\PPCoin\daemon>ppcoind getinfo
{
    "version" : "v0.3.0ppc-beta",
    "protocolversion" : 60003,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 39827,
    "moneysupply" : 17855111.98138700,
    "connections" : 1,
    "proxy" : "",
    "ip" : "79.142.88.19",
    "difficulty" : 45786.88897891,
    "testnet" : false,
    "keypoololdest" : 1364751450,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

guiminer setting (on server pc):

Code:

{
            "username": "x", 
            "balance_auth_token": "", 
            "name": "G-ppc1", 
            "hostname": "localhost", 
            "external_path": "", 
            "affinity_mask": 2, 
            "flags": "", 
            "autostart": true, 
            "device": 0, 
            "password": "x", 
            "port": "9902"
        }, 
        {
            "username": "x", 
            "balance_auth_token": "", 
            "name": "G-ppc2", 
            "hostname": "localhost", 
            "external_path": "", 
            "affinity_mask": 1, 
            "flags": "", 
            "autostart": true, 
            "device": 1, 
            "password": "x", 
            "port": "9902"
        }

and minning result - 370 kHash/s (expected 515 Mhash/s)

[dreamwatcher]

Personally I would just move to cgminer.

 AS for your coin config, get rid of all the extra garbage in the file. (ppcoin.conf)

Code:

server=1
rpcuser=<user>
rpcpassword=<nice long password>
rpcallowip=127.0.0.1
rpcallowip=192.168.2.*
rpcport=9902   [Totally optional as 9902 is the default PPC rpc port]

Getinfo:

Code:

{
    "version" : "v0.3.0ppc-beta",
    "protocolversion" : 60003,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 39827,
    "moneysupply" : 17855111.98138700,
    "connections" : 1,
    "proxy" : "",
    "ip" : "79.142.88.19",
    "difficulty" : 45786.88897891,
    "testnet" : false,
    "keypoololdest" : 1364751450,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

Looks normal, you really should have more then one connection to the network.
Add

Code:

addnode=84.200.84.74

to your ppcoin.conf file. Your daemon will try to connect to the cryptocoinexplorer daemon and It always has plenty of peer connections

Cgminer config file:  located in the .cgminer folder in your Home folder.

Code:

"pools" : [
        {
                "url" : "http://172.16.16.200:9902",
                "user" : "<User>",
                "pass" : "<Passworrd>'"
        }
]
,
"intensity" : "5",
"vectors" : "2,2,2",
"worksize" : "128,128,128",
"kernel" : "diablo,diablo,diablo",
"lookup-gap" : "0,0,0",
"thread-concurrency" : "0,0,0",
"shaders" : "0,0,0",
"gpu-engine" : "850",
"gpu-fan" : "0-65",
"gpu-memclock" : "800",
"gpu-memdiff" : "0,0,0",
"gpu-powertune" : "0,0,0",
"gpu-vddc" : "0.000,0.000,0.000",
"temp-cutoff" : "95,95,95",
"temp-overheat" : "85,85,85",
"temp-target" : "75,75,75",
"api-port" : "4028",
"expiry" : "120",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"gpu-threads" : "2",
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"queue" : "1",
"scan-time" : "60",
"temp-hysteresis" : "3",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}

You can grab CGminer at: https://bitcointalk.org/index.php?topic=28402.0
 
Direct link All files available from here:
http://ck.kolivas.org/apps/cgminer


I use a small startup script to start ther miner:

Code:

#! /bin/bash
export DISPLAY=:0

export GPU_USE_SYNC_OBJECTS=1

./cgminer

do not forget to chmod +x <name of scrypt, you just made. just use cg.sh>

You start the mining process with a simple    ./cg.sh  <enter>

Code:

miner@miner1:~/cgminer-2.11.2-x86_64-built$ ./cg.sh

2013-04-01 00:14:25] Started cgminer 2.11.2
 [2013-04-01 00:14:25] Started cgminer 2.11.2
 [2013-04-01 00:14:25] Loaded configuration file /home/miner/.cgminer/cgminer.conf
 [2013-04-01 00:14:26] Probing for an alive pool
 [2013-04-01 00:14:27] Long-polling activated for http://84.200.84.76:8339/LP
cgminer version 2.11.2 - Started: [2013-04-01 00:14:27]



--------------------------------------------------------------------------------
 (5s):1.111G (avg):1.103Gh/s | Q:4  A:0  R:0  HW:0  E:0%  U:0.0/m
 ST: 2  SS: 0  DW: 0  NB: 1  LW: 20  GF: 0  RF: 0  WU: 18.7
 Connected to 84.200.84.76 diff 8.29K with LP as user miner
 Block: 7dea3234228022c6...  Diff:8.29K  Started: [00:14:27]  Best share: 10
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0:  58.0C 3450RPM | 380.7M/406.4Mh/s | A:0 R:0 HW:0 U:0.00/m I: 5
 GPU 1:  50.0C 3110RPM | 380.0M/399.7Mh/s | A:0 R:0 HW:0 U:0.00/m I: 5
 GPU 2:  58.5C  65%    | 368.1M/388.5Mh/s | A:0 R:0 HW:0 U:0.00/m I: 5
--------------------------------------------------------------------------------

 [2013-04-01 00:14:25] Started cgminer 2.11.2
 [2013-04-01 00:14:25] Loaded configuration file /home/miner/.cgminer/cgminer.conf
 [2013-04-01 00:14:26] Probing for an alive pool
 [2013-04-01 00:14:27] Long-polling activated for http://84.200.84.76:8339/LP

Ok, well I am way overtired, if you still have questions feel free to ask. I will help as much as I can,,,,

[mech]

Thank you! I will try.