So can anyone tell me if a Raspberry Pi would actually work 100% with these at full speed?
I am using a http://www.amazon.co.uk/ORICO-Splitter-Aluminum-Backward-Compatible/dp/B00ECTIFW0/ref=sr_1_2?ie=UTF8&qid=1390469941&sr=8-2&keywords=ORICO+A3H10
ORICO A3H10 as my USB hub.
Will this work 100% with a Raspberry Pi and these BiFury's?
Would I install MinePeon on the Pi?
Topic: [ANN] Bi•Fury | 5 GH/s USB Miner [IN STOCK!] {SALE !} - page 6. (Read 305076 times)
Still cant get my bi*fury's to run on raspberry... If its the same problem a week from now, im going to sell them again.
What a waste of money and time, and no support from sellers what so ever.
DONT BUY THESE
What a waste of money and time, and no support from sellers what so ever.
DONT BUY THESE
They won't run on a rasberry pi as the native usb ports do not give enougth power. The pi also does not detect USB 3 hubs which you pretty much need for these. Try hooking the pi up to a POWERED USB 2 hub and make sure it has plenty of power. Using a 48W USB3 hub i can only run 4 of these on one hub.
I think you need some Dipo Electronic USB hubs. Professional standarded, 700 mA per port so all 19 ports can work even if you fill them up with bi-furies!
Check out my thread here:
https://bitcointalksearch.org/topic/sold-out-dipo-electronic-19-port-usb-hubs-418087
or
https://bitcointalksearch.org/topic/in-stock-shipping-open-professional-quality-usb-hubs-for-usb-bitcoin-miners-413406
why some times flash a red light and other time green? What that means?
That is when it is working on the shares and stuff when mining. 
why some times flash a red light and other time green? What that means?
On Minepeon you might also have to edit the "/etc/udev/rules.d/01-miner.rules".
Don't forget to add the following lines if they do not already exist:
Oh..and you have to hot plug them. First start mining software, then plug them in.
Don't forget to add the following lines if they do not already exist:
Quote
# BXF
ATTRS{idVendor}=="198c", ATTRS{idProduct}=="b1f1", SUBSYSTEMS=="usb", ACTION=="add", MODE="0666", GROUP="minepeon"
ATTRS{idVendor}=="198c", ATTRS{idProduct}=="b1f1", SUBSYSTEMS=="usb", ACTION=="add", MODE="0666", GROUP="minepeon"
Oh..and you have to hot plug them. First start mining software, then plug them in.
And how do i do that, saw some other guy having trouble with it in the mac too, but he didnt add what command he used either.
Code:
sudo su
nano /etc/udev/rules.d/01-miner.rules
that line is already there.
On Minepeon you might also have to edit the "/etc/udev/rules.d/01-miner.rules".
Don't forget to add the following lines if they do not already exist:
Oh..and you have to hot plug them. First start mining software, then plug them in.
Don't forget to add the following lines if they do not already exist:
Quote
# BXF
ATTRS{idVendor}=="198c", ATTRS{idProduct}=="b1f1", SUBSYSTEMS=="usb", ACTION=="add", MODE="0666", GROUP="minepeon"
ATTRS{idVendor}=="198c", ATTRS{idProduct}=="b1f1", SUBSYSTEMS=="usb", ACTION=="add", MODE="0666", GROUP="minepeon"
Oh..and you have to hot plug them. First start mining software, then plug them in.
And how do i do that, saw some other guy having trouble with it in the mac too, but he didnt add what command he used either.
Code:
sudo su
nano /etc/udev/rules.d/01-miner.rules
On Minepeon you might also have to edit the "/etc/udev/rules.d/01-miner.rules".
Don't forget to add the following lines if they do not already exist:
Oh..and you have to hot plug them. First start mining software, then plug them in.
Don't forget to add the following lines if they do not already exist:
Quote
# BXF
ATTRS{idVendor}=="198c", ATTRS{idProduct}=="b1f1", SUBSYSTEMS=="usb", ACTION=="add", MODE="0666", GROUP="minepeon"
ATTRS{idVendor}=="198c", ATTRS{idProduct}=="b1f1", SUBSYSTEMS=="usb", ACTION=="add", MODE="0666", GROUP="minepeon"
Oh..and you have to hot plug them. First start mining software, then plug them in.
And how do i do that, saw some other guy having trouble with it in the mac too, but he didnt add what command he used either.
On Minepeon you might also have to edit the "/etc/udev/rules.d/01-miner.rules".
Don't forget to add the following lines if they do not already exist:
Oh..and you have to hot plug them. First start mining software, then plug them in.
Don't forget to add the following lines if they do not already exist:
Quote
# BXF
ATTRS{idVendor}=="198c", ATTRS{idProduct}=="b1f1", SUBSYSTEMS=="usb", ACTION=="add", MODE="0666", GROUP="minepeon"
ATTRS{idVendor}=="198c", ATTRS{idProduct}=="b1f1", SUBSYSTEMS=="usb", ACTION=="add", MODE="0666", GROUP="minepeon"
Oh..and you have to hot plug them. First start mining software, then plug them in.
They do work on a raspberry PI:
At least they work running cgminer 3.8.4 compiled with the correct drivers.
At least they work running cgminer 3.8.4 compiled with the correct drivers.
What OS for the rasp did you use (Raspbian, Pidora, RaspBMC or other)??
Did you update the firmware on the bi*fury's?
What USB hub do you use, and how much power does the ac adapter provide?
No, I did not change the firmware. It was as shipped in early december.
The screenshot was taken while running all those devices on a 49 Port USB HUB with a "cheap" ATX PSU (25A).
Unfortunately I have no more BI*Fury's anymore so I can not do further tests, sorry.
Triede that, didnt work.
They do work on a raspberry PI:
At least they work running cgminer 3.8.4 compiled with the correct drivers.
At least they work running cgminer 3.8.4 compiled with the correct drivers.
What OS for the rasp did you use (Raspbian, Pidora, RaspBMC or other)??
Did you update the firmware on the bi*fury's?
What USB hub do you use, and how much power does the ac adapter provide?
No, I did not change the firmware. It was as shipped in early december.
The screenshot was taken while running all those devices on a 49 Port USB HUB with a "cheap" ATX PSU (25A).
Unfortunately I have no more BI*Fury's anymore so I can not do further tests, sorry.
They do work on a raspberry PI:
At least they work running cgminer 3.8.4 compiled with the correct drivers.
At least they work running cgminer 3.8.4 compiled with the correct drivers.
What OS for the rasp did you use (Raspbian, Pidora, RaspBMC or other)??
Did you update the firmware on the bi*fury's?
What USB hub do you use, and how much power does the ac adapter provide?
They do work on a raspberry PI:
At least they work running cgminer 3.8.4 compiled with the correct drivers.
At least they work running cgminer 3.8.4 compiled with the correct drivers.
Still cant get my bi*fury's to run on raspberry... If its the same problem a week from now, im going to sell them again.
What a waste of money and time, and no support from sellers what so ever.
DONT BUY THESE
What a waste of money and time, and no support from sellers what so ever.
DONT BUY THESE
They won't run on a rasberry pi as the native usb ports do not give enougth power. The pi also does not detect USB 3 hubs which you pretty much need for these. Try hooking the pi up to a POWERED USB 2 hub and make sure it has plenty of power. Using a 48W USB3 hub i can only run 4 of these on one hub.
I am using a powered USB 2.0 Hub, with the red wire cut in the usb cable. Works just fine on windows 7. But no matter what i do, i cant get them to be detected on the rasp. Not even one.
I really think Felipeo or someone else from the store should come with a solution to this. Since there is no point in running them on a machine with a big psu, i end up using more power then im gaining from mining this way.
Still cant get my bi*fury's to run on raspberry... If its the same problem a week from now, im going to sell them again.
What a waste of money and time, and no support from sellers what so ever.
DONT BUY THESE
What a waste of money and time, and no support from sellers what so ever.
DONT BUY THESE
They won't run on a rasberry pi as the native usb ports do not give enougth power. The pi also does not detect USB 3 hubs which you pretty much need for these. Try hooking the pi up to a POWERED USB 2 hub and make sure it has plenty of power. Using a 48W USB3 hub i can only run 4 of these on one hub.
I'm having an interesting problem with one of these sticks. I had a DOA that when it arrive reported a temperature of 20C and did nothing, usually you plug these in and they report 50C before they start hashing. Sent it back and the replacement came and reports temperature as 100C before it begins hashing.
This has not been a problem as i have used the temp cut off option in cgminer to stop it throttling as they are all under cooling and never reach more then 55C. However now it is showing no more then 1.7GHs with cg miner started with cgminer.exe --drillbit-options ext:230:1:950 --temp-cutoff 110 on 3.10.0. Running on a USB3 hub and nothing has changed.
I am guessing i have had a chip go bad but thought i would post in case CGminer preemptively cuts off before the 110 limit, i have tried the different firmwares but get the same result. Anyone know what these use as a temperature sensor? and if there is a way to trick it back to normal range(i suspect my DOA was returned with a tricked temp sensor)?
Upgrade to the latest firmware.This has not been a problem as i have used the temp cut off option in cgminer to stop it throttling as they are all under cooling and never reach more then 55C. However now it is showing no more then 1.7GHs with cg miner started with cgminer.exe --drillbit-options ext:230:1:950 --temp-cutoff 110 on 3.10.0. Running on a USB3 hub and nothing has changed.
I am guessing i have had a chip go bad but thought i would post in case CGminer preemptively cuts off before the 110 limit, i have tried the different firmwares but get the same result. Anyone know what these use as a temperature sensor? and if there is a way to trick it back to normal range(i suspect my DOA was returned with a tricked temp sensor)?
cgminer also supports a target temperature for these:
--bxf-temp-target
It does not cut off, it throttles to the slowest possible speed if it's over the range.
Yep was on the latest firmware but buggered up my batch file using --temp-cutoff instead of --bxf-temp-target. Classical case of PEBKAC thanks for pointing me in the right direction
Anyone know what these use as a temperature sensor? and if there is a way to trick it back to normal range(i suspect my DOA was returned with a tricked temp sensor)?
The temperature sensor is a 330 Ohm (nominal value at 25C) NTC resistor, located between the 2 bitfury chips and big black inductor. It's a 0603 component, slightly larger than the 0402 caps around the bitfurys.
Still cant get my bi*fury's to run on raspberry... If its the same problem a week from now, im going to sell them again.
What a waste of money and time, and no support from sellers what so ever.
DONT BUY THESE
What a waste of money and time, and no support from sellers what so ever.
DONT BUY THESE
I'm having an interesting problem with one of these sticks. I had a DOA that when it arrive reported a temperature of 20C and did nothing, usually you plug these in and they report 50C before they start hashing. Sent it back and the replacement came and reports temperature as 100C before it begins hashing.
This has not been a problem as i have used the temp cut off option in cgminer to stop it throttling as they are all under cooling and never reach more then 55C. However now it is showing no more then 1.7GHs with cg miner started with cgminer.exe --drillbit-options ext:230:1:950 --temp-cutoff 110 on 3.10.0. Running on a USB3 hub and nothing has changed.
I am guessing i have had a chip go bad but thought i would post in case CGminer preemptively cuts off before the 110 limit, i have tried the different firmwares but get the same result. Anyone know what these use as a temperature sensor? and if there is a way to trick it back to normal range(i suspect my DOA was returned with a tricked temp sensor)?
Upgrade to the latest firmware.This has not been a problem as i have used the temp cut off option in cgminer to stop it throttling as they are all under cooling and never reach more then 55C. However now it is showing no more then 1.7GHs with cg miner started with cgminer.exe --drillbit-options ext:230:1:950 --temp-cutoff 110 on 3.10.0. Running on a USB3 hub and nothing has changed.
I am guessing i have had a chip go bad but thought i would post in case CGminer preemptively cuts off before the 110 limit, i have tried the different firmwares but get the same result. Anyone know what these use as a temperature sensor? and if there is a way to trick it back to normal range(i suspect my DOA was returned with a tricked temp sensor)?
cgminer also supports a target temperature for these:
--bxf-temp-target
It does not cut off, it throttles to the slowest possible speed if it's over the range.
I'm having an interesting problem with one of these sticks. I had a DOA that when it arrive reported a temperature of 20C and did nothing, usually you plug these in and they report 50C before they start hashing. Sent it back and the replacement came and reports temperature as 100C before it begins hashing.
This has not been a problem as i have used the temp cut off option in cgminer to stop it throttling as they are all under cooling and never reach more then 55C. However now it is showing no more then 1.7GHs with cg miner started with cgminer.exe --drillbit-options ext:230:1:950 --temp-cutoff 110 on 3.10.0. Running on a USB3 hub and nothing has changed.
I am guessing i have had a chip go bad but thought i would post in case CGminer preemptively cuts off before the 110 limit, i have tried the different firmwares but get the same result. Anyone know what these use as a temperature sensor? and if there is a way to trick it back to normal range(i suspect my DOA was returned with a tricked temp sensor)?
This has not been a problem as i have used the temp cut off option in cgminer to stop it throttling as they are all under cooling and never reach more then 55C. However now it is showing no more then 1.7GHs with cg miner started with cgminer.exe --drillbit-options ext:230:1:950 --temp-cutoff 110 on 3.10.0. Running on a USB3 hub and nothing has changed.
I am guessing i have had a chip go bad but thought i would post in case CGminer preemptively cuts off before the 110 limit, i have tried the different firmwares but get the same result. Anyone know what these use as a temperature sensor? and if there is a way to trick it back to normal range(i suspect my DOA was returned with a tricked temp sensor)?
Hello All
After installing new firmware I was able to get the Bi*Furys to work using Zadig on CGminer.
This will show the mines under USB on device manger.
As I have been using BFGminer the Bi*Furys were not recognised even when I used the FDTI drivers still no luck.
I found this link on another thread, and installed the drivers, and windows did recognise it and gave it a com number, now I am able to use the Bi*Furys on BFGminer.
Hope this help anyone.
Link below for drivers.
https://www.dropbox.com/s/jpqcvsnx629ns4s/Windows-Mining-Infs.zip
After installing new firmware I was able to get the Bi*Furys to work using Zadig on CGminer.
This will show the mines under USB on device manger.
As I have been using BFGminer the Bi*Furys were not recognised even when I used the FDTI drivers still no luck.
I found this link on another thread, and installed the drivers, and windows did recognise it and gave it a com number, now I am able to use the Bi*Furys on BFGminer.
Hope this help anyone.
Link below for drivers.
https://www.dropbox.com/s/jpqcvsnx629ns4s/Windows-Mining-Infs.zip
Jump to: