I compiled BFGminer on my Linux server... here is the output:
....
I'm not sure what SICK means yet, but you can see it's delivering 172Mhps.
Sick just means something's not right. Did you try my suggestion for bfgminer with these, in which you point the second instance of pool address (and/or port) to some device:port that is NOT running a stratum proxy?....
I'm not sure what SICK means yet, but you can see it's delivering 172Mhps.
My guess is that will fix your "SICK" finding and then it'll run long enough for you to find the actual hashrate.
Thank you, I had forgotten about that... I've now added it to my configuration.
Things are starting to look better now... I'm getting a lot more activity on the cube.
M_01-16: 060 010 070 050 050 040 000 070 060 030 101 040 111 050 101 141
M_17-32: 020 040 141 060 000 040 000 151 080 010 000 040 070 070 040 030
M_33-48: 020 101 030 080 101 030 010 070 010 030 010 080 070 030 060 040
M_49-64: 040 111 080 040 030 070 030 000 020 020 000 030 020 030 030 000
M_65-80: 030 141 070 040 020 020 010 030 020 040 070 000 060 111 000 000
M_81-96: 050 080 000 101 010 020 020 000 010 010 040 020 010 080 020 010
Jobs:0000000665 Accepted:0000000423 Rejected:0000000025 (3:1) F1 F2 F3
MHS:04279 Utility:058 Efficieny:063.60%
Started before: 0d,00h,07m,14s
Current pool: 10.242.130.200 (A)
Switch mode: Primary/Backup
Clock selected: Low
Long Poll: active, LP requests: 4
and LP are working... I think you're on to something
