Topic: BFGMiner 5.5.0: CPU/GPU/FPGA/ASIC mining software, GBT+Stratum, RPC, Linux/Win64 - page 13. (Read 834500 times)
July 25, 2016, 09:38:51 AM
You could try increasing the queue size with the -Q option.
July 25, 2016, 01:48:47 AM
getwork doesn't perform very well since it needs to make a new request for every 4 Gh... so with a S5 that's almost 300 requests per second.
Well its odd, I have it turned down to the lowest frequency (100) and am only running one board. On a standard stratum pool like zpool.ca, I get about 275 GH. On a local getwork server I only get about 500 MH. I have another rig that is a RasPi + Gekkoscience stick. Its connected to the same local getwork server and I get 10 GH solid. It seems to find blocks much faster. I also get no "pool 0 is not providing work fast enough" errors. Its odd the S5 would hash so low while the Gekko, which is the same chips, hashes normally.
I have tried using both boards as well as completely stock settings and I get the same results.
July 24, 2016, 09:21:08 PM
getwork doesn't perform very well since it needs to make a new request for every 4 Gh... so with a S5 that's almost 300 requests per second.
July 24, 2016, 04:22:08 PM
I ended up just ditching the S3 in favor of an S5. I have everything working except perhaps you could shed some light on one issue I am having. My hashrate when mining on a big stratum mining pool is normal and works great, but when I am solo mining with Getwork my hashrate only shows about 600 MH to 1GH. It wont go past that. This is however, before I have found any blocks, so maybe it is innacurate? I am not solo mining BTC, its a very low difficulty sha256 alt, but I tested it with bitcoin client for comparison and I get the same low hashrate when solo mining. Thanks!
July 20, 2016, 11:32:07 AM
A while back i said something about getting this error and one other error i think the S3 hashed for 1 or 2 second then locked bfg and shut off access to the S3 to the point i had to do a hard ware reset at that point after hours of trying i gave up it got really annoying .
the other error was
mainly this Inappropriate
to check the kerrel drivers with openwrt
it may say USB in the check but it does list any all drivers installed or not . 
.
source
https://wiki.openwrt.org/doc/howto/bitcoinmining#installing_kernel_drivers
and that might even be the issue for some reason bfg keeps looking for USB drivers to load like you said kind of
luke by this
and it's finding nothing so it shut downs. i know it will work on S3's i think i had it running on my C1 which is a S3 over clock and water cooled it dos run on a S5 and works well but those miners use a bb as the controller you can do all the compiling on that controller and the S1/3 have a completely different controller with no room to do it like you can on a BB controller but I'm guessing at this point, I'm not really to interested in going back and messing with it for hours till i get annoyed but if some one gets it running I'm willing to give it a shot .
Code:
/dev/bitmain-asic: tcgetattr failed:Inappropriate ioctl for device
the other error was
Code:
bitmain_detect_one stop bitmain_initialize -1
mainly this Inappropriate
to check the kerrel drivers with openwrt
Code:
cat /sys/kernel/debug/usb/devices
.source
https://wiki.openwrt.org/doc/howto/bitcoinmining#installing_kernel_drivers
and that might even be the issue for some reason bfg keeps looking for USB drivers to load like you said kind of
luke by this
Quote
Looks like it's simply not getting a response from the kernel driver.
and it's finding nothing so it shut downs. i know it will work on S3's i think i had it running on my C1 which is a S3 over clock and water cooled it dos run on a S5 and works well but those miners use a bb as the controller you can do all the compiling on that controller and the S1/3 have a completely different controller with no room to do it like you can on a BB controller but I'm guessing at this point, I'm not really to interested in going back and messing with it for hours till i get annoyed but if some one gets it running I'm willing to give it a shot .
July 19, 2016, 05:29:54 PM
No, antminer S* use an ugly hack of a custom kernel module.
There is nothing USB about them.
There is nothing USB about them.
July 19, 2016, 05:00:06 PM
Looks like it's simply not getting a response from the kernel driver.
Anyone happen to know which kernel driver code the S3 uses?
Anyone happen to know which kernel driver code the S3 uses?
If you are meaning the version, its kernel 3.10.12
Could it be that I am missing the kmod-usb-serial-cp210x and other kmod drivers you list in the README? I tried to install them but I get an error saying they need kernel 3.10.49. I can't find how to just update the kernel version.
July 19, 2016, 04:54:21 PM
Looks like it's simply not getting a response from the kernel driver.
Anyone happen to know which kernel driver code the S3 uses?
Anyone happen to know which kernel driver code the S3 uses?
July 19, 2016, 04:41:44 PM
Sorry I should have read the README more carefully about providing debug logs. I used -D -T --verbose and heres what I got:
Code:
root@antMiner:/usr/bin# ./bfgminer -o http://192.168.1.104:50542 -u brkrpc -p pl
easeservevideo -S bitmain:auto --set bitmain:model=S3 --set btm:layout=32:8 --se
t btm:timeout=18 --set btm:clock=225 --set btm:reg_data=0882 -D -T --verbose
[2016-07-20 05:39:45] setrlimit: Soft fd limit not being changed from 1024 (FD_SETSIZE=1024; hard limit=4096)
[2016-07-20 05:39:45] Started bfgminer 5.4.2
[2016-07-20 05:39:45] lowlevel_scan: Found usb device at usb:001:004 (path=(null), vid=4254, pid=4153, manuf=BitMain Technology Inc., prod=Asic Control, serial=(null))
[2016-07-20 05:39:45] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=1d6b, pid=0002, manuf=Linux 3.10.12 ehci_hcd, prod=EHCI Host Controller, serial=ehci-platform)
[2016-07-20 05:39:45] lowlevel_scan: Found usb device at usb:001:002 (path=(null), vid=0409, pid=005a, manuf=(null), prod=(null), serial=(null))
[2016-07-20 05:39:46] BTM detect dev: /dev/bitmain-asic
[2016-07-20 05:39:46] BTM: cgpu_set_defaults: Matched with set default: bitmain:model=S3
[2016-07-20 05:39:46] BTM: Applied rule bitmain:model=S3
[2016-07-20 05:39:46] BTM: cgpu_set_defaults: Matched with set default: btm:layout=32:8
[2016-07-20 05:39:46] BTM: Applied rule btm:layout=32:8
[2016-07-20 05:39:46] BTM: cgpu_set_defaults: Matched with set default: btm:timeout=18
[2016-07-20 05:39:46] BTM: Applied rule btm:timeout=18
[2016-07-20 05:39:46] BTM: cgpu_set_defaults: Matched with set default: btm:clock=225
[2016-07-20 05:39:46] BTM: Applied rule btm:clock=225
[2016-07-20 05:39:46] BTM: cgpu_set_defaults: Matched with set default: btm:reg_data=0882
[2016-07-20 05:39:46] BTM: Applied rule btm:reg_data=0882
[2016-07-20 05:39:46] btm_init cgpu->device_fd=-1
[2016-07-20 05:39:46] Acquired exclusive advisory lock on /dev/bitmain-asic
[2016-07-20 05:39:46] /dev/bitmain-asic: tcgetattr failed: Inappropriate ioctl for device
[2016-07-20 05:39:46] btm_init open device fd = 12
[2016-07-20 05:39:46] bitmain_detect_one btm init ok
[2016-07-20 05:39:46] BitMain RxStatus Token: v(0) chip_status_eft(0) detect_get(1) chip_address(00) reg_address(00) crc(2f8c)
[2016-07-20 05:39:46] BitMain: Sent(12): 530008004000000000008c2f
[2016-07-20 05:39:46] ----bitmain_send_data stop ret=0 datalen=12
[2016-07-20 05:39:47] BMS0: InitSet error
[2016-07-20 05:39:47] bitmain_detect_one stop bitmain_initialize -1
[2016-07-20 05:39:47] BTM uninit BTM12
July 19, 2016, 05:35:55 AM
I feel like I have made progress here. I have been able to successfully cross-compile BFGMiner 5.4.2 for OpenWRT 14.07, ensuring the "--enable-btmain" option was turned on. I verified it in the compile logs. It now detects the S3 with a using "-S bitmain:auto" but crashes and needs to be restarted. Using "-S bitmain:all" yields no devices found.
Perhaps my command line needs modification? Here is the stock S3 cgminer command line:
I have cgminer startup disabled via the WebUI, so it should not be interfering with BFGMiner.
What do you take of these errors and is there anything I can do to get you more info about them? Thanks!
Code:
root@antMiner:/usr/bin# ./bfgminer -o 192.168.1.102:50542 -u USER -p PASSWORD -S bitmain:auto --set bitmain:model=S3 --set btm:layout=32:8 --set btm:timeout=18 --set btm:clock=225 --set btm:reg_data=0882
[2016-07-19 18:25:57] Started bfgminer 5.4.2
[2016-07-19 18:25:57] bitmain_detect_one btm init ok
[2016-07-19 18:25:57] BitMain RxStatus Token: v(0) chip_status_eft(0) detect_get(1) chip_address(00) reg_address(00) crc(2f8c)
[2016-07-19 18:25:59] BMS0: InitSet error
[2016-07-19 18:25:59] bitmain_detect_one stop bitmain_initialize -1
Perhaps my command line needs modification? Here is the stock S3 cgminer command line:
Code:
--bitmain-options 115200:32:8:18:225:0882
I have cgminer startup disabled via the WebUI, so it should not be interfering with BFGMiner.
What do you take of these errors and is there anything I can do to get you more info about them? Thanks!
July 19, 2016, 01:53:10 AM
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?Thanks for your help!
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.
July 19, 2016, 01:37:35 AM
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? Thanks for your help!
July 19, 2016, 01:28:27 AM
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!
Thanks for your help!
July 18, 2016, 10:51:27 PM
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.
July 18, 2016, 10:35:13 AM
At the very least, you will need --set bitmain:model=S3 or it won't know which protocol to use.
July 18, 2016, 06:05:30 AM
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 .
July 18, 2016, 04:59:45 AM
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:
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!
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!
July 15, 2016, 08:17:45 PM
July 12, 2016, 03:40:46 PM
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.
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 $
July 05, 2016, 11:06:25 PM
Firefox and Chrome have apparently decided Bitcoin (mining?) is malware 
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
Jump to: