mdude77, there's some discussion in the S2 hardware thread about the lower-than-expected hash rates. People are blaming a few things:

Under-powered PSU with which S2 ships

Crap soldering of chips to the boards

I've been debating between the S2 and the SP-10 Dawson as my next hardware purchase. The price difference is pretty significant - at this point with S2 coupons (or 112bit's group buy) I could almost get 2 of them for the price of a single Dawson - even if I were to jump on RoadStress' group buy of the Dawson. Unfortunately I don't know if I've got enough available circuits in my house to handle 2 more miners - and paying someone outlandish rates to host in a data center isn't going to happen, either. I might be calling in the electrician to see if I can get a new 240/30 circuit and install my own rack/cabinet at home.

Anyhow... that was way off topic, sorry about that

Can you give me the link you are referring to? As I said it only happens with p2pool. And I replaced the PSU.

M

I saw your other post as well. I missed the part where you stated this was solely a p2pool issue, and that Eligius reports at 990GH/s. I checked the graphs on your node, and the attached miners seem to have the proper mean hashing speed (assuming of course your S2s are on your node) .

What really strikes me as odd is the S2 itself reporting the lower-than-expected hash rate exclusively when you point it to p2pool. I wonder if the version of cgminer the S2 ships with might be the culprit? I know kano had released a new binary of cgminer for the S1. Maybe he's got one for the S2 as well?

Wish I could be of more help. In your other thread you mentioned there is one chain not reporting temps, but only a single X in the list, so I'm not sure that would be the problem. Again, I keep falling back to your statement that it works properly on Eligius, but not on p2pool. That really seems to rule out a hardware problem. Since you've already changed out the PSU with no effect and made sure the boards are properly seated, I'm out of other ideas.

EDIT: p2pool itself has been acting up recently. For example, there are a number of threads wondering why the getBlockTemplate latency is spiking across the board. I'm a victim of it as well. It's upwards of 1s now. Between 3am and 8am this morning the latency was normal, but before and after it sits at least 2.5 times higher than normal. I saw the same trend on the graphs on your node. Another thing I've noticed is that my local DOA percentage has climbed. Initially I was running about 1% or so... now I'm averaging about 4-6%. You can see the steady progression upwards on the monthly graphs on my node.

I only have one S2 at the moment. I saw a spike in the latency as well on my p2pool node. This low hashrate on p2pool isn't a recent phenomena, I've been playing with it for about 5 days now trying different things. Only recently did it occur to me it's limited to p2pool only.

I was minig at an public p2pool nod for a while and get paybents for every bloch founf - however, for yesterday's two I got no paymernt - how can I found out what went wrong (I still have my address at the activ users and predicted payment list.

EDIT: p2pool itself has been acting up recently. For example, there are a number of threads wondering why the getBlockTemplate latency is spiking across the board. I'm a victim of it as well. It's upwards of 1s now. Between 3am and 8am this morning the latency was normal, but before and after it sits at least 2.5 times higher than normal.

Bitcoind version 0.9 changed the default blocksize from 500kB to 750kB. That may explain it. You can test by telling Bitcoin to make 500000 byte blocks again:

EDIT: p2pool itself has been acting up recently. For example, there are a number of threads wondering why the getBlockTemplate latency is spiking across the board. I'm a victim of it as well. It's upwards of 1s now. Between 3am and 8am this morning the latency was normal, but before and after it sits at least 2.5 times higher than normal.

Bitcoind version 0.9 changed the default blocksize from 500kB to 750kB. That may explain it. You can test by telling Bitcoin to make 500000 byte blocks again:

The blockprioritysize (number of free transactions included) was lowered as well (I set it to ~1/3)

Hi phillipsjk,

I'm aware of the block size change in the 0.9.* clients; however, I'm not sure that would explain the latency spikes that are currently happening. I've had 0.9.1 installed and running since release and it is only within the past few days that the latency has gone haywire. My normal latency is ~0.4s, which by itself isn't that good since guys running the entire thing in a RAM drive get ~.02s. In the past 2 days, the latency has spent many hours of ~1s latency. It isn't only my node, either. Nothing has changed on my end in terms of hardware/software/load/network traffic/etc. Even if something had changed on my end, it wouldn't be reflected across multiple nodes on the network.

I'm aware of the block size change in the 0.9.* clients; however, I'm not sure that would explain the latency spikes that are currently happening. I've had 0.9.1 installed and running since release and it is only within the past few days that the latency has gone haywire. My normal latency is ~0.4s, which by itself isn't that good since guys running the entire thing in a RAM drive get ~.02s. In the past 2 days, the latency has spent many hours of ~1s latency. It isn't only my node, either. Nothing has changed on my end in terms of hardware/software/load/network traffic/etc. Even if something had changed on my end, it wouldn't be reflected across multiple nodes on the network.

I wish... I'm 100% SSD, have the same latency issue as the rest of us...

but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.

but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.

but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.

No still not working on my node, the pool 2 is now showing up in the Miner Status as Dead which is correct as it is my mates pool and it is down at the minute, but my node isn't even showing up. The only settings I changed is the IP the gateway and DNS ip's to point to my router under network/ WAN I haven't changed anything under the LAN tab that is just left on default which is protocol DHCP client

but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.

No still not working on my node, the pool 2 is now showing up in the Miner Status as Dead which is correct as it is my mates pool and it is down at the minute, but my node isn't even showing up. The only settings I changed is the IP the gateway and DNS ip's to point to my router under network/ WAN I haven't changed anything under the LAN tab that is just left on default which is protocol DHCP client

but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.

No still not working on my node, the pool 2 is now showing up in the Miner Status as Dead which is correct as it is my mates pool and it is down at the minute, but my node isn't even showing up. The only settings I changed is the IP the gateway and DNS ip's to point to my router under network/ WAN I haven't changed anything under the LAN tab that is just left on default which is protocol DHCP client

I get my node webpage. I have been mining with Antminer U1's for a few months now without a problem I can ping 192.168.1.20 from the network/diagnostics tab on the Ant S1 and it finds it

It won't connect to any p2pools I've tried a few and no connection, my mate had the same problem with his S1's in Houston Texas, will only connect to mining pools, so there must be a setting within the S1 that needs fixing

but when the S1 connects is goes straight to pool 3 why won't it connect to my node on the local network, under the mining status tab the first 2 pools aren't in the list only pool 3 as alive, is there a setting I have missed.

No still not working on my node, the pool 2 is now showing up in the Miner Status as Dead which is correct as it is my mates pool and it is down at the minute, but my node isn't even showing up. The only settings I changed is the IP the gateway and DNS ip's to point to my router under network/ WAN I haven't changed anything under the LAN tab that is just left on default which is protocol DHCP client