|
greaterninja
|
 |
September 25, 2013, 07:35:06 AM
Last edit: September 26, 2013, 05:20:29 PM by greaterninja |
|
plz make "how to" step4step frob back up to chainminer upgrade manual for noobs like me)
ChainMiner for M Board Version 2.X boards
DO not use this guide for Version 1x m-boards.
It will fry your chips. This is only meant for Version 2 of the M-board.I apologize for grammar as I took 2 sleeping pills and I can barely feel my fingers. 1.login as pi or root 2. type "nano /run/shm/.stat.log" if you wish to see the performance of all the chips on your board before upgrading chain miner. (optional step) 3.(backup your chainminer version) (this creates a copy of the folder) a. sudo cp -a /opt/bitfury /usr/bitfury.backup b. cd /opt/bitfury/ c. pwd (make sure you are in /opt/bitfury) d. ls -al (or type dir) e. rm -rf chainminer (this removes everything in the chainminer folder and the chainminer folder itself) 4. make sure you are in the /opt/bitfury directory and not in /opt/bitfury/chainminer (it should be deleted anyway 5. type "git clone https://github.com/bfsb/chainminer.git" 6. it should now start getting the chainminer git. 7. now type "cd chainminer" you should now be in the chainminer directory 8. type "make" 9. Its going to take 5-10 minutes to create the chainminer...maybe longer. I got some warning but everything was fine after it all finished. it will go back to a bash prompt when done. 9a. Just wait...this is the longest part of doing this change.. 10. sudo reboot |
|
|
|
|
|
greaterninja
|
|
September 25, 2013, 08:05:44 AM |
|
Kit #2 ; 2 h-cards; 67.517 GH/s to 72 GH/s; stock fans; before upgrading chain miner
1 AIfDSo 55 2.419 2.294 169 8 0 0 217 $
2 AIfDSo 55 2.076 2.262 145 23 0 0 214 $
3 AIfDSo 55 2.176 2.325 152 5 0 0 220 $
4 AIfDSo 55 2.090 2.209 146 7 0 0 209 $
5 AIfDSo 55 2.319 2.251 162 3 0 0 213 $
6 AIfDSo 55 2.448 2.357 171 10 0 0 223 $
7 AIfDSo 55 2.133 2.209 149 3 0 0 209 $
8 AIfDSo 55 1.890 2.399 132 5 0 0 227 $
9 AIfDSo 55 2.233 2.378 156 7 0 0 225 $
10 AIfDSo 55 2.019 2.146 141 12 1 0 203 $
11 AIfDSo 55 2.147 2.230 150 8 0 0 211 $
12 AIfDSo 55 2.004 2.230 140 6 0 0 211 $
13 AIfDSo 55 1.775 2.061 124 3 0 0 195 $
14 AIfDSo 55 2.090 2.251 146 3 0 0 213 $
15 AIfDSo 55 2.577 2.283 180 3 0 0 216 $
16 AIfDSo 55 2.105 2.272 147 4 0 0 215 $
17 AIfDSo 55 2.205 2.505 154 14 0 0 237 $
18 AIfDSo 55 2.677 2.410 187 10 0 0 228 $
19 AIfDSo 55 2.634 2.463 184 15 0 0 233 $
20 AIfDSo 55 2.205 2.410 154 19 0 0 228 $
21 AIfDSo 55 2.276 2.389 159 4 0 0 226 $
22 AIfDSo 55 2.377 2.431 166 6 0 0 230 $
23 AIfDSo 55 1.675 1.924 117 9 0 0 182 $
24 AIfDSo 55 2.119 2.463 148 8 0 0 233 $
25 AIfDSo 55 2.062 2.357 144 4 0 0 223 $
26 AIfDSo 55 2.248 2.431 157 17 0 0 230 $
27 AIfDSo 55 2.133 2.442 149 11 0 0 231 $
28 AIfDSo 55 2.176 2.410 152 11 0 0 228 $
29 AIfDSo 55 1.947 2.294 136 20 0 0 217 $
30 AIfDSo 55 2.262 2.420 158 18 0 0 229 $
31 AIfDSo 55 2.448 2.357 171 6 0 0 223 $
32 AIfDSo 55 2.391 2.484 167 14 0 0 235 $
speed:1760 noncerate[GH/s]:70.337 (2.198/chip) hashrate[GH/s]:74.347 good:4913 $
0: 880 34.503 36.159 2410 110 1 0 16 0 $
C: 880 35.834 38.188 2503 186 0 0 16 0 $
Kit #2 after upgrading chain miner for version 2 of the M-Board (European version with PCI-E power connectors) It is gaining speed. Time to test overnight.
GNU nano 2.2.6 File: /run/shm/.stat.log
1 AIfDSo 56 2.019 2.114 141 0 0 0 200 [0:0] 275 8 8 8 9 9 9 9 9 9 9 9 9 9 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2 AIfDSo 54 2.076 2.093 145 5 0 0 198 [0:1] 281 10 9 10 10 10 10 9 9 9 8 8 9 9 8 9 8 0 1 0 0 0 0 0 0 0 1 1 0 0 1 0 1
3 AIfDSo 55 2.047 2.156 143 0 0 0 204 [0:2] 277 9 9 9 9 9 9 9 9 9 9 9 9 9 8 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
4 AIfDSo 56 2.405 2.029 168 0 0 0 192 [0:3] 297 10 11 11 11 11 11 11 11 11 10 10 10 10 10 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed up
5 AIfDSo 55 2.233 2.082 156 0 0 0 197 [0:4] 303 10 10 10 10 10 9 9 9 9 10 10 10 10 10 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed up
6 AIfDSo 56 1.818 2.188 127 0 0 0 207 [0:5] 309 7 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
7 AIfDSo 56 1.747 2.051 122 0 0 0 194 [0:6] 292 7 7 7 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
8 AIfDSo 56 2.205 2.230 154 0 0 0 211 [0:7] 283 10 10 10 10 10 10 10 10 9 9 9 9 9 9 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
9 AIfDSo 55 2.162 2.220 151 0 0 0 210 [0:8] 281 10 10 10 10 10 9 9 9 9 9 9 9 9 9 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
10 AIfDSo 53 2.391 1.998 167 2 0 0 189 [0:9] 289 11 9 9 10 10 10 10 10 11 11 11 11 11 11 11 11 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0
11 AIfDSo 54 2.133 2.061 149 0 0 0 195 [0:A] 287 10 10 10 10 10 9 9 9 9 9 9 9 9 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed up
12 AIfDSo 55 1.961 2.072 137 0 0 0 196 [0:B] 296 9 9 9 9 9 9 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
13 AIfDSo 54 1.847 1.913 129 1 0 0 181 [0:C] 333 8 9 9 7 8 8 8 8 8 8 8 8 8 8 8 8 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0
14 AIfDSo 55 2.162 2.093 151 0 0 0 198 [0:D] 299 10 10 9 9 9 9 9 9 9 9 9 10 10 10 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed up
15 AIfDSo 54 1.804 2.124 126 0 0 0 201 [0:E] 291 8 8 8 8 8 7 7 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
16 AIfDSo 54 2.205 2.082 154 2 0 0 197 [0:F] 296 10 8 8 9 9 10 10 10 10 10 10 10 10 10 10 10 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0
17 AIfDSo 55 2.391 2.325 167 0 0 0 220 [C:0] 249 11 11 11 10 10 10 10 10 10 10 10 10 11 11 11 11 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed up
18 AIfDSo 54 2.176 2.230 152 0 0 0 211 [C:1] 272 10 10 10 10 10 10 10 10 9 9 9 9 9 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
19 AIfDSo 55 2.105 2.294 147 0 0 0 217 [C:2] 257 9 9 9 9 9 9 9 10 10 10 9 9 9 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
20 AIfDSo 54 2.391 2.251 167 0 0 0 213 [C:3] 282 11 11 10 10 10 10 10 10 10 10 10 11 11 11 11 11 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed up
21 AIfDSo 55 2.806 2.220 196 0 0 0 210 [C:4] 253 13 13 13 13 12 12 12 12 12 12 12 12 12 12 12 12 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed up
22 AIfDSo 55 2.276 2.241 159 0 0 0 212 [C:5] 283 10 10 10 10 10 10 10 9 10 10 10 10 10 10 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed up
23 AIfDSo 55 1.847 1.786 129 0 0 0 169 [C:6] 365 8 8 8 8 8 8 8 8 9 8 8 8 8 8 8 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 speed up
24 AIfDSo 55 2.190 2.294 153 0 0 0 217 [C:7] 275 9 9 9 9 9 10 10 10 10 10 10 10 10 10 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
25 AIfDSo 54 2.233 2.177 156 3 0 0 206 [C:8] 328 10 10 9 10 10 10 10 9 9 10 10 10 10 9 10 10 0 0 1 1 0 0 0 0 0 0 0 0 0 1 0 0
26 AIfDSo 54 2.448 2.241 171 3 0 0 212 [C:9] 265 10 11 11 10 10 11 11 11 10 11 11 11 11 11 11 10 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1
27 AIfDSo 56 2.219 2.251 155 0 0 0 213 [C:A] 251 10 10 10 10 10 10 10 10 10 10 10 9 9 9 9 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
28 AIfDSo 55 2.233 2.251 156 0 0 0 213 [C:B] 273 10 10 10 10 10 10 10 10 10 10 10 9 9 9 9 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
29 AIfDSo 54 2.262 2.114 158 2 0 0 200 [C:C] 315 10 10 10 10 10 10 10 10 10 10 10 9 9 10 10 10 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0
30 AIfDSo 55 2.105 2.230 147 1 0 0 211 [C:D] 297 10 9 9 9 9 9 9 9 9 9 9 9 9 10 10 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
31 AIfDSo 55 2.248 2.198 157 2 0 0 208 [C:E] 252 9 10 10 10 10 10 10 10 9 9 10 10 10 10 10 10 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0
32 AIfDSo 57 2.434 2.304 170 0 0 0 218 [C:F] 230 10 10 10 11 11 11 11 11 11 11 11 11 11 10 10 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
speed:1756 noncerate[GH/s]:69.578 (2.174/chip) hashrate[GH/s]:68.914 good:4860 errors:21 spi-errors:0 miso-errors:0 jobs:375 (record[GH/s]:69.092)
0: 878 33.214 33.506 2320 10 0 0
C: 878 36.364 35.408 2540 11 0 0
|
|
|
|
|
|
darkfriend77 (OP)
|
|
September 25, 2013, 09:01:55 AM |
|
plz make "how to" step4step frob back up to chainminer upgrade manual for noobs like me)
ChainMiner for M Board Version 2.X boards
DO not use this guide for Version 1x m-boards.
It will fry your chips. This is only meant for Version 2 of the M-board..... That's how I did it yesterday ... worked like a charm ... if you do it the first time ... the make command might take some minutes be sure to let it run till it gets you back to the command line ... ... 8. How to update on the most actual chainminer version (gitpull)?... first .. if it ain't broke don't fix it ...do backup of your actual bitfury chainminer version... pi@bitfury ~ $ cp -a /opt/bitfury /usr/bitfury.backup
Then move to chainminer get latest version clean make ... restart ... pi@bitfury ~ $ cd /opt/bitfury/chainminer
pi@bitfury ~ $ git pull
pi@bitfury ~ $ make clean
pi@bitfury ~ $ make restart the miner ... and hope it will still hash ... :-) ... |
|
|
|
|
jlsminingcorp
|
|
September 25, 2013, 10:15:16 AM |
|
Is everybody compiling stuff on the pi, or has anybody had any success cross-compiling from a more powerful machine?
|
|
|
|
|
Isokivi
|
|
September 25, 2013, 11:57:13 AM |
|
I didnt get bitminter pool working with my bitfury, can someone help me??
what url must i insert in the web interface? "stratum+tcp://mint.bitminter.com" or "stratum.mint.bitminter.com" or something else?? the miner not start with these?!
mint.bitminter.com port 3333 |
Bitcoin trinkets now on my online store: btc trinkets.com <- Bitcoin Tiepins, cufflinks, lapel pins, keychains, card holders and challenge coins. |
|
|
mr_rulezzz
Member
 Offline
Activity: 61
Merit: 10
|
|
September 25, 2013, 02:15:44 PM |
|
plz make "how to" step4step frob back up to chainminer upgrade manual for noobs like me)
ChainMiner for M Board Version 2.X boards
DO not use this guide for Version 1x m-boards.
It will fry your chips. This is only meant for Version 2 of the M-board.I apologize for grammar as I took 2 sleeping pills and I can barely feel my fingers. 1.login as pi or root 2. type "nano /run/shm/.stat.log" if you wish to see the performance of all the chips on your board before upgrading chain miner. (optional step) 3.(backup your chainminer version) (this creates a copy of the folder) a. sudo cp -a /opt/bitfury /usr/bitfury.backup b. cd /opt/bitfury/ c. pwd (make sure you are in /opt/bitfury) d. ls -al (or type dir) e. rm -rf chainminer (this removes everything in the chainminer folder) 4. make sure you are in the /opt/bitfury directory and not in /opt/bitfury/chainminer (it should be deleted anyway 5. type "git clone https://github.com/bfsb/chainminer.git" 6. it should now start getting the chainminer git. 7. now type "cd chainminer" you should now be in the chainminer directory 8. type "make" 9. Its going to take 5-10 minutes to create the chainminer...maybe longer. I got some warning but everything was fine after it all finished. it will go back to a bash prompt when done. 9a. Just wait...this is the longest part of doing this change.. 10. sudo reboot very nice! thank you very much! ) |
|
|
|
|
|
-Redacted-
|
|
September 25, 2013, 02:21:33 PM |
|
Is everybody compiling stuff on the pi, or has anybody had any success cross-compiling from a more powerful machine?
Why would anyone want to bother to build a cross-compilation environment? That would require a great deal of effort to duplicate something that is already trivial to perform on the RPI... |
|
|
|
|
|
juhakall
|
|
September 25, 2013, 03:57:35 PM |
|
Is everybody compiling stuff on the pi, or has anybody had any success cross-compiling from a more powerful machine?
Why would anyone want to bother to build a cross-compilation environment? That would require a great deal of effort to duplicate something that is already trivial to perform on the RPI... To make repeated testing of new versions faster. Or to make the compile time on git-bisect bearable for finding bugs. I already have a cross-compiling environment for ARM, to compile cgminer for my other raspberry. Only reason I haven't added chainminer to it is because there's so far been only one update. |
|
|
|
|
|
gmannn
|
|
September 25, 2013, 04:39:22 PM |
|
plz make "how to" step4step frob back up to chainminer upgrade manual for noobs like me)
ChainMiner for M Board Version 2.X boards
DO not use this guide for Version 1x m-boards.
It will fry your chips. This is only meant for Version 2 of the M-board.I apologize for grammar as I took 2 sleeping pills and I can barely feel my fingers. 1.login as pi or root 2. type "nano /run/shm/.stat.log" if you wish to see the performance of all the chips on your board before upgrading chain miner. (optional step) 3.(backup your chainminer version) (this creates a copy of the folder) a. sudo cp -a /opt/bitfury /usr/bitfury.backup b. cd /opt/bitfury/ c. pwd (make sure you are in /opt/bitfury) d. ls -al (or type dir) e. rm -rf chainminer (this removes everything in the chainminer folder) 4. make sure you are in the /opt/bitfury directory and not in /opt/bitfury/chainminer (it should be deleted anyway 5. type "git clone https://github.com/bfsb/chainminer.git" 6. it should now start getting the chainminer git. 7. now type "cd chainminer" you should now be in the chainminer directory 8. type "make" 9. Its going to take 5-10 minutes to create the chainminer...maybe longer. I got some warning but everything was fine after it all finished. it will go back to a bash prompt when done. 9a. Just wait...this is the longest part of doing this change.. 10. sudo reboot very nice! thank you very much! ) Thank you! Went from 17 to 25 gh/s noncerate on a stock starter kit. MISO errors from 40s to 0. |
|
|
|
|
|
jlsminingcorp
|
|
September 25, 2013, 04:47:23 PM |
|
Is everybody compiling stuff on the pi, or has anybody had any success cross-compiling from a more powerful machine?
Why would anyone want to bother to build a cross-compilation environment? That would require a great deal of effort to duplicate something that is already trivial to perform on the RPI... To make repeated testing of new versions faster. Or to make the compile time on git-bisect bearable for finding bugs. I already have a cross-compiling environment for ARM, to compile cgminer for my other raspberry. Only reason I haven't added chainminer to it is because there's so far been only one update. Exactly, and some things are so slow to compile on a pi that it's just unbearable. -Redacted-, I haven't tried compiling chainminer on a pi yet, so I'm afraid that I'm rather ignorant of the reality. However, I got the sense from darkfriend77's post that it takes a while, which is when I think it starts to become worth thinking about putting the effort in to cross compile. |
|
|
|
|
greaterninja
|
|
September 25, 2013, 05:19:15 PM |
|
I think step #9 on the front page should be revised as it is not rookie friendly. Following those steps will result in errors on a Verision 2.X September 16th kit as it will not reach a git repository without the steps I laid out.
|
|
|
|
|
klondike_bar
Legendary
Offline
Activity: 2184
Merit: 1005
ASIC Wannabe
|
|
September 25, 2013, 06:08:38 PM
Last edit: September 25, 2013, 06:40:39 PM by klondike_bar |
|
just ran the above chainminer gitpull, up and hashing again now, at auto 54 and decent rates (still climbing)
Previously, i had about 34ghash average poolside using 2 workers at difficulty 16, autotuning, and pencil mod of 1.178k. The actual hardware hashrate was closer to 37.5 but 2-15% error rates on the chips. aftermarket cooling includes a fan on each face of the board, as well as multiple heatsinks (tiny one on each chip, and then 5 small heatsinks on the backside, 1 opposite each capacitor cluster)
EDIT #1 (5min): 1 worker, diff=16 (bitminter), autotuning is 54 across the board, hashrate: 35.86Ghash, noncerate: 35.03Ghash. This is looking really good with the chainminer update!
EDIT #2 (15min): hashrate: 36.5Gh, Noncerate: 35.0Gh, autotuning is moving most chips up to 55 now
EDIT #3 (30min): hashrate: 37.4Gh, Noncerate: 36.3Gh, autotuning is about 50/50 between 54 and 55 on all chips. Several chips running at 54 have no errors, and a chip at 55 is 7% errors (hopefully fixed by next autotune)
|
|
|
|
skrazy
Newbie
Offline
Activity: 55
Merit: 0
|
|
September 25, 2013, 06:47:21 PM |
|
Just took a look at the results from 12+ hours of logging yesterday after pulling chainminer v1.2. The board looks quite stable and error rates dropped significantly (~1% over the entire peroid). I'm looking at 36 GH/s sustained over long periods just dc fans and no heat sinks. I've manually clocked all chips at 54 and have not noted any benefit in using the auto feature in v1.2. Now someone push the board up to 40  https://i.imgur.com/YffkOcE.jpg |
|
|
|
|
|
darkfriend77 (OP)
|
|
September 25, 2013, 06:51:09 PM |
|
I had mine pushed to 37-38 with one dead chip ... heatsinks & fan ... but it was unstable so .. i went back to 32 ... :-) ...
|
|
|
|
klondike_bar
Legendary
Offline
Activity: 2184
Merit: 1005
ASIC Wannabe
|
|
September 25, 2013, 07:05:43 PM |
|
Just took a look at the results from 12+ hours of logging yesterday after pulling chainminer v1.2. The board looks quite stable and error rates dropped significantly (~1% over the entire peroid). I'm looking at 36 GH/s sustained over long periods just dc fans and no heat sinks. I've manually clocked all chips at 54 and have not noted any benefit in using the auto feature in v1.2. Now someone push the board up to 40 how are you making that sort of log? Im moving to manual tuning now, since most chips are stable at 54/55 with 1% errors and 36Ghash/37Ghash-nonce. if it runs well for the next few hours i will consider moving the resistance from 1.178 to 1.165 (before it gave me issues, but that was prior to chainminer update) |
|
|
|
skrazy
Newbie
Offline
Activity: 55
Merit: 0
|
|
September 25, 2013, 07:09:34 PM |
|
Just took a look at the results from 12+ hours of logging yesterday after pulling chainminer v1.2. The board looks quite stable and error rates dropped significantly (~1% over the entire peroid). I'm looking at 36 GH/s sustained over long periods just dc fans and no heat sinks. I've manually clocked all chips at 54 and have not noted any benefit in using the auto feature in v1.2. Now someone push the board up to 40 how are you making that sort of log? Im moving to manual tuning now, since most chips are stable at 54/55 with 1% errors and 36Ghash/37Ghash-nonce. if it runs well for the next few hours i will consider moving the resistance from 1.178 to 1.165 (before it gave me issues, but that was prior to chainminer update) Send Isokivi a tip for saving you the headache. |
|
|
|
|
tccd
Newbie
Offline
Activity: 51
Merit: 0
|
|
September 25, 2013, 07:19:19 PM |
|
Wow, the new version of chainminer is magic. With stock version one of my chips was always with zero nonce rate, no mater what speed I set, so I disabled it. With the new version all my chips are OK and autotune is working fine.
|
|
|
|
|
btc4life
Newbie
Offline
Activity: 18
Merit: 0
|
|
September 25, 2013, 09:14:31 PM |
|
If all of this good news holds true across the board I would expect to get close to 600GH/s out of my rig if I ever receive a v2 board.
|
|
|
|
|
|
greaterninja
|
|
September 25, 2013, 10:22:38 PM |
|
If all of this good news holds true across the board I would expect to get close to 600GH/s out of my rig if I ever receive a v2 board.
I have 2 extra version 2.3 M boards right now. I might be willing to trade. |
|
|
|
|
klondike_bar
Legendary
Offline
Activity: 2184
Merit: 1005
ASIC Wannabe
|
|
September 26, 2013, 12:55:20 AM
Last edit: September 26, 2013, 10:43:45 PM by klondike_bar |
|
Just took a look at the results from 12+ hours of logging yesterday after pulling chainminer v1.2. The board looks quite stable and error rates dropped significantly (~1% over the entire peroid). I'm looking at 36 GH/s sustained over long periods just dc fans and no heat sinks. I've manually clocked all chips at 54 and have not noted any benefit in using the auto feature in v1.2. Now someone push the board up to 40 how are you making that sort of log? Im moving to manual tuning now, since most chips are stable at 54/55 with 1% errors and 36Ghash/37Ghash-nonce. if it runs well for the next few hours i will consider moving the resistance from 1.178 to 1.165 (before it gave me issues, but that was prior to chainminer update) Send Isokivi a tip for saving you the headache. ooh, not being a linux guy that still looks like a headache! (massive respect for the method/result though!). I can see 1.5hr averages at bitminter that work okay, but a longer-spanning solution would be nice. maybe the next sd update ill try to get the logger set up. right now, im seeing a very steady 36.5 Ghash at the pool over the last 3 hours, with the bitfury page suggesting it might be closer to 37 EDIT: after about 16hrs, looks like 36.8Ghash is the average hashrate, with the last 3hrs above 37Ghash EDIT 2: some new tweaking, and it looks like i am averaging 37.7Ghash |
|
|
|
|
