Pages:
Author

Topic: How to use ASICMiner Block Erupters with CGMiner on Windows 7 - page 5. (Read 87358 times)

legendary
Activity: 1540
Merit: 1001
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
newbie
Activity: 59
Merit: 0
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...
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
... use 3.3.2 ...
hero member
Activity: 724
Merit: 500
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!
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
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.
newbie
Activity: 13
Merit: 0
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
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
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
newbie
Activity: 13
Merit: 0
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.
legendary
Activity: 1652
Merit: 1067
Christian Antkow
Next release will have the fixed libusb in it (it seems a lot of OS have a bad libusb)
https://bitcointalksearch.org/topic/m.2870499
Shouldn't be too far away ...

 Kick-ass ! Looking forward to it.

 Cheers.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
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  Undecided
Next release will have the fixed libusb in it (it seems a lot of OS have a bad libusb)
https://bitcointalksearch.org/topic/m.2870499
Shouldn't be too far away ...
legendary
Activity: 1652
Merit: 1067
Christian Antkow
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  Undecided
newbie
Activity: 23
Merit: 0
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
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
With 3.1.1 you don't use Zadig for AMUs
newbie
Activity: 23
Merit: 0
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?
sr. member
Activity: 457
Merit: 250
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.  Grin
hero member
Activity: 774
Merit: 500
Lazy Lurker Reads Alot
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  Huh :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.


 
newbie
Activity: 17
Merit: 0
Followed instructions to the T - using 3.1.1 - perfect!
legendary
Activity: 1450
Merit: 1013
Cryptanalyst castrated by his government, 1952
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.


newbie
Activity: 36
Merit: 0
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!

legendary
Activity: 1540
Merit: 1001
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
Pages:
Jump to: