jddebug
|
|
December 01, 2013, 05:34:04 AM |
|
Hmmm.. Only averaging ~10 gh now. I stuck a fan next to it.... I'm not sure what else to do. what happens if you SSH to the system and type "nano /run/shm/.stat.log" and report back what you see. klondike_bar, If you (or anyone who understands what these logs mean) have time, please take a look at these. I've found my bitfurys are not performing like others I read about here and would like to get them working better. I've performed no mods. I just plugged them in and this is what I got. These are first batch US kits btw. Maybe I should do as you suggested to Trance but I'd like the feedback first. Thank you. If possible, shorten the lists to only the chips performing lower than 1.7GH, and it will be easier to spot the trend/problem. What batch is your hardware from? in the august/october stuff the hardware benefited from modding higher (not just speed but also getting low-performance chips to run correctly), but for the newer batch with higher voltage, issues will arise if you dont provide sufficient cooling (this means heatsinks AND airflow) I would suggest: buy a $10-15 multimeter and check the voltage on each card. Take the red positive signal from the top contact on the large cube-like inductor and the ground from the pci-e or screw terminal GND. You want a voltage around 0.77-0.82 if you have 'okay' cooling and 0.82-0.88 if you have relatively large heatsinks on each backside of the PCB, and lots of cool airflow In your case, the voltage on a lot of your cards seems low, almost like the august batch. check the voltage and if necessary, apply the pencil mod to increase it. If the voltage is high, then the issue is your cooling I'll clean up those logs and remove everything thats over 1.7GH. Sorry about that. I didn't know what would be good information and what would be useless. Yes, these are August batch.
|
|
|
|
jddebug
|
|
December 01, 2013, 05:56:50 AM |
|
I could use a legend telling what each column means. Is the hashrate 1.561 or 1.934? Does one of these tell what the voltage is?
2 AIfDSo 55 1.561 1.934 109 7 0 0 183 [0:1] 36 5 7 5 6 7 7 8 8 7 7 7 7 7 7 7 7 2 0 2 1 0 0 0 0 1 1 0 0 0 0 0 0
|
|
|
|
JTrain_51
Member
Offline
Activity: 84
Merit: 10
|
|
December 01, 2013, 05:59:03 AM |
|
Definitely very good advise and TLC on your miners. Totally agree great advice! Love your miners - hope to see more work done
|
|
|
|
Keefe
|
|
December 01, 2013, 08:10:54 AM Last edit: December 01, 2013, 08:49:54 AM by Keefe |
|
I could use a legend telling what each column means. Is the hashrate 1.561 or 1.934? Does one of these tell what the voltage is?
2 AIfDSo 55 1.561 1.934 109 7 0 0 183 [0:1] 36 5 7 5 6 7 7 8 8 7 7 7 7 7 7 7 7 2 0 2 1 0 0 0 0 1 1 0 0 0 0 0 0
I like to call the 1.934 number the work rate, though most call it the hashrate. It's based on how many work units were processed. It's a function of the voltage and speed setting (55 in this case), and is usually quite stable, unless the VRM is overloaded/overheating. The 1.561 number, commonly called the noncerate, is based on how many good nonces are found, and will vary randomly even under perfect conditions (i.e. no errors). Here's a legend for your line above: Chip#: 2 Flags: AIfDSo (A = autotune on, check the source code for the others) Speed: 55 Noncerate: 1.561 Hashrate: 1.934 Good nonces: 109 Nonce errors: 7 SPI errors: 0 MISO errors: 0 Work units: 183 Chip position: [0:1] Bad cores: 36 (how many of 756 have not yet found a good nonce) I don't know what the last two sets of numbers are. The boards don't have digital voltage or temp meters, unfortunately.
|
|
|
|
Keefe
|
|
December 01, 2013, 08:14:55 AM |
|
2) modify the miner.h file. to do this, SSH in and type: "cd /opt/bitfury/chainminer sudo pico miner.h" and then modify:
max_error : from 5 to 6 (increases tolerance to errors slightly) min_good : from 50 to 40 (increases tolerance to low-performance slightly) max_speed : from 57 to 55 def_speed : from 55 to 53 min_speed : 52 [these options help prevent the system from switching chips off if they are borderline working]
Don't forget to recompile chainminer after editing miner.h or nothing will change. Just running 'make' should do that.
|
|
|
|
Keefe
|
|
December 01, 2013, 08:43:03 AM |
|
I could use a legend telling what each column means. Is the hashrate 1.561 or 1.934? Does one of these tell what the voltage is?
2 AIfDSo 55 1.561 1.934 109 7 0 0 183 [0:1] 36 5 7 5 6 7 7 8 8 7 7 7 7 7 7 7 7 2 0 2 1 0 0 0 0 1 1 0 0 0 0 0 0
I like to call the 1.934 number the work rate, though most call it the hashrate. The work rate is based on how many work units were processed. It's a function of the voltage and speed setting (55 in this case), and is usually quite stable. The 1.561 number, commonly called the noncerate, is based on how many good nonces are found, and will vary randomly even under perfect conditions (i.e. no errors). Here's a legend for your line above: Chip#: 2 Flags: AIfDSo (A = autotune on, check the source code for the others) Speed: 55 Noncerate: 1.561 Hashrate: 1.934 Good nonces: 109 Nonce errors: 7 SPI errors: 0 MISO errors: 0 Work units: 183 Chip position: [0:1] Bad cores: 36 (how many of 756 have not yet found a good nonce) I don't know what the last two sets of numbers are. The boards don't have digital voltage or temp meters, unfortunately. In case you're curious about the math... After the first 5 minutes of chainminer running, the stats are updated every 5 minutes, so the numbers are based on the previous 5 minutes of work. Each core does 4194304 (2 22) hashes per work unit. 183 work units * 756 cores * 4194304 hashes / 300 seconds = 1.934 billion hashes per second. On average, 1 good nonce (diff=1) should be found per 4294967296 (2 32) hashes. Since 109 good nonces were found, it calcs the noncerate like this: 109 good nonces * 4294967296 average hashes per nonce / 300 seconds = 1.561 billion hashes per second. This was probably just an unlucky 5 minute interval and you'll see the noncerate higher than the hashrate at other times. The 7 nonce errors are nonces the chip reported as good but chainminer found to be actually bad. This happens because of bad bit flips during the hashing process in the chip and occurs much more often when overclocked too much. Less than 5% average nonce errors is just fine. In this case, we can expect at least 4.8% nonce errors anyway because apparently 36 of the 756 cores are malfunctioning, at least at this clock speed and voltage. The chip's hashing cores are arranged in a 21x36 grid, at least logically, so it is common to find a whole row or column bad. You can see that visually in /tmp/.core.log
|
|
|
|
Keefe
|
|
December 01, 2013, 08:48:19 AM |
|
3) modify the optimal settings to start the miner at a more managable speed. SSH and type: "nano /run/shm/.stat.log" change everything to AIfDSo 53 exit, and tell it to save as "opt/bitfury/best.cnf"
Don't forget the slash: /opt/bitfury/best.cnf
|
|
|
|
jddebug
|
|
December 01, 2013, 09:16:40 AM |
|
2) modify the miner.h file. to do this, SSH in and type: "cd /opt/bitfury/chainminer sudo pico miner.h" and then modify:
max_error : from 5 to 6 (increases tolerance to errors slightly) min_good : from 50 to 40 (increases tolerance to low-performance slightly) max_speed : from 57 to 55 def_speed : from 55 to 53 min_speed : 52 [these options help prevent the system from switching chips off if they are borderline working]
Don't forget to recompile chainminer after editing miner.h or nothing will change. Just running 'make' should do that. Do I need to be in a particular directory when I run "make"?
|
|
|
|
Keefe
|
|
December 01, 2013, 09:43:48 AM |
|
2) modify the miner.h file. to do this, SSH in and type: "cd /opt/bitfury/chainminer sudo pico miner.h" and then modify:
max_error : from 5 to 6 (increases tolerance to errors slightly) min_good : from 50 to 40 (increases tolerance to low-performance slightly) max_speed : from 57 to 55 def_speed : from 55 to 53 min_speed : 52 [these options help prevent the system from switching chips off if they are borderline working]
Don't forget to recompile chainminer after editing miner.h or nothing will change. Just running 'make' should do that. Do I need to be in a particular directory when I run "make"? Yes: /opt/bitfury/chainminer And you don't need to use sudo when working in that directory, as those files (miner.h, etc) are owned by user pi, not root.
|
|
|
|
john_es
Newbie
Offline
Activity: 12
Merit: 0
|
|
December 01, 2013, 06:20:29 PM |
|
OK, so I have this... which is great... 1.) Although the nrate was 60, btcguild shows only 40. Any idea for that? 18 AIfDSo 49 2.176 1.913 152 0 0 0 0 181 [1:1] 618 9 9 9 9 10 10 10 10 10 10 10 10 9 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 19 AIfDSo 49 1.761 1.871 123 0 0 0 0 177 [1:2] 639 7 8 8 8 8 8 8 8 8 8 8 8 7 7 7 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 20 AIfDSo 49 1.618 1.860 113 0 0 0 0 176 [1:3] 651 8 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 21 AIfDSo 49 1.904 1.860 133 0 0 0 0 176 [1:4] 632 9 9 9 9 8 8 8 8 8 8 8 8 8 8 8 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 22 AIfDSo 49 2.004 1.871 140 0 0 0 0 177 [1:5] 622 8 9 9 9 9 9 9 9 9 9 9 9 9 8 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 23 AIfDSo 49 1.861 1.829 130 0 0 0 0 173 [1:6] 631 8 8 8 8 8 8 8 8 8 8 9 9 8 8 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 24 AIfDSo 49 2.090 1.903 146 1 0 0 0 180 [1:7] 621 9 9 9 9 9 9 9 9 9 9 9 10 10 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 25 AIfDSo 49 1.761 1.945 123 0 0 0 0 184 [1:8] 640 7 7 8 8 8 8 8 8 8 8 8 8 8 7 7 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 26 AIfDSo 49 1.875 1.850 131 0 0 0 0 175 [1:9] 641 8 8 8 8 8 8 8 8 8 8 8 8 8 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 27 AIfDSo 49 1.833 1.892 128 0 0 0 0 179 [1:A] 636 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 28 AIfDSo 49 1.890 1.998 132 1 1 0 0 189 [1:B] 631 8 9 9 9 9 9 7 8 8 8 8 8 8 8 8 8 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 29 AIfDSo 49 1.833 1.955 128 0 0 0 0 185 [1:C] 639 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 30 AIfDSo 49 1.947 1.913 136 4 0 0 0 181 [1:D] 628 8 8 9 9 9 9 9 9 9 9 7 8 9 8 8 8 0 0 0 0 0 0 0 0 0 0 2 2 0 0 0 0 31 AIfDSo 49 1.689 1.776 118 1 0 0 0 168 [1:E] 646 8 8 8 8 8 7 7 7 7 7 7 7 7 6 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 32 AIfDSo 49 1.589 1.913 111 0 0 0 0 181 [1:F] 648 7 7 7 7 7 7 6 7 7 7 7 7 7 7 7 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed:1568 noncerate[GH/s]:59.485 (1.859/chip) hashrate[GH/s]:60.543 good:4155 errors:16 spi-err:3 miso-err:1 duplicates:0 jobs:314 cores:16% good:32 bad:0 off:0 (best[GH/s]:0.000) Sun Dec 1 17:19:50 2013 board-2 speed nrate hrate good errors spi-err miso-er duplic good bad off per chip good cores 0: 784 29.965 30.282 2093 9 1 1 0 16 0 0 (1.873/chip) 16% 1: 784 29.521 30.261 2062 7 2 0 0 16 0 0 (1.845/chip) 16%
Then it goes to this: 1 AIfDSo 49 0.888 1.025 62 1 0 1 0 97 [0:0] 583 3 4 4 4 4 4 4 4 4 4 4 4 4 4 4 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 2 AIfDSo 49 1.203 1.068 84 0 0 0 0 101 [0:1] 571 5 5 5 5 6 6 6 6 5 5 5 5 5 5 5 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 AIfDSo 49 1.160 1.057 81 0 0 0 0 100 [0:2] 574 5 5 5 5 6 5 5 5 5 5 5 5 5 5 5 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 AIfDSo 49 1.145 1.046 80 0 0 0 0 99 [0:3] 575 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 AIfDSo 49 0.959 1.078 67 0 0 0 0 102 [0:4] 585 5 5 4 4 4 4 4 4 4 4 4 4 4 4 4 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 AIfDSo 49 1.016 1.068 71 0 0 0 0 101 [0:5] 585 4 4 4 4 5 5 5 5 5 5 5 4 4 4 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 AIfDSo 49 0.787 1.036 55 0 0 0 0 98 [0:6] 600 3 3 3 3 3 3 3 3 4 4 4 4 4 4 4 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 AIfDSo 49 1.031 1.004 72 1 0 0 0 95 [0:7] 584 5 5 5 5 5 5 5 4 4 4 4 3 4 4 5 5 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 9 AIfDSo 49 0.916 1.110 64 0 0 0 0 105 [0:8] 576 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10 AIfDSo 49 0.959 1.036 67 0 0 0 0 98 [0:9] 580 5 5 5 4 4 4 4 4 4 4 4 4 4 4 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11 AIfDSo 49 1.160 1.046 81 1 0 0 0 99 [0:A] 572 5 5 6 6 5 5 5 5 5 5 5 5 5 5 4 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 12 AIfDSo 49 1.074 1.068 75 2 0 0 0 101 [0:B] 580 5 5 5 3 3 4 5 5 5 5 5 5 5 5 5 5 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 13 AIfDSo 49 1.045 1.068 73 0 0 0 0 101 [0:C] 575 4 4 4 4 4 4 5 5 5 5 5 5 5 5 5 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 14 AIfDSo 49 1.059 1.025 74 0 0 0 0 97 [0:D] 591 4 4 4 4 5 5 5 5 5 5 5 5 5 5 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 15 AIfDSo 49 1.217 1.046 85 0 1 0 0 99 [0:E] 561 6 6 6 6 5 5 5 5 5 5 5 5 5 5 5 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 16 AIfDSo 49 1.016 1.110 71 0 0 0 0 105 [0:F] 563 5 5 5 5 5 5 5 4 4 4 4 4 4 4 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 17 AIfDSo 49 1.918 1.903 134 0 0 0 0 180 [1:0] 539 9 9 9 8 8 8 8 8 8 8 8 8 8 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 18 AIfDSo 49 1.904 1.924 133 0 0 0 0 182 [1:1] 521 9 8 8 8 8 8 8 8 8 8 8 8 9 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 19 AIfDSo 49 1.833 1.881 128 0 0 0 0 178 [1:2] 544 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 20 AIfDSo 49 1.747 1.871 122 2 0 0 0 177 [1:3] 552 7 8 8 8 8 8 8 7 8 8 8 8 7 7 7 7 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 21 AIfDSo 49 1.704 1.871 119 2 0 0 0 177 [1:4] 544 7 7 7 7 7 7 8 8 8 8 8 8 8 7 7 7 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 22 AIfDSo 49 1.990 1.881 139 1 0 0 0 178 [1:5] 525 9 9 9 9 9 9 8 9 9 8 8 8 8 9 9 9 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 23 AIfDSo 49 1.618 1.839 113 0 0 0 0 174 [1:6] 541 7 7 7 7 7 7 7 7 7 7 7 7 8 7 7 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 24 AIfDSo 49 2.362 1.903 165 1 0 0 0 180 [1:7] 502 11 11 10 11 10 10 10 10 10 10 10 10 10 10 11 11 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 25 AIfDSo 49 1.918 1.945 134 2 0 0 0 184 [1:8] 534 9 9 9 8 8 8 8 8 8 8 8 8 8 9 9 9 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 26 AIfDSo 49 1.532 1.860 107 1 0 0 0 176 [1:9] 555 7 7 7 7 7 6 7 7 7 7 7 7 7 6 6 5 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 27 AIfDSo 49 1.833 1.903 128 1 0 0 0 180 [1:A] 531 8 9 8 8 8 8 8 8 8 8 8 8 8 7 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 28 AIfDSo 49 1.904 2.008 133 4 0 0 0 190 [1:B] 531 8 8 8 8 8 8 9 9 9 9 9 9 8 8 7 8 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 29 AIfDSo 49 2.004 1.945 140 1 0 2 1 184 [1:C] 526 9 9 9 8 8 8 8 9 9 9 9 9 9 9 9 9 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 30 AIfDSo 49 2.033 1.903 142 0 0 0 0 180 [1:D] 520 9 9 9 9 9 9 8 9 9 9 9 9 8 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 31 AIfDSo 49 1.947 1.776 136 2 0 0 0 168 [1:E] 544 8 8 8 8 8 9 9 9 9 8 8 8 9 9 9 9 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 32 AIfDSo 49 1.833 1.913 128 0 0 0 0 181 [1:F] 551 7 7 8 8 8 8 9 9 9 8 8 8 8 8 8 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed:1568 noncerate[GH/s]:46.715 (1.460/chip) hashrate[GH/s]:47.215 good:3263 errors:22 spi-err:1 miso-err:3 duplicates:1 jobs:300 cores:26% good:32 bad:0 off:0 (best[GH/s]:0.000) Sun Dec 1 17:24:50 2013 board-2 speed nrate hrate good errors spi-err miso-er duplic good bad off per chip good cores 0: 784 16.636 16.890 1162 5 1 1 0 16 0 0 (1.040/chip) 23% 1: 784 30.079 30.324 2101 17 0 2 1 16 0 0 (1.880/chip) 29%
Any idea how to toubleshoot this? I have fans pointed at the boards, they are cool. I also set the 49s to 53 in the best.cnf file, but it seems to keep putting them down to 49. then it goes down to this: board-2 speed nrate hrate good errors spi-err miso-er duplic good bad off per chip good cores 0: 848 6.483 7.065 397 492 0 3 57 16 0 0 (0.405/chip) 3% 1: 848 6.794 7.825 416 488 0 1 57 16 0 0 (0.425/chip) 3%
|
|
|
|
Doff
|
|
December 02, 2013, 12:20:05 AM |
|
Did you adjust your Pool difficulty to match the hashrate? If your are mining diff 1 shares it will slow down the miners like that.
|
|
|
|
zurg
|
|
December 02, 2013, 02:24:35 PM |
|
Is anyone mining Zetacoin? I need some help with pool (cant get CoinEx running) or heck even solo mining.
Thanks
|
|
|
|
tom99
|
|
December 02, 2013, 03:58:55 PM Last edit: December 02, 2013, 05:19:29 PM by tom99 |
|
Is anyone mining Zetacoin? I need some help with pool (cant get CoinEx running) or heck even solo mining.
Thanks
you can use bfgminer for it but I did not test yet. edit: solo ok with bfgminer.
|
|
|
|
zurg
|
|
December 02, 2013, 05:21:21 PM |
|
Is anyone mining Zetacoin? I need some help with pool (cant get CoinEx running) or heck even solo mining.
Thanks
you can use bfgminer for it but I did not test yet. edit: solo ok with bfgminer. How do you get bfgminer on it? Any guides? Thanks!
|
|
|
|
tom99
|
|
December 02, 2013, 05:53:58 PM |
|
Is anyone mining Zetacoin? I need some help with pool (cant get CoinEx running) or heck even solo mining.
Thanks
you can use bfgminer for it but I did not test yet. edit: solo ok with bfgminer. How do you get bfgminer on it? Any guides? Thanks! read here https://bitcointalk.org/index.php?topic=251966.3720I changed 4 to 1 for it to work old v1 mboard clock_gettime(CLOCK_PROCESS_CPUTIME_ID, &t1); for (i = 0; i < 1; i++) { slot_on = 1;
|
|
|
|
klondike_bar
Legendary
Offline
Activity: 2128
Merit: 1005
ASIC Wannabe
|
|
December 02, 2013, 11:37:03 PM |
|
OK, so I have this... which is great... 1.) Although the nrate was 60, btcguild shows only 40. Any idea for that? 18 AIfDSo 49 2.176 1.913 152 0 0 0 0 181 [1:1] 618 9 9 9 9 10 10 10 10 10 10 10 10 9 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 19 AIfDSo 49 1.761 1.871 123 0 0 0 0 177 [1:2] 639 7 8 8 8 8 8 8 8 8 8 8 8 7 7 7 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 20 AIfDSo 49 1.618 1.860 113 0 0 0 0 176 [1:3] 651 8 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 21 AIfDSo 49 1.904 1.860 133 0 0 0 0 176 [1:4] 632 9 9 9 9 8 8 8 8 8 8 8 8 8 8 8 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 22 AIfDSo 49 2.004 1.871 140 0 0 0 0 177 [1:5] 622 8 9 9 9 9 9 9 9 9 9 9 9 9 8 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 23 AIfDSo 49 1.861 1.829 130 0 0 0 0 173 [1:6] 631 8 8 8 8 8 8 8 8 8 8 9 9 8 8 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 24 AIfDSo 49 2.090 1.903 146 1 0 0 0 180 [1:7] 621 9 9 9 9 9 9 9 9 9 9 9 10 10 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 25 AIfDSo 49 1.761 1.945 123 0 0 0 0 184 [1:8] 640 7 7 8 8 8 8 8 8 8 8 8 8 8 7 7 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 26 AIfDSo 49 1.875 1.850 131 0 0 0 0 175 [1:9] 641 8 8 8 8 8 8 8 8 8 8 8 8 8 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 27 AIfDSo 49 1.833 1.892 128 0 0 0 0 179 [1:A] 636 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 28 AIfDSo 49 1.890 1.998 132 1 1 0 0 189 [1:B] 631 8 9 9 9 9 9 7 8 8 8 8 8 8 8 8 8 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 29 AIfDSo 49 1.833 1.955 128 0 0 0 0 185 [1:C] 639 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 30 AIfDSo 49 1.947 1.913 136 4 0 0 0 181 [1:D] 628 8 8 9 9 9 9 9 9 9 9 7 8 9 8 8 8 0 0 0 0 0 0 0 0 0 0 2 2 0 0 0 0 31 AIfDSo 49 1.689 1.776 118 1 0 0 0 168 [1:E] 646 8 8 8 8 8 7 7 7 7 7 7 7 7 6 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 32 AIfDSo 49 1.589 1.913 111 0 0 0 0 181 [1:F] 648 7 7 7 7 7 7 6 7 7 7 7 7 7 7 7 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed:1568 noncerate[GH/s]:59.485 (1.859/chip) hashrate[GH/s]:60.543 good:4155 errors:16 spi-err:3 miso-err:1 duplicates:0 jobs:314 cores:16% good:32 bad:0 off:0 (best[GH/s]:0.000) Sun Dec 1 17:19:50 2013 board-2 speed nrate hrate good errors spi-err miso-er duplic good bad off per chip good cores 0: 784 29.965 30.282 2093 9 1 1 0 16 0 0 (1.873/chip) 16% 1: 784 29.521 30.261 2062 7 2 0 0 16 0 0 (1.845/chip) 16%
Then it goes to this: 1 AIfDSo 49 0.888 1.025 62 1 0 1 0 97 [0:0] 583 3 4 4 4 4 4 4 4 4 4 4 4 4 4 4 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 2 AIfDSo 49 1.203 1.068 84 0 0 0 0 101 [0:1] 571 5 5 5 5 6 6 6 6 5 5 5 5 5 5 5 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 AIfDSo 49 1.160 1.057 81 0 0 0 0 100 [0:2] 574 5 5 5 5 6 5 5 5 5 5 5 5 5 5 5 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 AIfDSo 49 1.145 1.046 80 0 0 0 0 99 [0:3] 575 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 AIfDSo 49 0.959 1.078 67 0 0 0 0 102 [0:4] 585 5 5 4 4 4 4 4 4 4 4 4 4 4 4 4 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 AIfDSo 49 1.016 1.068 71 0 0 0 0 101 [0:5] 585 4 4 4 4 5 5 5 5 5 5 5 4 4 4 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 AIfDSo 49 0.787 1.036 55 0 0 0 0 98 [0:6] 600 3 3 3 3 3 3 3 3 4 4 4 4 4 4 4 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 AIfDSo 49 1.031 1.004 72 1 0 0 0 95 [0:7] 584 5 5 5 5 5 5 5 4 4 4 4 3 4 4 5 5 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 9 AIfDSo 49 0.916 1.110 64 0 0 0 0 105 [0:8] 576 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10 AIfDSo 49 0.959 1.036 67 0 0 0 0 98 [0:9] 580 5 5 5 4 4 4 4 4 4 4 4 4 4 4 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11 AIfDSo 49 1.160 1.046 81 1 0 0 0 99 [0:A] 572 5 5 6 6 5 5 5 5 5 5 5 5 5 5 4 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 12 AIfDSo 49 1.074 1.068 75 2 0 0 0 101 [0:B] 580 5 5 5 3 3 4 5 5 5 5 5 5 5 5 5 5 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 13 AIfDSo 49 1.045 1.068 73 0 0 0 0 101 [0:C] 575 4 4 4 4 4 4 5 5 5 5 5 5 5 5 5 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 14 AIfDSo 49 1.059 1.025 74 0 0 0 0 97 [0:D] 591 4 4 4 4 5 5 5 5 5 5 5 5 5 5 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 15 AIfDSo 49 1.217 1.046 85 0 1 0 0 99 [0:E] 561 6 6 6 6 5 5 5 5 5 5 5 5 5 5 5 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 16 AIfDSo 49 1.016 1.110 71 0 0 0 0 105 [0:F] 563 5 5 5 5 5 5 5 4 4 4 4 4 4 4 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 17 AIfDSo 49 1.918 1.903 134 0 0 0 0 180 [1:0] 539 9 9 9 8 8 8 8 8 8 8 8 8 8 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 18 AIfDSo 49 1.904 1.924 133 0 0 0 0 182 [1:1] 521 9 8 8 8 8 8 8 8 8 8 8 8 9 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 19 AIfDSo 49 1.833 1.881 128 0 0 0 0 178 [1:2] 544 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 20 AIfDSo 49 1.747 1.871 122 2 0 0 0 177 [1:3] 552 7 8 8 8 8 8 8 7 8 8 8 8 7 7 7 7 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 21 AIfDSo 49 1.704 1.871 119 2 0 0 0 177 [1:4] 544 7 7 7 7 7 7 8 8 8 8 8 8 8 7 7 7 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 22 AIfDSo 49 1.990 1.881 139 1 0 0 0 178 [1:5] 525 9 9 9 9 9 9 8 9 9 8 8 8 8 9 9 9 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 23 AIfDSo 49 1.618 1.839 113 0 0 0 0 174 [1:6] 541 7 7 7 7 7 7 7 7 7 7 7 7 8 7 7 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 24 AIfDSo 49 2.362 1.903 165 1 0 0 0 180 [1:7] 502 11 11 10 11 10 10 10 10 10 10 10 10 10 10 11 11 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 25 AIfDSo 49 1.918 1.945 134 2 0 0 0 184 [1:8] 534 9 9 9 8 8 8 8 8 8 8 8 8 8 9 9 9 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 26 AIfDSo 49 1.532 1.860 107 1 0 0 0 176 [1:9] 555 7 7 7 7 7 6 7 7 7 7 7 7 7 6 6 5 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 27 AIfDSo 49 1.833 1.903 128 1 0 0 0 180 [1:A] 531 8 9 8 8 8 8 8 8 8 8 8 8 8 7 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 28 AIfDSo 49 1.904 2.008 133 4 0 0 0 190 [1:B] 531 8 8 8 8 8 8 9 9 9 9 9 9 8 8 7 8 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 29 AIfDSo 49 2.004 1.945 140 1 0 2 1 184 [1:C] 526 9 9 9 8 8 8 8 9 9 9 9 9 9 9 9 9 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 30 AIfDSo 49 2.033 1.903 142 0 0 0 0 180 [1:D] 520 9 9 9 9 9 9 8 9 9 9 9 9 8 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 31 AIfDSo 49 1.947 1.776 136 2 0 0 0 168 [1:E] 544 8 8 8 8 8 9 9 9 9 8 8 8 9 9 9 9 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 32 AIfDSo 49 1.833 1.913 128 0 0 0 0 181 [1:F] 551 7 7 8 8 8 8 9 9 9 8 8 8 8 8 8 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed:1568 noncerate[GH/s]:46.715 (1.460/chip) hashrate[GH/s]:47.215 good:3263 errors:22 spi-err:1 miso-err:3 duplicates:1 jobs:300 cores:26% good:32 bad:0 off:0 (best[GH/s]:0.000) Sun Dec 1 17:24:50 2013 board-2 speed nrate hrate good errors spi-err miso-er duplic good bad off per chip good cores 0: 784 16.636 16.890 1162 5 1 1 0 16 0 0 (1.040/chip) 23% 1: 784 30.079 30.324 2101 17 0 2 1 16 0 0 (1.880/chip) 29%
Any idea how to toubleshoot this? I have fans pointed at the boards, they are cool. I also set the 49s to 53 in the best.cnf file, but it seems to keep putting them down to 49. then it goes down to this: board-2 speed nrate hrate good errors spi-err miso-er duplic good bad off per chip good cores 0: 848 6.483 7.065 397 492 0 3 57 16 0 0 (0.405/chip) 3% 1: 848 6.794 7.825 416 488 0 1 57 16 0 0 (0.425/chip) 3%
make sure you use the start-miner command or reboot after making changes to the best.cnf file. check your pool difficulty. if you are running 2 cards, your difficulty should be at least 64, but in some pools 128 will work a lot better.
|
|
|
|
Beans
|
|
December 09, 2013, 05:44:36 AM |
|
On my unit one of the last cards in a bank always seems to shut off after hour or so. Sometimes it comes back on for a while and sometimes the issue spreads to the 3rd card in the bank. I've rotated card positions and it doesn't seem to solve the problem. Anyone know what's causing this?
|
|
|
|
Keefe
|
|
December 09, 2013, 06:14:10 AM |
|
On my unit one of the last cards in a bank always seems to shut off after hour or so. Sometimes it comes back on for a while and sometimes the issue spreads to the 3rd card in the bank. I've rotated card positions and it doesn't seem to solve the problem. Anyone know what's causing this?
Have you secured your cards so they don't flutter in the airflow?
|
|
|
|
Cablez
Legendary
Offline
Activity: 1400
Merit: 1000
I owe my soul to the Bitcoin code...
|
|
December 09, 2013, 11:37:38 AM |
|
Regulator temp. not too high? That will cause hash cycling as well as it heats and cools off.
|
Tired of substandard power distribution in your ASIC setup??? Chris' Custom Cablez will get you sorted out right! No job too hard so PM me for a quote Check my products or ask a question here: https://bitcointalk.org/index.php?topic=74397.0
|
|
|
mwk13
Newbie
Offline
Activity: 13
Merit: 0
|
|
December 11, 2013, 07:01:26 AM |
|
I've applied copper heatsinks to the back of the new unmodded h-cards i have, directed fans (3x 120 mm) at them but the cards still get so hot they seem on the verge of burning up. What else can i try? Does anyone have instructions that show how to adjust the voltage using the trimpots? For now, I'd like to turn down the voltage to get ~25gh/s (currently at 33+ gh/s).
Thank you.
|
|
|
|
|