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

chanberg

hero member

Activity: 672

Merit: 500

Code:

root@raspberrypi:/home/pi/bfgminer-feature-gridseed-support# make
make all-recursive
make[1]: Entering directory `/home/pi/bfgminer-feature-gridseed-support'
Making all in lib
make[2]: Entering directory `/home/pi/bfgminer-feature-gridseed-support/lib'
make all-recursive
make[3]: Entering directory `/home/pi/bfgminer-feature-gridseed-support/lib'
make[4]: Entering directory `/home/pi/bfgminer-feature-gridseed-support/lib'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/home/pi/bfgminer-feature-gridseed-support/lib'
make[3]: Leaving directory `/home/pi/bfgminer-feature-gridseed-support/lib'
make[2]: Leaving directory `/home/pi/bfgminer-feature-gridseed-support/lib'
Making all in ccan.bfg
make[2]: Entering directory `/home/pi/bfgminer-feature-gridseed-support/ccan.bfg'
make[2]: *** No rule to make target `../ccan-upstream/ccan/opt/helpers.c', needed by `../ccan-upstream/ccan/opt/libccan_a-helpers.o'. Stop.
make[2]: Leaving directory `/home/pi/bfgminer-feature-gridseed-support/ccan.bfg'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/pi/bfgminer-feature-gridseed-support'
make: *** [all] Error 2
root@raspberrypi:/home/pi/bfgminer-feature-gridseed-support#

darkfriend77

sr. member

Activity: 434

Merit: 265

Quote from: Pistachio on March 11, 2014, 09:43:14 AM

This looks great. Anyone tried this with 40+ miners (off 4 USB hubs)?

Quote from: nwoolls on March 09, 2014, 03:25:22 AM

...

I tryed out yesterday with 20 on 2 hubs ... it was working ... but haven't tested more then 30 minutes.

As I wanted to have them hash on seperate workers ... to check some stuff ...

Pistachio

legendary

Activity: 1456

Merit: 1000

This looks great. Anyone tried this with 40+ miners (off 4 USB hubs)?

Quote from: nwoolls on March 09, 2014, 03:25:22 AM

The previous driver I linked is for the GridSeed 1-chip device, so far resold by DualMiner.

For support for the GridSeed 5-chip devices, if you are feeling crazy you can try this out (Scrypt-only currently):

https://github.com/nwoolls/bfgminer/commits/feature/gridseed-support

I give it the It Works For Me(tm) stamp of approval. Run it with -S gridseed:all and specify frequency with --set-device gridseed:clock=freq, e.g. 850 (default is 600).

For OS X users, these should be loaded automatically but in case they aren't:

Code:

sudo kextload -b com.apple.driver.AppleUSBCDC
sudo kextload -b com.apple.driver.AppleUSBCDCACMData

SHA2 support will be next followed by dual-algorithm support. If you have some of these and are feeling froggy, feedback is welcome.

Isuearl

member

Activity: 63

Merit: 10

Can't speak the praises enough of BFGminer.... I am a relative NOOB when it comes to mining, but I have been Using BFG miner for the most part...Its relatively simple....Just started using the Proxy yesterday....I had some consternation while setting it up...but it turned out it was my Antivirus program causing me the headache...turned off AV started the proxy and turned AV back on and now everything is hashing like a champ....
I want to thank Luke Jr for the hard work not to mention nwools and everyone else I missed for an overall decent piece of software.......(not to mention this thread which contains a boatload of info for the NOOBs).
To the NOOBs out there, just page through the thread...most of your questions will be answered somewhere....

Aurum

sr. member

Activity: 453

Merit: 250

dfgfdgfdg

Quote from: nwoolls on March 11, 2014, 07:38:32 AM

Quote from: hurricandave on March 10, 2014, 11:47:15 PM

I got my Antminer U2 today also, no luck so far. I'm using Windows 7 Pro 32-bit. SiLab drivers installed. Windows sees the device in corect port. The miner has a steady Red LED but BFGMiner has No New Device Found. I can't find any info from Bitmain for these either. Well, except for pricing.

I've contacted both Bitmain and resellers about getting a sample so we can upgrade the driver. No responses yet. I'd heard these were compatible with the U1 but apparently not.

Please add the AntMiner S1 to the MuM armory Grin

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: hurricandave on March 10, 2014, 11:47:15 PM

I got my Antminer U2 today also, no luck so far. I'm using Windows 7 Pro 32-bit. SiLab drivers installed. Windows sees the device in corect port. The miner has a steady Red LED but BFGMiner has No New Device Found. I can't find any info from Bitmain for these either. Well, except for pricing.

I've contacted both Bitmain and resellers about getting a sample so we can upgrade the driver. No responses yet. I'd heard these were compatible with the U1 but apparently not.

marcocoin

newbie

Activity: 34

Merit: 0

Quote from: hurricandave on March 11, 2014, 02:11:05 AM

Quote from: demonmaestro on March 11, 2014, 01:40:48 AM

Until Luke gives us some goodies to work with I am using cgminer.

Was your U2 showing a steady red led? This is my first ASIC and I feel like I talked myself into jumping in a foul moat.

Red led is always on.

When the miner is working there is a small green light flashing (on the U1 anyway).

marcocoin

newbie

Activity: 34

Merit: 0

Quote from: hurricandave on March 10, 2014, 11:47:15 PM

Quote from: demonmaestro on March 08, 2014, 09:08:57 PM

I've gotten my hands on some AntMiner U2s but bfgminer is not seeing them.

This is on a Raspi.

Code:

./bfgminer-3.10.0/bfgminer -S antminer:all -o stratum.myfuckingpool.com:3333 -u demonmaestro_usb -p 1

I got my Antminer U2 today also, no luck so far. I'm using Windows 7 Pro 32-bit. SiLab drivers installed. Windows sees the device in corect port. The miner has a steady Red LED but BFGMiner has No New Device Found. I can't find any info from Bitmain for these either. Well, except for pricing.

Have you tried giving the COM port numbers in the command line?

Something like this... -S \\.\COM1 or the COM port of your U2 antminer.

For example .. my run command bat file is:

bfgminer.exe -o ppc.fixx.ru:8437 -u xxxx.ppc01 -p xx1 -S \\.\COM3 -S \\.\COM4 -S \\.\COM8 -S \\.\COM9 -S antminer:all --set-device antminer:clock=x0981 --icarus-options 115200:2:2

I have a vista laptop and BFGminer 3.10...

BFGminer works fantastic with my Antminer U1 units and should be same for the U2 units.

By the way be very careful to not add extra spaces in between commands as that will create an error.

best regards

hurricandave

legendary

Activity: 966

Merit: 1003

Quote from: demonmaestro on March 11, 2014, 01:40:48 AM

Until Luke gives us some goodies to work with I am using cgminer.

Was your U2 showing a steady red led? This is my first ASIC and I feel like I talked myself into jumping in a foul moat.

demonmaestro

hero member

Activity: 574

Merit: 500

Mining for the hell of it.

Until Luke gives us some goodies to work with I am using cgminer.

hurricandave

legendary

Activity: 966

Merit: 1003

Quote from: demonmaestro on March 08, 2014, 09:08:57 PM

I've gotten my hands on some AntMiner U2s but bfgminer is not seeing them.

This is on a Raspi.

Code:

./bfgminer-3.10.0/bfgminer -S antminer:all -o stratum.myfuckingpool.com:3333 -u demonmaestro_usb -p 1

I got my Antminer U2 today also, no luck so far. I'm using Windows 7 Pro 32-bit. SiLab drivers installed. Windows sees the device in corect port. The miner has a steady Red LED but BFGMiner has No New Device Found. I can't find any info from Bitmain for these either. Well, except for pricing.

alandsidel

newbie

Activity: 3

Merit: 0

I have a (hopefully simple) question about the displayed difficulty in BFGMiner and other cpuminer derivatives like cgminer.

I'm working on some bitcoin related web stuff and am using both testnet and testnet-in-a-box. On the 'real' testnet, the difficulty is always shown as 2.73k even when I would expect it to be showing difficulty 1. Obviously I'm just not understanding something about testnet3 and the 20 minute difficulty 'reset' thing. If anyone can explain just what's going on there, I'd appreciate it.

Bitcoind and bitcoin-qt seem to always show the 'correct' difficulty (1 after 20 minutes of inactivity, real difficulty otherwise).

sunjar2013

member

Activity: 92

Merit: 10

Recently I use BFGMiner to drive my ASICMiner's USB deivce(333MH), it works very well, but I still have a problem that is when I trying to use a command like as bfgminer.exe 2>log.txt syntax to logging the output message, I found the log file is very verbose, just like:

[2014-03-10 17:56:29] 5s:397.3 avg:331.8 u:180.1 Mh/s | A:0 R:0+0(none) HW:0/none
[2014-03-10 17:56:34] 5s:372.7 avg:332.4 u:442.0 Mh/s | A:0 R:0+0(none) HW:0/none
[2014-03-10 17:56:41] 5s:213.4 avg:269.1 u:357.8 Mh/s | A:0 R:0+0(none) HW:0/none
[2014-03-10 17:56:47] 5s:355.6 avg:310.5 u:306.7 Mh/s | A:0 R:0+0(none) HW:0/none
...... etc

I remember the CGMiner only log the main message like as new block found or share accepted, and CGMiner not use time interval mode to log to file, it just write file when new message arrived. But BFGMiner not like this, it seems like write message every 5 second (can adjust by paramter or modify configuration file). My point is I don't like this record mode, if we use time interval mode we maybe miss something if interval value is to big, otherwise if this value too small, my hard driver is working hard beacause frequency read and write. So, is BFGMiner have a way to log data like CGMiner? Just execute write operate when output message appear?

By the way, BFGMiner is also a great program, many thanks for dev's work of this software.

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: Blackbird0 on March 10, 2014, 09:13:57 AM

First: the DualMiner chip seems to shut off a lot. As you know, the plural of anecdotes isn't data, but it seems to be happing more frequently on this build. The most I've gotten is 13 hours running without a problem. Sometimes it runs for only a couple hours before it shuts off. I've tried moving to a somewhat larger/more stable pool. Don't know if that helps. I'm mining Dogecoin if that matters.

Second: the OV function isn'tworking as expected. After 13 hours on my current run, it's averaging 71.1 KH/s. I'd be expecting it be higher with the 850 OC argument added.

I haven't had a unit "shut off" with either build on any OS, but I'll keep an eye out for it.

And 850 is the default frequency for U1s - you aren't OCing it so you aren't going to see a change in speed.

Blackbird0

full member

Activity: 207

Merit: 100

nwoolls: after a couple days running your DualMiner build, here's my experiences:

First: the DualMiner chip seems to shut off a lot. As you know, the plural of anecdotes isn't data, but it seems to be happing more frequently on this build. The most I've gotten is 13 hours running without a problem. Sometimes it runs for only a couple hours before it shuts off. I've tried moving to a somewhat larger/more stable pool. Don't know if that helps. I'm mining Dogecoin if that matters.

Second: the OV function isn'tworking as expected. After 13 hours on my current run, it's averaging 71.1 KH/s. I'd be expecting it be higher with the 850 OC argument added.

Any thoughts on this? Otherwise, the build is perfectly stable, and all my other devices in my SHA-256 instance is working fine.

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: nwoolls on March 09, 2014, 03:38:23 AM

https://www.dropbox.com/s/ho5lf1vqj57f5a2/bfgminer_gridseed_pr1.7z

I give this my I Haven't Tried It And It May Take A Custom INF stamp.

So these do need a custom INF file for Windows. This one works for the devices I have:

https://www.dropbox.com/s/w06b7nj1f07lv29/Windows_ASIC_CDC_Drivers.zip

Check the GridSeed folder. If this doesn't work for you let me know.

Edit: And here's a second pre-release. This includes support for both the 1-chip and 5-chip devices:

https://www.dropbox.com/s/i8cai8x79b79gzo/bfgminer_gridseed_pr2.7z

gigica viteazu`

sr. member

Activity: 458

Merit: 250

beast at work

Quote from: nwoolls on March 09, 2014, 08:31:40 PM

Let me know if you run into any issues. Would love to hear if it works under the Pi (it should). Haven't had a chance to test that yet.

Code:

minepeon@minepeon ~/_tmp/bfgminer-feature-gridseed-support $ ./autogen.sh
Getting submodules...
Running autoreconf -if...
configure.ac:42: installing './compile'
configure.ac:29: installing './config.guess'
configure.ac:29: installing './config.sub'
configure.ac:40: installing './install-sh'
configure.ac:40: installing './missing'
Makefile.am:39: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
Makefile.am: installing './depcomp'

minepeon@minepeon ~/_tmp/bfgminer-feature-gridseed-support $ ./configure --enable-scrypt
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... /usr/bin/mkdir -p
checking for gawk... gawk
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... /usr/bin/grep
checking for egrep... /usr/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 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... yes
checking for libevent... yes
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBUSB... yes
checking for hidapi... no
checking for hidapi... no
checking for hidapi... no
checking whether libusb_error_name is declared... yes
checking what baud rates your system supports... done
checking for best native curses library... ncursesw5
checking whether curses library supports wide characters... yes
checking whether the linker recognizes the -zorigin option... yes
checking for armv6l-unknown-linux-gnueabihf-ldconfig... no
checking for ldconfig... ldconfig
checking libudev.h usability... yes
checking libudev.h presence... yes
checking for libudev.h... yes
checking for LIBCURL... yes
checking for setrlimit... yes
checking for bswap_* functions... found in byteswap.h
checking if bswap_16 is already a macro... yes
checking for platform endian... little endian (endian.h)
checking if good static asserts compile... yes
checking if GNU format attribute compiles... yes
checking for clock_gettime(CLOCK_MONOTONIC)... yes
checking for library containing clock_gettime... none required
checking for clock_nanosleep... yes
checking for clock_gettime(CLOCK_MONOTONIC_RAW)... yes
checking for log2... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating x86_64/Makefile
config.status: creating x86_32/Makefile
config.status: creating ccan.bfg/Makefile
config.status: creating lib/Makefile
config.status: creating 70-bfgminer.rules
config.status: creating config.h
config.status: executing depfiles commands
=== configuring in libblkmaker (/home/minepeon/_tmp/bfgminer-feature-gridseed-support/libblkmaker)
configure: WARNING: no configuration information is in libblkmaker

------------------------------------------------------------------------
bfgminer 3.10.0 configuration options summary
------------------------------------------------------------------------

CFLAGS...............: -pthread -g -O2 -I/usr/include/libusb-1.0 -pthread -Ilibblkmaker
LDFLAGS..............: -pthread -Llibblkmaker/.libs -Wl,-rpath,\$$ORIGIN/libblkmaker/.libs,-zorigin -lpthread -lcurl -ljansson -L/usr/lib -lncursesw -lm -ludev -lusb-1.0 -lblkmaker_jansson-0.1 -lblkmaker-0.1
Installation.prefix..: /usr/local

Enabled..Lowlevel....: pci pci:uio pci:vfio usb vcom
Disabled.Lowlevel....: hid
Enabled..Drivers.....: antminer avalon bifury bigpic bitforce bitforce:uio bitfury_gpio cairnsmore drillbit erupter gridseed hashbusteravalon hashbusterusb hashfast icarus klondike littlefury modminer proxy proxy:getwork proxy:stratum twinfury x6500 ztex
Disabled.Drivers.....: bfsb cpu hashbuster knc metabank nanofury opencl
To enable nanofury, install hidapi
To enable hashbuster, install hidapi
Enabled..Algorithms..: SHA256d scrypt
Disabled.Algorithms..:
Enabled..Options.....: libusb ncursesw5
Disabled.Options.....:

minepeon@minepeon ~/_tmp/bfgminer-feature-gridseed-support $ make
make all-recursive
make[1]: Entering directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support'
Making all in lib
make[2]: Entering directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/lib'
GEN arg-nonnull.h
GEN c++defs.h
GEN warn-on-use.h
GEN signal.h
GEN string.h
make all-recursive
make[3]: Entering directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/lib'
make[4]: Entering directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/lib'
CC dummy.o
AR libgnu.a
make[4]: Leaving directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/lib'
make[3]: Leaving directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/lib'
make[2]: Leaving directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/lib'
Making all in ccan.bfg
make[2]: Entering directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/ccan.bfg'
make[2]: *** No rule to make target '../ccan-upstream/ccan/opt/helpers.c', needed by '../ccan-upstream/ccan/opt/libccan_a-helpers.o'. Stop.
make[2]: Leaving directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support/ccan.bfg'
Makefile:2035: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/minepeon/_tmp/bfgminer-feature-gridseed-support'
Makefile:826: recipe for target 'all' failed
make: *** [all] Error 2

Cassey

sr. member

Activity: 470

Merit: 250

Better to have 100 friends than 100 rubles

I recently have started having some shutdown errors. Program works fine, just generates stuff like what is below when I shutdown via q.

*** Error in `./bfgminer': double free or corruption (out): 0x00000000027a7850 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7e916)[0x7f2d9c732916]
/lib64/libc.so.6(+0x7f6b3)[0x7f2d9c7336b3]
./bfgminer[0x451492]
./bfgminer[0x41644e]
./bfgminer[0x422e99]
./bfgminer[0x4267eb]
/lib64/libpthread.so.0(+0x10b10)[0x7f2d9da3fb10]
/lib64/libpthread.so.0(pthread_cond_wait+0xcc)[0x7f2d9da3bcfc]
./bfgminer[0x40c3e3]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f2d9c6d8bf5]
./bfgminer[0x40d4b5]
======= Memory map: ========
00400000-004b4000 r-xp 00000000 fd:03 2448 /home/litecoin/bfgminer/bfgminer
006b4000-006b5000 r--p 000b4000 fd:03 2448 /home/litecoin/bfgminer/bfgminer
006b5000-006bb000 rw-p 000b5000 fd:03 2448 /home/litecoin/bfgminer/bfgminer
006bb000-006c5000 rw-p 00000000 00:00 0
01d46000-040c7000 rw-p 00000000 00:00 0 [heap]
7f2d58000000-7f2d58021000 rw-p 00000000 00:00 0
7f2d58021000-7f2d5c000000 ---p 00000000 00:00 0
7f2d5c000000-7f2d5c021000 rw-p 00000000 00:00 0
7f2d5c021000-7f2d60000000 ---p 00000000 00:00 0
7f2d60000000-7f2d60021000 rw-p 00000000 00:00 0
7f2d60021000-7f2d64000000 ---p 00000000 00:00 0
7f2d68000000-7f2d68021000 rw-p 00000000 00:00 0
7f2d68021000-7f2d6c000000 ---p 00000000 00:00 0
7f2d6d7fb000-7f2d6d7fc000 ---p 00000000 00:00 0
7f2d6d7fc000-7f2d6dffc000 rw-p 00000000 00:00 0 [stack:9883]
7f2d6dffc000-7f2d6dffd000 ---p 00000000 00:00 0
7f2d6dffd000-7f2d6e7fd000 rw-p 00000000 00:00 0
7f2d6e7fd000-7f2d6e7fe000 ---p 00000000 00:00 0
7f2d6e7fe000-7f2d6effe000 rw-p 00000000 00:00 0 [stack:9881]
7f2d6effe000-7f2d6efff000 ---p 00000000 00:00 0
7f2d6efff000-7f2d6f7ff000 rw-p 00000000 00:00 0
7f2d6f7ff000-7f2d6f800000 ---p 00000000 00:00 0
7f2d6f800000-7f2d70000000 rw-p 00000000 00:00 0
7f2d70000000-7f2d70021000 rw-p 00000000 00:00 0
7f2d70021000-7f2d74000000 ---p 00000000 00:00 0
7f2d74000000-7f2d744ec000 rw-p 00000000 00:00 0
7f2d744ec000-7f2d78000000 ---p 00000000 00:00 0
7f2d78000000-7f2d78021000 rw-p 00000000 00:00 0
7f2d78021000-7f2d7c000000 ---p 00000000 00:00 0
7f2d7c000000-7f2d7c65a000 rw-p 00000000 00:00 0
7f2d7c65a000-7f2d80000000 ---p 00000000 00:00 0
7f2d80000000-7f2d8065a000 rw-p 00000000 00:00 0
7f2d8065a000-7f2d84000000 ---p 00000000 00:00 0
7f2d84387000-7f2d84388000 ---p 00000000 00:00 0
7f2d84388000-7f2d84b88000 rw-p 00000000 00:00 0
7f2d84b88000-7f2d84b89000 ---p 00000000 00:00 0
7f2d84b89000-7f2d85389000 rw-p 00000000 00:00 0 [stack:9877]
7f2d85389000-7f2d8539a000 rw-s 0bf82000 00:05 7538 /dev/ati/card0
7f2d8539a000-7f2d853ab000 rw-s 0bf81000 00:05 7538 /dev/ati/card0
7f2d853ab000-7f2d853bc000 rw-s 0bf80000 00:05 7538 /dev/ati/card0
7f2d853bc000-7f2d853cd000 rw-s 0bf7e000 00:05 7538 /dev/ati/card0
7f2d853cd000-7f2d853de000 rw-s 0bf7d000 00:05 7538 /dev/ati/card0
7f2d853de000-7f2d853df000 ---p 00000000 00:00 0
7f2d853df000-7f2d85bdf000 rw-p 00000000 00:00 0
7f2d85bdf000-7f2d85be0000 ---p 00000000 00:00 0
7f2d85be0000-7f2d863e0000 rw-p 00000000 00:00 0
7f2d863e0000-7f2d863e1000 ---p 00000000 00:00 0
7f2d863e1000-7f2d86be1000 rw-p 00000000 00:00 0 [stack:9871]
7f2d86be1000-7f2d86be2000 ---p 00000000 00:00 0
7f2d86be2000-7f2d873e2000 rw-p 00000000 00:00 0 [stack:9870]
7f2d873e2000-7f2d873e3000 ---p 00000000 00:00 0
7f2d873e3000-7f2d87be3000 rw-p 00000000 00:00 0 [stack:9869]
7f2d87be3000-7f2d87bf6000 r-xp 00000000 08:03 20764 /lib64/libresolv-2.17.so
7f2d87bf6000-7f2d87df6000 ---p 00013000 08:03 20764 /lib64/libresolv-2.17.so
7f2d87df6000-7f2d87df7000 r--p 00013000 08:03 20764 /lib64/libresolv-2.17.so
7f2d87df7000-7f2d87df8000 rw-p 00014000 08:03 20764 /lib64/libresolv-2.17.so
7f2d87df8000-7f2d87dfa000 rw-p 00000000 00:00 0
7f2d87dfa000-7f2d87dff000 r-xp 00000000 08:03 20755 /lib64/libnss_dns-2.17.so
7f2d87dff000-7f2d87ffe000 ---p 00005000 08:03 20755 /lib64/libnss_dns-2.17.so
7f2d87ffe000-7f2d87fff000 r--p 00004000 08:03 20755 /lib64/libnss_dns-2.17.so
7f2d87fff000-7f2d88000000 rw-p 00005000 08:03 20755 /lib64/libnss_dns-2.17.so
7f2d88000000-7f2d8802a000 rw-p 00000000 00:00 0
7f2d8802a000-7f2d8c000000 ---p 00000000 00:00 0
7f2d8c000000-7f2d8c02a000 rw-p 00000000 00:00 0
7f2d8c02a000-7f2d90000000 ---p 00000000 00:00 0
7f2d90000000-7f2d9002a000 rw-p 00000000 00:00 0
7f2d9002a000-7f2d94000000 ---p 00000000 00:00 0
7f2d94008000-7f2d94019000 rw-s 0bf7c000 00:05 7538 /dev/ati/card0
7f2d94019000-7f2d9401a000 ---p 00000000 00:00 0
7f2d9401a000-7f2d9405a000 rw-p 00000000 00:00 0 [stack:9876]
7f2d9408a000-7f2d9409a000 rw-s 0bf72000 00:05 1642 /dev/ati/card2
7f2d9409a000-7f2d940aa000 rw-s 0bf71000 00:05 1642 /dev/ati/card2
7f2d940aa000-7f2d940ac000 rw-s 0bf70000 00:05 1642 /dev/ati/card2

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: gigica viteazu` on March 09, 2014, 08:17:49 PM

any tips to get this build for arch linux on raspberry pi

Follow the normal Linux instructions for cloning and building. It shouldn't take anything special other than making sure you use my repo and branch:

https://github.com/nwoolls/bfgminer/tree/feature/gridseed-support

Let me know if you run into any issues. Would love to hear if it works under the Pi (it should). Haven't had a chance to test that yet.

gigica viteazu`

sr. member

Activity: 458

Merit: 250

beast at work

Quote from: nwoolls on March 09, 2014, 03:25:22 AM

For support for the GridSeed 5-chip devices, if you are feeling crazy you can try this out (Scrypt-only currently):

https://github.com/nwoolls/bfgminer/commits/feature/gridseed-support

I give it the It Works For Me(tm) stamp of approval. Run it with -S gridseed:all and specify frequency with --set-device gridseed:clock=freq, e.g. 850 (default is 600).

any tips to get this build for arch linux on raspberry pi

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