Pages:
Author

Topic: Help with asicminer usb setup (Read 1486 times)

legendary
Activity: 966
Merit: 1000
- - -Caveat Aleo- - -
September 02, 2013, 07:18:16 PM
#33
Did you try a different computer? Where are you located? Maybe someone could make a house call or do a remote link...
newbie
Activity: 56
Merit: 0
September 02, 2013, 07:11:16 PM
#32
Without the silabs drivers, I still get the same "no devices detected" error in cgminer.
newbie
Activity: 56
Merit: 0
September 02, 2013, 07:03:02 PM
#31
I tried bitminter, but I got a timeout error when trying to probe the port, and I do have the silabs drivers installed.
newbie
Activity: 26
Merit: 0
September 02, 2013, 05:13:09 PM
#30
You can download the Eobot software, it automatically will work with an unlimited number of the Asicminer USB...you can choose BTC/LTC, and it will mine either one for you using the USB.  Here's the link:

www.eobot.com/EobotWindows.zip
cp1
hero member
Activity: 616
Merit: 500
Stop using branwallets
September 02, 2013, 02:06:31 PM
#29
When I have only the zadig WinUSB drivers installed, the miner isn't assigned a COM port.

That's right, that's why you don't use the -S option.
full member
Activity: 231
Merit: 100
September 02, 2013, 01:42:11 PM
#28
have you tried Bitminter? I had some problems, but with Bitminter I've seen all my 10 block erupters and now I'm mining from several days!
newbie
Activity: 56
Merit: 0
September 02, 2013, 01:20:12 PM
#27
When I have only the zadig WinUSB drivers installed, the miner isn't assigned a COM port.
cp1
hero member
Activity: 616
Merit: 500
Stop using branwallets
September 02, 2013, 12:44:09 AM
#26
You shouldn't have both zadig and the other drivers installed.  Just use the zadig.  Are the devices showing up properly there?
newbie
Activity: 56
Merit: 0
September 01, 2013, 11:37:29 PM
#25
Yes, I'll try it on another computer once I get home.
legendary
Activity: 966
Merit: 1000
- - -Caveat Aleo- - -
September 01, 2013, 11:30:41 PM
#24
Do you have another PC or laptop you can try?  I was unable to run my erupters on my windows7 64bit desktop but had no problem with my windows 7 netbook.
newbie
Activity: 56
Merit: 0
September 01, 2013, 11:24:53 PM
#23
For CGMiner, I tried uninstalling the SI labs drivers, reinstalling the zadig drivers, and then reinstalling the SI labs drivers, but I still get the same errors.
hero member
Activity: 798
Merit: 1000
September 01, 2013, 10:43:38 PM
#22
Also, if you want to try CGMiner again, try uninstalling the serial drivers first (the ones that identify the erupter as a COM port) from SI labs before you reinstall Zadig drivers.  You shouldn't see CP210x bridge anymore.
hero member
Activity: 798
Merit: 1000
September 01, 2013, 10:38:49 PM
#21
If you're trying with the latest BFGMiner 3.2.0, then try using -S erupter:all.

Also the permissions issues you're having occur often if you're trying to run BFGMiner directly from a folder under the desktop or the desktop itself.  If that's the case, try putting it in a folder directly on C:\ instead like C:\Mining\bfgminer.exe
newbie
Activity: 56
Merit: 0
September 01, 2013, 10:36:59 PM
#20
Yeah, it is plugged into a USB 2.0 port
newbie
Activity: 33
Merit: 0
September 01, 2013, 10:25:15 PM
#19
sorry we aren't being of much help....  the only other thing that I can think of (which didn't happen to me but I read about in a few places) is that USB3 ports cause issues sometimes... possible to try on a USB2 port? 
newbie
Activity: 56
Merit: 0
September 01, 2013, 10:19:56 PM
#18
I tried it, it just says "All devices disabled, cannot mine!"
newbie
Activity: 33
Merit: 0
September 01, 2013, 10:03:03 PM
#17
have you tried running bfgminer without specifying the com ports?  I typically only have to use the -S in older versions of cgminer....bfgminer has been no problem with just the address, user:pass combo
newbie
Activity: 56
Merit: 0
September 01, 2013, 08:57:02 PM
#16
When running as administrator, I still got the same error.

newbie
Activity: 56
Merit: 0
September 01, 2013, 12:56:07 PM
#15
What ABN said,

Left click and highlight your batch>right click> Run as admin
newbie
Activity: 33
Merit: 0
September 01, 2013, 12:46:33 PM
#14
did you try running it in "administrator" mode?

I didn't need to resort to that, but I found numerous threads where that was advised.....
Pages:
Jump to: