Thank you guys for testing. Seems like these instructions are working well. Those limits need some fine tuning so you can try these limits too: | Noncerate | | Speed | | <0.3 | | OFF | | 0.3-0.6 | | 52-53 | | 0.6-0.9 | | 53-54 | | >0.9 | | 55 |
|
|
|
|
MXRider,
What kind of gains have you seen using the steps you have mentioned above?
Gains depend on how well you have already tuned your unit. This is just a general guideline to manually tune your unit without wasting precious time. I've got over 370 GH/s from every Full kit I've tried this with. So if yours is hashing slower than that, you might want to give this a try  |
|
|
|
Anyone here with a Full kit hashing under 370 GH/s? Have you tweaked your unit manually? Let me try (SSH) or try these instrucions: 0) Do not use fans or any other active cooling 1) Set the clock speed to 55 for every chip (xx aIfDSo 55) 2) Let it hash for 10-15 minutes 3) sudo nano /run/shm/.stat.log 4) Turn off (xx aifdso 0) all the chips that are hashing slower than 0.3 GH/s 5) Lower the clock speed to 52 for every chip that is hashing 0.3-0.7 GH/s 6) Lower the clock speed to 54 for every chip that is hashing 0.7 - 1.1 GH/s 7) Save it to /opt/bitfury/best.cnf  sudo reboot I've tried this with three Full kits and several Starter kits and it seems to VERY good way to gain some hashrate easily. |
|
|
|
Since they are now providing "2 units of 200 Gh/s minimum" to make up for the fact they cannot provide a single unit of 400 Gh/s, it is an m-board with one Raspberry Pi and one or more hashing cards inserted. That makes a starter kit a unit with 25 Gh/s in it. What, you trying to use semantics to weasel out of a bet or something?
August orders were built from "bad" chips and that's why some of the H-cards have difficulties hitting 25 GH/s. Full kits is around 370 GH/s depending on the quality of your H-cards. They are not offering "2 units of 200 GH/s minimum". Full kit = one unit = M-board + 16 H-cards + RPi. October H-cards have better chips and they will achieve 25 GH/s without any problems. There is actually a new revision coming but let's wait punin 's comments on that one. |
|
|
|
|
Is there anyone from South Africa who is interested in earning some bitcoins or a free Bitfury miner? There is a guy named Neill Roelofse (also known as Clipse) who stole hundreds of bitcoins from me and several other miners in summer 2012. He lives in Cape Town.
Send me a PM if you can help me. I don't want my bitcoins back any more, I want revenge.
|
|
|
|
I had a similar issue ... somehow if I use load balanced mining .... with 40-42GH on 3 pools im getting 13GH at BTCGuild ... 13GH .... at eligius ... and 12 GH at Bitminter ...
if I change to mine 100% on BTCGuild it shows me 20-30 GH only .... i tryed with 16,32 & 64 diff
What shows? BTCGuild or the miner's web GUI? Check /run/shm/.putstat.log file. First number on each row is the amount of queued work. It should be zero. I had problems with BTCGuild. EMC works perfectly. |
|
|
|
Are you sure? I'd say from my limited testing that stopping/starting the miner is enough for it to load a new /opt/bitfury/best.cnf
spiccioli
I can confirm this, with fairly extensive testing. Yep, seems to be working. My poor Pi, it has been rebooted several times for no reason  |
|
|
|
My Kit has best performance after few minutes from start, before autotune starts messing with chip settings. After that everything falls down. Will it be ok to copy /run/shm/.stat.log to /opt/bitfury/best.cnf ? Or those files have different structure?
Also earlier when I have tried to modify settings I have fallen into problem. I have problem with using best.cnf for starting the miner. I made a copy of .best.log to best.cnf in /opt/bitfury directory, after that I have switched autotune off on few chips in .cnf file and saved the changes.
Then I have started the miner with console output in screen. After several minutes of mining if i open .stat.log all chips I have set to not use autotune, are set to autotune on, and have different speeds then those in /opt/bitfury/best.cnf file. Also there is no copy of best.cnf in /run/shm directory after miner starts. Am I suppose to copy best.cnf into /run/shm manually before starting the miner?
.stat.log and best.cnf have the structure. Keep in mind that .stat.log is changing. If I were you, I would copy the .best.log. Restarting the miner does not work. You need to reboot the Pi (sudo reboot) |
|
|
|
I have one suspicious chip too:  Look at number 16 on board 1. Just tried spiccioli's 50 value but the noncerate is still 0 for this chip. Just turn it off by setting the speed to zero.. That will help other chips to perform better. |
|
|
|
Im not entirely sure, but I'd say that chip 38 is dead and since they are chained any chips beyond it will not function.
I have a h-card with chips 7-16 inclusive which are dead, chip 16 barely hashes setting its speed at 50, but throws a ton of miso-errors. spiccioli I guess I'm just very unlucky, ordering 50gh and receiving 45gh..   I changed i to I, d to D, in every possible way, no way to turn on 38 or any later chip.. Thank you guys for your help, I will try to fire up the 2nd masterboard with the faulty hcard and another psu, but my hopes are already crushed. Right now its hashing with 20gh, what the.. Change it to "aIfDSo 54". Every letter has it's own meaning so you can't try upper and lower case letters randomly. I,D and S need to be on (CAPS = on). Some chips are just bad or even dead. I have some bad ones too. Great thing in Bitfury's gear is that other chips hash faster if one is turned off/dead. |
|
|
|
I'm raising or lowering the speed of the chips, depending on the number of errors. I have also turned off the autotune. The point of manual tuning is that it works a little bit better than autotune. Let's take the first chip as an example. Autotune is on ( AIfDSo). It can be turned off by changing the capital A to a normal a ( aIfDSo). Now the chip will always run at the speed you have set. Current speed is 55. Minimum is 52 and maximum is 57, higher the better of course. In this case I would raise the speed to 56 since there are practically no errors. Chip two: change the "aifdso" to "aIfDSo" and let's see how it does (it won't work at all with aifdso). Chip three: Something wrong with it. Turn off the autotune and keep the speed at 52. At least this is what I would do because 0,6 GH/s is still better than 0. More info here http://punin.com/README_BFSB_v0.1.txt |
|
|
|
Dani I hope you'll be able to solve the problem soon! Ok now, noob alarm! I'm here  I'm not good with ssh, so I ask you guys if I'm doing this right: I login as pi, go to the stat.log file and edit it with "pico .stat.log". I don't have write permission when editing it. Did I do ok so far? Now I see 3 chips that are shut down: 11 AIfDSo 0 16 AIfDSo 0 20 AIfDSo 0 and I set that to a(=Autotune off) 54(=Speed) 11 aIfDSo 54 16 aIfDSo 54 20 aIfDSo 54 Now I want to save the file to /opt/bitfury/best.cnf I press Ctrl+X, and it asks me if I want to save the file. I change the name to best.cnf Ok now the embarassing question: How can I save it in the right directory?.... yes I'm really that bad at it. After that I would just restart the miner and the chips should come to life? Thank you for helping me out! Here is how I tune my chips manually: - SSH into Pi (login "pi" password "raspberry"). - type "sudo nano /run/shm/.stat.log" - I'll edit the file and when done, press Ctrl+X - It will ask "Save modified buffer" and I press Y as in yes. - Now it says "File Name to Write: /run/shm/.stat.log". Just erase the whole file name with backspace and type "/opt/bitfury/best.cnf" and hit Enter. - type "sudo reboot" |
|
|
|
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. |
|
|
|
|
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.
|
|
|
|
 That is a sample picture of the file /run/shm/.stat.log Autotune ON = AIfDSo Autotune OFF = aIfDSo Number after the AIfDSo is the speed of the chip (52-57). Chip is off if it says 0. |
|
|
|
|
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.
|
|
|
|
could you tell us the ghz for ur setup?
500 GH/s. |
|
|
|
|
139mm but make it 140mm just in case.
That measurement is from edge of H-board's PCB to the edge of Raspi's PCB. Those two USB ports are sticking out a little bit but I don't think it matters when we are talking about case design. It's about 145mm with those USB ports.
|
|
|
|
I have to say I wish I had gone bitfury in the first place. These chips are at the moment my favourite on the market. Great looking pcbs too. If I wanted to run from a pc could I? M-board has GPIO connector and two PCI-E 6-pin connectors so Raspberry Pi is the way to go. Every piece of software can be updated. It's a normal RasPi so you can do whatever you want with it. |
|
|
|
|
Show Posts
