Nevermind. I managed to hack Scripta to handle the Kh/s output from the girnyau variant of cgminer. I also added some changes while I was there, like displaying the individual miner's hash rate in Kh/s when appropriate.

If anyone wants my changes, let me know. But be warned that I don't know much about PHP, so there might be more elegant ways to implement these fixes.

Thanks for this awesome mod Girhes!

But I'm running into a GUI issue with Scripta. It appears that the API output of this version of cgminer is not something that Scripta knows how to parse. What I see for the hash rate is:

NaN Th/s

Maybe there's an option that I can use that will provide the same status JSON text to Scripta? Or maybe someone has a Scripta mod that handles the alternative output?

Thanks in advance for any suggestions.

Yup. Same here. I can get to the main web site, but it times out when trying to get to my user stats.

Maybe the user statistics side of the site is running on a different server.

My reported CloudFlare site is San Jose.

According to the cgminer API and Scripta, it is submitting shares. When I first noticed that the red LED was off this weekend, it appeared that that unit's utility numbers were down. But since it was working to some degree, I just left it running.

I just checked it again and it's performing roughly the same as all the other units.

It surprised me too that it would do *anything* without 12 volt power, but it appears to be working. Maybe it is getting 12 volts, but the LED isn't working. I know that there's nothing wrong with the 12 volt power cable because I checked it with a meter.

Anyway, after the zombie incidents yesterday and this morning, I managed to find an old, unused powered USB 2 hub. I moved the affected unit to that hub. Haven't seen any zombies since. Of course it hasn't been long enough to be definitive, so I'm keeping an eye on things.

I'm seeing the same problem. I was just about to post, but you beat me to it.

I checked my local logs and it looks like my miners are still in communication with the server, so maybe just the web server is down.

Thanks for getting back to me. That's a good explanation. I don't have a spare hub at the moment, unfortunately.

I guess what I can do for now is look at the log for disconnect/reconnect events. That would at least confirm what's happening.

Too bad that cgminer and/or Scripta doesn't do a better job of reporting these issues. But as long as it's not trying to give work to zombies, I agree that's it's harmless.

Note that one of my GS units never shows the red LED on. Only the green LED is on. Searching indicates that that means this unit is not receiving 12 volt power.

If this one unit is really not receiving 12 volt power, then it must be powered by the USB bus. The USB hub is a powered Orico P10 U2. But under the hood these Orico's are actually have two hubs with different power characteristics. Perhaps the additional power draw of the bad GS unit is crapping out the sub-hub in the Orico.

I can probably experiment with moving the bad unit's USB cable to the other internal hub in the hopes that it will have less of an impact. Of course the real solution is to replace the unit. I'm working on getting an RMA.

LOL! I wish I knew that "glod" was a choice!

When I got mine, I asked for blue. They nicely told me that they only had black.

When I bought some more I asked for black, for consistency. They nicely told me that they only had blue.

So now I'm black and blue  

Actually it's nice to get different colors for different orders. Makes them easier to tell apart in case there are problems.

I'm on a Raspberry Pi running 10 GS units with the dtbartle version of cgminer that I built from sources. It's been running for about a week.

Today I noticed that Scripta was reporting that I have 16 devices when I only have 10. Further, it's telling me that I have hash power that is impossible.

When I go to the command line and ask cgminer to list the number of units, it comes back with the correct number of 10. However, when I run a little python script I wrote to get status from the cgminer API, it comes back and tells me that I have 16 devices.

I know that I can just bounce cgminer and it should get back to normal. But it would be nice if it would just work.

Again, this is the first time in a week that I've seen this. Although since I've been setting up and tweaking this rig, I don't think I've had cgminer running for more than a couple of days at a stretch. Currently it's been running for about 32 hours.

Any ideas, other than the obvious work around of restarting cgminer?

Thanks Alex. I've isolated the problems to specific units and have sent you a PM to start the RMA process.

It might not be a problem. But when I was debugging my rig, I moved my USB fans to this cheap, switchable hub, isolated from the miners:

http://www.amazon.com/gp/product/B00BWF5U0M/ref=oh_details_o01_s00_i02?ie=UTF8&psc=1

I have no idea if this helped or not. But for $7 it was worth it just to be able to turn my USB fans on and off as needed.

With my current rig, all of my DMs are on Oricos, laid out as per CruzCoins diagram (avoiding the USB plug by the power switch), and both of my fans (ARCTIC Breeze Mobiles) are on the cheap Sabrent switchable hub, with no cross connection to the DM units or the Pi.

This is working for me. Except for the one new DM, which I think might be marginal. As I said, I'm talking with DM support about that unit.

You will probably have better luck with a Raspberry Pi. I've got 29 units running on a single Pi. I do have a problem with one of them, and am working through that with DM support. But the rest are working great and my rig has been super reliable.

Also, in case you didn't notice, it's absolutely critical that you position your DMs in the right ports in the Orico hub. You can only have 9 per hub, and you have to avoid plugging a miner into the slot next to the power button. The reason is that an Orico hub is actually two hubs under the hood, with different power characteristics.

Probably not a problem if you only have 3, but in case it's relevant, make sure you avoid that slot by the power button. Ignoring that caused me stability problems early on.

If you decide you want out and want to sell your DMs, send me a PM. I'll probably take them off your hands if it's cheap enough...

jedimstr is absolutely right. I'm a new miner, late to the party, using nothing but GridSeeds. I've got two rigs that currently run at about 5 Mhs total. I've never used GPUs.

I'm on CleverMining.com, which is a multi-pool. I'm pretty happy with them.

I was on ghash.io during their 2x - 1.25x LTC reward promotion. After that was over, I moved back to CleverMining. I've been there ever since.

I looked into mining DOGE, but the numbers I ran showed that I'd be better off with CleverMining. But that was before the DOGE fork. So I'm keeping an eye out on DOGE. The author of this thread just added a DOGE pool to his comparison:

https://bitcointalk.org/index.php?topic=514242.new#new

Might be interesting to see how that pans out.

When you say it crashes, are you talking about the cgminer itself, or your Raspberry Pi?

If it's the Raspberry Pi, you should probably check that you've got the "slub_debug=FP" hack in place. This has been discussed in other places, but to save you searching time, here's what you need to do (if it's not already in place):

sudo nano /boot/cmdline.txt

Add the following code at the end of the first line (on the same line as the other text, DO NOT add new line!)


Save the file then reboot your Raspberry Pi.

What the above does is basically enable some kernel debug mode on the Raspberry Pi. I have no idea why debug mode prevents the system kernel crash, but there's a lot of anecdotal evidence that it does work. In my case, I couldn't run for more than an hour before my Pi would crash.

I suspect that there's a kernel bug that cgminer is somehow triggering. I don't know if anyone has seriously investigated this, given that most people just want a work around so that they can keep mining reliably. But if you're interested, here's a related thread that I found:

http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=55370

If the issue is that cgminer is crashing, not your Pi, doesn't it get restarted by the Scripta /etc/rc.local?

I've seen cgminer crash too. I got about 48 hours the last time before it crapped out. I'm using the dtbartle version that I built myself from the git sources, and I've got 10 GridSeed units.

This morning I decided to run cgminer in text only mode under daemontools. I've been running my Dual Miner version of cgminer like that for weeks on another rig and have never seen a crash of either the Pi or cgminer (and I don't have the slub_debug hack enabled on that Raspberry Pi, either). There's a lot to like about daemontools, including logging. And I see no need to have a terminal output in a detached screen process when Scripta does a nicer job of giving me visual miner status.

I have no idea if running cgminer in its default terminal mode under screen is in fact problematic or not. The stability problems might just be in the gc3355 implementation of cgminer. But I like how my other rig is running and it's nice to keep things consistent.

Anyway HTH...

I'm not sure that that is true. I looked at the cgminer sources for the DM and it definitely looks like that version of miner software handles frequencies up to 850. Looks like if you specify above that, it just gets capped to 850.

Maybe this is just the Linux version? I have no idea what the Windows version supports.

Earlier in this thread others have mentioned using 850 and gotten modest returns. For example, Poopypants said he was getting 72-75kh/s at 850. I tried using it too at one point, but backed off while trying to get my rig stable.

Now that my rig is stable, it would be nice to squeeze a little extra out of it. I might try it again...

I've got 10 GS units (stock, not modded) running at 850 under the dtbartle cgminer on a Raspberry Pi. All the units are working, but one of them is showing an inordinate number of hardware errors.

After 34 hours of runtime, the "bad" unit has had 110 hardware errors. The next runner up had 18. The remaining units are in single digits. The total number of HW errors across all the units is 155, so the bad unit accounts for 70% of the errors.

I'd like to try swapping cables and USB ports to see if the problem follows the unit itself. But I have to admit that I have no idea how to determine which physical unit is affected.

Can someone tell me how the cgminer output maps to physical devices? I tried lsusb, but it only shows generic information about the USB devices.

I know that I can just systematically unplug devices until the bad one disappears from the bus. But I was hoping there would be a better way than that. I'd like to leave as much of my rig running as possible while doing the diagnostics.

Thanks in advance for any suggestions.

Thanks for adding DOGE to the list. I'm also very interested in what happens with DOGE now after the fork.

I got my shipment of 10 units yesterday. Thanks Alex!

I've got the units in a test configuration and have been mining for about 12 hours. The only issue so far is that one unit is showing about 10 times as many hardware errors as the others. I'll try isolating the problem by switching cables and whatnot.

A bit of feedback. It would be nice if the power cables were a foot or two longer. As it is, you really have to put the units close to the power supply. In my final configuration, I'll probably solder some extensions on the power plugs so that I can isolate the power supplies to the back of my rig.

Lastly, my order was supposed to be without a controller because I've got my own Raspberry Pi. But in the USB hub box there was a little board that has an Ethernet and USB port. There was no case. I assume this is a controller, but I've never seen one before.

Maybe when I've isolated my hardware error problem we can figure out how to get this card back to you.

Thanks again for your support.

Wow! That's a really good price. It makes the DM2 pretty competitive with the GridSeed 5 chip units.

I only wish you did this sale earlier, *before* I decided to buy 10 GridSeed 5 chip units. I much prefer the ease of use and scalability you get from DMs.

They're already under 9 Gh/s. That a big difference from nearly 50 Gh/s at peak during the promo.

But they clearly got a lot of new registrations out of it and increased visibility, which I'm sure was their main goal.