Has anyone tried bfgminer on a v3 m-board. I was under the impression that it does not work with v3 m-boards and using it could even damage the cards/system. Any info on this?
that's what i'm using as described above with v2.2 h boards been running rock solid for +48hr now. totally solved my intermittent, random disconnects which was destroying my HR. |
|
|
|
however, when i try to update bfgminer with: cd bfgminer && git pull && make && sudo make install && sudo shutdown -r now
i get this: error: Your local changes to the following files would be overwritten by merge:
driver-bfsb.c
Please, commit your changes or stash them before you can merge.
Aborting
how can i fix this error? I had that problem back when I tried to update cgminer in minepeon. Kano used this as a solution back then: git checkout etc/miner.conf.donate
git pull
So I am guessing (might be wrong) your solution might be something like this: cd bfgminer && git checkout driver-bfsb.c && git pull && make && sudo make install && sudo shutdown -r now worked great Morblias, thank you. my stratum connection is rock solid now and i'm continuing to tweek chip settings. |
|
|
|
Sorry to post technical on the sales thread but does anyone have or know where I can get an image for the V3 M board. Nothing on the OP and not getting answers from the other threads.
Thanks!!
This is what I'm running. It's set up to use bfgminer, not chainminer. https://dl.dropboxusercontent.com/u/57535575/bitfury-sd-card-customized-2.img.xzOnce you have it installed, you might want to update bfgminer: cd bfgminer && git pull && make && sudo make install && sudo shutdown -r now salfter, your image is working well. it's been 48 hr and my periodic "reset" issues have disappeared and i now have a much more stable HR. thank you. however, when i try to update bfgminer with: cd bfgminer && git pull && make && sudo make install && sudo shutdown -r now
i get this: error: Your local changes to the following files would be overwritten by merge:
driver-bfsb.c
Please, commit your changes or stash them before you can merge.
Aborting
how can i fix this error? You can clone bfgminer into a similar named dir. sorry, linux noob here. can you be more specific, preferably with code needed? Have you personally modified the bfsb driver c file ?
If so what change?
like salfter, i have been changing the chip speed settings downwards until i eliminate all chip errors. this seems to be working well but you have to recompile to save the changes and then restart. remember, i'm using salfter's image and i don't know if he made any other changes to this file but i haven't noticed anything out of the ordinary. eventually, i'd like to be able to compile bfgminer on my own but there seems to be a requirement to insert a couple of "sudo modprobe" commands somewhere to get it to work and i haven't figured that out yet. |
|
|
|
Sorry to post technical on the sales thread but does anyone have or know where I can get an image for the V3 M board. Nothing on the OP and not getting answers from the other threads.
Thanks!!
This is what I'm running. It's set up to use bfgminer, not chainminer. https://dl.dropboxusercontent.com/u/57535575/bitfury-sd-card-customized-2.img.xzOnce you have it installed, you might want to update bfgminer: cd bfgminer && git pull && make && sudo make install && sudo shutdown -r now salfter, your image is working well. it's been 48 hr and my periodic "reset" issues have disappeared and i now have a much more stable HR. thank you. however, when i try to update bfgminer with: cd bfgminer && git pull && make && sudo make install && sudo shutdown -r now
i get this: error: Your local changes to the following files would be overwritten by merge:
driver-bfsb.c
Please, commit your changes or stash them before you can merge.
Aborting
how can i fix this error? |
|
|
|
Anyone know where I can get a new one of these PCI-e to Screw Terminal adapters?
Or where I can get the lugs that attach and are crimpted to the wires so I can make it myself?
Additionally, is it kosher to have both PCIe connectors hooked up, in addition to these two screw terminals, if we want to ensure our rigs are getting all the juice they require ? Read: Is having 4 power sources going to the M-Board going to cause it to melt ? Would be interested in picking up a few of these cables as well. You should not connect more than one PSU to the same rig, because they will fight each other. But there's no harm connecting a single PSU to a rig with as many connections (screw, PCIe, etc) as you want, the more the better within reason. I highly recommend using four 6+2-pin or 8-pin PCIe power cables from your PSU for a full rig. 6-pin PCIe power cables may use the same wire gauge and connector quality, but may not have the best connections inside the PSU or may be too limited by any per-rail OCP. If your PSU doesn't have four 6+2-pin/8-pin connectors, it may not be designed to provide as much continuous power to them as you need. so it's ok to mix 2 pci-e and 2 ring connectors cables from the same psu to one rig? |
|
|
|
I have gone almost a month at 400+gh and now recently my reported speeds are more like 200-300 at the pool. Reported rates on the unit itself are in the 300-350 range but they used to be almost 500. I have applied heatsinks to the backs of the chips and voltage regulater area and this is a climate controlled room with cool air blowing over the cards. This is the new version hardware as well. I regularly have cards going to zero, I manually tune them as far as 49 and they work at low rates and another card goes to zero, always at least one card down, sometimes as many as three. I am using a 1200w power supply as well so it's hard to believe it's because they aren't getting juice.
Any thoughts?
this is my experience as well along with several others. |
|
|
|
|
"but, but, i'm still trying to compute!"
don't bother, honey.
|
|
|
|
After I ran the stop-stratumproxy.sh, start-stratumproxy.sh, stop-miner.sh and start-miner.sh scripts it started working. No idea what was wrong.
Welcome to BitFury. |
|
|
|
My 400GH/s Bitfury rig is not hashing after sudo reboot command
Output of /run/shm/.stat.log after reboot:
1 AIfDSo 52 0.000 0.000 0 0 0 0 0 $
2 AIfDSo 52 0.000 0.000 0 0 0 0 0 $
3 AIfDSo 52 0.000 0.000 0 0 0 0 0 $
Output of /run/shm/.stat.log after a few minutes following reboot:
1 AiFDso 52 0.000 0.000 0 0 0 0 0 $
2 AiFDso 52 0.000 0.000 0 0 0 0 0 $
3 AiFDso 52 0.000 0.000 0 0 0 0 0 $
As you can see, the autotune is turning off the chips.
Please help!
make sure you wait at least a few min for hashing to occur. make sure you have enough cooling via fans +/- heatsinks. try rearranging some h boards. other than that, rebooting should've worked. Thank you for taking the time to reply. Couple things to add - Ive had this up and running since December. Ive had the speeds up to 55 (880) but AC kept turning off, so I lowered down to 52 until I got that fixed. The AC was fixed today so I bumped the speeds up to 55 again and proceeded with the reboot. Logically followed it would imply that I screwed up the best.cnf file or something. This happened once before where I had did a search and replace all of 55 to 52, but forgot to go back and change the chip numbers 55, 155 and 255. Once I fixed this the miner started up fine. Knowing I had done this once before I manually checked all the chip numbers and they are sequentially correct. Is there any way to make/restore a default best.cnf? Create /opt/bitfury/best.cnf like this to run all chips at speed 52 with autotune disabled or to whatever you desire: rm /opt/bitfury/best.cnf ; for i in {1..256} ; do echo -e "$i\taIfDSo\t52" >> /opt/bitfury/best.cnf ; done
|
|
|
|
My 400GH/s Bitfury rig is not hashing after sudo reboot command
Output of /run/shm/.stat.log after reboot:
1 AIfDSo 52 0.000 0.000 0 0 0 0 0 $
2 AIfDSo 52 0.000 0.000 0 0 0 0 0 $
3 AIfDSo 52 0.000 0.000 0 0 0 0 0 $
Output of /run/shm/.stat.log after a few minutes following reboot:
1 AiFDso 52 0.000 0.000 0 0 0 0 0 $
2 AiFDso 52 0.000 0.000 0 0 0 0 0 $
3 AiFDso 52 0.000 0.000 0 0 0 0 0 $
As you can see, the autotune is turning off the chips.
Please help!
make sure you wait at least a few min for hashing to occur. make sure you have enough cooling via fans +/- heatsinks. try rearranging some h boards. other than that, rebooting should've worked. |
|
|
|
Please forgive my ignorance on this, but can I put bfgminer or cgminer on the pi and use that instead of chainminer? From the bfgminer page, there is no support for the V3 M-board and I have not been able to get cgminer running. I can compile it with bitfury enabled, but when I start it up I get nothing.
i'm successfully running salfter's image of bfgminer from here: https://bitcointalk.org/index.php?topic=251966.msg4511347#msg4511347just installed it yesterday and the great news is it seems to have solved my "reset" problems i described earlier. that was my first priority in evaluating bfgminer. i still need to fine tune them as the hashing rate is not optimal with a fair # of HW errors on some rigs but i'm very much encouraged. Awesome. I wasn't sure about that one, but I will give it a try. Thanks for the help. make sure you change the pool settings as they currently are pointed at his pool  |
|
|
|
Please forgive my ignorance on this, but can I put bfgminer or cgminer on the pi and use that instead of chainminer? From the bfgminer page, there is no support for the V3 M-board and I have not been able to get cgminer running. I can compile it with bitfury enabled, but when I start it up I get nothing.
i'm successfully running salfter's image of bfgminer from here: https://bitcointalk.org/index.php?topic=251966.msg4511347#msg4511347just installed it yesterday and the great news is it seems to have solved my "reset" problems i described earlier. that was my first priority in evaluating bfgminer. i still need to fine tune them as the hashing rate is not optimal with a fair # of HW errors on some rigs but i'm very much encouraged. |
|
|
|
hey guys i am running in to a problem with my rigs. i have two full rigs (v2 h-card & v3 m-board)
for some reason both of them just stop hashing. what could the problem? i'm still able to go in to the web browser.
Hit save stratum info, wait for the confirmation. hit stop miners, wait for the confirmation. hit start miners, wait for the confirmation. It should be hashing again in a minute or two, if not something else is wrong. (Internet connection working?) its not working. i really don't know whats wrong it was working fine. internet is working correctly. i have other miners that are still running. its still looks like it is hashing from the blinking green light. but on the site (bitfury admin page) it shows 0 hash. try sudo reboot |
|
|
|
anyone solomining with bitfury?
i am and maybe i can offer a helpful perspective below since i can "see" my local stratum pool connection. I don't think it's a miner issue.. but on some level it could be.
The ONLY pool I haven't had this issue is Bitminter. All other pools when I set the hashrate takes a nosedive about 20-30min after I let it run.
At first I was able to run about a month on bitcoin.cz before it started doing it regularly, then switched to Bitminter.
Now I was trying to split my workload 1/2 , so 1/2 was at Bitminter still and 1/2 went to CoinEX for whatever currency.
Sometimes it works fine with no issues.. like right now.., it's been up for about 14 hours with just Proxy restart (I implemented that 2-3 days ago) at other times I check the pool and it's mining at like 3Gh/s vs. 20Gh/s+ that it should be.
Restarting the whole setup sometimes makes it stable.., but I haven't really found the spot that makes it tick.
Really hope I wont have to toy this much with my X-3's, lol.
Thanks
i have the same problems. the rigs ran fine for the first month or so. then my local stratum server instance started showing spontaneous "resets" of all my rigs on a random basis about every 15 min or so. it's been going on for the last month and i've been tearing my hair out trying to figure it out. i say "reset" b/c i can see the connection to the stratum server behave just like it does when i start up a rig cold from a poweroff. i initially see a rapid scrolling upwards of hashing lines as the rig connects with the stratum server. stratum automatically slows the rapid scrolling down to a once every 30 sec interval via the vardiff. but then each chip only hashes around 10. it takes a miner restart manually to kick hashing up over 30. this is hopefully where it should stabilize. but then a spontaneous "reset" hits again. it "seems" to be correlated with heat although i'm not sure of this. this happens over and over. my belief is that Chainminer needs continuous updating via Jared to gain stability and stop these resets. i say this b/c w/o ckolivas constantly fine tuning my Avalon instance of cgminer over a dozen times, we never would have been able to mine on a stable basis. i don't think i'll ever buy another miner unless i know ckolivas is actively supporting a cgminer instance. edit: i may be wrong about it being chainminer. |
|
|
|
|
i keep getting ip conflicts with my multiple rigs.
anyone have a good strategy for avoiding this?
|
|
|
|
Sorry to post technical on the sales thread but does anyone have or know where I can get an image for the V3 M board. Nothing on the OP and not getting answers from the other threads.
Thanks!!
This is what I'm running. It's set up to use bfgminer, not chainminer. https://dl.dropboxusercontent.com/u/57535575/bitfury-sd-card-customized-2.img.xzOnce you have it installed, you might want to update bfgminer: cd bfgminer && git pull && make && sudo make install && sudo shutdown -r now the *.img.xz won't open up on my raspi. You don't open the image on the raspi. First the image is compressed with .xz so first extract it to get the actual .img file Then use whatever disk util you prefer to clone the image to the SD card. nvm, got it with 7zip. |
|
|
|
Sorry to post technical on the sales thread but does anyone have or know where I can get an image for the V3 M board. Nothing on the OP and not getting answers from the other threads.
Thanks!!
This is what I'm running. It's set up to use bfgminer, not chainminer. https://dl.dropboxusercontent.com/u/57535575/bitfury-sd-card-customized-2.img.xzOnce you have it installed, you might want to update bfgminer: cd bfgminer && git pull && make && sudo make install && sudo shutdown -r now the *.img.xz won't open up on my raspi. You don't open the image on the raspi. First the image is compressed with .xz so first extract it to get the actual .img file Then use whatever disk util you prefer to clone the image to the SD card. ah, can that extraction be done on a Windows machine or does it have to be linux? |
|
|
|
Sorry to post technical on the sales thread but does anyone have or know where I can get an image for the V3 M board. Nothing on the OP and not getting answers from the other threads.
Thanks!!
This is what I'm running. It's set up to use bfgminer, not chainminer. https://dl.dropboxusercontent.com/u/57535575/bitfury-sd-card-customized-2.img.xzOnce you have it installed, you might want to update bfgminer: cd bfgminer && git pull && make && sudo make install && sudo shutdown -r now the *.img.xz won't open up on my raspi. |
|
|
|
|
Show Posts
