New Miner Needing Help with HD7870 settings on NSGminer?

greenuser

I will edit the conf like this

{
“pools” : [
{
“url” : “http://p2pool.neoscrypt.de:19327”,
“user” : “6wTKzQovBDnMrhxtcR44KyLz3xWAPx15Ap”,
“pass” : “”,
“pool-priority” : “0”
}
]
,
“temp-cutoff” : “90,90,90,90”,
“temp-target” : “75,75,75,75”,
“intensity” : “13,13,13,13”,
“vectors” : “1,1,1,1”,
“worksize” : “256,256,256,256”,
“kernel” : “neoscrypt,neoscrypt,neoscrypt,neoscrypt”,
“lookup-gap” : “0,0,0,0”,
“thread-concurrency” : “0,0,0,0”,
“shaders” : “0,0,0,0”,
“gpu-engine” : “0-1000,0-1000,0-1000,0-1000”,
“gpu-fan” : “0-55,0-78,0-100,0-100”,
“gpu-memclock” : “1500,1500,1500,1500”,
“gpu-memdiff” : “0,0,0,0”,
“gpu-powertune” : “0,0,0,0”,
“gpu-vddc” : “0.000,0.000,0.000,0.000”,
“temp-overheat” : “85,85,85,85”,
“api-port” : “4028”,
“expiry” : “120”,
“expiry-lp” : “3600”,
“gpu-dyninterval” : “7”,
“gpu-platform” : “0”,
“gpu-threads” : “2”,
“log” : “5”,
“no-pool-disable” : true,
“queue” : “1”,
“scan-time” : “60”,
“neoscrypt” : true,
“skip-security-checks” : “0”,
“submit-stale” : true,
“temp-hysteresis” : “3”,
“shares” : “0”,
“kernel-path” : “/usr/local/bin”
}
0

greenuser

Ok this rig has run fine mining Ethereum for the last 4 days
Today i tried to mine ftc

i tryed these bat files commands

nsgminer --neoscrypt -I 13 -o http://p2pool.neoscrypt.de:19327 -O 6wTKzQovBDnMrhxtcR44KyLz3xWAPx15Ap

Then:

nsgminer --neoscrypt -I 12 -o http://p2pool.neoscrypt.de:19327 -O 6wTKzQovBDnMrhxtcR44KyLz3xWAPx15Ap

Then:

nsgminer --neoscrypt –-gpu-engine 1000 --gpu-memclock 1500 -I 13 -o http://p2pool.neoscrypt.de:19327 -O 6wTKzQovBDnMrhxtcR44KyLz3xWAPx15Ap

Then:

nsgminer --neoscrypt –-gpu-engine 1000 --gpu-memclock 1500 -I 13 -o http://p2pool.neoscrypt.de:19327 -O 6wTKzQovBDnMrhxtcR44KyLz3xWAPx15Ap

The command window opend on each time and i saw some writing but it went blue screen with white vertical stripes before i could read anything. Had to reboot to get rid of the stripes

So then i tried sgminer 5 with

sgminer -o http://p2pool.neoscrypt.de:19327 -O 6gTcFMDZeJRL4tgJbnHQDjXZe8Gm7kKaT8

and got the same blue screen with white vertical stripes, again needed to boot to get out.

Currently mining Ethereum again.

greenuser

Ok its working!
I reinstalled all GPU drivers and noted clock and core values in GPU-Z while mining Ethereum
Core 1000Mhz
Clock 1200Mhz

nsgminer --neoscrypt –-gpu-engine 1000 --gpu-memclock 1200 -I 13 -o http://p2pool.neoscrypt.de:19327 -O 6wTKzQovBDnMrhxtcR44KyLz3xWAPx15Ap

Wellenreiter

Are you using this address: 6gTcFMDZeJRL4tgJbnHQDjXZe8Gm7kKaT8?

After about 3 hours of mining our stale rate went up and is at about 84% at the moment.
Looks like you set your GPU parameters a bit to aggressive

wrapper

@greenuser Did you try nsgminer with no setting? I’d be interested to see what Engine settings NSGminer sets on it’s own. It poles the GPU for it what it thinks its settings are.

Also, I found one of my cards would not run stable over Engine 980 it might be worth trying 990. You can check by optimizing the engine speed to reduce the number of rejects.

Sometimes a lower engine can give the highest hash, as its a complex relation between memory and speed which is different for every hashing algorithm. Also, the highest hash is not necessary the most energy efficient.

greenuser

I get the same results with no settings, when i reduce values, hashpower goes down.

But now that i am hashing, why do i get 50%+ stale hashrate?
shutting down as i am using power but not making coin.

greenuser

@Wellenreiter said:

Are you using this address: 6gTcFMDZeJRL4tgJbnHQDjXZe8Gm7kKaT8?

After about 3 hours of mining our stale rate went up and is at about 84% at the moment.
Looks like you set your GPU parameters a bit to aggressive

@Wellenreiter Sorry i only just saw your post. Yes my address, I will reduce -I

