I flashed with 2013-08-10 yesterday, and my hashrate appears to have dropped. I was using 2013-07-03 earlier.
Yes there's a small regression in the auto code, I'm working on it now.
great:)
http://ck.kolivas.org/apps/cgminer/avalon/20130813-1/
Topic: Avalon ASIC users thread - page 101. (Read 438596 times)
great:)
http://ck.kolivas.org/apps/cgminer/avalon/20130813-1/
I flashed with 2013-08-10 yesterday, and my hashrate appears to have dropped. I was using 2013-07-03 earlier.
The --avalon-auto option already does precisely that: it uses a rolling average to adjust frequency rather than an all time average.
Yes and it would be nice if one could pull the current % value out of the cgminer process and display it on the stats page (which is what Ben is trying to accomplish)
The --avalon-auto option already does precisely that: it uses a rolling average to adjust frequency rather than an all time average.
I suspect that what SolarSilver would like is a %age of recent hardware errors (over the last 10000 diff1 shares for good precision maybe). SolarSilver, you might want to look at Zabbix and how to use "differential" items to compute this kind of probe.
Ah yes, finally somebody who can read minds ;-) Spot on and thank you for the explanation.
...however, what are you doing with that figure?
OK, at the risk of this being a trick question, I'm going to humiliate myself by saying "we display the value thus adding readability"?
The %age isn't really useful because it's an average over the whole cgminer process lifetime (recent changes won't be detected by looking at it on a long-lived cgminer process). If you restart cgminer on a regular basis, it becomes useful as any large variation is cause for concern and might warrant opening a case, inspecting and maybe resetting, reapplying thermal grease, repairing...
I suspect that what SolarSilver would like is a %age of recent hardware errors (over the last 10000 diff1 shares for good precision maybe). SolarSilver, you might want to look at Zabbix and how to use "differential" items to compute this kind of probe.
...however, what are you doing with that figure?
OK, at the risk of this being a trick question, I'm going to humiliate myself by saying "we display the value thus adding readability"?
overclock the lazy way
...however, what are you doing with that figure?
OK, at the risk of this being a trick question, I'm going to humiliate myself by saying "we display the value thus adding readability"?
...however, what are you doing with that figure?
OK, at the risk of this being a trick question, I'm going to humiliate myself by saying "we display the value thus adding readability"?
I don't have any intention of including the hw error % as a separate statistic. I also don't understand why you'd start deleting statistics from debug output like that, and I have to tell you your calculations are completely wrong.
You don't think adding the hw error% will cut down on all those questions from people what have difficulty interpreting the confusing numbers?
Not sure what you mean by deleting statistics from debug output and for the record, I am only referring to the thread by Ben Turas https://bitcointalksearch.org/topic/modification-to-show-hw-and-rejected-on-avalon-cgminer-status-page-254331
My math is even worse than his ;-)
It's probably
Code:
(100*hw/(diffaccepted+hw))
?
...however, what are you doing with that figure?
I don't have any intention of including the hw error % as a separate statistic. I also don't understand why you'd start deleting statistics from debug output like that, and I have to tell you your calculations are completely wrong.
You don't think adding the hw error% will cut down on all those questions from people what have difficulty interpreting the confusing numbers?
Not sure what you mean by deleting statistics from debug output and for the record, I am only referring to the thread by Ben Turas https://bitcointalksearch.org/topic/modification-to-show-hw-and-rejected-on-avalon-cgminer-status-page-254331
My math is even worse than his ;-)
It's probably
Code:
(100*hw/(diffaccepted+hw))
?
I don't have any intention of including the hw error % as a separate statistic. I also don't understand why you'd start deleting statistics from debug output like that, and I have to tell you your calculations are completely wrong.
Yes there's a small regression in the auto code, I'm working on it now.
great:)
are you considering to include showing %HW? :
https://bitcointalksearch.org/topic/modification-to-show-hw-and-rejected-on-avalon-cgminer-status-page-254331
its not a big problem to do it myself, but I would like it to be included
Here's updated firmware:
http://ck.kolivas.org/apps/cgminer/avalon/20130813-1/
Hey Con,
not sure what you meant to modify between 20130813 and 20130813-1 (small regression in the auto code?) but could you integrate this in a future release?
Code:
--- cgminer.lua-20130813-1 Tue Aug 13 11:03:30 2013
+++ cgminer.lua-benturas Tue Aug 13 11:01:01 2013
@@ -39,6 +39,8 @@
for line in summary do
local elapsed, mhsav, foundblocks, getworks, accepted, rejected, hw, utility, discarded, stale, getfailures, localwork, remotefailures, networkblocks, totalmh, wu, diffaccepted, diffrejected, diffstale, bestshare = line:match("Elapsed=(%d+),MHS av=([%d%.]+),Found Blocks=(%d+),Getworks=(%d+),Accepted=(%d+),Rejected=(%d+),Hardware Errors=(%d+),Utility=([%d%.]+),Discarded=(%d+),Stale=(%d+),Get Failures=(%d+),Local Work=(%d+),Remote Failures=(%d+),Network Blocks=(%d+),Total MH=([%d%.]+),Work Utility=([%d%.]+),Difficulty Accepted=([%d]+)%.%d+,Difficulty Rejected=([%d]+)%.%d+,Difficulty Stale=([%d]+)%.%d+,Best Share=(%d+)")
if elapsed then
+ local mhw = string.format("%d(%1.2f%%)",hw,(100*hw/(diffaccepted+diffrejected+hw)));
+ local mrj = string.format("%d(%1.2f%%)",rejected,(100*rejected/(accepted+rejected)));
local str
local days
local h
@@ -72,8 +74,8 @@
['foundblocks'] = foundblocks,
['getworks'] = getworks,
['accepted'] = accepted,
- ['rejected'] = rejected,
- ['hw'] = hw,
+ ['rejected'] = mrj,
+ ['hw'] = mhw,
['utility'] = utility,
['discarded'] = discarded,
['stale'] = stale,
Does your reply "Not really, no." mean you are NOT putting it in ever, or that you have not thought about doing it yet and are considering it? Just confused ;-)
Yes there's a small regression in the auto code, I'm working on it now.
great:)
are you considering to include showing %HW? :
https://bitcointalksearch.org/topic/modification-to-show-hw-and-rejected-on-avalon-cgminer-status-page-254331
its not a big problem to do it myself, but I would like it to be included
Here's updated firmware:
http://ck.kolivas.org/apps/cgminer/avalon/20130813-1/
Yes there's a small regression in the auto code, I'm working on it now.
great:)
are you considering to include showing %HW? :
https://bitcointalksearch.org/topic/modification-to-show-hw-and-rejected-on-avalon-cgminer-status-page-254331
its not a big problem to do it myself, but I would like it to be included
Yes there's a small regression in the auto code, I'm working on it now.
I gave it a test, but the actual firmware produces more HW errors on my B1 Avalon so its throtteling down to 330-340 MHz (starting @350).
So I'm back on 20130703 and again waving around 357 MHz
So I'm back on 20130703 and again waving around 357 MHz
I have a 3-module batch 2 Avalon, and I have just acquired a batch 3 module to add to it. I've connected it and, after changing the miner count to 32, it seems to be running fine. I have not yet started overclocking it.
Questions:
1) Has anyone else added a batch 3 module to a batch 2 machine? If so, have you encountered any issues?
2) Should I change any settings other than the miner count in order to best recognize / utilize the new 4th module?
3) Will the stock batch 2 750W power supply be enough to overclock all 4 modules?
4) The screw holes don't match up and the IDE cord I had wasn't long enough, so right now I have it running outside the case. Does this matter? If I do get it jammed in the case, it looks like it will be closer to the adjacent module than the other modules are to each other; is this worth worrying about, heat-wise? I have an air conditioner blowing right on the Avalon.
Thanks in advance for any advice / ideas!
Questions:
1) Has anyone else added a batch 3 module to a batch 2 machine? If so, have you encountered any issues?
2) Should I change any settings other than the miner count in order to best recognize / utilize the new 4th module?
3) Will the stock batch 2 750W power supply be enough to overclock all 4 modules?
4) The screw holes don't match up and the IDE cord I had wasn't long enough, so right now I have it running outside the case. Does this matter? If I do get it jammed in the case, it looks like it will be closer to the adjacent module than the other modules are to each other; is this worth worrying about, heat-wise? I have an air conditioner blowing right on the Avalon.
Thanks in advance for any advice / ideas!
I've uploaded new firmware 20130813 with the latest version of cgminer 3.3.3.
http://ck.kolivas.org/apps/cgminer/avalon/20130813/
This release contained a concerted effort to decrease CPU usage for stratum mining, and makes a massive difference when mining on p2pool.
A reminder that my firmware does not contain code to detect batch3 devices so you'll have to manually enter the higher target and overheat temperatures into your configuration.
http://ck.kolivas.org/apps/cgminer/avalon/20130813/
This release contained a concerted effort to decrease CPU usage for stratum mining, and makes a massive difference when mining on p2pool.
A reminder that my firmware does not contain code to detect batch3 devices so you'll have to manually enter the higher target and overheat temperatures into your configuration.
One of my batch 3 avalons is performing very poorly due to a high HW errors. Unplugging all by one module, each module individually has between a 25 and 75% HW error rate at either 256 or 300Mhz.
This degraded performance starting after about 6 hours of mining at 300Mhz.
Is there anything I should try before trying to make a warranty claim?
I was calculating the hardware error rate wrong. It should be HW/LocalWork, which brings the error rates i'm seeing to a much more reasonable 1%.This degraded performance starting after about 6 hours of mining at 300Mhz.
Is there anything I should try before trying to make a warranty claim?
Regardless, 3 out of 4 of my batch 3 units end up with <10Gh/s after 3-12hrs of mining, some more frequently than others.
Could this behavior be due to the new temperature throttling feature? I have the default temperature limits of 70C target and 90C cutoff, but I don't see the temps going over 70C.
I'm having this same issue.
EDIT: so is the solution is to disable wifi or to implement the load monitor with auto-restart? Is this issue resolved?
For me, disabling/removing wifi/wlan wasn't enough.
If you already removed wifi and it's still a problem, look at your load avg, if it's spiking, then you probably need the auto-restart I posted at https://bitcointalk.org/index.phptopic=140539.msg2898478#msg2898478
If the load avg is low (under 1.0) then you should check all the connectors inside your avalon. I did have one of the wide ribbon cables wiggle loose (I probably bumped it installing the psu) and the result was about 20%+ lower peak hashes and odd hangups.
Jump to: