I have talked with our EE he has said that the hashrate of 2.2ghs is because of the bitfury chip. He says that this is the average that people will be getting. If you are lucky you can get units that perform higher or if you aren't lucky you could potentially get some worse units it all depends on the bitfury chip. It seems when we build prototypes that we where lucky with the chips that we received.
For fairness, the burden of this 'bad luck' should be carried mainly by the seller, not by the consumers. The specified claimed performance was "Spec: Rated speed 2.6Gh/s. +/- 10%" ( https://bitcointalk.org/index.php?topic=299295.0. You probably need to consider some sort of compensation, for example in coupons on future sales, rather than 'passing the buck' and blaming luck. |
|
|
|
The latest cgminer doesn't work at all (not even for block erupters, and yes, tried without them plugged in also) it just says "failed to initialise" / "you need to install a WinUSB driver for - BF1"
I have tried versions 3.7, 3.6.6, 3.5 and 3.4.3, to no avail
Well the instructions are pretty clear. Cgminer won't work till you install a winusb driver for any USB devices. The instructions are plastered all over the README and ASIC-README files. I followed these instructions, installed the winusb driver with the aid of zadig, the BF1 device was correctly identified in Device Manager, but Cgminer 'refused' to detect it....  Cheers Kabopar |
|
|
|
Ok, so this is getting frustrating...
I've downloaded the bfgminer build which has the bf1.inf in it, which i've installed for my device successfully getting a COM port assigned to it.. yet no miner will work with it
The latest cgminer doesn't work at all (not even for block erupters, and yes, tried without them plugged in also) it just says "failed to initialise" / "you need to install a WinUSB driver for - BF1"
I have tried versions 3.7, 3.6.6, 3.5 and 3.4.3, to no avail
bfgminer simply won't detect anything... at all... just says no devices.. have tried the -S bigpic:all as well as \\.\COMn aswell as bigpic:\\.\COMn
it fails to work with either block erupter or bluefury
I have tried the version with the .inf, as well as version 3.4.0
bitminter beta detects all devices... but the bluefury gets the error "Probe of port COM43 failed: timeout"
I really don't care what miner I have to use, and whether or not it can run both varieties of miners at the same time or not.. I just want them hashing...
FYI, I am working with the infamous Windows Vista
P.S: Despite not hashing, the device gets hot, wtf?
This made me think it was DOA - but I have now tried 2 different devices, and they both behaved the same way.
So, can anybody please tell me what they're using, and how they got it to work? or point out anything I've clearly missed?
Thanks in advance
I did not try it on Vista. On Win7 I am using the bfgminer32 per the instructions earlier in this thread. I use the sample #MINE.bat file edited to suit my pool. bfgminer.exe -S "BF1:all" -o (not bigpic:all). My single BF1 device gets about 2.26 GH/sec (I think that the number that matters is the second number in the bfgminer display, which is the all time average, while the first is a short term exponentially decaying average and the last number looks like a short time actually submitted shares average. The long term average should be taken after things stabilize (quoting any numbers in the first few minutes is misleading and not representative of the long term performance). Good luck Yes!! the BF1:all worked! and getting a steady 2.33 Thank you so much. I'm glad it was something stupidly simple I was doing wrong, I was getting worried. I'd like to tip you, have an address?  I'm glad that it worked for you! your tip is appreciated 1ERcg5GaUri6gSpnUDuwBz6o2mY6vGwM3b Cheers Kabopar |
|
|
|
Ok, so this is getting frustrating...
I've downloaded the bfgminer build which has the bf1.inf in it, which i've installed for my device successfully getting a COM port assigned to it.. yet no miner will work with it
The latest cgminer doesn't work at all (not even for block erupters, and yes, tried without them plugged in also) it just says "failed to initialise" / "you need to install a WinUSB driver for - BF1"
I have tried versions 3.7, 3.6.6, 3.5 and 3.4.3, to no avail
bfgminer simply won't detect anything... at all... just says no devices.. have tried the -S bigpic:all as well as \\.\COMn aswell as bigpic:\\.\COMn
it fails to work with either block erupter or bluefury
I have tried the version with the .inf, as well as version 3.4.0
bitminter beta detects all devices... but the bluefury gets the error "Probe of port COM43 failed: timeout"
I really don't care what miner I have to use, and whether or not it can run both varieties of miners at the same time or not.. I just want them hashing...
FYI, I am working with the infamous Windows Vista
P.S: Despite not hashing, the device gets hot, wtf?
This made me think it was DOA - but I have now tried 2 different devices, and they both behaved the same way.
So, can anybody please tell me what they're using, and how they got it to work? or point out anything I've clearly missed?
Thanks in advance
I did not try it on Vista. On Win7 I am using the bfgminer32 per the instructions earlier in this thread. I use the sample #MINE.bat file edited to suit my pool. bfgminer.exe -S "BF1:all" -o (not bigpic:all). My single BF1 device gets about 2.26 GH/sec (I think that the number that matters is the second number in the bfgminer display, which is the all time average, while the first is a short term exponentially decaying average and the last number is the actually submitted shares average. The long term average should be taken after things stabilize (quoting any numbers in the first few minutes is misleading and not representative of the long term performance). Good luck |
|
|
|
|
Thanks. I'm in Sydney, the Drillbit website says "Direct Bank Deposit - Australian customers are welcome to pay via direct bank transfer", but it's not clear if this is still the policy.
Cheers
|
|
|
|
|
Barn,
(see pm) I'm interested in Drillbit 8 board. Do you accept local bank deposits as well as BTC?
Cheers
|
|
|
|
Here it is on Win7  and here on Ubuntu 13.10  In all tests got an average hash rate of about 2.26 GH/sec |
|
|
|
I meant to try Eligius earlier, I haven't used it in a few weeks now... but I have made most of my btc there... anyhow..
Switched the pool, I see 4 at 2.6GH/s to 3GH/s, going to going to give it a little while, but I am seeing much better numbers off the bat with Eligius (still have yet to see a HW error!).
Tried Eligius as well, for almost 7 minutes, the hash rate was as on the previous pools that I tried (Slush and BTC)  |
|
|
|
Are you using Ubuntu 13 or 12.04.xx? Just curious.
I am using 13 I switched as I was using 12.04... after switching it appears the rep is having some issues (didn't on 12.04) of which won't let you install bfgminer (that way). I checked the server, the server connection is fine, just files aren't there.  I am getting this also on Ubuntu 13.10 In "software and updates", "other software" you have to change "saucy" to "raring" in the ppa. Thanks for the useful tip about the ppa repository settings. I had the same problem and applying this allowed me to install bfgminer on Ubuntu 13.10 (amd64). It is running bfgminer 3.0.99 now with the BF device, reaching about 2.26 GH/sec as on the Win7 machine. We may be entitled to some compensation, as it is becoming clear that the BlueFury cannot attain the originally specified hash rate. [img]https://i.imgur.com/OtZFnpv.jpg[img] after more than 1 hour, so it is statistically correct |
|
|
|
Interested in how this is working with cgminer. Anyone using it successfully? Did cgminer find it on its own?
I can't get cgminer to detect mine either... zadig worked fine and my computer recognizes them, just no cgminer... What is the command to recognize them?? Also, when following the driver installation instructions to switch to bfgminer, I get an access denied error when installing... +1 When you switch back to bfgminer you need to re-install the original drivers (that were modified by zadig). I went through this and managed to get back to bfgminer (use the file indicated earlier in this thread, which contains the driver for the BF device as well as a bfgminer version 3.2.0 which avoids the hardware errors that later versions have). |
|
|
|
Well... I compiled the latest revision of CGMiner on MinePeon 0.2.4 w/options --disable-opencl --disable-adl --enable-bflsc --enable-bitforce --enable-icarus --enable-modminer --enable-ztex --enable-avalon --enable-bitfury (same options as the tutorial in Rasbian Wheezy). The devices were never detected, so I switched to Raspbian Wheezy, latest updated, first trying CGMiner per the .DEB package and instructions on the tutorial, results were the same, no devices were detected under CGMiner (they would show in lsusb).  I then uninstalled the CGMiner package (dpkg -r cgminer) and installed BFGMiner per tutorial instructions, after which the devices were detected. This is a hub that I can easily run 8 ASIC Erupters, so it should have no power issues running 8 BlueFuries, however I started off with 5 and decided to let them hash awhile to see what kind of rates I was getting... Granted, I'm not getting any hardware errors (which is awesome), but also not seeing GH/s rate I should be seeing. Now with this being said, I am going to try a few different pools and see what results I have. As well, I'm going to try to make a build on Raspbian of CGMiner (since I have yet to get CGMiner to work with the devices and apparently CGMiner so far, from what I've read has the best results...).  EDIT: Just made a fresh build of CGMiner on Raspbian, still won't detect any devices, I also notice that CGMiner disables all the devices as I tried to use BFGMiner after (which was working seconds before trying CGMiner) and get 'All devices disabled, cannot mine!'. I thought that was semi-interesting... Congrats on getting this going. I also could not get CGMiner to detect the BF device. Your hash rates are similar to what I got, which is below the advertised "Spec: Rated speed 2.6Gh/s. +/- 10%"  |
|
|
|
Can someone please post their .bat for bfgminer. I used win7 install instructions. Drivers have loaded fine. But I can't get bfgminer to recognize the BitFurys. Using bfgminer 3.2.3-win32. The only thing it's recognizing is OCL - whatever that is.
using bfgminer32 ver 3.2.0 and the batch file as per the Mining Support instructions (edit the file #Mine.bat) bfgminer.exe -S "BF1:all" -o stratum+tcp://stratum.bitcoin.cz:3333 -u ..... works ok w/o H errors I did not find a way yet to get more than about 2.26 GH/sec from my single BF device. OK - I have ver 3.2.0 but see no file #mine.bat. Does the # stand for something else? I have never seen a file start with #. I downloaded the bfgminer version from the Win7 instructions earlier in this thread (Download Alpha Drivers Here : http://www.mediafire.com/download/819me4zvdju8lyg/bfgminerWin.zip) There is a file called #MINE.bat, which you can edit with notepad. The original content is bfgminer.exe -S "BF1:all" -o stratum+tcp://stratum.mining.eligius.st:3334 -O YOUR_BITCOIN_ADDRESS The important part is the BF driver which is pointed to by the file bf1.inf in this zip file. You have to install this driver per the instructions in this thread to get the BF device recognized. Good luck |
|
|
|
I run Block erupters and a Red fury on one machine. Compiled cgminer without bitfury support and bfgminer with only bitfury support and I run both on the same computer.
I now run both my BE's and single BlueFury on the same Win7 64 machine with 2 separate instances of bfgminer (3.2.1 for the BE's with the -s erupter: all in the short-cut's target command line and 3.2.0 with bfgminer.exe -S "BF1:all" -o ... in a batch file (as per Beastlymac's mining support thread)). I'm getting the same performance as when I ran them on 2 separate PC's. The BE instance is turned on first, then the BF. There is a brief message when the 2nd one starts, but the BF device is detected consistently. |
|
|
|
Received mine today they are hashing but with horrible error rates 58%+ and only hashing at 2.3GH
Miner Version
bfgminer3.4.0
Devices
Name ID Temp MH/s Accept Reject Error Utility Last Share
BPM 0 N/A 2313.506 93 0 [0%] 387 [59.36%] 11.093 20:24:44
BPM 1 N/A 2218.942 93 0 [0%] 446 [62.91%] 11.093 20:24:48
Totals 2 4532.448 186 0 [0%] 833 [61.13%] 22.186
For now I would recommend everyone use cgminer or our version of bfgminer 3.0.99 until we fix it. I have been communicating with Luke and we are working out the issues. switched to your specific Raspbian Wheezy Setup Bfgminer build and still only getting 2.3GH Look like these are performing 20% lower than spec. I'm running only two of them in a D-Link Hi-Speed USB 2.0 7-Port Powered Hub (DUB-H7) and 1 raspberry Pi as controller I am running a single BF, on Win7 per the instructions in https://bitcointalk.org/index.php?topic=319419.0. With bfgminer ver 3.2.0 and the recommended batch file (bfgminer.exe -S "BF1:all" -o ...) it runs without H errors, but with the same lower hash rate that you are getting (about 2.26 GH/sec)....  |
|
|
|
|
Tried ubuntu x386 12.10 with bfgminer, however it failed to detect the BF device (used -S /dev/ttyACM0)
previously also tried cgminer 3.6.6.1 on Win7, but this did not detect the BF miner (driver was installed using zadig, and showed up in Device Manager)
back to bfgminer 3.2.0 on Win7...
hashing rate is still 2.26 GH, tried on 2 pools (Slush and BTC Guild), the bfgminer display is consistent with what the pools report.
|
|
|
|
Can someone please post their .bat for bfgminer. I used win7 install instructions. Drivers have loaded fine. But I can't get bfgminer to recognize the BitFurys. Using bfgminer 3.2.3-win32. The only thing it's recognizing is OCL - whatever that is.
using bfgminer32 ver 3.2.0 and the batch file as per the Mining Support instructions (edit the file #Mine.bat) bfgminer.exe -S "BF1:all" -o stratum+tcp://stratum.bitcoin.cz:3333 -u ..... works ok w/o H errors I did not find a way yet to get more than about 2.26 GH/sec from my single BF device. |
|
|
|
Interested in how this is working with cgminer. Anyone using it successfully? Did cgminer find it on its own?
Tried cgminer 3.5.0, installed the drivers using zadig, but cgminer wouldn't detect the BF device. Gave up, installed the previous driver and went back to bfgminer. So far only bfgminer32 ver 3.2.0 as in the guide above works with a low H error rate. It is detected with bfgminer64 ver 3.4.0, but the H error rate is very high. On my single BF device I could not get higher hash rate than about 2.26 GH/sec. |
|
|
|
After trying to run the Blue Fury miner with bfgminer3.4.0 with -S bigpic:all, it was detected and hashed, but had a very high H error rate (about 61%) after about 40 minutes. The hash rate was about 2.26 GH/Sec.
Trying the original modified bfgminer 3.2.0 resolves the H error rate, but the hash rate is still about 2.26 GH/sec.
Is there any way to change the configuration or firmware to get closer to the specifiec 2.6 GH/sec?
A couple of things. Do you mean version 3.0.99? Have you tried cgminer? What hub are you using? Are you sure it is providing enough power. Are you able to test on a Ubuntu pc? Have you tried a different pool? I downloaded the file per the installations instructions in this thread, and it runs bfgminer 3.2.0 (that is the text appearing in the DOS box when it runs), not 3.0.99. I just downloaded it again and it has the same date/time and size as the one that I am running. I did not try cgminer or Ubuntu yet (I prefer to stay with bfgminer, as it is running well with my USB BE's and I read that cgminer tends to disrupt the drivers for those). The hub used is a cheap 10 port USB 2.0 with a 4A supply. This BlueFury is the only device on the hub, so there should be no issue with power. I tried a different pool (BTC guild) and the hash rate is similar. Ok, am I right to assume you are trying to run both the block eruptors and the fury unit in the same instance of bfgminer? If so can you try just running it on its own without the block eruptors plugged in? Also does your command line have Icarus:all and bigpic:all? Edit don't worry I have had a talk with Luke-jr and it is something we should fix in a couple of days if necessary we will push a new firmware out to the public. Sorry for the inconvenience. The BlueFury is running on a separate PC, which does not have any USB BE's. I intend to eventually run both on the same PC, under separate instances of bfgminer. The bfgminer command line uses the #mine.bat batch file in the guidelines which contains bfgminer.exe -S "BF1:all" -o pool url -u user -p pwd I tried to install cgminer on windows, but still have a problem with it recognizing the BlueFury device. I installed the driver using zadig, I can see it in Device Manager, but have no idea how to convince Cgminer to detect it. I went now back to bfgminer (had to revert back to the Com driver) so that it can do something useful while I look for a better solution. Is Icarus:all and bigpic:all needed on the bfgminer command line? |
|
|
|
After trying to run the Blue Fury miner with bfgminer3.4.0 with -S bigpic:all, it was detected and hashed, but had a very high H error rate (about 61%) after about 40 minutes. The hash rate was about 2.26 GH/Sec.
Trying the original modified bfgminer 3.2.0 resolves the H error rate, but the hash rate is still about 2.26 GH/sec.
Is there any way to change the configuration or firmware to get closer to the specifiec 2.6 GH/sec?
A couple of things. Do you mean version 3.0.99? Have you tried cgminer? What hub are you using? Are you sure it is providing enough power. Are you able to test on a Ubuntu pc? Have you tried a different pool? I downloaded the file per the installations instructions in this thread, and it runs bfgminer 3.2.0 (that is the text appearing in the DOS box when it runs), not 3.0.99. I just downloaded it again and it has the same date/time and size as the one that I am running. I did not try cgminer or Ubuntu yet (I prefer to stay with bfgminer, as it is running well with my USB BE's and I read that cgminer tends to disrupt the drivers for those). The hub used is a cheap 10 port USB 2.0 with a 4A supply. This BlueFury is the only device on the hub, so there should be no issue with power. I tried a different pool (BTC guild) and the hash rate is similar. |
|
|
|
Julz, thanks for the direct delivery. I managed to get it going, but the results are strange. Not sure if it is a faulty device or something else. Running the latest BFGMiner (3.4.0). The rest of the installation is per Beastlymac in https://bitcointalk.org/index.php?topic=299295.0. To avoid interactions with other things it is running entirely alone, on a separate Win7 64 PC as a single device on a powered hub. I am getting a very high H error rate (about 61% after about 40 minutes) and the hash rate is about 2.26GH/sec (on Slush's pool). I tried resetting the device, the miner software etc, but there is no improvement. I wonder if it is a faulty device or a configuration problem. Cheers I think it is something to do with the latest version of bfgminer. I would try either our version or the latest cgminer version. Alternatively if you can install a Ubuntu vm or just install Ubuntu and dual boot I would recommend that. Thanks Beastlymac, I'll try these suggestions. As I already found, with the original modified bfgminer 3.2.0 that you recommend in your guide, the H error issue is gone, but the hash rate remains lower than expected at about 2.26 GH/sec. (Life would be boring without some little puzzles like this one... Cheers |
|
|
|
|
Show Posts
