Archive for the ‘General Info’ Category

raspberry-pi-controller

We just got our Raspberry Pi and we are about to start testing the few already available mining images for the device that help you get started in using it for a Gridseed ASIC mining controller. You can of course start with a normal distribution and compile the miner yourself and set things up to run with the Raspberry Pi, however this requires some extra knowledge and time and not anybody can do it. On the other hand you have readily available images that you just need to write on and SD card and run them on the Raspberry Pi and supposedly you just need to configure the pool settings and you will be up and running in no time. Could it be that easy, or you should expect to have some troubles, we are going to find out soon enough. For now we’ll list the Gridseed optimized images that we could find available to use on Raspberry Pi, so you might want to give them a try as well…

Scripta is a Litecoin mining distribution for Raspberry Pi that provides a web interface for easier controlling, configuring and monitoring your mining devices. Originally it does not support Gridseed devices, but by replacing the supplied cgminer with a one supporting Gridseed ASICs you can easily make it work with Gridseed devices as well. In fact we suspect that most of the other images available below are based on Scripta based on some screenshots we’ve seen even though we still haven’t started testing any of them.

MinerEU does provide a dedicated Raspberry Pi image for Gridseed usb miner to their customers only. The image is now freely available, so you can download it and try it out if you are interested. We are going to give it a try for sure.

Hash Master apparently does provide their Raspberry Pi image along with the device if you purchase the complete controller package from them. We could not find their Pi image available for download other then the complete package they offer as a Pi-based controller with SD card and preloaded image on it, so we are not going to be able to test this image, but it seems to be pretty much Scripta with some visual modifications and the proper cgminer for Gridseed.

Zoom Hash does not give out much information about their image or even screenshots, but has a short guide and instructions for installing the image along with a download link available for everyone. We are going to be trying their image for the Raspberry Pi.

Hashra also does provide an image with some instructions to setup and use the Raspberry Pi as a controller for Gridseed ASIC devices. They do not sell RPi separately, but include it with their 20 miners package as a controller for the ASIC devices. They call their software for RPi Hashra Controla and it has web-based interface available.

This is it for now, time for testing the images. If you know about another Raspberry Pi image for Gridseed ASIC miners please feel free to share information about it so that we can include it in the list and also test it along with the others.

pb-mining-new-website

Today the Bitcoin cloud mining service PB Mining has updated their website, something that they have previously announced. Earlier today there was a message about the update pointing to the new IP address of the website, though some of you might still see that message until the DNS cache is refreshed. The new website is not a complete makeover, but more like adding new features and improvements to the interface of the service. We are happy to see that some of the things that we did not like about it initially are now fixed, such as the ability to update your Bitcoin payment wallet address. There is now more clearly structured and detailed information about your cloud hashrate and when your cloud mining contract expires and so on. There could be a few more issues n the next days that need to be worked on, but hopefully things will be back to normal and the support of the service is working to bring everything back to normal after the update.

We’ve been testing the service for a month already and though we had some concerns when we first started, now we can say that most of them are gone. The service has been running stable and problem free and we were getting our mined coins each week on time. We are still not ready to invest a lot of coins in the service as we are still testing it, but we are gradually adding more hashrate pretty much each week or when the difficulty has increased. The reason or that is the decrease in price per GHS that the service has with each difficulty adjustment to the already most attractive price they have for cloud mining.

At the moment they have 78 THS worth of hashrate and the option to buy a contract at 0.0075 BTC per GHS currently says that it has all been sold out. This however can be a result of temporary disabling the option to purchase new hashrate until everything is operating normally after the move, the same can also be true about new registrations. If you are already using the service and are having some issues try contacting the support or post in the dedicated thread about the service on Bitcointalk linked below.

To the PB Mining cloud mining service dedicated topic at the Bitcointalk forum…

bfgminer-gridseed-actual-hashrate

It seems that many users are having trouble understanding what is the actual hashrate they get from their 5-chip Gridseed ASIC miners, the reason for that is partly related to how the Gridseeds are handles in different miner software and the difference in what is being reported. We are starting with the bfgminer 3.10.0 with Gridseed support running a single unit – see the screenshot above as the example that we are going to talk about. Note that the bfgminer has just been started and there are 11 accepted shares, 2 rejected and 0 hardware errors. The first number showing 361.2 KHS is the local hashrate of the miner (running at 850 MHz), this is calculated based on the frequency the miner is running at and is the hashrate that you should be getting in ideal conditions, however normally the conditions differ. The actual hashrate you are getting is the third number, the one we have marked in red, so that you can clearly see what we are talking about. That third number shows the actual hashrate based on the number of accepted shares and their difficulty, it takes into account the rejected shares and the hardware errors you get. The number is calculated as an average since you have started the miner software. The question that you are probably going to ask is why if in ideal conditions we should be getting 361.2 KHS here we have 426.7 KHS as actual hashrate. The reason for that lies in the fact that we just had 11 shares accepted and we had luck so that their difficulty was below the average, so the reported hashrate is averaged over a very short period of time and is not what we should be getting in the long run. You need to leave the miner run for a longer time in order to have a better representation of the actual hashrate you will be getting, but in the long run you are most likely going to get a result that is a bit lower than the optimal value of 361.2 KHS.

cgminer-gridseed-actual-hashrate

In the second example we are going to be looking at cgminer 3.7.2 modified to support Gridseed. In the example above we have a single miner overclocked to run at 950 MHz and the software miner has been running for a few hours already. Again the first number that shows 404.3 KHS is the theoretical hashrate in ideal conditions that is based on the operating frequency of the miner. The second number that we have marked with red is the actual hashrate that we are getting with this ASIC device running cgminer. The second number takes into account the time the miner is running, the number of accepted shares and their difficulty, the number of rejected shares and the hardware errors the device is getting. So instead of 404.3 KHS the actual hashrate we are getting is 401.5 KHS in this case and this is the result we are getting with the cgminer running for 4 hours.

gridseed-asic-miner-pool-hashrate

If we take a look at the hashrate reported by the pool for the Gridseed ASIC miner using the cgminer example above we can see that the pool reports 398.46 KHS and not 401.5 KHS. The number of submitted shares and rejected ones reported by the pool is also different. The reason for that is that the pool statistics has been reset about 8 hours before starting the miner and the statistics in cgminer is for about 4 hours only. The reported actual hashrate of cgminer is based on 4 hours of running, however the reported hashrate by the pool is based only on the shares submitted in the past 1 hour. Different mining pools base their average hashrate on the number of shares submitted in the last X minutes and that period can vary between 1 minute to 1 hour or even more. And as with the software miners not being able to report very adequate hashrate in just a minute or two, if the pool reports hashrate based on the shares submitted over a short period of time it might be reporting lower or higher values that are not close to the real one. Looking at the right number in bfgminer or cgminer should give you a pretty good idea on the actual hashrate you are getting, also pools that average hashrate over a longer period of time such as at least 5 or 10 minutes can be used to give you a good idea.

The first miner available with support for the Gridseed ASIC devices was a modified version of cpuminer that however does not report local or actual hashrate as that software miner does not keep statistics for the number of accepted and rejected shares, neither does take into account the hardware errors produced by the device. So it reports a hashrate of 0 all of the time, even though it is actually working, the only way to find what is the actual hashrate if using cpuminer is to look at the hashrate reported by the pool.


top