Quote from: lightfoot on September 15, 2013, 02:56:03 AM

CGMiner won't talk to my Jally; apparently the problem is some sort of timing error, it works fine with my erupters. So I'm back on BFG, and blind as to the details of my JP. Oh well.

FF: Sorry you blew up your JP, can you post what kinds of temps you were running and error rates? Every time I tried to move above 7 the unit would generate more heat, a lot more errors (5-10%), and not a lot more hashing. It's back to stock speed 7.4gh or so 43c, 2.6% error rate, and 335.7mh/s, 1.6/.91% error rate on the two erupters.

So an overall hashing rate of 8gh/s. I can live with that although with the difficulty change I just dropped from .05btc/day to .03btc/day. Ah well.....

Temps were 47-50C, 4-5% error rate with 1.2.5 and __ASIC_FREQUENCY_ACTUAL_INDEX=7. Keep in mind that I was getting roughly 2% error rate with the default 1.0.0 firmware straight from BFL, though (my stock Jalapeno was also hashing pretty high, 5.8GH/s so wasn't too concerned about the slightly high HW error rate). This was before I replaced the fan, added heatsinks, flashed the firmware, or did any other mods.

Maybe I had some dud chips and the firmware flash/higher frequency just accelerated their failure?

Leaving it unplugged for a little bit can get it going again (still only initializes with one ASIC, processor 7). After running for a little while (20-30 min or so), though, HW errors start increasing a bunch and eventually it stops accepting shares. If I do a java API stats when this happens it shows the ASIC frequency as 0MHz.

Almost seems like it's overheating, but temps reported in cgminer seem fine (40-41C). Might try removing the case and pointing a box fan at it just to rule overheating out.