Others here seem to have Stale hashrate 20%+ too. 6f1q2U6TuR8FijX96na9dHDko4HYAu3XPr

greenuser

@Wellenreiter

Current conf file

{
“pools” : [
{
“url” : “http://p2pool.neoscrypt.de:19327”,
“user” : “6gTcFMDZeJRL4tgJbnHQDjXZe8Gm7kKaT8”,
“pass” : “”,
“pool-priority” : “0”
}
]
,
“temp-cutoff” : “95,95,95,95”,
“temp-target” : “75,75,75,75”,
“intensity” : “11,11,11,11”,
“vectors” : “1,1,1,1”,
“worksize” : “256,256,256,256”,
“kernel” : “neoscrypt,neoscrypt,neoscrypt,neoscrypt”,
“lookup-gap” : “0,0,0,0”,
“thread-concurrency” : “0,0,0,0”,
“shaders” : “0,0,0,0”,
“gpu-engine” : “970,970,970,970”,
“gpu-fan” : “0-85,0-85,0-90,0-85”,
“gpu-memclock” : “1300,1300,1300,1300”,
“gpu-memdiff” : “0,0,0,0”,
“gpu-powertune” : “0,0,0,0”,
“gpu-vddc” : “0.000,0.000,0.000,0.000”,
“temp-overheat” : “85,85,85,85”,
“api-port” : “4028”,
“expiry” : “120”,
“expiry-lp” : “3600”,
“gpu-dyninterval” : “7”,
“gpu-platform” : “0”,
“gpu-threads” : “2”,
“log” : “5”,
“no-pool-disable” : true,
“queue” : “1”,
“scan-time” : “60”,
“neoscrypt” : true,
“skip-security-checks” : “0”,
“submit-stale” : true,
“temp-hysteresis” : “3”,
“shares” : “0”,
“kernel-path” : “/usr/local/bin”
}

So i turned up Mem clock to 1300 and turned down Core clock to 970.
Mem Clock shows correct values in GPU-Z but Core clock (gpu-engine) still reads 1000Mhz although set at 970Mhz, not sure why.
Ints set down at 11

I will watch for Stale Shares

wrapper

@greenuser said:

I get the same results with no settings, when i reduce values, hashpower goes down.

But now that i am hashing, why do i get 50%+ stale hashrate?
shutting down as i am using power but not making coin.

The fact that other miners are suffering, means it is with the server or communications to it. There is trouble with connections the further you are away, for instance.

Not having a good pool connection : it’s one good thing about running a local p2pool node, it acts as a buffer, collecting your shares then passing them round the network.

Also, it would be interesting to save a ping in a 5 min chron script and do a chart of connection variability from the output.

greenuser

So i need to find a closer pool to me here in Cornwall UK?

wrapper

@greenuser stales can be due to connections

I say you need to run a p2pool node like me, it’s pretty easy and low power. ie there are few in UK on about cornwall

How much are the cpus doing now on your miner?

greenuser

@wrapper Low on hard drive space, how big are the files?

Relatively small, it clears over a day as stratum is reached and block go by. I think it is python, I’ll see if I can see

greenuser

@wrapper, I got loads of CPU and Ram free

wrapper

You are running windows?

greenuser

@wrapper yep

wrapper

Looks like a windows build is possible. Or try Ubuntu Bash on windows and compile it in there.

It isn’t a simple download / release yet as far as I can see.

I’m sure Wellenreiter could do one, when he can get time, we’re a bit over run building and test a couple of new releases.

There are other members about that have helped with windows builds, who might see the thread and help.

https://github.com/wellenreiter01/p2pool-neoscrypt

The guide for virtual box is a out of date and needs some further fixes from the transfer to the ne NodeBB forum. So, I’ve done an emergency fix, but that guide needs replacing updating now…

https://forum.feathercoin.com/topic/729/guide-setup-p2pool-for-feathercoin-in-virtualbox

wrapper

I’d be intersted to see your ping, I’ll do it from here for comparison : ping neoscrypt.de

time=42.0 ms

greenuser

Pinging neoscrypt.de [217.160.170.182] with 32 bytes of data:
Reply from 217.160.170.182: bytes=32 time=27ms TTL=54
Reply from 217.160.170.182: bytes=32 time=26ms TTL=54
Reply from 217.160.170.182: bytes=32 time=26ms TTL=54
Reply from 217.160.170.182: bytes=32 time=26ms TTL=54

Ping statistics for 217.160.170.182:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 27ms, Average = 26ms

Cornwall to Germany

Wellenreiter

Well neoscrypt.de is not the p2pool host, probably not even in the same data center, as I can see from the IP Address returned.

The p2pool node is p2pool.neoscrypt.de (ip 46.4.0.101)

wrapper

@Wellenreiter That was not the point of the analysis, we measured the time from each computer to a common site/point in Germany!

The data still told us if the person being supported had a worse connection than me, by linking to the same site. I tried pinging to the actual site first but that seemed blocked.

— 46.4.0.101 ping statistics —
30 packets transmitted, 0 received, 100% packet loss, time 29230ms