There wasgoed previously a bug that would prevent some USB devices being listed ter /dev .

Despite a loterijlot of people claiming that mining cryptocurrency is dead and no longer profitable, it is still a joy thing to participate with and so I picked up a Zeusminer Blizzard (pictured below) on eBay to use with my Raspberry Pi to mine some Dogecoin.

If you’ve made it to this guide, I’m going to assume you’re relatively familiar with mining and what devices such spil the Zeusminer Blizzard are for and are simply wanting to get it working, so I’ll skip overheen that introduction and get straight to how to set up this miner using a Raspberry Pi.

Setting up the prerequisites

The very first thing you’ll need to do is install Raspbian on to your Raspberry Pi. If you have not done this before head overheen to http://www.raspberrypi.org/documentation/installation/installing-images/ for information on how to do this. I very recommend using NOOBS to do this, it will make your life a lotsbestemming lighter!

Once Raspbian is setup, boot into the directive line and ass-plug a keyboard and your miner into the Pi and begin by very first ensuring that your package list is up to date and that you have the latest versions of the installed packages with this directive:

Once the update and upgrade is finished wij need to ensure that wij have the latest kernel and firmware updates. Why you ask? There wasgoed previously a bug that would prevent some USB devices being listed ter /dev . Ter the setting of this guide, it may prevent our miner showcasing up spil /dev/ttyUSB0 and thus result te bfgminer not being able to find the device.

To perform the updates, come in the following directive:

Now restart your Raspberry Pi using the following guideline to ensure the latest updates are ter use:

Next, wij’ll need to install a number of packages to permit us to clone the bfgminer source code, configure and compile it. Kwestie the following guideline to install the required dependencies:

Setting up bfgminer

Now wij’re ready to grab the source code! I’m presently running a fork by Darkwinde that I know to be working with the Zeusminer Blizzards. If you want to use a more latest fork I cannot assure compatibility or that the launch parameters will be the same.

To clone the source code to your huis directory, run this guideline:

Next up wij need to build bfgminer, which can take fairly some time, so most likely best to grab a coffee or something to eat whilst you wait. Commence by coming in the bfgminer directory that wasgoed just created by the cloning process and run autogen.sh:

Next, ensure the configuration script is executable and run it.

Significant: the CFLAGS value contains the capital letterteken O, not the number zero.

Now run the make guideline:

And now install:

And finish up with:

Setting up a bfgminer configuration and executing

Wij’re almost there now! If you toevluchthaven’t already, cork te your miner and ensure it is being recognised by running:

The output from this should look something akin to the below:

If you can see the device I have spil device 004 then wij’re good to go. If not, attempt another USB cable or power supply to the miner to ensure the connection is OK and that sufficient power is being provided.

Now, run bfgminer using the following instruction, substituting the parts te curly braces with the suitable information:

The –zeus-cc parameter specifies the number of chips that are available te our miner, te the case of the blizzard this is 6, if you’re using a different prototype you’ll need to ensure you come in the keurig number.

And that’s it, you should now be successfully mining!

If bfgminer fails to find your device, run the following instruction to find possible devices:

If you have more entries, attempt substituting ttyUSB0 with the suitable number. If this comes back no results then it means Raspbian is failing to pickup your device, which is why wij installed the latest kernel and firmware updates earlier. If you skipped that step and are having this problem please be sure to go back and do it.

Optional steps

Below are a few toegevoegd things you may be interested te doing, but are not required ter order to run bfgminer.

Running on boot

If you want to run bfgminer when your Raspberry Pi boots up ter case of a power cut or any other event that would cause it to reboot, very first install screen:

This program, if you’re not familiar with it, will permit us to run bfgminer on a separate screen and detach it and reattach it spil wij please.

Next, wij’re going to use crontab to setup our bootup instruction, to do this run:

Make sure you do not sudo this directive, spil if you do you’ll be editing the tasks to be run by root, not pi. Now, add the following to the bottom of the opstopping:

Now when your Raspberry Pi reboots, bfgminer will be launched ter a screen that you can reattach to at any time by running:

To detach from that screen again, simply press CTRL + A + D.

Running Numerous Zeusminers

If you want to run numerous Zeusminers, simply substitute -S zeus:/dev/ttyUSB0 with -S zeus:all and bfgminer will search for all available Zeusminers for you. This is also a possible solution if you’re fighting to identify the device to pass ter.

Creating a configuration verkeersopstopping

If you are intending to run bfgminer by hand rather than on boot te the background, it may be useful to create a configuration verkeersopstopping rather than issuing the utter instruction each time. To do this, press the S key when on the main bfgminer screen pictured below.

Now, you’ll be on the settings screen, spil vanaf the screenshot below.

Press the W key on your keyboard and inject the path where you wish to save your configuration verkeersopstopping to.

Now when you want to launch bfgminer using thesis settings you can do so by running:

Sharing the love

If this guide wasgoed of use to you and you want to share some of the love, you can send mij some dogecoin to DEk6N8dcTBJrikDoxhgpNh6ZdmtFdEPeuG 🙂

Related movie: hướng dẩn kiếm tiền với vòi bitcoin Cointellect


Leave a Reply

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