sadly bfgminer does not see my boards
driver is libusbx from windows
That's what happens when you have the wrong driver... driver is libusbx from windows
Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 61. (Read 1193208 times)
January 15, 2014, 07:12:00 PM
January 15, 2014, 06:37:47 PM
January 15, 2014, 05:58:08 PM
I am having and odd problem running my BiFury.
I also get the same results with the new BFGminer installed.
I run BFG and get a msg and it says "User does not have privileges to install COM 9" Com 9 is where my BiFury is.
I have tried this on all usb ports and my USB hub and while recognized I get the same error.
When I run with this command -d? -S noauto -S bifury:all -D -T it runs through so fast and shuts down BFG.
Any help would be great.
I also get the same results with the new BFGminer installed.
I run BFG and get a msg and it says "User does not have privileges to install COM 9" Com 9 is where my BiFury is.
I have tried this on all usb ports and my USB hub and while recognized I get the same error.
When I run with this command -d? -S noauto -S bifury:all -D -T it runs through so fast and shuts down BFG.
Any help would be great.
January 15, 2014, 04:59:15 PM
This should actually be 265 or higher:
drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
Be sure you have the original drivers, no Zadig/WinUSB/libusb nonsense.drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
I'll increase the clock limits in the next version I guess...
Don't stop at 265 either... I run my thumbs (with active cooling in winter weather) at 270.
I'll let you know once I get my shipment of Dry Ice..
cryogenic helium is a dwindling resource
January 15, 2014, 04:56:34 PM
This should actually be 265 or higher:
drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
Be sure you have the original drivers, no Zadig/WinUSB/libusb nonsense.drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
I'll increase the clock limits in the next version I guess...
Don't stop at 265 either... I run my thumbs (with active cooling in winter weather) at 270.
I'll let you know once I get my shipment of Dry Ice..
January 15, 2014, 04:54:52 PM
This should actually be 265 or higher:
drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
Be sure you have the original drivers, no Zadig/WinUSB/libusb nonsense.drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
I'll increase the clock limits in the next version I guess...
Don't stop at 265 either... I run my thumbs (with active cooling in winter weather) at 270.
January 15, 2014, 04:53:08 PM
This should actually be 265 or higher:
drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
Be sure you have the original drivers, no Zadig/WinUSB/libusb nonsense.drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
I'll increase the clock limits in the next version I guess...
Don't stop at 265 either... I run my thumbs (with active cooling in winter weather) at 270.
January 15, 2014, 04:33:13 PM
YAY, 3.10.0
Device scan provides the following: nanofury_lowl_probe: Matched "NanoFury NF1 0.6" serial "0000082420", but mcp2210 lowlevel driver failed to open it
Device scan provides the following: nanofury_lowl_probe: Matched "NanoFury NF1 0.6" serial "0000082420", but mcp2210 lowlevel driver failed to open it
January 15, 2014, 04:17:41 PM
When is Bfg 3.10 downloadable from github ?
Probably a few seconds after it's released, at a guess.
Wow, such a helpful response...
HERP DERP.
New version available when new version released, like always. January 15, 2014, 04:05:54 PM
This should actually be 265 or higher:
drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
Be sure you have the original drivers, no Zadig/WinUSB/libusb nonsense.drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
I'll increase the clock limits in the next version I guess...
January 15, 2014, 03:55:03 PM
This should actually be 265 or higher:
drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
Try -S drillbit:auto or all or specify the path per device
January 15, 2014, 03:52:20 PM
This should actually be 265 or higher:
drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
drillbit: Expand allowed external clock range to 0-255
I run my thumbs at 265 all day.
I didn't find any information on how to run with drillbit devices? Did I miss it in the documentation? When I run with no arguments no devices are detected.
January 15, 2014, 03:47:39 PM
See what I mean? 
January 15, 2014, 03:44:27 PM
NEW VERSION 3.10.0, JANUARY 15 2014
Human readable changelog:
Full changelog:
Human readable changelog:
- Support for AntMiner U1, Drillbit, and HashFast devices.
- Option --weighed-stats to display share-count columns (A/R) weighed to difficulty 1.
- x6500: maxclock setting (use with --set-device) to limit dynamic clocking range.
- opencl/adl: Fixed crash on exit with R9 series GPUs.
Full changelog:
- Downgrade official Windows build compiler to GCC 4.7.3.
- Bugfix: Stratum: Accept JSON Number type for port number
- Bugfix: proxy: Set start timer when creating new virtual devices
- antminer: Add support for the Identify function - flashes LED 10 times
- drillbit: Expand allowed external clock range to 0-255
- drillbit: Forbid setting external clock usage if not supported by device
- Check for DBC_TEMP capability before trying to read temperature
- Bugfix: drillbit: Reduce work message to correct size
- README: Update documentation for new udev rules and "video" group
- Bugfix: opencl/adl: Set iSpeedType for get-fanspeed requests, and ensure we don't change do something weird with the fan when initially setting user-defined speed flag.
- Bugfix: drillbit: Initialise rv variable
- Bugfix: Simplify adding "http://" prefix to avoid strncat overflow (length excludes null byte)
- hashfast: Debuglog work flushing
- hashfast: Implement OP_NONCE search flag
- hashfast: Log seq numbers for nonces found
- hashfast: Count hashes done by nonces found, rather than no-pending-work (which could be triggered by flushes)
- hashfast: Just keep a queue of the 32 most recent work items per core
- hashfast: Convert to minerloop_queue driver model
- hashfast: Gracefully complain if we are given an unknown chip or core address
- udev rule for hashfast devices
- hashfast: New driver using UMS protocol
- CRC-8-CCITT implementation
- AUTHORS: Add Lingchao Xu and move nwoolls up to antminer driver (and mention TwinFury driver for Andreas)
- knc: Workaround false compiler warning about "uninitialised" vars
- Bugfix: drillbit: Access fd after potentially reopening
- Remove Christmas colouring
- drillbit: Add udev rule
- drillbit: Correct configure logic to check for generic bitfury code (needed to decode nonces)
- drillbit: Implement some basic problem recovery
- drillbit: Support identify command
- drillbit: Read/write access to clock and voltage configuration from RPC and ManageTUI
- drillbit: Store board configuration
- drillbit: Read temperature sensor
- drillbit: Check nonces against prev work
- drillbit: Implement mining
- drillbit: Only detection code
- antminer: Initial support for the Bitmain AntMiner U1 ASIC Includes support for identifying the U1 separately from Icarus and Block Erupter Also includes overclocking via --set-device antminer:clock=xHEX
- Extend horizontal lines to full screen width
- Log devid for USB string request failures
- Bugfix: segmentation fault if the terminal window is too narrow for the Help and Quit items
- Accept "address" spelled out in --coinbase-addr option
- Bugfix: document the need to package zlib1.dll in the Windows build instructions
- Bugfix: Stratum: Re-read pool sock var after suspend+restart
- Silence false uninitialised var use warning and calculate dev_runtime only once
- Bugfix: HID API not properly detected on Mac OS X
- Adjust device list size as necessary when accessing options
- Avoid erasing the screen when statusy is not changing
- Abstract common set_statusy code out of change_logwinsize and check_winsizes
- TUI: Support pgup/pgdown for scrolling device list by page
- Bugfix: icarus: quirk_reopen is an int
- Bugfix: Do not allocate spi_port on the Stack, even to initialize - EXC_BAD_ACCESS on OS X
- get_statline3: Simplify statistics gathering
- Bugfix: twinfury: Use serial number formatted over USB, so it works with --scan
- twinfury: Only debuglog temperature debugging data when --device-protocol-dump is enabled
- Bugfix: twinfury: Populate temperature info on both processors
- Option --weighed-stats to display A and R values weighed by difficulty
- README.GPU: Document always-disabled-by-default for OpenCL driver
- AUTHORS: Add Nate Woolls
- Extend menu to full width of window
- Abstract out spaces-to-eol to bfg_wspctoeol function
- Elaborate on spi_port+stack problem in comments
- Bugfix: Do not allocate spi_port on the Stack - EXC_BAD_ACCESS on OS X
- Bugfix: don't attempt to probe Bluetooth devices when scanning hardware
- x6500: Allow overriding the maximum frequency used by the dynclock logic Can now use e.g. --set-device x6500:maxclock=210 Prevents spending time on frequencies that only produce HW errors
- HACKING: Clearly document that dname must be lowercase and alphabetic
- bifury: Tolerate corruption in submit message, remapping shares to the first processor if chip id is unrecognised
- bifury: Tolerate corruption in hwerror message
- bifury: Tolerate corruption in job message, and only count hashes done when completing a known job
- Use a lowercase driver name to fix --scan pattern matching Otherwise the following doesn't work: -S noauto -S twinfury:auto
January 15, 2014, 03:41:45 PM
When is Bfg 3.10 downloadable from github ?
Probably a few seconds after it's released, at a guess.
Wow, such a helpful response...
There is no release tagged as 3.10.
Ljr will update thread with summary and updated title when 3.10 is deemed "ready"
January 15, 2014, 03:20:07 PM
I am stupid at programming...
How do i build 3.9.0 and include CPU support for windows x64?
Is there a build that is out there that supports it? I know its useless for BTC but I have my pools set so my CPU farm is mining new and emerging altcoins..... and it would be nice to have the same program for allll my mining
How do i build 3.9.0 and include CPU support for windows x64?
Is there a build that is out there that supports it? I know its useless for BTC but I have my pools set so my CPU farm is mining new and emerging altcoins..... and it would be nice to have the same program for allll my mining
January 15, 2014, 02:33:55 PM
When is Bfg 3.10 downloadable from github ?
Probably a few seconds after it's released, at a guess.
Wow, such a helpful response...
January 15, 2014, 02:12:12 PM
When is Bfg 3.10 downloadable from github ?
Probably a few seconds after it's released, at a guess.
January 15, 2014, 02:06:58 PM
When is Bfg 3.10 downloadable from github ?
January 15, 2014, 01:47:15 PM
Luke-
I just wanted to thank you for your support on the GPU side of things. I am well aware of your opinion on ALTs and GPU mining, and appreciate the recent work you've done to add/fix a couple things recently. Expect a small donation in the near future.
Thanks again.
I just wanted to thank you for your support on the GPU side of things. I am well aware of your opinion on ALTs and GPU mining, and appreciate the recent work you've done to add/fix a couple things recently. Expect a small donation in the near future.
Thanks again.
Jump to: