Bitcoin Forum
June 26, 2017, 07:27:59 AM *
News: Latest stable version of Bitcoin Core: 0.14.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 [48] 49 50 51 52 53 »
  Print  
Author Topic: BFGMiner 5.4.2: GBT+Stratum, RPC, Mac/Linux/Win64, Antminer S1-S5, solo stratum  (Read 608836 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
Buchi-88
Legendary
*
Offline Offline

Activity: 1288



View Profile
June 13, 2016, 07:20:05 PM
 #941

"set-device" : ["antminer:voltage=x780","antminer:clock=237.5","antminer:chip=BM1382"]

Thank you for your help so i hope the U3 runs good on my Pi and the bfgminer Wink

Edit:

The speed are correct or a little bit low?

Quote
bfgminer version 5.4.2 - Started: [2016-06-13 21:15:59] - [  0 days 00:04:28]
 [M]anage devices [P]ool management Settings [D]isplay options                                                       [H]elp [Q]uit
 Pools: 3 (0,1,2)            Diff:64-512  +  LU:[21:19:34]
 Block: ...f034333d061fb293  Diff:92.9k (664.8G)  Started: [21:19:45]  I:?
 ST:0  F:0  NB:20  AS:0  BW:[ 92/  9 B/s]  E:0.00  BS:23
 1/4          |  0.00/35.22/113.7Mh/s | A:0 R:0+0(none) HW:2/ 22%
-------------------------------------------------------------------------------------------------------------------------------------
 AMU 0:       | 142.9/34.70/112.0Mh/s | A:0 R:0+0(none) HW:2/ 22%
-------------------------------------------------------------------------------------------------------------------------------------




   ▄██████▀▀       ▄█████▄
 ▄██▀▀▀          ▄█████████▄
▐██             ▐███████████▌
▐██▌         █  ▐███████████▌
▐██▌       ▄██▌  ▀█████████▀
▐███     ▄███▀     ▀█████▀
▐███   ▄███▀  ▄█▄
▐███   █▀   ▄███▀  ▄▄▄▄    ▄
▐███      ▄███▀  ▄███▀     █
▐███▌    ▄██▀   ███▀      ▐█
▐███▌  ▄██▀   ▄██▀        ██
▐███▌  ▀     ▀▀           ██
▐████▄▄▄▄                ▐██
 ▀██████████████████████▄██▀
   ▀██████████████████████▀
█  █
█  █
█  █
█  █
█  █
█  █
█  █
█  █
.
█  █
█  █
█  █
█  █
█  █
█  █
█  █
█  █
.
.
█  █
█  █
█  █
█  █
█  █
█  █
█  █
█  █
1498462079
Hero Member
*
Offline Offline

Posts: 1498462079

View Profile Personal Message (Offline)

Ignore
1498462079
Reply with quote  #2

1498462079
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1498462079
Hero Member
*
Offline Offline

Posts: 1498462079

View Profile Personal Message (Offline)

Ignore
1498462079
Reply with quote  #2

1498462079
Report to moderator
1498462079
Hero Member
*
Offline Offline

Posts: 1498462079

View Profile Personal Message (Offline)

Ignore
1498462079
Reply with quote  #2

1498462079
Report to moderator
Luke-Jr
Legendary
*
Offline Offline

Activity: 2198



View Profile
June 13, 2016, 08:02:07 PM
 #942

Magnitudes slower than I would expect from a U3...

Buchi-88
Legendary
*
Offline Offline

Activity: 1288



View Profile
June 13, 2016, 08:14:35 PM
 #943

Magnitudes slower than I would expect from a U3...

I also think so, may know they have a solution ?



   ▄██████▀▀       ▄█████▄
 ▄██▀▀▀          ▄█████████▄
▐██             ▐███████████▌
▐██▌         █  ▐███████████▌
▐██▌       ▄██▌  ▀█████████▀
▐███     ▄███▀     ▀█████▀
▐███   ▄███▀  ▄█▄
▐███   █▀   ▄███▀  ▄▄▄▄    ▄
▐███      ▄███▀  ▄███▀     █
▐███▌    ▄██▀   ███▀      ▐█
▐███▌  ▄██▀   ▄██▀        ██
▐███▌  ▀     ▀▀           ██
▐████▄▄▄▄                ▐██
 ▀██████████████████████▄██▀
   ▀██████████████████████▀
█  █
█  █
█  █
█  █
█  █
█  █
█  █
█  █
.
█  █
█  █
█  █
█  █
█  █
█  █
█  █
█  █
.
.
█  █
█  █
█  █
█  █
█  █
█  █
█  █
█  █
Luke-Jr
Legendary
*
Offline Offline

Activity: 2198



View Profile
June 13, 2016, 10:09:47 PM
 #944

Magnitudes slower than I would expect from a U3...

I also think so, may know they have a solution ?
Perhaps try a lower clock rate?

Buchi-88
Legendary
*
Offline Offline

Activity: 1288



View Profile
June 14, 2016, 09:11:26 AM
 #945

Magnitudes slower than I would expect from a U3...

I also think so, may know they have a solution ?
Perhaps try a lower clock rate?

with a manuall start without bfgminer.conf, the U3 runs good... so i will test a today then i hope i have a solution...

The normal spec of the U3 where 225/750?? ~ 50Gh/s?



   ▄██████▀▀       ▄█████▄
 ▄██▀▀▀          ▄█████████▄
▐██             ▐███████████▌
▐██▌         █  ▐███████████▌
▐██▌       ▄██▌  ▀█████████▀
▐███     ▄███▀     ▀█████▀
▐███   ▄███▀  ▄█▄
▐███   █▀   ▄███▀  ▄▄▄▄    ▄
▐███      ▄███▀  ▄███▀     █
▐███▌    ▄██▀   ███▀      ▐█
▐███▌  ▄██▀   ▄██▀        ██
▐███▌  ▀     ▀▀           ██
▐████▄▄▄▄                ▐██
 ▀██████████████████████▄██▀
   ▀██████████████████████▀
█  █
█  █
█  █
█  █
█  █
█  █
█  █
█  █
.
█  █
█  █
█  █
█  █
█  █
█  █
█  █
█  █
.
.
█  █
█  █
█  █
█  █
█  █
█  █
█  █
█  █
Buchi-88
Legendary
*
Offline Offline

Activity: 1288



View Profile
June 14, 2016, 07:55:52 PM
 #946

Magnitudes slower than I would expect from a U3...

I also think so, may know they have a solution ?
Perhaps try a lower clock rate?

Good evening,

after i change my bfgminer.conf to this:

Quote
...
"scan" : [
   "antminer:all"
],
"set-device" : [
   "antminer:chip=BM1382",
   "antminer:voltage=x780",
   "antminer:clock=237.5",
   "antminer:timing=0.022421"
]

The U3 start without problems Wink

Quote
bfgminer version 5.4.2 - Started: [2016-06-14 11:08:25] - [  0 days 10:45:03]
 [M]anage devices [P]ool management Settings Display options             [H]elp [Q]uit
 Pools: 2 (0,2)              Diff:128  +  LU:[21:53:55]
 Block: ...4d5a001ffe217759  Diff:107k (763.6G)  Started: [21:54:25]  I:?
 ST:7  F:2  NB:2007  AS:0  BW:[ 44/ 11 B/s]  E:398.13  BS:455k
 1/4          | 42.81/42.88/46.03Gh/s | A:3147 R:5+1(.18%) HW:2/.00%
-------------------------------------------------------------------------------------------
 AMU 0:       | 42.76/42.88/46.03Gh/s | A:3147 R:5+1(.18%) HW:2/.00%
-------------------------------------------------------------------------------------------

But i'dont know about the speed with 225? ~45Gh/s are OK?

regards and THX



   ▄██████▀▀       ▄█████▄
 ▄██▀▀▀          ▄█████████▄
▐██             ▐███████████▌
▐██▌         █  ▐███████████▌
▐██▌       ▄██▌  ▀█████████▀
▐███     ▄███▀     ▀█████▀
▐███   ▄███▀  ▄█▄
▐███   █▀   ▄███▀  ▄▄▄▄    ▄
▐███      ▄███▀  ▄███▀     █
▐███▌    ▄██▀   ███▀      ▐█
▐███▌  ▄██▀   ▄██▀        ██
▐███▌  ▀     ▀▀           ██
▐████▄▄▄▄                ▐██
 ▀██████████████████████▄██▀
   ▀██████████████████████▀
█  █
█  █
█  █
█  █
█  █
█  █
█  █
█  █
.
█  █
█  █
█  █
█  █
█  █
█  █
█  █
█  █
.
.
█  █
█  █
█  █
█  █
█  █
█  █
█  █
█  █
Luke-Jr
Legendary
*
Offline Offline

Activity: 2198



View Profile
July 01, 2016, 09:47:13 PM
 #947

As miners should be well aware by now, using a CSV-enabled node will be required by block 419328 (~July 4).

Miners using centralised pools via stratum need only ensure their pool is upgraded.

Miners who are solo mining must upgrade bitcoind to Bitcoin Knots 0.12.1.knots20160629.rc2, which has just been released.
Bitcoin Core 0.12.1 is not sufficient due to delays (mostly my fault) in getting GBT updated for CSV upstream. (when released, 0.12.2 and 0.13 will work)
Knots can, however, be configured to use Core's policy defaults by simply adding "corepolicy=1" to your bitcoin.conf file (though I do not recommend this; Knots' own defaults are much better for the network).
In any case, mining nodes should be configured for a larger-than-default memory pool. For example, "maxmempool=1000".
In addition to CSV and BIP9 GBT support, Knots is also backward compatible with current versions of BFGMiner and libblkmaker (using the version/force mechanism), so you do not need to upgrade BFGMiner.

(Note that unlike CSV, SegWit will require upgrading both bitcoind and BFGMiner for GBT and solo mining, so plan on this in a few months.)

toptek
Legendary
*
Offline Offline

Activity: 952


View Profile
July 06, 2016, 02:33:39 AM
 #948

luke im not sure if your ware of this or not but why does fire fox keeping doing this

http://bfgminer.org/
 
http://luke.dashjr.org/programs/bitcoin/files/bfgminer/


Reported Unwanted Software Page!

This web page at bfgminer.org has been reported to contain unwanted software and has been blocked based on your security preferences.

Unwanted software pages try to install software that can be deceptive and affect your system in unexpected ways.

it just started .!!!, Internet Explorer doesn't.

i hate using Internet Explorer aka IE .

cya

P.S.

edit: NM figured it out it seems the update i got a few days ago enabled some thing i don't use or have enable, it's no longer blocked after i turned it off in fire fox .
Luke-Jr
Legendary
*
Offline Offline

Activity: 2198



View Profile
July 06, 2016, 03:10:42 AM
 #949

Firefox and Chrome have apparently decided Bitcoin (mining?) is malware Sad

movellan
Full Member
***
Offline Offline

Activity: 233


View Profile
July 06, 2016, 03:56:45 AM
 #950

luke im not sure if your ware of this or not but why does fire fox keeping doing this

http://bfgminer.org/
 
http://luke.dashjr.org/programs/bitcoin/files/bfgminer/


Reported Unwanted Software Page!

This web page at bfgminer.org has been reported to contain unwanted software and has been blocked based on your security preferences.

Unwanted software pages try to install software that can be deceptive and affect your system in unexpected ways.

it just started .!!!, Internet Explorer doesn't.

i hate using Internet Explorer aka IE .

cya

P.S.

edit: NM figured it out it seems the update i got a few days ago enabled some thing i don't use or have enable, it's no longer blocked after i turned it off in fire fox .

Just click on 'Ignore Warning' and continue.
toptek
Legendary
*
Offline Offline

Activity: 952


View Profile
July 06, 2016, 04:06:25 AM
 #951

Firefox and Chrome have apparently decided Bitcoin (mining?) is malware Sad

so it seems !!!!

Quote

Just click on 'Ignore Warning' and continue.


sense i hate clicking warnings ,  i know are not bad links,
i turned off
Code:
Block reported attack sites in fire fox
sense to me anti software is BS and most of the time never works right and it's how care full you are any way on the webb etc etc ...


Nilssonnet
Newbie
*
Offline Offline

Activity: 1


View Profile
July 12, 2016, 08:40:46 PM
 #952

I'm having issues installing bfgminer on Raspberry Pi (model B), Raspbian Jessy (latest image). I could run it before with Raspbian Wheezy and I followed this guide: http://www.instructables.com/id/Bitcoin-Mining-using-Raspberry-Pi/?ALLSTEPS

Now with new memory card I want to install bfgminer again and it won't compile. I'm still following the guide but have also followed the tips from https://github.com/luke-jr/bfgminer/issues/627, did not work. Installed autoreconf and still not able to compile.

Code:
pi@raspberrypi:~ $ git clone https://github.com/luke-jr/bfgminer.git
Cloning into 'bfgminer'...
remote: Counting objects: 47561, done.
remote: Total 47561 (delta 0), reused 0 (delta 0), pack-reused 47561
Receiving objects: 100% (47561/47561), 36.68 MiB | 1.02 MiB/s, done.
Resolving deltas: 100% (30625/30625), done.
Checking connectivity... done.
pi@raspberrypi:~ $ cd bfgminer/
pi@raspberrypi:~/bfgminer $ dir
70-bfgminer.rules.in       driver-icarus.h      lowl-pci.h
ADL                        driver-jingtian.c    lowl-spi.c
adl.c                      driver-klondike.c    lowl-spi.h
adl_functions.h            driver-klondike.h    lowl-usb.c
adl.h                      driver-kncasic.c     lowl-usb.h
api.c                      driver-knc.c         lowl-vcom.c
api-example.c              driver-littlefury.c  lowl-vcom.h
api-example.php            driver-metabank.c    m4
api-example.py             driver-minergate.c   Makefile.am
api-example.rb             driver-minion.c      make-release
arg-nonnull.h              driver-modminer.c    malgo
AUTHORS                    driver-nanofury.c    mcp2210.c
autogen.sh                 driver-opencl.c      mcp2210.h
avalonhost-raminst         driver-opencl.h      miner.c
binloader.c                driver-proxy.c       miner.h
binloader.h                driver-proxy.h       miner.php
bitstreams                 driver-rockminer.c   NEWS
ccan.bfg                   driver-stratum.c     ocl.c
ccan-upstream              driver-titan.c       ocl.h
c++defs.h                  driver-twinfury.c    opencl
ChangeLog                  driver-twinfury.h    openwrt
CL                         driver-x6500.c       README
compat.h                   driver-zeusminer.c   README.ASIC
configure.ac               driver-ztex.c        README.CPU
COPYING                    dynclock.c           README.Debian
debian                     dynclock.h           README.FPGA
deviceapi.c                example.conf         README.GPU
deviceapi.h                findnonce.c          README.OpenWrt
driver-aan.c               findnonce.h          README.RPC
driver-aan.h               gc3355.c             README.scrypt
driver-alchemist.c         gc3355.h             setup-vfio
driver-antminer.c          gen-version.sh       sha256_4way.c
driver-avalon.c            HACKING              sha256_altivec_4way.c
driver-avalon.h            httpsrv.c            sha256_cryptopp.c
driver-avalonmm.c          httpsrv.h            sha256_generic.c
driver-bfsb.c              iospeeds.h           sha256_sse2_amd64.c
driver-bfx.c               iospeeds_posix.h     sha256_sse2_i386.c
driver-bifury.c            jtag.c               sha256_sse4_amd64.c
driver-bigpic.c            jtag.h               sha256_via.c
driver-bigpic.h            knc-asic             sha2.c
driver-bitforce.c          lib                  sha2.h
driver-bitfury.c           libbase58            start-bfgminer.sh
driver-bitfury.h           libbitfury.c         test-bfgminer.sh
driver-bitmain.c           libbitfury.h         titan-asic.c
driver-bitmain.h           libblkmaker          titan-asic.h
driver-cairnsmore.c        libztex.c            tm_i2c.c
driver-cointerra.c         libztex.h            tm_i2c.h
driver-cointerra.h         LICENSE              todo_ztex.txt
driver-cpu.c               linux-usb-bfgminer   usbtest.py
driver-cpu.h               logging.c            util.c
driver-drillbit.c          logging.h            util.h
driver-dualminer.c         lowlevel.c           version.c
driver-erupter.c           lowlevel.h           warn-on-use.h
driver-getwork.c           lowl-ftdi.c          windows-build.txt
driver-gridseed.c          lowl-ftdi.h          winhacks.h
driver-hashbusteravalon.c  lowl-hid.c           work2d.c
driver-hashbuster.c        lowl-hid.h           work2d.h
driver-hashbusterusb.c     lowl-mswin.c         x86_32
driver-hashfast.c          lowl-mswin.h         x86_64
driver-icarus.c            lowl-pci.c
pi@raspberrypi:~/bfgminer $ ./autogen.sh
Getting submodules...
Submodule 'ccan' (git://git.ozlabs.org/~ccan/ccan) registered for path 'ccan-ups                                    tream'
Submodule 'knc-asic' (git://github.com/KnCMiner/knc-asic) registered for path 'k                                    nc-asic'
Submodule 'libbase58' (git://github.com/luke-jr/libbase58.git) registered for pa                                    th 'libbase58'
Submodule 'libblkmaker' (git://github.com/bitcoin/libblkmaker.git) registered fo                                    r path 'libblkmaker'
Cloning into 'ccan-upstream'...
remote: Counting objects: 18814, done.
remote: Compressing objects: 100% (7023/7023), done.
remote: Total 18814 (delta 13484), reused 15731 (delta 11499)
Receiving objects: 100% (18814/18814), 13.30 MiB | 996.00 KiB/s, done.
Resolving deltas: 100% (13484/13484), done.
Checking connectivity... done.
Submodule path 'ccan-upstream': checked out '8b0bdb090e2882aa431e89f4bc7aa4736e9e2838'
Cloning into 'knc-asic'...
remote: Counting objects: 902, done.
remote: Total 902 (delta 0), reused 0 (delta 0), pack-reused 902
Receiving objects: 100% (902/902), 2.78 MiB | 1.37 MiB/s, done.
Resolving deltas: 100% (582/582), done.
Checking connectivity... done.
Submodule path 'knc-asic': checked out 'e75c9ba362466546a83f1e705b62510a0e0afc6c'
Cloning into 'libbase58'...
remote: Counting objects: 192, done.
remote: Total 192 (delta 0), reused 0 (delta 0), pack-reused 192
Receiving objects: 100% (192/192), 34.77 KiB | 0 bytes/s, done.
Resolving deltas: 100% (108/108), done.
Checking connectivity... done.
Submodule path 'libbase58': checked out '16c2527608053d2cc2fa05b2e3b5ae96065d1410'
Cloning into 'libblkmaker'...
remote: Counting objects: 798, done.
remote: Total 798 (delta 0), reused 0 (delta 0), pack-reused 798
Receiving objects: 100% (798/798), 151.85 KiB | 0 bytes/s, done.
Resolving deltas: 100% (521/521), done.
Checking connectivity... done.
Submodule path 'libblkmaker': checked out 'd2dde7a9edd4ec0360b82dd70be5586163ac2fe8'
Running autoreconf -if...
configure.ac:35: warning: macro 'AM_PATH_LIBGCRYPT' not found in library
configure.ac:29: warning: AM_PATH_LIBGCRYPT missing; CLI tool will not be available
configure.ac:29: warning: AM_PATH_LIBGCRYPT missing; CLI tool will not be available
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:35: warning: macro 'AM_PATH_LIBGCRYPT' not found in library
configure.ac:29: warning: AM_PATH_LIBGCRYPT missing; CLI tool will not be available
configure.ac:29: warning: AM_PATH_LIBGCRYPT missing; CLI tool will not be available
configure.ac:29: warning: AM_PATH_LIBGCRYPT missing; CLI tool will not be available
configure.ac:17: installing './ar-lib'
configure.ac:16: installing './compile'
configure.ac:18: installing './config.guess'
configure.ac:18: installing './config.sub'
configure.ac:13: installing './install-sh'
configure.ac:13: installing './missing'
Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:18: installing './ar-lib'
configure.ac:17: installing './compile'
configure.ac:19: installing './config.guess'
configure.ac:19: installing './config.sub'
configure.ac:14: installing './install-sh'
configure.ac:14: installing './missing'
Makefile.am: installing './depcomp'
configure.ac:43: installing './compile'
configure.ac:30: installing './config.guess'
configure.ac:30: installing './config.sub'
configure.ac:41: installing './install-sh'
configure.ac:41: installing './missing'
Makefile.am:40: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
Updating version.h...
cmp: version.h: No such file or directory
pi@raspberrypi:~/bfgminer $ ./configure
checking build system type... armv6l-unknown-linux-gnueabihf
checking host system type... armv6l-unknown-linux-gnueabihf
checking target system type... armv6l-unknown-linux-gnueabihf
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking for gcc option to accept ISO C99... -std=gnu99
checking for ranlib... ranlib
checking whether gcc -std=gnu99 needs -traditional... no
checking for ranlib... (cached) ranlib
checking how to run the C preprocessor... gcc -E
checking for a sed that does not truncate output... /bin/sed
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for stdint.h... (cached) yes
checking for mprotect... yes
checking for sigaction... yes
checking for sigaltstack... yes
checking for siginterrupt... yes
checking for mmap... yes
checking for MAP_ANONYMOUS... yes
checking whether memchr works... yes
checking whether memmem is declared... yes
checking for memmem... yes
checking whether memmem works... yes
checking for C/C++ restrict keyword... __restrict
checking for uid_t in sys/types.h... yes
checking for inline... inline
checking whether the preprocessor supports include_next... yes
checking whether system header files limit the line length... no
checking for wchar_t... yes
checking for unsigned long long int... yes
checking for long long int... yes
checking whether stdint.h conforms to C99... yes
checking whether memmem is declared without a macro... yes
checking whether mempcpy is declared without a macro... yes
checking whether memrchr is declared without a macro... yes
checking whether rawmemchr is declared without a macro... yes
checking whether stpcpy is declared without a macro... yes
checking whether stpncpy is declared without a macro... yes
checking whether strchrnul is declared without a macro... yes
checking whether strdup is declared without a macro... yes
checking whether strncat is declared without a macro... yes
checking whether strndup is declared without a macro... yes
checking whether strnlen is declared without a macro... yes
checking whether strpbrk is declared without a macro... yes
checking whether strsep is declared without a macro... yes
checking whether strcasestr is declared without a macro... yes
checking whether strtok_r is declared without a macro... yes
checking whether strerror_r is declared without a macro... yes
checking whether strsignal is declared without a macro... yes
checking whether strverscmp is declared without a macro... yes
checking whether strtok_r is declared... (cached) yes
checking whether memmem works in linear time... yes
checking for memmem... (cached) yes
checking whether memmem works... (cached) yes
checking for struct sigaction.sa_sigaction... yes
checking for volatile sig_atomic_t... yes
checking for sighandler_t... yes
checking whether sigaction is declared without a macro... yes
checking whether sigaddset is declared without a macro... yes
checking whether sigdelset is declared without a macro... yes
checking whether sigemptyset is declared without a macro... yes
checking whether sigfillset is declared without a macro... yes
checking whether sigismember is declared without a macro... yes
checking whether sigpending is declared without a macro... yes
checking whether sigprocmask is declared without a macro... yes
checking for sigprocmask... yes
checking whether NULL can be used in arbitrary expressions... yes
checking for strtok_r... yes
checking whether strtok_r works... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for ANSI C header files... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking sys/epoll.h usability... yes
checking sys/epoll.h presence... yes
checking for sys/epoll.h... yes
checking for sys/mman.h... (cached) yes
checking sys/prctl.h usability... yes
checking sys/prctl.h presence... yes
checking for sys/prctl.h... yes
checking sys/file.h usability... yes
checking sys/file.h presence... yes
checking for sys/file.h... yes
checking sys/termios.h usability... yes
checking sys/termios.h presence... yes
checking for sys/termios.h... yes
checking linux/spi/spidev.h usability... yes
checking linux/spi/spidev.h presence... yes
checking for linux/spi/spidev.h... yes
checking for struct i2c_msg.buf... no
checking for struct i2c_msg.len... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking for chroot... yes
checking for sleep... yes
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking whether HASH_ITER is declared... yes
checking whether DL_CONCAT is declared... yes
checking linux/vfio.h usability... yes
checking linux/vfio.h presence... yes
checking for linux/vfio.h... yes
checking for pthread_cancel... with -pthread -lpthread
checking for nanosleep... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for JANSSON... yes
checking for libmicrohttpd... no
configure: WARNING: libmicrohttpd 0.9.5+ not found; getwork proxy will be unavailable
checking for libevent... no
configure: error: Package requirements (libevent >= 2.0.3) were not met:

No package 'libevent' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables libevent_CFLAGS
and libevent_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
pi@raspberrypi:~/bfgminer $ make
make: *** No targets specified and no makefile found.  Stop.
pi@raspberrypi:~/bfgminer $
toptek
Legendary
*
Offline Offline

Activity: 952


View Profile
July 16, 2016, 01:17:45 AM
 #953

I'm having issues installing bfgminer on Raspberry Pi (model B), Raspbian Jessy (latest image). I could run it before with Raspbian Wheezy and I followed this guide: http://www.instructables.com/id/Bitcoin-Mining-using-Raspberry-Pi/?ALLSTEPS

Now with new memory card I want to install bfgminer again and it won't compile. I'm still following the guide but have also followed the tips from https://github.com/luke-jr/bfgminer/issues/627, did not work. Installed autoreconf and still not able to compile.

Code:
pi@raspberrypi:~ $ git clone https://github.com/luke-jr/bfgminer.git
Cloning into 'bfgminer'...
remote: Counting objects: 47561, done.
remote: Total 47561 (delta 0), reused 0 (delta 0), pack-reused 47561
Receiving objects: 100% (47561/47561), 36.68 MiB | 1.02 MiB/s, done.
Resolving deltas: 100% (30625/30625), done.
Checking connectivity... done.
pi@raspberrypi:~ $ cd bfgminer/
pi@raspberrypi:~/bfgminer $ dir
70-bfgminer.rules.in       driver-icarus.h      lowl-pci.h
ADL                        driver-jingtian.c    lowl-spi.c
adl.c                      driver-klondike.c    lowl-spi.h
adl_functions.h            driver-klondike.h    lowl-usb.c
adl.h                      driver-kncasic.c     lowl-usb.h
api.c                      driver-knc.c         lowl-vcom.c
api-example.c              driver-littlefury.c  lowl-vcom.h
api-example.php            driver-metabank.c    m4
api-example.py             driver-minergate.c   Makefile.am
api-example.rb             driver-minion.c      make-release
arg-nonnull.h              driver-modminer.c    malgo
AUTHORS                    driver-nanofury.c    mcp2210.c
autogen.sh                 driver-opencl.c      mcp2210.h
avalonhost-raminst         driver-opencl.h      miner.c
binloader.c                driver-proxy.c       miner.h
binloader.h                driver-proxy.h       miner.php
bitstreams                 driver-rockminer.c   NEWS
ccan.bfg                   driver-stratum.c     ocl.c
ccan-upstream              driver-titan.c       ocl.h
c++defs.h                  driver-twinfury.c    opencl
ChangeLog                  driver-twinfury.h    openwrt
CL                         driver-x6500.c       README
compat.h                   driver-zeusminer.c   README.ASIC
configure.ac               driver-ztex.c        README.CPU
COPYING                    dynclock.c           README.Debian
debian                     dynclock.h           README.FPGA
deviceapi.c                example.conf         README.GPU
deviceapi.h                findnonce.c          README.OpenWrt
driver-aan.c               findnonce.h          README.RPC
driver-aan.h               gc3355.c             README.scrypt
driver-alchemist.c         gc3355.h             setup-vfio
driver-antminer.c          gen-version.sh       sha256_4way.c
driver-avalon.c            HACKING              sha256_altivec_4way.c
driver-avalon.h            httpsrv.c            sha256_cryptopp.c
driver-avalonmm.c          httpsrv.h            sha256_generic.c
driver-bfsb.c              iospeeds.h           sha256_sse2_amd64.c
driver-bfx.c               iospeeds_posix.h     sha256_sse2_i386.c
driver-bifury.c            jtag.c               sha256_sse4_amd64.c
driver-bigpic.c            jtag.h               sha256_via.c
driver-bigpic.h            knc-asic             sha2.c
driver-bitforce.c          lib                  sha2.h
driver-bitfury.c           libbase58            start-bfgminer.sh
driver-bitfury.h           libbitfury.c         test-bfgminer.sh
driver-bitmain.c           libbitfury.h         titan-asic.c
driver-bitmain.h           libblkmaker          titan-asic.h
driver-cairnsmore.c        libztex.c            tm_i2c.c
driver-cointerra.c         libztex.h            tm_i2c.h
driver-cointerra.h         LICENSE              todo_ztex.txt
driver-cpu.c               linux-usb-bfgminer   usbtest.py
driver-cpu.h               logging.c            util.c
driver-drillbit.c          logging.h            util.h
driver-dualminer.c         lowlevel.c           version.c
driver-erupter.c           lowlevel.h           warn-on-use.h
driver-getwork.c           lowl-ftdi.c          windows-build.txt
driver-gridseed.c          lowl-ftdi.h          winhacks.h
driver-hashbusteravalon.c  lowl-hid.c           work2d.c
driver-hashbuster.c        lowl-hid.h           work2d.h
driver-hashbusterusb.c     lowl-mswin.c         x86_32
driver-hashfast.c          lowl-mswin.h         x86_64
driver-icarus.c            lowl-pci.c
pi@raspberrypi:~/bfgminer $ ./autogen.sh
Getting submodules...
Submodule 'ccan' (git://git.ozlabs.org/~ccan/ccan) registered for path 'ccan-ups                                    tream'
Submodule 'knc-asic' (git://github.com/KnCMiner/knc-asic) registered for path 'k                                    nc-asic'
Submodule 'libbase58' (git://github.com/luke-jr/libbase58.git) registered for pa                                    th 'libbase58'
Submodule 'libblkmaker' (git://github.com/bitcoin/libblkmaker.git) registered fo                                    r path 'libblkmaker'
Cloning into 'ccan-upstream'...
remote: Counting objects: 18814, done.
remote: Compressing objects: 100% (7023/7023), done.
remote: Total 18814 (delta 13484), reused 15731 (delta 11499)
Receiving objects: 100% (18814/18814), 13.30 MiB | 996.00 KiB/s, done.
Resolving deltas: 100% (13484/13484), done.
Checking connectivity... done.
Submodule path 'ccan-upstream': checked out '8b0bdb090e2882aa431e89f4bc7aa4736e9e2838'
Cloning into 'knc-asic'...
remote: Counting objects: 902, done.
remote: Total 902 (delta 0), reused 0 (delta 0), pack-reused 902
Receiving objects: 100% (902/902), 2.78 MiB | 1.37 MiB/s, done.
Resolving deltas: 100% (582/582), done.
Checking connectivity... done.
Submodule path 'knc-asic': checked out 'e75c9ba362466546a83f1e705b62510a0e0afc6c'
Cloning into 'libbase58'...
remote: Counting objects: 192, done.
remote: Total 192 (delta 0), reused 0 (delta 0), pack-reused 192
Receiving objects: 100% (192/192), 34.77 KiB | 0 bytes/s, done.
Resolving deltas: 100% (108/108), done.
Checking connectivity... done.
Submodule path 'libbase58': checked out '16c2527608053d2cc2fa05b2e3b5ae96065d1410'
Cloning into 'libblkmaker'...
remote: Counting objects: 798, done.
remote: Total 798 (delta 0), reused 0 (delta 0), pack-reused 798
Receiving objects: 100% (798/798), 151.85 KiB | 0 bytes/s, done.
Resolving deltas: 100% (521/521), done.
Checking connectivity... done.
Submodule path 'libblkmaker': checked out 'd2dde7a9edd4ec0360b82dd70be5586163ac2fe8'
Running autoreconf -if...
configure.ac:35: warning: macro 'AM_PATH_LIBGCRYPT' not found in library
configure.ac:29: warning: AM_PATH_LIBGCRYPT missing; CLI tool will not be available
configure.ac:29: warning: AM_PATH_LIBGCRYPT missing; CLI tool will not be available
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:35: warning: macro 'AM_PATH_LIBGCRYPT' not found in library
configure.ac:29: warning: AM_PATH_LIBGCRYPT missing; CLI tool will not be available
configure.ac:29: warning: AM_PATH_LIBGCRYPT missing; CLI tool will not be available
configure.ac:29: warning: AM_PATH_LIBGCRYPT missing; CLI tool will not be available
configure.ac:17: installing './ar-lib'
configure.ac:16: installing './compile'
configure.ac:18: installing './config.guess'
configure.ac:18: installing './config.sub'
configure.ac:13: installing './install-sh'
configure.ac:13: installing './missing'
Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:18: installing './ar-lib'
configure.ac:17: installing './compile'
configure.ac:19: installing './config.guess'
configure.ac:19: installing './config.sub'
configure.ac:14: installing './install-sh'
configure.ac:14: installing './missing'
Makefile.am: installing './depcomp'
configure.ac:43: installing './compile'
configure.ac:30: installing './config.guess'
configure.ac:30: installing './config.sub'
configure.ac:41: installing './install-sh'
configure.ac:41: installing './missing'
Makefile.am:40: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
Updating version.h...
cmp: version.h: No such file or directory
pi@raspberrypi:~/bfgminer $ ./configure
checking build system type... armv6l-unknown-linux-gnueabihf
checking host system type... armv6l-unknown-linux-gnueabihf
checking target system type... armv6l-unknown-linux-gnueabihf
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking for gcc option to accept ISO C99... -std=gnu99
checking for ranlib... ranlib
checking whether gcc -std=gnu99 needs -traditional... no
checking for ranlib... (cached) ranlib
checking how to run the C preprocessor... gcc -E
checking for a sed that does not truncate output... /bin/sed
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking for stdint.h... (cached) yes
checking for mprotect... yes
checking for sigaction... yes
checking for sigaltstack... yes
checking for siginterrupt... yes
checking for mmap... yes
checking for MAP_ANONYMOUS... yes
checking whether memchr works... yes
checking whether memmem is declared... yes
checking for memmem... yes
checking whether memmem works... yes
checking for C/C++ restrict keyword... __restrict
checking for uid_t in sys/types.h... yes
checking for inline... inline
checking whether the preprocessor supports include_next... yes
checking whether system header files limit the line length... no
checking for wchar_t... yes
checking for unsigned long long int... yes
checking for long long int... yes
checking whether stdint.h conforms to C99... yes
checking whether memmem is declared without a macro... yes
checking whether mempcpy is declared without a macro... yes
checking whether memrchr is declared without a macro... yes
checking whether rawmemchr is declared without a macro... yes
checking whether stpcpy is declared without a macro... yes
checking whether stpncpy is declared without a macro... yes
checking whether strchrnul is declared without a macro... yes
checking whether strdup is declared without a macro... yes
checking whether strncat is declared without a macro... yes
checking whether strndup is declared without a macro... yes
checking whether strnlen is declared without a macro... yes
checking whether strpbrk is declared without a macro... yes
checking whether strsep is declared without a macro... yes
checking whether strcasestr is declared without a macro... yes
checking whether strtok_r is declared without a macro... yes
checking whether strerror_r is declared without a macro... yes
checking whether strsignal is declared without a macro... yes
checking whether strverscmp is declared without a macro... yes
checking whether strtok_r is declared... (cached) yes
checking whether memmem works in linear time... yes
checking for memmem... (cached) yes
checking whether memmem works... (cached) yes
checking for struct sigaction.sa_sigaction... yes
checking for volatile sig_atomic_t... yes
checking for sighandler_t... yes
checking whether sigaction is declared without a macro... yes
checking whether sigaddset is declared without a macro... yes
checking whether sigdelset is declared without a macro... yes
checking whether sigemptyset is declared without a macro... yes
checking whether sigfillset is declared without a macro... yes
checking whether sigismember is declared without a macro... yes
checking whether sigpending is declared without a macro... yes
checking whether sigprocmask is declared without a macro... yes
checking for sigprocmask... yes
checking whether NULL can be used in arbitrary expressions... yes
checking for strtok_r... yes
checking whether strtok_r works... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for ANSI C header files... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking sys/epoll.h usability... yes
checking sys/epoll.h presence... yes
checking for sys/epoll.h... yes
checking for sys/mman.h... (cached) yes
checking sys/prctl.h usability... yes
checking sys/prctl.h presence... yes
checking for sys/prctl.h... yes
checking sys/file.h usability... yes
checking sys/file.h presence... yes
checking for sys/file.h... yes
checking sys/termios.h usability... yes
checking sys/termios.h presence... yes
checking for sys/termios.h... yes
checking linux/spi/spidev.h usability... yes
checking linux/spi/spidev.h presence... yes
checking for linux/spi/spidev.h... yes
checking for struct i2c_msg.buf... no
checking for struct i2c_msg.len... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking for chroot... yes
checking for sleep... yes
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking whether HASH_ITER is declared... yes
checking whether DL_CONCAT is declared... yes
checking linux/vfio.h usability... yes
checking linux/vfio.h presence... yes
checking for linux/vfio.h... yes
checking for pthread_cancel... with -pthread -lpthread
checking for nanosleep... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for JANSSON... yes
checking for libmicrohttpd... no
configure: WARNING: libmicrohttpd 0.9.5+ not found; getwork proxy will be unavailable
checking for libevent... no
configure: error: Package requirements (libevent >= 2.0.3) were not met:

No package 'libevent' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables libevent_CFLAGS
and libevent_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
pi@raspberrypi:~/bfgminer $ make
make: *** No targets specified and no makefile found.  Stop.
pi@raspberrypi:~/bfgminer $


why not use Ubuntu 16 new version due out at the end of the month, it is suppose to fix a lot of issue for rasp berry PI the first version of ubuntu 16 broke . i use mostly cubieboards , banana pis and orange Pi they actually work better for me with ubuntu 16 from here http://www.armbian.com/  yea there is no rasp berry support on that site they won't support them ,I don't use them much but  if the new of ubuntu 16.04.1 fixes a lot of stuff I may again .


and this  might fix this  issue

 
Quote
AM_PATH_LIBGCRYPT missing; CLI tool will not be available


try this
Code:
sudo apt-get -y install libgcrypt20-dev

then re compile it with this

Code:
sudo apt-get -y install git-core build-essential autoconf automake libtool pkg-config nodejs libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev libncurses5-dev unzip libblkmaker-0.1-dev
sudo git clone https://github.com/luke-jr/bfgminer.git

cd bfgminer
sudo ./autogen.sh -rpath-link

sudo chmod +x ./configure 
sudo ./configure

sudo make



w0mp
Member
**
Offline Offline

Activity: 103


View Profile
July 18, 2016, 09:59:45 AM
 #954

Hello,

I am having issues getting BFGMiner 5.4.2 to recognize my antminer S3+.  I have it successfully installed and it launches fine, but no matter what options I put, it cannot see it.  I have searched through this thread and saw other people have been having the same issue.  Are there any known fixes?  I am using the syntax exactly as described in the README for the Bitmain options.  Was this release NOT built with the --enable-bitmain option?  How can I tell?

I am this OpenWRT:  BARRIER BREAKER (Bleeding Edge, r38031)

I have tried the BFGMiner releases for 12.09 and 15.05, both with the same results.  I beleive my OpenWRT version says its 14.0x.  

I am the latest S3+ firmware.  

Here is my command:

Code:
./bfgminer -o 192.168.50.103:50542 -u USER -p PASSWORD -S bitmain:all --set btm:layout=32:8 --set btm:timeout=18 --set btm:clock=225 --set btm:reg_data=0882 --set btm:voltage=x0725

I saw that there was a later version of OpenWRT that specifically said it supports the S3, but I cannot flash it.  The GUI says its not a valid firmware, like toptek said its because Bitmain locks it.

ANY help is greatly appreciated.  Thanks!
toptek
Legendary
*
Offline Offline

Activity: 952


View Profile
July 18, 2016, 11:05:30 AM
 #955

There is a openwrt version on the openwrt site under the download page for S3 but i think it has CG miner in it sadly and there is another link on the open wrt web site that tells you how to run bfg over openwrt which i have on a PI type with Zeus miners but no luck with S1 S3 .I have got it running on S5 c1 etc  but that  ant's controller is different and has enough memory to compile it on the ant . sorry i can't help more .
Luke-Jr
Legendary
*
Offline Offline

Activity: 2198



View Profile
July 18, 2016, 03:35:13 PM
 #956

At the very least, you will need --set bitmain:model=S3 or it won't know which protocol to use.

w0mp
Member
**
Offline Offline

Activity: 103


View Profile
July 19, 2016, 03:51:27 AM
 #957

At the very least, you will need --set bitmain:model=S3 or it won't know which protocol to use.

I originally had that in there but took it out to experiment.  No difference in result using it or not.  I think if I can get the Antminer is failsafe mode, I can flash a newer OpenWRT firmware, like the one 15.05 that says it supports antminer s3.  I see a bunch of commits to code on the OpenWRT site that pertain to antminer s3.  I dont really care if I have a web interface or not, I just SSH in anyways.
w0mp
Member
**
Offline Offline

Activity: 103


View Profile
July 19, 2016, 06:28:27 AM
 #958

Luke-Jr, are the BFGMiner builds on your openwrt repository compiled with the bitmain drivers included?  I see in the openwrt directory of the github, the makefile for openwrt has it disabled.  Just wondering if I am wasting my time trying to cross compile for openwrt with bitmain enabled.  There is no way to tell from the already compiled BFGMiner packages are there?

Thanks for your help!
Luke-Jr
Legendary
*
Offline Offline

Activity: 2198



View Profile
July 19, 2016, 06:37:35 AM
 #959

Luke-Jr, are the BFGMiner builds on your openwrt repository compiled with the bitmain drivers included?  I see in the openwrt directory of the github, the makefile for openwrt has it disabled.  Just wondering if I am wasting my time trying to cross compile for openwrt with bitmain enabled.  There is no way to tell from the already compiled BFGMiner packages are there?

Thanks for your help!
Only the ar71xx builds. I wonder if others need it?

w0mp
Member
**
Offline Offline

Activity: 103


View Profile
July 19, 2016, 06:53:10 AM
 #960

Luke-Jr, are the BFGMiner builds on your openwrt repository compiled with the bitmain drivers included?  I see in the openwrt directory of the github, the makefile for openwrt has it disabled.  Just wondering if I am wasting my time trying to cross compile for openwrt with bitmain enabled.  There is no way to tell from the already compiled BFGMiner packages are there?

Thanks for your help!
Only the ar71xx builds. I wonder if others need it?

Well the ar71xx is what the antminer S3 requires I believe.  The one thing I am wondering is if its not working because you compiled for OpenWRT versions 12.09 and 15.05, and the S3 is 14.07.  Not sure if there is backwards/forward compatibility.  I grabbed the 14.07 openwrt compile tools and am going to attempt to cross-compile it.

I am not too familiar with OpenWRT so I am just taking a stab in the dark here.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 [48] 49 50 51 52 53 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!