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

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: Mattster28 on November 27, 2013, 03:16:32 PM

Anybody else have their average stat line disappear on ver 3.4.0? The stats for each miner are still showing but the average for both has disappeared. This happened once before so I tried to zero the stats to see if it would come back and well, that didnt work. Had to restart to get them to come back.

I've seen this, but the system with the problem didn't have a debug build Sad

I think hitting DMMM will fix it at least temporarily?

Quote from: jedimstr on November 27, 2013, 03:26:41 PM

Running 3.7.0 compiled using Homebrew.

The running stats log on the second half of the terminal window does not have any line breaks. It updates as one continuous string that just fills the bottom of the screen:

Bug when compiled without unicode support. Already fixed in git.

jedimstr

hero member

Activity: 798

Merit: 1000

Running 3.7.0 compiled using Homebrew.

The running stats log on the second half of the terminal window does not have any line breaks. It updates as one continuous string that just fills the bottom of the screen:

Other than that, I'm loving the quicker start with the Parallel device scanning. I'm getting more blinkies too... you can never have too many blinkies.

Mattster28

full member

Activity: 169

Merit: 100

Anybody else have their average stat line disappear on ver 3.4.0? The stats for each miner are still showing but the average for both has disappeared. This happened once before so I tried to zero the stats to see if it would come back and well, that didnt work. Had to restart to get them to come back.

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Hi Luke-Jr

Set up and working on my win7x86

I had to remove the -G from my bat file, then all was ok.

Thanks for the work.

GaliX

hero member

Activity: 504

Merit: 500

1NtkLdA98eGnsn8nEKpBGRd2VYGNBkGzd6

Thank you very much for your work!

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: HellDiverUK on November 27, 2013, 12:57:07 PM

Quote from: Luke-Jr on November 27, 2013, 11:06:51 AM

NEW VERSION 3.6.0, NOVEMBER 12 2013

oops

HellDiverUK

hero member

Activity: 1246

Merit: 501

Quote from: Luke-Jr on November 27, 2013, 11:06:51 AM

NEW VERSION 3.6.0, NOVEMBER 12 2013

rupy

hero member

Activity: 725

Merit: 503

It was! My wifi card was utter crap! Never buy the cheapest hardware! Thx!

Code:

BFL 0: 66.0C | 59.25/58.01/62.94Gh/s | A:86 R:0+0(none) HW:16/.78%

Luke-Jr

legendary

Activity: 2576

Merit: 1186

NEW VERSION 3.7.0, NOVEMBER 27 2013

Human readable changelog:

Support for new Bi*fury and Twinfury mining devices.
Device probing has been rewritten to scan all devices in parallel (much faster). As a result, the order of devices found is no longer deterministic (consistent) at all.
Parallel device probing makes --device's former syntax unusable, so it has been modified to use the same pattern matching as --set-device. Note that things like --scan-serial ztex:all are now valid, but probably much more dangerous than with VCOM drivers; a bare driverless "all" only affects VCOM drivers for this reason.
Pattern matching for --set-device (and now --device) supports identifying specific devices by serial number or path. To use this, insert either of these between @ symbols where you would have previously put an index. So for example, --device 'BFL@FTWOTOP4' (bitforce device with serial FTWOTOP4) or --set-device '@/dev/ttyUSB0@a:osc6_bits=52' (first processor of device on /dev/ttyUSB0).
BFGMiner-written config files now include the scan-serial and set-device settings.
cpu and opencl drivers have been disabled by default in all cases. Use -S cpu:auto or -S opencl:auto if you need them.
Automatically workaround cgminer driver breakage on Linux.

Full changelog:

FTDI scan: Use intptr_t to avoid warning about different size type cast
Bugfix: proxy: Add missing unistd.h include
Bugfix: bifury: Precision specifications should be int, not size_t
Bugfix: klondike: Include config.h first
Bugfix: binloader: Include config.h first
README.ASIC: Include support URI for bi*fury driver and firmware
Added MultiMiner as an example of a GUI application that wraps bfgminer using the RPC interface
Silence non-issue warnings
bifury: Add support for hwerror message
inc_hw_errors2: Support reporting hw errors without a known nonce
bifury: Initialise cutofftemp to 75 C
bifury: Turn chips off and on when disabled and enabled
bifury: Split out bifury_send_clock
Bugfix: bifury: Avoid double-free and double-close on version parse errors during probe
bifury: Add support for clock command
bifury: Update for "job" protocol change
bifury: Update to current git
bifury: Workaround bugs in older firmware by flooding device with work until it proves it has needwork
bifury: Attempt to submit shares even if maxroll limit is ignored
Clone cgminer's submit_noffset_nonce interface
Bugfix: bifury: Check that there is a line before comparing it to "version "
bifury: Prune jobs older than 16 queued, to eventually clean up discarded work (from flushes)
Replace ucs2tochar* with ucs2_to_utf8* to handle Unicode
README.ASIC: Document Bi*Fury firmware upgrade
bifury: Free work when we know it's complete
bifury: Implement hashrate reporting using "job" messages
bifury: Tolerate other data before version reply
bifury: Abstract line parsing into bifury_readln function
Bugfix: bifury: Use a char array, rather than pointer to char array, for bifury_init_cmds
bifury: Unify SEND devprotodump logging code
fpgautils: Skip SetCommConfig on Windows if baud is not to be set
Check for U+2022 and replace it with "*" is unprintable
Use replacement character for non-printable Unicode
Use UTF-8 for Unicode
Implement a utf8_decode function to produce wchar_t needed by curses
bifury: New driver
Bugfix: twinfury: Handle flash request for both chips, and avoid using proc uninitialised
Bugfix: twinfury: Fix various technicalities
Bugfix: twinfury: Remove incorrect tcflush
Twinfury communication protocol changed to be more robust. A preamble is sent before the actual command.
LED flashing changed: - setting a flag and flash the LED during the poll cycle - mutex removed
Renamed bf2 driver -> twinfury driver bin2hex utility used to convert the serial number
BF2 driver comment edited
BF2 - Twin Bitfury USB miner driver added
Deprecate --ndevs|-n (redundant with -d? and GPU-only)
Never abort startup just because we have no devices (there may be cases this is pointless, but at least it's consistent)
cgpu_match: Accept ranges for letter processor specification
cgpu_match: Accept ranges for numeric elements
test_cgpu_match: Test with more than one device/processor
configure: Condense configuration options summary a bit
configure: Put configuration options summary back after everything completes
Workaround bug in MinGW-w64: Check for strtok_r to be defined at compile-time, and don't override it unless we really want to override
Bugfix: configure: Use new need_lowl_vcom instead of need_fpgautils
configure: Explicitly check for sleep
Bugfix: Set LIBUSB_LIBS for non-pkgconf non-header-subdir libusb installations
Move unused winsock2.h includes to the end of config.h
Use lround instead of llround, since it has better compatibility with older MingW and Cygwin versions
lowl-hid: Save and use hid_enumerate results from library test
Silence Windows build warnings
mcp2210: Remove cruft leftover from HID code (moved out)
lowl-vcom: sysfs scan: Simplify maybe_strdup into _sysfs_do_read
lowl-vcom: sysfs scan: Don't bother getting product string until we confirm it is in fact a tty device
input_pool: Accept a null password
Bugfix: Move const data into the scope it needs to be in
Bugfix: Restore case insensitivity to --scan driver names
Accept "@" separator for serial/path in --scan to match --device and --set-device better
README: Uppercase the sequence letter when talking about multiple pools
README: Mention "make install" and clarify saving settings
Bugfix: avalon: Don't "probe" with -S
bitforce: Add lowl_* to bitforce_queue so it can be specified by name as a driver
Bugfix: devpath_to_devid: Be strict about COM port specifications on Windows
Bugfix: avalon: Don't "probe" with -S all
Bugfix: Only count devices in -d?
RPC: {dev,proc}details: Add 'Processors', 'Manufacturer', 'Product', 'Serial', 'Target Temperature', 'Cutoff Temperature'
debian: Need to explicitly add opencl support to build.
Correctly document klondike as being enabled by default
Simplify logic for README.ASIC and README.FPGA install
Split fpgautils into lowl-vcom and binloader, and fix internal build dependencies
Add README.CPU to "make install" distribution when built with CPU mining support
line 2913 added urlencode
Bugfix: RPC: Release apisock on error in tidyup
klondike - dont try to flush if not initialised
Rename --scan-serial to --scan
Bugfix: Handle invalid driver names cleanly
Workaround libcurl bug to properly support HTTP proxies for stratum
Bugfix: Write klondike options for klondike-options (not icarus options)
README.OpenWrt: Change example repository to "latest", and document alternatives
mcp2210: Add support for --device-protocol-dump
Bugfix: Initialise dynamic osc6_bits variables
README: Fixed a few typos here and there and improved wording (Thanks miningpenguin!)
README: Moved CPU sections to README.CPU and elaborated more on it
README*: Grammatical cleanups
README.ASIC: More KnCMiner
README.ASIC: Add section about KnCMiner
Bugfix: opencl: Dynamic mode should disable threads for this device, not just N after the first
Bugfix: Make curses_input return NULL on a blank line, as most callers expect
Duplicate (hidden) --userpass option before --pool-priority so it can be used in config files
Only probe VCOM devices on bare "all" scan-serial request
Provide backports of uthash LL_{PREPEND,FOREACH{,_SAFE}}2 (only added in 1.9.7, not yet in major distros)
Upgrade required uthash version to 1.9.4 for LL_CONCAT
README: Update documentation for scan-serial
README: Bitstreams no longer included with BFGMiner source
README: Remove incomplete and unnecessary list of ASIC/FPGA devices
write_config: Add scan-serial and set-device
write_config: Update to make JSON Array of named parameters
Remove support for comma-separated values in --device, and update documentation
lowlevel: Collapse multiple lowlevel drivers on the same devid to a secondary linked list, and only spawn one thread to probe all lowlevels on a given devid
Bugfix: vcom_devinfo_scan: Clean up hashtable when done
README: Update cgminer driver FAQ with Windows-specific answer, now that we have a workaround for *nix
cpu/opencl: Always disable by default; removes deprecated -G option entirely
vcom_lowl_probe_wrapper: Attempt to reattach detached USB devices
Bugfix: erupter: Prioritise Emerald after Sapphire
Bugfix: Allow "drv:auto" to override general "noauto"
Bugfix: _probe_device_match: Fix inverted logic
Bugfix: Don't try to call lowl_probe for drivers that don't support that interface
lowl-hid: Use usb devids for libusb-based hidapi devices
Replace bfg_claim_hid with lowlevel_claim
lowlevel: Generic claim interface for lowlevel info
cgpu_match: Compare dev_t under paths
Rework -d? output to display more useful information now that device ordering is non-deterministic
cgpu_match: Add support for matching by serial number or path
Unit tests for cgpu_match
Rework --device option to accept a pattern and JSON Array in config; removes support for processor ranges
Remove --remove-disabled option, as it conflicts with hotplug, per-processor stuff, etc already
Bugfix: Reimplement "noauto" flag
Bugfix: Restore "-S foo" without driver name functionality
Bugfix: scan-serial: Compare dev_t as well
littlefury: Convert to lowl_probe
hashbuster: Convert to lowl_probe
avalon: Convert to lowl_probe
cairnsmore/erupter/icarus: Convert to lowl_probe
bigpic: Convert to lowl_probe
ztex: Convert to lowl_probe
x6500: Convert to lowl_probe
nanofury: Convert to lowl_probe
modminer: Convert to lowl_probe
klondike: Convert to lowl_probe
bitforce: Convert to lowl_probe
fpgautils: Wrapper to easily adapt an old detectone to new lowl_probe
lowlevel: Add match variants of detect functions
DevAPI: add_cgpu: Use mutex to ensure thread safety
Make detectone_meta_info thread-local
New threaded device probe framework

Mudbankkeith

hero member

Activity: 868

Merit: 1000

Quote from: rupy on November 27, 2013, 10:37:29 AM

Is the hardware broken?

Code:

BFL 0: 70.0C | 55.13/56.72/33.15Gh/s | A:1691 R:35+1238( 40%) HW:141/.60%

I tried multiple pools.

What is the device? is it a BFL single? 40% stale sounds line network problem.

Kronkvist

newbie

Activity: 9

Merit: 0

Is there any startup commands for bfg to run a Drillbit systems Thumb on peon ?

If any please share

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: rupy on November 27, 2013, 10:37:29 AM

Is the hardware broken?

Code:

BFL 0: 70.0C | 55.13/56.72/33.15Gh/s | A:1691 R:35+1238( 40%) HW:141/.60%

I tried multiple pools.

Sounds like a bad internet connection.

rupy

hero member

Activity: 725

Merit: 503

Is the hardware broken? Or is it my internet connection?

Code:

BFL 0: 70.0C | 55.13/56.72/33.15Gh/s | A:1691 R:35+1238( 40%) HW:141/.60%

I tried multiple pools.

nov

sr. member

Activity: 433

Merit: 251

Independent crypto developer

I installed BFGMiner 3.5.2 - installed via opkg on DD WRT router TL WR1043nd.

If I try to start bfgminer, I am getting:

bfgminer
Error opening terminal: xterm.

Do you know, what could be the issue, please?

Thanks in advance.

EDIT: Resolved it somehow, it is starting now.

Is BFGMiner 3.5.2 WRT latest version?
Command: opkg find bfgminer, gives me:

opkg find bfgminer
bfgminer - 3.5.2-1 - Modular Bitcoin CPU/GPU/FPGA miner in C

drewage

member

Activity: 262

Merit: 10

Quote from: Luke-Jr on November 26, 2013, 08:47:13 PM

Edit: But do note that earlier Bi*furys shipped with buggy firmware and might not work very well until you upgrade the firmware (see BFGMiner README.ASIC for instructions.

I totally missed this. I'll have to look at it tomorrow. Gotta sleep now.

drewage

member

Activity: 262

Merit: 10

Quote from: Luke-Jr on November 26, 2013, 08:47:13 PM

Quote from: drewage on November 26, 2013, 08:32:19 PM

Well, I can't wait for the next version to come out. I have one of the bi-furies and I can't for the life of me get it recognized and running. I've tried compiling BFGMiner from source and CGMiner from source on Ubuntu. I've tried using precompiled binaries of CGMiner on OS X and I've gotten no love. Mostly it's been unrecognized but when it has been recognized as a bitfury device it hasn't initialized. It can just sit on it's hot little ass until I have more time to screw with it or 3.7 comes out. There's no doubt though, this thing needs a fan. It gets HOT just being plugged in. Undecided

Not sure when(if?) they'll be publishing the Windows INF file, but here's one that should work.

Actually, I don't own a Windows box. Haven't for a couple of years but I might have a Win7 disc buried in the junk pile somewhere. I have an old MacMini I'm dual booting Ubuntu on and that's what I run BFGMiner 3.6.0 on and all my working miners are running off of that box. I was trying to test the red hot using an Ubuntu VM on my MacBook Pro. It shows up on the Mac but even though I've added a filter for it for the VM there's something hinky going on where the Mac isn't letting go of it and sooooo the VM can't use it.

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: drewage on November 26, 2013, 08:32:19 PM

Well, I can't wait for the next version to come out. I have one of the bi-furies and I can't for the life of me get it recognized and running. I've tried compiling BFGMiner from source and CGMiner from source on Ubuntu. I've tried using precompiled binaries of CGMiner on OS X and I've gotten no love. Mostly it's been unrecognized but when it has been recognized as a bitfury device it hasn't initialized. It can just sit on it's hot little ass until I have more time to screw with it or 3.7 comes out. There's no doubt though, this thing needs a fan. It gets HOT just being plugged in. Undecided

Not sure when(if?) they'll be publishing the Windows INF file, but here's one that should work.

Edit: But do note that earlier Bi*furys shipped with buggy firmware and might not work very well until you upgrade the firmware (see BFGMiner README.ASIC for instructions.

drewage

member

Activity: 262

Merit: 10

Well, I can't wait for the next version to come out. I have one of the bi-furies and I can't for the life of me get it recognized and running. I've tried compiling BFGMiner from source and CGMiner from source on Ubuntu. I've tried using precompiled binaries of CGMiner on OS X and I've gotten no love. Mostly it's been unrecognized but when it has been recognized as a bitfury device it hasn't initialized. It can just sit on it's hot little ass until I have more time to screw with it or 3.7 comes out. There's no doubt though, this thing needs a fan. It gets HOT just being plugged in. Undecided

stridergt

newbie

Activity: 9

Merit: 0

I posted the following on the cgminer thread, but since minepeon can utilize bfgminer too, I could use some of your help:

I am using minepeon (cgminer3.6.4) with a Jalapeno and observing that DAcc (Difficulty Accepted) is 60-85% when mining with the eligius pool and 100-105% when mining with BTCguild. (both pools had min difficulty set to auto, but even when I changed BTCguild to 8+GH/s, the difference in percentage roughly stayed the same)
Can someone elaborate a bit on the Dacc calculation and the difference I am observing between the two pools, does it affect my share contribution accordingly???
I checked github, but I was a bit lost. I also asked at the minepeon forum but the dev just parsed the DAcc value and could not elaborate on the calculation method.

Thank you in advance

ikolubr

newbie

Activity: 18

Merit: 0

Quote from: Luke-Jr on November 25, 2013, 07:11:08 PM

Quote from: ikolubr on November 25, 2013, 04:44:05 PM

Hi guys,
I'm new here. I was using CGminer on ubuntu and decided to change to BFGminer. I installed through the PPA. BFGMiner doesn't recognize my BFL's and recognize just one of my usb asicminers, I have 11 of them.
Anything I need to do extra? Do I need to install drivers for them or BFL like in Windows?!

Any ideas?

Thank you,
Igor

From README:

Quote

Q: I ran cgminer, and now BFGMiner doesn't work!
A: cgminer has its own non-standard implementations of the drivers for most USB devices, and disables the official drivers (on Windows, you did this manually using Zadig). Before you can use BFGMiner, you will need to restore the original driver. With Linux, usually rebooting or re-plugging the device is sufficient.

Thank you Sir. Very Appreciated!

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