when i use the -S erupter:all it doesnt recognize any of my usb miners :\
3.4.0 won't recognise my usb erupters either
I am using the same .conf that I used with 3.3.0 and never had this issue before
Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 105. (Read 1193219 times)
October 26, 2013, 06:02:24 PM
3.4.0 won't recognise my usb erupters either
I am using the same .conf that I used with 3.3.0 and never had this issue before
October 26, 2013, 05:20:02 PM
when i use the -S erupter:all it doesnt recognize any of my usb miners :\
October 26, 2013, 05:00:28 PM
Just add --http-port 8330 to your batch file (or shortcut). Point your Blade to the IP of your PC running BFGMiner with port 8330. It really is that simple. Once the Blade connects it'll appear as a "PXY" device.
You'll need to run the Win32 version on Windows (even if you're running 64-bit Windows). It works OK on all other versions for Linux/OpenWRT etc.
You'll need to run the Win32 version on Windows (even if you're running 64-bit Windows). It works OK on all other versions for Linux/OpenWRT etc.
ty! worked perfect... i had been trying to get it to work with 64bit
October 26, 2013, 04:30:55 PM
Just add --http-port 8330 to your batch file (or shortcut). Point your Blade to the IP of your PC running BFGMiner with port 8330. It really is that simple. Once the Blade connects it'll appear as a "PXY" device.
You'll need to run the Win32 version on Windows (even if you're running 64-bit Windows). It works OK on all other versions for Linux/OpenWRT etc.
You'll need to run the Win32 version on Windows (even if you're running 64-bit Windows). It works OK on all other versions for Linux/OpenWRT etc.
October 26, 2013, 04:26:54 PM
could someone on windows 7 please post the txt of a batchfile that will work for using blades please?
October 26, 2013, 04:15:12 PM
Can anyone tell me how to use a blade erupter with BFGminer?
yes please i cant get it either...
October 26, 2013, 04:10:12 PM
Can anyone tell me how to use a blade erupter with BFGminer?
October 26, 2013, 03:49:11 PM
NEW VERSION 3.4.0, OCTOBER 26 2013
Human readable changelog:
Full changelog:
Human readable changelog:
- New drivers for KnC miners and NanoFury USB miners.
- Per-chip dynamic osc6_bits detection for BFSB, MegaBigPower, and Metabank bitfury boards.
- Ability to set default options for various devices using --set-device commandline option; for example, if you have all your NanoFury miners in a USB 3 hub (with 900 mA power available), you can increase the oscillator speed with: --set-device NFY:osc6_bits=53 (or "set-device":["NFY:osc6_bits=53"] in a config file).
- Con Kolivas's completely rewritten load-balance strategy with per pool quota support. See the updated README to see how it works.
- If we switch away from a pool in failover mode, we will now only switch back to it if it's up for at least 5 minutes to avoid reconnecting to pools that are only intermittently up - good for DDoS situations which we've seen a lot of lately. (by Con Kolivas)
- Updated miner.php from Kano.
- Proxy settings now default to SOCKS5 instead of SOCKS4. Prefix your proxy IP with "socks4://" if you need to use the older protocol.
Full changelog:
- Bugfix: knc: Use separate DEV_RECOVER_DRV deven when doing automatic core disable/re-enable, so user-initiated disables are left alone
- Document existing enum dev_enable usage
- Bugfix: knc: Only try to re-enable cores after we've actually asserted them as disabled, otherwise we won't actually assert the enable either
- knc: Automatically disable and re-enable problematic cores
- AUTHORS: Add Dmitry Sorokin
- bitfury: Disable dynamic osc6_bits when manually setting a specific value
- bitfury_do_io: Make use of timer_elapsed
- bitfury: Only use dynamic osc6_bits with boards that support it explicitly (BFSB and Metabank for now)
- bitfury: More debugging info for dynamic osc6_bits
- Bugfix: bitfury: Fix tv_stat to persist
- bitfury: Remove useless debugging
- bitfury: Simplify dynamic osc6_bits logic such that the range is defined in one place
- bitfury: Remove unused skip_stat
- Bugfix: bitfury: Stick to tracking best_done per-chip, and never call zero_stats (which is for users, not drivers)
- Bugfix: bitfury: Use proc_repr rather than incorrectly calculated chip_id
- Bugfix: bitfury: struct bitfury_device is already chip-specific
- bitfury: dynamic osc_6 bits
- bitfury: Improve frequency calculation - fixes occasional miscalculations as well as makes it safer with multiple devices
- bitfury: Added frequency calculation
- tm_i2c: Corrected copyright
- Allow --set-device opt=val without a device specification to attempt setting it on every device
- Bugfix: knc: Maintain queue_full for all cores, so they continue to queue work even if the first is disabled
- bitfury: Allow setting osc6_bits up to 60
- Bugfix: Set status to LIFE_DEAD2 when killing threads at shut off, to avoid calling driver code
- Skip "testing stability" message at startup
- Try switching pools if for some reason we end up with only idle pools and have ended up current_pool set to an idle one.
- Check a pool is stable for >5 mins before switching back to it.
- ManageTUI: Slash key performs processor selection by search
- nanofury: Populate dev_product and dev_serial
- mcp2210: Implement mcp2210_close
- Bugfix: mcp2210: hid_write needs a report id, especially on Windows
- mcp2210: Workaround some Windows snprintf not handling wide strings correctly by simply copying character-per-character (only works for ASCII data)
- Bugfix: chroot: Check that chdir succeeds
- AUTHORS: Add pontus
- knc: Expose Voltage and DCDC Current to TUI Manage device
- knc: Expose Voltage and DCDC Current to RPC status
- knc: Store volt/current on knccore
- knc: Read voltage/current from DCDCs
- Bugfix: knc: Fix temperature readout of half-celcius
- Bugfix: Only define have_libusb if building with libusb support
- littlefury: Remove unused code
- bitfury: RPC procset: Ignore extra data (like newline) after numbers
- Add --set-device option to allow setting default procset commands
- README: Document hidapi dependency for NanoFury sticks
- AUTHORS: Include Vladimir Strinski for NanoFury code
- mcp2210: Set GPIO output mode atomically with their output values
- nanofury: Power off device when shutting down
- make-release: Include libhidapi-0.dll
- mcp2210: Port to Windows
- configure: Find hidapi.h for mcp2210 using pkg-config
- bitfury: Provide read/write access to osc6_bits from the Manage TUI
- nanofury: Reduce oscillator bits to 50 to stay within USB specs
- bitfury: If multiple integers differ after 4 tries, just go with the first so we can start mining
- nanofury: Implement actual mining code
- nanofury: Turn off device after checkport
- nanofury: New driver; detect device
- mcp2210: Implement protocol required for NanoFury USB sticks
- mcp2210: Skeleton low-level driver for MCP2210 USB to SPI Master bridge
- ft232r: Use lowlevel interface for ft232r_open
- Abstract ft232r scan+probe interface into new generic lowlevel driver interface
- configure: Error if knc driver is requested, but linux/i2c-dev.h is missing or not from i2c-tools
- knc: Attempt to express core enable/disable to controller
- knc: Put knc_device on every processor device_data
- Refactor device disable/enable logic so that drv.thread_{disable,enable} actually get called
- Bugfix: knc: Check that device actually has work queued, before trying to find the most recent one
- knc: Read temperature sensors
- DevAPI: minerloop_queue: Run watchdog in device thread
- knc: Pass queue flush to device when its most recent job produces stale shares
- knc: Issue flush command at init
- Bugfix: knc: Perform le32toh on unknown-work nonces
- knc: Use independent device_id for works to enforce 15-bit size
- Bugfix: spi_emit_nop: Correct counter logic
- knc: Implement mining
- knc: Use FPGA i2c to identify present ASICs
- knc: Basic detection of boards on expected i2c buses
- DevAPI: generic_detect: Just use an enum for flags
- Use list of drivers/algos/options generated by configure in --help info
- miner.php correct sort gen field names largest to smallest
- api ... the code related to device elapsed
- api add device elapsed since hotplug devices Elapsed is less than cgminer Elapsed
- RPC: Include more info in per-device/processor status
- API add 'MHS %ds' to 'summary'
- Icarus remove unneeded opt_debug tests due to applog being a macro
- We should only yield once in cg_wunlock
- Provide a function to downgrade a cglock from a write lock to an intermediate variant.
- Reset quotas on load balance for all pools at the same time to avoid running out during selection and unintentionally dropping to fallback.
- Break out of select pool from a common point for appropriate debug messages and to avoid further tests.
- Find the greatest common denominator in quotas and use the smallest number of consecutive work items per pool in quota load balance mode to smooth hashrate across pools with large quotas. Give excess quota to priority pool 0 instead of pool 0.
- Add subdir-objects to automake options.
- Use the --failover-only flag to have special meaning in combination with load-balance mode to distribute any unused quota back to pool 0 to maintain ratios amongst other pools.
- Display quota and allow it to be modified via the pool menu.
- More README about quotas.
- Document quotas and new load-balance strategy.
- Add API commands and modify output to support pool quota displaying and changing.
- Change message in status when using a balanced pool strategy to notify if there's a stratum pool as well.
- Add quota support to configuration files.
- Rotate pools on all failures to set a pool in select_pool.
- Use quotas for load-balance pool strategy.
- Provide a mechanism for setting a pool quota to be used by load-balance.
- Change --socks-proxy option to default to SOCKS5
- Cope with trailing slashes in stratum urls.
- Make extract_sockaddr set variables passed to it rather than pool struct members.
- miner.php sort the mcast rigs so they are always in the same relative order
- miner.php allow sending the muticast message multiple times
- miner.php mcast ignore duplicate replies
- miner.php coding warning
- miner.php disable 'gen' by default
- miner.php allow formula generation of new fields
- miner.php add doctype
- miner.php remove incorrect echo
- miner.php optional error if not enough mcast rigs are found
- take_queued_work_bymidstate should use a write lock.
- API mcast add a description option with miner.php
- Skip dissecting opt->names in parse_config if it doesn't exist.
- ICA optional limit timing with short=N or long=N
- logging - applogsiz() for large messages
- Provide a funcion that looks up queued work by midstate and then removes it from the device hash database.
- Wait until all pools are done testing before giving up, regardless of how long they take to fail
- AUTHORS: Add Ricardo Iván Vieitez Parra and Paul Wouters
- Bugfix: Check that setgid succeeds
- When using --chroot, chdir to the new root
- Bugfix: Add missing drivers to --help list
- Bugfix: Zero stats: cgpu->diff_stale
- fpgautils: serial_close: Explicitly release advisory lock before closing, in case fd has been inherited by a process forked by system()
- Use serial_close to pair with every serial_open
- Workaround bug in Plibc by resetting locale to "C" at startup
- Bugfix: bitfury: Check for necessity of linux/i2c.h so build succeeds with i2c-tools's userspace linux/i2c-dev.h
- bitforce: Workaround bugs in current firmware for the Chili
- Bugfix: DevAPI: Reduce race-collision delay to 1ms so thread_shutdown actually gets called before threads are killed forcefully
- Bugfix: configure: Use AC_SYS_LARGEFILE to ensure nonce/share log files can safely grow bigger than 2 GB
- Bugfix: Correct argument type for --submit-threads option
- littlefury: Workaround Xcode bug initialising fields in anonymous unions
- Bugfix: write_config: Make intensity list writing more readable, and avoid extraneous argument in dynamic intensity case
- DevAPI: Trigger mt_disable_start after init, if a device is disabled before minerloop starts
- icarus: Skip sending new work if entering DEV_RECOVER* modes
- icarus: When disabling, close device fd and stop sending new work
- RPC: Use get_api_extra_device_status for full-device status, for devices with only a single processor
October 26, 2013, 12:43:32 PM
Not yet, but support should be added by version 3.5.
how soon is expected version 3.5.3.5 likely within a month.
October 26, 2013, 04:40:35 AM
A simple question: every time I start BFGminer all my pools specified in .conf file start mining together.
Is there an option I can add in .conf file to disable unwanted pools?
thx
Is there an option I can add in .conf file to disable unwanted pools?
thx
October 26, 2013, 04:04:51 AM
Not yet, but support should be added by version 3.5.
how soon is expected version 3.5. October 26, 2013, 12:31:17 AM
if it supports HEH16A form technobit.eu ?
Not yet, but support should be added by version 3.5. October 25, 2013, 07:35:10 PM
I apologize for the stupid question,
but never found information about BFGMiner 3.3.0 for openwrt
if it supports HEH16A form technobit.eu ?
now i run one Jalapeno, quite stable working for now.
thanks for your time. Greetings to all
but never found information about BFGMiner 3.3.0 for openwrt
if it supports HEH16A form technobit.eu ?
now i run one Jalapeno, quite stable working for now.
thanks for your time. Greetings to all
October 25, 2013, 01:48:39 PM
It looks to be a problem with i2c-tools - the version I have installed is the one that is installed by yast - 3.1.0-2.1.2, but I'm not 100%. So I removed it using yast, and now I get this error:
Please try the latest git; it should work with i2c-tools's version of the header 
Just tried downloading it from the git - perhaps I'm doing it wrong? I previously downloaded the zip to my machine, then unzipped it and went from there. The current git doesn't appear to have a configure script in it? Again, sorry to appear like a complete bozo, I do have some ability, honestly!
Thanks
Darren
October 25, 2013, 01:45:39 PM
It looks to be a problem with i2c-tools - the version I have installed is the one that is installed by yast - 3.1.0-2.1.2, but I'm not 100%. So I removed it using yast, and now I get this error:
Please try the latest git; it should work with i2c-tools's version of the header Just tried downloading it from the git - perhaps I'm doing it wrong? I previously downloaded the zip to my machine, then unzipped it and went from there. The current git doesn't appear to have a configure script in it? Again, sorry to appear like a complete bozo, I do have some ability, honestly!
Thanks
Darren
October 25, 2013, 12:28:41 PM
Anybody have an idea why im getting so many stales at start up? It only happens when I start my miner. Im getting anywhere between 9-22+. Im running bfgminer 3.2.1 connecting to btcguild.
I get the same with hw errors on my blade. what hardware do you have?
BFL SC 60gh.
October 25, 2013, 12:27:20 PM
Anybody have an idea why im getting so many stales at start up? It only happens when I start my miner. Im getting anywhere between 9-22+. Im running bfgminer 3.2.1 connecting to btcguild.
I get the same with hw errors on my blade. what hardware do you have?
October 25, 2013, 12:24:22 PM
Anybody have an idea why im getting so many stales at start up? It only happens when I start my miner. Im getting anywhere between 9-22+. Im running bfgminer 3.2.1 connecting to btcguild.
Edit: This is happening with a BFL 60gh.
Edit: This is happening with a BFL 60gh.
October 25, 2013, 11:54:19 AM
It looks to be a problem with i2c-tools - the version I have installed is the one that is installed by yast - 3.1.0-2.1.2, but I'm not 100%. So I removed it using yast, and now I get this error:
Please try the latest git; it should work with i2c-tools's version of the header October 25, 2013, 03:33:03 AM
I've been using bfgminer successfully on a windows machine for a few weeks, and want to transfer it to my (always on anyway) openSUSE linux server I have at home (as I'm no longer going to be mining scrypt with GPUs on that machine - I am running bfg for bitcoin and cgminer for scrypt).
I'm trying to compile from source, and got round issues of a couple of dependencies, but have now hit a hurdle which I can't sort out:
./configure works fine.
When I run make I get the following error:
It looks to be a problem with i2c-tools - the version I have installed is the one that is installed by yast - 3.1.0-2.1.2, but I'm not 100%. So I removed it using yast, and now I get this error:
The compilation gets further, but has a different problem - do I need to put a 'correct' version of i2c-dev.h in the linux/ folder? I' usually expect ./configure to sort out dependencies, but I'm not an expert on this by any means.
I'd appreciate any hints/help as to how to get this installed, whether it's use another method or fix compiling from source.
I'm trying to compile from source, and got round issues of a couple of dependencies, but have now hit a hurdle which I can't sort out:
./configure works fine.
When I run make I get the following error:
Code:
CC bfgminer-spidevc.o
In file included from spidevc.c:51:0:
/usr/include/linux/i2c-dev.h:38:8: error: redefinition of âstruct i2c_msgâ
In file included from spidevc.c:50:0:
/usr/include/linux/i2c.h:68:8: note: originally defined here
In file included from spidevc.c:51:0:
/usr/include/linux/i2c-dev.h:90:7: error: redefinition of âunion i2c_smbus_dataâ
In file included from spidevc.c:50:0:
/usr/include/linux/i2c.h:126:7: note: originally defined here
make[2]: *** [bfgminer-spidevc.o] Error 1
make[2]: Leaving directory `/home/darren/bfgminer-3.3.0'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/darren/bfgminer-3.3.0'
make: *** [all] Error 2
In file included from spidevc.c:51:0:
/usr/include/linux/i2c-dev.h:38:8: error: redefinition of âstruct i2c_msgâ
In file included from spidevc.c:50:0:
/usr/include/linux/i2c.h:68:8: note: originally defined here
In file included from spidevc.c:51:0:
/usr/include/linux/i2c-dev.h:90:7: error: redefinition of âunion i2c_smbus_dataâ
In file included from spidevc.c:50:0:
/usr/include/linux/i2c.h:126:7: note: originally defined here
make[2]: *** [bfgminer-spidevc.o] Error 1
make[2]: Leaving directory `/home/darren/bfgminer-3.3.0'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/darren/bfgminer-3.3.0'
make: *** [all] Error 2
It looks to be a problem with i2c-tools - the version I have installed is the one that is installed by yast - 3.1.0-2.1.2, but I'm not 100%. So I removed it using yast, and now I get this error:
Code:
CC bfgminer-miner.o
CC bfgminer-deviceapi.o
CC bfgminer-util.o
CC bfgminer-sha2.o
CC bfgminer-api.o
CC bfgminer-logging.o
CC bfgminer-driver-opencl.o
CC bfgminer-ocl.o
CC bfgminer-findnonce.o
CC bfgminer-adl.o
CC bfgminer-fpgautils.o
CC bfgminer-dynclock.o
CC bfgminer-driver-bitforce.o
CC bfgminer-driver-bigpic.o
CC bfgminer-driver-icarus.o
CC bfgminer-driver-cairnsmore.o
CC bfgminer-driver-erupter.o
CC bfgminer-driver-avalon.o
CC bfgminer-hexdump.o
CC bfgminer-driver-modminer.o
CC bfgminer-driver-bitfury.o
CC bfgminer-libbitfury.o
CC bfgminer-spidevc.o
spidevc.c:51:27: fatal error: linux/i2c-dev.h: No such file or directory
compilation terminated.
make[2]: *** [bfgminer-spidevc.o] Error 1
make[2]: Leaving directory `/home/darren/bfgminer-3.3.0'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/darren/bfgminer-3.3.0'
make: *** [all] Error 2
CC bfgminer-deviceapi.o
CC bfgminer-util.o
CC bfgminer-sha2.o
CC bfgminer-api.o
CC bfgminer-logging.o
CC bfgminer-driver-opencl.o
CC bfgminer-ocl.o
CC bfgminer-findnonce.o
CC bfgminer-adl.o
CC bfgminer-fpgautils.o
CC bfgminer-dynclock.o
CC bfgminer-driver-bitforce.o
CC bfgminer-driver-bigpic.o
CC bfgminer-driver-icarus.o
CC bfgminer-driver-cairnsmore.o
CC bfgminer-driver-erupter.o
CC bfgminer-driver-avalon.o
CC bfgminer-hexdump.o
CC bfgminer-driver-modminer.o
CC bfgminer-driver-bitfury.o
CC bfgminer-libbitfury.o
CC bfgminer-spidevc.o
spidevc.c:51:27: fatal error: linux/i2c-dev.h: No such file or directory
compilation terminated.
make[2]: *** [bfgminer-spidevc.o] Error 1
make[2]: Leaving directory `/home/darren/bfgminer-3.3.0'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/darren/bfgminer-3.3.0'
make: *** [all] Error 2
The compilation gets further, but has a different problem - do I need to put a 'correct' version of i2c-dev.h in the linux/ folder? I' usually expect ./configure to sort out dependencies, but I'm not an expert on this by any means.
I'd appreciate any hints/help as to how to get this installed, whether it's use another method or fix compiling from source.
Jump to: