New Miner Needing Help with HD7870 settings on NSGminer?
-
So i need to find a closer pool to me here in Cornwall UK?
-
@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?
-
@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
-
@wrapper, I got loads of CPU and Ram free
-
You are running windows?
-
@wrapper yep
-
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
-
I’d be intersted to see your ping, I’ll do it from here for comparison : ping neoscrypt.de
time=42.0 ms
-
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=54Ping 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 = 26msCornwall to Germany
-
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)
-
@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 -
@wrapper
My rig failed-over to https://give-me-coins.com at just past midnight last night. I’m looking at it hashing now and have received 30ftc in 12 hours, is that good?
651 KH/s for 12 hours with 0% invalid shares.It should have failed back again when http://p2pool.neoscrypt.de:19327/static/ came good.
Maybe the software takes the better pool for my settings. p2pool.neoscrypt.de is still my prioraty pool. -
Your earning seemed OK for the time mining, you loose stratum changing pools though.
I had trouble with failing back (on one of my miners), it may be a bug / incompatibility to the particular driver.
… which is why I went to my own local p2pool, which is a buffer to connection issues. Local p2pool has been rock stable, no failovers since.
