For the love of..., please pay attention:

As of today I'll be travelling overseas for the next 6 weeks. I plan to intermittently available online and coordinate releases if necessary but do not expect heavy development or support from myself during that time.

README FAQ

The Jalapeños are all wildly different in quality due to being all the earliest chips out. Just about any amount of hardware errors is pretty much normal. Some are <.1% while others are 10%.

While I'm at it, a word about the overclocking, based on what I've seen so far...

I'd suggest enabling --avalon-auto with a range of frequencies with --avalon-freq even if you're not overclocking, to allow cgminer to clock it down should you have an issue with heat.

For example, if you just want to run it at 300, add these to More Options:
--avalon-auto --avalon-freq 256-300

If you do want to overclock:
For batch 1 owners with the original PSU, I wouldn't suggest going over 325 or you'll risk your PSU failing:
--avalon-auto --avalon-freq 256-325

For batch 2 owners, there were a number of different PSUs, but even they can run into trouble so I'd suggest 345 as the upper limit to prevent instability:
--avalon-auto --avalon-freq 256-345

If you have upgraded your PSU to a good one >= 850W, then you can probably run --avalon-auto without a frequency range, and it may tune you up to around 365.

You're welcome, either the address in my forum signature or the one from the cgminer readme. Thanks for donating

One possibility. There are a few different ways that it restarts. One is an actual error in the code that makes it hang and stop submitting work, which should be fixed in this latest firmware. The other is multiple pool or network outages - and this is where the watchdog is trigger happy, as any period of 2+ minutes without work is enough for cgminer to stop being able to make work and the watchdog is not smart enough to detect what it is. Another is fpga screwups, but they are getting less likely with more fixes going into the cgminer direct USB code than they used to be with the old serial interface thereby bypassing one potential point of failure. An operating system error is also possible, and seems more common with the wifi enabled for reasons that aren't clear. Finally there's true hardware failure of one sort or another - overheat, inadequate power etc.

For Avalon users not watching the avalon asic users thread, I have posted updated Avalon firmware with all the overclocking options now in the git master code, and fixed a bug which would occasionally make the avalon fail to start.

http://ck.kolivas.org/apps/cgminer/avalon/20130703/

The new avalon options are:

--avalon-auto       Adjust avalon overclock frequency dynamically for best hashrate
--avalon-cutoff <arg> Set avalon overheat cut off temperature (default: 60)
--avalon-fan <arg> Set fanspeed percentage for avalon, single value or range (default: 20-100)
--avalon-freq <arg> Set frequency range for avalon-auto, single value or range
--avalon-options <arg> Set avalon options baud:miners:asic:timeout:freq
--avalon-temp <arg> Set avalon target temperature (default: 50)


The interface has been modified to allow any arbitrary speed so you can overclock it. Suggest no higher than 325 for batch 1 due to power limitations! Most settle at 350ish, but I set mine a little lower to avoid hardware issues.

New Avalon firmware:

http://ck.kolivas.org/apps/cgminer/avalon/20130703/

Fixed one longstanding bug where it would occasionally fail to start yay. \o/

Should also prevent one mode of failure while it's running.

Accepted/Rejected is changed in the current master version for precisely this reason. The web interface, on the other hand, may lag. It's the legacy of constantly shifting changing landscape of bitcoin mining.

That's unusual. It should work out to 42:300 now. Did you start with a fresh configuration or have you always done "keep settings" from the old firmware?

Sigh, also wrong.

The absolute values that count here are:
Accepted: 39126
Rejected: 789
HW: 406

Discarded is totally meaningless, I wish it wasn't in the display at all. It's a number from when getwork was the protocol in use and means nothing in the local work generation era.

All looks pretty good. My only concern is more about your Avalon itself. It's obviously hot where you are at the moment, as your fans have ramped up to almost the maximum. Due to them including 2 high pressure 38mm fans and 1 regular pressure 25mm fan, when the 38mm fans run at maximum speed, the air pressure is so high in the case that the 25mm fan is blowing but air is actually moving backwards through it. I don't know what the solution there is...

That's what you want then. The fact that you've submitted 1013 accepted shares in your screenshot and it counts as 39126 DiffA means you can tell you are running vardiff at about diff 40, which is also what you want.

Accepted depends on difficulty so it's relative. HW error count is an absolute. You must compare it to diff1 shares and remember that doesn't include the hw errors themselves.

Hardware error percentage is:
100 * HW / (diff1shares + HW)

I'm not sure which of slush's stratum code you're using, as stratum is the protocol, not the software, and cgminer implements its own stratum support. If it's slush's stratum proxy, then that doesn't do anything more than mining directly to bitcoind, and bitcoind can't keep up with an avalon mining with cgminer (it bombs beyond about 5GH). If you are using some kind of pool software from slush, then I'm not really familiar with it, but it could just be increasing your share target difficulty, which is what you want it to do.

I'm not really sure why this happens, but it appears to happen when code outside of cgminer kills it, so I suspect it's because it's not allowing it time to shut down properly and perhaps the API port is still bound to the old zombie process and you're not seeing the new one mining, or the new cgminer process is fighting the old one for access to the device.

Thanks, but not possible.

Looks fine to me? Your hardware error count is under 1.5% and your hashrate is 77GH.

What am I looking at? Looks okay to me.

Yes I am saying that.