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

[Cassey]

Is there a place to see the network rate or is there a block explorer available?  If not, how hard is it to make one?

All bitcoin/litecoin based wallets will respond to a "getmininginfo" request which will show you the network hashrate.  Please PM me for assistance since that isn't a bfgminer issue, at least not directly <smile>.

[Luke-Jr]

I tried BFGminer 3.10 on win7 on my Hashfast Babyjet yesterday and even tho the "M1" device was listed as an USB device during startup, BFGMiner didn't detect it as a device.

I looked at the readme files but couldn't find any mentioning of the babyjet, even tho release notes state it's supported.
Can anybody help me out?

HashFast uses a USB CDC protocol, so you'll need the correct CDC driver.
I'm not sure if they've made an official one yet or not.

[storm2k5]

I tried BFGminer 3.10 on win7 on my Hashfast Babyjet yesterday and even tho the "M1" device was listed as an USB device during startup, BFGMiner didn't detect it as a device.

I looked at the readme files but couldn't find any mentioning of the babyjet, even tho release notes state it's supported.
Can anybody help me out?

HashFast uses a USB CDC protocol, so you'll need the correct CDC driver.
I'm not sure if they've made an official one yet or not.

I currently use the zadig USB driver with cgminer. AFAIK it doesn't emulate a com port, it just shows up as USB device "M1". I've heard from some people that they got BFGMiner working with the babyjet, so I'm curious how it works.

[Luke-Jr]

Just to clarify, there is no "emulating a com port" going on, VCOM is a native OS interface on every OS.

[storm2k5]

Just to clarify, there is no "emulating a com port" going on, VCOM is a native OS interface on every OS.

So that's what the generic drivers like WinUSB, libusb-win32 and libusbk are for?

Code:

 [2014-02-15 18:10:25] Started bfgminer 3.10.0
 [2014-02-15 18:10:26] usb_devinfo_scan: Error opening device usb:003:001: LIBUSB_ERROR_NOT_SUPPORTED
..
 [2014-02-15 18:10:26] usb_devinfo_scan: Error opening device usb:001:001: LIBUSB_ERROR_NOT_SUPPORTED
 [2014-02-15 18:10:26] hidapi_try_lib: Couldn't load libhidapi.dll: unknown
 [2014-02-15 18:10:26] hidapi_try_lib: Successfully loaded libhidapi-0.dll
 [2014-02-15 18:10:26] hid_devinfo_scan: Found "USB Optical Mouse" serial "	"
 [2014-02-15 18:10:26] hid_devinfo_scan: Found "(null)" serial "	"
 [2014-02-15 18:10:26] hid_devinfo_scan: Found "EP2 Interrupt" serial "	"
 [2014-02-15 18:10:26] hid_devinfo_scan: Found "EP2 Interrupt" serial "	"
 [2014-02-15 18:10:26] hid_devinfo_scan: Found "EP2 Interrupt" serial "	"
 [2014-02-15 18:10:26] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
 [2014-02-15 18:10:26] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
 [2014-02-15 18:10:26] Failed to get PortName registry key value in lowl-vcom.c _vcom_devinfo_scan_windows__hubport():447: The system cannot find the file specified.
 [2014-02-15 18:10:26] FTDI reports 0 devices
 [2014-02-15 18:10:26] FTDI device list failed, not using FTDI autodetect
 [2014-02-15 18:10:26] QueryDosDevice returned insufficent buffer error; enlarging to 200
 [2014-02-15 18:10:26] QueryDosDevice returned insufficent buffer error; enlarging to 400
 [2014-02-15 18:10:26] QueryDosDevice returned insufficent buffer error; enlarging to 800
 [2014-02-15 18:10:26] QueryDosDevice returned insufficent buffer error; enlarging to 1000
 [2014-02-15 18:10:26] QueryDosDevice returned insufficent buffer error; enlarging to 2000
 [2014-02-15 18:10:26] QueryDosDevice returned insufficent buffer error; enlarging to 4000
 [2014-02-15 18:10:26] lowlevel_scan: Found usb device at usb:001:001 (path=(null), vid=1033, pid=0194, manuf=(null), prod=(null), serial=(null))
...
 [2014-02-15 18:10:26] lowlevel_scan: Found usb device at usb:002:013 (path=(null), vid=297c, pid=0001, manuf=HashFast LLC, prod=M1 Module, serial=24dexxxxxxxxxxxxxxxxxxxxxxxxxx)
...
...
 [2014-02-15 18:10:26] No devices detected!

AFAIK there is no manufacturer driver for windows. I might try this on linux.

[Luke-Jr]

Just to clarify, there is no "emulating a com port" going on, VCOM is a native OS interface on every OS.

So that's what the generic drivers like WinUSB, libusb-win32 and libusbk are for?

No, WinUSB/etc just expose a raw USB interface to software.

[storm2k5]

No, WinUSB/etc just expose a raw USB interface to software.

Ok, so I guess if there is no driver for it for windows, then it wont work on windows (not that I'm aware of any manufacturer driver for linux)
Thanks for your help.

[Luke-Jr]

No, WinUSB/etc just expose a raw USB interface to software.

Ok, so I guess if there is no driver for it for windows, then it wont work on windows (not that I'm aware of any manufacturer driver for linux)
Thanks for your help.

Telling Windows to use its standard CDC driver tends to be relatively simple.

[nwoolls]

Telling Windows to use its standard CDC driver tends to be relatively simple.

Is this that Windows INF business? If so I can link to some files and give some pointers.

[Luke-Jr]

Telling Windows to use its standard CDC driver tends to be relatively simple.

Is this that Windows INF business? If so I can link to some files and give some pointers.

Yes

[storm2k5]

Telling Windows to use its standard CDC driver tends to be relatively simple.

Is this that Windows INF business? If so I can link to some files and give some pointers.

Yes

Please. I guess it needs me to make an inf file that loads winusb.sys?
Edit: I was under the impression that this is what zadig does if I tell it to install winusb for the M1 device (it then shows up as an Universal Serial Bus device in devmgr like it should)

[nwoolls]

Telling Windows to use its standard CDC driver tends to be relatively simple.

Is this that Windows INF business? If so I can link to some files and give some pointers.

Yes

Here are some INFs for various CDC devices that I've either downloaded from the manufacturers or created myself:

https://www.dropbox.com/s/jpqcvsnx629ns4s/Windows-Mining-Infs.zip

Basically what you need to do is take one of these (I'd suggest the LittleFury INF) and edit it, replacing:

• The VID values (there are two) with the VID values reported in the Windows Device Manager
• The PID values (again two) with the PID values from Device Manager
• Optional: The VENDOR and PRODUCT values with whatever you like

That's about it. You'll need to jump through whatever hoops your version of Windows requires for using unsigned drivers.

[storm2k5]

That's about it. You'll need to jump through whatever hoops your version of Windows requires for using unsigned drivers.

Yay, success! Thanks for the help!

I have added the inf file I made to the zip and uploaded it:
https://www.dropbox.com/s/w607kpr4j2fh0o0/Windows-Mining-Infs.zip

[storm2k5]

Sorry being such a bother.

I looked at the source on github and found some pointers on how I can set the clock on the BabyJet.

static const struct bfg_set_device_definition hashfast_set_device_funcs_probe[] = {
{"clock", hashfast_set_clock, "clock frequency (can only be set at startup, with --set-device)"},
{NULL},
};

Is clock rate setting through --set-device really implemented? What would be the argument?

I tried things like --set-device HFA:clock=600 which didn't seem to work

[Luke-Jr]

Sorry being such a bother.

I looked at the source on github and found some pointers on how I can set the clock on the BabyJet.

static const struct bfg_set_device_definition hashfast_set_device_funcs_probe[] = {
{"clock", hashfast_set_clock, "clock frequency (can only be set at startup, with --set-device)"},
{NULL},
};

Is clock rate setting through --set-device really implemented? What would be the argument?

I tried things like --set-device HFA:clock=600 which didn't seem to work

Are you actually running the code from git?
That being said, I didn't test this yet either... but it's so simple I'd be surprised by a bug.

[storm2k5]

Are you actually running the code from git?
That being said, I didn't test this yet either... but it's so simple I'd be surprised by a bug.

No, I'm running the 3.10 x86 binaries. Just looking on git to get behind the --set-device syntax. And naturally assumed my syntax is wrong.
Should have looked at git history <.<

[Meuh6879]

request :

After 2-4 days, on my BFL ... i have somes unexpected queue error (a chip does a loop).
BFGminer view this.

In my computer, i have created a "planned job" to kill BFGMiner task every 6 hours and restart after 1 min to avoid this.
But, in BFGMiner, you can add this feature ?

Like :
- if unexpected queue error from 1 chip append, wait 10-20 second
- if always append
- kill USB probe
- restart USB probe after 5 second
- continu job like usual.

Thanks  

Note : i don't touch anything on my setup (i don't unplug BFL or restart PC) ... kill BFGminer and restart solve the problem in all situation.
I have a BFL 12GH/s and a BES 333MH/s.

[zipman]

Hey Guys newbie here still. My powered usb hub I bought was not working right when I plugged in some of my BE. I had an antminer that was not running at the 1.6 it was advertised as. per a suggestion on the site my usb hub might not be putting enough power I looked at the website for the company that made it and right there on the page it said it is not for asic mining. so I returned it and the only beefed up powered usb port they had was a 28 port 4 amp. My question is will I be wasting tons of ports on this beast? I spent like $90 bucks on it. I do plan on building up my mining operation but not all at once just a miner here and there.

[HellDiverUK]

Hey Guys newbie here still. My powered usb hub I bought was not working right when I plugged in some of my BE. I had an antminer that was not running at the 1.6 it was advertised as. per a suggestion on the site my usb hub might not be putting enough power I looked at the website for the company that made it and right there on the page it said it is not for asic mining. so I returned it and the only beefed up powered usb port they had was a 28 port 4 amp. My question is will I be wasting tons of ports on this beast? I spent like $90 bucks on it. I do plan on building up my mining operation but not all at once just a miner here and there.

This thread is NOT the place for this question - try the Hardware section of the forum.

[freddyfarnsworth]

A post from elsewhere:
"""We have not switched from "Scrypt" to "Adaptive-N-Factor Scrypt" (aka supposedly ASIC resistant, as if thats a huge problem for scrypt coins right now) for several very good reasons, all outlined by our development team here: https://kittehcoin.info/forums/meow-technical-discussion/does-kitteh-have-this-same-doge-mining-problem/msg2388/#msg2388; Majsta makes some excellent points as well."""

Any one else no longer able to use bfgminer on scrypt GPU on alt pools ?
All of a sudden, any pool address nothing works here on any of 6 machines.. what changed other than kgw and n factor ?
It was working fine a week ago. I noticed the pools were disconnected from stratum, on reboot nothing works, everywhere.
bfgminer -S opencl:auto --scrypt -o stratum+tcp://altcoinpool.org:3341 -u xxx.xxx -p x -I 9,9,9

Ant / usb / gpu miners on Bitminter still works fine.

Is nwools taking care of scrypt now ?