OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB

[justworks]

Hello, if anyone could help me figure this out it would be great!

I have BFGminer on my wr703n (openWRT) running a few antminers.

The thing is, if I run the command from an ssh session everything is ok, but if I put the same command into the luci startup so it would run automatically on each boot BFGminer eats 100% of the routers CPU and becomes unstable after a few hours, hardware errors and GH/s drop.

The command is:

bfgminer -S antminer:all -o mypool -u myusername -p x --set-device antminer:clock=x0981

So again, through a ssh session, the CPU usage is 0 to 1%, as a startup command its 99 to 100%.


The main point of the wr703n miner was so my computer does not have to be on, but I am not there yet

Try --syslog ? Or -T and pipe output to /dev/null

-T worked like a charm! Thankyou very much, for the solution and a super fast response

[pauljbl]

Anyone having problem with gridseed on nwools fork bfgminer it works great but after so long it stops submitting shares and I have to restart it again.

Doesn't seem to do it on dbartle fork

This is on a pi with Debian

[justworks]

did anyone compile a version of bfgminer with support for scrypt and the usb dualminer for openwrt and was maybe willing to share it?

I am having trouble compiling it myself, not that experienced in that area yet... :/

EDIT: for brcm47xx

[amix]

did anyone compile a version of bfgminer with support for scrypt and the usb dualminer for openwrt and was maybe willing to share it?

I am having trouble compiling it myself, not that experienced in that area yet... :/

EDIT: for brcm47xx

try this it might help - its going to be easter weekend project
http://wiki.openwrt.org/doc/howto/bitcoinmining

[BRADLEYPLOOF]

Any idea about creating a version to support this: http://zeusminer.com/product/zeus-scrypt-asic-miner-300khs/

I'd like to get one to play with and help out.  If I can get a developer version of it nwools can ssh into my raspberry pi and play with it...gigadee

[justworks]

did anyone compile a version of bfgminer with support for scrypt and the usb dualminer for openwrt and was maybe willing to share it?

I am having trouble compiling it myself, not that experienced in that area yet... :/

EDIT: for brcm47xx

try this it might help - its going to be easter weekend project
http://wiki.openwrt.org/doc/howto/bitcoinmining

I got bitcoin minig working on openwrt already and it works great. But for the gridseed dualminer I would need a build that has scrypt and the gridseed drivers integrated. And here I am having problems...

[li_gangyi]

Anyone having problem with gridseed on nwools fork bfgminer it works great but after so long it stops submitting shares and I have to restart it again.

Doesn't seem to do it on dbartle fork

This is on a pi with Debian

I have the same setup with you and am experiencing the same issue.

I build the BFGminer myself. 10 gridseeds on the PI. After awhile (seemingly random time) one of them will stop submitting shares and I have to restart BFGminer for it to work again.

[poopypants]

Anyone having problem with gridseed on nwools fork bfgminer it works great but after so long it stops submitting shares and I have to restart it again.

Doesn't seem to do it on dbartle fork

This is on a pi with Debian

I have the same setup with you and am experiencing the same issue.

I build the BFGminer myself. 10 gridseeds on the PI. After awhile (seemingly random time) one of them will stop submitting shares and I have to restart BFGminer for it to work again.

Same problem... I stopped using bfgminer because of it until it gets sorted.  Using the bfgminer-gridseed-clean branch.

[chirale]

Pushed a "gridseed" branch to the main BFGMiner git based on nwoolls's code.
I'm not sure how these are supposed to perform, but I get some inconsistent results in benchmark mode:

Code:

DMU 0:       |  36.8/ 68.2/ 41.7kh/s | A: 28 R:0+0(none) HW:0/none
GSD 0:       |  0.73/ 1.27/ 0.17Mh/s | A:112 R:0+0(none) HW:8/none

How's it work for others who have been using them in production?

I've been using it for a while with my gridseeds with no issues but with the dualminers every time it hits a HW error it seems to stop submitting shares to the pool. I could go to manage devices disable processor and reenable and it submits shares for a bit then stops.  I've compiled it twice and still the same both times.

That's why I lovered Dualminer frequency to 800, but this only makes babysitting Dualminers easier, not eliminating it.

I've tried it clocked at 850 and default.  It does run a little longer but still stops.

Same with me. GSD round miners working great, but dualminer "stick", often stop submitting shares to the pool.
thank you

[klintay]

using bfgminer 3.10.0 with the Gridseed Blade and here are the results:



It started out hashing like two 5 chip miners but then the average long term speed increased slowly. However the other two speeds (5 second  average etc) are still showing incorrect speed. I logged into the mining pool and the speed seems to be correct there.

0.2 btc bounty for a version of bfgminer that shows the correct speed. 

[Luke-Jr]

using bfgminer 3.10.0 with the Gridseed Blade and here are the results:

BFGMiner 3.10.0 doesn't support any scrypt ASICs at all.
So, what are these results with?

[justworks]

I have been using this version on windows for the last week and everything works fine. I currently have two gridseeds on it.


The first post in this link, version 3.99.0:
http://cryptomining-blog.com/tag/gridseed-bfgminer/

