PS - Also would like to know the correct syntax for assigning each USB Block Erupter to a separate worker.
Once you have the direct USB working you run two instances of CGMiner cgminer-nogpu.exe --usb ICA:1 -o mint.bitminter.com:8332 -u username_workername01 -p password and cgminer-nogpu.exe --usb ICA:1 -o mint.bitminter.com:8332 -u username_workername02 -p password This will run one Block Erupter in each instance to two different worker names. Don't know why you would want to run two workers on one pool. I run three instances with the same number of BE's for three different pools. That way I can compare performance between different pools easily. Also helps ameliorate variance. Also using port 8332 implies your using getwork protocol. I would strongly recommend that you use the stratum protocol. |
|
|
|
|
The -S and --icarus option's is ONLY for CGMiner 3.1.1.
The later versions use direct USB. So follow the instructions with the ASIC Readme included with the CGMiner download.
The problem with these web sites are that they are rarely up to date. The readme's with the software is always up to date.
|
|
|
|
The only thing now I have to find is a way to run cgminer from the taskbar like I've done for GUIMiner and how to control multiple devices when I get more bitcoin miners (one instruction book said to tell it by com ports but that was before WinUSB was the needed).
CGMiner will us all that are available by default. Also look at the Advanced USB options in the readme. |
|
|
|
|
The BFL Jalapeno was supposed to be a coffee warmer. They even sent me a coffee cup. But the top of the thing is the coolest part of it. It's not a very well designed coffee warmer.
|
|
|
|
Or you could use BFGMiner and the VCP drivers, which means you don't have to fool about with the pointless WinUSB stuff.
You only have to fool around with pointless serial drivers. And good luck if you want to run multiple instances of the miner and your serial ports get reassigned on the fly by Windoze. |
|
|
|
sometimes main pool is "not submitting work fast enough" but as the pool has not failed cgminer will not switch to backup pool?
That's not a pool failure. If you don't want that to happen then you'll need to have a pool that provides work fast enough as your primary pool. Failover only goes to the next pool when the primary actually fails for good and for a certain amount of time. |
|
|
|
you mine ltc ? if so did you put the --scrypt argument?
no im mining BTC with Slush pool and i made the .bat with the flags from the Wiki Why don't you try the flags from the Readme. If you still have trouble post your command line. Or maybe post in the CGMiner thread as well. Sam |
|
|
|
Received my GB 7 coupon devices yesterday.
Waiting patiently for my GB 4 notification.
Thanks Canary,
Sam
it was PMed to you you around 1 AM Got it and paid this morning. Just sent PM with signed message. Thanks, Sam |
|
|
|
|
Received my GB 7 coupon devices yesterday.
Waiting patiently for my GB 4 notification.
Thanks Canary,
Sam
|
|
|
|
Bitcoin-QT can't handle that much hashrate.
interesting. I never knew that. Nonsense, Qt can handle anything you throw at it. To say otherwise is to doubt Satoshi, and I will not have it. /Troll People that have solo mined with high hash rate ASIC's have setup their own pool software to do it. The Bitcoin-QT client has no Stratum protocol nor variable difficulty. Edit: All I am trying to say is that solo mining 23,506.34 GH/s is no trivial task. He was being sarcastic  Ah, sarcasm, a difficult concept to master. Thanks, Sam |
|
|
|
Bitcoin-QT can't handle that much hashrate.
interesting. I never knew that. Nonsense, Qt can handle anything you throw at it. To say otherwise is to doubt Satoshi, and I will not have it. /Troll People that have solo mined with high hash rate ASIC's have setup their own pool software to do it. The Bitcoin-QT client has no Stratum protocol nor variable difficulty. Edit: All I am trying to say is that solo mining 23,506.34 GH/s is no trivial task. |
|
|
|
I tried cgminer 3.4.1, but it says "No devices detected! Waiting for USB hotplug devices"
Follow the instructions in the ASIC Readme. |
|
|
|
i suppose that i could run one regular instance and one no gpu instance.
Yep, or use -G to disable your GPU with regular cgminer.exe. |
|
|
|
i have notice over the past couple of days the pool has started to level off as far as in speed.
Also its kinda funny over the top 3 users how big of a jump it is to first place.
261043 23,506.34 GH/s
256259 5,476.64 GH/s
253209 5,413.26 GH/s
us holiday weekend. no shipping. wait til this week edit: who the F#$% is running 23 Thash on a pool? split it off and mine on your own If it's an individual, it's easier than running your own pool software to just solo mine. Bitcoin-QT can't handle that much hashrate. |
|
|
|
Using the later CGMiner's with direct USB makes it really easy to run multiple instances with however many AMU's you want in each instance.
I use the command line --usb ICA:5 in each instance and have 5 devices pointed at multiple pools. Makes it really easy to assess pool performance.
Sam
really? it works like that? what if there is one gpu, will they fight over it? i was wondering what i was going to do when there were too many AMUs to fit in the bigest window i can make. Yep, just like that. I retired my GPU's so I use the cgminer-nogpu.exe. So if you want to run one instance of cgmner.exe for your GPU's only use --usb ICA:0 and it won't use any AMU's. Then run a separate instance with cgminer-nogpu.exe for all your AMU's, or any number of them you wish. It's covered in the readme under "Advanced USB options:". Sam |
|
|
|
|
Using the later CGMiner's with direct USB makes it really easy to run multiple instances with however many AMU's you want in each instance.
I use the command line --usb ICA:5 in each instance and have 5 devices pointed at multiple pools. Makes it really easy to assess pool performance.
Sam
|
|
|
|
How can this pool be only at 3700 GH/s and find 17% of all blocks ?!?!
What is the real Hashrate of this pool ?
You need to stop relying on blockchain.info for identifying blocks. They have -never- had Deepbit's blocks correctly identified since the day they made that pie chart. At least it's not the same person asking the same question on the same page. Still doesn't say much. |
|
|
|
How can this pool be only at 3700 GH/s and find 17% of all blocks ?!?!
What is the real Hashrate of this pool ?
This pool is 1552 Gh/s. |
|
|
|
cgminer 3.4.0
Update to 3.4.1 |
|
|
|
|
Show Posts
