I haven't used Block Erupters before, but I have read that CGMiner hates them.
BFGMiner is the goto miner for Block Erupters (and I believe all ASIC devices)
If CGMiner "hates" anything it's USB 3.0 hubs. I have been using CGMiner 3.3.1 with 15 Block Erupters and it has been working great and has been very easy to setup. I use USB 2.0 hubs. Could you post an example of either your command line (redacted) or .conf file if you use those (I do with my gpu miners, but not sure what the BE equivalent would be - mine are still enroute). Thanks! "cgminer-nogpu --usb ICA:5 -o [pool stuff]" That tells CGMiner to grab 5 of my 15 Block Erupters. I run 3 instances with 5 per pool. Or you could just use "cgminer-nogpu -o [pool stuff]" and have it use all Block Erupters in one instance. Read the ASIC Readme to setup the WinUSB driver if your using Windoze. Sam |
|
|
|
|
DGM isn't the reason pools have gone under. PPS is the reason many if not most pools have gone under.
I like DGM it's easy to spell and everything.
|
|
|
|
|
I use CGMiner with direct USB and it uses 1 or 2% CPU. I run 4 instances. It will peak at 9 or 10% but immediately drop back down.
BFGMiner uses USB serial drivers which has more overhead so may run higher CPU utilization. But it should be very low too.
Bitcoin mining typically uses very little CPU.
Sam
|
|
|
|
Hey guys, for some reason it's failing to load all of my devices with the config below, any ideas?
C:\cgminer\cgminer-nogpu.exe -o stratum.btcguild.com:3333 -u [username] -p [pw] --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S all
(Yes, I removed the username/pw)
I also tried listing out all of the COM ports individually and cgminer fails and closes.
What version of CGMiner are you using? 3.1.1 Edit: BFGminer is working perfectly, bye bye cgminer. I was going to suggest reading the 3.1.1 readme as I "think" CGMiner does not have a "-S all" option. Glad that your mining though. Sam |
|
|
|
I haven't used Block Erupters before, but I have read that CGMiner hates them.
BFGMiner is the goto miner for Block Erupters (and I believe all ASIC devices)
If CGMiner "hates" anything it's USB 3.0 hubs. I have been using CGMiner 3.3.1 with 15 Block Erupters and it has been working great and has been very easy to setup. I use USB 2.0 hubs. |
|
|
|
My problem is I have 2 video cards, and a Jalapeno all running on the same system. 1 video card is giving me problems and I want to disable it and still use the other video card AND my Jalapeno (the cards are hooked up in a watercooling rig and I was trying to prevent ripping it completely apart in order to remove the bad card from the system altogether). All of the things I tried would either let me run just the Jalapeno, or just one the one video card, not both.
Yes I understand that. So to disable the bad GPU you need to know which device it is and then use the remove disable in conjunction with that device. In my suggested example "-d 0 --remove-disabled" That would completely remove device 0 from CGMiner's knowledge and would just mine your other devices. If your bad GPU is a different device then substitute the 0 with the correct number. Sam |
|
|
|
Hey guys, for some reason it's failing to load all of my devices with the config below, any ideas?
C:\cgminer\cgminer-nogpu.exe -o stratum.btcguild.com:3333 -u [username] -p [pw] --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S all
(Yes, I removed the username/pw)
I also tried listing out all of the COM ports individually and cgminer fails and closes.
What version of CGMiner are you using? |
|
|
|
Hey guys, need a little help myself this morning and my Google-fu isnt working well (lack of food probably isnt helping). I have a rig running 2 GPUs and a Jala. One of my GPUs is giving me fits for some reason today, so I want to shut it down and mine with just the one card and my Jala. Its a watercooled unit and I am in the middle of work so dont have time to just rip it apart before anyone just asks why dont I take the card out.
I am trying to shut down the one card and mine with just the other and Jala, I can use -d 1 to use the one card, or I can use -G to shut them down and mine with the Jala, but I cant get them both working with the combination of -d 1 and --usb. I think my problem is the --usb and the syntax, but for the life of me I cant seem to figure out what it is (I've tried --usb 0, --usb BAJ, --usb baj, --usb BAJ0, and --usb baj0).
Is there something I am obviously missing, or is it just not wanting to play nice with me today?
--remove-disabled Remove disabled devices entirely, as if they didn't exist --device|-d <arg> Select device to use, one value, range and/or comma separated (e.g. 0-2,4) default: all So it could look something like this -d 0 --remove-disabled Correct me if I am wrong, removing disabled will just not show the disabled item on my cgminer screen --remove-disabled will completely remove that GPU/device from CGMiner's knowledge. So preface it with -d 0, -d 1 or -d 2 or whatever device the bad GPU is. I thought that is what you wanted to do? If so that is how you do it. Sam |
|
|
|
Hey guys, need a little help myself this morning and my Google-fu isnt working well (lack of food probably isnt helping). I have a rig running 2 GPUs and a Jala. One of my GPUs is giving me fits for some reason today, so I want to shut it down and mine with just the one card and my Jala. Its a watercooled unit and I am in the middle of work so dont have time to just rip it apart before anyone just asks why dont I take the card out.
I am trying to shut down the one card and mine with just the other and Jala, I can use -d 1 to use the one card, or I can use -G to shut them down and mine with the Jala, but I cant get them both working with the combination of -d 1 and --usb. I think my problem is the --usb and the syntax, but for the life of me I cant seem to figure out what it is (I've tried --usb 0, --usb BAJ, --usb baj, --usb BAJ0, and --usb baj0).
Is there something I am obviously missing, or is it just not wanting to play nice with me today?
--remove-disabled Remove disabled devices entirely, as if they didn't exist --device|-d <arg> Select device to use, one value, range and/or comma separated (e.g. 0-2,4) default: all So it could look something like this -d 0 --remove-disabled |
|
|
|
|
I use CGMiner-nogpu.exe 3.3.1 with my block erupters and it works great for me. It doesn't require OpenCL.
I would think BFGMiner would have a command line option to disable GPU support so that you don't need OpenCL, but I don't know that for sure.
Sam
|
|
|
|
|
Small payouts aren't really good for you. You could end up paying a higher transaction fee then the amount of BTC you're trying to send.
My minimum payout is 1 BTC on each pool I use.
|
|
|
|
Maybe it's because you're one of the last 3 people still mining on Deepbit lol. Seriously though, I stuck with them for a couple years and when I switched to Slush's pool I started getting about 10% more BTC with the same speed at the same difficulty....
Once I hit next cash out i'm done with them. Was just waiting for someone like you to ask me why I'm still with them, when I have no idea myself. Thanks for the feedback It's not bad for a backup pool. But it will continue to dwindle in usefulness until it gets updated to support stratum and variable difficulty. And many people dislike the proportional payout as well. |
|
|
|
Terahash, not terrahash. Terra = earth, Tera = SI prefix based on teras = monster.
Hmmm, MonsterHash/s, not bad. I still like Fred though. |
|
|
|
You really need to make this README more dumber friendly...
Doesn't seem too difficult to me. Could be worded better I guess -----------------------ASIC Readme------------------------- WINDOWS: On windows, the direct USB support requires the installation of a WinUSB driver (NOT the ftdi_sio driver), and attach it to the Butterfly labs device. The easiest way to do this is to use the zadig utility which will install the drivers for you and then once you plug in your device you can choose the "list all devices" from the "option" menu and you should be able to see the device as something like: "BitFORCE SHA256 SC". Choose the install or replace driver option and select WinUSB. You can either google for zadig or download it from the cgminer directoy in the DOWNLOADS link above. ------------------------------------------------------------- Here is my interpretation of the above paragraph and the steps I took 1. Unplug all Erupters 2. Run Zadig - Install WinUSB (I may have rebooted, can't remember for sure) - I could not install WinUSB while Erupters were plugged in. 3. Plug in one Erupter, verify that it is set to WinUSB. If not set it to WinUSB. 4. Close Zadig, plug in the rest of the Erupters, run CGMiner. Done |
|
|
|
|
It's working OK for me at the moment.
If your having a problem try posting in Deepbits support thread. [Tycho] may see it sooner than in a new random thread.
|
|
|
|
If you were going to rename it, what would you call it? Would you use a person's name? Whose name would you use?
Fred |
|
|
|
It looks like you have the default 8 connections. Setup Port Forwarding so that you can get more connections. My client used to run with 60+ connections until I limited it to 20.
Also if this is the wallet that you have been doing your AMU transactions with you may have a problem with wallet fragmentation. If that is the case I would PM a Pool Op and see what they do about it.
Sam
I have forwarding on, but it never goes over 8 anyways Set your router to forward TCP 8332 traffic to the IP of the machine with your bitcoin client. Then set that machines firewall to accept unsolicited incoming TCP 8332 packets. Those two steps should get you more the 8 connections. It should work better. Don't know if it will solve your issue though. Sam is it 8333 or 8332 ? i see different info.. Doh! Yep TCP 8333 for the client. |
|
|
|
It looks like you have the default 8 connections. Setup Port Forwarding so that you can get more connections. My client used to run with 60+ connections until I limited it to 20.
Also if this is the wallet that you have been doing your AMU transactions with you may have a problem with wallet fragmentation. If that is the case I would PM a Pool Op and see what they do about it.
Sam
I have forwarding on, but it never goes over 8 anyways Set your router to forward TCP 8332 traffic to the IP of the machine with your bitcoin client. Then set that machines firewall to accept unsolicited incoming TCP 8332 packets. Those two steps should get you more the 8 connections. It should work better. Don't know if it will solve your issue though. Sam |
|
|
|
Hey everyone. I think I'm having some trouble with failsafe, and I can't seem to shake it!
LukeJr over at eligius said that the pool was working properly, so I assume this is on my side.
Yesterday, and last night, Eligius connection was interrupted. It then reassigned difficultly and sat connected instead of rolling over to my failsafe. This doesn't *seem* to be affecting my slush or BTCguild connections, but I have seen it happen when BTCguild is down.
If anyone could give me some insight or maybe some troubleshooting options for making failsafe work. I'd be insanely and infinitely
Well it's failover not failsafe, I believe. You use it by adding more than one pool to the command line. After the miner starts go to your pool list and verify that they are all alive. I would also switch to each one to verify that it actually works and that you entered everything correctly. Some pools fail in a way that the mining node keeps sending the miner work so the mining software can't detect the outage. I have no idea about Eligius though, so I don't know if that fits or not. Sam |
|
|
|
|
You can run one instance of CGMiner for your ASIC's and GPU's or split them as you described. Either way is fine.
When I got my Block Erupters I retired my two GPU's. I was amazed how much the noise level went down. After running them 2+ years straight I hadn't realized how much noise GPU's make since I was accustomed to it.
Sam
|
|
|
|
|
Show Posts
