|
micax1
|
 |
December 05, 2013, 04:49:15 AM |
|
Run bfgminer with -S opencl:auto
Already find it, But thank you! appreciate it! |
|
|
|
|
|
|
|
Be very wary of relying on JavaScript for security on crypto sites. The site can change the JavaScript at any time unless you take unusual precautions, and browsers are not generally known for their airtight security.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
evolvia31
Member
 Offline
Activity: 74
Merit: 10
|
|
December 05, 2013, 06:07:42 AM
Last edit: December 05, 2013, 08:31:14 AM by evolvia31 |
|
Try to enter "erupter:/dev/ttyUSBn" .Where n is the number of USB listed in /dev/ directory.
I didn't have any entry on the /dev list which begins ttyUSB. When I plug the usb erupter block the only new entry in the /dev are: cuaU0 cuaU0.init cuaU0.lock ttyU0 ttyU0.init ttyU0.lock BFGMiner is probably broken on FreeBSD. Any FreeBSD developers who can help out?
Have you an idea if i can help you to debug ? can i launch bfgminer with a high verbose mode to see where is the problem ? Compilation works fine with some errors CC bfgminer-miner.o
In file included from ./sha2.h:39,
from miner.c:59:
./miner.h:61:1: warning: "alloca" redefined
In file included from miner.c:27:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
miner.c: In function 'raise_fd_limits':
miner.c:10835: warning: comparison is always true due to limited range of data type
CC bfgminer-deviceapi.o
In file included from deviceapi.h:10,
from deviceapi.c:28:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/uthash.h:29,
from deviceapi.h:8,
from deviceapi.c:28:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-util.o
In file included from deviceapi.h:10,
from lowl-vcom.h:9,
from util.c:56:
miner.h:61:1: warning: "alloca" redefined
In file included from util.c:19:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-sha2.o
In file included from sha2.h:39,
from sha2.c:40:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from miner.h:27,
from sha2.h:39,
from sha2.c:40:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-api.o
In file included from deviceapi.h:10,
from api.c:29:
miner.h:61:1: warning: "alloca" redefined
In file included from api.c:21:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-logging.o
In file included from logging.c:19:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from util.h:22,
from logging.h:33,
from logging.c:18:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-proxy.o
In file included from deviceapi.h:10,
from driver-proxy.c:18:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/uthash.h:29,
from driver-proxy.c:16:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-httpsrv.o
CC bfgminer-driver-getwork.o
In file included from deviceapi.h:10,
from driver-getwork.c:28:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from driver-getwork.c:24:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-stratum.o
In file included from deviceapi.h:10,
from driver-stratum.c:29:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from driver-stratum.c:27:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
driver-stratum.c:648:2: warning: no newline at end of file
CC bfgminer-lowl-vcom.o
In file included from lowl-vcom.c:32:
miner.h:61:1: warning: "alloca" redefined
In file included from lowl-vcom.c:19:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-lowl-usb.o
In file included from lowl-usb.c:23:
miner.h:61:1: warning: "alloca" redefined
In file included from lowl-usb.c:15:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-binloader.o
In file included from deviceapi.h:10,
from binloader.c:19:
miner.h:61:1: warning: "alloca" redefined
In file included from binloader.c:16:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-lowlevel.o
In file included from lowlevel.c:21:
miner.h:61:1: warning: "alloca" redefined
In file included from lowlevel.c:13:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-dynclock.o
In file included from dynclock.c:17:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from miner.h:27,
from dynclock.c:17:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-bitforce.o
In file included from deviceapi.h:10,
from driver-bitforce.c:24:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/uthash.h:29,
from deviceapi.h:8,
from driver-bitforce.c:24:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-bigpic.o
In file included from driver-bigpic.c:20:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from miner.h:27,
from driver-bigpic.c:20:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-twinfury.o
In file included from driver-twinfury.c:16:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from miner.h:27,
from driver-twinfury.c:16:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-icarus.o
In file included from driver-icarus.c:33:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from miner.h:27,
from driver-icarus.c:33:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-cairnsmore.o
In file included from icarus-common.h:20,
from driver-cairnsmore.c:17:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from miner.h:27,
from icarus-common.h:20,
from driver-cairnsmore.c:17:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-erupter.o
In file included from driver-erupter.c:14:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from miner.h:27,
from driver-erupter.c:14:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-avalon.o
In file included from deviceapi.h:10,
from driver-avalon.c:38:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/uthash.h:29,
from deviceapi.h:8,
from driver-avalon.c:38:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-hexdump.o
CC bfgminer-driver-klondike.o
In file included from deviceapi.h:10,
from driver-klondike.c:30:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/uthash.h:29,
from deviceapi.h:8,
from driver-klondike.c:30:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-modminer.o
In file included from driver-modminer.c:24:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from util.h:22,
from binloader.h:7,
from driver-modminer.c:20:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-x6500.o
In file included from deviceapi.h:10,
from driver-x6500.c:23:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from util.h:22,
from binloader.h:7,
from driver-x6500.c:21:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-ft232r.o
In file included from ft232r.c:23:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/uthash.h:29,
from lowlevel.h:8,
from ft232r.h:18,
from ft232r.c:20:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-jtag.o
In file included from jtag.c:22:
miner.h:61:1: warning: "alloca" redefined
In file included from jtag.c:16:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-ztex.o
In file included from driver-ztex.c:22:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from miner.h:27,
from driver-ztex.c:22:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-libztex.o
In file included from deviceapi.h:10,
from libztex.c:36:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from util.h:22,
from binloader.h:7,
from libztex.c:34:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-bifury.o
In file included from deviceapi.h:10,
from driver-bifury.c:21:
miner.h:61:1: warning: "alloca" redefined
In file included from driver-bifury.c:15:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-bitfury.o
In file included from driver-bitfury.c:28:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from miner.h:27,
from driver-bitfury.c:28:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-libbitfury.o
In file included from libbitfury.c:34:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/jansson.h:12,
from util.h:22,
from logging.h:33,
from libbitfury.c:33:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-spidevc.o
CC bfgminer-driver-littlefury.o
In file included from deviceapi.h:10,
from driver-littlefury.c:17:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/uthash.h:29,
from deviceapi.h:8,
from driver-littlefury.c:17:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
CC bfgminer-driver-hashbuster2.o
In file included from deviceapi.h:10,
from driver-hashbuster2.c:18:
miner.h:61:1: warning: "alloca" redefined
In file included from /usr/local/include/uthash.h:29,
from deviceapi.h:8,
from driver-hashbuster2.c:18:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
cd libblkmaker && make
CCLD bfgminer
CC bitforce-firmware-flash.o
CCLD bitforce-firmware-flash
CC api-example.o
CCLD bfgminer-rpc
I try to compile bfgminer with CPU and GPU mining and it works fine, CPU mining works and GPU mining works too. But it never detect any usb erupter [EDIT]: I try with hub with external power, and i have a strange result. If i run bfgminer without command "-S erupter:all" bfgminer launches, but if i launch it with this command bfgminer stay on the first display version and after one hour nothing else. Ohter test, if i run bfgminer without command "-S erupter:all", and i go to manage device, if i put "erupter:/dev/cuaU0" or "erupter:/dev/ttyU0", i have the message : "No new devices found". But if i put this command "erupter:all", i have no response, program is freezing, i must kill task to exit it. |
|
|
|
|
|
rupy
|
|
December 05, 2013, 08:57:56 AM |
|
Thanks but I had tried with 3.8.0 as well ....  no luck either. The output posted was from 3.8.0 as well, I got the screenshot mixed up, so sorry about that. However, both screen output from either versions are the same, it shows the BPM0 with zero hash and device not able to be detected. I got the driver installed correctly for bfgminer and it is displayed in the control panel correctly. I followed the instructions given. I have even tried cgminer installation setup as well but nothing happens either. I hope that does not means it is DOA. Another thing is the LED does not light up when I insert into the USB ports as well. I have to start bfg then pull my redfury out of the USB, put it back in, then manually add it with bigpic:all from inside bfg. |
BANKBOOK GWT Wallet & no-FIAT Billing API
|
|
|
fatkream
Newbie
Offline
Activity: 7
Merit: 0
|
|
December 05, 2013, 10:19:01 AM |
|
Thanks but I had tried with 3.8.0 as well .... no luck either. The output posted was from 3.8.0 as well, I got the screenshot mixed up, so sorry about that. However, both screen output from either versions are the same, it shows the BPM0 with zero hash and device not able to be detected. I got the driver installed correctly for bfgminer and it is displayed in the control panel correctly. I followed the instructions given. I have even tried cgminer installation setup as well but nothing happens either. I hope that does not means it is DOA. Another thing is the LED does not light up when I insert into the USB ports as well. I have to start bfg then pull my redfury out of the USB, put it back in, then manually add it with bigpic:all from inside bfg. Okay. Thanks. I am willingly to try anything |
|
|
|
|
|
stef942
|
|
December 05, 2013, 10:19:57 AM |
|
Hello, is there a special parameter to add to detect GPU ? i try to run an hd5970 with bfgminer 3.8.0 under win7 and the card is not detected. i cant detect it in the menu (manage device > + >"auto" detect CPU and "all" said no device detected or something like that)  |
|
|
|
|
|
Mudbankkeith
|
|
December 05, 2013, 11:10:46 AM |
|
Hello, is there a special parameter to add to detect GPU ? i try to run an hd5970 with bfgminer 3.8.0 under win7 and the card is not detected. i cant detect it in the menu (manage device > + >"auto" detect CPU and "all" said no device detected or something like that) Hi. after last update my OCL devices are not automatically discovered. Please advise.
Run bfgminer with -S opencl:auto |
BTc donations welcome:- 13c2KuzWCaWFTXF171Zn1HrKhMYARPKv97
|
|
|
|
stef942
|
|
December 05, 2013, 11:36:00 AM
Last edit: December 05, 2013, 12:25:08 PM by stef942 |
|
doesnt work : bfgminer version 3.8.0 - Started: [2013-12-05 12:22:37] - [ 0 days 00:05:19]
[M]anage devices [P]ool management [S]ettings [D]isplay options [H]elp [Q]uit
Connected to stratum01.hashco.ws diff 0 with stratum as user xxxx
Block: ...1c268283 #844564 Diff:33 (242.2Mh/s) Started: [12:27:56]
ST:2 F:0 NB:12 AS:0 BW:[ 26/ 3 B/s] E:0.00 I: 2.51mBTC/hr BS:0
0 37.0C | 0.02/ 0.02/53.89Mh/s | A:4 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
OCL 0: 37.5C | 0.01/ 0.01/30.86Mh/s | A:2 R:0+0(none) HW:0/none
OCL 1: 36.5C | 0.01/ 0.01/26.86Mh/s | A:2 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
[2013-12-05 12:27:51] Accepted 0511adce OCL 0 Diff 0/0
[2013-12-05 12:27:52] Accepted 036032e9 OCL 1 Diff 0/0
[2013-12-05 12:27:56] Stratum from pool 0 detected new block
thats what i get when i go to [M] >> + (add device), it says no new device found bfgminer version 3.8.0 - Started: [2013-12-05 12:22:37] - [ 0 days 00:07:55]
[M]anage devices [P]ool management [S]ettings [D]isplay options [H]elp [Q]uit
Connected to stratum01.hashco.ws diff 0 with stratum as user xxxxx
Block: ...d3a8c94840a96fd6 Diff:2 (19.77Mh/s) Started: [12:30:27]]
ST:2 F:1 NB:30 AS:0 BW:[ 36/ 3 B/s] E:0.00 I:20.81mBTC/hr BS:0
0 39.0C | 0.03/ 0.02/36.42Mh/s | A:4 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
OCL 0: 39.5C | 0.01/ 0.01/19.79Mh/s | A:2 R:0+0(none) HW:0/none
OCL 1: 38.5C | 0.01/ 0.01/18.07Mh/s | A:2 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
Select processor to manage using up/down arrow keys
OCL 0 : 39.0C | 0.01/ 0.01/21.20Mh/s | A:2 R:0+0(none) HW:0/none
Kernel: scrypt
I:d8 F: 90% (1543 RPM) E: 735 MHz M: 1010 MHz V: 1.050V A: 78% P: 0%
Last initialised: [2013-12-05 12:23:19]
Thread 0: 13.1 Kh/s Enabled ALIVE
[D]isable [I]ntensity [R]estart GPU [C]hange settings
[Slash] Find processor [Plus] Add device(s) [Enter] Close device manager
No new devices found ouh forget it, its working now, im a noob  |
|
|
|
|
|
Beave162
|
|
December 06, 2013, 06:32:49 AM |
|
Why is my bfgminer closing immediately after I open it? I have been using it for months and didn't have this problem...
|
YaCoin: YL5kf54wPPXKsXd5T18xCaNkyUsS1DgY7z
BitCoin: 14PFbLyUdTyxZg3V8hnvj5VXkx3dhthmDj
|
|
|
evolvia31
Member
Offline
Activity: 74
Merit: 10
|
|
December 06, 2013, 07:13:56 AM |
|
you use a config file or command line to launch it ?
generally, that's a wrong parameter in command line or a wrong syntax in config file which generate this result.
|
|
|
|
|
|
BRADLEYPLOOF
|
|
December 06, 2013, 12:47:50 PM |
|
I'm trying to use block erupters on windows xp, but it only allows me to use 1 block erupter and says that the others can't be found, or causes the exclamation point in the triangle when i view the device manage. I've uninstalled and reinstalled the us-uart driver, but to no avail. Is there something I'm missing?
|
|
|
|
|
|
HellDiverUK
|
|
December 06, 2013, 12:53:18 PM |
|
Is there something I'm missing?
An OS that doesn't suck when it comes to USB support. |
|
|
|
|
evolvia31
Member
Offline
Activity: 74
Merit: 10
|
|
December 06, 2013, 02:02:41 PM |
|
otherwise, usb block erupter need lots of watt  , you use hub with external power or directly usb motherboard. I think after one usb erupter, you must use a hub with external power to have such as power. |
|
|
|
|
|
BRADLEYPLOOF
|
|
December 06, 2013, 02:08:48 PM |
|
otherwise, usb block erupter need lots of watt , you use hub with external power or directly usb motherboard. I think after one usb erupter, you must use a hub with external power to have such as power. I've got an external powered usb hub. I can plug in 1 erupter and it's find, shows up as COM4. Then, when I plug in a second one into the usb hub, it says "installing device" then errors our saying "device may not have installed properly", and then the COM4 has the ! in a triangle. I know the hub works on my windows 7 machine. I can also plug in 2 erupters directly into the box and they show up as COM4 and COM21, but when I plug in the hub and try to attach another one, it boots COM4 and gives me that ! triangle. I mostly use that computer for old, fun, XP games...just thought I'd try it out though... |
|
|
|
|
|
Mudbankkeith
|
|
December 06, 2013, 02:15:08 PM |
|
otherwise, usb block erupter need lots of watt , you use hub with external power or directly usb motherboard. I think after one usb erupter, you must use a hub with external power to have such as power. I've got an external powered usb hub. I can plug in 1 erupter and it's find, shows up as COM4. Then, when I plug in a second one into the usb hub, it says "installing device" then errors our saying "device may not have installed properly", and then the COM4 has the ! in a triangle. I know the hub works on my windows 7 machine. I can also plug in 2 erupters directly into the box and they show up as COM4 and COM21, but when I plug in the hub and try to attach another one, it boots COM4 and gives me that ! triangle. I mostly use that computer for old, fun, XP games...just thought I'd try it out though... You need USB2 ports on your PC USB1 is to slow and USB3 sometimes has problems. |
BTc donations welcome:- 13c2KuzWCaWFTXF171Zn1HrKhMYARPKv97
|
|
|
|
BRADLEYPLOOF
|
|
December 06, 2013, 03:43:46 PM |
|
otherwise, usb block erupter need lots of watt , you use hub with external power or directly usb motherboard. I think after one usb erupter, you must use a hub with external power to have such as power. I've got an external powered usb hub. I can plug in 1 erupter and it's find, shows up as COM4. Then, when I plug in a second one into the usb hub, it says "installing device" then errors our saying "device may not have installed properly", and then the COM4 has the ! in a triangle. I know the hub works on my windows 7 machine. I can also plug in 2 erupters directly into the box and they show up as COM4 and COM21, but when I plug in the hub and try to attach another one, it boots COM4 and gives me that ! triangle. I mostly use that computer for old, fun, XP games...just thought I'd try it out though... You need USB2 ports on your PC USB1 is to slow and USB3 sometimes has problems. I do have a USB2 port on it, but I don't know which one it is...is there an easy way to tell? I can see the hub controller for it in the device manager, just don't know which of the 7 ports is actually it |
|
|
|
|
|
Mudbankkeith
|
|
December 06, 2013, 03:51:11 PM |
|
otherwise, usb block erupter need lots of watt , you use hub with external power or directly usb motherboard. I think after one usb erupter, you must use a hub with external power to have such as power. I've got an external powered usb hub. I can plug in 1 erupter and it's find, shows up as COM4. Then, when I plug in a second one into the usb hub, it says "installing device" then errors our saying "device may not have installed properly", and then the COM4 has the ! in a triangle. I know the hub works on my windows 7 machine. I can also plug in 2 erupters directly into the box and they show up as COM4 and COM21, but when I plug in the hub and try to attach another one, it boots COM4 and gives me that ! triangle. I mostly use that computer for old, fun, XP games...just thought I'd try it out though... You need USB2 ports on your PC USB1 is to slow and USB3 sometimes has problems. I do have a USB2 port on it, but I don't know which one it is...is there an easy way to tell? I can see the hub controller for it in the device manager, just don't know which of the 7 ports is actually it Traditionally usb1 "black"..............usb2 "white"................usb3 "blue" But device manager should indicate which port you are connecting when you plug in a stick. |
BTc donations welcome:- 13c2KuzWCaWFTXF171Zn1HrKhMYARPKv97
|
|
|
|
Xer0
|
|
December 06, 2013, 04:50:38 PM |
|
Seems I'm getting a Nanofury to replace a dead Bluefury. Anything I need to be aware of as regards getting the Nanofury working on BFGMiner on Linux (or indeed OpenWRT)?
You'll have to build hidapi for OpenWrt and recompile BFGMiner to use it. is this a git-source-and-cross-compile task or does it require intensive tinkering? |
|
|
|
|
Luke-Jr (OP)
Legendary
Offline
Activity: 2576
Merit: 1186
|
|
December 06, 2013, 04:56:00 PM |
|
Seems I'm getting a Nanofury to replace a dead Bluefury. Anything I need to be aware of as regards getting the Nanofury working on BFGMiner on Linux (or indeed OpenWRT)?
You'll have to build hidapi for OpenWrt and recompile BFGMiner to use it. is this a git-source-and-cross-compile task or does it require intensive tinkering? It requires writing code. |
|
|
|
|
sly5am
|
|
December 07, 2013, 03:00:34 AM |
|
Why is my bfgminer closing immediately after I open it? I have been using it for months and didn't have this problem...
Same problem here.. BFL gear working fine with version 3.6.0 bfgminer, as soon as I upgraded to 3.8.0 the program opens then immediately closes and doesn't run. Same OS and environment, Win 7. hope there is a fix in the newer version. |
|
|
|
Zich
Legendary
Offline
Activity: 1190
Merit: 1000
|
|
December 07, 2013, 11:30:38 AM |
|
Seems I'm getting a Nanofury to replace a dead Bluefury. Anything I need to be aware of as regards getting the Nanofury working on BFGMiner on Linux (or indeed OpenWRT)?
You'll have to build hidapi for OpenWrt and recompile BFGMiner to use it. Cheers Luke-Jr. I think I'll stick to the RPi then.  I hear there are significant problems with Nanofury on the RPi's buggy USB stack... I plan to be looking into this in the upcoming weeks, but it may be a hardware issue I can't workaround. Good news thanks to derjanb Working fine here after hours of trying... At least I get ~2.3 GH/s out of the Nanofury. I'm using bfgminer 3.8.0 (latest git version) and all you have to do (after compiling) is to enforce the USB 2.0 low speed mode to make the USB communication stable. Note: this will also limit the network speed of your Raspi! The slowdown can be achieved by putting dwc_otg.speed=1 into /boot/cmdline.txt. Note: all statements need to be at one line. See this page for more infomation: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=53832#sig411106 (the last section at the bottom. Question: what does NFY 0: Frequency drop over 50% detected, reinitialising mean? I see a lot of these messages. |
|
|
|
|
|
