Bitcoin Mining on Mac OS X – cgminer – bfgminer

Development Technobabble

Ter my previous two posts ter this series I introduced two easy-to-use bitcoin miners for OS X: BitMinter and GUIMiner. However, while thesis miners are relatively effortless to install and use, they do not suggest the best spectacle when it comes to hash rates. For that you’ll want to look at cgminer and bfgminer. Thesis are native C miners and, paired with the right kernels, their spectacle exceeds the other two miners by fairly a broad margin.

cgminer &, bfgminer

The bfgminer project is a fork of the cgminer project. Now, I have no dog ter this fight, but my understanding is that the teams aren’t on excellent terms. However, I have had good luck with both contraptions and have worked with both authors te order to fix a crash (cgminer, bfgminer) related to numerous GPU’s on OS X and have no complaints whatsoever. Both miners opoffering similar show te my practice.

Installation

To get began, you will need to install the Xcode. Xcode is a free download from the Apple App Store.

Next you’ll need the Xcode Directive Line Instruments. Launch Xcode and then click the Xcode>,Preferences menukaart voorwerp. Click the Downloads tabulator and then click Install next to Guideline Line Devices.

If the text next to Xcode Directive Line Implements says Installed, carry on to the next step.

Next you’ll need to install Homebrew. Homebrew is a package manager for OS X that provides a sane way of installing *nix instruments, libraries, and their dependencies. It is similar to MacPorts for OS X or apt for Linux. Installing Homebrew is super-easy. Open up Terminal.app and run the following directive (from the Homebrew homepage):

After you install Homebrew, make sure you run the following guideline (spil the installer should instruct you):

Make sure you address any errors or warnings before proceeding spil they may prevent the miners from installing.

Ter my previous postbode I indicated that it wasgoed necessary to compile cgminer and bfgminer from their source code te order to install them on OS X. While that wasgoed necessary at the time, after some reading and experimenting with Homebrew I wasgoed able to create packages (called formulas with Homebrew) for installing cgminer and bfgminer on OS X Ten.8. Once Homebrew is successfully installed, you can run the following directions to install cgminer and bfgminer:

brew tapkast nwoolls/xgminer

brew install cgminer

brew tapkast nwoolls/xgminer

brew install bfgminer

If you specify the –HEAD (two dashes) parameter for brew install then the latest source-code will be pulled for the miner from Github rather than using the latest official release.

You can visit the Github repository to view the package contents.

If you run into errors installing the above formulas you can attempt running brew install with the –debug –verbose parameters to find where things went wrong. I’d also recommend using brew doctor to diagnose any issues.

Usage

Both cgminer and bfgminer are command-line utilities. You can either run them without any directive line parameters and pack te the prompts for mining pool URL and credentials or you can use the following format to specify your pool:

cgminer -o http://pool.url:port -u username -p password

bfgminer -o http://pool.url:port -u password -p password

If you have numerous graphics cards you’ll want to use the –no-opencl-binaries parameter with bfgminer to avoid a crash on startup. This is not necessary with cgminer spil it detects OS X and applies the same workaround automatically.

Other notable instruction line parameters are -I (for power) and -k (for kernel). If you pass ter -I d then the miner will use less resources so you can use your PC (think D for Desktop). Passing ter -I 9 is a safe value for having the miner use spil much of your graphics resources spil possible to mine. Your PC will be much less responsive. Eventually, -k lets you specify a kernel. I find on OS X that using -k diablo gives the best vertoning. So, my command-line using cgminer with the BitMinter pool would look something like this:

cgminer -k diablo -o http://mint.bitminter.com:8332 -u username_workername -p password -I 9

And for bfgminer:

bfgminer -k diablo -o http://mint.bitminter.com:8332 -u username_workername -p password -I 9 –no-opencl-binaries

Refer to the projects on Github for total documentation of the available command-line parameters.

Spil you can see from the average te the upper-left of each miner’s output, with cgminer and bfgminer I average 460 Mh/s. Compare that to 400 Mh/s with GUIMiner and 370 Mh/s with BitMinter and you can see why thesis command-line miners are preferred overheen their GUI counterparts.

Conclusion

Thesis are arousing times for crypto currency, whether you’re a geek or a speculator or merely a bystander. And, while OS X is pulling up the rear when it comes to supported OS’s for bitcoin mining, hopefully I’ve demonstrated some viable options for getting your feet humid with mining on OS X. BitMinter is a superb option for getting embarked, spil it gives you both a bitcoin mining pool with low fees and ready-to-use mining software. GUIMiner is a nice option for improved spectacle and plasticity ter mining pool choice. And, if you’ve determined mining is your thing and you want the absolute best show out of your equipment, you can’t go wrong with cgminer or bfgminer.

UPDATE: Since my original postbode I’ve had some good help from Bitcoin community member and blogger Kerry on how to get binaries such spil cgminer and bfgminer packaged te a self-contained way. If you are interested te the shell scripts that make this possible you can check them out on Github here. I have submitted thesis scripts to the authors of both cgminer and bfgminer so, ter the future, wij may see official OS X binary distributions.

Ter the meantime, if you’d like to attempt thesis out instead of following the instructions above, you can download them from the Releases pagina here.

Related movie: Hashflare | SCRYPT VS SHA-256 CLOUD MINING


Leave a Reply

Your email address will not be published. Required fields are marked *

*