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

[Mudbankkeith]

I'm not sure if this would fall under Mining Hardware or under Mining Software. Though, it does appear to be strictly software-based.
---

Is there any reason why a BeagleBone Black would yield ~30% HWs. But on a PC, only yield ~ 1%?  

Setup:
.............................................-> 9 port self-powered HUB-> 9 erupters
BBB -> 7 port self-powered hub [
.............................................-> 9 port self-powered HUB-> 9 erupters

I've tried CGminer...but couldn't get that to work unless I use a MineNinja. But I get a lot of 'zombie' sticks that just drop out for no reason and remain lit. Doesn't seem to happen with BFGminer though.

I would also note that while running MineNinja, CGminer reports ~1% HW.

---

Would really like to know what's going on as with one software package, I end up with 0 hashing at random times (CGminer). And another, I end up with ~4.6 GH/s (actually recorded by the mining pool's website) of my 6GH/s (BGFminer).

Hub compatibility problems.....not all hubs work with all computers.
Hub power problems.........you need 2.55w at each usb socket,  thats 5v at 510mA,....minimum.............. the hub itself needs between 30% to 50% of the incoming power above this.

[Illutian]

Hub compatibility problems.....not all hubs work with all computers.
Hub power problems.........you need 2.55w at each usb socket,  thats 5v at 510mA,....minimum.............. the hub itself needs between 30% to 50% of the incoming power above this.

The 7 port worked just fine when I ran two of them. Then I got the 9 port hubs, those hubs are the Anker 9port + 1 charger port ((http://www.amazon.com/Charging-Adapter-VL812-B2-Chipset-Firmware/dp/B005NGQWL2)). I would hope that 60 watts is enough

If I run just one 9 port hub the HWs are ~1%. Add the moment I add a second Anker hub they increase to 30%.. But only for BFGminer. And only on a BBB [ARM-based CPU]. BGFminer works fine on the PC using the exact same hubs in the exact same configuration; I literally unplug the USB cable from the BB and plug it into the computer. CGminer has no problems. On either a PC or BBB.

Which is why I posted here. BFGminer clearly has an issue when more that 9 Erupters are being controlled on a BBB (or maybe any ARM-based computer).

[Mbarbian]

Thank You!! 

what you can do is create two different config files each with the settings needed to mine the individual coins


open two cmd windows and navigate to the bfgminer folder


in one:bfgminer.exe -c config.BTC.conf -S BES:\\.\COMxxx .......

in the other: bfgminer.exe -c config.TRC.conf -S BES:\\.\COMyyy

[pmagid]

I am trying to compile and run the latest source from git on my Beagle Bone Black (Angstrom Linux).  I can get it to successfully compile using the instructions I found here: http://forum.kncminer.com/blogs/the-big-countdown/9943-rockin-my-knc-with-bfgminer-on-eligius-st   However, when I run it only the first 7 USB Block Erupters  seem to work on my 49 port hub.  I get the following error:  Work division autodetection failed (assuming 2): got 00000000.  What does this error mean?  Now this hardware works just fine with bfgminer when I plug it into a standard pc running Ubuntu 13.10.  What am I doing wrong?

[Luke-Jr]

NEW VERSION 3.5.0, NOVEMBER 6 2013

Not as big a release as originally planned - I still have a stack of devices waiting for me to write drivers... but they'll come soon. Notably, this release does not include the planned TechnoB⃦it driver due to technical complications with Linux.

Human readable changelog:

• hashbuster: New driver for HashBuster nano ASIC miners.
• littlefury: Updated driver to use latest bitfury code.
• Autodetection support for Windows extended to all VCOM-based devices (instead of just FTDI, libusb, and hidapi); this includes at least ModMiner, Big Picture Mining (BF1, RedFury, BlueFury), and USB Block Erupters.
• Reworked autodetection to scan system devices once and share results with all drivers.

Full changelog:

• bigpic: Probe sooner than most drivers, but still after icarus/erupter
• cpu/opencl: Fix probe priorities to be last
• Bugfix: RPC: Correct per-device Work Utility to be per-minute instead of per-second
• Bugfix: Fix Windows VCOM enumeration to work with new lowlevel code
• Bugfix: nanofury: Use maybe_strdup in case strings may be missing
• Bugfix: bitfury: Fix processor disable/enable for all bitfury-based devices
• hashbuster: Get temperature when available
• Bugfix: hashbuster: Use maybe_strdup where there might not be a string
• hid: Treat null-length strings as missing entirely
• hashbuster: Enable dynamic osc6_bits
• hashbuster: New driver
• Split a hid lowlevel out of mcp2210
• ztex: Convert to use lowlevel usb enumerator
• A quick flag to allow drivers to convey the desire to rescan devices (from lowlevel up)
• Lowlevel USB enumerator for libusb
• dname for lowlevel drivers
• Bugfix: lowlevel: Avoid null pointer dereference on devices that are missing USB strings
• lowlevel: Add a userpointer to lowl_found_devinfo_func_t and use it for serial_autodetect
• Rework VCOM autodetection to go through lowlevel interface, avoiding repeat USB string fetching
• lowlevel: Keep track of the claimed devid and debuglog every found device
• ft232r: devinfo_scan: Don't skip claimed USB devices
• ft232r: Be more tolerant of USB open failure or missing strings
• RPC: Build most of CONFIG "Device Code" by iterating over registered driver list
• drv_detect_all: Use priority-sorted list of registered drivers
• Build hash tables to find drivers by dname or name
• Build a linked list of registered drivers
• BFG_REGISTER_DRIVER macro to commonly pre-define device_drv structures
• Move have_libusb checks out of drv_detect_all
• Replace opt_nogpu with simple function that adds opencl:noauto to scan-serial list
• opencl: Remove ancient gpu_threads variable, not really needed anymore
• Bugfix: Stop waiting for pool testing as soon as one is active
• bitfury: Clean up by making private functions static, and naming public ones with [lib]bitfury_ prefix
• bitfury: Remove old (unused) driver code
• bitfury_gpio: Convert to using current bitfury driver code
• Bugfix: littlefury: Upgrade to use current bitfury driver (old one didn't work with littlefury anymore anyway)
• Bugfix: test_work_current: Make hexstr buffer large enough for blkhashstr later on (issuing old work msg)
• README: Document --enable-knc configure option
• README: Document --disable-nanofury configure option
• Windows autodetect: clear detectone meta info
• Check for Windows DDK headers, and where they are (and build without them if unavailable)
• Windows SetupAPI-based detection for USB VCOM devices (tested with CP210x and CDC)
• ucs2tochar{,_dup} functions to convert USB string descriptors to char* format
• bfg_strerror: Support for Windows system errors
• Introduce applogfail* macros
• Bugfix: scrypt: Add missing include stdbool.h
• Bugfix: Explicitly cast uses of be32toh to uint32_t
• Bugfix: Add missing includes of config.h, stdbool.h, and stdint.h
• lowlevel: Convey device manufacturer up to nanofury cgpus
• nanofury: Store device HID path for RPC
• lowlevel: Promote path to a normal element for devices to simplify things a bit
• nanofury: Claim mcp2210/hid devices
• mcp2210: Implement claim on HID paths
• fpgautils: Use string identifiers for internal hardware claims
• ztex: Keep interface claimed as a lock
• Bugfix: mcp2210: Check for NULL hid device strings before trying to convert them to ASCII
• FTDI autodetect: Enable populating USB product and serial number
• Bugfix: FTDI autodetect: Add missing parameter values and remove unused buffer
• Bugfix: bigpic: Don't active poll event without a poll function

[Mudbankkeith]

Hi Luke-Jr

Not as big as planned? It Big enough!

Lots of extras for us to look for.

Magic .

[Mudbankkeith]

Hi,

I haven't been able to get the USB Erupters to work with 3.5.0 (running Win8.1 x64). They are on COM's 5,12,13,14. I am using the following syntax.

bfgminer-3.5.0-win64\bfgminer.exe -o http://xxxxx -u xxxx.1 -p xxxx-G -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100

But bfgminer isn't detecting them. They last worked with 3.4.0. Are there new commands I need to use?

I'm new to this. Thanks for any help.

Reading the change log I think "  -G -S all  "  is all that's needed, I will have a go now.

[HellDiverUK]

Block Erupters aren't working on 3.5.0 on OpenWRT either.  Tried all the various options, but they're not being picked up.  Same command as always used (screen -dmS bfg bfgminer -S all --http-port 8330).  Tried the --scan-serial options as well.

Unfortunately I'm on an SSH session via LogMeIn to my home PC from work, so I can't see what's physically happening, nor can I cold reboot.   

[Mudbankkeith]

Hi,

I haven't been able to get the USB Erupters to work with 3.5.0 (running Win8.1 x64). They are on COM's 5,12,13,14. I am using the following syntax.

bfgminer-3.5.0-win64\bfgminer.exe -o http://xxxxx -u xxxx.1 -p xxxx-G -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100

But bfgminer isn't detecting them. They last worked with 3.4.0. Are there new commands I need to use?

I'm new to this. Thanks for any help.

I have an update. I was able to get it to work using the following syntax.

bfgminer-3.5.0-win64\bfgminer.exe -o http://xxxx -u xxxx.1 -p xxxx.1 -G --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S //./COM5 -S //./COM12 -S //./COM13 -S //./COM14

Well it looks like bfgminer 3.5.0 isn't able to automatically detect my USB Erupters. Do I need a special syntax or is it that 3.5.0 doesn't do this anymore?

Thanks.

I can get it to work with:-
bfgminer.exe -o http://xxxx -u xxxx.1 -p xxxx.1 -G -S //./COM5 -S //./COM12
with 70 erupters,.... not for now!!!!!!!!!!

Staying with 3.4.0  for now

[hanti]

my usb erupters does not work anymore (debian 7.1 x86)
-S erupter:all doesnt work
-S all doesnt work

[HellDiverUK]

I rolled back to 3.4.0 on OpenWRT and it's all working again, exact same command used between the two.  

3.5.0's Erupter support is confirmed broken.

[hanti]

i had to use this to get it working ./bfgminer -S erupter:/dev/ttyUSB0 -S erupter:/dev/ttyUSB1 -S erupter:/dev/ttyUSB2 ..... till usb45

[disclaimer201]

Can anyone tell me what commands I need to start bfg with to get it to detect the hashbuster nanos? I have two of them connected, but can't find the devices. Thank You!!!!

[juhakall]

With the newest git commit, compiling without libusb doesn't seem to work. If I don't enable any USB device support, the following compile error happens:

bfgminer-miner.o:miner.c:(.text+0x2f16): undefined reference to `__vcom_devinfo_findorcreate'

EDIT: Fixed by new commit

[pmagid]

I am trying to compile and run the latest source from git on my Beagle Bone Black (Angstrom Linux).  I can get it to successfully compile using the instructions I found here: http://forum.kncminer.com/blogs/the-big-countdown/9943-rockin-my-knc-with-bfgminer-on-eligius-st   However, when I run it only the first 7 USB Block Erupters  seem to work on my 49 port hub.  I get the following error:  Work division autodetection failed (assuming 2): got 00000000.  What does this error mean?  Now this hardware works just fine with bfgminer when I plug it into a standard pc running Ubuntu 13.10.  What am I doing wrong?

Anyone have any pointers or ideas...   Sorry for the repost but i am worried my original post got swamped by the new version post and subsequent detection issues.   BTW I have not yet tried the latest version.

[Luke-Jr]

Everyone who had problems with 3.5.0, please test latest git and let me know if I fixed them all...
Windows users can get binaries from http://luke.dashjr.org/tmp/code/webisect/webisect.php?dobuild=bfgminer

[curtiskam]

The newest build again finds my block erupters!  Nice job.

[hanti]

mine are working too

[disclaimer201]

Downloaded the latest version, bfgminer detects my gpus but not my hashbusters. Something about libusb not supported error comes up quickly when I scan for devices. Would I need to start the miner with special commands?

[chamber32]

With 3.5.0 on my RPi, all my USB Erupters work, but not my BFL 5+ GHash.
I have tried starting without a config file and adding pool, but no luck.
I get the error "/dev/ttyUSB0 is already in use by another process"
(I also have a wireless dongle in the RPi, but didn't get this error with 3.4.0.)

Any ideas?

thx,

chamber32