Bitcoin Forum
April 24, 2014, 11:51:58 PM *
News: Due to the OpenSSL heartbleed bug, changing your forum password is recommended.
 
   Home   Help Search Donate Login Register  
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 ... 160
  Print  
Author Topic: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB, HFA  (Read 576585 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
Luke-Jr
Hero Member
*****
Offline Offline

Activity: 1218



View Profile

Ignore
April 05, 2013, 06:53:14 PM
 #1

Announcing BFGMiner 3.10, the modular ASIC/FPGA miner written in C. BFGMiner features dynamic clocking, monitoring, and remote interface capabilities.

"St. Barbara's Faithfully Glorified Mining Initiative Naturally Exceeding Rivals", or just basically a freaking good miner.

This code is provided entirely free of charge by the programmer, so donations would be greatly appreciated.
Please consider donating: 1QATWksNFGeUJCWBrN4g6hGM178Lovm7Wh
If you are donating for a specific bugfix/feature request, please post the Issue number and it will be flagged as "funded".

If you find a bug or have a suggestion, please check to see if it's already been reported and, if not, report it.
Help can also be obtained (or provided) by joining the support mailing list or IRC: chat.freenode.net #eligius
READ THE README INCLUDED IN THE ARCHIVE BEFORE ASKING QUESTIONS.
Also, please note that this thread is for discussion of BFGMiner, its features and bugs - if you feel the need to troll or talk off-topic, start another forum thread (and PM me with it if you want my attention).

If you want to help develop BFGMiner, the best way to get in touch with me is on IRC.
We also have a development mailing list, mainly used to pre-announce upcoming releases for third-party packagers.

If you would like to be notified of new versions, please join the announcement mailing list.

For miners using ModMiner, X6500, or ZTEX devices, you will need to download bitstreams for BFGMiner 3+ to work with your device. Download links and instructions are included in the README.FPGA file.

Latest release: 3.10.0 (announcement & changes)Stable release: 3.5.7
Archive of all official release source & binaries

Features:
Sample output:
Code:
bfgminer version 3.10.0 - Started: [2013-08-20 02:03:56] - [  0 days 00:35:05]
 [M]anage devices [P]ool management [S]ettings [D]isplay options  [H]elp [Q]uit
 Connected to mining.eligi.us diff 32 with stratum as user 1QATWksNFGeUJCWBrN4g6hGM178Lovm7Wh
 Block: ...a83dc890 #249720  Diff:31.3M (223.8Th/s)  Started: [01:22:11]
 ST:10  F:0  NB:5  AS:0  BW:[341/153 B/s]  E:89.27  I: 6.58mBTC/hr  BS:89.7k
 7/36   77.0°C │ 90.13/91.42/92.50Gh/s │ A:2171 R:7+0(.49%) HW:430/.62%
───────────────┼───────────────────────┼────────────────────────────────────────
 BFL 0: 65.9°C │ 877.7/871.2/940.5Mh/s │ A:  20 R:0+0(none) HW:  0/none
 BFL 1: 68.0°C │ 30.58/29.63/30.37Gh/s │ A: 733 R:3+0(.64%) HW:  8/.05%
 BFL 2: 78.0°C │ 56.98/58.81/59.58Gh/s │ A:1379 R:4+0(.44%) HW:195/.68%
 MMQ 0: 50.0°C │ 799.8/785.1/537.3Mh/s │ A:  15 R:0+0(none) HW: 21/5.7%
 XBS 0: 48.2°C │ 398.0/400.3/ 8.18Mh/s │ A:   4 R:0+0(none) HW: 51/ 25%
 ZTX 0:        │ 198.5/197.6/196.7Mh/s │ A:   3 R:0+0(none) HW: 27/none
 ZTX 1:        │ 849.0/836.6/992.4Mh/s │ A:  20 R:0+0(none) HW:129/.70%
───────────────┴───────────────────────┴────────────────────────────────────────
 [2013-08-02 02:38:58.462496] Accepted 0321a601 BFL 2p pool 0 Diff 81/32
 [2013-08-02 02:38:59.007820] Accepted 00c348b2 BFL 2d pool 0 Diff 335/32
 [2013-08-02 02:38:59.133534] Accepted 05b3443a BFL 2n pool 0 Diff 44/32
 [2013-08-02 02:38:59.785127] Accepted 07563198 ZTX 1a pool 0 Diff 34/32
---
Pool menu:
Code:
0: Enabled  Strtm Priority 0: stratum+tcp://stratum.mining.eligius.st:3334  User:1QATWksNFGeUJCWBrN4g6hGM178Lovm7Wh
1: Disabled GWork Priority 1: http://127.0.0.1:9332  User:x

Current pool management strategy: Load Balance
[A]dd pool [R]emove pool [D]isable pool [E]nable pool
[C]hange management strategy [S]witch pool [I]nformation
Or press any other key to continue

Device management menu:
Code:
Select processor to manage using up/down arrow keys
 MMQ 0d: 41.0°C │ 194.0/190.9/32.98Mh/s │ A:   4 R:0+0(none) HW: 0/none
  ModMiner LJRalpha  from BTCFPGA
Serial: 19191F145358077D4FAADA7AF5000004
Clock speed: 194

[D]isable [C]lock speed
Or press Enter when done
Code:
Select processor to manage using up/down arrow keys
 OCL 0 : 77.0C | 272.2/272.2/265.7Mh/s | A:2992 R:13+0(.43%) HW:0/none
I:10  F: 69% (2655 RPM)  E: 765 MHz  M: 1000 MHz  V: 1.088V  A: 99%  P: 0%
Last initialised: [2013-07-08 05:33:26]
Thread 0: 90.9 Mh/s Enabled ALIVE
Thread 1: 90.6 Mh/s Enabled ALIVE
Thread 2: 90.8 Mh/s Enabled ALIVE

[D]isable [I]ntensity [R]estart GPU [C]hange settings
Or press Enter when done

Change GPU settings menu:
Code:
Temp: 72.0 C
Fan Speed: 50% (4489 RPM)
Engine Clock: 950 MHz
Memory Clock: 825 Mhz
Vddc: 1.175 V
Activity: 99%
Powertune: 20%
Fan autotune is enabled (0-85)
GPU engine clock autotune is enabled (880-950)
Change [A]utomatic [E]ngine [F]an [M]emory [V]oltage [P]owertune
Or press any other key to continue

Settings menu:
Code:
[L]ongpoll: On
[Q]ueue: 0
[S]cantime: 60
[E]xpiry: 120
[R]etries: -1
[W]rite config file
[B]FGMiner restart
Select an option or any other key to return

Display menu:
Code:
[N]ormal [C]lear [S]ilent mode (disable all output)
[D]ebug:off
[P]er-device:off
[Q]uiet:off
[V]erbose:off
[R]PC debug:off
[W]orkTime details:off
su[M]mary detail level:devices
[L]og interval:5
[Z]ero statistics
Select an option or any other key to return


On exiting:
Code:
Summary of runtime statistics:

Started at [2011-07-19 14:40:09]
Runtime: 2 hrs : 31 mins : 18 secs
Average hashrate: 1680.1 Megahash/s
Solved blocks: 0
Best share difficulty: 49
Share submissions: 3489
Accepted shares: 3489
Rejected shares: 0 + 9 stale (0.00%)
Accepted difficulty shares: 32
Rejected difficulty shares: 0
Hardware errors: 3
Efficiency (accepted shares * difficulty / 2 KB): 0.05
Utility (accepted shares / min): 34.26/min

Unable to get work from server occasions: 16
Work items generated locally: 330
Submitting work remotely delay occasions: 33
New blocks detected on network: 10

Pool: http://getwork.mining.eligius.st:8337
 Share submissions: 3426
 Accepted shares: 3426
 Rejected shares: 0 + 0 stale (0.00%)
 Accepted difficulty shares: 31
 Rejected difficulty shares: 0
 Efficiency (accepted * difficulty / 2 KB): 0.08
 Unable to get work from server occasions: 0
 Submitting work remotely delay occasions: 0

Summary of per device statistics:

 ICA 0:       | 375.9/376.0/349.5Mh/s | A: 487 R:4+0(none) HW:  0/none
 MMQ 0: 46.0C | 629.9/632.0/526.8Mh/s | A: 734 R:0+0(none) HW:196/none
 XBS 0: 46.9C | 392.0/397.8/398.3Mh/s | A: 555 R:0+0(none) HW: 57/none
 ZTX 0:       | 198.6/198.5/190.2Mh/s | A: 265 R:0+0(none) HW: 95/none
 ZTX 1:       | 855.0/848.7/825.3Mh/s | A:1150 R:4+0(none) HW:176/none

1398383518
Hero Member
*
Offline Offline

Posts: 1398383518

View Profile Personal Message (Offline)

Ignore
1398383518
Reply with quote  #2

1398383518
Report to moderator
Unbeatable Service & Product Support
Grab Your Miners at GAWMiners.com
Order Before April 25th to receive
Double your Hashing Power for 1 week!

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1398383518
Hero Member
*
Offline Offline

Posts: 1398383518

View Profile Personal Message (Offline)

Ignore
1398383518
Reply with quote  #2

1398383518
Report to moderator
1398383518
Hero Member
*
Offline Offline

Posts: 1398383518

View Profile Personal Message (Offline)

Ignore
1398383518
Reply with quote  #2

1398383518
Report to moderator
1398383518
Hero Member
*
Offline Offline

Posts: 1398383518

View Profile Personal Message (Offline)

Ignore
1398383518
Reply with quote  #2

1398383518
Report to moderator
Luke-Jr
Hero Member
*****
Offline Offline

Activity: 1218



View Profile

Ignore
April 05, 2013, 06:54:39 PM
 #2

NEW VERSION 3.0.0, APRIL 5 2013

Please note that libcurl 7.29.0 has a socket leak with request failures, which can lead to BFGMiner running out of file descriptors and/or crashing if you have a dead pool! All older and newer versions of libcurl should be fine.

Also note that if you are compiling from git yourself, you must manually run configure after autogen.sh - it is no longer run automatically to be consistent with how every other software package does this.

2.10.6 is also released and promoted to stable. Note it does not support ASICs.

Human readable changelog:
  • New device driver for ASIC devices, including both Butterfly Labs' BitForce SC and Avalon.
  • Enhanced device driver API, enabling devices to asynchronously handle multiple slave processors. Use --show-processors to view each individually (not yet supported for Avalon).
  • You can now use --request-diff <difficulty> to ask for a specific share target from pools that support BIP 23 GBT Basic Pool Extensions.
  • Support for submitting found blocks to a local Bitcoin GBT server (bitcoind or Bitcoin-Qt with -server flag): just append #allblocks to the end of your bitcoind's URI.
  • Stratum connection resuming support - if you lose an active stratum connection, BFGMiner will attempt to resubmit any lost shares when it reconnects.
  • Android target support. You will have to compile it yourself, but it should just work - no patching needed.
  • New Python RPC client example from Christian Berendt.

Full changelog
  • debian: Include new api-example.py in docs
  • added example for Python using the RPC API
  • added SPEC file for SUSE distributions
  • Bugfix: bitforce: Free initialization data to avoid trivial one-time memory leak
  • Support for local submission of found blocks (GBT only)
  • bitforce: RPC pgaset fanmode 0-5 for manual fan control
  • bitforce: More debugging information
  • Bugfix: modminer: Since RPC always includes the temperature, we don't need to add it specially
  • bitforce: Expose dual temperature sensors to RPC
  • bitforce: Support for up to 2 temperature sensors per processor
  • Bugfix: bitforce: BFP_QUEUE: Attempt to recover from extra queue results, or the next job finishing early
  • bitforce: Always send a new job ASAP after flushing the queue
  • bitforce: Implement "Queue Job Pack" (ZWX) and use it for XLINK devices to avoid USB latency issues
  • bitforce: Ignore INPROCESS added to ZOX response
  • Implement minerloop_queue for devices that process work items too fast to keep track of which one they're currently working on
  • bitforce: Split ZOX command into its own function
  • Bugfix: DevAPI: Free work when preparing it fails
  • DevAPI: Abstract get_and_prepare_work for minerloops
  • DevAPI: Move select() logic from minerloop_async to do_notifier_select
  • Clarify stratum mining.set_difficulty debug log message
  • No longer call configure from autogen.sh
  • Bugfix: bitforce: Ensure result_busy_polled gets set for queue mode to avoid unnecessary 10ms wait times
  • Bugfix: bitforce: Use common code for end of job_get_results, so queue results don't short-circuit timing code
  • Bugfix: bitforce: Ensure "OK" doesn't remain in queued results buffer
  • Bugfix: bitforce: next_line needs to increment beyond the newline character
  • Update README for x970 memdiff values.
  • Do not scan other gpu platforms if one is specified.
  • Update README for sync objects on windows.
  • Add information for setting gpu max alloc and sync parameters for windows with scrypt.
  • Whitelist AMD APP SDK 2.8 for diablo kernel.
  • Show pool number in switch message
  • Clear just the socket buffer when we don't care what is left in a stratum socket.
  • Clear the stratum socket whenever we are closing it since the buffer is going to be reused.
  • Do not continue work from a stratum pool where the connection has been interrupted.
  • Close any existing stratum socket if we are attempting to restart stratum so the pool knows the connection has gone.
  • Show mechanism of stratum interruption if select times out.
  • Make stratum connection interrupted message higher priority to be visible at normal logging levels.
  • API add 'Network Difficulty' to 'coin'
  • avalon: if all result are wrong in one batch read. reinit the avalon
  • avalon: record the last result temperature info
  • delay when close avalon; only record matched result
  • avalon: fix no_matching_work only count when debug
  • avalon: minor change
  • avalon: add idle code
  • avalon: fliter the temp_max >= 100, print the result for debug.
  • avalon: export more data to API stats
  • avalon: add default chip frequency
  • avalon: fix the work_i3 init
  • avalon: add reinit_device
  • avalon: the temp_history_count base on timeout
  • avalon: fix mistake on adjest_fan
  • avalon.c: fix the copyright
  • bfgminer-rpc: add -o option: no format, only the result
  • avalon: update fan pwm
  • avalon: update the FAN_PWM MAX/MIN
  • avalon: minor change
  • avalon: overclock code
  • avalon: fix the display
  • avalon: minor change
  • avalon: fix the fan/temp control
  • avalon: fix the temp_avg
  • avalon: fix temp
  • avalon: add fan/temp control
  • avalon: add FAN speed factor
  • avalon: add TODO on fan/temp control. cleanup detect
  • avalon: add the gate_miner bits
  • avalon: only send one byte on reset
  • avalon: add support on send 2 bulk taskes at begin
  • avalon: fix the hash_count return
  • avalon: fix the LOG_WARNING
  • avalon: add comment on hash_count
  • avalon: WORKAROUND on hashrate
  • avalon: update max miner_num
  • avalon: add more info on api
  • avalon: add nonce_elf and more info on match miner_num
  • avalon: change reset to 300ms
  • avalon: move bulk buffer to it's info structrue
  • avalon: more work on hashrate and read_count
  • avalon: add baud 38400 support
  • avalon: fix nonce_range EB
  • avalon: fix the hashrate wrong
  • more info on avalon API
  • avalon: fix the nonce_range EL
  • avalon: fix the read count
  • avalon: more work on nonce_range
  • avalon: read() times and send delay fixed
  • avalon: add the send delay option
  • avalon: print out fan/temp info
  • avalon: add the result info (fan/temp etc)
  • avalon: more check on hardware error
  • avalon: more work on get_work_count
  • avalon: now we have dynamic get_work_count
  • avalon: more work on parameters
  • avalon: add timeout parameter
  • avalon: baud as parameter now
  • avalon: send work pitch should be : (15*(8+2)*4/19200)s
  • avalon: more work on match work
  • avalon: fix free_work
  • avalon: continue on reset work. wait for buffer empty
  • avalon: add options, if write() error. sleep(1) before reset()
  • avalon: more cleanup
  • avalon: finish read when Buffer empty
  • avalon: fix the nonce EB issue
  • avalon: MORE work
  • avalon: fix the EB/LB issue
  • avalon: some cleanup
  • avalon: fix the first configure task
  • more work on the avalon buffer
  • avalon: fix the BIG_ENDIAN issue
  • avalon: Fix the buffer statu
  • change defines to avalon parameters
  • fix the cts return
  • avalon: change the data to uint8_t, add some test temp code
  • avalon: fix task init
  • avalon: more data format work
  • change to avalon data format
  • debug: add a debug hexdump.c
  • avalon: add some code on match work
  • avalon: try to correct the pool_status and dev_status
  • avalon: more work on multi-works
  • avalon: more work on read
  • avalon: more work on get results
  • more RTS code on avalon.c/h
  • more RTS code
  • avalon: some cleanup
  • avalon: more work on new work queue structrue
  • fpgautils.c: use lancelot as target
  • avalon: since we submit task as bulk data. modify again
  • add scanhash_queue
  • renmae avalon.h to driver-avalon.h
  • fpgautils.c: add get_serial_cts
  • understand the avalon protocol more
  • avalon: new software structrue but target as lancelot
  • add avalon.h
  • avalon: fix warning
  • avalon: add TODO comments
  • more AVALON defines
  • avalon: more work
  • add driver-avalon.c
  • add avalon support to automake
  • Default to work queue mode on BitForce SC devices
  • bitforce: Implement support for non-contiguous XLINK slave addressing
  • gnulib: stdint: fix build with Android's Bionic fox x86
  • gnulib: stdint: Improve support for Android.
  • gnulib: stdint: Add support for Android.
  • Check for ?e##toh macros independently from hto?e##
  • If pthread_cancel is missing/emulated, set asynchronous thread cancel type on stage, watchdog, watchpool, and longpoll threads since the emulation cannot support deferred cancellation
  • If pthread_cancel is missing (Bionic/Android), emulate it using pthread_kill and pthread_exit
  • configure: Intelligently detect what flags/libs get us working pthread, and define HAVE_PTHREAD_CANCEL if pthread_cancel is available
  • Bugfix: Initialize mutex_request to invalid so devices that don't use it (bitforce) don't try to
  • RPC: pools: Add "Message" to show last client.show_message received over stratum
  • Stratum: Support client.show_message method
  • Don't retry without resume support, if the first attempt just timed out
  • Bugfix: minerloop_async: Intelligently handle work updates and device disables during transitions
  • Bugfix: minerloop_async: Free old (unused) prepared work when replacing it with an upgraded one
  • Bugfix: Free pool sessionid before replacing it
  • Bugfix: Stratum: Address dereference-after-free and memory leak introduced in resume support
  • Stratum: If old protocol fails as well, try to resume again next time around
  • Bugfix: Stratum: Only failover to old mining.subscribe protocol if the previous attempt was the new one (fixes a flood of retries)
  • Try to extract the sessionid associated with mining.notify on 3rd level array and submit it along with the userid to support mining resume, failing gracefully and restarting if the pool rejects it.
  • Cope with misread sessionid on stratum for now.
  • Use the sessionid as passed on stratum connect to attempt to resume a connection once and then clear it if it fails, to use a new connection.
  • Move to storing the nonce1 in the work struct instead of the sessionid for the now defunct first draft mining.resume protocol.
  • Only continue submitting shares with mining.resume support on stratum when the session id matches.
  • Provide support for mining.resume with stratum, currently re-authorising after successful resumption pending finalising of the protocol process.
  • Provide basic framework for restarting stratum depending on whether resume support exists or not.
  • Abstract out the setting up of the stratum curl socket.
  • Remove redundant setting of strings to NULL since the whole work struct is zeroed.
  • Only clear stratum shares mandatorily on stratum dropouts when the pool does not support resume.
  • Stratum: Keep trying to submit shares, even across reconnects
  • Use new select loop primitives in submission thread
  • Bugfix: Missing pool_no parameter to applog for no-stratum-sessionid debug message
  • Do as much outside of mutex locking of sshare_lock as possible.
  • Remove last reference to struct work used outside the sshare_lock in submit_work_thread
  • Unlock the sshare_lock in submit_work_thread when all references to work and sshare are complete.
  • Bugfix: Copy and free sessionid on work objects
  • Add timestamps to stratum_share structs as they're generated and copy the stratum sessionid if it exists to stratum work generated.
  • Store session id for stratum if the pool supports it for future mining.resume support.
  • Keep the unique id of each work item across copy_work to prevent multiple work items having the same id.
  • x6500: Never consider processors idle if they're enabled
  • x6500: Make mutex management cleaner by blocking device select loop during idle get_stats
  • Bugfix: minerloop_async: Always refer to real thread for select loop
  • Bugfix: Initialize work_restart_notifier[1] to INVSOCK instead of -1 to be portable
  • ztex: Use restart_wait to react quicker to work updates
  • Handy TIMEVAL_USECS macro
  • Restore blocking restart_wait function with nearly identical semantics as old one
  • Bugfix: bitforce: Rework sleep delay adjustment logic to properly deal with more accurate timing readings (added in device API update)
  • Hidden --force-rollntime option for getwork pools (use like --pool-priority, after each pool definition)
  • Include processor id in get_work logging
  • Support for BIP23 BPE request target extension via new --request-diff option
  • Hidden option to reduce "work update" messages to debug level: --quiet-work-updates
  • Change "work restart" to "work update" in messages to reflect reality more accurately (no work is lost), and normalize case of "longpoll"
  • HACK: Since get_work still blocks, reportin all processors dependent on this thread
  • Move FD_SETSIZE definition to configure so it affects everywhere it needs to
  • Move absolute_uri function to util.c
  • Remove now-unused blocking-wait code (restart_cond, restart_wait, and stale_wait)
  • Bugfix: bitforce: Zero hashes complete if we get an invalid response
  • HACK: Since get_work still blocks, reportout all processors dependent on this thread
  • bitforce: Support for work queue protocol on BitForce SC devices
  • Use new double-stage format for SC devices
  • modminer+x6500: Expose frequencies to API in terms of MHz to be consistent with ztex driver and cgminer
  • bitforce: Replace (bool)cgpu->nonce_range with (enum)bitforce_data->proto
  • bitforce: XLINK support for multiple processors
  • bitforce: Prepare log messages for XLINK by separating into proc and dev messages
  • bitforce: Always use fd/mutex pointers on actual device, to prepare for XLINK support
  • bitforce: Get fd/mutex pointers only once per function
  • bitforce: Abstract commands to bitforce_cmd1 (single-stage) and bitforce_cmd2 (double-stage) functions
  • bitforce: Debuglog device information during detection
  • Bugfix: Missing includes needed on Windows
  • Bugfix: Use waddstr instead of wprintw to display completed device summary line, so literal %s don't get interpreted as formatting options
  • Bugfix: bitforce: Avoid polling continuously between work restart and job completion
  • bitforce: Use poll device API when job_get_results needs to wait
  • bitforce: Use poll device API when job_start needs to wait
  • stale_work_future function to determine in advance if a work/share will be stale at some future time
  • bitforce: Minimally refactor to adapt to new minerloop_async
  • minerloop_async: Break out of select on work_restart_notifier
  • Replace UNIX-only work_restart_fd pipe with portable work_restart_notifier
  • Bugfix: Clean out unused variables from minerloop_async
  • Move new device API code to new deviceapi.c source file
  • Make minerloop_async more async, using some callbacks to handle event completions
  • Split part of minerloop_async into do_get_results, and a bit other reorganization
  • Abstract select_timeout function to convert a realtime timeval to a timeout pointer for select()
  • Split part of minerloop_async into do_process_results, and don't allow api->job_get_results to return hashes
  • Split part of minerloop_async into do_job_prepare and do_job_start
  • Initialize thr->tv_poll to -1 (disabled)
  • Update the hashmeter one last time before disabling a device
  • minerloop_async: Break out of select for wakeup notifications
  • Replace mining thread queues (which were only used for wakeup pings) with notifiers (which can be used with select and co)
  • Unify all mining thread wakeup to mt_enable (simplifying code)
  • Bugfix: get_statline: Correct device summary status, only showing DEAD or OFF if it affects all processors
  • Working processor disable/enable with new async minerloop (currently gets stuck if all processors disabled)
  • Bugfix: get_statline: Only care about the processor status if --show-processors is set
  • Bugfix: watchdog: Use processor thr_info even if it isn't a real thread
  • Only support thread-per-device or N-threads-per-processor; simplify work_restart check
  • x6500: Remove mutex, since driver is single-threaded now
  • Bugfix: Update utility every get_statline call, and include every processor involved
  • HACKING: New text file to document the internal workings of (currently) the device API
  • Bugfix: mining_threads is now a total of thr_info objects, not necessarily actual running threads
  • x6500: Working (but incomplete) asynchronous/single-threaded driver
  • Incomplete (but workable) asynchronous minerloop
  • Core support for managing multiple processors from a single thread
  • Allow device drivers to implement their own minerloop
  • Move cgpu_info and thr_info initialization to main, and ensure all get initialized before starting any threads
  • Refactor and simplify miner_thread (no major behavioural changes)
  • Move difficulties to end of share result message, so they can be made to line up nicely
  • Bugfix: Consolidate share result message code (including fixing displayed hash portion for stratum)
  • miner.php: Include ProcID in Device column as a letter
  • Show summaries per-device unless --show-processors is used (also available on Display TUI menu)
  • Order next_proc linked list in processor id order
  • Consolidate processor summary line generation for TUI and text-only modes
  • RPC: Update to include ProcID so multiprocessor devices can be understood correctly
  • RPC: Common function for adding device-identifying fields
  • modminer: Make single-processor statline look like other temperature-only statlines
  • modminer: Split each FPGA into its own logical processor (in the same device still)
  • modminer: Get mutex pointer only once per function
  • ztex: Combine master+slave devices into a single multiprocessor device
  • Preformat dev_repr (device representation) and proc_repr (processor representation) once for use everywhere
  • x6500: Split each FPGA into its own logical processor (in the same device still)
  • x6500: Get mutex pointer only once per function
  • Minimal support for defining devices with multiple logical processors
  • Rename all README files to standard README.* style
Bugfixes included in both 3.0.0 and 2.10.6:
  • Bugfix: openwrt: Never include _ in platform name
  • Bugfix: Fixed typo in bfgminer-rpc usage
  • pool_active: Ensure temporary curl is always cleaned up
  • Try to find jansson via pkg-config first, and fall back to checking system defaults if that fails
  • Attempt to find libjansson via pkg-config if AC_CHECK_LIB fails
  • Update scrypt readme re drivers and sdk.
  • Bugfix: README: Move --device out of GPU only options
  • Update .gitignore
  • Added bfgminer-rpc binary to .gitignore
  • Bugfix: Actually change to the newly selected pool when statum is inactive and it decides to change
  • Bugfix: modminer: Properly fail on dynclock error
  • Bugfix: opencl: Clean pc_data->work before freeing pc_data
  • Bugfix: Correct order of libblkmaker libraries so static builds work
  • Bugfix: Need to ensure __BIG_ENDIAN__ is defined before including uthash.h
  • Bugfix: Stratum: When destroying cURL easy handle, be sure to clear pool stratum_curl pointer
  • Bugfix: bitforce: Fix warning
  • Bugfix: Stratum: Properly handle non-integer "id" for client.get_version requests
  • json_dumps_ANY utility function to portably implement json_dumps(..., ... | JSON_ENCODE_ANY)
  • Bugfix: bitforce: Free old name when updating it on reinitialization
  • Stratum: Include pool number in send/recv protocol logging
  • Include pool number in stratum thread name
  • API always report failed send() replies
  • API.java allow partial reads
  • Bugfix: Stratum: Use curl_easy_cleanup to close connection, so cURL understands what is going on
  • Bugfix: hash_pop: If a work should be rolled, use a clone of it rather than consume a rollable work
  • openwrt: Move Makefile into a bfgminer subdirectory to avoid symlinking issues
  • openwrt: Use --with-curses=ncurses to avoid ncursesw dependency
  • configure: Support --with-curses=FOO to look for curses implementation in libFOO
  • Set pool socket to INVSOCK after closing connection, just in case
  • Clean up compiler warnings
  • Bugfix: Check that pool is active one last time before selecting it
  • Bugfix: Trim whitespace (like newlines) off the end of debug info from libcurl
  • Bugfix: submit_nonce: Backup the original work->blk.nonce since the miner code uses it to track work consumption
  • Bugfix: Scheduler needs to unpause disabled devices, even if it isn't waking them up
  • Bugfix: Use SOCKETTYPE for notifiers, to avoid potential overflow on Win64
  • Bugfix: Some versions of MingW define localtime_r, but don't handle the timeval.tv_sec case that we use; so undef any preexisting one and use our own
  • Bugfix: reinit_gpu: Remember the selected device to correctly change properties of
  • Bugfix: cpu: reinit_device hasn't worked since 93b284d, so just remove it entirely instead of letting it screw with thread 0
  • Document necessity to run ldconfig and possibly configure ld.so
  • Bugfix: Complete startup after just one pool is found active, no need to wait for the rest
  • Bugfix: Update links
  • miner.php: Replace PGA dev number with concatenated device ID
  • Bugfix: miner.php: Display devices with aligned columns instead of assuming they come out of the RPC aligned
  • Bugfix: miner.php: Silence PHP "local timezone" warning
  • Bugfix: api-example: Try to use BSD sockets on any non-Windows platform
  • Bugfix: stratum: Delay mining.get_transactions request until after auth has succeeded, so its failure doesn't abort the connection (also avoids any delay from a large result)
  • --no-getwork option to disable getwork protocol support
  • Clarify dependencies with Debian/Ubuntu package names

Epoch
Hero Member
*****
Offline Offline

Activity: 798



View Profile

Ignore
April 05, 2013, 09:19:16 PM
 #3

Will try this out later tonight.

BTC: 1DJVUnLuPA2bERTkyeir8bKn1eSoRCrYvx
NMC: NFcfHSBBnq622pAr1Xoh9KtnBPA5CUn6id
tnkflx
Sr. Member
****
Offline Offline

Activity: 329


View Profile

Ignore
April 05, 2013, 09:29:43 PM
 #4

"St. Barbara's Faithfully Glorified Mining Initiative Naturally Exceeding Rivals", or just basically a freaking good miner.

Really?

| Operating electrum.be |
JackRabiit
Hero Member
*****
Offline Offline

Activity: 1162


Okey Dokey Lokey


View Profile

Ignore
April 05, 2013, 11:28:45 PM
 #5

Woah that is the biggest thing of mining software release notes ive ever seen!
Definitly gonna read through it all, and if i see something intresting ill give it a shot!

nathanrees19
Full Member
***
Offline Offline

Activity: 196


palm glued to face


View Profile

Ignore
April 06, 2013, 03:52:50 AM
 #6

"St. Barbara's Faithfully Glorified Mining Initiative Naturally Exceeding Rivals", or just basically a freaking good miner.

Really?

Seems legit.

I nearly fell off my chair after seeing it though.

Tired of disagreeing with people? Join the anti-BFL circlejerk today!
Matthew N. Wright puts painfully obvious IP loggers in PMs. I can't believe anyone ever trusted this guy.
bitcoindaddy
Sr. Member
****
Offline Offline

Activity: 470


View Profile

Ignore
April 06, 2013, 11:50:47 AM
 #7

Core dumped - lost a whole night's worth of mining.

Edit: unfortunately, I have no core file (because of ulimit).
rmolby
Member
**
Offline Offline

Activity: 75


View Profile

Ignore
April 06, 2013, 01:33:43 PM
 #8

Core dumped - lost a whole night's worth of mining.

On mine it didn't dump the core, but yesterday after upgrading to 3.0 it just sat there for about 6 hours in "WAIT" state on a dead pool... I had to be AFK and didn't notice it had entered the WAIT state... frustrating...

I fixed my bfgminer.conf so any pools that occationally go dead are the failover pools... I was using http://eligius.st as my primary pool but it shows up as dead currently... so I'm currently using https://eclipsemc.com for my primary pool.

BTW, does anyone have a comprehensive list of pools that operate a getblocktemplate server besides the above two?

BitMessenger: BM-ooioAPn1RUJZjThVDgTYEpPVjPmsVm9j2 --- Cryptsy Trades - send me any currency via Cryptsy 75f95ed5d1aa02759c456f67f60d31b9466761c6
iongchun
Member
**
Offline Offline

Activity: 75


View Profile

Ignore
April 06, 2013, 01:57:49 PM
 #9

Core dumped - lost a whole night's worth of mining.

On mine it didn't dump the core, but yesterday after upgrading to 3.0 it just sat there for about 6 hours in "WAIT" state on a dead pool... I had to be AFK and didn't notice it had entered the WAIT state... frustrating...

I fixed my bfgminer.conf so any pools that occationally go dead are the failover pools... I was using http://eligius.st as my primary pool but it shows up as dead currently... so I'm currently using https://eclipsemc.com for my primary pool.

BTW, does anyone have a comprehensive list of pools that operate a getblocktemplate server besides the above two?

BitMinter?

Bitcoin: 1NFMpJUW7sTKmnVKj12MxhPvCvzAKQ5gUV
Namecoin: N5Tnt3JyMeizsoAFAZDr7CSxjzDtPSisK8
Mining with P2Pool. Graph. Blocks.
rmolby
Member
**
Offline Offline

Activity: 75


View Profile

Ignore
April 06, 2013, 02:21:35 PM
 #10

Core dumped - lost a whole night's worth of mining.

On mine it didn't dump the core, but yesterday after upgrading to 3.0 it just sat there for about 6 hours in "WAIT" state on a dead pool... I had to be AFK and didn't notice it had entered the WAIT state... frustrating...

I fixed my bfgminer.conf so any pools that occationally go dead are the failover pools... I was using http://eligius.st as my primary pool but it shows up as dead currently... so I'm currently using https://eclipsemc.com for my primary pool.

BTW, does anyone have a comprehensive list of pools that operate a getblocktemplate server besides the above two?

Well, I answered my own question... check out https://en.bitcoin.it/wiki/Comparison_of_mining_pools for a comparison of mining pools... I'm not sure how often this is updated tho...

BitMessenger: BM-ooioAPn1RUJZjThVDgTYEpPVjPmsVm9j2 --- Cryptsy Trades - send me any currency via Cryptsy 75f95ed5d1aa02759c456f67f60d31b9466761c6
Epoch
Hero Member
*****
Offline Offline

Activity: 798



View Profile

Ignore
April 06, 2013, 04:14:35 PM
 #11

I was running 2 instances (2 separate machines) of BFGMiner 3.0.0 last night on Bitminter. One of them (15 fpgas) crashed around 1-2am PST. The other (2 fpgas) did not. A 3rd system running 3.0.0 on ozcoin also did not crash overnight. I've had these problems before on Bitminter, on occasion; anecdotally when it happens my web session seems to get logged off, so this suggests that there may have been some problem on Bitminter.

Of course the mining software should not crash; it should handle any 'problems' more elegantly. But I can see this being something difficult to debug since it happens so rarely and the conditions required for it are not well understood.

BTC: 1DJVUnLuPA2bERTkyeir8bKn1eSoRCrYvx
NMC: NFcfHSBBnq622pAr1Xoh9KtnBPA5CUn6id
Luke-Jr
Hero Member
*****
Offline Offline

Activity: 1218



View Profile

Ignore
April 06, 2013, 04:31:40 PM
 #12

Core dumps and/or backtraces would be very helpful to debugging any crashes. Did the 2.99.x versions work stable for those experiencing this?

I've not experienced any crashing myself, but it does seem there are conditions where the SC devices have begun to stop hashing (which IMO is much more annoying than a crash), so I definitely need to put a focus on just fixing stuff for 3.0.1.

BTW, does anyone have a comprehensive list of pools that operate a getblocktemplate server besides the above two?
The getblocktemplate wiki page has a long list of pools, though perhaps it should be merged into the pool comparison page.

Epoch
Hero Member
*****
Offline Offline

Activity: 798



View Profile

Ignore
April 06, 2013, 04:40:24 PM
 #13

Core dumps and/or backtraces would be very helpful to debugging any crashes. Did the 2.99.x versions work stable for those experiencing this?
I've been running bfgminer-02d8f20 (a 2.99.x variant you provided). IIRC I had experienced a few crashes with that version during the March 26-29 period; again, on Bitminter and not Ozcoin or Slush (I was using all 3 during that period). But before that time, I've had no issues with bfgminer-02d8f20.

BTC: 1DJVUnLuPA2bERTkyeir8bKn1eSoRCrYvx
NMC: NFcfHSBBnq622pAr1Xoh9KtnBPA5CUn6id
Shevek
Sr. Member
****
Offline Offline

Activity: 252



View Profile

Ignore
April 06, 2013, 06:11:49 PM
 #14

Just installed from ppa (ubuntu 12.04):

 bfgminer -n
 [2013-04-06 20:11:28] Failed to load OpenCL library, no GPUs usable                   
 [2013-04-06 20:11:28] 0 GPU devices max detected

Proposals for improving bitcoin are like asses: everybody has one
1SheveKuPHpzpLqSvPSavik9wnC51voBa
Luke-Jr
Hero Member
*****
Offline Offline

Activity: 1218



View Profile

Ignore
April 06, 2013, 06:30:47 PM
 #15

Just installed from ppa (ubuntu 12.04):

 bfgminer -n
 [2013-04-06 20:11:28] Failed to load OpenCL library, no GPUs usable                   
 [2013-04-06 20:11:28] 0 GPU devices max detected
Do older versions work? Can you run:
Code:
bfgminer -D -d?

Shevek
Sr. Member
****
Offline Offline

Activity: 252



View Profile

Ignore
April 06, 2013, 07:33:53 PM
 #16

Just installed from ppa (ubuntu 12.04):

 bfgminer -n
 [2013-04-06 20:11:28] Failed to load OpenCL library, no GPUs usable                   
 [2013-04-06 20:11:28] 0 GPU devices max detected
Do older versions work? Can you run:
Code:
bfgminer -D -d?

Sorry, It was a false alarm  Sad I was tweaking two equipments via ssh and I installed the program in the wrong one

The program works ok. It's a fork of cgminer, isn't it?

Thanks for your quick reaction.

Proposals for improving bitcoin are like asses: everybody has one
1SheveKuPHpzpLqSvPSavik9wnC51voBa
twobitcoins
Full Member
***
Offline Offline

Activity: 144


View Profile

Ignore
April 06, 2013, 08:27:57 PM
 #17

Should there be a git tag for the 3.0.0 release?  I don't see one.
Luke-Jr
Hero Member
*****
Offline Offline

Activity: 1218



View Profile

Ignore
April 06, 2013, 08:28:49 PM
 #18

It's a fork of cgminer, isn't it?
It began as a fork of cgminer (a CPU/GPU miner), but not to be confused with the current cgminer, which has become a fork of BFGMiner for trolling reasons.

Luke-Jr
Hero Member
*****
Offline Offline

Activity: 1218



View Profile

Ignore
April 06, 2013, 08:29:21 PM
 #19

Should there be a git tag for the 3.0.0 release?  I don't see one.
Forgot to push the tags to GitHub, sorry. Should be there now.

purelithium
Hero Member
*****
Offline Offline

Activity: 490



View Profile

Ignore
April 06, 2013, 10:51:04 PM
 #20

I've had multiple crashes today on both my mining rigs while connected to eligius via stratum (GBT doesn't work)

How can I get crash logs to you from windows?

SHA-256 11 Gh/s | scrypt 2.5 Mh/s
Like my post? 1H7bfRYh7F89mfmFgsRCdn4awDaUHQmYqY
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 ... 160
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!