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

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: movellan on June 22, 2013, 07:35:46 AM

Quote from: mdude77 on June 22, 2013, 06:15:05 AM

Quote from: movellan on June 21, 2013, 10:20:17 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

movellan

full member

Activity: 368

Merit: 100

Quote from: mdude77 on June 22, 2013, 06:15:05 AM

Quote from: movellan on June 21, 2013, 10:20:17 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?

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: movellan on June 21, 2013, 10:20:17 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

movellan

full member

Activity: 368

Merit: 100

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.

ks3rv3rg

newbie

Activity: 56

Merit: 0

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.

joae1975

hero member

Activity: 752

Merit: 500

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

movellan

full member

Activity: 368

Merit: 100

Quote from: ScaryHash on June 18, 2013, 11:50:11 AM

Quote from: movellan on June 18, 2013, 11:46:06 AM

Quote from: -ck on June 18, 2013, 09:15:36 AM

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.

movellan

full member

Activity: 368

Merit: 100

Quote from: joae1975 on June 18, 2013, 11:17:58 AM

Quote from: -ck on June 18, 2013, 09:15:36 AM

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

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

ScaryHash

hero member

Activity: 529

Merit: 501

Quote from: movellan on June 18, 2013, 11:46:06 AM

Quote from: -ck on June 18, 2013, 09:15:36 AM

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.

movellan

full member

Activity: 368

Merit: 100

Quote from: -ck on June 18, 2013, 09:15:36 AM

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.

joae1975

hero member

Activity: 752

Merit: 500

Quote from: -ck on June 18, 2013, 09:15:36 AM

3.2.2?

i got it working with 3.1.1 using cgminer-nogpu

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

3.2.2?

movellan

full member

Activity: 368

Merit: 100

Quote from: Naelr on June 13, 2013, 09:42:36 PM

Quote from: dangue on June 11, 2013, 05:22:57 PM

Quote from: mdude77 on June 10, 2013, 09:56:39 AM

Quote from: 8-bit on June 10, 2013, 09:23: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. Sad

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?

ScaryHash

hero member

Activity: 529

Merit: 501

Hey guys, thanks a bunch !!

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

Grin

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.

FiatKiller

sr. member

Activity: 378

Merit: 250

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.

Naelr

full member

Activity: 231

Merit: 100

Quote from: dangue on June 11, 2013, 05:22:57 PM

Quote from: mdude77 on June 10, 2013, 09:56:39 AM

Quote from: 8-bit on June 10, 2013, 09:23: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. Sad

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

Naelr

full member

Activity: 231

Merit: 100

Quote from: Adrian-x on June 10, 2013, 08:09:32 PM

Quote from: Naelr on June 10, 2013, 07:28:37 PM

Quote from: mdude77 on June 10, 2013, 01:01:12 PM

Quote from: 8-bit on June 10, 2013, 12: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

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.

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.

FiatKiller

sr. member

Activity: 378

Merit: 250

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!

agibby5

sr. member

Activity: 267

Merit: 250

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.

innovation

sr. member

Activity: 280

Merit: 250

oh. I know the use of \\.\. So many thanks to you.

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