Bitcoin Forum

Bitcoin => Hardware => Topic started by: mdude77 on May 30, 2013, 06:42:32 PM



Title: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on May 30, 2013, 06:42:32 PM
If there's another thread that describes this, I apologize.  I had to hunt a bit to find everything needed to get it working, so I thought I'd paste it all here so future miners can save some time:

If using version 3.1.1, it needs a driver to make the USB devices visible as COM devices (a UART driver).  Follow these instructions:

1 - As listed in the FPGA-README doc with cgminer, install this driver for your little USB miners: http://sourceforge.net/projects/libwdi/files/zadig/

Note the "latest" link on the top of the page isn't what you want!  You want the one that starts with Zadig.  As of this writing, the version is: zadig_v2.0.1.160.7z
Also note you will need 7zip to unzip it.

2 - After it installs, reboot as windows tells you do.  Wait until Zadig tells you its done installing, windows may ask you before Zadig says it is done.  

Note that you only have to do it once for all your miners, not once for each one.
Also note that the renaming doesn't seem to work right, or is not intuitive.  I tried renaming one and it didn't work.

3 - Install the UART to COM drivers from here: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

4 - Check device manager, you should see items under your ports section now, with the COM port assigned for each one.

5 - Run cgminer-nogpu with these options:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

For my 7 miners, I'm using:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9

Note that if you have more than 7, you will probably need to use this format for the COM ports to recognize COM10 and beyond:

-S \\.\COM3 -S \\.\COM4 -S \\.\COM5 -S \\.\COM6 -S \\.\COM7 -S \\.\COM8 -S \\.\COM9 -S \\.\COM11 -S \\.\COM12 -S \\.\COM13


If using version 3.4.2 (or higher), you do NOT want the UART driver, so follow these instructions:

1 - As listed in the FPGA-README doc with cgminer, install this driver for your little USB miners: http://sourceforge.net/projects/libwdi/files/zadig/

Note the "latest" link on the top of the page isn't what you want!  You want the one that starts with Zadig.  As of this writing, the version is: zadig_v2.0.1.160.7z
Also note you will need 7zip to unzip it.

2 - After it installs, reboot as windows tells you do.  Wait until Zadig tells you its done installing, windows may ask you before Zadig says it is done.  

Note that you only have to do it once for all your miners, not once for each one.
Also note that the renaming doesn't seem to work right, or is not intuitive.  I tried renaming one and it didn't work.

3 - Run cgminer-nogpu with whatever options you need to point to your pools.  No other parms are necessary.  

For my 25 miners, I'm using:

cgminer-nogpu.exe -c "cgminer.conf"


Version 3.1.1 gives me about 333mh/s on Win7x64.  Version 3.4.2 gives me about 335mh/s.  I seem to get less hardware errors on 3.4.2 as well.


If you need a configuration file for pools, here is what I use:

Code:
{
"pools" : [
{
"url" : "http://stratum.btcguild.com:3333",
"user" : "user",
"pass" : "password"
},
{
"url" : "http://stratum.ozco.in:3333",
"user" : "user",
"pass" : "password"
},
{
"url" : "http://192.168.0.194:8332",
"user" : "user",
"pass" : "password"
}
]
}

Note that the first two pools are true pools, the third one is a local instance of bitcoind. 

M


***UPDATED 9/8/2013 to include info on 3.4.2 and an example of cgminer.conf with pools.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Xian01 on May 30, 2013, 07:50:43 PM
Great post ! FWIW, if you don't want to run the separate nogpu executable, you can specify the regular cgminer.exe with the -G flag.

According to Kano in the CGMiner thread, v3.2.0 will have some spectacular work done to make mining with these easier, complete with hot-swap capabilities. Great stuff !


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Adrian-x on May 30, 2013, 08:00:11 PM
Thanks to both of you, just posting so I can find this later, when my USB thingies ship.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on May 31, 2013, 01:42:28 AM
...
Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed.  
...
Yes I posted 115200:2:1 on the first day I got it almost 3 weeks ago and then corrected it that day :P
https://bitcointalk.org/index.php?topic=28402.msg2129115#msg2129115

As you used, you would only use 115200:1:1

3.1.1 still requires the windows serial driver for Icarus devices (but only for Icarus and Avalon devices)

3.2.0 will not use any serial drivers and you must use zadig to set the WinUSB driver for them (3.2.0 will be released shortly)

3.2.0 auto detects all supported USB mining devices and auto hotplugs them all also.
It sets the --icarus-options and --icarus-timing performance numbers automatically for each device also - but you can override them of course.

The Asicminer USB (Block Erupter USB) shows up as "AMU" i.e. AMU 0, AMU 1, AMU 2 ...


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on May 31, 2013, 10:42:40 AM
...
Awesome, I cannot wait to try 3.2.0.  Still waiting for my erupters.

Kano,

Have you had a chance to test 3.2.0 on Windows?  It should work by just compiling git sources or do I have to do anything special?
Same build instructions as 3.1.1?  For running, we need to set WinUSB in zadig, right?  So 3.2.0 will be the first version to use direct USB for Icarus driver.

Feels like I've been working more on the damn windows side than the linux code recently.
Linux on 3.2.0 (out now) is pretty rock solid.

Windows seems to have finally settled down after some strange problems with my VM and power issues with USB on a real windows box.
I'll not be surprised if there are Windows problems, but do help by reporting them if you find any.

Yes all USB devices in cgminer now use WinUSB, the two driver changes for 3.2.0 are Avalon and Icarus = Icarus, Lancelot, Black Arrow Lancelot, Asicminer USB and Cairnsmore1 - but I've no idea even if the Cairnsmore1 code works ...


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: CanaryInTheMine on May 31, 2013, 08:27:33 PM
...
Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed.  
...
Yes I posted 115200:2:1 on the first day I got it almost 3 weeks ago and then corrected it that day :P
https://bitcointalk.org/index.php?topic=28402.msg2129115#msg2129115

As you used, you would only use 115200:1:1

3.1.1 still requires the windows serial driver for Icarus devices (but only for Icarus and Avalon devices)

3.2.0 will not use any serial drivers and you must use zadig to set the WinUSB driver for them (3.2.0 will be released shortly)

3.2.0 auto detects all supported USB mining devices and auto hotplugs them all also.
It sets the --icarus-options and --icarus-timing performance numbers automatically for each device also - but you can override them of course.

The Asicminer USB (Block Erupter USB) shows up as "AMU" i.e. AMU 0, AMU 1, AMU 2 ...
not sure how the new version is supposed to work, but 10 sticks on a hub and not a single one detected with new version... same result as arklan is reporting


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: CanaryInTheMine on June 01, 2013, 08:17:48 AM
...
Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed.  
...
Yes I posted 115200:2:1 on the first day I got it almost 3 weeks ago and then corrected it that day :P
https://bitcointalk.org/index.php?topic=28402.msg2129115#msg2129115

As you used, you would only use 115200:1:1

3.1.1 still requires the windows serial driver for Icarus devices (but only for Icarus and Avalon devices)

3.2.0 will not use any serial drivers and you must use zadig to set the WinUSB driver for them (3.2.0 will be released shortly)

3.2.0 auto detects all supported USB mining devices and auto hotplugs them all also.
It sets the --icarus-options and --icarus-timing performance numbers automatically for each device also - but you can override them of course.

The Asicminer USB (Block Erupter USB) shows up as "AMU" i.e. AMU 0, AMU 1, AMU 2 ...

i've yet to see 3.2.0 work for me... it does not detect anything... i'm still running bfgminer instead.
would like to get cgminer 3.2.0 working though


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 01, 2013, 11:35:02 AM
...
Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed.  
...
Yes I posted 115200:2:1 on the first day I got it almost 3 weeks ago and then corrected it that day :P
https://bitcointalk.org/index.php?topic=28402.msg2129115#msg2129115

As you used, you would only use 115200:1:1

3.1.1 still requires the windows serial driver for Icarus devices (but only for Icarus and Avalon devices)

3.2.0 will not use any serial drivers and you must use zadig to set the WinUSB driver for them (3.2.0 will be released shortly)

3.2.0 auto detects all supported USB mining devices and auto hotplugs them all also.
It sets the --icarus-options and --icarus-timing performance numbers automatically for each device also - but you can override them of course.

The Asicminer USB (Block Erupter USB) shows up as "AMU" i.e. AMU 0, AMU 1, AMU 2 ...

i've yet to see 3.2.0 work for me... it does not detect anything... i'm still running bfgminer instead.
would like to get cgminer 3.2.0 working though

3.1.1 works fine with the info I posted above.  I can't get 3.2.0 to work either.  Some people seem to think it's USB 3.0 hub related.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on June 02, 2013, 01:01:09 AM
...
Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed.  
...
Yes I posted 115200:2:1 on the first day I got it almost 3 weeks ago and then corrected it that day :P
https://bitcointalk.org/index.php?topic=28402.msg2129115#msg2129115

As you used, you would only use 115200:1:1

3.1.1 still requires the windows serial driver for Icarus devices (but only for Icarus and Avalon devices)

3.2.0 will not use any serial drivers and you must use zadig to set the WinUSB driver for them (3.2.0 will be released shortly)

3.2.0 auto detects all supported USB mining devices and auto hotplugs them all also.
It sets the --icarus-options and --icarus-timing performance numbers automatically for each device also - but you can override them of course.

The Asicminer USB (Block Erupter USB) shows up as "AMU" i.e. AMU 0, AMU 1, AMU 2 ...

i've yet to see 3.2.0 work for me... it does not detect anything... i'm still running bfgminer instead.
would like to get cgminer 3.2.0 working though

3.1.1 works fine with the info I posted above.  I can't get 3.2.0 to work either.  Some people seem to think it's USB 3.0 hub related.

M
Yes USB 3.0 is certainly on the top of the list for problems (that I'll need to sort out shortly)

Also the initialisation error (4) I've yet to be able to reproduce the cause for me (and work out a fix)
So certainly for windows, for now I'll say 3.1.1 while I try sort out solutions to problems being seen.
On linux, if 3.2.0 just works, then go with that, if it gets initialisation failures, use 3.1.1 for now until I can sort out that error.

On linux the switch from 3.2.0 back to 3.1.1 just requires you to stop cgminer 3.2.0 and then unplug+replug the USB devices.
If you run USB on both 3.2.0 and 3.1.1 at the same time, it will cause problems.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: twobits on June 02, 2013, 03:12:48 AM
So has anyone gotten it to work with 3.2.0 yet?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Xian01 on June 02, 2013, 03:28:03 AM
So has anyone gotten it to work with 3.2.0 yet?

 Not here. Can't get any of the Erupters to show up in Device Manager as COM devices with the WinUSB driver installed :( Have only been able to get 3.1.1 working with the SiLabs driver :(


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: dwdoc on June 02, 2013, 03:32:43 AM
Kano, keep us posted on 3.2.0. A bunch of USB miner group purchases are being delivered.  :)


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on June 02, 2013, 04:45:47 AM
So has anyone gotten it to work with 3.2.0 yet?

 Not here. Can't get any of the Erupters to show up in Device Manager as COM devices with the WinUSB driver installed

I thought 3.2.0 is using direct USB so you don't need USB/COM divers.  It suppose to detect Erupters as a device attached to USB port not a COM port.
so you should not see any COM ports in the Device Manager.

Or am I missing something?
Yes that's the idea (and it was working for me on windows with just one emerald)
However, the "(4)" error (debug shows that) is something I've not yet resolved - which is I think the cause of failure to initialise on windows for anyone getting that problem.
(and on linux I think some may have see it)

Yes I'll update here once it's sorted out.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: flowdab on June 02, 2013, 06:25:25 AM
If there's another thread that describes this, I apologize.  I had to hunt a bit to find everything needed to get it working, so I thought I'd paste it all here so future miners can save some time:

1 - As listed in the FPGA-README doc with cgminer, install this driver for your little USB miners: http://sourceforge.net/projects/libwdi/files/zadig/

Note the "latest" link on the top of the page isn't what you want!  You want the one that starts with Zadig.  As of this writing, the version is: zadig_v2.0.1.160.7z
Also note you will need 7zip to unzip it.

2 - After it installs, reboot as windows tells you do.  Wait until Zadig tells you its done installing, windows may ask you before Zadig says it is done. 

Note that you only have to do it once for all your miners, not once for each one.
Also note that the renaming doesn't seem to work right, or is not intuitive.  I tried renaming one and it didn't work.

3 - Install the UART to COM drivers from here: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

4 - Check device manager, you should see items under your ports section now, with the COM port assigned for each one.

5 - Run cgminer-nogpu with these options:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

For my 7 miners, I'm using:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9

Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed. 

I'm getting about 333mh/s with the above on Win7x64.

M


You sir are a man among men. Thanks for posting.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 02, 2013, 10:13:10 AM
So has anyone gotten it to work with 3.2.0 yet?

 Not here. Can't get any of the Erupters to show up in Device Manager as COM devices with the WinUSB driver installed

I thought 3.2.0 is using direct USB so you don't need USB/COM divers.  It suppose to detect Erupters as a device attached to USB port not a COM port.
so you should not see any COM ports in the Device Manager.

Or am I missing something?

The way I understand it, there are 2 drivers needed for 3.1.1 to work:

1 - the WinUSB driver to get the item recognized by windows as a USB device
2 - the USB to UART driver to make them accessible via COM port

3.2.0 still requires #1, but not #2.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Rant2112 on June 02, 2013, 06:54:20 PM
I can't get 3.2 to work.

I'm running xUbuntu 13.04.

When I start up cgminer 3.2, syslog shows:

cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
cp210x 2-2.2:1:0: device disconnected

cgminer 3.1.1 works fine with the -S option.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: True___Blue on June 03, 2013, 09:45:06 PM

5 - Run cgminer-nogpu with these options:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

For my 7 miners, I'm using:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9

Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed. 

I'm getting about 333mh/s with the above on Win7x64.

M


I really appreciate your post. For all of us noobs out there can you be a bit more specific on how you do step 5? Very basic stuff I know, but I am trying to learn. When I run my cgminer no gpu it first wants me to enter a url. After I put in the mining pool info and my worker info it goes away. How do I set it up to run using the options you have specified?  I know its connected and working b/c I am able to mine using the USB BE using bitminter's software. Thanks.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 03, 2013, 10:11:12 PM

5 - Run cgminer-nogpu with these options:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

For my 7 miners, I'm using:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9

Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed. 

I'm getting about 333mh/s with the above on Win7x64.

M


I really appreciate your post. For all of us noobs out there can you be a bit more specific on how you do step 5? Very basic stuff I know, but I am trying to learn. When I run my cgminer no gpu it first wants me to enter a url. After I put in the mining pool info and my worker info it goes away. How do I set it up to run using the options you have specified?  I know its connected and working b/c I am able to mine using the USB BE using bitminter's software. Thanks.

Sounds like you are trying to run it from windows explorer?  What you want to do is create a command script to run it that pauses at the end, so you can see what it's saying before windows closes the command window.  If Bitminter's software is working for you, you might want to stick with that.  Bitminter is one of the best pools around if you don't want to go pay per share (PPS).  It's what I use. :)

To make a command script, open notepad and enter something like this:

Code:
cd \mining\cgminer
cgminer.exe [with your parameters]
pause

Then save it where you can easily get to it as cgminer.cmd. Hopefully you've already turned off the "feature" in windows to hide known file extensions (tools -> folder options in windows explorer), otherwise you'll end up with a file called cgminer.cmd.txt.

The cgminer readme has info on what parms to use to specify a pool, password, and so forth.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: logicbomb666 on June 04, 2013, 12:53:43 AM
just wanted to say thanks for making this thread, go my USB miner in the mail today and had it hashing away within minutes due to your info.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: thoughtcourier on June 04, 2013, 04:51:25 AM
I downloaded CGMiner 3.2 which got rid of the -S flag, leading to much swearing on my end before I put a pause on the batch file and the diffed the repo to figure out what this mysterious flag did. There is no -S flag in 3.2, and personally, my auto-detect doesn't work. Only in Bitcoinland does removing features count for user-friendliness (I believe they removed it because 3.2 is supposed to autodetect, but it didn't. Complaints aside, serious thanks to kano and cgminer people)

These instructions work fine for 3.1.
Also, I'm on XP but your instructions worked fine.


Edit: If anyone is wondering, that flag does the following:

--scan-serial|-S <arg> Serial port to probe for Icarus mining device


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: BitAddict on June 04, 2013, 08:42:26 PM

5 - Run cgminer-nogpu with these options:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

For my 7 miners, I'm using:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9

Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed. 

I'm getting about 333mh/s with the above on Win7x64.

M


I really appreciate your post. For all of us noobs out there can you be a bit more specific on how you do step 5? Very basic stuff I know, but I am trying to learn. When I run my cgminer no gpu it first wants me to enter a url. After I put in the mining pool info and my worker info it goes away. How do I set it up to run using the options you have specified?  I know its connected and working b/c I am able to mine using the USB BE using bitminter's software. Thanks.

Thanks for the info. I was really upset trying to make them work with cgminer... it was just shutting down.
But with Bitminter sofware works!!!  ;D


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Humax on June 04, 2013, 11:00:25 PM

For my 7 miners, I'm using:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9

Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed. 

I'm getting about 333mh/s with the above on Win7x64.

M


Thanks for the tip. Yours is the best amoung so many. But I can't get any to work starting at COM10.

Anybody got solution for this? btw, no USB hub. I got 16 USB slots on my pc.

Windows 8 is able to find 1 USB Erupter. Testing on my Windows XP laptop tomorrow.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: DustMite on June 04, 2013, 11:39:46 PM

...I can't get any to work starting at COM10.

Anybody got solution for this? btw, no USB hub. I got 16 USB slots on my pc.

Windows 8 is able to find 1 USB Erupter. Testing on my Windows XP laptop tomorrow.
I'm running Win 7 x64 with a USB hub and I'm having the same problem. As soon as it gets to COM10 and higher it gives an error about unable to find it.
Anybody else have this problem?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: dwdoc on June 04, 2013, 11:54:37 PM
Are they USB 2.0 or 3.0 ports? I am running Windows 7 64bit and have 10 usb miners running with cgminer-nogpu.exe (5 connected to PC and 5 to a Dynex hub). COMs show up all the way to COM16. They are all on USB 2.0 ports. I noticed when I tried connecting one to a usb 3.0 port it did not show up...


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: dwdoc on June 04, 2013, 11:55:29 PM
Anybody found a way to tweak up the hashrate on the usb miners? Is that even possible?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: DustMite on June 05, 2013, 12:07:52 AM
I'm using an Anker USB 3.0 port and I have no problems with COM3-9 but as soon as it gets to double digit COM ports is when I have problems.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 05, 2013, 01:25:21 AM
I'm using an Anker USB 3.0 port and I have no problems with COM3-9 but as soon as it gets to double digit COM ports is when I have problems.

Have you tried using the other format for the COM ports?  I've seen them listed here, something \\COM10\\ or something.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: DustMite on June 05, 2013, 08:25:57 AM
I wound up using these parameters in a batch file for cgminer 3.1.1:

Quote
cgminer-nogpu.exe --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S \\.\COM3 -S \\.\COM4 -S \\.\COM5 -S \\.\COM6 -S \\.\COM7 -S \\.\COM8 -S \\.\COM9 -S \\.\COM11 -S \\.\COM12 -S \\.\COM13

and it was finally able to recognize all 10 of these miners.
They're hashing along nicely around 334 Mh/s each.  :)


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 05, 2013, 09:53:47 AM
I wound up using these parameters in a batch file for cgminer 3.1.1:

Quote
cgminer-nogpu.exe --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S \\.\COM3 -S \\.\COM4 -S \\.\COM5 -S \\.\COM6 -S \\.\COM7 -S \\.\COM8 -S \\.\COM9 -S \\.\COM11 -S \\.\COM12 -S \\.\COM13

and it was finally able to recognize all 10 of these miners.
They're hashing along nicely around 334 Mh/s each.  :)

That's the one I was thinking of.  Thanks, I'll update the top!

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: af_newbie on June 05, 2013, 11:47:51 AM
if you are using the config file (bfgminer) enter them like this:
"disable-gpu" : true,
"auto-fan" : true,
"api-listen" : true,
"api-port" : "4030",
"api-network" : true,
"api-allow" : "W:127.0.0.1",
"expiry" : "120",
"failover-only" : true,
"gpu-threads" : "5",
"log" : "5",
"retry-pause" : "5",
"expiry" : "90",
"queue" : "0",
"scan-time" : "60",
"submit-stale" : true,
"icarus-timing" : "3.0=100",
"icarus-options" : "115200:1:1",
"scan-serial" : [ "icarus:\\\\.\\COM11", "icarus:\\\\.\\COM12" ]


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: DustMite on June 05, 2013, 06:23:45 PM
Oh cool, thanks for posting this. Maybe this will help out others who may be having troubles like I was having.   


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 1phone1world on June 06, 2013, 01:59:56 AM
i am okay with every step up to this one:

5 - Run cgminer-nogpu with these options:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

what exactly does that string of code look like if i am making my own .bat file

also I am only running 1 usb miner and running bitminter for the extra namecoins so where would i input my worker log in info? before or after the icarus timing?



Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Adrian-x on June 06, 2013, 02:56:10 AM
i am okay with every step up to this one:

5 - Run cgminer-nogpu with these options:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

what exactly does that string of code look like if i am making my own .bat file

also I am only running 1 usb miner and running bitminter for the extra namecoins so where would i input my worker log in info? before or after the icarus timing?

You can run it concurrent with a GUP miner using 3.1.1 just use cgminer instead of cgminer-nopu (I have 2 GPU's and 2 USB things) The .bat text below presumes you launch in the root folder of CGMiner, and you mine with btcguild.com (obviously just use your mining pool of choice and change the user name XXXXX and password. Also check the device manager to get the correct COM port once installed.
 
Code:
cgminer -o http://stratum.btcguild.com:3333 -u XXXXX -p password -I 9 --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S //./COM4 
You can find all the tweaking option in the readme text in the root of CGMiner folder.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: qukkM on June 06, 2013, 09:49:41 PM
i have installed both the zadig driver and the UART to COM drivers but 3.1 says no devices are detected, but i can see it in device manager.

on 3.2 it says i need to install a wondows driver for AMU so it at least recognises it is plugged in but i cannot connect to it.

any ideas/


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: tabbek on June 07, 2013, 12:06:07 AM
another thanks out to mdude77 for the short write-up.  got up and running nice and quick like.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 07, 2013, 12:07:13 AM
i have installed both the zadig driver and the UART to COM drivers but 3.1 says no devices are detected, but i can see it in device manager.

on 3.2 it says i need to install a wondows driver for AMU so it at least recognises it is plugged in but i cannot connect to it.

any ideas/

What command line are you using for 3.1.1?

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 1phone1world on June 07, 2013, 12:55:26 AM
i am okay with every step up to this one:

5 - Run cgminer-nogpu with these options:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

what exactly does that string of code look like if i am making my own .bat file

also I am only running 1 usb miner and running bitminter for the extra namecoins so where would i input my worker log in info? before or after the icarus timing?

You can run it concurrent with a GUP miner using 3.1.1 just use cgminer instead of cgminer-nopu (I have 2 GPU's and 2 USB things) The .bat text below presumes you launch in the root folder of CGMiner, and you mine with btcguild.com (obviously just use your mining pool of choice and change the user name XXXXX and password. Also check the device manager to get the correct COM port once installed.
 
Code:
cgminer -o http://stratum.btcguild.com:3333 -u XXXXX -p password -I 9 --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S //./COM4 
You can find all the tweaking option in the readme text in the root of CGMiner folder.

well that got me a bit further  i had to take out the -s//./com4 because it says -s is not a recognizable command i am using 3.2 if that matters. also here is my new error

proving for an alive pool
pool 0 slow/down or URL credentials invalid


and here is my code
Code:
cgminer -o http://mint.bitminter.com:8332 -u xxx -p xxx -I 9 --icarus-options 115200:1:1 --icarus-timing 3.0=100

anyone see anything wrong with this?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 1phone1world on June 07, 2013, 01:40:23 AM
nevermind i got it up and running the problem was with the bitminter log in and it was username_minername and then password..


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 1phone1world on June 07, 2013, 04:45:47 AM
okay sorry for spamming in a row..but i found this topic to be really helpful so i keep coming back here..

I am totally up and running now but i need someone to help with the damage control...

i accidentally changed all my wifes (ports? devices?) to WinUSB (v6.1.7600.16385) with the Zadig program before i know what I was doing..

so now, naturally, her usb keyboard, and mouse don't work.. any suggestions? Haven't tried anything yet, just powered it down and called it a night last night..haha

So she dosen't know yet, so lets fix it? Wired keyboard and mouse = done deal? or am I in a world of shit?

Thanks!

-D


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: CanaryInTheMine on June 07, 2013, 06:19:46 AM
okay sorry for spamming in a row..but i found this topic to be really helpful so i keep coming back here..

I am totally up and running now but i need someone to help with the damage control...

i accidentally changed all my wifes (ports? devices?) to WinUSB (v6.1.7600.16385) with the Zadig program before i know what I was doing..

so now, naturally, her usb keyboard, and mouse don't work.. any suggestions? Haven't tried anything yet, just powered it down and called it a night last night..haha

So she dosen't know yet, so lets fix it? Wired keyboard and mouse = done deal? or am I in a world of shit?

Thanks!

-D
go into device manager and right click on affected devices and do uninstall. reboot and it should reinstall the drivers for the keyboard etc...

obviosuly you may not be able to get into device mamger if your input devices are messed up, so the next thing is to plug in another/different usb keyboard and mouse and then perform what I just suggested

all else fails, do a restore to a previous config.
booting in safe mode may work.. dunno...


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 1phone1world on June 07, 2013, 07:10:06 AM
 ::) :P  Safe mode did not work, but it gave me an idea.

Last known Good configuration is back to being my friend again...at least that gave me back the keyboard! At first i had the mouse too but it reinstalled itself with those corrupt drivers, so i manually did the keyboard control panel uninstall and it worked fine...thanks alot for the reply..

what was weird was the sound was coming from pc speaker haha - haven't heard sound coming from a pc speaker in over 20 years. Anyway its all fixed for now..

good enough.

She'll never know...
Thanks!
-D


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on June 07, 2013, 12:56:07 PM
We've got cgminer 3.2.1 out now :)

Seems there was an initialisation problem that (unfortunately) worked without any problem on my Desktop (Fedora 18) and my Windows VM running on it also.

Finally tracked it down in time for the 3.2.1 release:
https://bitcointalk.org/index.php?topic=28402.msg2397710#msg2397710

Leave feedback in the cgminer thread if you find any problems - thanks :)


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: ndr76 on June 08, 2013, 06:44:02 PM
I have a problem with cgminer on my usb erupter.
3.1.1 works fine, but 3.2.1 gives me this never ending series of errors:

[2013-06-08 19:38:12] USB init open device failed, err -3, you dont have priviledge to access - AMU device 1:9
[2013-06-08 19:38:12] Icarus detect (1:9) failed to initialise (incorrect device?)
 [2013-06-08 19:38:17] USB init open device failed, err -3, you dont have priviledge to access - AMU device 1:9
 [2013-06-08 19:38:17] Icarus detect (1:9) failed to initialise (incorrect device?)
 [2013-06-08 19:38:22] USB init open device failed, err -3, you dont have priviledge to access - AMU device 1:9
 [2013-06-08 19:38:22] Icarus detect (1:9) failed to initialise (incorrect device?)
.....

The only usb connected mining hardware is the AsicMiner usb Erupter.
I set the same permissions on both 3.1.1 and 3.2.1:

-rwxr-sr-x 1 andrea dialout  304853 May 24 09:46 cgminer-3.1.1/cgminer
-rwxr-sr-x 1 andrea dialout 1160140 Jun  8 19:35 cgminer-3.2.1/cgminer

Running debian 7.0.

cgminer compiled with ./configure --enable-icarus --enable-bflsc --disable-opencl

------------------------------------------------------------------------
cgminer 3.2.1
------------------------------------------------------------------------


Configuration Options Summary:

  curses.TUI...........: FOUND: -lncurses
  OpenCL...............: Detection overrided. GPU mining support DISABLED
  scrypt...............: Disabled (needs OpenCL)
  ADL..................: SDK NOT found, GPU monitoring support DISABLED

  Avalon.ASICs.........: Disabled
  BFL.ASICs............: Enabled
  BitForce.FPGAs.......: Disabled
  Icarus.FPGAs.........: Enabled
  ModMiner.FPGAs.......: Disabled
  Ztex.FPGAs...........: Disabled

Compilation............: make (or gmake)
  CPPFLAGS.............:
  CFLAGS...............: -g -O2 -I/usr/include/libusb-1.0  
  LDFLAGS..............:  -lpthread
  LDADD................:  -lcurl   -ljansson -lpthread     -lm -lusb-1.0  

Installation...........: make install (as root if needed, with 'su' or 'sudo')
  prefix...............: /usr/local


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: maxpower on June 08, 2013, 07:04:29 PM
I have a problem with cgminer on my usb erupter.
3.1.1 works fine, but 3.2.1 gives me this never ending series of errors:

[2013-06-08 19:38:12] USB init open device failed, err -3, you dont have priviledge to access - AMU device 1:9
[2013-06-08 19:38:12] Icarus detect (1:9) failed to initialise (incorrect device?)
 [2013-06-08 19:38:17] USB init open device failed, err -3, you dont have priviledge to access - AMU device 1:9
 [2013-06-08 19:38:17] Icarus detect (1:9) failed to initialise (incorrect device?)
 [2013-06-08 19:38:22] USB init open device failed, err -3, you dont have priviledge to access - AMU device 1:9
 [2013-06-08 19:38:22] Icarus detect (1:9) failed to initialise (incorrect device?)
.....

The only usb connected mining hardware is the AsicMiner usb Erupter.
I set the same permissions on both 3.1.1 and 3.2.1:

-rwxr-sr-x 1 andrea dialout  304853 May 24 09:46 cgminer-3.1.1/cgminer
-rwxr-sr-x 1 andrea dialout 1160140 Jun  8 19:35 cgminer-3.2.1/cgminer

Running debian 7.0.

cgminer compiled with ./configure --enable-icarus --enable-bflsc --disable-opencl

------------------------------------------------------------------------
cgminer 3.2.1
------------------------------------------------------------------------


Configuration Options Summary:

  curses.TUI...........: FOUND: -lncurses
  OpenCL...............: Detection overrided. GPU mining support DISABLED
  scrypt...............: Disabled (needs OpenCL)
  ADL..................: SDK NOT found, GPU monitoring support DISABLED

  Avalon.ASICs.........: Disabled
  BFL.ASICs............: Enabled
  BitForce.FPGAs.......: Disabled
  Icarus.FPGAs.........: Enabled
  ModMiner.FPGAs.......: Disabled
  Ztex.FPGAs...........: Disabled

Compilation............: make (or gmake)
  CPPFLAGS.............:
  CFLAGS...............: -g -O2 -I/usr/include/libusb-1.0  
  LDFLAGS..............:  -lpthread
  LDADD................:  -lcurl   -ljansson -lpthread     -lm -lusb-1.0  

Installation...........: make install (as root if needed, with 'su' or 'sudo')
  prefix...............: /usr/local

Try running cgminer with sudo. Normal users generally don't have the right permissions to access raw USB devices. There are some notes about this in the 3.2.1 README.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: ndr76 on June 08, 2013, 08:21:49 PM
I finally managed to get cgminer 3.2.1 to work with Debian 7.0 !  ;D

Her's what I did:
sudo cp cgminer-3.2.1/01-cgminer.rules /etc/udev/rules.d/
sudo service udev restart

Now unplug and plug again the usb erupter.
Restart cgminer and it should work.

cgminer 3.2.1 no longer requires to specify the serial device, nor any icarus timing options. I also read that it should improve the hashing rate compared to 3.1.1.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on June 09, 2013, 12:20:30 PM
Repeat of my request in the cgminer thread:
https://bitcointalk.org/index.php?topic=28402.msg2419696#msg2419696
Question ... ?
Is anyone having problems with cgminer 3.2.1 Icarus mining (Icarus, Lancelot or Erupter only) on anything OTHER than the RPi?
I seem to have narrowed it down to possibly being a timer bug (happening inside libusb - so possibly a kernel problem)
And if you are NOT having problems with 3.2.1 on RPi, could you tell me your kernel version?
with uname -a
Thanks!

Edit: and not using USB 3.0 :)


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 8-bit on June 10, 2013, 01:01:21 PM
Hello, thks for info. Im on Windows XP

I can't seem to get it to pop up in Device Manager. I installed this for step one: http://sourceforge.net/projects/libusb-win32/?source=recommended

Was this correct XP version? I got one of these guys for my BDAY and would love to get her working!


Screenshots:
http://s1341.photobucket.com/user/tommybstring/media/screenshot1_zpsc467e7a0.jpg.html
http://s1341.photobucket.com/user/tommybstring/media/shot2_zps513ef553.jpg.html
http://s1341.photobucket.com/user/tommybstring/media/shot3_zps215d9792.jpg.html
http://s1341.photobucket.com/user/tommybstring/media/shot4_zps9e4b0d04.jpg.html

Thank-You


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 10, 2013, 01:19:52 PM
Hello, thks for info. Im on Windows XP

I can't seem to get it to pop up in Device Manager. I installed this for step one: http://sourceforge.net/projects/libusb-win32/?source=recommended

Was this correct XP version? I got one of these guys for my BDAY and would love to get her working!


Screenshots:
http://s1341.photobucket.com/user/tommybstring/media/screenshot1_zpsc467e7a0.jpg.html
http://s1341.photobucket.com/user/tommybstring/media/shot2_zps513ef553.jpg.html
http://s1341.photobucket.com/user/tommybstring/media/shot3_zps215d9792.jpg.html
http://s1341.photobucket.com/user/tommybstring/media/shot4_zps9e4b0d04.jpg.html

Thank-You

I think you're looking in the wrong place.  Once both drivers are installed, they'll show up under ports, not USB.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 8-bit on June 10, 2013, 02:23:07 PM
you're correct, it was listed under ports.

when i double click cgminer nogpu this is what im seeing

http://s1341.photobucket.com/user/tommybstring/media/shot1_zpsbce4d3f3.jpg.html

this is my first mining attempt, many thks


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 10, 2013, 02:56:39 PM
you're correct, it was listed under ports.

when i double click cgminer nogpu this is what im seeing

http://s1341.photobucket.com/user/tommybstring/media/shot1_zpsbce4d3f3.jpg.html

this is my first mining attempt, many thks

You're using cgminer 3.2.1.  It doesn't work with the UART driver (it's what makes it show up as a COM port).  Use 3.1.1 and you should be fine.

If you want to use 3.2.1, you'll have to uninstall the UART driver.  Rumor has it this doesn't work properly if you have it plugged into a USB 3.0 port.  I haven't tried it yet, took too long for me to recover from trying 3.2.0. :(

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 8-bit on June 10, 2013, 03:38:51 PM
This is the screen I have now using cgminer 3.1.1.
http://s1341.photobucket.com/user/tommybstring/media/shot9_zpsae3bb49f.jpg.html?sort=3&o=0

Its asking for URL, should I type the code you mentioned in last step directly into this space?

(I have a coinotron account and will be using their pool)

Kinda lost, thks


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 10, 2013, 03:41:02 PM
This is the screen I have now using cgminer 3.1.1.
http://s1341.photobucket.com/user/tommybstring/media/shot9_zpsae3bb49f.jpg.html?sort=3&o=0

Its asking for URL, should I type the code you mentioned in last step directly into this space?

(I have a coinotron account and will be using their pool)

Kinda lost, thks

Check cointron for info on what to put in cgminer for mining.  You will need a URL, possibly a port, and a username/pw (you might pick these on the coinotron website).

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 8-bit on June 10, 2013, 04:21:52 PM
done, im logged into cg miner with my coinotron account. 0.0 khash/sec

where do i put the line of code to recognize my usb device, thks


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 10, 2013, 04:23:58 PM
done, im logged into cg miner with my coinotron account. 0.0 khash/sec

where do i put the line of code to recognize my usb device, thks

I think you might have forgotten to change the parameters to cgminer to reflect your COM ports:

Code:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

Put the proper COM ports in where you see x, y, z, and so forth, adding more as needed and deleting those that aren't needed.  If you get up to COM10, you have to use the other format detailed on my first post.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: FiatKiller on June 10, 2013, 04:38:26 PM
::) :P  Safe mode did not work, but it gave me an idea.

Last known Good configuration is back to being my friend again...at least that gave me back the keyboard! At first i had the mouse too but it reinstalled itself with those corrupt drivers, so i manually did the keyboard control panel uninstall and it worked fine...thanks alot for the reply..

what was weird was the sound was coming from pc speaker haha - haven't heard sound coming from a pc speaker in over 20 years. Anyway its all fixed for now..

good enough.

She'll never know...
Thanks!
-D

For future ref: under Accessories > Ease of Access, is an On Screen keyboard if you have mouse but no keyboard. Saved me a few times. I know that was not your exact situation.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 8-bit on June 10, 2013, 04:44:25 PM


Put the proper COM ports in where you see x, y, z, and so forth, adding more as needed and deleting those that aren't needed.  If you get up to COM10, you have to use the other format detailed on my first post.

M
[/quote]

ha, im such a newb :/

What screen am I supposed to be at while adding these COM ports?

somewhere inside cg miner?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 10, 2013, 05:00:47 PM
Quote

Put the proper COM ports in where you see x, y, z, and so forth, adding more as needed and deleting those that aren't needed.  If you get up to COM10, you have to use the other format detailed on my first post.

M

ha, im such a newb :/

What screen am I supposed to be at while adding these COM ports?

somewhere inside cg miner?

Open up notepad.
Enter this:

Code:
cd \mining\cgminer
cgminer-nogpu.exe --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9
pause

Changing the path to your cgminer path as necessary, and the COM ports as necessary.  Then save it as "cgminer.cmd". 

If you haven't configured a pool yet, and saved it, you'll be prompted for your pool URL and credentials.

Once you see everything is working, press the "S" and then "W" in cgminer to save the settings to a configuration file.  Next time it should work w/o asking anything.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 8-bit on June 10, 2013, 05:17:59 PM
I did overwrite the config file now that i have it working. Used the default name.

Last question, I always run the cgminer.cmd file correct? Because if i try the cgminer no gpu file it doesn't work, but cgminer.cmd does.

Whats you LTC wallet address ? Thank-you so much mdude77


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 10, 2013, 05:21:02 PM
I did overwrite the config file now that i have it working. Used the default name.

Last question, I always run the cgminer.cmd file correct? Because if i try the cgminer no gpu file it doesn't work, but cgminer.cmd does.

Whats you LTC wallet address ? Thank-you so much mdude77

The command script (cgminer.cmd) is your best bet.

LTC addy is LWSZmAC1zGUvsSMfGtdhUz39oZfGpEPL38.  Thanks! :)

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 8-bit on June 10, 2013, 05:28:02 PM
wow,that baby runs hot.. i just have one of those sticks, so i wanted to run it right off the USB slot (no fan)

Should i get a hub to get it away from the computer? Possible overheating or fire hazard concerns ??

I'm new and don't want to do something stupid.

Donation Sent, thks again :)


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 10, 2013, 06:01:12 PM
wow,that baby runs hot.. i just have one of those sticks, so i wanted to run it right off the USB slot (no fan)

Should i get a hub to get it away from the computer? Possible overheating or fire hazard concerns ??

I'm new and don't want to do something stupid.

Donation Sent, thks again :)

You want some sort of active cooling on it.  I have a box fan blowing on mine.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Naelr on June 11, 2013, 12:28:37 AM
wow,that baby runs hot.. i just have one of those sticks, so i wanted to run it right off the USB slot (no fan)

Should i get a hub to get it away from the computer? Possible overheating or fire hazard concerns ??

I'm new and don't want to do something stupid.

Donation Sent, thks again :)

You want some sort of active cooling on it.  I have a box fan blowing on mine.

M

a box fan.. woah overkill.. This is all I have for 11 of them and they stay cool to the touch.

https://i.imgur.com/3qfzLG6.jpg?1


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 11, 2013, 12:42:49 AM
wow,that baby runs hot.. i just have one of those sticks, so i wanted to run it right off the USB slot (no fan)

Should i get a hub to get it away from the computer? Possible overheating or fire hazard concerns ??

I'm new and don't want to do something stupid.

Donation Sent, thks again :)

You want some sort of active cooling on it.  I have a box fan blowing on mine.

M

a box fan.. woah overkill.. This is all I have for 11 of them and they stay cool to the touch.

Neat idea.  I still have GPUs, the fan is for the both the GPUs and these.  When the GPUs are gone I'll switch to something smaller.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Adrian-x on June 11, 2013, 01:09:32 AM
wow,that baby runs hot.. i just have one of those sticks, so i wanted to run it right off the USB slot (no fan)

Should i get a hub to get it away from the computer? Possible overheating or fire hazard concerns ??

I'm new and don't want to do something stupid.

Donation Sent, thks again :)

You want some sort of active cooling on it.  I have a box fan blowing on mine.

M
a box fan.. woah overkill.. This is all I have for 11 of them and they stay cool to the touch.

https://i.imgur.com/3qfzLG6.jpg?1
I always get a kick out of seeing other peoples rigs setup, the first thought that goes through my mind is the biggest revolution in the history of the modem worlds is being run on hacked together computers and cooled with little fans, or some inappropriate blower.  In comparison to the well organised server farms of the of a falling financial system.    


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: CommanderVenus on June 11, 2013, 08:42:07 AM
you're correct, it was listed under ports.

when i double click cgminer nogpu this is what im seeing

http://s1341.photobucket.com/user/tommybstring/media/shot1_zpsbce4d3f3.jpg.html

this is my first mining attempt, many thks

