Bitcoin Forum
April 23, 2014, 07:04:07 PM *
News: Due to the OpenSSL heartbleed bug, changing your forum password is recommended.
 
  Home Help Search Donate Login Register  
  Show Posts
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 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 ... 200
401  Bitcoin / Mining software (miners) / Re: BFGMiner 3.7.0: modular ASIC/FPGA, GBT, Strtm, RPC, Mac/Lnx/W64, bifury/twinfury on: November 27, 2013, 06:11:40 PM
NEW VERSION 3.6.0, NOVEMBER 12 2013


 Huh


oops
402  Bitcoin / Hardware / Re: [ANN] Bi•Fury | 5+ GH/s USB Miner [FASTEST USB MINER IN THE WORLD][IN STOCK!] on: November 27, 2013, 04:25:47 PM
BFGMiner 3.7.0 released with Bi*fury support
403  Bitcoin / Hardware / Re: [ANN] Twin Bitfury USB miner on: November 27, 2013, 04:25:36 PM
BFGMiner 3.7.0 released with Twinfury support
404  Bitcoin / Mining software (miners) / Re: BFGMiner 3.7.0: modular ASIC/FPGA, GBT, Strtm, RPC, Mac/Lnx/W64, bifury/twinfury on: November 27, 2013, 04:06:51 PM
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 <path/serial>
  • 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
405  Bitcoin / Mining software (miners) / Re: BFGMiner 3.6.0: modular ASIC/FPGA, GBT, Strtm, RPC, Lnx/OpnWrt/PPA/W64, HBR/KLN on: November 27, 2013, 03:39:33 PM
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.
406  Bitcoin / Development & Technical Discussion / Re: Yet another Coin Control Release on: November 27, 2013, 05:56:51 AM
The point is to let you micromanage what coins (UTXO entries) you consume in a given transaction.
There is no such thing as a "from address".
407  Bitcoin / Mining software (miners) / Re: BFGMiner 3.6.0: modular ASIC/FPGA, GBT, Strtm, RPC, Lnx/OpnWrt/PPA/W64, HBR/KLN on: November 27, 2013, 01:47:13 AM
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.
408  Bitcoin / Mining software (miners) / Re: BFGMiner 3.6.0: modular ASIC/FPGA, GBT, Strtm, RPC, Lnx/OpnWrt/PPA/W64, HBR/KLN on: November 26, 2013, 12:11:08 AM
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.
409  Bitcoin / Mining / Re: Miners: Time to deprioritise/filter address reuse! on: November 25, 2013, 04:28:51 PM
How would that work with pools that have public stats? Especially Eligius, actually.

Perhaps show hash(BIP32 seed)? Otherwise, public seeds would not result in any more privacy.
Actually, I was thinking we should use hash(recurring invoice id) for the stats page, and not publish a list of those at all.
wizkid057 disagrees at the moment, though, so I'm not sure how it will turn out.
410  Bitcoin / Mining software (miners) / Re: BFGMiner 3.6.0: modular ASIC/FPGA, GBT, Strtm, RPC, Lnx/OpnWrt/PPA/W64, HBR/KLN on: November 24, 2013, 07:06:13 PM
Is the Klondike K16 supported now in BFG?  I can't be sure looking at the readmes.
The driver is pretty poor code (almost verbatim import from cgminer), so I'll probably rewrite it when/if they get back to me with protocol specs (or maybe reverse engineer it from this code), but it should work as of 3.6.0...
411  Bitcoin / Pools / Re: [600Th] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # on: November 24, 2013, 06:59:51 PM
It's a mining pool, not a bank...
412  Bitcoin / Mining software (miners) / Re: BFGMiner 3.6.0: modular ASIC/FPGA, GBT, Strtm, RPC, Lnx/OpnWrt/PPA/W64, HBR/KLN on: November 24, 2013, 12:16:13 PM
README
413  Bitcoin / Mining / Re: Miners: Time to deprioritise/filter address reuse! on: November 24, 2013, 04:31:00 AM
Doesn't matter, there's a pseudonym visible.
Anonymity means you cannot name them at all.
Bitcoin is at best pseudonymous.

Practical difference: a pseudonym can be named/identified and theoretically be found, whereas someone anonymous cannot be identified at all distinct from any other actor.
414  Bitcoin / Mining / Re: Miners: Time to deprioritise/filter address reuse! on: November 24, 2013, 01:50:54 AM
Hopefully it won't be forced until Bitcoin-qt supports it.
I don't expect it to ever be forced at the blockchain level.
415  Bitcoin / Mining / Re: Miners: Time to deprioritise/filter address reuse! on: November 24, 2013, 01:13:25 AM
Does not look like the official client supports that.
There is no official client, or official anything. Official implies centralisation.

However, I believe that everyone should decide that for themselves
Address reuse takes away that choice from other users.
Using a unique address per transaction, as Bitcoin was always intended to be used, allows each user to choose for themselves whether they want their transaction record public or not.

However, this affects not only the destination but also source addresses as I understand it.
There are no source addresses.
Addresses are only ever used to receive.

So, if I have mined a lot of coins (and on Eligius, all coins go to a single address, can't really change it, can I?) I have to wait longer if I want to make a few smaller purchases? Actually, same applies to coins bought in an exchange - unless I want to spend time manually withdrawing to different addresses.
Yes, if you use Bitcoin wrong, this will make your transactions take slightly longer to confirm.
That's intentional.
I will continue to work closely with wizkid057 to ensure Eligius gets support for BIP32 as soon as possible.

I like the current system where I can keep coins received by mining in one address (so if I see the notification that 1P5p... received coins I know it is from mining, 175... means LabRat paid dividends etc).
Future software versions implementing BIP32 should be able to notify you based on the recurring invoice id used.
416  Bitcoin / Mining / Re: Miners: Time to deprioritise/filter address reuse! on: November 24, 2013, 12:10:20 AM
Using bitcoin correctly won't stop your government from tracking you, and isn't intended to.
What it can do, is stop everyone else from tracking you.
417  Bitcoin / Pools / Re: [600Th] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # on: November 23, 2013, 09:44:23 AM
Hi wizkid,

I was thinking about changing my deposit address. But since my "Share Rewarded" is about 91% right now, I wanted to check if changing addresses and abandoning my old account makes it less likely that those stored shares might be paid someday. Based on my understanding of the reward system I didn't think it would matter, but I wanted to run it by you first. Thanks!
Won't matter.
418  Bitcoin / Pools / Re: [600Th] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # on: November 23, 2013, 03:15:05 AM
My unpaid balance is above my payout threshold, but there is nothing showing in the payout queue (totally blank)
What's going on???
Anyone else seeing the same thing?
I was a few seconds away and jumped to 8 blocks til payout. It does all arrive eventually it seems.

Is the preferred payout to new addresses in effect?  I see on bitcointax.info that there are choices like on spending Bitcoin, last in first out; or first in first out or averaging.  It says if Bitcoins are mixed in an address they can't be separated out.  There is suppose to be a tax advantage to one or another scheme.  So, wanting us to use new addresses might be to our advantage eventually aside from the reduced ripoff potential.
bitcointax.info is wrong; I would have to say whoever wrote it doesn't understand how bitcoin works.
419  Bitcoin / Mining software (miners) / Re: BFGMiner 3.6.0: modular ASIC/FPGA, GBT, Strtm, RPC, Lnx/OpnWrt/PPA/W64, HBR/KLN on: November 23, 2013, 02:49:49 AM
Is Bi•Fury gonna be supported in the next version?  I know it's in the pipeline, just curious.
In fact, you can try the "bifury" branch I pushed to git... It won't report hashrates, but it should mine... Wink
I'll do that this weekend though I won't be able to actually 'try' it until Monday night.  Smiley

Did you have any heat issues with it? (I'm assuming, of course, that you received an engineering sample.)
Plan on using oven gloves to unplug it...
420  Bitcoin / Mining software (miners) / Re: BFGMiner 3.6.0: modular ASIC/FPGA, GBT, Strtm, RPC, Lnx/OpnWrt/PPA/W64, HBR/KLN on: November 22, 2013, 11:02:17 PM
For CPU or scrypt problems, especially on Mac: patches welcome.
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 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 ... 200
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!