Quote from: jonnybravo0311 on November 29, 2014, 04:54:58 PM

Quote from: mdude77 on November 29, 2014, 04:45:13 PM

Quote from: mdude77 on November 29, 2014, 04:39:32 PM

Quote from: MissouriMiner on November 29, 2014, 04:34:49 PM

Quote from: mdude77 on November 29, 2014, 04:04:55 PM

Anyone have a C1 pointing at p2pool? Mine seems to behave like my S2 pre-fix ... abysmal.

I was expecting the C1 to act like a S3, but it doesn't, it acts like an S2. Including the annoying "have to set queue to 0 every reboot" problem.

M

I have C1's using P2Pool. Mine are getting the full 1000GH/s, but they do require the same re-setting of queue after a reboot. I also set the pseudo share difficulty. It has been discussed that setting pseudo difficulty does not effect the overall performance, however setting pseudo difficulty will make cgminer and the UI show the expected hashrate. I use +1028 (If you use +1024, Best Share is not displayed. But with +1028, best Share works. I have no idea why.) Regarding setting the queue, S2/S4/C1 all have the same OS configuration.

Thanks, I was using 518. Are you using queue 0 or 1?

M

Doing as you said, setting queue to 0, gives me 965GH/s and 9% rejects. Completely unreasonable, just like my S2.

M

Why am I not surprised by this... Bitmain claims to want to support p2pool... but the only products they've ever released that worked with p2pool out of the gate are the S1 and S3. Even those products use forked versions of cgminer that until recently was based on 3.x. Furthermore, their binaries throw away stale shares, which can lead to potential block solutions being tossed.

I'm not able to get my S2 working reasonably either, even with the latest firmware. Sad

M