Yeah, the increased hashrate on multipool.us with Kano's is coming at a big price for me ... 59.85% rejects on Nicehash vs 3.2% at multipool (I flip between both based on the price at Nicehash) ...
[2014-07-27 21:47:48] Rejected 3235311f Diff 1.3K/512 AS2 0 pool 0 (Invalid ntime rolling.)
[2014-07-27 21:47:50] Accepted 0963b632 Diff 6.98K/512 AS2 0 pool 0
[2014-07-27 21:47:52] Accepted 0eaf3303 Diff 4.46K/512 AS2 0 pool 0
[2014-07-27 21:47:53] Accepted 2f8a9177 Diff 1.38K/512 AS2 0 pool 0
[2014-07-27 21:47:55] Rejected 1cc9bed3 Diff 2.28K/512 AS2 0 pool 0 (Invalid ntime rolling.)
[2014-07-27 21:47:56] Accepted 7f3e1e32 Diff 515/512 AS2 0 pool 0
[2014-07-27 21:47:58] Rejected 59d3794f Diff 730/512 AS2 0 pool 0 (Invalid ntime rolling.)
Looking at my graphs on Nicehash, this was not happening with the old firmware -
The red part is the rejected hashrate ...
So it comes down to -
~5% better hashrate on multipool but losing out on high priced periods on Nicehash with Kano's firmware, or, back to the status quo with an acceptable hashrate on both with the stock firmware ...
Bitmain support pointed me to the latest
S3 firmware (yes,
S3 firmware) to resolve the beeping issues ... perhaps I'll give that a go ...
Update: Just got home and my room is extremely hot, and the AC has been on all weekend, and it's maybe 18 degrees outside ... the room did not get this hot before ... I can't say 100% for sure, but I think the Kano build is also making the box run a LOT hotter, because nothing else in this room has changed in the last week ...
Update 2: Can't flash S3 firmware onto the S2, it's a .bin file and the S2 is looking for a .tar file