Where can we find an image of the SD card? My filesystem is messed (fsck currently trying to repair...) because I powered off the rpi too often without proper shutdown. I'm worried I may need to reflash my SD card.
Topic: [GUIDE] BitFury Miner Support/Tuning - page 36. (Read 148049 times)
I didn't see this in the thread so I thought I would ask.
Is there any specific power supply that people recommend?
I'll be using it in conjunction with one of the open air metal cases that Spotswood makes, so I'd like it to be able to fit in that.
Is there any specific power supply that people recommend?
I'll be using it in conjunction with one of the open air metal cases that Spotswood makes, so I'd like it to be able to fit in that.
so there is no problem in using internal fast if it works any better? Is the speed range the same 53-57?
No, there's no problem. Not sure about the speed range. I would just experiment with different values and see what works best. I just added some heatsinks to one of my cards today to test them out before I committed to buying enough for all 16 cards.
They seem to fit the surface area of each chip perfectly.
http://www.amazon.com/Cosmos-Aluminum-Cooling-Heatsinks-cooler/dp/B007XACV8O/ref=sr_1_1?s=electronics&ie=UTF8&qid=1379368738&sr=1-1&keywords=Cosmos+%C2%AE+20+PCS+mini+Aluminum+Chips
They seem to fit the surface area of each chip perfectly.
http://www.amazon.com/Cosmos-Aluminum-Cooling-Heatsinks-cooler/dp/B007XACV8O/ref=sr_1_1?s=electronics&ie=UTF8&qid=1379368738&sr=1-1&keywords=Cosmos+%C2%AE+20+PCS+mini+Aluminum+Chips
I thought these chips were designed to put heat out through the bottom, and that heatsinks should go on the back of the board over the thermal vias...
Thanks I didn't realize the heat was designed to come out the back, I moved the heatsinks to the other side and the chips are staying much cooler now.
What does it really change using "Internal Fast" instead of "Internal Divided Slow" ?
The chips have 3 oscillator options: external, internal slow and internal fast. In addition, there's a /2 divider that can be switched on. Bitfury recommended the slow internal oscillator if it was fast enough. The /2 divider makes the clock slightly less jittery, and also allows smaller steps in clock speed. The H-cards have an option for external clock, but it's not used on the m-board.
Thanks,
so there is no problem in using internal fast if it works any better? Is the speed range the same 53-57?
spiccioli
What does it really change using "Internal Fast" instead of "Internal Divided Slow" ?
The chips have 3 oscillator options: external, internal slow and internal fast. In addition, there's a /2 divider that can be switched on. Bitfury recommended the slow internal oscillator if it was fast enough. The /2 divider makes the clock slightly less jittery, and also allows smaller steps in clock speed. The H-cards have an option for external clock, but it's not used on the m-board.
Pipe it through a socket to another machine?
Does Bitfury have any stratum logs i cant seem to find any and i keep having problems with Bitminter, Overnight the speed always drops to around 1gh/s tho bitfury admin still shows 40gh/s.
Edit
Ill try https://bitcointalksearch.org/topic/m.3172013 see if it makes any difference
Edit
Ill try https://bitcointalksearch.org/topic/m.3172013 see if it makes any difference
no id doesnt by default, but you can load up the screen instance (see screen -ls)
You could use tee on the startup to pipe to a logfile and the screen, I guess, but you aint got a lot of space there
Does Bitfury have any stratum logs i cant seem to find any and i keep having problems with Bitminter, Overnight the speed always drops to around 1gh/s tho bitfury admin still shows 40gh/s.
Edit
Ill try https://bitcointalksearch.org/topic/m.3172013 see if it makes any difference
Edit
Ill try https://bitcointalksearch.org/topic/m.3172013 see if it makes any difference
Added:
7. Hashrate droping regularly, despite bitfury admin showing steady noncerate?
Someone may find this useful... If your pool reports your hashrate dropping regularly DESPITE bitfury admin showing steady noncerate:
1) ssh into your pi
2) run command: crontab -e
3) add this line at the end of file:
It will restart your stratum proxy every 10 minutes from now on. If you want to cancel it, just run the command again and delete the line.
1) ssh into your pi
2) run command: crontab -e
3) add this line at the end of file:
Quote
*/10 * * * * sudo /opt/bitfury/start-stratumproxy.sh
4) save & exitIt will restart your stratum proxy every 10 minutes from now on. If you want to cancel it, just run the command again and delete the line.
I have it running at 480 465 GH/s stable now. Thats a 400 GH/s kit. So I'm pretty happy with that...I'm staying at 1.2 .
Using pencil trick, I had an H-Card go from 21 GH/s to 39 GH/s . However, after 60 seconds the hashrate slowly decreases to lower than 21 GH/s. Is this a result of the auto-tuning?
EDIT: When miner is restarted, card goes back to 39 GH/s .. but then does the same thing.
EDIT: When miner is restarted, card goes back to 39 GH/s .. but then does the same thing.
What did you set it to?
Mine has been rock solid all day. Few rare errors, like 150 out of over 200k.
Make sure the you're reading no less than 1.1k Ohm on your multimeter. I screwed up the first time and got a reading of 1.08k which was too little resistance which caused some chips to shutdown and kill my hashrate... Then after redoing it, I got a reading of 1.18k. Since then, I've been rock solid between 32-34Gh/s for a day and a half now.
Using pencil trick, I had an H-Card go from 21 GH/s to 39 GH/s . However, after 60 seconds the hashrate slowly decreases to lower than 21 GH/s. Is this a result of the auto-tuning?
EDIT: When miner is restarted, card goes back to 39 GH/s .. but then does the same thing.
My guess-EDIT: When miner is restarted, card goes back to 39 GH/s .. but then does the same thing.
The regulator autoshutting
....Is there a way to run it and not have it autoshutdown? It was hashing like a boss...Heat was fine...is it the auto-tune, or a hardware limit I'm hitting?
Wow, how can it increase hashing so much while stating that "heat was fine"? Did you actually measure with a temperature probe placed on the board?
The board is self-protecting itself from being fried and by pencil modding it you also just voided its warranty.
Using pencil trick, I had an H-Card go from 21 GH/s to 39 GH/s . However, after 60 seconds the hashrate slowly decreases to lower than 21 GH/s. Is this a result of the auto-tuning?
EDIT: When miner is restarted, card goes back to 39 GH/s .. but then does the same thing.
My guess-EDIT: When miner is restarted, card goes back to 39 GH/s .. but then does the same thing.
The regulator autoshutting
....Is there a way to run it and not have it autoshutdown? It was hashing like a boss...Heat was fine...is it the auto-tune, or a hardware limit I'm hitting?
I just added some heatsinks to one of my cards today to test them out before I committed to buying enough for all 16 cards.
They seem to fit the surface area of each chip perfectly.
http://www.amazon.com/Cosmos-Aluminum-Cooling-Heatsinks-cooler/dp/B007XACV8O/ref=sr_1_1?s=electronics&ie=UTF8&qid=1379368738&sr=1-1&keywords=Cosmos+%C2%AE+20+PCS+mini+Aluminum+Chips
They seem to fit the surface area of each chip perfectly.
http://www.amazon.com/Cosmos-Aluminum-Cooling-Heatsinks-cooler/dp/B007XACV8O/ref=sr_1_1?s=electronics&ie=UTF8&qid=1379368738&sr=1-1&keywords=Cosmos+%C2%AE+20+PCS+mini+Aluminum+Chips
I thought these chips were designed to put heat out through the bottom, and that heatsinks should go on the back of the board over the thermal vias...
Using pencil trick, I had an H-Card go from 21 GH/s to 39 GH/s . However, after 60 seconds the hashrate slowly decreases to lower than 21 GH/s. Is this a result of the auto-tuning?
EDIT: When miner is restarted, card goes back to 39 GH/s .. but then does the same thing.
EDIT: When miner is restarted, card goes back to 39 GH/s .. but then does the same thing.
What did you set it to?
Mine has been rock solid all day. Few rare errors, like 150 out of over 200k.
I just added some heatsinks to one of my cards today to test them out before I committed to buying enough for all 16 cards.
They seem to fit the surface area of each chip perfectly.
http://www.amazon.com/Cosmos-Aluminum-Cooling-Heatsinks-cooler/dp/B007XACV8O/ref=sr_1_1?s=electronics&ie=UTF8&qid=1379368738&sr=1-1&keywords=Cosmos+%C2%AE+20+PCS+mini+Aluminum+Chips
http://i106.photobucket.com/albums/m264/atunicus/DSCN0803.jpg
They seem to fit the surface area of each chip perfectly.
http://www.amazon.com/Cosmos-Aluminum-Cooling-Heatsinks-cooler/dp/B007XACV8O/ref=sr_1_1?s=electronics&ie=UTF8&qid=1379368738&sr=1-1&keywords=Cosmos+%C2%AE+20+PCS+mini+Aluminum+Chips
http://i106.photobucket.com/albums/m264/atunicus/DSCN0803.jpg
Using pencil trick, I had an H-Card go from 21 GH/s to 39 GH/s . However, after 60 seconds the hashrate slowly decreases to lower than 21 GH/s. Is this a result of the auto-tuning?
EDIT: When miner is restarted, card goes back to 39 GH/s .. but then does the same thing.
My guess-EDIT: When miner is restarted, card goes back to 39 GH/s .. but then does the same thing.
The regulator autoshutting
Using pencil trick, I had an H-Card go from 21 GH/s to 39 GH/s . However, after 60 seconds the hashrate slowly decreases to lower than 21 GH/s. Is this a result of the auto-tuning?
EDIT: When miner is restarted, card goes back to 39 GH/s .. but then does the same thing.
EDIT: When miner is restarted, card goes back to 39 GH/s .. but then does the same thing.
Hi,
I've found, because of an error, that sometimes a bad chip can hash at low speed using "aIFdso" instead of the normal "aIfDSo" flag string.
What does it really change using "Internal Fast" instead of "Internal Divided Slow" ?
I've made tests lowering speed down to 10 without conclusive findings, btw boards are extremely "instable", simply restarting miner can be enough for a good chip to start throwing errors that slow it down/shut it down.
I'm going to change miner so that best.conf speed is the minimum it can go irregardless of errors of any kind while keeping the auto-tune flag active.
I'm doing this to see if I can stop the spiralling down of the unit which tends to slow down if left mining alone with auto-tune on.
spiccioli
ps. note that I've changed my miner to accept speeds lower than 52 and that I've not pencil-modded them (yet).
I've found, because of an error, that sometimes a bad chip can hash at low speed using "aIFdso" instead of the normal "aIfDSo" flag string.
Code:
18 aIFdso 47 0.687 0.888 48 26 0 0 84 [1:1] 288 4 3 3 4 1 2 3 2 2 3 4 2 4 4 3 4 1 2 1 0 3 2 1 2 3 2 1 3 1 1 2 1
47 aIFdso 40 0.272 0.835 19 26 0 0 79 [2:E] 443 1 2 1 1 2 1 1 1 2 2 0 1 1 1 1 1 2 1 2 1 0 1 2 2 1 1 3 2 2 2 2 2
72 aIFdso 47 0.487 0.930 34 19 0 0 88 [4:7] 288 2 3 2 2 2 1 3 2 1 3 2 3 2 2 2 2 1 0 1 1 1 2 0 2 3 1 2 1 1 1 1 1
97 aIFdso 47 0.515 0.814 36 24 0 0 77 [6:0] 288 1 1 2 2 2 1 2 3 2 3 3 2 4 1 3 4 3 2 1 1 1 3 2 1 2 1 1 2 0 3 1 0
143 aIFdso 40 0.344 0.909 24 22 0 0 86 [8:E] 504 2 2 1 2 2 2 1 2 0 2 1 1 1 2 0 3 1 1 2 1 1 1 2 1 3 1 2 1 1 1 3 0
151 aIFdso 47 0.458 0.814 32 14 0 0 77 [9:6] 288 2 2 2 3 3 2 2 3 2 1 1 1 2 2 3 1 1 1 1 0 0 1 1 0 1 1 1 2 1 1 0 2
162 aIFdso 47 0.558 0.814 39 17 0 0 77 [A:1] 288 2 3 1 4 4 1 2 2 3 3 3 3 1 1 3 3 2 1 3 0 0 2 1 1 0 0 0 0 2 3 1 1
178 aIFdso 40 0.329 0.824 23 20 0 0 78 [B:1] 552 3 0 2 2 1 1 1 1 0 3 1 2 1 2 2 1 0 3 1 0 1 1 1 1 3 0 2 1 2 1 1 2
182 aIFdso 40 0.086 0.835 6 45 0 0 79 [B:5] 656 1 1 0 0 0 1 0 0 0 2 0 0 1 0 0 0 2 2 3 3 4 3 4 3 3 1 3 3 2 3 3 3
200 aIFdso 48 0.716 0.877 50 0 0 0 83 [C:7] 36 3 3 3 3 3 3 3 3 3 3 3 3 4 4 3 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
205 aIFdso 44 0.544 0.698 38 0 0 0 66 [C:C] 36 2 3 3 3 3 3 3 2 2 2 2 2 2 2 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
225 aIFdso 40 0.501 0.835 35 19 0 0 79 [E:0] 288 3 3 1 2 1 3 2 2 0 3 3 2 3 3 2 2 1 1 2 1 2 0 1 1 3 0 0 1 1 1 2 2
238 aIFdso 40 0.415 0.708 29 15 0 0 67 [E:D] 289 1 3 1 2 2 2 3 2 2 3 1 2 2 0 1 2 2 0 2 1 1 1 0 1 1 0 1 0 0 2 2 1
254 aIFdso 40 0.229 0.846 16 42 0 0 80 [F:D] 596 0 0 0 1 3 2 1 0 2 1 1 1 1 1 1 1 4 4 4 3 1 1 2 3 1 2 2 3 3 3 3 3
256 aIFdso 44 0.415 0.877 29 14 0 0 83 [F:F] 324 2 1 2 1 3 3 3 1 2 2 1 2 1 2 1 2 1 2 1 2 0 0 0 2 0 0 1 0 1 1 2 1
47 aIFdso 40 0.272 0.835 19 26 0 0 79 [2:E] 443 1 2 1 1 2 1 1 1 2 2 0 1 1 1 1 1 2 1 2 1 0 1 2 2 1 1 3 2 2 2 2 2
72 aIFdso 47 0.487 0.930 34 19 0 0 88 [4:7] 288 2 3 2 2 2 1 3 2 1 3 2 3 2 2 2 2 1 0 1 1 1 2 0 2 3 1 2 1 1 1 1 1
97 aIFdso 47 0.515 0.814 36 24 0 0 77 [6:0] 288 1 1 2 2 2 1 2 3 2 3 3 2 4 1 3 4 3 2 1 1 1 3 2 1 2 1 1 2 0 3 1 0
143 aIFdso 40 0.344 0.909 24 22 0 0 86 [8:E] 504 2 2 1 2 2 2 1 2 0 2 1 1 1 2 0 3 1 1 2 1 1 1 2 1 3 1 2 1 1 1 3 0
151 aIFdso 47 0.458 0.814 32 14 0 0 77 [9:6] 288 2 2 2 3 3 2 2 3 2 1 1 1 2 2 3 1 1 1 1 0 0 1 1 0 1 1 1 2 1 1 0 2
162 aIFdso 47 0.558 0.814 39 17 0 0 77 [A:1] 288 2 3 1 4 4 1 2 2 3 3 3 3 1 1 3 3 2 1 3 0 0 2 1 1 0 0 0 0 2 3 1 1
178 aIFdso 40 0.329 0.824 23 20 0 0 78 [B:1] 552 3 0 2 2 1 1 1 1 0 3 1 2 1 2 2 1 0 3 1 0 1 1 1 1 3 0 2 1 2 1 1 2
182 aIFdso 40 0.086 0.835 6 45 0 0 79 [B:5] 656 1 1 0 0 0 1 0 0 0 2 0 0 1 0 0 0 2 2 3 3 4 3 4 3 3 1 3 3 2 3 3 3
200 aIFdso 48 0.716 0.877 50 0 0 0 83 [C:7] 36 3 3 3 3 3 3 3 3 3 3 3 3 4 4 3 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
205 aIFdso 44 0.544 0.698 38 0 0 0 66 [C:C] 36 2 3 3 3 3 3 3 2 2 2 2 2 2 2 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
225 aIFdso 40 0.501 0.835 35 19 0 0 79 [E:0] 288 3 3 1 2 1 3 2 2 0 3 3 2 3 3 2 2 1 1 2 1 2 0 1 1 3 0 0 1 1 1 2 2
238 aIFdso 40 0.415 0.708 29 15 0 0 67 [E:D] 289 1 3 1 2 2 2 3 2 2 3 1 2 2 0 1 2 2 0 2 1 1 1 0 1 1 0 1 0 0 2 2 1
254 aIFdso 40 0.229 0.846 16 42 0 0 80 [F:D] 596 0 0 0 1 3 2 1 0 2 1 1 1 1 1 1 1 4 4 4 3 1 1 2 3 1 2 2 3 3 3 3 3
256 aIFdso 44 0.415 0.877 29 14 0 0 83 [F:F] 324 2 1 2 1 3 3 3 1 2 2 1 2 1 2 1 2 1 2 1 2 0 0 0 2 0 0 1 0 1 1 2 1
What does it really change using "Internal Fast" instead of "Internal Divided Slow" ?
I've made tests lowering speed down to 10 without conclusive findings, btw boards are extremely "instable", simply restarting miner can be enough for a good chip to start throwing errors that slow it down/shut it down.
I'm going to change miner so that best.conf speed is the minimum it can go irregardless of errors of any kind while keeping the auto-tune flag active.
I'm doing this to see if I can stop the spiralling down of the unit which tends to slow down if left mining alone with auto-tune on.
spiccioli
ps. note that I've changed my miner to accept speeds lower than 52 and that I've not pencil-modded them (yet).
Jump to: