Quote from: klondike_bar on November 01, 2013, 08:16:00 PM

Quote from: Jumpsu on November 01, 2013, 07:16:15 PM

Quote from: Keefe on November 01, 2013, 05:52:34 PM

A better test would be to power the card and measure voltage at the top of the Pulse inductor. If you get ~0.75v there (or whatever it's adjusted to), the power circuit (including that capacitor) is probably fine. I only say "probably" because I just fixed a board that was missing a cap on the back side. Before replacing that tiny back-side cap, the voltage at the Pulse top was correct, but the card wouldn't hash stably.

okay, i measured, it was 0.3V or 0V, what i can do next?

problem card,A1, not detected

31 aIfDSo 55 1.241 2.199 50 23 0 0 120 [8:E] 708 3 4 2 1 2 2 4 5 4 $
32 aIfDSo 55 1.639 2.236 66 37 0 0 122 [8:F] 693 2 3 4 7 2 4 6 4 3 $
33 aIfDSo 55 0.670 0.495 27 0 0 0 27 [C:0] 730 2 2 2 2 1 1 1 1 1 $
34 aIfDSo 55 1.763 2.401 71 28 0 0 131 [C:1] 687 2 2 5 5 3 3 4 6 4 $
35 aIfDSo 55 0.000 0.037 0 0 0 0 2 [C:2] 756 0 0 0 0 0 0 0 0 0 $
36 aIfDSo 55 0.000 0.000 0 0 0 0 0 [C:3] 756 0 0 0 0 0 0 0 0 0 $
37 aIfDSo 55 0.000 0.000 0 0 0 0 0 [C:4] 756 0 0 0 0 0 0 0 0 0 $
38 aIfDSo 55 0.794 1.741 32 23 0 0 95 [C:5] 724 2 2 1 3 2 1 1 2 3 $
39 aIfDSo 55 1.440 2.566 58 36 0 0 140 [C:6] 699 4 3 3 3 4 6 6 5 2 $
40 aIfDSo 55 1.514 2.419 61 38 0 0 132 [C:7] 697 3 5 5 4 3 4 5 1 5 $
41 aIfDSo 55 0.869 2.511 35 48 0 0 137 [C:8] 721 1 0 2 2 1 3 1 3 4 $
42 aifdso 55 0.000 0.000 0 0 0 0 0 [C:9] 756 0 0 0 0 0 0 0 0 0 $
43 aIfDSo 55 1.663 2.383 67 40 0 0 130 [C:A] 693 5 6 3 3 5 2 5 6 4 $
44 aIfDSo 55 1.738 2.456 70 34 0 0 134 [C:B] 689 5 3 4 3 3 4 5 3 7 $
45 aIfDSo 55 1.266 2.438 51 28 0 0 133 [C:C] 706 3 3 5 3 4 3 2 2 3 $
46 aIfDSo 55 1.763 2.364 71 16 0 0 129 [C:D] 687 5 4 4 4 5 5 5 4 3 $
47 aIfDSo 55 1.936 2.511 78 27 0 0 137 [C:E] 680 5 5 5 5 4 7 5 5 5 $
48 aIfDSo 55 1.589 2.364 64 20 0 0 129 [C:F] 693 4 5 4 5 5 4 4 4 2 $
49 aIfDSo 55 0.000 0.000 0 0 0 0 0 [D:0] 756 0 0 0 0 0 0 0 0 0 $
50 aIfDSo 55 0.000 0.000 0 0 0 0 0 [D:1] 756 0 0 0 0 0 0 0 0 0 $
51 aIfDSo 55 0.000 0.000 0 0 0 0 0 [D:2] 756 0 0 0 0 0 0 0 0 0 $
52 aifdso 55 0.000 0.000 0 0 0 0 0 [D:3] 756 0 0 0 0 0 0 0 0 0 $
...

speed:5092 noncerate[GH/s]:53.973 (0.574/chip) hashrate[GH/s]:85.449 good:2174 errors:1078 spi-errors:1 miso-error$
4: 832 19.787 29.564 797 361 1 4
8: 880 17.180 29.198 692 379 0 0
C: 880 17.006 26.687 685 338 0 0
D: 880 0.000 0.000 0 0 0 0
E: 864 0.000 0.000 0 0 0 0
F: 756 0.000 0.000 0 0 0 0

okay, lets start at the top:
1) you are forcing tuning to run at 55 when you use "aIfDSo 55". the fact you are seeing more than 10% errors means you should not have them higher than 53 or 54. change them to auto-tuning. (AIfDSo)
2) a few chips (such as 52) are set as "aifdso". this wont work in the bitfury system unless you were forcing custom timing clocks and other info to the chip (you aren't). change them to AIfDSo.
3) where are 1-30?
4) Your chips are producing way to many errors. half of their hash rate is actually errors. You need to cool your chips better. The chips currently at zero likely switched off because the autotuning was overwhelmed by the high error rate. you need to have good cooling fans, and likely add some heatsinks.
5) if you havent yet, update your chainminer following the method mentioned several times in this thread.

do the above and then check again. it should resolve 90% of your hashrate issues. as for the 0.3V you are measuring, try again after the changes. if its still <0.6V, check the values of the resistors R01F and R02F. in a board with capacitors these should be 1.0 and 1.25 k(ohm) respectively. In a board without capacitors they should be -?- and 1.7k(ohm) respectively (i dont know the R01F value for the board, but its likely not 1.0k like the first version)

if your resistors are not these values, thats the issue. if they are correct, then its onto the next step. probably the small TI chip found right beside them (it has about 12 or 14 pins) that is responsible for bringing 12v->0.7v

Wait... are you saying that for chips that don't work/generate too many errors, setting them as aifdso doesn't work?? if not, what additional information needs to be provided to actually turn them off?? I can see a bunch of zero's in that line, which that seems to indicate they are technically switched off, so I don't understand why you're saying that aifdso alone doesn't fix the problem.... Thx for clarifying...