There should be a series of lights like a NIC card would have near that red light if you have a proper and active network connection via the RJ-45 port on the Raspberry Pi.  Sounds like you have either (1) a bad network cable, or (2) the Raspberry has a bad RJ-45 port.  Try a different cable and see how that works which is the simpler of the two trouble shooting wise.

StarMiner is currently imaged only for a Raspberry Pi.  We have a "StarMiner groupie" who plans on donating a set of CubieBoards (another ARM based system) for fulfill that request as well as to assist with long term support of that specific hardware.  At this time though, the BeagleBone line is not currently support.

As for supported hardware for the Raspberry Pi, you can find references to these on our SourceForge Discussion section here.

Happy and profitable mining to all!

You are quite welcome.  A cron job with starmine restart will work just as well.

As for your initial issue, perhaps doing some "fine tuning" of the configuration file for Gridseed ASIC units and considering other pools might be another option.  We have not received any similar reports of "random stops" with Gridseed ASIC units prior to yours at this time.

Happy and profitable mining to all!

You could make a cron job that runs every hour that would run the following code:
once you had the proper ASIC profile selected (which I presume you do ) from the webUI.

Happy and profitable mining to all!

From a quick review of Rock Miner's Github repository, it appears that Rock Miner ASIC units are using cgminer with a modified version of the Icarus driver/module.  The Icarus driver/module is more of a "generic FPGA" driver/module, thus it is not specific typically for one particular ASIC or FPGA unit.  This is what was initially released with Zeus Miner's ASIC unit (though we developed a "better driver/module" accordingly ) and also explains why some of the Zeus Miner ASIC units were not performing up to specification.  Without having some Rock Miner ASIC units "in hand", we (the "StarMiner crew") cannot say how their version of cgminer may or may not work of course.  This is just from reviewing the information on their Github repository and knowing the history of how others have used the Icarus driver/module in the past.

Happy and profitable mining to all!

03 July 2014 version release notes and change log:
Files for download from SourceForge can be found here.

• Modifications to the Gridseed configuration files removing the "per_chip_stats" as noted in StarMiner SourceForge ticket #7.
• Updated modules/drivers for both Gridseed and Zeus Miner ASIC units.
• With respects to the "newer" Zeus Miner "batch 2" ASIC units, the ability to use the provided serial number to have specific settings per individual ASIC unit if using USB mode via libusb (versus --scan-serial mode).
• With respects to the "newer" Zeus Miner "batch 2" ASIC units, the ability to ID the individual ASIC unit based off of the number of chips within each unit. These will have the Zeus Miner ASIC names by default instead of the rebranded names.

It is quite possible, save we do not have this particular ASIC "in hand" to do any development work or testing with it for long term support.  It would also be one of the first SHA-256 ASIC units requested to be supported under StarMiner as well.

I have reached out to Rock Miners directly, though if you wish to post a request in their forum thread as well, that would probably help some.

Out of curiosity and assuming you have a R-Box ASIC with Rock Miner's Raspberry Pi image, how it is?

Happy and profitable mining to all!

Good to hear and you are quite welcome.

For reference, lighttpd does break things down modular wise a bit, so the question is quite understandable.

Happy and profitable mining to all!

The files would be (depending on the version of StarMiner) under either /etc/apache2/ (versions prior to 15 June 2014 release) or /etc/lighttpd/ (versions including and after 15 June 2014 release).

Happy and profitable mining to all!

27 June 2014 version release notes and change log:[/b]
Files for download from SourceForge can be found here.

• Patch of the mining application by dmaxl that addresses "wall of rejects" with mining pools that have network latency issues.
• Fix of the Gridseed ASIC configuration files so that they appear when editing via the webUI.

You (as well as everyone else) are quite welcome.   Download the latest image (web link noted above), give it a test run (or permanently which is even better ) and feel free to inquire if you have any questions and/or issues.  Feel free to post your results as well (including screen shots) and feedback (positive preferred, constructive as well of course).  We have a collection of screen shots from the previous images of various mining set ups on our LitecoinTalk forum thread.

Happy and profitable mining to all!

25 June 2014 version release notes and change log:
Files for download from SourceForge can be found here.

• Improved Gridseed and Zeus Miner ASIC unit support via an improved mining application and related driver/modules.
• Updated configuration profiles for individual and multiple Gridseed, Scriptor, and Zeus Miner ASIC units to parallel with the updated and improved driver/modules.
• The webUI being HTTP by default, though HTTPS can be enabled if desired to address some latency issues.
• Updated all of the StarMiner scripts accordingly to work with the previously noted configuration profiles.
• Updated Raspberry Pi Linux kernel/firmware.

I figured I would "tempt some tummies" of our "StarMiner groupies" out here with a screen shot preview of our latest test round of StarMiner.  Here are two screen shots of StarMiner with Zeus Miner "Blizzard" ASIC units.  For reference, these are "stock" units without any physical modifications.


This is using one "Blizzard" ASIC unit for over a 24 hour period (~36 hours in this case).  Please do note that yes, the ASIC is mining right around 1.5Mh/s here.  



This is using two "Blizzard" ASIC units.  Do note, we are hashing at ~1.5Mh/s per Blizzard here as well.  I was hoping to have some more graph data for a full "24 hour" representation, however I think our "proof of concept" with improved mining application software illustrates quite well here.

Now while some folks will say, "there are hardware errors", keep in mind that with an ASIC unit, hardware errors are acceptable to some degree.  The reject rate is...well...quite minimum (if not extremely minimal!).  Thus, quality is being produced here mining wise.

This image should be available in the next day or so (minus the upload time to SourceForge) pending some additional testing of our StarMiner code and script, plus some "house keeping" items.

Happy and profitable mining to all!

Since this thread has been relatively quiet, I am suspecting most of the "StarMiner groupies" are enjoying StarMiner and are happily mining away there in the crypto coin verse.

So a minor update on the prior update.  We are doing a few more tests of the mining application code for performance improvements (does anyone want to take a guess at the hash rate a Zeus Miner "Blizzard" ASIC is properly showing now? ).  We also have some improvements so that multiple Zeus Miner ASIC units can be detected without the -S option we implemented to help everyone out here a bit.  That is just with the mining application as well.   However, we want to be thorough with the testing first before releasing the updated image to ensure "quality" that our "StarMiner groupies" have come to expect and enjoy.  So please be patient a bit more and we should have something ready this coming week.

For upgrading, we will be documenting a slightly better process on "HowTo" do so.  However, one will still need to manually edit the pool settings in the configuration files due to the changes in the mining application itself.  The easiest way is to "copy and paste" your pool settings into a "note pad" text editor, upgrade the image, test out StarMiner with startest for your particular ASIC unit or pick one of the current ASIC profiles (e.g., zm-blizzard for a Zeus Miner "Blizzard" ASIC), then "copy and paste" the pool settings back via either the webUI text editor (which is fixed in the upcoming release) or via stared on the command line.  Due to the enhancements to the mining application, copying the prior configuration files in full will not work here and in fact prevent the mining application from properly mining with the ASIC.

More to come of course.   Happy and profitable mining to all!

Good to hear!  If you want to share a screen shot after you run your StarMiner + Gridseed Blade units for a while, I am sure others would love to see the results.  Our LitecoinTalk forum thread actually has quite a few from the "StarMiner groupies" showing and sharing their successes as well.

Now a simple explanation about StarMiner and the initial configuration files and profiles being used.  These files are meant to be "basic" and "simple" so that one can run startest from the command line to verify StarMiner with your Gridseed or Zeus Miner ASIC or Scriptor FPGA "does work".  The configuration files with startest will work in full with the "basic model" of the ASIC hardware (e.g., a Gridseed "Mini" or a Zeus Miner "Blizzard"), but are not expected to be show "optimal" for the other ASIC nor run long term for efficient and effective mining performance.  So then, one needs to select the proper hardware profile from the webUI and adjust accordingly (e.g., "gs-blade" for your specific case) using stared on the command line or from the webUI editor page to have "optimal" performance for the most part (yes, occasionally some minor adjustments might be needed ).  By "basic" (with respect to Gridseed ASIC units) this is with a clock speed of 850MHz and a single unit.  One can adjust these by adding the parameters for the chip count, and even specific ASIC clock frequencies by the serial number if such is desired.  Do note, the "serial number" aspect is Gridseed units specific only as Zeus Miner did not include such an option with their ASIC hardware (i.e., all Zeus Miner ASIC units would have to use the same clock frequency "across the board" here).

Also to note, the "StarMiner crew" for the majority are located in the US Mountain Time zone (UTC/GMT-7).  Please keep this in mind when posting or sending messages since contrary to popular belief, most of us are not "glued to the computer 24 hours a day", and do have other obligations in life.  We do our best though to respond to postings and inquiries as quickly as possible though.

Congrats once again on getting StarMiner up and running on your Gridseed Blades!  

Happy and profitable mining to all!

You actually just caught me in front of the computer responding to messages.

With regards to the recent release, go into the SeedManager configuration (URL is http://<StarMiner IP address or hostname>/cgi-bin/sconfig.pl) and raise the "Hardware Error" level a bit.  This is causing some concerns, when in fact if you take a closer look, the Accept/Reject numbers are appropriate with Rejects being "low" (relatively speaking of course).  Unlike GPU rigs, ASIC units can produce hardware errors, but the share is still acceptable from the results.

Thanks for the positive remarks about your experience with StarMiner.

To answer your question, option (2) (download the latest image from our SourceForge site under Files and reimage your SD card) is the only choice currently.  We are working on a better upgrade methodology, but it is still "not up to par" to be released into the public unfortunately.

Also to note, our LitecoinTalk forum thread has several successful cases of "StarMiner groupies" using the Gridseed Blade ASIC units.   There are even a few screen shots as well, including one "groupie" who was able to successfully mix both Gridseed Blade units with Gridseed Mini units (it is recommended to NOT attempt this with Zeus Miner ASIC units at this time!).

Feel free to advise on any issues you may encounter, as well as share your experience in using StarMiner as well.  We actually encourage both, especially screen shots of StarMiner with your ASIC units "live" mining away.   We suggest using an image hosting service like Imgur (which is free) for the screen shots.

Happy and profitable mining to all!

Just some "eye candy" screen shots from our end.

This is x2 Gridseed Mini ASIC units on StarMiner via dmaxl on Github's cgminer fork. 



This is x2 Zeus Miner Blizzard ASIC units on StarMiner via the Zeus Miner "version" of cgminer.   



Folks using the prior release will note the addition of the actual ASIC units showing up just below the Pool section on the webUI.

15 June 2014 version release notes and change log:
Files for download from SourceForge can be found here.

• Scriptor 8x FPGA support.
• Created multiple configuration profiles for individual Gridseed, Scriptor, and Zeus Miner ASIC units including the following:

• Gridseed "Mini".
• Gridseed "Blade".
• Scriptor, "Scriptor 8x".
• Zeus Miner "Blizzard".
• Zeus Miner "Cyclone".
• Zeus Miner "Hurricane X2".
• Zeus Miner "Hurricane X3".
• Xeus Miner "Thunder X2".
• Zeus Miner "Thunder X3".

and also included profiles matching the Zeus Miner ASIC units rebranded by GAW Miners.  The defaults are made for using up to ten (10) ASIC units at once.  Depending on the ASIC brand, the end user will need to adjust accordingly to account for multiple ASIC units being controlled by StarMiner.

• The webUI is running on lighttpd which should have some improvement on the previous latency issues.  Thanks to sling00 on Github for this work here.
• The additional of a "if the mining application stops" script and related scheduled checking of such to restart a "dead miner".  Thanks to worldly on LitecoinTalk for this work here.
• The webUI will now show the Zeus Miner ASIC units on the "Overview" page (below the Pools, above the graph).
• Updated all of the StarMiner scripts accordingly to work with the previously noted configuration profiles.
• Updated Raspberry Pi Linux kernel/firmware.

Possible issues:

• Due to StarMiner being able to support Gridseed, Scriptor, and Zeus Miner ASICs, it is strongly advised <strong>NOT</strong> to attempt to use a single StarMiner Raspberry Pi unit to control a mix of both types of ASIC units.  This is due to the limitations of a Raspberry Pi being just an ARM CPU with 512MB of RAM running a single mining application and webUI with statistical data reporting.  Unfortunately and once again, this "little guy" (the Raspberry Pi that is) can only handle so much.

This post is in reference to a StarMiner SourceForge Ticket made recently.

There is publicly known an issue in general with Raspberry Pi model B units that have stamped on the board itself Made in China (versus the Made in the UK versions).  We (Linux ETC) have experienced this issue first hand as well.  If one were to Google such, you will find a list of various complaints and griefs about this.  The "short version" is that quite often, the Made in China Raspberry Pi units are poorly fabricated when compared to the Made in the UK versions.  This is why Raspberry Pi (the company and .org itself) decided to move a majority of their production to the Sony UK facility.  There are still "some" Raspberry Pi's made in China (allegedly for the "far east market"), and I am not saying that all Raspberry Pi units from China "are bad" here, nor all from the UK "are good" either.  It seems though the reason for the move (besides RaspberryPi.org is based in the UK ) is for better quality and overall control of the manufacturing process.

So when you first boot up StarMiner on a Raspberry Pi, and things start going wrong with your network, do not blame StarMiner on it right off please.  StarMiner is a bit more "process and resource" intensive that a majority of images and applications that can run on a Raspberry Pi, yes.  However, out of nearly 300 downloads since StarMiner's initial release on 20 April 2014, and this is the only reported instance of "gremlins in mix", I think I will trust the logic and stats that 1 out of ~300 that StarMiner is not the cause nor fault here.  Now potentially a faulty Raspberry Pi with a bad NIC (Network Interface Controller) in this particular case does seem to fit the bill as potentially the cause.