How to use ASICMiner Block Erupters with CGMiner on Windows 7 - page 2.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: mdude77 on October 27, 2013, 12:39:55 AM

Quote from: rpg on October 26, 2013, 05: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?

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.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: rpg on October 26, 2013, 05: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?

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

rpg

hero member

Activity: 728

Merit: 500

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?

EfterlysT

full member

Activity: 425

Merit: 109

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:

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 ?

rivanj

newbie

Activity: 5

Merit: 0

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

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: rivanj on September 29, 2013, 04: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 >.<

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

rivanj

newbie

Activity: 5

Merit: 0

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 >.<

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: daddyfatsax on September 27, 2013, 08:57:08 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

daddyfatsax

hero member

Activity: 857

Merit: 1000

Anger is a gift.

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.

JBT

full member

Activity: 165

Merit: 100

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?

mdude77

legendary

Activity: 1540

Merit: 1001

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

JBT

full member

Activity: 165

Merit: 100

Quote from: kano on September 07, 2013, 03:45:22 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

kano

legendary

Activity: 4592

Merit: 1851

Linux since 1997 RedHat 4

... 2 AMUs solo mining on an RPi Raspbian using 1.7% CPU ...
Gotta do something with these worthless pieces of ...

KyrosKrane

sr. member

Activity: 295

Merit: 250

Quote from: -ck on September 06, 2013, 06:08:41 PM

Quote from: KyrosKrane on September 06, 2013, 05:34:50 PM

Quote from: -ck on September 06, 2013, 04:42:29 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?

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 Sad

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.

norpick

newbie

Activity: 32

Merit: 0

Quote from: norpick on September 06, 2013, 06:10:31 PM

Quote from: -ck on September 06, 2013, 06:07:57 PM

Quote from: norpick on September 06, 2013, 05: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?

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

norpick

newbie

Activity: 32

Merit: 0

Quote from: -ck on September 06, 2013, 06:07:57 PM

Quote from: norpick on September 06, 2013, 05: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?

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....

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: KyrosKrane on September 06, 2013, 05:34:50 PM

Quote from: -ck on September 06, 2013, 04:42:29 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?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: norpick on September 06, 2013, 05: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?

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

norpick

newbie

Activity: 32

Merit: 0

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?

KyrosKrane

sr. member

Activity: 295

Merit: 250

Quote from: -ck on September 06, 2013, 04:42:29 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?

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