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

[HellDiverUK]

Finally got BFGMiner running on Debian on my BeagleBone Black.  It's MUCH faster than the RaspberryPi.  I'm running getwork proxy for 65GH and it's running at less than 10% CPU at full speed.  The Pi can't do that for shit.

Trying USB miners later (I think I got hidapi running).

Still looking forward to getting LongPoll support.

[Taugeran]

Finally got BFGMiner running on Debian on my BeagleBone Black.  It's MUCH faster than the RaspberryPi.  I'm running getwork proxy for 65GH and it's running at less than 10% CPU at full speed.  The Pi can't do that for shit.

Trying USB miners later (I think I got hidapi running).

Still looking forward to getting LongPoll support.

I've got hidalgo working on bbb with a few NFY. I remember having to compile libhidapi with --prefix=#####

Can't remember the exact location. Will check make file when I get home

[HellDiverUK]

Finally got BFGMiner running on Debian on my BeagleBone Black.  It's MUCH faster than the RaspberryPi.  I'm running getwork proxy for 65GH and it's running at less than 10% CPU at full speed.  The Pi can't do that for shit.

Trying USB miners later (I think I got hidapi running).

Still looking forward to getting LongPoll support.

I've got hidalgo working on bbb with a few NFY. I remember having to compile libhidapi with --prefix=#####

Can't remember the exact location. Will check make file when I get home

I had no issues, hidapi installed no problems.  The IceFurys are mining perfectly.  I've got approx 90GH going through the BBB between proxies and USB miners.  Less than 20% CPU.

Stats at http://847pool.no-ip.biz:7544/miner.php

[MineForeman.com]

Finally got BFGMiner running on Debian on my BeagleBone Black.  It's MUCH faster than the RaspberryPi.  I'm running getwork proxy for 65GH and it's running at less than 10% CPU at full speed.  The Pi can't do that for shit.

Trying USB miners later (I think I got hidapi running).

Still looking forward to getting LongPoll support.

I've got hidalgo working on bbb with a few NFY. I remember having to compile libhidapi with --prefix=#####

Can't remember the exact location. Will check make file when I get home

Build with;-

git clone https://github.com/signal11/hidapi
cd hidapi
./bootstrap
./configure --prefix=/
make
make install

And bfgminer will pick it up without any options, and I can confirm, the BBB will run the NFY devices fine.

Neil

[HellDiverUK]

Build with;-

git clone https://github.com/signal11/hidapi
cd hidapi
./bootstrap
./configure --prefix=/
make
make install

And bfgminer will pick it up without any options, and I can confirm, the BBB will run the NFY devices fine.

Neil

I didn't even need to use the --prefix=/ part, and it all worked.

[MineForeman.com]

Update on my investigations on ARM and NFY;-

Arch Linux on x86/64 bfgminer 3.9.0 = No problems, works as expected.

Arch Linux on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.

Rasberian on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.

Arch Linux on CubieBoard2 (ARMv7) bfgminer 3.9.0 = Detects, initializes, bfgminer often has to reset the NFY's because the hashrate falls below 50%, often segfaults and core dumps.

Arch Linux on BeagleBone Black (ARMv7) bfgminer 3.9.0 = Detects, initializes, occasionally segfaults and core dumps.  Does not handle unplug events and a restart (of bfgminer or the ARM device) will often leave the NFY's locked.

As a note, all other hardware drivers that I can test (BFL, ICA, BPM, ZTX) work fine on all platforms.

My build scripts are;-

hidapi (the necessary library)

Code:

git clone https://github.com/signal11/hidapi
cd hidapi
./bootstrap
./configure --prefix=/
make
make install
cd ..

bfgminer

Code:

git clone https://github.com/luke-jr/bfgminer.git
cd bfgminer
./autogen.sh
./configure 
make
make install

Is anyone experiencing anything different?  If so, can I possibly grab an image of the OS from you so I can compare/see what is different.

Neil

[nwoolls]

Arch Linux on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.
...

Is anyone experiencing anything different?  If so, can I possibly grab an image of the OS from you so I can compare/see what is different.

This is what I get with Ice Fury along with MinePeon compiled with NanoFury support:

 

Code:

[2014-01-03 02:41:42] Started bfgminer 3.9.0
 [2014-01-03 02:41:43] Probing for an alive pool
 [2014-01-03 02:41:43] Pool 0 http://192.168.0.15:3333 alive
 [2014-01-03 02:41:43] Network difficulty changed to 1.42G (10.15Ph/s)
 [2014-01-03 02:41:43] Stratum from pool 0 detected new block
 [2014-01-03 02:41:43] Pool 0 is hiding block contents from us
 [2014-01-03 02:41:45] NFY 0: Previous nonce mismatch (4th try), recalibrating
 [2014-01-03 02:41:45] mcp2210_spi_transfer: Failed to continue SPI transfer (1 bytes remaining)
 [2014-01-03 02:41:47] mcp2210_spi_transfer: Failed to continue SPI transfer (59 bytes remaining)
 [2014-01-03 02:41:47] NFY 0 failure, attempting to reinitialize
 [2014-01-03 02:41:47] mcp2210_set_cfg_spi: Error setting current SPI config (248)
 [2014-01-03 02:41:47] mcp2210_set_cfg_spi: Error setting current SPI config (248)
 [2014-01-03 02:41:48] NFY 0 failure, disabling!
 [2014-01-03 02:41:49] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:49] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:50] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:50] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:51] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:52] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:52] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:56] mcp2210_spi_transfer: Failed to continue SPI transfer (59 bytes remaining)
 [2014-01-03 02:41:56] NFY 0 failure, disabling!
 [2014-01-03 02:41:56] mcp2210_set_cfg_spi: Error setting current SPI config (248)
 [2014-01-03 02:41:56] mcp2210_set_cfg_spi: Error setting current SPI config (248)
 [2014-01-03 02:41:56] NFY 0 failure, disabling!
 [2014-01-03 02:41:56] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:56] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:57] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:58] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:58] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:59] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:41:59] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:42:00] mcp2210_set_cfg_spi: Failed to set current SPI config
 [2014-01-03 02:42:02] mcp2210_spi_transfer: Failed to continue SPI transfer (59 bytes remaining)
 [2014-01-03 02:42:02] NFY 0 failure, disabling!
 [2014-01-03 02:42:02] mcp2210_set_cfg_spi: Error setting current SPI config (248)
 [2014-01-03 02:42:02] mcp2210_set_cfg_spi: Error setting current SPI config (248)
 [2014-01-03 02:42:02] NFY 0 failure, disabling!
 [2014-01-03 02:42:02] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:42:02] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:42:03] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:42:04] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:42:04] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:42:05] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:42:05] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries
 [2014-01-03 02:42:06] NFY 0: bitfury_init_oldbuf: Giving up after 4 tries

Occasionally I get a few accepted shares first.

[Luke-Jr]

Update on my investigations on ARM and NFY;-

Arch Linux on x86/64 bfgminer 3.9.0 = No problems, works as expected.

Arch Linux on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.

Rasberian on Raspberry Pi (ARMv6) bfgminer 3.9.0 = Detects but cannot initialize, often segfaults and core dumps.

Arch Linux on CubieBoard2 (ARMv7) bfgminer 3.9.0 = Detects, initializes, bfgminer often has to reset the NFY's because the hashrate falls below 50%, often segfaults and core dumps.

Arch Linux on BeagleBone Black (ARMv7) bfgminer 3.9.0 = Detects, initializes, occasionally segfaults and core dumps.  Does not handle unplug events and a restart (of bfgminer or the ARM device) will often leave the NFY's locked.

Curious you have trouble on non-RPI platforms too...
Can you post backtraces for those crashes?

[MineForeman.com]

Occasionally I get a few accepted shares first.

Very similar to what I get, I have not noticed any shares though (I have not really been looking though).

The Pi is defiantly most effected of the ARM systems, a bit understandable it being ARMv6 with a dodgy USB controller.  I just tried Pidora (a Fedora Remix) with the same results as Arch and Rasperian.

Neil

[MineForeman.com]

Can you post backtraces for those crashes?

No worries, I will just reload/recompile "-g" on the CubeBoard2 and get back to you.  It seems to have the most 'intresting' results.

Neil

[dave111223]

Any chance bfgminer will have built-in Antminer U1 support anytime soon?

[Taugeran]

Any chance bfgminer will have built-in Antminer U1 support anytime soon?

He's a working on it. Ljr just moved into a new house. So give em a few

[HellDiverUK]

On the BBB one of my IceFurys (NFY0) gives lots of 'dropped nonces' errors on startup, the other (NFY1) is perfect.  NFY0 eventually stabilises after about a minute and runs fine.  I have nowhere near the errors listed by Nate.

As I said, I'm running Debian on the BBB with bfg compiled from source.

[Mudbankkeith]

My Antminers are here.

Hashing on a rPi but only at 500Mh/s

[philipma1957]

My Antminers are here.

Hashing on a rPi but only at 500Mh/s

I am getting 2 gh with windows 7 and the custom cgminer build..  waiting on luke to get ant miners set for bfgminer.


At luke-jr how is you new home?   nice a new home and a new year wrapped into one.   good luck with it.


Ps I sent  a small amount of BTC  for a house warming gift.

[CanaryInTheMine]

I have an instance of bfgminer proxy running on port 8332.

starting another one on different port:


reproducible with other port combinations and on both win 7 and 8

what am i doing wrong?

not an issue with prior to 3.9.0 versions of bfgminer.

[HellDiverUK]

reproducible with other port combinations and on both win 7 and 8

what am i doing wrong?

not an issue with prior to 3.9.0 versions of bfgminer.

That's weird, I've got 3.9.0 running on Windows 7, OpenWRT, Debian and whatever MinePeon runs on, and I've not seen this.

[CanaryInTheMine]

reproducible with other port combinations and on both win 7 and 8

what am i doing wrong?

not an issue with prior to 3.9.0 versions of bfgminer.

That's weird, I've got 3.9.0 running on Windows 7, OpenWRT, Debian and whatever MinePeon runs on, and I've not seen this.

it ignores the specified port number and instead  binds on same port as the 1st instance of bfgminer running in proxy... weird indeed

[HellDiverUK]

Something borked with libmicrohttpd?

[MineForeman.com]

Curious you have trouble on non-RPI platforms too...
Can you post backtraces for those crashes?

So frustrating, with -g (for gdb to work) it now hangs instead of dumping or does something like this;-

Code:

 [2014-01-03 15:32:45] Accepted 0bdcc753 NFY 2  pool 0 Diff 21/3
 [2014-01-03 15:32:48] Accepted 50870b4b NFY 1  pool 0 Diff 3/3
 [2014-01-03 15:32:49] NFY 0: Frequency drop over 50% detected, reinitialising
 [2014-01-03 15:32:51] Accepted 10cd03da NFY 2  pool 0 Diff 15/3
 [2014-01-03 15:32:53] NFY 1: Frequency drop over 50% detected, reinitialising
 [2014-01-03 15:32:58] Stratum from pool 0 requested work update
 [2014-01-03 15:32:58] Stratum from pool 0 requested work update
 [2014-01-03 15:32:59] NFY 2: Frequency drop over 50% detected, reinitialising
 [2014-01-03 15:33:01] NFY 0: Frequency drop over 50% detected, reinitialising
 [2014-01-03 15:33:06] Accepted 221a7e06 NFY 2  pool 0 Diff 7/4
 [2014-01-03 15:33:08] Accepted 1fa212cc NFY 1  pool 0 Diff 8/4
 [2014-01-03 15:33:09] NFY 2: Frequency drop over 50% detected, reinitialising
 [2014-01-03 15:33:09] Accepted 1deb4a50 NFY 0  pool 0 Diff 8/4
 [2014-01-03 15:33:15] NFY 0: Frequency drop over 50% detected, reinitialising
 [2014-01-03 15:33:15] Accepted 1f343916 NFY 0  pool 0 Diff 8/4
 [2014-01-03 15:33:22] Accepted 3b47e48e NFY 2  pool 0 Diff 4/4
 [2014-01-03 15:33:22] NFY 2: Frequency drop over 50% detected, reinitialising
 [2014-01-03 15:33:24] NFY 1: Frequency drop over 50% detected, reinitialising
 [2014-01-03 15:33:24] Accepted 00c13a9e NFY 0  pool 0 Diff 339/4
 [2014-01-03 15:33:26] Accepted 283cab17 NFY 0  pool 0 Diff 6/4
 [2014-01-03 15:33:27] NFY 0: Frequency drop over 50% detected, reinitialising
 [2014-01-03 15:33:29] Stratum from pool 0 requested work update
 [2014-01-03 15:33:34] NFY 1: Frequency drop over 50% detected, reinitialising
 [2014-01-03 15:33:35] NFY 0: Frequency drop over 50% detected, reinitialising
 [2014-01-03 15:33:35] NFY 2: Frequency drop over 50% detected, reinitialising

Or just does not detect the devices at all.

I am not sure what to do now, any advice would be appreciated.

Neil