Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 144. (Read 5805649 times)

--usb ICA:0 ?

Hi all,

I`m trying to run 3.10 with just drillbits. I want it to disable the cgminer from trying to load my block erupters (i use bfg for that) i have tried --disable-icarus but it says its not a recognised function.

any ideas?

My units arrived today. I will get one shipped out tomorrow.

I guess you are looking for --usb, described in the README starting on line 310?

f.x: ./cgminer --usb BF1:1

Id also be up for this tbh. Fractal BC's code base is great, but its still not stable! Im sure the community as a whole could donate some to you for testing as so many people bought them and they don't worj properly !

I'll donate one to you or kano or ... - which would be easier/cheaper to ship from germany;)

fractalbc already did a good job how it seams:https://github.com/fractalbc/cgminer

As soon as I add the Nanofury devices it crapped out either immediately, or after a number of hours.  There's no other services running at all on the machine, it's a bare (and I do mean bare) install of Debian Wheezy on the BeagleBone Black with only enough installed to get cgminer running.

I'll try upgrading to the latest version on git.

Unplug each while it's running and see which gets unplugged in cgminer.

So how would i go about finding the bad hub or device?

Neither of us have an antminer U1, no one is offering to give us some, and no one is pushing code to us to be accepted for those devices. So at this stage there is precisely zero progress and nothing on the horizon.

Can't think of anything. Possibly totally unrelated and some service on the machine, crond or other.

There was no nanofury support on 3.9.0 

There's a bug in the 3.10.0 release that crashes when a device is (effectively) unplugged that was fixed immediately after in git, so grab a git tarball from master or build from git.

Erupters run at usb1.1 speed and protocol and perhaps are having some communication interaction making everything work in the same crap manner - depends greatly on how usb hubs manage different speed devices. Try them on separate hubs.

One USB connection still appears to be flaky and one of the subdevices appears to be flat out frying. I know of people opening them up and replacing hubs and/or cables to fix them.

Nope, nothing's changed. Just use the cgminer.exe instead.

--usb docs updated

BAS is BFL ASIC
ICA is Icarus based I think block erupters came under that
BF1 I am relatively sure is Bitfury.
BFL is the FPGA boards.
BXF I have no idea on.

The first version
  --usb 1:2,1:3,1:4,1:*
allows you to select which devices to mine on with a list of USB
 bus_number:device_address
All other USB devices will be ignored

The second version
  --usb BAS:1,BFL:1,MMQ:0,ICA:0,KLN:0
allows you to specify how many devices to choose based on each device
driver cgminer has - there are currently 5 USB drivers: BAS, BFL, MMQ.
ICA & KLN
N.B. you can only specify which device driver to limit, not the type of
each device, e.g. with BAS:n you can limit how many BFL ASIC devices will
be checked, but you cannot limit the number of each type of BFL ASIC
Also note that the MMQ count is the number of MMQ backplanes you have
not the number of MMQ FPGAs

The third version
  --usb :10
means only use a maximum of 10 devices of any supported USB devices
Once cgminer has 10 devices it will not configure any more and hotplug will
not scan for any more
If one of the 10 devices stops working, hotplug - if enabled, as is default
- will scan normally again until it has 10 devices

Someone more in the know may correct me. The only ones I used where BAS and BFL so the others are gleaned from reading the forum.

If I want to restrict an instance of cgminer to BitFury mining, e.g. "usb" : "BF1:16,ICA:0,BAS:0", what is the code for them

I've seen BF1, BFL and BXF used in the readmes but no mention where ReadMe explains the 3 ways to use the command.

TIA

Im guessing no further progress has been made with integrating the AntMiner U1's into the CGMiner core code?

I don't see any updates on Github but just thought id check

There's something up with 3.10.0 and Nanofurys.  I was using 3.9.0 with 2xNanofurys and a Bitburner Fury.  3.10.0 worked for a few days, and now segfaults with a glibc error upon execution if the nanos are plugged in.  Works perfectly with just the Bitburner.  cgminer segs as soon as I plug the nanofurys in, too.

Running on Debian Wheezy on x86.