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

[Luke-Jr]

Downloaded the latest version, bfgminer detects my gpus but not my hashbusters. Something about libusb not supported error comes up quickly when I scan for devices. Would I need to start the miner with special commands?

Shouldn't... Can you paste the output of:

Code:

bfgminer -D -d?

[ThinkFast]

Trying to mine litecoins with bfgminer.
W2KSP3
GPU 0 HD4850

LTC.bat:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
bfgminer -d 0 --scrypt -o http://ltc.give-me-coins.com:3333 -u user.worker -p pass --failover-only --shaders=800 -I 10

Log:
 [2013-11-06 18:46:44] Probing for an alive pool
 [2013-11-06 18:46:45] Pool 0 http://ltc.give-me-coins.com:3333 alive
 [2013-11-06 18:46:45] Network difficulty changed to 1.06k ( 7.57Gh/s)
 [2013-11-06 18:46:45] Stratum from pool 0 detected new block
 [2013-11-06 18:46:45] Pool 0 is hiding block contents from us
 [2013-11-06 18:46:45] Pool 0 now providing block contents to us
 [2013-11-06 18:47:24] Stratum from pool 0 requested work update

Question: Why am I not seeing the complete interface like I do when I'm mining btc? It usually draws it after a few secs.
Is this because I'm running from a batch file?
Thanks!

[juhakall]

Thanks for adding MHS 5s to summary API response! BTW, I noticed that the devicescan API command isn't considered privileged. Shouldn't it be?

[disclaimer201]

Downloaded the latest version, bfgminer detects my gpus but not my hashbusters. Something about libusb not supported error comes up quickly when I scan for devices. Would I need to start the miner with special commands?

Shouldn't... Can you paste the output of:

Code:

bfgminer -D -d?

Only one hashbuster connected to this rig atm.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.

 [2013-11-07 01:47:20] setrlimit: Not supported by platform
 [2013-11-07 01:47:20] Started bfgminer 3.5.0
 [2013-11-07 01:47:20] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-07 01:47:20] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-07 01:47:20] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-07 01:47:20] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-07 01:47:20] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-07 01:47:20] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-07 01:47:20] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-07 01:47:20] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-07 01:47:20] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-07 01:47:20] usb_devinfo_scan: Error opening device: LIBUSB_ERROR_NOT_
SUPPORTED
 [2013-11-07 01:47:20] hidapi_try_lib: Couldn't load libhidapi.dll: unknown

 [2013-11-07 01:47:20] hidapi_try_lib: Successfully loaded libhidapi-0.dll

 [2013-11-07 01:47:20] hid_devinfo_scan: Found "USB Optical Mouse" serial "(null
)"
 [2013-11-07 01:47:20] hid_devinfo_scan: Found "USB Keyboard" serial "  "

 [2013-11-07 01:47:20] hid_devinfo_scan: Found "USB Keyboard" serial "  "

 [2013-11-07 01:47:20] hid_devinfo_scan: Found "USB Keyboard" serial "  "

 [2013-11-07 01:47:20] Failed to get PortName registry key value in fpgautils.c
_vcom_devinfo_scan_windows__hubport():451: Das System kann die angegebene Datei
nicht finden.

 [2013-11-07 01:47:20] FTD2XX.DLL failed to load, not using FTDI autodetect

 [2013-11-07 01:47:20] QueryDosDevice returned insufficent buffer error; enlargi
ng to 200
 [2013-11-07 01:47:20] QueryDosDevice returned insufficent buffer error; enlargi
ng to 400
 [2013-11-07 01:47:20] QueryDosDevice returned insufficent buffer error; enlargi
ng to 800
 [2013-11-07 01:47:20] QueryDosDevice returned insufficent buffer error; enlargi
ng to 1000
 [2013-11-07 01:47:20] QueryDosDevice returned insufficent buffer error; enlargi
ng to 2000
 [2013-11-07 01:47:20] QueryDosDevice returned insufficent buffer error; enlargi
ng to 4000
 [2013-11-07 01:47:20] lowlevel_scan: Found usb device at usb:008:001 (path=(nul
l), vid=1033, pid=0194, manuf=(null), prod=(null), serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found usb device at usb:004:002 (path=(nul
l), vid=fa04, pid=0011, manuf=(null), prod=(null), serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found usb device at usb:006:002 (path=(nul
l), vid=04e8, pid=3292, manuf=(null), prod=(null), serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found usb device at usb:006:004 (path=(nul
l), vid=04d9, pid=1503, manuf= , prod=USB Keyboard, serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found usb device at usb:006:003 (path=(nul
l), vid=046d, pid=c05a, manuf=Logitech, prod=USB Optical Mouse, serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found usb device at usb:003:001 (path=(nul
l), vid=1002, pid=4396, manuf=(null), prod=(null), serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found usb device at usb:002:001 (path=(nul
l), vid=1002, pid=4396, manuf=(null), prod=(null), serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found usb device at usb:001:001 (path=(nul
l), vid=1002, pid=4396, manuf=(null), prod=(null), serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found usb device at usb:007:001 (path=(nul
l), vid=1002, pid=4399, manuf=(null), prod=(null), serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found usb device at usb:004:001 (path=(nul
l), vid=1002, pid=4397, manuf=(null), prod=(null), serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found usb device at usb:006:001 (path=(nul
l), vid=1002, pid=4397, manuf=(null), prod=(null), serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found usb device at usb:005:001 (path=(nul
l), vid=1002, pid=4397, manuf=(null), prod=(null), serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found hid device at hid:\\?\hid#vid_04d9&p
id_1503&mi_01&col02#7&17b36bba&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030} (pa
th=\\?\hid#vid_04d9&pid_1503&mi_01&col02#7&17b36bba&0&0001#{4d1e55b2-f16f-11cf-8
8cb-001111000030}, vid=04d9, pid=1503, manuf= , prod=USB Keyboard, serial=
)
 [2013-11-07 01:47:20] lowlevel_scan: Found hid device at hid:\\?\hid#vid_04d9&p
id_1503&mi_01&col01#7&17b36bba&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (pa
th=\\?\hid#vid_04d9&pid_1503&mi_01&col01#7&17b36bba&0&0000#{4d1e55b2-f16f-11cf-8
8cb-001111000030}, vid=04d9, pid=1503, manuf= , prod=USB Keyboard, serial=
)
 [2013-11-07 01:47:20] lowlevel_scan: Found hid device at hid:\\?\hid#vid_04d9&p
id_1503&mi_00#7&2ae387f8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (path=\\?
\hid#vid_04d9&pid_1503&mi_00#7&2ae387f8&0&0000#{4d1e55b2-f16f-11cf-88cb-00111100
0030}, vid=04d9, pid=1503, manuf= , prod=USB Keyboard, serial=  )

 [2013-11-07 01:47:20] lowlevel_scan: Found hid device at hid:\\?\hid#vid_046d&p
id_c05a#6&16bc53f1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} (path=\\?\hid#v
id_046d&pid_c05a#6&16bc53f1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}, vid=0
46d, pid=c05a, manuf=Logitech, prod=USB Optical Mouse, serial=(null))

 [2013-11-07 01:47:20] lowlevel_scan: Found vcom device at com:1 (path=\\.\COM1,
 vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))

 [2013-11-07 01:47:22] CL Platform 0 vendor: Advanced Micro Devices, Inc.

 [2013-11-07 01:47:22] CL Platform 0 name: AMD Accelerated Parallel Processing

 [2013-11-07 01:47:22] CL Platform 0 version: OpenCL 1.2 AMD-APP (1124.2)

 [2013-11-07 01:47:22] Platform 0 devices: 2
 [2013-11-07 01:47:22]  0       Cypress
 [2013-11-07 01:47:22]  1       Cypress
 [2013-11-07 01:47:22] GPU 0 iAdapterIndex 0 strUDID PCI_VEN_1002&DEV_6898&SUBSY
S_22891787&REV_00_4&2B98F9DC&0&0010A iBusNumber 1 iDeviceNumber 0 iFunctionNumbe
r 0 iVendorID 1002 strAdapterName  ATI Radeon HD 5800 Series

 [2013-11-07 01:47:22] GPU 1 iAdapterIndex 3 strUDID PCI_VEN_1002&DEV_6898&SUBSY
S_22891787&REV_00_4&343F1821&0&0020A iBusNumber 2 iDeviceNumber 0 iFunctionNumbe
r 0 iVendorID 1002 strAdapterName  ATI Radeon HD 5800 Series

 [2013-11-07 01:47:22] GPU 0 ATI Radeon HD 5800 Series hardware monitoring enabl
ed
 [2013-11-07 01:47:22] GPU 1 ATI Radeon HD 5800 Series hardware monitoring enabl
ed
 [2013-11-07 01:47:22] Devices detected:
 [2013-11-07 01:47:22]   0. OCL 0 : ATI Radeon HD 5800 Series (driver: opencl)

 [2013-11-07 01:47:22]   1. OCL 1 : ATI Radeon HD 5800 Series (driver: opencl)

 [2013-11-07 01:47:22] Timers: Using QueryPerformanceCounter

 [2013-11-07 01:47:22] Recalibrating timeofday offset (delta 1383757715.799438s)

2 devices listed

[jdkackley]

I'm having absolutely no luck at all with the Blue Fury and BFGMiner

[Luke-Jr]

Downloaded the latest version, bfgminer detects my gpus but not my hashbusters. Something about libusb not supported error comes up quickly when I scan for devices. Would I need to start the miner with special commands?

Shouldn't... Can you paste the output of:

Code:

bfgminer -D -d?

Only one hashbuster connected to this rig atm.

Does Windows see it?

[Luke-Jr]

I'm having absolutely no luck at all with the Blue Fury and BFGMiner

Details? OS? Did you install the driver (if Windows)?

[disclaimer201]

Downloaded the latest version, bfgminer detects my gpus but not my hashbusters. Something about libusb not supported error comes up quickly when I scan for devices. Would I need to start the miner with special commands?

Shouldn't... Can you paste the output of:

Code:

bfgminer -D -d?

Only one hashbuster connected to this rig atm.

Does Windows see it?

I'm using a virtualbox to mine with it just fine. The device gets detected as some usb device, then a virtualbox usb driver is installed by windows. I'm using windows 7 64 bit by the way.

It works fine in the virtual box, but I get an error whenever I want to use more than one device in the virtualbox. Probably some driver issue. That's why I was hoping for an out of the box solution that would support multiple miners on one computer. (Yes, my current "solution" to the problem is to have as many computers as I have hashbuster nanos. Lol)

[Luke-Jr]

Downloaded the latest version, bfgminer detects my gpus but not my hashbusters. Something about libusb not supported error comes up quickly when I scan for devices. Would I need to start the miner with special commands?

Shouldn't... Can you paste the output of:

Code:

bfgminer -D -d?

Only one hashbuster connected to this rig atm.

Does Windows see it?

I'm using a virtualbox to mine with it just fine. The device gets detected as some usb device, then a virtualbox usb driver is installed by windows. I'm using windows 7 64 bit by the way.

It works fine in the virtual box, but I get an error whenever I want to use more than one device in the virtualbox. Probably some driver issue. That's why I was hoping for an out of the box solution that would support multiple miners on one computer. (Yes, my current "solution" to the problem is to have as many computers as I have hashbuster nanos. Lol)

I wonder if the VirtualBox driver messes up the normal one...

[jdkackley]

I'm having absolutely no luck at all with the Blue Fury and BFGMiner

Details? OS? Did you install the driver (if Windows)?

Windows 7 64 bit, Yes I installed the driver. I can get it to work with the BFGMiner they included in the driver package but thats it. Tried your latest version and version 3.2 which worked pretty well for me. I have your latest (i call it 3.5.1) running AM eruptors in the next room. But this thing doesnt like the new versions.

Let me know what I can do to help!

BTW windows sees my Blue Fury

[Luke-Jr]

I'm having absolutely no luck at all with the Blue Fury and BFGMiner

Details? OS? Did you install the driver (if Windows)?

Windows 7 64 bit, Yes I installed the driver. I can get it to work with the BFGMiner they included in the driver package but thats it. Tried your latest version and version 3.2 which worked pretty well for me. I have your latest (i call it 3.5.1) running AM eruptors in the next room. But this thing doesnt like the new versions.

Let me know what I can do to help!

BTW windows sees my Blue Fury

Can you try with -S bigpic:\\.\COMn where n is the number of the COM port it uses?
Be sure you don't do anything between plugging it in fresh, and trying it this way...

Edit: Only slightly more importantly, if you download latest git again (it's changed more), does it work?

[jdkackley]

Luke the latest works with that command. Thank you Thank you.

Can I run that in conjunction with my ASIC Miner usbs? Or do I have to call out all of them separately?

[Luke-Jr]

Luke the latest works with that command. Thank you Thank you.

Can I run that in conjunction with my ASIC Miner usbs? Or do I have to call out all of them separately?

As long as you don't use -S all (or any variant of all)

[cnbtcnews]

why when I use bfgminer, local speed display 880G,  but pool speed display 780G?

[jdkackley]

Luke the latest works with that command. Thank you Thank you.

Can I run that in conjunction with my ASIC Miner usbs? Or do I have to call out all of them separately?

As long as you don't use -S all (or any variant of all)

Thank you for your help kind Sir!

[ThinkFast]

Trying to mine litecoins with bfgminer.
W2KSP3
GPU 0 HD4850

LTC.bat:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
bfgminer -d 0 --scrypt -o http://ltc.give-me-coins.com:3333 -u user.worker -p pass --failover-only --shaders=800 -I 10

Log:
 [2013-11-06 18:46:44] Probing for an alive pool
 [2013-11-06 18:46:45] Pool 0 http://ltc.give-me-coins.com:3333 alive
 [2013-11-06 18:46:45] Network difficulty changed to 1.06k ( 7.57Gh/s)
 [2013-11-06 18:46:45] Stratum from pool 0 detected new block
 [2013-11-06 18:46:45] Pool 0 is hiding block contents from us
 [2013-11-06 18:46:45] Pool 0 now providing block contents to us
 [2013-11-06 18:47:24] Stratum from pool 0 requested work update

Question: Why am I not seeing the complete interface like I do when I'm mining btc? It usually draws it after a few secs.
Is this because I'm running from a batch file?
Thanks!

Also, Is the current version of bfgminer good for mining litecoins? Because in the litecoin Mining hardware comparison I see a lot of references to older versions. I'm assuming the document is out of date. I don't see a lot of info for setting up bfgminer to mine litecoins. Mostly cgminer.

Luke: The README.txt refers to a README.GPU, but there is not such document in the 3.5.0 release.

[Luke-Jr]

Also, Is the current version of bfgminer good for mining litecoins? Because in the litecoin Mining hardware comparison I see a lot of references to older versions. I'm assuming the document is out of date. I don't see a lot of info for setting up bfgminer to mine litecoins.

I don't support scams like Litecoin, but I'm not aware of any reason it wouldn't work.
Maybe someone else who knows or cares about it can provide more helpful advice (and maybe even take over maintaining scrypt in BFGMiner?).

Luke: The README.txt refers to a README.GPU, but there is not such document in the 3.5.0 release.

Thank you for reporting this bug, I will make sure I get it fixed in 3.5.1.

[astutiumRob]

Everyone who had problems with 3.5.0, please test latest git and let me know if I fixed them all...

Latest git build appears to be picking up a non-existant bitfury device which (as it's not there) is gettng 100% HW errors ...
 BPM 0:       |  3.00/21.26/ 0.00Gh/s | A:0 R:0+0(none) HW:692/100%

redoing my standard config and disabling all bitfury related devices seems to fix it:
./configure --enable-scrypt --disable-avalon --disable-opencl --disable-bitfury --disable-bfsb --disable-bigpic --disable-modminer --disable-x6500 --disable-ztex --disable-littlefury --disable-nanofury --disable-metabank --enable-cpumining --enable-bitforce --enable-icarus --disable-knc

-although it has now 'lost' 2 of the USB-BlockErupters

[Luke-Jr]

NEW VERSION 3.5.1, NOVEMBER 7 2013

Human readable changelog:

• Bug fixes only.

Full changelog:

• Bugfix: make-release: Add README.GPU document
• Demote USB string fetch failure to LOG_DEBUG since it is rather common
• Bugfix: RPC: devscan shouldn't be available to read-only access
• Bugfix: bigpic: Ignore the bitfury chip's counter as best we can
• Bugfix: bigpic: Accept other delimiters in Bitfury BF1 product string in autodetection
• Bugfix: Fix VCOM/fpgautils build check
• Bugfix: Only include VCOM code when VCOM/fpgautils support is being built
• Bugfix: Reimplement scan-serial "all" keyword
• Bugfix: bitforce detect: Close device after ZGX failure
• Bugfix: Define lowl_usb even if libusb support is omitted, since VCOM and HID drivers check against it for warnings

[Luke-Jr]

Everyone who had problems with 3.5.0, please test latest git and let me know if I fixed them all...

Latest git build appears to be picking up a non-existant bitfury device which (as it's not there) is gettng 100% HW errors ...
 BPM 0:       |  3.00/21.26/ 0.00Gh/s | A:0 R:0+0(none) HW:692/100%

redoing my standard config and disabling all bitfury related devices seems to fix it:
./configure --enable-scrypt --disable-avalon --disable-opencl --disable-bitfury --disable-bfsb --disable-bigpic --disable-modminer --disable-x6500 --disable-ztex --disable-littlefury --disable-nanofury --disable-metabank --enable-cpumining --enable-bitforce --enable-icarus --disable-knc

-although it has now 'lost' 2 of the USB-BlockErupters

Please

Code:

bfgminer -D -d?