You're using cgminer 3.2.1.  It doesn't work with the UART driver (it's what makes it show up as a COM port).  Use 3.1.1 and you should be fine.

If you want to use 3.2.1, you'll have to uninstall the UART driver.  Rumor has it this doesn't work properly if you have it plugged into a USB 3.0 port.  I haven't tried it yet, took too long for me to recover from trying 3.2.0. :(

M
Uninstalling those drivers just makes them appear in "Other devices" with the yellow ! sign. Is there a way to get them working with 3.2.1?

3.1.1 is working just fine in windows 7 32 bit though.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 11, 2013, 09:46:52 AM
you're correct, it was listed under ports.

when i double click cgminer nogpu this is what im seeing

http://s1341.photobucket.com/user/tommybstring/media/shot1_zpsbce4d3f3.jpg.html

this is my first mining attempt, many thks

You're using cgminer 3.2.1.  It doesn't work with the UART driver (it's what makes it show up as a COM port).  Use 3.1.1 and you should be fine.

If you want to use 3.2.1, you'll have to uninstall the UART driver.  Rumor has it this doesn't work properly if you have it plugged into a USB 3.0 port.  I haven't tried it yet, took too long for me to recover from trying 3.2.0. :(

M
Uninstalling those drivers just makes them appear in "Other devices" with the yellow ! sign. Is there a way to get them working with 3.2.1?

3.1.1 is working just fine in windows 7 32 bit though.

Supposedly you have to use Zadig to fix the driver.  It'll then show up in USB devices. 

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: dangue on June 11, 2013, 10:22:57 PM
you're correct, it was listed under ports.

when i double click cgminer nogpu this is what im seeing

http://s1341.photobucket.com/user/tommybstring/media/shot1_zpsbce4d3f3.jpg.html

this is my first mining attempt, many thks

You're using cgminer 3.2.1.  It doesn't work with the UART driver (it's what makes it show up as a COM port).  Use 3.1.1 and you should be fine.

If you want to use 3.2.1, you'll have to uninstall the UART driver.  Rumor has it this doesn't work properly if you have it plugged into a USB 3.0 port.  I haven't tried it yet, took too long for me to recover from trying 3.2.0. :(

M

Just hoping for a quick clarification:  By USB 3.0 port do you mean on the computer or where the miner is physically connected.  I guess what I'm wondering is if the miners being plugged into a USB 3.0 hub but the hub being plugged into a 2.0 port on the computer makes a difference or if any USB 3.0 connection in the chain is enough to mess it up.

I'm running on 3.1.1 right now, but would love to try 3.2.1 to see if it does reduce the number of HW errors as some have reported.  But I don't want to generate unnecessary problems for myself if it is already known not to work.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 12, 2013, 12:30:25 AM
Just hoping for a quick clarification:  By USB 3.0 port do you mean on the computer or where the miner is physically connected.  I guess what I'm wondering is if the miners being plugged into a USB 3.0 hub but the hub being plugged into a 2.0 port on the computer makes a difference or if any USB 3.0 connection in the chain is enough to mess it up.

I'm running on 3.1.1 right now, but would love to try 3.2.1 to see if it does reduce the number of HW errors as some have reported.  But I don't want to generate unnecessary problems for myself if it is already known not to work.

Excellent question.

I can tell you the computer I have my miners on does _not_ have a 3.0 port.  The 3.0 hub is plugged into a 2.0 port.  I could not get 3.2.0 to work, but that may not be USB 3.0 related.  I spent too much time trying to get it work and recovering from that attempt to make me a bit wary of trying again until I see confirmations was others that it's working properly.  So far all I've seen is akin to "we're pretty sure it doesn't work with 3.0".

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: joae1975 on June 12, 2013, 08:15:17 AM
Just got my USB ASICminer running on an Anker USB 3.0 hub using cgminer-nogpu v3.1.1.  So it can be done.  Here's my .bat file txt.

Code:
C:\Users\my name\Desktop\cgminer-3.1.1-windows\cgminer-nogpu.exe -o http://rr.btcmp.com:8332 -u XXX -p YYY --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S \\.\COM3

It worked after repeatedly installing these drivers:
http://sourceforge.net/projects/libwdi/files/zadig/
http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

Keep doing it until the "(COM3)" appears after the "Silicon Labs CP210x USB to UART Bridge"

If "(COM3)" is not visible for 1 USB device, cgminer can't see it.

This is coming from an excited noob miner.   I DID IT!!!

Can't wait for my other 5 to come in the mail.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 12, 2013, 09:44:21 AM
Just got my USB ASICminer running on an Anker USB 3.0 hub using cgminer-nogpu v3.1.1.  So it can be done.  Here's my .bat file txt.

Code:
C:\Users\my name\Desktop\cgminer-3.1.1-windows\cgminer-nogpu.exe -o http://rr.btcmp.com:8332 -u XXX -p YYY --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S \\.\COM3

It worked after repeatedly installing these drivers:
http://sourceforge.net/projects/libwdi/files/zadig/
http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

Keep doing it until the "(COM3)" appears after the "Silicon Labs CP210x USB to UART Bridge"

If "(COM3)" is not visible for 1 USB device, cgminer can't see it.

This is coming from an excited noob miner.   I DID IT!!!

Can't wait for my other 5 to come in the mail.

It definitely works with 3.1.1.  The question is whether it works with 3.2.1 or not.  I have the same config, btw, with an Anker USB 3.0 hub.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: joae1975 on June 12, 2013, 11:17:11 AM
Just got my USB ASICminer running on an Anker USB 3.0 hub using cgminer-nogpu v3.1.1.  So it can be done.  Here's my .bat file txt.

Code:
C:\Users\my name\Desktop\cgminer-3.1.1-windows\cgminer-nogpu.exe -o http://rr.btcmp.com:8332 -u XXX -p YYY --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S \\.\COM3

It worked after repeatedly installing these drivers:
http://sourceforge.net/projects/libwdi/files/zadig/
http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

Keep doing it until the "(COM3)" appears after the "Silicon Labs CP210x USB to UART Bridge"

If "(COM3)" is not visible for 1 USB device, cgminer can't see it.

This is coming from an excited noob miner.   I DID IT!!!

Can't wait for my other 5 to come in the mail.

It definitely works with 3.1.1.  The question is whether it works with 3.2.1 or not.  I have the same config, btw, with an Anker USB 3.0 hub.

M
I read somewhere that the Anker 3.0's wouldn't work with cgminer.  Not trying to be smart, but why should we even care if it doesn't work with 3.2.1 or higher.  If it works, it works....right?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: dangue on June 12, 2013, 02:04:31 PM
Just got my USB ASICminer running on an Anker USB 3.0 hub using cgminer-nogpu v3.1.1.  So it can be done.  Here's my .bat file txt.

Code:
C:\Users\my name\Desktop\cgminer-3.1.1-windows\cgminer-nogpu.exe -o http://rr.btcmp.com:8332 -u XXX -p YYY --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S \\.\COM3

It worked after repeatedly installing these drivers:
http://sourceforge.net/projects/libwdi/files/zadig/
http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

Keep doing it until the "(COM3)" appears after the "Silicon Labs CP210x USB to UART Bridge"

If "(COM3)" is not visible for 1 USB device, cgminer can't see it.

This is coming from an excited noob miner.   I DID IT!!!

Can't wait for my other 5 to come in the mail.

It definitely works with 3.1.1.  The question is whether it works with 3.2.1 or not.  I have the same config, btw, with an Anker USB 3.0 hub.

M
I read somewhere that the Anker 3.0's wouldn't work with cgminer.  Not trying to be smart, but why should we even care if it doesn't work with 3.2.1 or higher.  If it works, it works....right?

That's reportedly version 3.2.0 and 3.2.1 (although it might be fixed in 3.2.1).  The reason why it matters is that cgminer 3.2.1 has been altered to work better with the USB ASICS (making them hot swappable and supposedly reducing the HW error rate).  Getting the HW error rate as low as possible to improve miner efficiency and productivity will help improve profitability.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: joae1975 on June 12, 2013, 02:36:32 PM
That's reportedly version 3.2.0 and 3.2.1 (although it might be fixed in 3.2.1).  The reason why it matters is that cgminer 3.2.1 has been altered to work better with the USB ASICS (making them hot swappable and supposedly reducing the HW error rate).  Getting the HW error rate as low as possible to improve miner efficiency and productivity will help improve profitability.
I have a fan on mine.  FED EX guy just brought 5 more to the door!  WOOT! Hooked 'em up asap.
...getting ~2375Mh/s on 6 USB's


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: dangue on June 12, 2013, 07:50:43 PM
Ran into a weird problem.  My apologies if it has already been answered somewhere, but a search didn't lead me to anything fruitful. 

For the past couple of days I've been running cgminer 3.1.1 with 3 USB ASICs on a Anker 3.0 hub.  I just received two more today.  I plugged them in and made note of the COM ports they were assigned and added them to the bat file.  When I run the file, cgminer recognizes that they are all there, but only "ICA 0" is initialized, "ICA 1" - "ICA 4" all show as "OFF".

Here's the code:
Code:
start /D "C:\Users\Dan\Desktop\Bitcoin\CGMiner" cgminer-nogpu.exe -o stratum+tcp://stratum.bitcoin.cz:3333 -u user.worker2 -p password--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM5 -S COM6 -S COM7 -S COM9

But, if I give each COM it's own line, they all work (but with five different cgminer instances).

Here's that code:
Code:
start /D "C:\Users\Dan\Desktop\Bitcoin\CGMiner" cgminer-nogpu.exe -o stratum+tcp://stratum.bitcoin.cz:3333 -u user.worker2 -p password--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3
start /D "C:\Users\Dan\Desktop\Bitcoin\CGMiner" cgminer-nogpu.exe -o stratum+tcp://stratum.bitcoin.cz:3333 -u user.worker2 -p password--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM5
start /D "C:\Users\Dan\Desktop\Bitcoin\CGMiner" cgminer-nogpu.exe -o stratum+tcp://stratum.bitcoin.cz:3333 -u user.worker2 -p password--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM6
start /D "C:\Users\Dan\Desktop\Bitcoin\CGMiner" cgminer-nogpu.exe -o stratum+tcp://stratum.bitcoin.cz:3333 -u user.worker2 -p password--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM7
start /D "C:\Users\Dan\Desktop\Bitcoin\CGMiner" cgminer-nogpu.exe -o stratum+tcp://stratum.bitcoin.cz:3333 -u user.worker2 -p password--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM9

Ideally, I'd like to have one instance of cgminer open for all of them.  Has anyone else encountered this?  Or any thoughts on how to fix it?  I'm not a coder by trade, so odds are it's something simple that I'm overlooking.  Thanks for the help.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: innovation on June 13, 2013, 02:21:49 PM
oh. I know the use of \\.\. So many thanks to you.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: agibby5 on June 13, 2013, 04:58:11 PM
I got mine working using this:
Code:
.\cgminer-3.1.1-windows\cgminer-nogpu.exe --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S \\.\COM14 -S \\.\COM15 -S \\.\COM16 -S \\.\COM17 -S \\.\COM19 -S \\.\COM20 -S \\.\COM21 -S \\.\COM22 -S \\.\COM23 -S \\.\COM24   

However this is super annoying since when you reboot, the com ports might no longer line up.  Anyway, I couldn't get it working under 3.2.1 at all.  The threads kept dying and the devices were added over and over until cgminer crashes.  Ugh. I wish I didn't have to pass all those command line args to 3.1.1.  I'd rather use the automatically configured 3.2+, however it appears too buggy at the moment for me.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: FiatKiller on June 13, 2013, 11:22:53 PM
Used Orig Post to get 9 instantly working on an Anker plugged into USB 2.0 port and using cg 3.1.1

Will experiment with later cg versions as days go on - just happy to have my first ASICs working! woo hoo!


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Naelr on June 14, 2013, 02:39:27 AM
wow,that baby runs hot.. i just have one of those sticks, so i wanted to run it right off the USB slot (no fan)

Should i get a hub to get it away from the computer? Possible overheating or fire hazard concerns ??

I'm new and don't want to do something stupid.

Donation Sent, thks again :)

You want some sort of active cooling on it.  I have a box fan blowing on mine.

M
a box fan.. woah overkill.. This is all I have for 11 of them and they stay cool to the touch.

https://i.imgur.com/3qfzLG6.jpg?1
I always get a kick out of seeing other peoples rigs setup, the first thought that goes through my mind is the biggest revolution in the history of the modem worlds is being run on hacked together computers and cooled with little fans, or some inappropriate blower.  In comparison to the well organised server farms of the of a falling financial system.    

WOAH MAN THAT IS DEEP... yea that was a quick hack together because the box behind that the fans are on is my NAS that has a mobo going bad.  (New mobo is on floor bought with bitcoins but the memory got lost in shipping)  My plan is to get a junk power supply and rig it up to just start and hook the fans to that.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Naelr on June 14, 2013, 02:42:36 AM
you're correct, it was listed under ports.

when i double click cgminer nogpu this is what im seeing

http://s1341.photobucket.com/user/tommybstring/media/shot1_zpsbce4d3f3.jpg.html

this is my first mining attempt, many thks

You're using cgminer 3.2.1.  It doesn't work with the UART driver (it's what makes it show up as a COM port).  Use 3.1.1 and you should be fine.

If you want to use 3.2.1, you'll have to uninstall the UART driver.  Rumor has it this doesn't work properly if you have it plugged into a USB 3.0 port.  I haven't tried it yet, took too long for me to recover from trying 3.2.0. :(

M

Just hoping for a quick clarification:  By USB 3.0 port do you mean on the computer or where the miner is physically connected.  I guess what I'm wondering is if the miners being plugged into a USB 3.0 hub but the hub being plugged into a 2.0 port on the computer makes a difference or if any USB 3.0 connection in the chain is enough to mess it up.

I'm running on 3.1.1 right now, but would love to try 3.2.1 to see if it does reduce the number of HW errors as some have reported.  But I don't want to generate unnecessary problems for myself if it is already known not to work.

I had  a usb 3.0 4 port plugged into usb 2.0 slot and 3.2.1 worked in linux just fine.  I kept getting zombied devices when I assume they would normally get a hardware error.  The beauty of 3.2.1 was the miner would go offline then comeback as a different usb miner and start hashing away until the next error but my screen would fill up with zombies.  And because of all the zombies going on my hashrate was lower.  I am sticking with 3.1.1 for the higher hashrate and I think it just looks better without 15 zombies not hashing away.

Naelr


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: FiatKiller on June 14, 2013, 10:27:58 AM
You have to remember that higher USB versions are downwardly compatible. You just miss out on any benefits of the newer version like more speed, etc.  90% of the normal users out there have no clue to look for a blue port when plugging in their new devices, so from a marketing standpoint they would never shoot themselves in the foot like that.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: ScaryHash on June 17, 2013, 10:38:45 PM
Hey guys, thanks a bunch !!

Much props for the instructions. Got it running after a little fiddling.

 ;D ;D

Update.

3.2.0 does not work, neither does 3.2.2. Same exact bat file instructions.

3.1.1 works even on high speed blue USB 3.0 ports (tried on a different computer), or regular 2.0 ports.

More updates as I screw with this stuff some more. It does get hot. I just have it sitting on a single usb extension cable lying sideways on the top fan exhaust. Seems to work quite well.




Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: movellan on June 18, 2013, 02:14:48 PM
you're correct, it was listed under ports.

when i double click cgminer nogpu this is what im seeing

http://s1341.photobucket.com/user/tommybstring/media/shot1_zpsbce4d3f3.jpg.html

this is my first mining attempt, many thks

You're using cgminer 3.2.1.  It doesn't work with the UART driver (it's what makes it show up as a COM port).  Use 3.1.1 and you should be fine.

If you want to use 3.2.1, you'll have to uninstall the UART driver.  Rumor has it this doesn't work properly if you have it plugged into a USB 3.0 port.  I haven't tried it yet, took too long for me to recover from trying 3.2.0. :(

M

Just hoping for a quick clarification:  By USB 3.0 port do you mean on the computer or where the miner is physically connected.  I guess what I'm wondering is if the miners being plugged into a USB 3.0 hub but the hub being plugged into a 2.0 port on the computer makes a difference or if any USB 3.0 connection in the chain is enough to mess it up.

I'm running on 3.1.1 right now, but would love to try 3.2.1 to see if it does reduce the number of HW errors as some have reported.  But I don't want to generate unnecessary problems for myself if it is already known not to work.

I had  a usb 3.0 4 port plugged into usb 2.0 slot and 3.2.1 worked in linux just fine.  I kept getting zombied devices when I assume they would normally get a hardware error.  The beauty of 3.2.1 was the miner would go offline then comeback as a different usb miner and start hashing away until the next error but my screen would fill up with zombies.  And because of all the zombies going on my hashrate was lower.  I am sticking with 3.1.1 for the higher hashrate and I think it just looks better without 15 zombies not hashing away.

Naelr

I get the zombie generation on 3.2.1 also, and it crashes shortly after startup. Have you heard of any updates/fixes?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: -ck on June 18, 2013, 02:15:36 PM
3.2.2?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: joae1975 on June 18, 2013, 04:17:58 PM
3.2.2?
i got it working with 3.1.1 using cgminer-nogpu


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: movellan on June 18, 2013, 04:46:06 PM
3.2.2?

Thanks for the heads-up. No more zombies. While on the subject, F-secure flags both executables as trojans. This has been since I started with 3.1.1.1.  I added both the directory and files to the exclusion list, but after an hour or so running time F-secure will try to clean the files, ends up putting them in the quarantine list and the machine hangs and needs a cold-boot to get going again.  Any ideas? Thanks.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: ScaryHash on June 18, 2013, 04:50:11 PM
3.2.2?

Thanks for the heads-up. No more zombies. While on the subject, F-secure flags both executables as trojans. This has been since I started with 3.1.1.1.  I added both the directory and files to the exclusion list, but after an hour or so running time F-secure will try to clean the files, ends up putting them in the quarantine list and the machine hangs and needs a cold-boot to get going again.  Any ideas? Thanks.


Does the same thing on mine. cgminer and cgminer no gpu are flagged as trojans, why I have no idea. I just go to the quarantine list and hit restore, it puts them right back.

One of those things I guess.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: movellan on June 18, 2013, 05:52:18 PM
3.2.2?
i got it working with 3.1.1 using cgminer-nogpu

Thanks again for you help earlier via PM. Newest ver is 3.2.2 and it's working fine now. Command string is

Code:
cgminer-nogpu.exe -o stratum+tcp://stratum.mining.eligius.st:3334 -u <address here> -p x

Just insert your own miner string. You have to uninstall the CP210x_VCP_Windows COM drivers installed for 3.1.1.1 to get 3.2.2.2 to recognize the erupters as AMU units. The Zadig drivers remain. I had to reboot and power-cycle the USB hub for the AMU's to be recognized.



Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: movellan on June 18, 2013, 06:10:23 PM
3.2.2?

Thanks for the heads-up. No more zombies. While on the subject, F-secure flags both executables as trojans. This has been since I started with 3.1.1.1.  I added both the directory and files to the exclusion list, but after an hour or so running time F-secure will try to clean the files, ends up putting them in the quarantine list and the machine hangs and needs a cold-boot to get going again.  Any ideas? Thanks.


Does the same thing on mine. cgminer and cgminer no gpu are flagged as trojans, why I have no idea. I just go to the quarantine list and hit restore, it puts them right back.

One of those things I guess.

I unchecked the "handle harmful files automatically" box and it hasn't popped up again yet.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: joae1975 on June 19, 2013, 12:33:20 AM
Code:
C:\Users\XYZ\Desktop\cgminer-3.1.1-windows\cgminer-nogpu.exe -o http://rr.btcmp.com:8332 -u XXXXX -p YYYYY --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S \\.\COM3 -S \\.\COM4 -S \\.\COM5 -S \\.\COM6 -S \\.\COM7 -S \\.\COM8
This is my command for 6 miners


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: ks3rv3rg on June 20, 2013, 11:42:51 PM
Windows 8
CGminer 3.2.2

cgminer.exe -O USER:PASS -o stratum.triplemining.com:3334 --gpu-powertune 20 --gpu-fan 100 --gpu-engine 1111,1111,1000 --gpu-memclock 1005,1005,900

With this .bat CGminer opens and Runs all three gpus 7950s, as well as recognizes my block erupter.  I have the BE in a USB 3.0 slot and its mining consistently at 333mh/s~.

I followed the instructions in the OP and everything worked perfectly.

Very informative, Thank you.

*edit:  Also, as you can see by my bat config I did not need to include and special settings for the Block Erupter.  I just installed the two drivers, restarted my computer and CGminer 3.2.2 recognized the card.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: movellan on June 22, 2013, 03:20:17 AM
When I received my erupters, I tried using CGminer 3.1.1.1 and 3.2.1. Trying various configs with each version always resulted in machine seizure, sometimes in as little as 20 min and sometimes after 5-6 hours.

I gave up and switched to bfgminer 3.1.0 and no crashes, thank you! However during my attempts to get cgminer working, I had tried uninstalling and re-installing the SiLabs VCP driver several times. Each time the COM port numbers advanced till now I'm up to COM14--> onward. Is there any way to remove all the extra COM ports and get back to COM3 --> onward? TIA.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 22, 2013, 11:15:05 AM
When I received my erupters, I tried using CGminer 3.1.1.1 and 3.2.1. Trying various configs with each version always resulted in machine seizure, sometimes in as little as 20 min and sometimes after 5-6 hours.

I gave up and switched to bfgminer 3.1.0 and no crashes, thank you! However during my attempts to get cgminer working, I had tried uninstalling and re-installing the SiLabs VCP driver several times. Each time the COM port numbers advanced till now I'm up to COM14--> onward. Is there any way to remove all the extra COM ports and get back to COM3 --> onward? TIA.

I had that problem as well.  You can manually renumber them in device manager, somewhere under advanced settings.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: movellan on June 22, 2013, 12:35:46 PM
When I received my erupters, I tried using CGminer 3.1.1.1 and 3.2.1. Trying various configs with each version always resulted in machine seizure, sometimes in as little as 20 min and sometimes after 5-6 hours.

I gave up and switched to bfgminer 3.1.0 and no crashes, thank you! However during my attempts to get cgminer working, I had tried uninstalling and re-installing the SiLabs VCP driver several times. Each time the COM port numbers advanced till now I'm up to COM14--> onward. Is there any way to remove all the extra COM ports and get back to COM3 --> onward? TIA.

I had that problem as well.  You can manually renumber them in device manager, somewhere under advanced settings.

M

Thanks, worked like a charm. BTW, did you ever have an luck with a command line string for Bytecoin solo mining?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on June 22, 2013, 01:20:54 PM
When I received my erupters, I tried using CGminer 3.1.1.1 and 3.2.1. Trying various configs with each version always resulted in machine seizure, sometimes in as little as 20 min and sometimes after 5-6 hours.

I gave up and switched to bfgminer 3.1.0 and no crashes, thank you! However during my attempts to get cgminer working, I had tried uninstalling and re-installing the SiLabs VCP driver several times. Each time the COM port numbers advanced till now I'm up to COM14--> onward. Is there any way to remove all the extra COM ports and get back to COM3 --> onward? TIA.

I had that problem as well.  You can manually renumber them in device manager, somewhere under advanced settings.

M

Thanks, worked like a charm. BTW, did you ever have an luck with a command line string for Bytecoin solo mining?


I don't know what Bytecoin is.. so I'd say no. :)

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: jcpham on June 24, 2013, 03:56:58 PM
http://jcph.am/2013/06/24/usb-erupter-tutorial/

long time cgminer user. bfgminer was easier.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: FiatKiller on June 24, 2013, 07:33:58 PM
I did notice the com port numbers changing on reboot. After reinstalling the WINUSB driver with zadig globally, I got cg 3.2.2 to work. Also, 3.2.3 is out today. May work even better, but I'm not stopping cg to find out! lol


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: ppumkin on June 25, 2013, 10:45:12 AM
Hello guys. I tried setting these guys up on Ubuntu and Windows.

On Ubuntu  (headless console only) there is no driver install required and usgin cgminer 3.2.+ I am supposed to be able to use cgminer without any settings (com ports, icarus-options) 
cgminer starts up and detects all the eropters.. but it seems highlty unstable. the hashing is all over the place and they get sick very often. I have them plugged into a USB 2.0 powered HUB and direct into the MB USB ports. neither one has a stable megahash. How can I fix this? I really want to use Ubuntu as this pc runs 24/7.

SO I went over to windows that has an onboard USB2.0 and USB3.0 - and plugged 1 into each. SO i got 2. I downloaded the zadig utility. It shows the 2 erupters.I press install driver.... failed (other)
They show up as cp2102 USB To uart Bridge adapter? and when i select one from the list it shows the driver as NONE.

I can run cgminer 3.3 nogpu and it says it found the device but it needs the winusb drivers to work.

It seems like I am the only person in the whole world that cannot get any of this stuff to work.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: FiatKiller on June 25, 2013, 06:46:21 PM
Did you try a reboot? Also, make sure it says WinUSB on the box above install and that you have the proper device chosen. It will do them all as a group.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: PeZ on June 25, 2013, 06:49:35 PM
I am still using cgminer 3.1.1 with Angstrom Linux. It has been very stable. People have been having problems with the newer versions.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Quantus on June 27, 2013, 06:30:51 AM
Dose every one have to fight with these things? I thought all the bugs were worked out and that most people could just plug um in? Dose the latest Cg-miner detect the new erupters?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: joae1975 on June 27, 2013, 07:06:30 AM
Dose every one have to fight with these things? I thought all the bugs were worked out and that most people could just plug um in? Dose the latest Cg-miner detect them?
use cgminer 3.1.1 with this code:


Code:
C:\Users\XYZ\Desktop\cgminer-3.1.1-windows\cgminer-nogpu.exe -o http://rr.btcmp.com:8332 -u XXXXX -p YYYYY --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S \\.\COM3 -S \\.\COM4 -S \\.\COM5 -S \\.\COM6 -S \\.\COM7 -S \\.\COM8

Of course change the things you need to change.  Does that help?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: movellan on June 27, 2013, 07:12:45 AM
Dose every one have to fight with these things? I thought all the bugs were worked out and that most people could just plug um in? Dose the latest Cg-miner detect them?

Did you install the Zadig drivers exactly as the OP instructed in the first post of this thread? You must let the installer finish and you will get a message indicating a successful install.

THEN, go to Control Panel > System and Security and click on "Device Manager", then click on "USB Controllers". You should see your ASIC'S listed as UART devices. Now CGminer 3.3.x should auto-recognize them as AMU's and if the rest of your command line is correct they should be mining away.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: movellan on June 27, 2013, 07:18:23 AM
Dose every one have to fight with these things? I thought all the bugs were worked out and that most people could just plug um in? Dose the latest Cg-miner detect them?
use cgminer 3.1.1 with this code:


Code:
C:\Users\XYZ\Desktop\cgminer-3.1.1-windows\cgminer-nogpu.exe -o http://rr.btcmp.com:8332 -u XXXXX -p YYYYY --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S \\.\COM3 -S \\.\COM4 -S \\.\COM5 -S \\.\COM6 -S \\.\COM7 -S \\.\COM8

Of course change the things you need to change.  Does that help?


It will if he has the Zadig drivers properly installed and then installed the SiLabs CP210 drivers ONLY ONCE. If he tried fiddling around installing and un-installing the CP210 stuff like I did at first, the COM numbers are going to be different and your command line might not work for him.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Quantus on June 27, 2013, 07:24:44 AM
I have not even gotten mine yet. But threads like this scare the shit out me


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: movellan on June 27, 2013, 07:28:43 AM
I thought all the bugs were worked out.....?

There are always bugs, even in 1916.

https://www.youtube.com/watch?v=hc5hPcpEL7o (https://www.youtube.com/watch?v=hc5hPcpEL7o)


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Quantus on June 27, 2013, 07:49:59 AM
so you have to use  command line interface for these things you can't use the gui miner interface?
I'm just looking for simplicity. I screw things up at every turn. I'd prefer to install a virtual OS on top of Windows if its easier.

NVM i found a better break down here
http://rdmsnippets.com/tag/install-block-erupter-on-windows-7/


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: joae1975 on June 27, 2013, 10:25:54 AM
so you have to use  command line interface for these things you can't use the gui miner interface?
I'm just looking for simplicity. I screw things up at every turn. I'd prefer to install a virtual OS on top of Windows if its easier.

NVM i found a better break down here
http://rdmsnippets.com/tag/install-block-erupter-on-windows-7/
To be a BTC miner means you gotta learn how to be one.  Search and search the boards, the internet, until you get it.  You will.  We're happy to help, but that's how I learned.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: BR0KK on June 27, 2013, 06:11:58 PM
so you have to use  command line interface for these things you can't use the gui miner interface?
I'm just looking for simplicity. I screw things up at every turn. I'd prefer to install a virtual OS on top of Windows if its easier.

NVM i found a better break down here
http://rdmsnippets.com/tag/install-block-erupter-on-windows-7/
To be a BTC miner means you gotta learn how to be one.  Search and search the boards, the internet, until you get it.  You will.  We're happy to help, but that's how I learned.


im fighting with this right now....



Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: digeros on July 04, 2013, 09:55:17 PM

For my 7 miners, I'm using:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9

Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed. 

I'm getting about 333mh/s with the above on Win7x64.

M


Thanks for the tip. Yours is the best amoung so many. But I can't get any to work starting at COM10.

Anybody got solution for this? btw, no USB hub. I got 16 USB slots on my pc.

Windows 8 is able to find 1 USB Erupter. Testing on my Windows XP laptop tomorrow.

You need to add the \\.\ in front of the com ports call, so it will look like this for cgminer -S \\.\com113 -S \\.\com199... etc


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: BR0KK on July 05, 2013, 11:10:30 AM
If you have a raspberry pi at home give minepeon a try .... ;)


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Neptune on July 09, 2013, 12:40:42 AM
Ok, I've tried this every way I can think...  can't get the zadig drivers to install...when I plug in the AsicMiner I get an error 43...

This is the only thing that has seemed to work(but obviously doesn't)   I plug in the miner, go to device manager and uninstall it, open Zadig and install the WinUSB driver, it says it installs successfully, device manager never changes and I never get a prompt to reboot...

I have installed the CP210x driver also...nothing...  If I try to install the Zadig WinUSB driver without first uninstalling the default driver in Device manager, the install fails.

Anything would help at this point and a big Thanks in advance, this community always steps up!

P.S. when I install the driver from Zadig, the device disappears from the list in Zadig.



Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: ScaryHash on July 09, 2013, 01:39:32 AM
For some strange reason, CG miner 3.1.1 has started crashing with a USB block erupter. Could not get it to work with either cg miner 3.3.1 or 3.2.0 or 3.2.1 or 3.1.1. Even though 3.1.1 worked fine before. ...I know...weird..

So, I went to bfgminer 3.1.2, uninstalled the UART drivers on page 1, rebooted, installed the drivers again, rebooted, and I'm using this line in my .bat file.



bfgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u youraddresshere -p x -I 9 -S all

It recognizes the usb block erupter, no other drivers needed, I don't have to specify a com port, and it's recognizing my dual Nvidia 560GTX cards (yes, i now, don't ask, they were paid for a long time ago...:)

Hope it helps somebody. ;D





Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: sephtin on July 11, 2013, 02:26:32 AM
Ok, I've tried this every way I can think...  can't get the zadig drivers to install...when I plug in the AsicMiner I get an error 43...

This is the only thing that has seemed to work(but obviously doesn't)   I plug in the miner, go to device manager and uninstall it, open Zadig and install the WinUSB driver, it says it installs successfully, device manager never changes and I never get a prompt to reboot...

I have installed the CP210x driver also...nothing...  If I try to install the Zadig WinUSB driver without first uninstalling the default driver in Device manager, the install fails.

Anything would help at this point and a big Thanks in advance, this community always steps up!

P.S. when I install the driver from Zadig, the device disappears from the list in Zadig.

Not sure if you've gotten it working yet, but this (linked earlier in this thread, I think) got me working on 3.1.1:
http://rdmsnippets.com/tag/install-block-erupter-on-windows-7/

Note: don't reset them to WinUSB after installing the other drivers.  Just make sure that they are listed as having COM#, and then specify the COM# in your shortcut or batch file, and you should be ok.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Neptune on July 11, 2013, 01:04:47 PM
Ok, I've tried this every way I can think...  can't get the zadig drivers to install...when I plug in the AsicMiner I get an error 43...

This is the only thing that has seemed to work(but obviously doesn't)   I plug in the miner, go to device manager and uninstall it, open Zadig and install the WinUSB driver, it says it installs successfully, device manager never changes and I never get a prompt to reboot...

I have installed the CP210x driver also...nothing...  If I try to install the Zadig WinUSB driver without first uninstalling the default driver in Device manager, the install fails.

Anything would help at this point and a big Thanks in advance, this community always steps up!

P.S. when I install the driver from Zadig, the device disappears from the list in Zadig.

Not sure if you've gotten it working yet, but this (linked earlier in this thread, I think) got me working on 3.1.1:
http://rdmsnippets.com/tag/install-block-erupter-on-windows-7/

Note: don't reset them to WinUSB after installing the other drivers.  Just make sure that they are listed as having COM#, and then specify the COM# in your shortcut or batch file, and you should be ok.

Ya I've been every permutation of these instructions I can think of and I get the same "no go" situation...  When I plug the devices(I have 3) into any USB port it is reported that there is a problem with the device and it is shut down.  Error 43.  I have tried this on 4 different systems and I get the same error from all 3 USB miners.   The actual information when you look at the properties of the device is:  "Windows has stopped this device becuase it has reported problems. (code 43)"

any further assistance would be greatly appreciated!



Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on July 11, 2013, 01:31:35 PM
Ok, I've tried this every way I can think...  can't get the zadig drivers to install...when I plug in the AsicMiner I get an error 43...

This is the only thing that has seemed to work(but obviously doesn't)   I plug in the miner, go to device manager and uninstall it, open Zadig and install the WinUSB driver, it says it installs successfully, device manager never changes and I never get a prompt to reboot...

I have installed the CP210x driver also...nothing...  If I try to install the Zadig WinUSB driver without first uninstalling the default driver in Device manager, the install fails.

Anything would help at this point and a big Thanks in advance, this community always steps up!

P.S. when I install the driver from Zadig, the device disappears from the list in Zadig.

Not sure if you've gotten it working yet, but this (linked earlier in this thread, I think) got me working on 3.1.1:
http://rdmsnippets.com/tag/install-block-erupter-on-windows-7/

Note: don't reset them to WinUSB after installing the other drivers.  Just make sure that they are listed as having COM#, and then specify the COM# in your shortcut or batch file, and you should be ok.

Ya I've been every permutation of these instructions I can think of and I get the same "no go" situation...  When I plug the devices(I have 3) into any USB port it is reported that there is a problem with the device and it is shut down.  Error 43.  I have tried this on 4 different systems and I get the same error from all 3 USB miners.   The actual information when you look at the properties of the device is:  "Windows has stopped this device becuase it has reported problems. (code 43)"

any further assistance would be greatly appreciated!



Did they ever work?  I would suspect they are damaged, but the odds of having 3 damaged are pretty slim.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Neptune on July 13, 2013, 02:24:54 AM
Actually I got 2 of the 3 miners working which is great, but the third just wont show up as anything other than "Unknown Device" and the 'Bridge' drivers won't install on that device...I've contacted the guy I bought them from and he is willing to try to get it to work and send me an alternate.

Like them so much I bought 3 more yesterday...

Thanks for the help!



Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: aigeezer on July 15, 2013, 11:42:39 PM
I just got five new erupters going on a new Anker USB 3 hub, thanks to a lot of help from this thread and elsewhere.

The usual thrashing about, but two particular oopsies that made things messy for a while: first, despite many comments here, it took me a while to realize that 3.1.1 really is the version to use, at least for now. The main symptom if you don't is that the -S argument is not recognized in 3.3.1 (and other versions, I think). Second, I got obscure errors (pool 0 json stratum auth failed) for a while because of a simple upper/lower case error in the first character of my pool user name - the sort of thing you could stare at and miss for quite a while. Very humbling fooling around with the old DOS-style interface - I used to know that stuff inside out, now it seems absurdly labor-intensive.

I can still use my 7970 with Guiminer at the same time, but the power draw, the heat, and the fan noise will probably make me give it up. I've only tried it with Guiminer for a few minutes just now, but the hash rate for the 7970 seems to be down quite a bit also. Maybe I can use it for gaming!

Five more erupters tomorrow on a different platform and hub if all goes well.

Thanks again for all the good advice here.




Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: rrrix on July 24, 2013, 02:15:14 AM
Followed instructions to the T - using 3.1.1 - perfect!


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: bronan on July 25, 2013, 12:50:39 PM
This far its been some adventure getting these usb miners to work
It looked all simple but it can be less simple just because either hub or usb ports might mess up
I had bought 5 usb erupters from a group buy, and since i received these things been trying to get them to work all 5
Now here comes the crazy thing some work easy others don't
Also had struggled with the jalapeno but since i installed the latest FTDI driver it works easy with bfgminer
Since that i wanted to add the block erupters which i will call amu's from now on i had to try many things
First i tried to get them working with bfgminer but it does not see the amu's
So i took cgminer 3.3.1 and poof it does see 2 amu instant but was whining about the wrong driver
Then i downloaded the zadig driver tool at first zadig does not show any devices

You have to select in the top bar under options list all devices
Then it shows the uart bridge controllers if you plugged all in
This might get confusing or might not even work easy

I found that best way for me was when i had one stick in and reboot after i changed that driver into winusb
people said that only once the winusb driver has to be installed but that does not work on my machines

After that its best to reboot your machine when the zadig has stopped searching
Do not start before it ended the search because windows instant message restart now just wait till that search ended.
I am not sure if its really is needed to wait but to be honest better safe then sorry.

I had to select each and every one of them separate to get the amu's to work

So i took all out besides the one allready installed
You can start cgminer with the mentioned parameters and you see the amu starting to mine at your pool

Then i started zadig again and put the next stick into a free usb slot in cgminer you get the message that it does not have the right driver. Which is libusb by default for windows sadly the rename driver does not work else it would have been easier to see which one has been changed properly.

You select again list all devices in zadig en you will see an newly added uart and when you click on it in zadig you will see in the first box what driver it shows in my pc it showed libusb.

So i changed that by choose install winusb driver.

Now windows whines about reboot again you do not need todo that simply pull the last added amu out and reinsert it.

Meanwhile keep an eye on your running cgminer you will see it being added and a few seconds later it starts hashing like the first
Keep doing that with all of your amu's till they are hashing like they should

After i got them all plugged in from 5 i found 2 stick where giving alot of HW errors and where not sending any shares or at least hardly any.
I think these are flawed/broken sticks ( after 1 day working one of them does not mine at all anymore ), currently trying to get them replaced before i order more of the amu's

Now to make this story even more complex cgminer does not find the stupid jala but guess what the bfgminer finds the jala instant.
But bfgminer refuses to find the amu's  ??? :S
I have been messing with this for several hours and really do not understand why it does see one or the other but not both

There are posts from people who seem to have any hardware running on cgminer and bfgminer but somehow for me its a mess
It might have todo with me running win8 but i am in the proces to buy such a solution like the raspberry pi although i see people having issues with them as well

Some usb hubs gives issues and usb 3.0  ports can be a some work as well, in most cases a pc has usb 2.0 and usb 3.0 slots as soon as you got the amu's to work on the usb 2.0 slots you get them to work on the 3.0 slots as well is what i found out.
I found some ports on the mainboards are shared ports and have a limited power output look carefull at the specs of your mainboard if these ports are shared hubs.
For instance the board of a friend an gigabyte board has 4 usb ports which are actually 2 REAL usb ports but being split into 4 which obvious gave an issue if put 4 amu's in those 4 ports when he took at 1 and put that into the front usb ports they ran fine.


 


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: bitcoiner49er on July 25, 2013, 01:15:19 PM
I had to switch to 3.1.1. Using 3.3 it auto-detects just fine, but would randomly "disconnect" requiring me to hot-plug it (remove from USB port, re-install). Now going on 3 days with no interruptions.  ;D


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: maud138 on August 01, 2013, 01:24:08 PM
I hope somebody can help me.
I use Windows XP and have 3 block erupters. One is working fine with cgminer 3.1.1
I followed the instructions, used the toUARTBridgeVCPDrivers and Zadig.

When I try to install a second (or a third) one, Windows gives an error and says: " I can't load the driver because there is already an exactly the same piece of hardware."

So There isn't a new COM popping up in the hardwaremanager and Zadig doesn't see the second one.

What can I do?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on August 01, 2013, 10:57:33 PM
With 3.1.1 you don't use Zadig for AMUs


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: maud138 on August 05, 2013, 02:06:22 PM
Thanks Kano,

I still don't have more than one Block Erupter working on my Windows XP. Everytime I plug in another one, Windows gives me code 42 "duplicate device".

Is there a solution for this (other than buying a hub, I just have 2 erupters and lots of USB-ports)

Thanks


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Xian01 on August 05, 2013, 02:11:17 PM
With 3.1.1 you don't use Zadig for AMUs

 Sorry for the slight derail, but have you gentlemen made any progress with the USB 3 issues in your latest-and-greatest ? I'm still using 3.1.1 for simplicity as I have USB 3 hubs galore under Windows  :-\


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on August 05, 2013, 02:28:11 PM
With 3.1.1 you don't use Zadig for AMUs

 Sorry for the slight derail, but have you gentlemen made any progress with the USB 3 issues in your latest-and-greatest ? I'm still using 3.1.1 for simplicity as I have USB 3 hubs galore under Windows  :-\
Next release will have the fixed libusb in it (it seems a lot of OS have a bad libusb)
https://bitcointalk.org/index.php?topic=220905.msg2870499#msg2870499
Shouldn't be too far away ...


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Xian01 on August 05, 2013, 03:16:56 PM
Next release will have the fixed libusb in it (it seems a lot of OS have a bad libusb)
https://bitcointalk.org/index.php?topic=220905.msg2870499#msg2870499
Shouldn't be too far away ...

 Kick-ass ! Looking forward to it.

 Cheers.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: dingens on August 05, 2013, 09:46:41 PM
Im gettin following error:

 [2013-08-05 23:38:50] Started cgminer 3.3.0
 [2013-08-05 23:38:50] Started cgminer 3.3.0
 [2013-08-05 23:38:50] USB init, open device failed, err -12, you need to instal
l a WinUSB driver for - AMU device 1:2
 [2013-08-05 23:38:50] Icarus detect (1:2) failed to initialise (incorrect devic
e?)
 [2013-08-05 23:38:51] No devices detected!
 [2013-08-05 23:38:51] Waiting for USB hotplug devices or press q to quit
 [2013-08-05 23:38:51] Need to specify at least one pool server.
Input server details.
URL:
Im on win 7 64, the usb driver is visable at the control panel.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on August 06, 2013, 12:13:14 AM
Im gettin following error:

 [2013-08-05 23:38:50] Started cgminer 3.3.0
 [2013-08-05 23:38:50] Started cgminer 3.3.0
 [2013-08-05 23:38:50] USB init, open device failed, err -12, you need to instal
l a WinUSB driver for - AMU device 1:2
 [2013-08-05 23:38:50] Icarus detect (1:2) failed to initialise (incorrect devic
e?)
 [2013-08-05 23:38:51] No devices detected!
 [2013-08-05 23:38:51] Waiting for USB hotplug devices or press q to quit
 [2013-08-05 23:38:51] Need to specify at least one pool server.
Input server details.
URL:
Im on win 7 64, the usb driver is visable at the control panel.

"USB init, open device failed, err -12, you need to install a WinUSB driver for - AMU device 1:2"

... as per ASIC-README, FPGA-README and README ... on windows you need to switch to the WinUSB driver using Zadig


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: dingens on August 06, 2013, 06:39:56 AM
Oh I got it! Thx so far but my cgminer/cmd closes after the input of pool info...
What Im doing wrong? Im at 50btc.com


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on August 06, 2013, 06:51:59 AM
Oh I got it! Thx so far but my cgminer/cmd closes after the input of pool info...
What Im doing wrong? Im at 50btc.com
No idea ... more info required ...
Run cgminer in a cmd window and you'll see what your next problem is.
My guess would be incorrect pool info - but no idea.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Sharky444 on August 11, 2013, 11:49:23 AM
I'm mining Litecoins with my Radeon 7970, so I have some cgminer experience.

Today I've purchased 2 Block Erupters to also mine Bitcoins.

Unfortunately I've a problem to get both of them running.

I've created a new cgminer folder and installed cgminer 3.2.2 there.

Plugged in the two Block Erupters and installed the drivers from here:

http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

cgminer 3.2.2 did not detect the Erupters, so I've found this thread.

Used zadig.exe to replace the drivers with the WinUSB versions.

So far so good, cgminer-nogpu detection problem is solved. But there's still a problem left!.

Problem: only ONE Erupter is detected!

This is no hardware fault, because if ANY of the TWO erupters I have is plugged to any USB port cgminer detects it, but always only one, so I see this:

 AMU 0:                | 321.5M/317.1Mh/s | A:0 R:0 HW:0 WU: 6.7/m
 
there is no AMU 1:, no matter what I do!?

The device manager (Windows 7 x64) shows two CP21202 USB devices.

Please help!


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on August 11, 2013, 12:41:27 PM
... use 3.3.2 ...


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Yinero on August 12, 2013, 04:13:14 PM
I have no idea what is going on but it is really aggravating....

I follow the guide here to the T. this is what happens.

I instal the zandig drivers then did the UAT to COM driver. Go to start cgminer-nogpu and it says that I need to instal the zandig drivers again.... so I do that and then it says no devices detected. I try to then make a .bat file instead of just starting cgminer-nogpu and all it does is instantly crash and I have everything typed in properly and correct. I'm also using 3.3.2 like everyone is saying too...


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on August 12, 2013, 10:08:03 PM
I have no idea what is going on but it is really aggravating....

I follow the guide here to the T. this is what happens.

I instal the zandig drivers then did the UAT to COM driver. Go to start cgminer-nogpu and it says that I need to instal the zandig drivers again.... so I do that and then it says no devices detected. I try to then make a .bat file instead of just starting cgminer-nogpu and all it does is instantly crash and I have everything typed in properly and correct. I'm also using 3.3.2 like everyone is saying too...

You don't want 3.3.2 if you're using the UAT to COM driver.  Use 3.1.1 with the UAT to COM, or don't use the UAT to COM.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Yinero on August 12, 2013, 10:37:36 PM
I have no idea what is going on but it is really aggravating....

I follow the guide here to the T. this is what happens.

I instal the zandig drivers then did the UAT to COM driver. Go to start cgminer-nogpu and it says that I need to instal the zandig drivers again.... so I do that and then it says no devices detected. I try to then make a .bat file instead of just starting cgminer-nogpu and all it does is instantly crash and I have everything typed in properly and correct. I'm also using 3.3.2 like everyone is saying too...

You don't want 3.3.2 if you're using the UAT to COM driver.  Use 3.1.1 with the UAT to COM, or don't use the UAT to COM.

M

Switched to 3.1.1 didn't change a thing. Still says no USB detected.... and when i run the .bat it just crashes instantly again...


Figured it out:
Quote

--icarus-options 115200:1:1 --icarus-timing 3.0=100
-S COM3 -S COM4

when making the .bat file for 3.1.1. I deleted the strikedout portion of the above quote and cgminer would work with the asics. However instead of them appearing as COM or AMU, it shows up as ICA.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on August 13, 2013, 01:14:21 AM
I have no idea what is going on but it is really aggravating....

I follow the guide here to the T. this is what happens.

I instal the zandig drivers then did the UAT to COM driver. Go to start cgminer-nogpu and it says that I need to instal the zandig drivers again.... so I do that and then it says no devices detected. I try to then make a .bat file instead of just starting cgminer-nogpu and all it does is instantly crash and I have everything typed in properly and correct. I'm also using 3.3.2 like everyone is saying too...

You don't want 3.3.2 if you're using the UAT to COM driver.  Use 3.1.1 with the UAT to COM, or don't use the UAT to COM.

M

Switched to 3.1.1 didn't change a thing. Still says no USB detected.... and when i run the .bat it just crashes instantly again...


Figured it out:
Quote

--icarus-options 115200:1:1 --icarus-timing 3.0=100
-S COM3 -S COM4

when making the .bat file for 3.1.1. I deleted the strikedout portion of the above quote and cgminer would work with the asics. However instead of them appearing as COM or AMU, it shows up as ICA.

All mine show up as ICA.  I have 22 of them on one computer now with 3.1.1, and one long command line. :)

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on August 13, 2013, 06:22:57 AM
...
Figured it out:
Quote

--icarus-options 115200:1:1 --icarus-timing 3.0=100
-S COM3 -S COM4

when making the .bat file for 3.1.1. I deleted the strikedout portion of the above quote and cgminer would work with the asics. However instead of them appearing as COM or AMU, it shows up as ICA.
If you don't use --icarus-options 115200:1:1 --icarus-timing 3.0=100 it will not report on the screen correctly and will probably not hash correctly

You should be using the latest 3.3.3

3.1.1 will show all Icarus driver devices as ICA no matter what they are (and requires -S)

3.3.3 uses the USB naming ICA/LLT/BLT/AMU/CMR and automatically sets the options and automatically finds them ... if you follow the simple documented instructions I wrote in cgminer ...


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: ommfpt on August 22, 2013, 02:09:19 AM
So I've tried this for the past few hours, but nothing is working. The program always tell me something like "error 0 on select in avalon_gets" and something about it not being an avalon. Anyone got anything?

Using 3.3.3. Tried with 3.1.1 and 3.2.1, but no dice on either.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on August 23, 2013, 12:31:03 AM
So I've tried this for the past few hours, but nothing is working. The program always tell me something like "error 0 on select in avalon_gets" and something about it not being an avalon. Anyone got anything?

Using 3.3.3. Tried with 3.1.1 and 3.2.1, but no dice on either.

The latest version is 3.4.0.

Using it for USB erupters is very different between 3.1.1 and newer version.  3.1.1 must have the USB to UART driver installed.  Newer versions must not.  What exactly are you trying?

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: ommfpt on August 23, 2013, 02:47:03 AM
So I've tried this for the past few hours, but nothing is working. The program always tell me something like "error 0 on select in avalon_gets" and something about it not being an avalon. Anyone got anything?

Using 3.3.3. Tried with 3.1.1 and 3.2.1, but no dice on either.

The latest version is 3.4.0.

Using it for USB erupters is very different between 3.1.1 and newer version.  3.1.1 must have the USB to UART driver installed.  Newer versions must not.  What exactly are you trying?

M

I have tried both 3.3.3 and 3.4.0 with no luck, but this may be because of the drivers that I had installed from trying with 3.1.1

edit: uninstalled drivers, now get "No devices detected!"


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: bitcoinsucker1 on August 24, 2013, 01:00:58 AM
Getting this error...  

Win 7 x64



 [2013-08-23 18:59:49] Started cgminer 3.4.0
 [2013-08-23 18:59:49] Started cgminer 3.4.0
 [2013-08-23 18:59:50] USB init, open device failed, err -12, you need to instal
l a WinUSB driver for - ICA device 2:1
 [2013-08-23 18:59:50] Icarus detect (2:1) failed to initialise (incorrect devic
e?)
 [2013-08-23 18:59:54] Need to specify at least one pool server.
Input server details.
URL:


EDIT:  Did the ziag thing seemed to work alright

https://i.imgur.com/pxqXm6M.png

Device drivers

https://i.imgur.com/gMluclI.png


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on August 24, 2013, 01:17:23 AM
Getting this error...  

Win 7 x64



 [2013-08-23 18:59:49] Started cgminer 3.4.0
 [2013-08-23 18:59:49] Started cgminer 3.4.0
 [2013-08-23 18:59:50] USB init, open device failed, err -12, you need to instal
l a WinUSB driver for - ICA device 2:1
 [2013-08-23 18:59:50] Icarus detect (2:1) failed to initialise (incorrect devic
e?)
 [2013-08-23 18:59:54] Need to specify at least one pool server.
Input server details.
URL:


EDIT:  Did the ziag thing seemed to work alright

https://i.imgur.com/pxqXm6M.png

Device drivers

https://i.imgur.com/gMluclI.png

ziag is the USB to UART converter.  3.1.1 needs that, 3.4.0 does not.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: bitcoinsucker1 on August 24, 2013, 01:43:51 AM
Either way im getting that error


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: colemab on August 24, 2013, 04:35:25 AM
If you installed the silabs USB to UART bridge VCP Drivers, be sure to uninstall them - that is unless you are using the bitminter java client.

I am using cgminer 3.3.1 on win x64 and had the same type error until I removed the above driver and then re-added the zdiag (win usb) drivers and rebooted.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: enki74 on August 27, 2013, 08:42:25 AM
If you installed the silabs USB to UART bridge VCP Drivers, be sure to uninstall them - that is unless you are using the bitminter java client.

I am using cgminer 3.3.1 on win x64 and had the same type error until I removed the above driver and then re-added the zdiag (win usb) drivers and rebooted.

So to be clear you are saying with cgminer 3.4.0 uninstall uart bridge drivers? How is this done thru the zadig? you have (zdiag) above is this a typo? I have been trying this all day and only gotten worse now I can not even figure out what my usb drivers should look like?
Thanks for any help....

additional info:
I have had the ASIC running on cgminer 2.11.3 and usb to uart bridge drivers from silcon labs but wanted to integrate my ASIC's with Multimine and use the new cgminer 3.4.0 which this thread says to remove the Uart drivers from Silcon labs, sooo my questions are:

How to remove the USB to UART bridge drivers and how to install the ??? whatever drivers to run with cgminer 3.4.0 .....

I have been using the zadig utility which I must say is confusing at best.  Is there a sequence to plugging in the ASIC's or the usb hubs after before anything like that?  So anyone that can shed some clear light on this is much appreciated! now I'm off to catch som zzz'z after a 24 hrs up!


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: aigeezer on August 27, 2013, 12:14:58 PM
I have no helpful advice right now, but I thought it might be useful to mention my "port chaos" yesterday, still not completely resolved, from adding a few more erupters. I had ten erupters running smoothly on 3.1.1 using two Anker hubs, seven on one hub and three on the other. My intended change was to add four more erupters, to yield a total of fourteen on this 'puter (core i7, Win7 64). Should have been trivial, right?

Several hours later, I got the system stable again using three of the planned additions - a fourth would always make CGMiner crash, although that fourth erupter will run fine on other machines. A non-mining USB device using a virtual COM port (COM 1) has been disabled somehow in the process, details unknown so far. COM port allocation would change on most reboot and hub connect/disconnect cycles. USB controllers might get recognized immediately by Win7 or recognition might take minutes. Sometimes driver uninstall/replacement appeared to help, other times not.

I realize 3.1.1 is not the latest version, and that some of my problems are certainly of my own making. My main point in writing this is to warn that such changes are not trivial, and that (as far as I know) there are no clear, concise instructions around that will cover all upgrade situations.

I'm confident that a few more hours today will get everything working, but I expect it to be picky, tedious work geek summertime fun.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: movellan on August 27, 2013, 02:08:03 PM
I have no helpful advice right now, but I thought it might be useful to mention my "port chaos" yesterday, still not completely resolved, from adding a few more erupters. I had ten erupters running smoothly on 3.1.1 using two Anker hubs, seven on one hub and three on the other. My intended change was to add four more erupters, to yield a total of fourteen on this 'puter (core i7, Win7 64). Should have been trivial, right?

Several hours later, I got the system stable again using three of the planned additions - a fourth would always make CGMiner crash, although that fourth erupter will run fine on other machines. A non-mining USB device using a virtual COM port (COM 1) has been disabled somehow in the process, details unknown so far. COM port allocation would change on most reboot and hub connect/disconnect cycles. USB controllers might get recognized immediately by Win7 or recognition might take minutes. Sometimes driver uninstall/replacement appeared to help, other times not.

I realize 3.1.1 is not the latest version, and that some of my problems are certainly of my own making. My main point in writing this is to warn that such changes are not trivial, and that (as far as I know) there are no clear, concise instructions around that will cover all upgrade situations.

I'm confident that a few more hours today will get everything working, but I expect it to be picky, tedious work geek summertime fun.


What works for me:

1) Shut down computer

2) Shut off all hubs containing Erupters. Do not use other devices on the same hub with Erupters.

3) Start computer and let it normalize to idle. If you are using any sort of VPN, do not start it yet.

4) Open up device manager and open the COM ports entry.

5) Turn on the first hub (with 7 USB units in your case) containing Erupters and watch the COM ports listing. After a few seconds you should have COM3 through  COM9 listed. If not, check for dupes. If found, check for missing COM port(s). If missing are found, right click on the second entry of the dupe and go to Advanced and change it the the missing port number. Once everything is set OK, run your miner to verify that all COM's are working OK.

6) Shut down computer and shut off the hub. Unfortunately I have to go through this each time changes are made. Perhaps your experience will differ.

7) Start computer, let normalize, and turn on the first hub again. Check device manager to see if all ports have returned properly.

8) Now turn on the second hub and go through the above procedure to set the COM ports correctly.

9) When everything is working OK, you can turn on the VPN if in use. Go through the startup routine a few times. It seems Windoze will "remember" the COM setup after a few starts and give less trouble on subsequent runs.

HTH


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: enki74 on August 27, 2013, 02:51:39 PM
I have no helpful advice right now, but I thought it might be useful to mention my "port chaos" yesterday, still not completely resolved, from adding a few more erupters. I had ten erupters running smoothly on 3.1.1 using two Anker hubs, seven on one hub and three on the other. My intended change was to add four more erupters, to yield a total of fourteen on this 'puter (core i7, Win7 64). Should have been trivial, right?

Several hours later, I got the system stable again using three of the planned additions - a fourth would always make CGMiner crash, although that fourth erupter will run fine on other machines. A non-mining USB device using a virtual COM port (COM 1) has been disabled somehow in the process, details unknown so far. COM port allocation would change on most reboot and hub connect/disconnect cycles. USB controllers might get recognized immediately by Win7 or recognition might take minutes. Sometimes driver uninstall/replacement appeared to help, other times not.

I realize 3.1.1 is not the latest version, and that some of my problems are certainly of my own making. My main point in writing this is to warn that such changes are not trivial, and that (as far as I know) there are no clear, concise instructions around that will cover all upgrade situations.

I'm confident that a few more hours today will get everything working, but I expect it to be picky, tedious work geek summertime fun.


I have had 14 total running with 3.1.1 two 10 port hubs half populated (seems to not be able to go more than that) one 5 port with three and one straight into the back of the machine running on windows 7 but noooo I wanted to put them into multiminer and now have none working :(.......


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: aigeezer on August 27, 2013, 09:19:00 PM
Getting this error...  

Win 7 x64



 [2013-08-23 18:59:49] Started cgminer 3.4.0
 [2013-08-23 18:59:49] Started cgminer 3.4.0
 [2013-08-23 18:59:50] USB init, open device failed, err -12, you need to instal
l a WinUSB driver for - ICA device 2:1
 [2013-08-23 18:59:50] Icarus detect (2:1) failed to initialise (incorrect devic
e?)
 [2013-08-23 18:59:54] Need to specify at least one pool server.
Input server details.
URL:


EDIT:  Did the ziag thing seemed to work alright

https://i.imgur.com/pxqXm6M.png

Device drivers

https://i.imgur.com/gMluclI.png

After some trial and error I got to that stage also (using 3.4.0 now with old drivers deleted and so forth). I've gone a bit farther in an attempt to pin things down. I disconnected both my hubs, and used only a single block erupter plugged directly into a casefront USB socket. My list of USB devices now shows only that single device which I had renamed to "Block Erupter" using the edit function in Zadig.

After reboots and appropriate waits, I get the same kind of error some of us have been getting with hubs, namely this kind of thing "open device failed, err -12, you need to install a WinUSB driver for...". This is after installing a WinUSB driver as shown in bitcoinsucker1's post.

If I run just cgminer it will find my graphics card as expected and start mining with it, while also producing the error message for the Erupter. If I run cgminer-nogpu it produces only the error message. With multiple Erupters it produces multiple similar error messages.

I'm still digging, but that's what I know so far - it's not a hub or multiple Erupter issue, and 3.4.0 finds my graphics card (anyone remember them for mining?) without any fuss.

Edit: It's getting interesting. The single erupter was plugged in to a USB 3.0 port on the front of my machine. CGMiner was giving "error -12" messages. I added a second erupter on a USB 2.0 port also on the front of the machine and it started mining right away. CGMiner was running throughout, so it recognized the hot-plugged second erupter. The "error -12" messages continued. I pulled out the original erupter but the messages did not stop. I plugged that erupter into another USB 2.0 port and it started mining after a brief delay. So at the moment my miners work with CGMiner on USB 2.0 ports but not on a USB 3.0 port (which used to be connected to a hub that worked with miners on 3.1.1). The error -12 messages keep coming though. More testing soon - getting closer.

    


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on August 27, 2013, 10:01:38 PM
I have no helpful advice right now, but I thought it might be useful to mention my "port chaos" yesterday, still not completely resolved, from adding a few more erupters. I had ten erupters running smoothly on 3.1.1 using two Anker hubs, seven on one hub and three on the other. My intended change was to add four more erupters, to yield a total of fourteen on this 'puter (core i7, Win7 64). Should have been trivial, right?

Several hours later, I got the system stable again using three of the planned additions - a fourth would always make CGMiner crash, although that fourth erupter will run fine on other machines. A non-mining USB device using a virtual COM port (COM 1) has been disabled somehow in the process, details unknown so far. COM port allocation would change on most reboot and hub connect/disconnect cycles. USB controllers might get recognized immediately by Win7 or recognition might take minutes. Sometimes driver uninstall/replacement appeared to help, other times not.

I realize 3.1.1 is not the latest version, and that some of my problems are certainly of my own making. My main point in writing this is to warn that such changes are not trivial, and that (as far as I know) there are no clear, concise instructions around that will cover all upgrade situations.

I'm confident that a few more hours today will get everything working, but I expect it to be picky, tedious work geek summertime fun.

Hmm.  I'm using 22 erupters atm, 19 on 10-port hubs, 3 on a 5-port hub.  I started with one hub.  Every step along the way to add more, this is what I do:

1 - Plug in the new erupter.  If a new hub is needed, plug it in first.
2 - Shut down cgminer.
3 - Change my cgminer script to reference the new COM ports (have always been incremental, so if I have 5 and the last one is COM7, the next one is COM8)
4 - Restart cgminer.

Sometimes I have reset a USB hub, but usually "it just works".

Note my hubs are not daisy chained.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: miter_myles on August 27, 2013, 10:52:17 PM
I was starting to get pissed one night setting things up when I realized on my mobo (ASrock extreme 3)... I had half of my setup plugged into a usb 2.0 port and the other have on a usb 3.0 port.. which was reading the erupters differently and not playing nice... keeping everything on usb 2.0 ports (for me at least) keeps things playing nice..


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: aigeezer on August 27, 2013, 11:36:43 PM
I was starting to get pissed one night setting things up when I realized on my mobo (ASrock extreme 3)... I had half of my setup plugged into a usb 2.0 port and the other have on a usb 3.0 port.. which was reading the erupters differently and not playing nice... keeping everything on usb 2.0 ports (for me at least) keeps things playing nice..

I'm starting to think the same way. I just got all my miners working finally (see gory details upthread). Things started to get better when I stopped using USB 3.0 ports (where CGMiner 3.1.1 used to work fine with ten miners on two Anker hubs) and switched to USB 2.0, working up from a single Erupter miner there to my present setup which is:

Two Anker hubs daisy-chained, one with six erupters and the other with seven, plugged into a single USB 2.0 socket on the mobo at the back of the case.

It's not conclusive, but it's strongly suggestive that something goes wrong with USB 3.0, possibly only after version 3.1.1 of CGMiner.

One more little thing that I'm too tired to look into right now - the CGMiner reporting window is pretty full with "accepted" messages (yea) but from time to time I see a truncated "e?>" popping up in the left hand corner. I fear it's the old "error -12" message still coming up, but mainly hidden by the good stuff now. I'll check into it Real Soon Now.              :)

Thanks for the help, everyone. It seems like we all have similar but still unique things happening.



Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: JBT on September 03, 2013, 07:11:18 PM
this really helped to get going.   but all this is to use one worker, i got mine like this
cgminer.exe -o http://stratum.bitcoin.cz:3333 -u worker.name1 -p password5 -G -S \\.\com11 --icarus-options 115200:1:1 --icarus-timing 3.0=100

i have 5 shortcuts for each stick. i just changed worker.name1 to worker.name2 3 4 5.

is there a better way?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: aigeezer on September 03, 2013, 10:10:17 PM
this really helped to get going.   but all this is to use one worker, i got mine like this
cgminer.exe -o http://stratum.bitcoin.cz:3333 -u worker.name1 -p password5 -G -S \\.\com11 --icarus-options 115200:1:1 --icarus-timing 3.0=100

i have 5 shortcuts for each stick. i just changed worker.name1 to worker.name2 3 4 5.

is there a better way?

It seems to be safe now to move up to 3.4.0 or 3.4.1, in which case the parameters become much simpler. I have one machine still running 7 erupters on 3.1.1 with the messy parameters. It never crashes. My machine running 3.4.0 for a week or so and 3.4.1 as of yesterday crashes cgminer about once a day, for reasons yet unknown.

One shortcut should handle several workers though, regardless of version.

For example, this bat file using 3.4.1 finds all 13 erupters mounted on two hubs and allows for a backup pool:

C:\cgminer\cgminer-3.4.1-windows\cgminer-nogpu.exe -o http://stratum.bitcoin.cz:3333 -u blah.blee -p somepassword -o http://stratum.btcguild.com:3333 -u blah_something -p whatever




Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on September 03, 2013, 10:54:49 PM
this really helped to get going.   but all this is to use one worker, i got mine like this
cgminer.exe -o http://stratum.bitcoin.cz:3333 -u worker.name1 -p password5 -G -S \\.\com11 --icarus-options 115200:1:1 --icarus-timing 3.0=100

i have 5 shortcuts for each stick. i just changed worker.name1 to worker.name2 3 4 5.

is there a better way?

It seems to be safe now to move up to 3.4.0 or 3.4.1, in which case the parameters become much simpler. I have one machine still running 7 erupters on 3.1.1 with the messy parameters. It never crashes. My machine running 3.4.0 for a week or so and 3.4.1 as of yesterday crashes cgminer about once a day, for reasons yet unknown.

One shortcut should handle several workers though, regardless of version.

For example, this bat file using 3.4.1 finds all 13 erupters mounted on two hubs and allows for a backup pool:

C:\cgminer\cgminer-3.4.1-windows\cgminer-nogpu.exe -o http://stratum.bitcoin.cz:3333 -u blah.blee -p somepassword -o http://stratum.btcguild.com:3333 -u blah_something -p whatever

Good to know.  I was thinking I'll put 3.4.2 on another rig and move the erupters over there.  That way if it doesn't work, it won't take an hour reconfiguring the drivers.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Rival on September 03, 2013, 11:13:01 PM
I have  W7 x64. Just got in 9 sticks delivered today Plugged them into a 10 port Anker Uspeed 3.0. Loaded cgminer 3.1.1, and loaded the UART to COM drivers listed by the OP. Ran into the issue where I had to specify -s for each COM device, but that was it. 9 sticks hashing at just over 3Ghs happily cooled by the Artic Breeze as recommended by the OP.

It could not have been easier, it took less than 20 minutes from part arrival to hashing.

My total out-of-pocket was a little high at $370 but I bought the sticks on ebay. This includes the hub and fan from Amazon. From a $$ standpoint (not a bitcoin standpoint) I should ROI in around 130 days assuming btc price remains stable.

Thank-you mdude77 for a very good and useful guide. Now my graphic cards can get a well deserved rest. They already paid for themselves, as well as my new little 3ghs rig.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: aigeezer on September 03, 2013, 11:38:59 PM

Good to know.  I was thinking I'll put 3.4.2 on another rig and move the erupters over there.  That way if it doesn't work, it won't take an hour reconfiguring the drivers.

M

Tag-team updates can save a lot of grief. I hadn't even noticed 3.4.2 was out until I saw your post though - thought I was up to the minute with 3.4.1.

I took a chance and switched my 3.4.1 'puter to 3.4.2 just now with no safety nets of any kind. No drama yet. Same bat file, except for the change in version number of course.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: bitcoiner49er on September 04, 2013, 01:58:52 PM
I added some erupters yesterday via a new DUB-7 hub daisy chained into another DUB-7. I was using 3.3.4, which was crashing every 24 hours. Anyways, when I ran cgminer it would detect all of them fine, but within 5-10 mins I would get a ZOMBIE erupter. I tried rebooting and changing the erupters around (to make sure it wasn't just a bad erupter). I even tried 3.1.1 - no luck.
I downloaded 3.4.2 and tried again. ZOMBIE!  >:( ??? So I unplugged it without shutting down cgminer and then hot plugged it another port. After a brief pause and windows notifying me that the drivers were installed, it was detected by cgminer and ran strong all day. Weird.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: aigeezer on September 04, 2013, 02:26:27 PM
I added some erupters yesterday via a new DUB-7 hub daisy chained into another DUB-7. I was using 3.3.4, which was crashing every 24 hours. Anyways, when I ran cgminer it would detect all of them fine, but within 5-10 mins I would get a ZOMBIE erupter. I tried rebooting and changing the erupters around (to make sure it wasn't just a bad erupter). I even tried 3.1.1 - no luck.
I downloaded 3.4.2 and tried again. ZOMBIE!  >:( ??? So I unplugged it without shutting down cgminer and then hot plugged it another port. After a brief pause and windows notifying me that the drivers were installed, it was detected by cgminer and ran strong all day. Weird.

I get occasional zombies on 3.4.2, actually on 3.4.x come to think of it, but never on 3.1.1. Sometimes I can hot-swap the zombie and it starts up fine. Other times I have to hot-swap the whole hub it is on (power off, disconnect USB, then reconnect). I see I have a zombie right now, in fact. It's random with respect to position on a hub, which erupter fails, and choice of hub itself as far as I can see.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on September 04, 2013, 02:37:26 PM
A zombie is simply a device that has stopped responding to libusb and thus I can no longer talk to it otherwise libusb will crash.
Normally, it should simply hotplug the device back again and push the zombie off the screen and replace it with the hotplugged device.
A common cause of this is the device overheating.
They have no temperature sensors so I can certainly not throttle the device when they get too hot ... all I can do is keep mining until it fails.
Yes I still do not understand why they don't have a temperature sensor ...
(I almost burnt my finger on one the other day trying to unplug it :P)


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: aigeezer on September 04, 2013, 02:58:04 PM
A zombie is simply a device that has stopped responding to libusb and thus I can no longer talk to it otherwise libusb will crash.
Normally, it should simply hotplug the device back again and push the zombie off the screen and replace it with the hotplugged device.
A common cause of this is the device overheating.
They have no temperature sensors so I can certainly not throttle the device when they get too hot ... all I can do is keep mining until it fails.
Yes I still do not understand why they don't have a temperature sensor ...
(I almost burnt my finger on one the other day trying to unplug it :P)

Thanks, kano. I forgot to mention that when I come across a zombie it is almost always cool to the touch. This could be because I just didn't notice it for a while and gave it time to cool off. My erupters are all under wall-plug fans, but sometimes they still feel uncomfortably warm while running - never hot enough to make me recoil though.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: JBT on September 04, 2013, 04:48:13 PM

It seems to be safe now to move up to 3.4.0 or 3.4.1, in which case the parameters become much simpler. I have one machine still running 7 erupters on 3.1.1 with the messy parameters. It never crashes. My machine running 3.4.0 for a week or so and 3.4.1 as of yesterday crashes cgminer about once a day, for reasons yet unknown.

One shortcut should handle several workers though, regardless of version.

For example, this bat file using 3.4.1 finds all 13 erupters mounted on two hubs and allows for a backup pool:

C:\cgminer\cgminer-3.4.1-windows\cgminer-nogpu.exe -o http://stratum.bitcoin.cz:3333 -u blah.blee -p somepassword -o http://stratum.btcguild.com:3333 -u blah_something -p whatever


yes but all 13 erupters will use the same worker, cg and bfminer works well but i want to assign each erupter its own worker. its easier to see which stick is doing what


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: 3dcgminer on September 04, 2013, 05:24:06 PM
Getting confused with the different cgminer versions and which drivers to install.

Right now I get nothing out of 3.11 and 3.42 with the zadig drivers, can someone please clarify which driver to use for 3.42?

Running Win7 64 bit with Anker 10-port hub, tested in both USB2 and USB3 ports. Bat file using only cgminer-nogpu and pool info.
"No deviced detected"

EDIT: From the FPGA readme (why not the ASIC readme?)
"You must also make sure you are using the latest libusb-1.0.dll supplied with cgminer (not the libusbx version)"
libusb-1.0.dll is not even included in 3.42, so I took it from 3.40. Still no miners in cgminer.  >:(

EDIT 2: Got them running, after unplugging and replugging them on different ports of the hub.
Running on cgminer 3.42 with no parameters other than the pool, zadig 2.0.1.160 drivers only.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on September 04, 2013, 05:35:43 PM
...
yes but all 13 erupters will use the same worker, cg and bfminer works well but i want to assign each erupter its own worker. its easier to see which stick is doing what
Run each one: ./cgminer --usb ICA:1 ... etc


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: JBT on September 04, 2013, 07:08:16 PM
...
yes but all 13 erupters will use the same worker, cg and bfminer works well but i want to assign each erupter its own worker. its easier to see which stick is doing what
Run each one: ./cgminer --usb ICA:1 ... etc
cgminer-nogpu -o http://pool -u user.1 -p password --usb ica:1 -u user.2 -p password --usb ica:2 -u user.3 -p password --usb ica:3

something like that?

one of my sticks just gone zombie mode will not work anywhere on the hub except on the pc..... weird

ps. for this usb i will need to uninstall the silicon drivers and install the usb drivers?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on September 05, 2013, 01:38:16 AM
...
yes but all 13 erupters will use the same worker, cg and bfminer works well but i want to assign each erupter its own worker. its easier to see which stick is doing what
Run each one: ./cgminer --usb ICA:1 ... etc
cgminer-nogpu -o http://pool -u user.1 -p password --usb ica:1 -u user.2 -p password --usb ica:2 -u user.3 -p password --usb ica:3

something like that?
...
No.

cgminer will assign all devices to the first active pool(/worker) in failover mode (the default)
or it will assign all devices to all pools(/workers) in balance or loadbalance mode

If you wish to handle each device independently, you need to run a cgminer for each device (and each will connect to all the pools individually)
Thus you would run
cgminer-nogpu -o http://pool -u user.1 -p password --usb ICA:1
cgminer-nogpu -o http://pool -u user.2 -p password --usb ICA:1
cgminer-nogpu -o http://pool -u user.3 -p password --usb ICA:1

and each cgminer would only use 1 ICA device (ICA is the driver for AMU,ICA,BLT,LLT,CMR)

of course you can change or add more to the --usb option if you also have other non ica devices ...
e.g. --usb :1 means grab whatever the first USB mining device is, it can find, and only one device

Quote
ps. for this usb i will need to uninstall the silicon drivers and install the usb drivers?
On windows, of course ... as it says to.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: JBT on September 05, 2013, 05:21:43 PM
these erupter sticks don't show temperature in bfg or cgminer do they?  i measured the temp and got like 62C plus
anyone know the max operating temperature?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: KyrosKrane on September 05, 2013, 06:41:55 PM
OK, I have a strange situation here, maybe y'all can help me make some sense of this.

I recently moved, but I didn't take my computer with me. When I got to my new place, I bought a new Core i7 4770K based PC with a Z87 chipset based motherboard, a 7970 graphics card, and all the other usual accoutrements.  Brand new hard disk.  Installed Windows 7 Ultimate, drivers for the motherboard and graphics, Microsoft Security Essentials, 7-Zip, and nothing else.  Ran Windows Update until it ran out of things to patch. Downloaded and unzipped Zadig and cgminer, but didn't run them yet. So far, all normal.

Next, I plugged a single Block Erupter directly into USB slot on the case.  Windows dutifully reported that the driver failed to load. I ran the Zadig tool and installed the WinUSB driver. Now the device appears properly in the Device Manager.  If I unplug it and replug it, Windows doesn't give any error messages.

Next, I ran cgminer. It asked for my pool info, which I entered.  It found my graphics card, but not the BE.  It didn't give any error message indicating USB problems or anything like that.

Confused, I saved the config file, exited, and ran cgminer-nogpu.  It reported no devices found at all.  Unplugging and replugging the BE did nothing.  Trying other slots, USB2, USB3, all elicited no response from cgminer.  Tried a hub with a BE in it, same thing -- no response from cgminer.

My USB ports work normally.  If I plug a USB thumb drive or keyboard into the same slot as the BE, it works without issue.  There's no yellow ! sign in Device manager.  There's no error message from cgminer about missing drivers, or anything like that.  It just ... doesn't see the block erupter.  Any ideas?

(Once we get to the point where cgminer sees the BE, I'll ask the follow up about why this PC says it runs out of USB resources after about ten devices...)

Edit: Couple more bits of info.  I've tried this with cgminer 3.4.1 and 3.4.2. I run cgminer with no command line options, just the config file.  I also tried editing the config file to delete everything except my pool. I did read through the various readme files, but nothing pertinent jumped out at me. 

I did try multiple different BEs, and all had the same result.  I also tried with multiple BEs plugged in at once.  No joy.  Unplugging and replugging while cgminer was running didn't do anything either.

The HDD was reformatted, so there's no weird software lurking around.  If you deem it necessary, I'd be happy to reformat the disk again. I have access to all current versions of Windows, if you want me to try something else.  Other than this glitch, the computer seems to work normally. When mining with the GPU, it seems to be perfectly fine and puts out somewhere north of 500Mh/s (I don't remember the exact number, but it seems in the ballpark for this card on stock settings).


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on September 05, 2013, 09:14:58 PM
./cgminer -n

If they don't show up then my guess would be a USB3 port that libusb doesn't know how to deal with.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on September 06, 2013, 01:19:09 AM
these erupter sticks don't show temperature in bfg or cgminer do they?  i measured the temp and got like 62C plus
anyone know the max operating temperature?

That's pretty hot.  They need active cooling, or their lifespan will decrease.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on September 06, 2013, 05:09:42 AM
these erupter sticks don't show temperature in bfg or cgminer do they?  i measured the temp and got like 62C plus
anyone know the max operating temperature?

That's pretty hot.  They need active cooling, or their lifespan will decrease.

M
No there is no temperature sensor ... I guess it was some sort of cost saving idea ...


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: KyrosKrane on September 06, 2013, 01:34:15 PM
./cgminer -n

If they don't show up then my guess would be a USB3 port that libusb doesn't know how to deal with.

Code:

C:\Users\Admin\Downloads\cgminer>cgminer -V
cgminer 3.4.2

C:\Users\Admin\Downloads\cgminer>rem no block erupters plugged in

C:\Users\Admin\Downloads\cgminer>cgminer -n
 [2013-09-06 17:26:03] CL Platform 0 vendor: Advanced Micro Devices, Inc.

 [2013-09-06 17:26:03] CL Platform 0 name: AMD Accelerated Parallel Processing

 [2013-09-06 17:26:03] CL Platform 0 version: OpenCL 1.2 AMD-APP (1124.2)

 [2013-09-06 17:26:03] Platform 0 devices: 1
 [2013-09-06 17:26:03]  0       Tahiti
 [2013-09-06 17:26:03] Failed to ADL_Adapter_ID_Get. Error -1

 [2013-09-06 17:26:03] Failed to ADL_Adapter_ID_Get. Error -1

 [2013-09-06 17:26:03] GPU 0 AMD Radeon HD 7900 Series hardware monitoring enabl
ed
 [2013-09-06 17:26:03] 1 GPU devices max detected
 [2013-09-06 17:26:03] USB all: found 4 devices - listing known devices

 [2013-09-06 17:26:03] No known USB devices

C:\Users\Admin\Downloads\cgminer>rem one block erupter plugged in

C:\Users\Admin\Downloads\cgminer>cgminer -n
 [2013-09-06 17:26:30] CL Platform 0 vendor: Advanced Micro Devices, Inc.

 [2013-09-06 17:26:30] CL Platform 0 name: AMD Accelerated Parallel Processing

 [2013-09-06 17:26:30] CL Platform 0 version: OpenCL 1.2 AMD-APP (1124.2)

 [2013-09-06 17:26:30] Platform 0 devices: 1
 [2013-09-06 17:26:30]  0       Tahiti
 [2013-09-06 17:26:31] Failed to ADL_Adapter_ID_Get. Error -1

 [2013-09-06 17:26:31] Failed to ADL_Adapter_ID_Get. Error -1

 [2013-09-06 17:26:31] GPU 0 AMD Radeon HD 7900 Series hardware monitoring enabl
ed
 [2013-09-06 17:26:31] 1 GPU devices max detected
 [2013-09-06 17:26:31] USB all: found 4 devices - listing known devices

 [2013-09-06 17:26:31] No known USB devices


I also ran cgminer with this command line, in case it provides any further useful info.  Here's the first few lines of the output.

cgminer-nogpu --debug --verbose 2>cgminer.debug.output.txt

Code:
 [2013-09-06 17:30:48] Started cgminer 3.4.2
 [2013-09-06 17:30:48] Loaded configuration file cgminer.conf
 [2013-09-06 17:30:48] USB scan devices: checking for ICA devices
 [2013-09-06 17:30:48] RES: thread starting
 [2013-09-06 17:30:48] ICA looking for ICA 067b:2303 but found 8086:8c26 instead
 [2013-09-06 17:30:48] ICA looking for AMU 10c4:ea60 but found 8086:8c26 instead
 [2013-09-06 17:30:48] ICA looking for BLT 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:30:48] ICA looking for LLT 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:8350 but found 8086:8c26 instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:30:48] ICA looking for ICA 067b:2303 but found 8086:8c2d instead
 [2013-09-06 17:30:48] ICA looking for AMU 10c4:ea60 but found 8086:8c2d instead
 [2013-09-06 17:30:48] ICA looking for BLT 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:30:48] ICA looking for LLT 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:8350 but found 8086:8c2d instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:30:48] ICA looking for ICA 067b:2303 but found 8087:8000 instead
 [2013-09-06 17:30:48] ICA looking for AMU 10c4:ea60 but found 8087:8000 instead
 [2013-09-06 17:30:48] ICA looking for BLT 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:30:48] ICA looking for LLT 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:8350 but found 8087:8000 instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:30:48] ICA looking for ICA 067b:2303 but found 8087:8008 instead
 [2013-09-06 17:30:48] ICA looking for AMU 10c4:ea60 but found 8087:8008 instead
 [2013-09-06 17:30:48] ICA looking for BLT 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:30:48] ICA looking for LLT 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:8350 but found 8087:8008 instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:6014 but found 8087:8008 instead
 [2013-09-06 17:30:48] USB scan devices: checking for BAS devices
 [2013-09-06 17:30:48] BAS looking for BAS 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:30:48] BAS looking for BAS 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:30:48] BAS looking for BAS 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:30:48] BAS looking for BAS 0403:6014 but found 8087:8008 instead
 [2013-09-06 17:30:48] USB scan devices: checking for BFL devices
 [2013-09-06 17:30:48] BFL looking for BFL 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:30:48] BFL looking for BFL 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:30:48] BFL looking for BFL 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:30:48] BFL looking for BFL 0403:6014 but found 8087:8008 instead
 [2013-09-06 17:30:48] USB scan devices: checking for MMQ devices
 [2013-09-06 17:30:49] MMQ looking for MMQ 1fc9:0003 but found 8086:8c26 instead
 [2013-09-06 17:30:49] MMQ looking for MMQ 1fc9:0003 but found 8086:8c2d instead
 [2013-09-06 17:30:49] MMQ looking for MMQ 1fc9:0003 but found 8087:8000 instead
 [2013-09-06 17:30:49] MMQ looking for MMQ 1fc9:0003 but found 8087:8008 instead
 [2013-09-06 17:30:49] Not a ZTEX device 8086:8c26
 [2013-09-06 17:30:49] Not a ZTEX device 8086:8c2d
 [2013-09-06 17:30:49] Not a ZTEX device 8087:8000
 [2013-09-06 17:30:49] Not a ZTEX device 8087:8008
 [2013-09-06 17:30:49] USB scan devices: checking for AVA devices
 [2013-09-06 17:30:49] AVA looking for BTB 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:30:49] AVA looking for AVA 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:30:49] AVA looking for BTB 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:30:49] AVA looking for AVA 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:30:49] AVA looking for BTB 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:30:49] AVA looking for AVA 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:30:49] AVA looking for BTB 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:30:49] AVA looking for AVA 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:30:49] No devices detected!
 [2013-09-06 17:30:49] Waiting for USB hotplug devices or press q to quit
 [2013-09-06 17:30:49] Probing for an alive pool
 [2013-09-06 17:30:49] Popping work to stage thread
 [2013-09-06 17:30:49] Testing pool http://stratum.bitcoin.cz:3333
 [2013-09-06 17:30:49] Probing for GBT support
 [2013-09-06 17:30:49] HTTP request failed: Empty reply from server
 [2013-09-06 17:30:49] Failed to connect in json_rpc_call
 [2013-09-06 17:30:49] No GBT coinbase + append support found, using getwork protocol
 [2013-09-06 17:30:50] HTTP request failed: Empty reply from server
 [2013-09-06 17:30:50] Failed to connect in json_rpc_call
 [2013-09-06 17:30:50] Pool 0 stratum session id: ae6812eb4cd7735a302a8a9dd95cf71f
 [2013-09-06 17:30:50] JSON-RPC decode failed: (unknown reason)
 [2013-09-06 17:30:50] Failed to resume stratum, trying afresh
 [2013-09-06 17:30:51] Pool 0 stratum session id: ae6812eb4cd7735a302a8a9dd95cf71f
 [2013-09-06 17:30:51] Pool 0 difficulty changed to 3
 [2013-09-06 17:30:51] Stratum authorisation success for pool 0
 [2013-09-06 17:30:51] Pool 0 http://stratum.bitcoin.cz:3333 alive
 [2013-09-06 17:30:51] API not running - API will not be available
 [2013-09-06 17:30:51] Generated stratum merkle 7513ff33ce55ff44b86f9219e298ab3f0c8777d9b8626cdcd69402476132c164
 [2013-09-06 17:30:51] Generated stratum header 00000002b509afe0ce26c772c7a2da2c08a7e3446d84468946f35fd600000029000000007513ff33ce55ff44b86f9219e298ab3f0c8777d9b8626cdcd69402476132c1645229d90f1931679c000000000000008000000000000000000000000000000000000000000000000000000000000000
 [2013-09-06 17:30:51] Work job_id 17b8 nonce2 0 ntime 5229d90f
 [2013-09-06 17:30:51] Generated target 0000000000000000000000000000000000000000000000000000555500000000
 [2013-09-06 17:30:51] Generated stratum work
 [2013-09-06 17:30:51] Pushing work from pool 0 to hash queue
 [2013-09-06 17:30:51] Network diff set to 86.9M
 [2013-09-06 17:30:51] New block: 002946f35fd66d84... diff 86.9M
 [2013-09-06 17:30:51] Generated stratum merkle 25c4fd56cf9622756dd231804542c10138ea7c82ee574e9b00506d41691bb593
 [2013-09-06 17:30:51] Generated stratum header 00000002b509afe0ce26c772c7a2da2c08a7e3446d84468946f35fd6000000290000000025c4fd56cf9622756dd231804542c10138ea7c82ee574e9b00506d41691bb5935229d90f1931679c000000000000008000000000000000000000000000000000000000000000000000000000000000
 [2013-09-06 17:30:51] Work job_id 17b8 nonce2 1 ntime 5229d90f
 [2013-09-06 17:30:51] Generated target 0000000000000000000000000000000000000000000000000000555500000000
 [2013-09-06 17:30:51] Generated stratum work
 [2013-09-06 17:30:51] Pushing work from pool 0 to hash queue
 [2013-09-06 17:30:56] USB scan devices: checking for ICA devices
 [2013-09-06 17:30:56] ICA looking for ICA 067b:2303 but found 8086:8c26 instead
 [2013-09-06 17:30:56] ICA looking for AMU 10c4:ea60 but found 8086:8c26 instead
 [2013-09-06 17:30:56] ICA looking for BLT 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:30:56] ICA looking for LLT 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:30:56] ICA looking for CMR 0403:8350 but found 8086:8c26 instead
 [2013-09-06 17:30:56] ICA looking for CMR 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:30:56] ICA looking for ICA 067b:2303 but found 8086:8c2d instead
 [2013-09-06 17:30:56] ICA looking for AMU 10c4:ea60 but found 8086:8c2d instead
 [2013-09-06 17:30:56] ICA looking for BLT 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:30:56] ICA looking for LLT 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:30:56] ICA looking for CMR 0403:8350 but found 8086:8c2d instead
 [2013-09-06 17:30:56] ICA looking for CMR 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:30:56] ICA looking for ICA 067b:2303 but found 8087:8000 instead
 [2013-09-06 17:30:56] ICA looking for AMU 10c4:ea60 but found 8087:8000 instead
 [2013-09-06 17:30:56] ICA looking for BLT 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:30:56] ICA looking for LLT 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:30:56] ICA looking for CMR 0403:8350 but found 8087:8000 instead
 [2013-09-06 17:30:56] ICA looking for CMR 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:30:56] ICA looking for ICA 067b:2303 but found 8087:8008 instead
 [2013-09-06 17:30:56] ICA looking for AMU 10c4:ea60 but found 8087:8008 instead
 [2013-09-06 17:30:56] ICA looking for BLT 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:30:56] ICA looking for LLT 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:30:56] ICA looking for CMR 0403:8350 but found 8087:8008 instead
 [2013-09-06 17:30:56] ICA looking for CMR 0403:6014 but found 8087:8008 instead
 [2013-09-06 17:30:56] USB scan devices: checking for BAS devices
 [2013-09-06 17:30:56] BAS looking for BAS 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:30:56] BAS looking for BAS 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:30:56] BAS looking for BAS 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:30:56] BAS looking for BAS 0403:6014 but found 8087:8008 instead
 [2013-09-06 17:30:56] USB scan devices: checking for BFL devices
 [2013-09-06 17:30:56] BFL looking for BFL 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:30:56] BFL looking for BFL 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:30:56] BFL looking for BFL 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:30:56] BFL looking for BFL 0403:6014 but found 8087:8008 instead
 [2013-09-06 17:30:56] USB scan devices: checking for MMQ devices
 [2013-09-06 17:30:57] MMQ looking for MMQ 1fc9:0003 but found 8086:8c26 instead
 [2013-09-06 17:30:57] MMQ looking for MMQ 1fc9:0003 but found 8086:8c2d instead
 [2013-09-06 17:30:57] MMQ looking for MMQ 1fc9:0003 but found 8087:8000 instead
 [2013-09-06 17:30:57] MMQ looking for MMQ 1fc9:0003 but found 8087:8008 instead
 [2013-09-06 17:30:57] USB scan devices: checking for AVA devices
 [2013-09-06 17:30:57] AVA looking for BTB 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:30:57] AVA looking for AVA 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:30:57] AVA looking for BTB 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:30:57] AVA looking for AVA 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:30:57] AVA looking for BTB 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:30:57] AVA looking for AVA 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:30:57] AVA looking for BTB 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:30:57] AVA looking for AVA 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:30:57] (5s):0.000 (avg):0.000h/s | A:0  R:0  HW:0  WU:0.0/m
 [2013-09-06 17:31:02] USB scan devices: checking for ICA devices
 [2013-09-06 17:31:02] ICA looking for ICA 067b:2303 but found 8086:8c26 instead
 [2013-09-06 17:31:02] ICA looking for AMU 10c4:ea60 but found 8086:8c26 instead
 [2013-09-06 17:31:02] ICA looking for BLT 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:31:02] ICA looking for LLT 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:31:02] ICA looking for CMR 0403:8350 but found 8086:8c26 instead
 [2013-09-06 17:31:02] ICA looking for CMR 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:31:02] ICA looking for ICA 067b:2303 but found 8086:8c2d instead
 [2013-09-06 17:31:02] ICA looking for AMU 10c4:ea60 but found 8086:8c2d instead
 [2013-09-06 17:31:02] ICA looking for BLT 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:31:02] ICA looking for LLT 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:31:02] ICA looking for CMR 0403:8350 but found 8086:8c2d instead
 [2013-09-06 17:31:02] ICA looking for CMR 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:31:02] ICA looking for ICA 067b:2303 but found 8087:8000 instead
 [2013-09-06 17:31:02] ICA looking for AMU 10c4:ea60 but found 8087:8000 instead
 [2013-09-06 17:31:02] ICA looking for BLT 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:31:02] ICA looking for LLT 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:31:02] ICA looking for CMR 0403:8350 but found 8087:8000 instead
 [2013-09-06 17:31:02] ICA looking for CMR 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:31:02] ICA looking for ICA 067b:2303 but found 8087:8008 instead
 [2013-09-06 17:31:02] ICA looking for AMU 10c4:ea60 but found 8087:8008 instead
 [2013-09-06 17:31:02] ICA looking for BLT 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:31:02] ICA looking for LLT 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:31:02] ICA looking for CMR 0403:8350 but found 8087:8008 instead
 [2013-09-06 17:31:02] ICA looking for CMR 0403:6014 but found 8087:8008 instead
 [2013-09-06 17:31:02] USB scan devices: checking for BAS devices
 [2013-09-06 17:31:02] BAS looking for BAS 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:31:02] BAS looking for BAS 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:31:02] BAS looking for BAS 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:31:02] BAS looking for BAS 0403:6014 but found 8087:8008 instead
 [2013-09-06 17:31:02] USB scan devices: checking for BFL devices
 [2013-09-06 17:31:03] BFL looking for BFL 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:31:03] BFL looking for BFL 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:31:03] BFL looking for BFL 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:31:03] BFL looking for BFL 0403:6014 but found 8087:8008 instead
 [2013-09-06 17:31:03] USB scan devices: checking for MMQ devices
 [2013-09-06 17:31:03] MMQ looking for MMQ 1fc9:0003 but found 8086:8c26 instead
 [2013-09-06 17:31:03] MMQ looking for MMQ 1fc9:0003 but found 8086:8c2d instead
 [2013-09-06 17:31:03] MMQ looking for MMQ 1fc9:0003 but found 8087:8000 instead
 [2013-09-06 17:31:03] MMQ looking for MMQ 1fc9:0003 but found 8087:8008 instead
 [2013-09-06 17:31:03] USB scan devices: checking for AVA devices
 [2013-09-06 17:31:03] (5s):0.000 (avg):0.000h/s | A:0  R:0  HW:0  WU:0.0/m
 [2013-09-06 17:31:03] AVA looking for BTB 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:31:03] AVA looking for AVA 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:31:03] AVA looking for BTB 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:31:03] AVA looking for AVA 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:31:03] AVA looking for BTB 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:31:03] AVA looking for AVA 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:31:03] AVA looking for BTB 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:31:03] AVA looking for AVA 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:31:08] USB scan devices: checking for ICA devices
 [2013-09-06 17:31:08] ICA looking for ICA 067b:2303 but found 8086:8c26 instead
 [2013-09-06 17:31:08] ICA looking for AMU 10c4:ea60 but found 8086:8c26 instead
 [2013-09-06 17:31:08] ICA looking for BLT 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:31:08] ICA looking for LLT 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:31:08] ICA looking for CMR 0403:8350 but found 8086:8c26 instead
 [2013-09-06 17:31:08] ICA looking for CMR 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:31:08] ICA looking for ICA 067b:2303 but found 8086:8c2d instead
 [2013-09-06 17:31:08] ICA looking for AMU 10c4:ea60 but found 8086:8c2d instead
 [2013-09-06 17:31:08] ICA looking for BLT 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:31:08] ICA looking for LLT 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:31:08] ICA looking for CMR 0403:8350 but found 8086:8c2d instead
 [2013-09-06 17:31:08] ICA looking for CMR 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:31:08] ICA looking for ICA 067b:2303 but found 8087:8000 instead
 [2013-09-06 17:31:08] ICA looking for AMU 10c4:ea60 but found 8087:8000 instead
 [2013-09-06 17:31:08] ICA looking for BLT 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:31:08] ICA looking for LLT 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:31:08] ICA looking for CMR 0403:8350 but found 8087:8000 instead
 [2013-09-06 17:31:08] ICA looking for CMR 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:31:08] ICA looking for ICA 067b:2303 but found 8087:8008 instead
 [2013-09-06 17:31:08] ICA looking for AMU 10c4:ea60 but found 8087:8008 instead
 [2013-09-06 17:31:08] ICA looking for BLT 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:31:08] ICA looking for LLT 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:31:08] ICA looking for CMR 0403:8350 but found 8087:8008 instead
 [2013-09-06 17:31:08] ICA looking for CMR 0403:6014 but found 8087:8008 instead
 [2013-09-06 17:31:08] USB scan devices: checking for BAS devices
 [2013-09-06 17:31:08] BAS looking for BAS 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:31:08] BAS looking for BAS 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:31:08] BAS looking for BAS 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:31:08] BAS looking for BAS 0403:6014 but found 8087:8008 instead
 [2013-09-06 17:31:08] USB scan devices: checking for BFL devices
 [2013-09-06 17:31:08] BFL looking for BFL 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:31:08] BFL looking for BFL 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:31:08] BFL looking for BFL 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:31:08] BFL looking for BFL 0403:6014 but found 8087:8008 instead
 [2013-09-06 17:31:08] USB scan devices: checking for MMQ devices
 [2013-09-06 17:31:09] MMQ looking for MMQ 1fc9:0003 but found 8086:8c26 instead
 [2013-09-06 17:31:09] MMQ looking for MMQ 1fc9:0003 but found 8086:8c2d instead
 [2013-09-06 17:31:09] MMQ looking for MMQ 1fc9:0003 but found 8087:8000 instead
 [2013-09-06 17:31:09] MMQ looking for MMQ 1fc9:0003 but found 8087:8008 instead
 [2013-09-06 17:31:09] USB scan devices: checking for AVA devices
 [2013-09-06 17:31:09] AVA looking for BTB 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:31:09] AVA looking for AVA 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:31:09] AVA looking for BTB 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:31:09] AVA looking for AVA 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:31:09] AVA looking for BTB 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:31:09] AVA looking for AVA 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:31:09] AVA looking for BTB 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:31:09] AVA looking for AVA 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:31:09] (5s):0.000 (avg):0.000h/s | A:0  R:0  HW:0  WU:0.0/m


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: techman05 on September 06, 2013, 09:06:08 PM
does cgminer not work well with vista. I'm obviously having problems entering the commands to get it to recognize my device and set the com.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: -ck on September 06, 2013, 09:42:29 PM
I also ran cgminer with this command line, in case it provides any further useful info.  Here's the first few lines of the output.

cgminer-nogpu --debug --verbose 2>cgminer.debug.output.txt

Code:
 [2013-09-06 17:30:48] Started cgminer 3.4.2
 [2013-09-06 17:30:48] Loaded configuration file cgminer.conf
 [2013-09-06 17:30:48] USB scan devices: checking for ICA devices
 [2013-09-06 17:30:48] RES: thread starting
 [2013-09-06 17:30:48] ICA looking for ICA 067b:2303 but found 8086:8c26 instead
 [2013-09-06 17:30:48] ICA looking for AMU 10c4:ea60 but found 8086:8c26 instead
 [2013-09-06 17:30:48] ICA looking for BLT 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:30:48] ICA looking for LLT 0403:6001 but found 8086:8c26 instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:8350 but found 8086:8c26 instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:6014 but found 8086:8c26 instead
 [2013-09-06 17:30:48] ICA looking for ICA 067b:2303 but found 8086:8c2d instead
 [2013-09-06 17:30:48] ICA looking for AMU 10c4:ea60 but found 8086:8c2d instead
 [2013-09-06 17:30:48] ICA looking for BLT 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:30:48] ICA looking for LLT 0403:6001 but found 8086:8c2d instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:8350 but found 8086:8c2d instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:6014 but found 8086:8c2d instead
 [2013-09-06 17:30:48] ICA looking for ICA 067b:2303 but found 8087:8000 instead
 [2013-09-06 17:30:48] ICA looking for AMU 10c4:ea60 but found 8087:8000 instead
 [2013-09-06 17:30:48] ICA looking for BLT 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:30:48] ICA looking for LLT 0403:6001 but found 8087:8000 instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:8350 but found 8087:8000 instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:6014 but found 8087:8000 instead
 [2013-09-06 17:30:48] ICA looking for ICA 067b:2303 but found 8087:8008 instead
 [2013-09-06 17:30:48] ICA looking for AMU 10c4:ea60 but found 8087:8008 instead
 [2013-09-06 17:30:48] ICA looking for BLT 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:30:48] ICA looking for LLT 0403:6001 but found 8087:8008 instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:8350 but found 8087:8008 instead
 [2013-09-06 17:30:48] ICA looking for CMR 0403:6014 but found 8087:8008 instead
Interesting, it's not showing up an AMU at all... nothing matches AMU 10c4:ea60


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: KyrosKrane on September 06, 2013, 10:34:50 PM
Interesting, it's not showing up an AMU at all... nothing matches AMU 10c4:ea60
I checked the BE device properties in Device Manager, and I did see those bytes (10c4:ea60) in the various device setting strings.  So Windows itself is identifying the device correctly and loading the right driver.

If it helps you debug this further, the motherboard I'm using is a Gigabyte GA-Z87X-UD4H.  Is there anything further I can do to help resolve this, or do we just have to wait for whoever is in charge of libusb development to add support for this motherboard/chipset/whatever the root cause is?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: norpick on September 06, 2013, 10:54:01 PM
all i keep getting is no devices detected. iv tried everything and iv got no where, this is actually starting to drive me insane! any advice would not go a miss right now.
iv tried different forms of .bat files from \\.\COM3 to \COM3 also tried both -s and -S and nothing seems to work, iv only been using bit minter and they work fine there but i would like to start trying other pools now,
my device manager show me all COM Ports that im using the block erupters with, im running windows 7 64bit too if that helps?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: -ck on September 06, 2013, 11:07:57 PM
all i keep getting is no devices detected. iv tried everything and iv got no where, this is actually starting to drive me insane! any advice would not go a miss right now.
iv tried different forms of .bat files from \\.\COM3 to \COM3 also tried both -s and -S and nothing seems to work, iv only been using bit minter and they work fine there but i would like to start trying other pools now,
my device manager show me all COM Ports that im using the block erupters with, im running windows 7 64bit too if that helps?

cgminer does NOT USE COM PORTS. Please read the included ASIC-README file.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: -ck on September 06, 2013, 11:08:41 PM
Interesting, it's not showing up an AMU at all... nothing matches AMU 10c4:ea60
I checked the BE device properties in Device Manager, and I did see those bytes (10c4:ea60) in the various device setting strings.  So Windows itself is identifying the device correctly and loading the right driver.

If it helps you debug this further, the motherboard I'm using is a Gigabyte GA-Z87X-UD4H.  Is there anything further I can do to help resolve this, or do we just have to wait for whoever is in charge of libusb development to add support for this motherboard/chipset/whatever the root cause is?
Hmm there are some usb3 ports that are apparently not working with libusb, perhaps you have some. Try different ports or a hub or something to see if that's it?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: norpick on September 06, 2013, 11:10:31 PM
all i keep getting is no devices detected. iv tried everything and iv got no where, this is actually starting to drive me insane! any advice would not go a miss right now.
iv tried different forms of .bat files from \\.\COM3 to \COM3 also tried both -s and -S and nothing seems to work, iv only been using bit minter and they work fine there but i would like to start trying other pools now,
my device manager show me all COM Ports that im using the block erupters with, im running windows 7 64bit too if that helps?

cgminer does NOT USE COM PORTS. Please read the included ASIC-README file.

will do thanks, im new to all this so still learning and understanding whats what....


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: norpick on September 06, 2013, 11:22:32 PM
all i keep getting is no devices detected. iv tried everything and iv got no where, this is actually starting to drive me insane! any advice would not go a miss right now.
iv tried different forms of .bat files from \\.\COM3 to \COM3 also tried both -s and -S and nothing seems to work, iv only been using bit minter and they work fine there but i would like to start trying other pools now,
my device manager show me all COM Ports that im using the block erupters with, im running windows 7 64bit too if that helps?

cgminer does NOT USE COM PORTS. Please read the included ASIC-README file.

will do thanks, im new to all this so still learning and understanding whats what....
everything listed in the ASIC-README iv already done  installing the drivers


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: KyrosKrane on September 07, 2013, 07:32:12 AM
Interesting, it's not showing up an AMU at all... nothing matches AMU 10c4:ea60
I checked the BE device properties in Device Manager, and I did see those bytes (10c4:ea60) in the various device setting strings.  So Windows itself is identifying the device correctly and loading the right driver.

If it helps you debug this further, the motherboard I'm using is a Gigabyte GA-Z87X-UD4H.  Is there anything further I can do to help resolve this, or do we just have to wait for whoever is in charge of libusb development to add support for this motherboard/chipset/whatever the root cause is?
Hmm there are some usb3 ports that are apparently not working with libusb, perhaps you have some. Try different ports or a hub or something to see if that's it?
Unfortunately, I've tried with both the USB 2 and USB 3 ports on my PC, as well as a USB 2 hub plugged into both ports. No joy :( I don't have a USB 3 hub to test with, but I doubt it matters at this point.

I'm shifting my efforts towards mining with a Raspberry Pi, but that has its own issues - the Pi doesn't seem to recognize all the Erupters, and the whole Pi seems to freeze up after about five minutes. Still trying to figure out why and get a reproducible crash before I ask for help on that. Still, if I can get all 30+ Erupters mining successfully off an RPi, that would be the ideal scenario.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: kano on September 07, 2013, 08:45:22 AM
... 2 AMUs solo mining on an RPi Raspbian using 1.7% CPU ...
Gotta do something with these worthless pieces of ...


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: JBT on September 08, 2013, 08:14:04 AM
... 2 AMUs solo mining on an RPi Raspbian using 1.7% CPU ...
Gotta do something with these worthless pieces of ...

was actually pondering getting a rasp and running the whole thing plus 10 sticks of batter/solar......meaning running cost will be free


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on September 08, 2013, 11:21:54 AM
I updated the first post to clarify version info, and to add info on how to use 3.4.2, plus a sample config file for those that are completely new.

I switched to 3.4.2 and it was about as seamless as it could get.  I had two machines configured identically, complete with UART and USB drivers.  One had all my erupters, the other had none.  So I removed the UART driver from the one without erupters, rebooted, put cgminer 3.4.2 in a new folder, made a new script to start cgminer, and plugged all my erupters in.  I did one hub at a time to make sure it worked, and it worked.  No more COM port madness. :)  I think I'm getting 335MH/s per device now, compared to 333, and I think my hardware errors are lower.  I checked to see what I had on the old machine, and I think I was running around 7%, but I may have had an error in my math.  I'm running about 1.2% with 3.4.2.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: JBT on September 14, 2013, 07:47:48 AM
using bfgminer -q is that only for the que  of how many bits of work to dl to do?

ed: also what is good q to set?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: daddyfatsax on September 27, 2013, 01:57:08 PM
I having an issue with cgminer 3.4.2 restarting every 24 hours. Running windows 7 with 20 erupters. I am using cgwatcher, so whenever the miners stop watcher will make sure it starts again. Is there something I am missing that is causing cgminer to reset? I have 3.3.1 running scrypt on my gpu rig, and it has been running non stop for over a month now.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on September 28, 2013, 12:35:40 AM
I having an issue with cgminer 3.4.2 restarting every 24 hours. Running windows 7 with 20 erupters. I am using cgwatcher, so whenever the miners stop watcher will make sure it starts again. Is there something I am missing that is causing cgminer to reset? I have 3.3.1 running scrypt on my gpu rig, and it has been running non stop for over a month now.

3.4.2/3 crashes on me after a period of time.  Anywhere from a few days to close to a week.  Haven't seen a pattern, other than it always crashes in winsock.  On win7, with scrypt, cgminer hangs after about 3 days, presumably because the lousy AMD driver resets.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: rivanj on September 29, 2013, 09:11:12 AM
Hi,

I've followed the instructions and read through the pages to try and solve the current issue I'm having, (uninstalled old drivers, used zadig, etc).

Currently in cg 3.4.2 (Win7 64bit) I'm getting AMU 0 - 7 displaying and hashing correctly (Using 13 USB erupters in total). The problem is I get repeating messages (that are pushing any display/setting option I try to look at) as follows:

"Icarus detect (1:3) failed to initialise (incorrect device?)
USB init, open device failed, err -12, you need to install a WinUSB driver for - AMU device 1:3" over and over again o_o;

I have them all display on my device manager, though 4 show as "Unknown device" whereas the others will have a different title in unison. I've hit a wall here since I can get them all working on bitminter, but I'd rather have them all running in cg.


o_o Derp. Nevermind. I had one plugged into a 3.0 USB port (Asrock extreme 4 mobo). Plugged it into 2.0 and everything is running as it should be *fingers crossed*

Thanks for the helpful (newbie friendly) thread >.<


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on September 29, 2013, 12:55:16 PM
Hi,

I've followed the instructions and read through the pages to try and solve the current issue I'm having, (uninstalled old drivers, used zadig, etc).

Currently in cg 3.4.2 (Win7 64bit) I'm getting AMU 0 - 7 displaying and hashing correctly (Using 13 USB erupters in total). The problem is I get repeating messages (that are pushing any display/setting option I try to look at) as follows:

"Icarus detect (1:3) failed to initialise (incorrect device?)
USB init, open device failed, err -12, you need to install a WinUSB driver for - AMU device 1:3" over and over again o_o;

I have them all display on my device manager, though 4 show as "Unknown device" whereas the others will have a different title in unison. I've hit a wall here since I can get them all working on bitminter, but I'd rather have them all running in cg.


o_o Derp. Nevermind. I had one plugged into a 3.0 USB port (Asrock extreme 4 mobo). Plugged it into 2.0 and everything is running as it should be *fingers crossed*

Thanks for the helpful (newbie friendly) thread >.<


I've found two systems now 3.4.3 won't find the miner on.  One is an older motherboard with USB 2.0 ports.  Another is a laptop with newer USB 3.0 ports.  Two other computers work just fine.  It seems the direct USB support is still a bit spotty.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: rivanj on October 01, 2013, 03:50:20 AM
I'm setting up a second mining rig, only two 2.0 ports on it, so will be trying to get the 3.0 ports working properly.
On second attempt with one usb erupter I managed to get it recognized, then after about 20 minutes it does the repeating errors again o_O


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: EfterlysT on October 11, 2013, 08:57:04 PM
I have only used bitminters own software to run my usb eruptors earlier without any problem. Now i want to put all my usb devices to mine in another slush pool with cgminer.

I dont get it to work at all. I am using Win 7 32bit version.

If i try the 3.1.1 version of cgminer it only tells me it dont find any devices.

If i try the 3.5.0 version of cgminer i get:
http://i18.photobucket.com/albums/b142/EfterlysT/Bitcoin/cgminer.jpg (http://s18.photobucket.com/user/EfterlysT/media/Bitcoin/cgminer.jpg.html)

Everything fires up without problems with bitminter client.

Does anyone know what to to to get it work with cgminer ? I have tried like all win7 guides i have found without luck. I guess the problem lies with the winusb driver ?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: rpg on October 26, 2013, 10:23:57 PM
I'm running 3.6.4 on win7 64 with about 45 sticks and I'm finding that sometimes when a stick goes zombie all the others go sick. Because of that I started running 4 instances with 12 sticks each as to not affect the hash rate that much. Has this been reported? Is zombie a real zobie and killing everyone :-) Now serious, could it be the thread manager going crazy?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on October 27, 2013, 05:39:55 AM
I'm running 3.6.4 on win7 64 with about 45 sticks and I'm finding that sometimes when a stick goes zombie all the others go sick. Because of that I started running 4 instances with 12 sticks each as to not affect the hash rate that much. Has this been reported? Is zombie a real zobie and killing everyone :-) Now serious, could it be the thread manager going crazy?

we're not sure why some machines get zombified and some don't.  I have one machine it works fine on with 36, another machine (much newer and more powerful) I get errors and zombies left and right.  if are one of the unlucky ones, try an earlier version until you get one that works.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: -ck on October 27, 2013, 05:59:56 AM
I'm running 3.6.4 on win7 64 with about 45 sticks and I'm finding that sometimes when a stick goes zombie all the others go sick. Because of that I started running 4 instances with 12 sticks each as to not affect the hash rate that much. Has this been reported? Is zombie a real zobie and killing everyone :-) Now serious, could it be the thread manager going crazy?

we're not sure why some machines get zombified and some don't.  I have one machine it works fine on with 36, another machine (much newer and more powerful) I get errors and zombies left and right.  if are one of the unlucky ones, try an earlier version until you get one that works.

M
Yah I've been busting a gut left right and centre trying to find a common reason and fix for all of them on all OSs. My most recent bugfix for this very problem was only uploaded 2 hours ago, along with en experimental .exe using the bugfix.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on October 27, 2013, 05:10:51 PM
I'm running 3.6.4 on win7 64 with about 45 sticks and I'm finding that sometimes when a stick goes zombie all the others go sick. Because of that I started running 4 instances with 12 sticks each as to not affect the hash rate that much. Has this been reported? Is zombie a real zobie and killing everyone :-) Now serious, could it be the thread manager going crazy?

we're not sure why some machines get zombified and some don't.  I have one machine it works fine on with 36, another machine (much newer and more powerful) I get errors and zombies left and right.  if are one of the unlucky ones, try an earlier version until you get one that works.

M
Yah I've been busting a gut left right and centre trying to find a common reason and fix for all of them on all OSs. My most recent bugfix for this very problem was only uploaded 2 hours ago, along with en experimental .exe using the bugfix.

I appreciate your efforts.  I'd help test if I had the problem.  The rig in the basement with these works fine with 3.6.4+.  The fans are too noisy to run them up here on the machine that regularly has the problems.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Illutian on October 31, 2013, 03:56:25 PM
Whelp,

3.6.6

And I'm staring 18 "CP2102 USB to UART Bridge Controller" 's in Windows 8.1's Device Manager.

And "No devices detected!" in CGminer.  ::)


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on October 31, 2013, 04:01:12 PM
Whelp,

3.6.6

And I'm staring 18 "CP2102 USB to UART Bridge Controller" 's in Windows 8.1's Device Manager.

And "No devices detected!" in CGminer.

There seems to be something wrong.  ::)

I get this when I have my erupters plugged into a blue USB 3.0 port.  have any 2.0 ports to plug them into?

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Illutian on October 31, 2013, 04:10:48 PM
Whelp,

3.6.6

And I'm staring 18 "CP2102 USB to UART Bridge Controller" 's in Windows 8.1's Device Manager.

And "No devices detected!" in CGminer.

There seems to be something wrong.  ::)

I get this when I have my erupters plugged into a blue USB 3.0 port.  have any 2.0 ports to plug them into?

M

They're USB 3 hubs plugged into a USB 2 port. Apparently I had to not only REBOOT. But I also had to unplug and re-plug the entire Hub assembly....why I would need to do that after rebooting is beyond me. Seeing as nothing else was done and I rebooted just for shits 'n giggles.

Now CGminer-nogpu sees them


...and promptly crashes after running them for 3secs.

WTF is wrong now.... >:(

EDIT:

Oh and unless someone can tell me how the hell to run 'cgminer.exe' with a no GPU flag I won't bother. It causes my Nvidia Drivers to crash.


EDIT #2:

But MultiMiner uses CGminer 3.6.6 just fine...


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on October 31, 2013, 09:33:31 PM
Whelp,

3.6.6

And I'm staring 18 "CP2102 USB to UART Bridge Controller" 's in Windows 8.1's Device Manager.

And "No devices detected!" in CGminer.

There seems to be something wrong.  ::)

I get this when I have my erupters plugged into a blue USB 3.0 port.  have any 2.0 ports to plug them into?

M

They're USB 3 hubs plugged into a USB 2 port. Apparently I had to not only REBOOT. But I also had to unplug and re-plug the entire Hub assembly....why I would need to do that after rebooting is beyond me. Seeing as nothing else was done and I rebooted just for shits 'n giggles.

Now CGminer-nogpu sees them


...and promptly crashes after running them for 3secs.

WTF is wrong now.... >:(

EDIT:

Oh and unless someone can tell me how the hell to run 'cgminer.exe' with a no GPU flag I won't bother. It causes my Nvidia Drivers to crash.


EDIT #2:

But MultiMiner uses CGminer 3.6.6 just fine...

BTW, I'm using cgminer-nogpu 3.6.6 on a win8.1x64 box with 36 erupters with no problems.  I don't know why it works for some people and not others.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: forzendiablo on November 12, 2013, 09:16:09 PM
working good.

which USB hub would u suggest?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: RBCastro on November 13, 2013, 09:09:32 PM
CGMINER 3.8.1

I don't know if it is right, but it is working for me.

I made this line of code:


--icarus-options 115200:1:1 --icarus-timing 3.0=100 -s 0002 -s PORT#


The PORT# you get going on:

CONTROL PANEL > DEVICE MANAGER > UNIVERSAL SERIAL BUS

There will be a list of all ASIC on the HUB (CP2102 USB to UART Bridge Controller), click PROPERTIES and get the port number: "Port_#0002.Hub_#0006"

If you have like 5 ASIC, it will be some like this:


--icarus-options 115200:1:1 --icarus-timing 3.0=100 -s 0002 -s 0003 -s 0004 -s 0005 -s 0006




I hope I have helped in some way, if the code isn't right, please reply :)


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: btceic on November 21, 2013, 11:25:12 AM
What is the correct way to reset cgminer to re-detect all attached AMU's when they go sick, dead or zombie?

Currently I have to unplug and re-plug in the power or usb hub to get them to be recognized again, every 6 hours or so.

Info:
Win 7 N Ultimate
39 USB Eruptors on Anker 9+1 powered hubs.
cgminer-nogpu 3.6.4

Should I switch to cgminer 3.8.x?


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: -ck on November 21, 2013, 11:26:47 AM
What is the correct way to reset cgminer to re-detect all attached AMU's when they go sick, dead or zombie?

Currently I have to unplug and re-plug in the power or usb hub to get them to be recognized again, every 6 hours or so.

Info:
Win 7 N Ultimate
39 USB Eruptors on Anker 9+1 powered hubs.
Use this binary till it's improved in the next version:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-undead.exe

EDIT: But ideally avoiding them failing in the first place is the correct solution.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: HellDiverUK on November 21, 2013, 11:27:00 AM
What is the correct way to reset cgminer to re-detect all attached AMU's when they go sick, dead or zombie?


Fix your USB hub power issues, rather than worrying about software.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: btceic on November 21, 2013, 12:18:39 PM
Thanks guys, I will give that a try.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Ragdollcatman on December 07, 2013, 10:31:57 AM
Hi can someone tell me what to do about mine.

I currently have 4 Bitfury Red Fury usb miners and 1 Bitfury Blue Fury + 9 block erupters.

I am using cgminer 3.8.2 or 3.8.3 (when I can get the program to work - it seems to hate USB hubs and constantly fails at connecting to the bitminter pool)

I keep finding that numerous erupters fail.

Now this is going to become a major problem because at the moment I waiting for another Blue Fury which from the look of it will end up being a Nano Fury while the 2 Nano Furies I ordered from someone else look like they'll be non-existent.

The thing is is that I'm going to be buying a 20 port hub, 20 erupters and 2 Jalapeno units from a friend of mine. He plans on moving up whereas this will be all I ever own.

I would like to get it all working on cgminer otherwise it means re-formatting my bitcoin rig so that I can go back to the silas labs driver.  CGminer only seems to work best with the bitfury sticks whereas BFGminer seems best with everything else.  I would like to be able to leave it mining and not find that multiple erupters have gone zombie on me.

I've tried making a bat file and I can't get them to work. I don't know what the heck is wrong with CGminer but it just sits there blinking that underscore at me.  It won't ask for the url, username or password.  If I run a batfile with those typed in it still doesn't do anything.

Starting to get really, really sick of it. There is no proper help and to be honest I feel that I should not have to manually enter things into a bat file when it is for something that should be coded into the program itself.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on December 07, 2013, 12:26:54 PM
Hi can someone tell me what to do about mine.

I currently have 4 Bitfury Red Fury usb miners and 1 Bitfury Blue Fury + 9 block erupters.

I am using cgminer 3.8.2 or 3.8.3 (when I can get the program to work - it seems to hate USB hubs and constantly fails at connecting to the bitminter pool)

I keep finding that numerous erupters fail.

Now this is going to become a major problem because at the moment I waiting for another Blue Fury which from the look of it will end up being a Nano Fury while the 2 Nano Furies I ordered from someone else look like they'll be non-existent.

The thing is is that I'm going to be buying a 20 port hub, 20 erupters and 2 Jalapeno units from a friend of mine. He plans on moving up whereas this will be all I ever own.

I would like to get it all working on cgminer otherwise it means re-formatting my bitcoin rig so that I can go back to the silas labs driver.  CGminer only seems to work best with the bitfury sticks whereas BFGminer seems best with everything else.  I would like to be able to leave it mining and not find that multiple erupters have gone zombie on me.

I've tried making a bat file and I can't get them to work. I don't know what the heck is wrong with CGminer but it just sits there blinking that underscore at me.  It won't ask for the url, username or password.  If I run a batfile with those typed in it still doesn't do anything.

Starting to get really, really sick of it. There is no proper help and to be honest I feel that I should not have to manually enter things into a bat file when it is for something that should be coded into the program itself.

I believe there are options to tell cgminer only to use certain devices.  Maybe you should run one instance of cgminer for the bitfury and bfgminer for everything else?  Or maybe an older version of cgminer for the erupters (3.1.1 was very stable, just needed the USB to UART driver as well) and the newest for bitfury?

Remember the software is free.  The authors help out of their own goodness.  Those that help are also doing it in the community spirit.

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Ragdollcatman on December 07, 2013, 06:11:28 PM
i don't get any options - I've tried pressing S for settings, it just goes blank for a moment then goes back to the list of devices. The only letter that does anything is the q to quit.

Well if anyone knows who the writers are and they are members here could someone point one of them to me so I can discuss how to make a working bat file because I seem to be the unluckiest person ever to bitcoin.

Most of the time the software doesn't even work. It just goes to the bit where it is supposed to ask for the url and doesn't do anything. 9 times out of 10 when it DOES actually ask for the details it fails to connect to the pool.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: mdude77 on December 07, 2013, 06:52:08 PM
i don't get any options - I've tried pressing S for settings, it just goes blank for a moment then goes back to the list of devices. The only letter that does anything is the q to quit.

Well if anyone knows who the writers are and they are members here could someone point one of them to me so I can discuss how to make a working bat file because I seem to be the unluckiest person ever to bitcoin.

Most of the time the software doesn't even work. It just goes to the bit where it is supposed to ask for the url and doesn't do anything. 9 times out of 10 when it DOES actually ask for the details it fails to connect to the pool.

Command line options.  Did you see my main post here?  It has details on how to make a configuration file.  You shouldn't have to type in a URL.

https://bitcointalk.org/index.php?topic=220450.0

M


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: Ragdollcatman on December 07, 2013, 07:23:50 PM
I tried making a bat file with the url etc but it just ignores it.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: svennand on January 06, 2014, 09:06:42 PM
Can anyone help me?, im having issues with getting this running
when i follow the first tutorial with cgminer 3.1.1 and setting

cgminer-nogpu.exe -o xxx-u xx -p x --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S \\.\COM79 -S \\.\COM80

It works like a charm, until i go beyond 9 block erupters (have 67 of em...), if i go beyond cgminer either crashes or i get error finding devices.

When i try to follow tutorial two with 3.4.2 (tried 3.4.2 and others up to 3.8.5) i install that other driver and everything seems fine in control panel,
Restart the machine, but i cant for the love of god get it to register any devices. just get no devices detected, waiting for usb hotplug

if i try to manually unplug/replug when cgminer is running i get:
err -12 you need to install a winusb driver for -amu device
icarus detected: failed to initialise <incorrect device?>

Which suggest that that zadig didnt work, but i checked and redid it several times. they do not show up as com but as
CP2102 USB to UART Bridge Controller.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: -ck on January 14, 2014, 11:21:05 AM
Unplug them all. Plug only one in and change the driver to winusb then remove it. Then reboot, start cgminer and plug them in one by one. Or install linux.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: svennand on January 14, 2014, 12:42:53 PM
Unplug them all. Plug only one in and change the driver to winusb then remove it. Then reboot, start cgminer and plug them in one by one. Or install linux.

i went with the last decision:P moved them over to my linux rig.


Title: Re: How to use ASICMiner Block Erupters with CGMiner on Windows 7
Post by: peteypete416 on July 12, 2014, 10:04:50 PM
is it normal to only be able to run 14 asic saphires on cgminer if I put in one more 15 then it just shuts off and goes blank?