I have a system that utilizes both gpus and fpgas and I want to run one cgminer instance for gpus and another for fpgas. Starting in 2.11.0 with the new usb subsystem, I am unable to start an instance of cgminer for just the gpus. Whenever I try to start the instance for gpus only, cgminer displays "MTX: BitForce USB failed to get cgminer-usb..." and exits. Is there any way to disable the usb detection like how "-S noauto" used to work?

I don't know if this unique to my rig (7 BFL's on an Atom ITX running Ubuntu 12.10 Server) but I have been using the same steps to git clone and compile going back many versions. Never any issues. Starting today with 2.11.1 when I would start my same cgminer script I have been using it would say "./cgminer: -S: unrecognized option". I removed the "-S auto" from my script and all is good. Just passing the info in case anyone runs into it.

Keep building on the changes required for BFL SC when it comes out, adding new features and fixing bugs with the new 2.11 branch... This is still the unstable development version but is proving quite stable for my testing so far.

I have a system that utilizes both gpus and fpgas and I want to run one cgminer instance for gpus and another for fpgas. Starting in 2.11.0 with the new usb subsystem, I am unable to start an instance of cgminer for just the gpus. Whenever I try to start the instance for gpus only, cgminer displays "MTX: BitForce USB failed to get cgminer-usb..." and exits. Is there any way to disable the usb detection like how "-S noauto" used to work?

--hotplug 0

tried that and still had the same problem

Yep at the moment all BFL/MMQ devices are detected immediately.

--hotplug 0 will only stop it finding new devices when you plug them in.

I've decided on how to handle this already but not implemented it yet.I'll move it further up the todo list

In the mean time, if you start the cgminer that uses the FPGAs first (with -G), then start the GPU cgminer 2nd with --hotplug 0 then the GPU miner won't pick them up at startup or later via hotplug.

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLUFreeNode IRC: irc.freenode.net channel #kano.isMajority developer of the ckpool codeHelp keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!

Keep building on the changes required for BFL SC when it comes out, adding new features and fixing bugs with the new 2.11 branch... This is still the unstable development version but is proving quite stable for my testing so far.

Keep building on the changes required for BFL SC when it comes out, adding new features and fixing bugs with the new 2.11 branch... This is still the unstable development version but is proving quite stable for my testing so far.

Heh whoops, I just got a crash so it's not quite there yet

Yup, me too........

Working on it. There're some fixes in git already which should prevent the crash.

This is a sub net within a closed network, but i get the following after 30 seconds, and I know the addressee works, also made a local host and it still fails with -o http://127.0.0.1:8332 but CG miner crashes (hard) after loading strantum.

Galaxy10 Password: ******* [2013-03-08 13:33:49] Press any key to exit, or cgminer will try again in 15s. [2013-03-08 13:35:07] Pool 0 slow/down or URL or credentials invalid [2013-03-08 13:35:07] Unable to get work from pool 0 http://25.174.60.33:8332 [2013-03-08 13:35:07] No servers were found that could be used to get work from. [2013-03-08 13:35:07] Please check the details from the list below of the servers you have input [2013-03-08 13:35:07] Most likely you have input the wrong URL, forgotten to add a port, or have not set up workers [2013-03-08 13:35:07] Pool: 0 URL: http://25.174.60.33:8332 User:Galaxy10 Password: ******** [2013-03-08 13:35:07] Press any key to exit, or cgminer will try again in 15s.