[klintay]

using bfgminer 3.10.0 with the Gridseed Blade and here are the results:

BFGMiner 3.10.0 doesn't support any scrypt ASICs at all.
So, what are these results with?

sorry its a modified version of bfgminer 3.10.0 from https://bitcointalk.org/index.php?topic=482352

it's the bastard love child of your genius 

[maxihatop]

Hi,

Please help.

I downloaded bfgminer from Git, and built it successfully on FreeBSD 9.1
There was minor problem with configure.ac (path to uthash headers), but I built it successfully.

But, I see, the new configure does not support anymore bflsc driver,
so I unable to run configure with this option:

./configure --enable-bflsc

And, as result, I cannot use bfgminer with Butterfly SC 60 device.

Can you return this driver into package?

PS:
I tried to checkout old commit from Oct, 18, dfa849ab62f886d448002453c9434f928038ae24.
this commit contains driver, but unfortunately, FreeBSD does not have libusb, and configure stops at:
configure: error: ./configure failed for compat/libusb-1.0

Thanks,
Oleg

[Luke-Jr]

I downloaded bfgminer from Git, and built it successfully on FreeBSD 9.1
There was minor problem with configure.ac (path to uthash headers), but I built it successfully.

What about uthash?

But, I see, the new configure does not support anymore bflsc driver,
so I unable to run configure with this option:

./configure --enable-bflsc

There never was a "bflsc" driver.

And, as result, I cannot use bfgminer with Butterfly SC 60 device.

Why not? The standard "bitforce" driver should work fine.

PS:
I tried to checkout old commit from Oct, 18, dfa849ab62f886d448002453c9434f928038ae24.
this commit contains driver, but unfortunately, FreeBSD does not have libusb, and configure stops at:
configure: error: ./configure failed for compat/libusb-1.0

This commit is from the cgminer fork, not BFGMiner.

[maxihatop]

What about uthash?

I don't know why, but configure does not search uthash headers in the /usr/local/include.

I modified configure.ac, and wrote direct path to include files (added part is bold):
#include </usr/local/include/utlist.h>
#include </usr/local/include/uthash.h>

Thereafter, configure runs OK.

The standard "bitforce" driver should work fine.

Sorry, but something wrong. see terminal output:

# lsusb
Bus /dev/usb Device /dev/ugen2.2: ID 0403:6014 Future Technology Devices International, Ltd
Bus /dev/usb Device /dev/ugen2.1: ID 0000:0000
Bus /dev/usb Device /dev/ugen1.1: ID 0000:0000
Bus /dev/usb Device /dev/ugen0.1: ID 0000:0000

# ls -la /dev/ugen2.2
lrwxr-xr-x  1 root  wheel  9 Apr 19 20:27 /dev/ugen2.2 -> usb/2.2.0
# ls -la /dev/usb/2.2.0
crw-------  1 root  operator    0, 120 Apr 19 20:27 /dev/usb/2.2.0


# ./bfgminer/bfgminer -o pool.xxx.com:0000 -u username -p secret -D -T --verbose -S all
 [2014-04-19 20:32:46] setrlimit: Changed soft fd limit from 11095 to 1024 (FD_SETSIZE=1024; hard limit=11095)         
 [2014-04-19 20:32:46] Started bfgminer 3.99.0
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:002:002 (path=(null), vid=0403, pid=6014, manuf=FTDI, prod=BitFORCE SHA256 SC, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:002:001 (path=(null), vid=0000, pid=0000, manuf=CMDTECH, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=0000, pid=0000, manuf=SiS, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:000:001 (path=(null), vid=0000, pid=0000, manuf=SiS, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found ft232r device at usb:002:002 (path=(null), vid=0403, pid=6014, manuf=FTDI, prod=BitFORCE SHA256 SC, serial=(null))
 [2014-04-19 20:32:46] Reattaching kernel driver for usb:002:002
 [2014-04-19 20:32:46] Reattaching kernel driver for usb:002:002
 [2014-04-19 20:32:46] Device rescan requested
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:002:002 (path=(null), vid=0403, pid=6014, manuf=FTDI, prod=BitFORCE SHA256 SC, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:002:001 (path=(null), vid=0000, pid=0000, manuf=CMDTECH, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=0000, pid=0000, manuf=SiS, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:000:001 (path=(null), vid=0000, pid=0000, manuf=SiS, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found ft232r device at usb:002:002 (path=(null), vid=0403, pid=6014, manuf=FTDI, prod=BitFORCE SHA256 SC, serial=(null))
 [2014-04-19 20:32:46] Reattaching kernel driver for usb:002:002
 [2014-04-19 20:32:46] Reattaching kernel driver for usb:002:002
 [2014-04-19 20:32:46] Device rescan requested a second time, delaying
 [2014-04-19 20:32:46] schedule_rescan: Scheduling rescan (no rescans currently pending)
 [2014-04-19 20:32:46] No devices detected!
 [2014-04-19 20:32:46] Waiting for devices
 [2014-04-19 20:32:46] Probing for an alive pool
 
I seen this message, and decided, probably some problems with a driver.

Also, I tried to use M+, with line:
Enter target:bitforce/dev/ugen2.2

Anyway see:
(no devices)
[Plus] Add device(s)  [Enter] Close device manager
No new devices found

So, this time I have no idea, what is happening...

[Luke-Jr]

What about uthash?

I don't know why, but configure does not search uthash headers in the /usr/local/include.

I modified configure.ac, and wrote direct path to include files (added part is bold):
#include </usr/local/include/utlist.h>
#include </usr/local/include/uthash.h>

Thereafter, configure runs OK.

This is a compiler/OS issue.

The standard "bitforce" driver should work fine.

Sorry, but something wrong. see terminal output:

# lsusb
Bus /dev/usb Device /dev/ugen2.2: ID 0403:6014 Future Technology Devices International, Ltd
Bus /dev/usb Device /dev/ugen2.1: ID 0000:0000
Bus /dev/usb Device /dev/ugen1.1: ID 0000:0000
Bus /dev/usb Device /dev/ugen0.1: ID 0000:0000

# ls -la /dev/ugen2.2
lrwxr-xr-x  1 root  wheel  9 Apr 19 20:27 /dev/ugen2.2 -> usb/2.2.0
# ls -la /dev/usb/2.2.0
crw-------  1 root  operator    0, 120 Apr 19 20:27 /dev/usb/2.2.0


# ./bfgminer/bfgminer -o pool.xxx.com:0000 -u username -p secret -D -T --verbose -S all
 [2014-04-19 20:32:46] setrlimit: Changed soft fd limit from 11095 to 1024 (FD_SETSIZE=1024; hard limit=11095)         
 [2014-04-19 20:32:46] Started bfgminer 3.99.0
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:002:002 (path=(null), vid=0403, pid=6014, manuf=FTDI, prod=BitFORCE SHA256 SC, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:002:001 (path=(null), vid=0000, pid=0000, manuf=CMDTECH, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=0000, pid=0000, manuf=SiS, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:000:001 (path=(null), vid=0000, pid=0000, manuf=SiS, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found ft232r device at usb:002:002 (path=(null), vid=0403, pid=6014, manuf=FTDI, prod=BitFORCE SHA256 SC, serial=(null))
 [2014-04-19 20:32:46] Reattaching kernel driver for usb:002:002
 [2014-04-19 20:32:46] Reattaching kernel driver for usb:002:002
 [2014-04-19 20:32:46] Device rescan requested
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:002:002 (path=(null), vid=0403, pid=6014, manuf=FTDI, prod=BitFORCE SHA256 SC, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:002:001 (path=(null), vid=0000, pid=0000, manuf=CMDTECH, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=0000, pid=0000, manuf=SiS, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found usb device at usb:000:001 (path=(null), vid=0000, pid=0000, manuf=SiS, prod=OHCI root HUB, serial=(null))
 [2014-04-19 20:32:46] lowlevel_scan: Found ft232r device at usb:002:002 (path=(null), vid=0403, pid=6014, manuf=FTDI, prod=BitFORCE SHA256 SC, serial=(null))
 [2014-04-19 20:32:46] Reattaching kernel driver for usb:002:002
 [2014-04-19 20:32:46] Reattaching kernel driver for usb:002:002
 [2014-04-19 20:32:46] Device rescan requested a second time, delaying
 [2014-04-19 20:32:46] schedule_rescan: Scheduling rescan (no rescans currently pending)
 [2014-04-19 20:32:46] No devices detected!
 [2014-04-19 20:32:46] Waiting for devices
 [2014-04-19 20:32:46] Probing for an alive pool
 
I seen this message, and decided, probably some problems with a driver.

Also, I tried to use M+, with line:
Enter target:bitforce/dev/ugen2.2

Anyway see:
(no devices)
[Plus] Add device(s)  [Enter] Close device manager
No new devices found

So, this time I have no idea, what is happening...

I would expect something like /dev/cuaU0 on BSD.

[maxihatop]

I would expect something like /dev/cuaU0 on BSD.

Yes, on my system exist two devices /dev/cuau*:
# ls -l /dev/cu*
crw-rw----  1 uucp  dialer    0,  45 Apr 19 21:16 /dev/cuau0
crw-rw----  1 uucp  dialer    0,  46 Jan 30 13:14 /dev/cuau0.init
crw-rw----  1 uucp  dialer    0,  47 Jan 30 13:14 /dev/cuau0.lock
crw-rw----  1 uucp  dialer    0,  51 Apr 19 21:18 /dev/cuau1
crw-rw----  1 uucp  dialer    0,  52 Jan 30 13:14 /dev/cuau1.init
crw-rw----  1 uucp  dialer    0,  53 Jan 30 13:14 /dev/cuau1.lock

but both following attempts anyway do not found BFL SC device:

Enter target:bitforce:/dev/cuau0
Enter target:bitforce:/dev/cuau1

No new devices found

[Luke-Jr]

Frontend/GUI authors: Do you hide the BFGMiner window? Will an informational notice annoy you or your users?

[rrob]

Is there an updated BFGMiner which works with Gridseed Blades that produces the correct hash power of the blades?