dani
|
|
September 03, 2013, 08:27:57 PM |
|
ATTENTION!!! PLEASE PERFORM OPTICAL INSPECTION OF BOARDS YOU'VE RECEIVED!! THERE HAVE BEEN REPORTS OF SOLDERING ERRORS! I WILL SEND INSTRUCTIONS TO DO THIS SHORTLY!!
Any update on this? My device should arrive tomorrow, I don't want to risk anything here.. I can confirm that the boards really do not seem to like cooling. Im even partially blocking any natural air-movement to them and have achieved the best results seen thus far: speed": 1766, "noncerate": 50.967, "noncerateperchip":1.593, "hashrate":52.690, "good":3560, "errors":148, "spi-errors":2, "miso-errors":0, "jobs":375, "record":50.924
Which translates in to a constant average hashrate of just under 49,5 Gh/s.
[edit] In should propably in all fairness also say that achieving this also required turning the autotune off and hand tuning the chips for about two working days... the problem with 5 minute samples is that you do need a lot of them to make the right adjustments.
Did I miss the option to tune the h-boards? If I understood correct you are tuning on your own, non-h-board, correct? Otherwise would you share this information?
|
Hai
|
|
|
Isokivi
|
|
September 03, 2013, 08:36:59 PM |
|
Did I miss the option to tune the h-boards? If I understood correct you are tuning on your own, non-h-board, correct? Otherwise would you share this information? The basics are covered in http://punin.com/README_BFSB_v0.1.txtPlease note that everything does not apply for the kits your getting, you will have a preinstalled image on the sd card.But what does apply is how to read the logs and configs and how to modify the latter. To put it short, I disabled autotune after a 24h run for all chips and used the best run generated as a starting point. I tuned the chips based on about 50 5 minute runs, rising the speed of a chip if it had 0 errors and lowering it if it had 10% or more. Takes forever and is anal as hell.. most of you guys will love doing this .
|
Bitcoin trinkets now on my online store: btc trinkets.com <- Bitcoin Tiepins, cufflinks, lapel pins, keychains, card holders and challenge coins.
|
|
|
dani
|
|
September 03, 2013, 08:42:05 PM |
|
Did I miss the option to tune the h-boards? If I understood correct you are tuning on your own, non-h-board, correct? Otherwise would you share this information? The basics are covered in http://punin.com/README_BFSB_v0.1.txtPlease note that everything does not apply for the kits your getting, you will have a preinstalled image on the sd card.But what does apply is how to read the logs and configs and how to modify the latter. To put it short, I disabled autotune after a 24h run for all chips and used the best run generated as a starting point. I tuned the chips based on about 50 5 minute runs, rising the speed of a chip if it had 0 errors and lowering it if it had 10% or more. Takes forever and is anal as hell.. most of you guys will love doing this . Totally right! Thanks for the info, I missed it.
|
Hai
|
|
|
marto74
|
|
September 04, 2013, 04:00:48 AM |
|
What is the IP address of the web interface of the Rpi
|
|
|
|
tccd
Newbie
Offline
Activity: 51
Merit: 0
|
|
September 04, 2013, 04:32:46 AM |
|
What is the IP address of the web interface of the Rpi
You can see it in your router's web interface -> DHCP Clients List.
|
|
|
|
Isokivi
|
|
September 04, 2013, 06:57:55 AM Last edit: September 04, 2013, 07:23:34 AM by Isokivi |
|
What do you mean by "tuning autotune off and hand tuning..." ?
Can you describe what you did?
spiccioli
Well firstly I mean turning autotune off, that's a typo. I let the harware run for about 24h, grabbed the best.log and copied it as follows: cp /tmp/.best /opt/bitfury/best.cnf And started manually changing the speeds in /opt/bitfury/best.cnf based on a large number of results with 5 or more minute intervals, thus using a new .stat.log every time. The log only holds a five minute sample, so I collected a large number of notes on each chip using paper and pen. When a chip constantly had 0 errors I pushed it's speed higher and when a chip constantly showed over 10% errors I lovered it. I also re-enabled a bad chip that autotune had shut down, it's not working properly, but is producing 2/3 valid shares without interfering with the other chips, using a speed of 52. All other chips are now between 54 and 56 speed, 57 was a now go on every chip because of the hightened error rate. The final modifications (so far) were made based on 20 samples and I believe that this is optimal for now, I will propably try altering the operating temperature next, with a modifiable make-shif enclosure and see where that leads me. I am by far not sure the 10% rule is optimal, someone else will propably figure out the optimal number there. The results of my current settings measured from poolside over 6 shifts (9h) put my hashrate with only the 2-board starter kit at 50,68 Gh/s.
|
Bitcoin trinkets now on my online store: btc trinkets.com <- Bitcoin Tiepins, cufflinks, lapel pins, keychains, card holders and challenge coins.
|
|
|
spiccioli
Legendary
Offline
Activity: 1379
Merit: 1003
nec sine labore
|
|
September 04, 2013, 07:20:19 AM Last edit: September 04, 2013, 08:53:35 AM by spiccioli |
|
What do you mean by "tuning autotune off and hand tuning..." ?
Can you describe what you did?
spiccioli
Thanks Isokivi, I had removed my message since I saw you posted a link just after my question spiccioli
|
|
|
|
|
Humax
Full Member
Offline
Activity: 203
Merit: 100
The law of the universe!
|
|
September 04, 2013, 12:36:30 PM |
|
Got my Starter Kit also and hashing 41-42GH Delivery was few days overdue, I'm not complaining at all, and compensation for not hitting the target of 25 GH is 16 GH as a gift! Chrismas came early this year This is how business is done right! Others can try and learn from this!
|
Help me feed my hamster! Donate sunflower seeds!
|
|
|
AsicShill
Newbie
Offline
Activity: 42
Merit: 0
|
|
September 04, 2013, 12:53:47 PM |
|
Looks like you europeans lucked out this time. Metabank will most likely be shipping miners 10 to 20% below spec. USA bitfury starter kits will be single board 25GH delivery. Remains to be seen if they are 25GH or "25GH"
|
|
|
|
Foofighter
|
|
September 04, 2013, 12:58:07 PM |
|
|
ex official Canaan Distributor (Cryptouniverse)
|
|
|
dani
|
|
September 04, 2013, 03:21:00 PM Last edit: September 04, 2013, 03:34:32 PM by dani |
|
Got my bitfury today, I was super excited. Got it up and running, no problems. I ordered 2 starter kits and received 2 m-boards, 2 raspberry pis, 3(!) SD Cards (thank you, though it's a mistake I think) and 3 h-boards. Within the first 60 seconds I scored 71gh/s and was quite happy, but after changing the pool settings I was only seeing 50gh, it went up to 56 and kept falling down. Currently I rund at Noncerate: 48.533GH/s according to webinterface and 46.31gh/s according to 256s eligius pool. ( http://eligius.st/~wizkid057/newstats/userstats.php/14cbUKDLpZPJUMfr3DcKWZXmiaQRYpaZbd if anyone cares ). Average 3 hours is 46.84gh/s, which seems pretty low. here are some pics for you guys! I put the slowest h-board to C-1, but it didnt seem to improve. So right now I'm a sad panda, I feel like the only one who got less power than everyone else :/ Edit: Totally forgot to thank punin and bitfury and everyone else involved for this hardware, I hope I'll be able to tune the speed to where it should be Edit2: I saw the first time (when the slowest hboard was connected at B1) the slow hboard hashing at 12gh, now its down to 6. The other two are more or less hashing constantly, but the third is giving me a hard time :/
|
Hai
|
|
|
MXRider
|
|
September 04, 2013, 03:34:42 PM |
|
Dani:
SSH into your RasPi and check what /run/shm/.stat.log says. I'm pretty sure half of the chips (rows 33 to 48) are turned off. When a chip is turned off, it will look like this "xx AIfDSo 0". Change them to "xx AIfDSo 54" and save the file to /opt/bitfury/best.cnf.
Do a reboot and report back here. I would also like to know what /run/shm/.putstat.log says.
|
|
|
|
dani
|
|
September 04, 2013, 04:31:40 PM Last edit: September 04, 2013, 04:47:33 PM by dani |
|
Dani:
SSH into your RasPi and check what /run/shm/.stat.log says. I'm pretty sure half of the chips (rows 33 to 48) are turned off. When a chip is turned off, it will look like this "xx AIfDSo 0". Change them to "xx AIfDSo 54" and save the file to /opt/bitfury/best.cnf.
Do a reboot and report back here. I would also like to know what /run/shm/.putstat.log says.
+1 you were right, 12 from board 3 were turned off, 1 from board 3 as well. Turned them on and sudo reboot; 31gh/s now, slowly ramping up and going down.. keeps rising about less than 1gh per minute, not sure this will go up to 50+ again. Speed on every board dropped, the last board the msot (2gh). /run/shm/.putstat.log turned the chips on, still 54, but zero hasrate. Also the last two entries are "0000000" all over for the turned off chips. Hm.. your help is very much appreciated, thank you! putstat.log reports now (I put spaces here, because the messageboard somehow changes it to a link): 1 3305 172 171 [ 0] http:// 127.0.0.1:8332/ 2 3301 167 165 [1]http://127.0.0.1:8333/ 1 3260 142 141 [2]http://127.0.0.1:8334/ Edit: didnt get higher than 34gh. I turned the same chips off again, didnt change anything, 30gh now. Here is what putstat.log reports now, I mentioned a lot of errors now:
|
Hai
|
|
|
MXRider
|
|
September 04, 2013, 04:51:18 PM |
|
Looks like autotune is shutting down chips on the last board. You have to turn off the autotune for chips 33-48 (only the ones with "0")
Try changing every "AIfDSo 0" to "aIfDSo 54". Capital A means autotune is ON and normal a means it's OFF. Reboot and you should see at least 19 GH/s.
.putstat.log is showing if you have network problems. That could slow down the miner. In this case, you do not have anything wrong with you connection.
|
|
|
|
dani
|
|
September 04, 2013, 05:16:53 PM Last edit: September 04, 2013, 05:37:41 PM by dani |
|
Looks like autotune is shutting down chips on the last board. You have to turn off the autotune for chips 33-48 (only the ones with "0")
Try changing every "AIfDSo 0" to "aIfDSo 54". Capital A means autotune is ON and normal a means it's OFF. Reboot and you should see at least 19 GH/s.
.putstat.log is showing if you have network problems. That could slow down the miner. In this case, you do not have anything wrong with you connection.
Thanks. I set it to aIfDSo 54, like you said, but when I save it to /opt/bitfury/best.cnf and reboot, /run/shm/.stat.log still reports a 0 instead of 54, isn't that odd? Anyhow, I'm back to 50gh and still a lot of dead chips. Any other chance? Punin any idea? Edit: It's strange, I get 42gh now (didnt change anything, no fans working btw), admin panels says: 1: 24.138GH/s Bank 2 5: 12.312GH/s Bank 3 9: 6.514GH/s Edit2: 5 minutes passed, now: 1: 23.322GH/s Bank 2 5: 9.363GH/s Bank 3 9: 6.5GH/s 39gh now.. is it supposed to go up and down in speed all the time?
|
Hai
|
|
|
bbxx
|
|
September 04, 2013, 05:23:53 PM |
|
If i buy now, when it will be shipped?
|
|
|
|
pbigmoon
Newbie
Offline
Activity: 59
Merit: 0
|
|
September 04, 2013, 05:26:01 PM |
|
If i buy now, when it will be shipped?
Probably end of October
|
|
|
|
|
MXRider
|
|
September 04, 2013, 06:15:29 PM |
|
Looks like autotune is shutting down chips on the last board. You have to turn off the autotune for chips 33-48 (only the ones with "0")
Try changing every "AIfDSo 0" to "aIfDSo 54". Capital A means autotune is ON and normal a means it's OFF. Reboot and you should see at least 19 GH/s.
.putstat.log is showing if you have network problems. That could slow down the miner. In this case, you do not have anything wrong with you connection.
Thanks. I set it to aIfDSo 54, like you said, but when I save it to /opt/bitfury/best.cnf and reboot, /run/shm/.stat.log still reports a 0 instead of 54, isn't that odd? Anyhow, I'm back to 50gh and still a lot of dead chips. Any other chance? Punin any idea? Edit: It's strange, I get 42gh now (didnt change anything, no fans working btw), admin panels says: 1: 24.138GH/s Bank 2 5: 12.312GH/s Bank 3 9: 6.514GH/s Edit2: 5 minutes passed, now: 1: 23.322GH/s Bank 2 5: 9.363GH/s Bank 3 9: 6.5GH/s 39gh now.. is it supposed to go up and down in speed all the time? No, not that much. Could you post another picture (or a link to that picture) of the .stat.log -file. I'm pretty sure you have autotune on and several chips are turned off.
|
|
|
|
|