Pages:
Author

Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 82. (Read 1193218 times)

hero member
Activity: 868
Merit: 1000
otherwise, usb block erupter need lots of watt Smiley, 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.
hero member
Activity: 520
Merit: 500
otherwise, usb block erupter need lots of watt Smiley, 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
hero member
Activity: 868
Merit: 1000
otherwise, usb block erupter need lots of watt Smiley, 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.
hero member
Activity: 520
Merit: 500
otherwise, usb block erupter need lots of watt Smiley, 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...
member
Activity: 74
Merit: 10
otherwise, usb block erupter need lots of watt Smiley, 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.
hero member
Activity: 1246
Merit: 501
Is there something I'm missing?

An OS that doesn't suck when it comes to USB support.
hero member
Activity: 520
Merit: 500
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?
member
Activity: 74
Merit: 10
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.
hero member
Activity: 809
Merit: 501
Why is my bfgminer closing immediately after I open it?  I have been using it for months and didn't have this problem...
full member
Activity: 181
Merit: 100
doesnt work :

Code:
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

Code:
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  Grin




hero member
Activity: 868
Merit: 1000
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)  Huh


Hi. after last update my OCL devices are not automatically discovered. Please advise.

Run bfgminer with -S opencl:auto
full member
Activity: 181
Merit: 100
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)  Huh
newbie
Activity: 7
Merit: 0
Thanks but I had tried with 3.8.0 as well ....  Embarrassed 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
hero member
Activity: 725
Merit: 503
Thanks but I had tried with 3.8.0 as well ....  Embarrassed 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.
member
Activity: 74
Merit: 10
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

Code:
 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.
hero member
Activity: 708
Merit: 502

Run bfgminer with -S opencl:auto

Already find it, But thank you! appreciate it!
newbie
Activity: 19
Merit: 0
Finally managed to compile a version of bfgminer which supports CPU mining. Trying to mine LTC via scrypt. This is the command I use.

Code:
bfgminer --scrypt -S noauto -S cpu:auto -t 32 -E 1 -s 1 -o stratum+tcp://global.wemineltc.com:3333 ....

This is the result I get. But don't seem to be hashing though. Am I missing something?

https://i.imgur.com/DOOfhA0.jpg

[2013-12-05 11:36:35] Started at [2013-12-05 11:28:50]
[2013-12-05 11:36:35] Pool: stratum+tcp://global.wemineltc.com:3333

[2013-12-05 11:36:35] CPU hasher algorithm used: scrypt
[2013-12-05 11:36:35] Runtime: 0 hrs : 7 mins : 45 secs
[2013-12-05 11:36:35] Average hashrate: 0.0 Megahash/s
[2013-12-05 11:36:35] Solved blocks: 0
[2013-12-05 11:36:35] Best share difficulty: 0
[2013-12-05 11:36:35] Share submissions: 0
[2013-12-05 11:36:35] Accepted shares: 0
[2013-12-05 11:36:35] Rejected shares: 0 + 0 stale (nan%)
[2013-12-05 11:36:35] Accepted difficulty shares: 0
[2013-12-05 11:36:36] Rejected difficulty shares: 0
[2013-12-05 11:36:36] Hardware errors: 1
[2013-12-05 11:36:36] Network transfer:   9.5 /   1.1 kB  ( 20.6 /   2.4  B/s)

[2013-12-05 11:36:36] Efficiency (accepted shares * difficulty / 2 KB): 0.00

[2013-12-05 11:36:36] Utility (accepted shares / min): 0.00/min

[2013-12-05 11:36:36] Unable to get work from server occasions: 0

[2013-12-05 11:36:36] Work items generated locally: 548
[2013-12-05 11:36:36] Submitting work remotely delay occasions: 0

[2013-12-05 11:36:36] New blocks detected on network: 4
legendary
Activity: 2576
Merit: 1186
BFGMiner is probably broken on FreeBSD. Any FreeBSD developers who can help out?
member
Activity: 122
Merit: 10
Try to enter "erupter:/dev/ttyUSBn" .Where n is the number of USB listed in /dev/ directory.
member
Activity: 74
Merit: 10
Hi all,
I'm newbie here.

I have a problem with my config.


I'm running Under FreeBSD 8.x

When i run "./configure" all is right i have this output:
Quote
------------------------------------------------------------------------
bfgminer 3.8.0 configuration options summary
------------------------------------------------------------------------

  CFLAGS...............: -I/usr/local/include/ncurses -I/usr/local/include -pthread -g -O2 -I/usr/local/include -pthread -Ilibblkmaker
  LDFLAGS..............: -pthread -Llibblkmaker/.libs -Wl,-rpath,\$$ORIGIN/libblkmaker/.libs,-zorigin -lpthread -L/usr/local/lib -lcurl -L/usr/local/lib -ljansson -L/usr/local/lib -rpath /usr/local/lib -lncurses -ltinfo -lm -lusb -lblkmaker_jansson-0.1 -lblkmaker-0.1
  Installatio[Suspicious link removed]efix..: /usr/local

  Enabled..Drivers.....: avalon bifury bigpic bitforce bitfury_gpio cairnsmore erupter hashbuster2 icarus klondike littlefury modminer proxy proxy:getwork proxy:stratum twinfury x6500 ztex
  Disabled.Drivers.....: bfsb cpu hashbuster knc metabank nanofury opencl
    To enable nanofury, install hidapi
    To enable hashbuster, install hidapi
  Enabled..Algorithms..: SHA256d
  Disabled.Algorithms..: scrypt
  Enabled..Options.....: ncurses5
  Disabled.Options.....:


When i run "make" all is right too, i have this output:
Quote
cd libblkmaker && make
  CCLD     bfgminer
  CC       bitforce-firmware-flash.o
  CCLD     bitforce-firmware-flash
  CC       api-example.o
  CCLD     bfgminer-rpc


but when i launch bfgminer, it didn't detect my usb erupter block

When i connect the usb erupter block i have this message:
Quote
Dec  4 12:01:47 xxxxx kernel: ugen5.2: at usbus5
Dec  4 12:01:47 xxxxx kernel: uslcom0: on usbus5
and in the /dev i have this:
Quote
cuaU0
cuaU0.init
cuaU0.lock
ttyU0
ttyU0.init
ttyU0.lock

Anyone can help me??
When bfgminer is launch if i push "m" and "+", if i put "erupter:/dev/ttyU0" or "erupter:/dev/cuaU0" i have this message:
Quote
(no devices)
[Plus] Add device(s)  [Enter] Close device manager
No new devices found


Erupter works fine on Windows.

Thanks to your help

Pages:
Jump to: