Note, the orange LED doesn't directly mean the watchdog is firing. All that means is that literally the chip isn't currently hashing, it's waiting for more work from the host.
If the Orange LED is lighting though, it does mean your board isn't hashing during that period (So at least a small percentage of the time, depending on how much the led is lit, it's idle, and not making money). This can simply mean that the job interval is incorrect, or the pool is not providing work fast enough (if the led is only lighting for short bits here and there) but if it's staying on for longer periods of time, like a minute plus, and does it frequently then it likely signifies a hardware (or at least a bitstream) problem.
There is a watchdog in the software typically that attempts to send fresh work down if it hasn't heard from the miner in too long a period. The other watchdog in the FPGA itself is purely for detecting if the DCM goes unstable, and restarts the DCM to acquire a new clock lock.
Topic: Bounty[PAID OUT] : a bitstream for better utilizing the Cairnsmore1 157-294.5btc - page 2. (Read 21992 times)
August 26, 2012, 09:59:12 AM
August 26, 2012, 04:37:51 AM
(MH/s) div 71.5 = (U/min) 
I believe the U factors in invalids too, am I right ? ..what about rejects ?Utility in cgminer is defined as (total accepted shares / total uptime in minutes), i.e. it is what the pool is paying you for. It considers HW errors, invalids and rejects and is therefore the best available measure for your effective hashing power in the long term.
In contrast to that, the MH/s value reported for Icarus / CM1 may be off if your board has problems. That is due to the lack of explicit reporting when the FPGA searched the whole nonce range without finding a share. If after the given or calculated timeout you do not hear from your CM1, you assume that it processed the range and add 2^32 (or more precisely: the number of hashes you assume should have been processed during this period) to the share counter. In fact, the FPGA might have entered a hang condition and just stopped before being restarted by the watchdog. Then your MH/s value looks better than it actually is.
If your board has no problems, in the long run MH/s = U * 71.58. If you find your board's values are too far off from this relation, watch your board and you should find it being restarted by the watchdog regularly (see the orange LEDs lit).
August 26, 2012, 04:02:22 AM
(MH/s) div 71.5 = (U/min)
I believe the U factors in invalids too, am I right ? ..what about rejects ? 
August 26, 2012, 03:51:18 AM
(MH/s) div 71.5 = (U/min)
August 26, 2012, 03:48:03 AM
what U value should I be expecting from the shortfin200 and 210 streams?
If my memory serves me correct 200 should be above 5.2 (right now I have a 52h run saying 5.44 and 5.54 on 200mhs) I dont have a pair running 210 atm. Currently Im running a mix of 220-200mhs bitstreams, with U:'s between 5.44 and 6.06. August 25, 2012, 10:09:56 PM
what U value should I be expecting from the shortfin200 and 210 streams?
August 24, 2012, 07:06:48 PM
I agree to let the funds to be paid out.
I have a stable and good speed bitstream working (hashvoodoo175) on my 2 boards.
They do not appear to like the faster ones, but with so many reporting good reports for the faster ones I can't blame the bitstream.
So it's achieved what I want and I do look forward to improvements.
I have a stable and good speed bitstream working (hashvoodoo175) on my 2 boards.
They do not appear to like the faster ones, but with so many reporting good reports for the faster ones I can't blame the bitstream.
So it's achieved what I want and I do look forward to improvements.
My boards are 430 series yet are unstable too. They often need resetting several times a day.
Can your hashvoodoo175 bitstreamed CM1s run for days or better without needed to be reset?
Yes it appears so. Usually it was something else on the board that gave out first with other bitstreams, but this one lasted so long (2 days+) that it proved their was a small fault with my usb hub. They don't use that now and it's been completely solid since.
August 24, 2012, 05:37:17 PM
I agree to let the funds to be paid out.
I have a stable and good speed bitstream working (hashvoodoo175) on my 2 boards.
They do not appear to like the faster ones, but with so many reporting good reports for the faster ones I can't blame the bitstream.
So it's achieved what I want and I do look forward to improvements.
I have a stable and good speed bitstream working (hashvoodoo175) on my 2 boards.
They do not appear to like the faster ones, but with so many reporting good reports for the faster ones I can't blame the bitstream.
So it's achieved what I want and I do look forward to improvements.
My boards are 430 series yet are unstable too. They often need resetting several times a day.
Can your hashvoodoo175 bitstreamed CM1s run for days or better without needed to be reset?
The prior release of the 175 (the 175 OC from the 16th) has so far been rock solid stable on all boards I'm aware of it being tested on. (on my boards the highest uptime I had without problems was like 4-5 days, but the only reason I interrupted that was for reflashing or development. Several others reported success reviving pre-50 boards which had major stability problems using this bitstream and now they mine fine).
If you're having stability problems please try out that bitstream and let me know how it goes.
My hope (once I have time to tackle it) is to update a new release to have this kind of stability again (the current release is far less stable).
August 24, 2012, 05:30:14 PM
I don't have a board yet, but the reported rates and stability in the 2 CM threads are good enough for me - well done and thanks in advance for when I get my board in September
August 24, 2012, 05:14:26 PM
I agree to let the funds to be paid out.
I have a stable and good speed bitstream working (hashvoodoo175) on my 2 boards.
They do not appear to like the faster ones, but with so many reporting good reports for the faster ones I can't blame the bitstream.
So it's achieved what I want and I do look forward to improvements.
I have a stable and good speed bitstream working (hashvoodoo175) on my 2 boards.
They do not appear to like the faster ones, but with so many reporting good reports for the faster ones I can't blame the bitstream.
So it's achieved what I want and I do look forward to improvements.
My boards are 430 series yet are unstable too. They often need resetting several times a day.
Can your hashvoodoo175 bitstreamed CM1s run for days or better without needed to be reset?
August 24, 2012, 04:27:38 PM
Thanks for your feedback. We are at almost 80% now.
Will contact the remaining folks and we should have a full acceptance tomorrow.
Will contact the remaining folks and we should have a full acceptance tomorrow.
August 24, 2012, 03:20:21 PM
I agree to release funds.
August 24, 2012, 03:10:35 PM
thought i had agreed, guess not. I'm down to give em the bounty. (don't quit workin on it though gents 
)
) August 24, 2012, 01:23:44 PM
I agree to let the funds to be paid out.
I have a stable and good speed bitstream working (hashvoodoo175) on my 2 boards.
They do not appear to like the faster ones, but with so many reporting good reports for the faster ones I can't blame the bitstream.
So it's achieved what I want and I do look forward to improvements.
I have a stable and good speed bitstream working (hashvoodoo175) on my 2 boards.
They do not appear to like the faster ones, but with so many reporting good reports for the faster ones I can't blame the bitstream.
So it's achieved what I want and I do look forward to improvements.
August 24, 2012, 12:11:16 PM
zefir,
I agree to release funds.
spiccioli
I agree to release funds.
spiccioli
August 24, 2012, 11:56:50 AM
Ok, updated the votes so far in the spreadsheet.
For those of you not using Google Docs, this is the current state:
Contributor BTC Payment accepted
-----------------------------------------
Arvicco 30 UNKNOWN
Cranky4u 2 YES
dietwice 1 UNKNOWN
Doff 2 UNKNOWN
Fefox 5 UNKNOWN
Hpman 1 UNKNOWN
Isokivi 3 YES
julz 1 UNKNOWN
Lethos 5 UNKNOWN
misternoodle 1 YES
roomservice 10 YES
salty 1 UNKNOWN
ShadesOfMarble 2 YES
Slipbye 10 YES
Slipbye 20 YES
Slipbye 10 YES
Slipbye 10 YES
spiccioli 10 UNKNOWN
spiccioli 10 UNKNOWN
steamboat 9 UNKNOWN
tf101 2 UNKNOWN
zefir 50 YES
-----------------------------------------
Total BTC: 195
Accepted for Payment: 118 BTC / 61%
Like guessed, we already have 60+% support to release the funds. Please consider dropping me an ACK/NACK either here in the tread, via PM, or in #cm1 to approve your support. As soon as spiccioli and Arvicco (who contributed a large amount but was silent thereafter) confirm, we are at 85+% and ready to transfer.
For those of you not using Google Docs, this is the current state:
Contributor BTC Payment accepted
-----------------------------------------
Arvicco 30 UNKNOWN
Cranky4u 2 YES
dietwice 1 UNKNOWN
Doff 2 UNKNOWN
Fefox 5 UNKNOWN
Hpman 1 UNKNOWN
Isokivi 3 YES
julz 1 UNKNOWN
Lethos 5 UNKNOWN
misternoodle 1 YES
roomservice 10 YES
salty 1 UNKNOWN
ShadesOfMarble 2 YES
Slipbye 10 YES
Slipbye 20 YES
Slipbye 10 YES
Slipbye 10 YES
spiccioli 10 UNKNOWN
spiccioli 10 UNKNOWN
steamboat 9 UNKNOWN
tf101 2 UNKNOWN
zefir 50 YES
-----------------------------------------
Total BTC: 195
Accepted for Payment: 118 BTC / 61%
Like guessed, we already have 60+% support to release the funds. Please consider dropping me an ACK/NACK either here in the tread, via PM, or in #cm1 to approve your support. As soon as spiccioli and Arvicco (who contributed a large amount but was silent thereafter) confirm, we are at 85+% and ready to transfer.
August 24, 2012, 08:19:19 AM
Im good to release also
August 24, 2012, 08:18:20 AM
I agree, let's release the bounty to the devs for their hard work.
August 24, 2012, 04:40:31 AM
As I said, I'm ok with paying out the bounty.
August 24, 2012, 04:13:05 AM
Mine might be unstable-ish...but I dont think it is the bitstream and I want to encourage work not stamp it out...
I vote for a release of the bounty....run free with the buffaloes oh wild bitcoins
I vote for a release of the bounty....run free with the buffaloes oh wild bitcoins
Jump to: