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

storm2k5

member

Activity: 84

Merit: 10

Quote from: Luke-Jr on February 15, 2014, 06:36:44 PM

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 <.<

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: storm2k5 on February 15, 2014, 05:43:37 PM

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.

Quote

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

member

Activity: 84

Merit: 10

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.

Quote

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

storm2k5

member

Activity: 84

Merit: 10

Quote from: nwoolls on February 15, 2014, 02:44:59 PM

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

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: Luke-Jr on February 15, 2014, 01:38:54 PM

Quote from: nwoolls on February 15, 2014, 01:27:54 PM

Quote from: Luke-Jr on February 15, 2014, 12:39:50 PM

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

member

Activity: 84

Merit: 10

Quote from: Luke-Jr on February 15, 2014, 01:38:54 PM

Quote from: nwoolls on February 15, 2014, 01:27:54 PM

Quote from: Luke-Jr on February 15, 2014, 12:39:50 PM

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)

Luke-Jr

legendary

Activity: 2576

Merit: 1186

Quote from: nwoolls on February 15, 2014, 01:27:54 PM

Quote from: Luke-Jr on February 15, 2014, 12:39:50 PM

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

nwoolls

hero member

Activity: 840

Merit: 1002

Quote from: Luke-Jr on February 15, 2014, 12:39:50 PM

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

legendary

Activity: 2576

Merit: 1186

Quote from: storm2k5 on February 15, 2014, 12:35:18 PM

Quote from: Luke-Jr on February 15, 2014, 12:29:04 PM

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.

storm2k5

member

Activity: 84

Merit: 10

Quote from: Luke-Jr on February 15, 2014, 12:29:04 PM

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

legendary

Activity: 2576

Merit: 1186

Quote from: storm2k5 on February 15, 2014, 12:26:01 PM

Quote from: Luke-Jr on February 15, 2014, 11:04:18 AM

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

member

Activity: 84

Merit: 10

Quote from: Luke-Jr on February 15, 2014, 11:04:18 AM

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

legendary

Activity: 2576

Merit: 1186

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

storm2k5

member

Activity: 84

Merit: 10

Quote from: Luke-Jr on February 15, 2014, 10:47:22 AM

Quote from: storm2k5 on February 15, 2014, 09:48:29 AM

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

legendary

Activity: 2576

Merit: 1186

Quote from: storm2k5 on February 15, 2014, 09:48:29 AM

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.

Cassey

sr. member

Activity: 470

Merit: 250

Better to have 100 friends than 100 rubles

Quote from: BRADLEYPLOOF on February 15, 2014, 10:19:58 AM

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 .

BRADLEYPLOOF

hero member

Activity: 520

Merit: 500

Quote from: Cassey on February 14, 2014, 09:10:31 PM

Quote from: Luke-Jr on February 14, 2014, 09:00:38 PM

Diff 1 is very high for scrypt.

Yeah, had a boatload of early GPU raiders drive it up. They have mostly dropped off now, but its going to take days to get through the blocks for a readjustment. That is why I was trying to brings some of my GPUs online to help - we need to solve something like 340 more blocks before the difficulty will drop.

I was quite surprised when within about 4 hours of launch we topped 40MHash/sec in the network pool. Its down to about 7.5MHash now.

FWIW - I did this coin to get educated in the bits, pieces, and processes, and it has been VERY educational

Related question: How would bfgminer behave if I told it to balance between this and my normal real coin pools? Would each pool get 1/2 the effort or would the accepted share rate imbalance come into play?

Please PM me if you would like to know more about my altcoin or related adventures.

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?

storm2k5

member

Activity: 84

Merit: 10

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?

djaychela

newbie

Activity: 35

Merit: 0

Quote from: trojanguys on January 09, 2014, 06:49:29 PM

Please anyone help me understand how to use bfgminer with ant miner, i am a new to all of this and have had no success
Huh

Are you on Windows? I'm assuming you're talking about the Antminer U1

If you are, make sure you have the right drivers installed (The Silicon Labs CP210x ones) so that your ant miners appear as a COM port to Windows. If this isn't right, bfgminer won't be able to access the antminers.

Then you need to launch bfgminer with all the right command line switches for your pool, etc., but importantly add

-S antminer:all

and I think that should do it.

Having said that, if you are on Windows, I'd recommend nwools' excellent multiminer as it makes life a lot easier , giving you a GUI to work with, and allowing swapping coins/pools a piece of cake. It'll download bfgminer for you and takes a lot of the hard work out of getting things up and running.

jedimstr

hero member

Activity: 798

Merit: 1000

Quote from: mfread on February 14, 2014, 11:45:40 PM

@Cassey

You're a champion for posting your Linux miner USB setup, but alas it's mostly gobble-dee-gook to me, but I do hope it helps someone else.

I'll search around to see if anyone has a pre-built .iso I can download (and work out how to get the gfx drivers on to it). Or I'll try and find instructions for the entire process. I'm sure the info is out there, but I was hoping to cut down the days it'll take me to understand all this into something a little more turnkey / manageable

Quote from: Cassey on February 14, 2014, 08:27:26 PM

Quote from: mfread on February 14, 2014, 07:28:52 PM

Does anyone have the know-how to build a LiveCD (or USB) Linux distro to support GPU and ASIC/ANT mining? The GPU in question (for now) is a AMD Radeon 6970 (but might change in the future).

For what its worth, all my main mining machines run a Gentoo Linux booted off a 16GB USB. Works just fine. 3.10.0 is even in the portage tree, although you will need to ACCEPT_KEYWORD override to get the latest version. I took a few early notes when I was building software mirrored USBs, those are attached below (sorry they are a bit long):

--cut--

For a more user friendly Linux setup, you may want to check out BAMT. The latest updated editions are more for GPU mining though so for ASICs you'll still have to do more fiddling.

Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 33. (Read 1193271 times)