I've got one board that hashes at full speed, but puts out about 75% hardware errors. I tried another board with the same power/usb cable and it works just fine. I've got three boards up and running on three different computers at the moment. They all seem to be averaging about 21.8 gigahashes at the recommended start settings.
Chad
What are your "starter" settings?
My current settings are --drillbit-options int:53:2:850 This produces slightly higher results than 'stock' (int:40:1:850).
had some issues with 950, but will continue exploring
Trying --drillbit-options int:52:2:950 I am getting
'timing out unresponsive AsicX', the Drillbit 8 board doesn't start. went back to int:53:2:850 and all is fine.
Cheers
I am seeing the exact same behavior with 1 dillbit 8 board and a raspberry pi, 52:2:850 works fine but [anything]:2:950 causes the ASICs to timeout and then the board becomes unresponsive.
With 52:2:850 there are no HW errors, but the hashrate is ~18Gh/s. Could this be a heating issue? If there was a heating issue I'd assume the HW error count would go up, but maybe there is some hidden throttling happening?
I'm going to leave it running overnight to see where the speed averages out to by the morning.
After more attempts, I managed to 'convince' the Drillbit 8 Board to run at --drillbit-options int:52:2:950
Had the 'timing out unresponsive Asic X' messages, and the board did not hash, so removed the USB cable to the board (while still powered and cgminer running), re-plugged the USB cable and now it got detected 'correctly' and is hashing nicely. I did not touch it since. I now have 2 fans blowing at it from both sides, the heatsink gets warm but not overly hot (can still be touched). Also installed a small heatsink on the 3 MosFets (as I wasn't given the 3 little ones when I got the board). The average hash rate is about 22.5 GH/sec, R:485 HW: 58 WU:315 after about 3.5 hours.

(the image is from an earlier time, but it has been going steady since)
Cheers