Topic: Minera 0.4.0 and Gridseed 5 Chip miners mine Bitcoin? (Read 4505 times)

There it is!!! Now I see it! The "sudo" did the trick.

Now I can see that each miner is working, and the speed and error rate of each miner.

Thank you Axiste!!!

oh, might need to do:

sudo screen -r bfgminer

as its in rc.local its probably started as root user not minera

Nope....  Didn't work. When I enter "screen -r bfgminer" it returns "There is no screen to be resumed matching bfgminer."

If I enter "screen -r" I see my Gridseeds mining away.

while on ssh, you need to do:

screen -r bfgminer

which will bring it to the front so you can see it in the terminal.

then, to leave it running when you finish looking at it, do:

ctrl + a, then d

this will move it back to background, otherwise if you press q it will quit.

Thanks Axiste!!!! Great info! I got it working! The Gridseed 5 Chips are mining AND my Red Furies are mining too. I can tell they are mining because the lights on them are flashing and the worker stats page (on the pool's website) shows them working. But I can't see BFGminer running from SSH or my browser.

Here's what I ended up putting in....
screen -dmS bfgminer /var/www/minera/minera-bin/bfgminer -o stratum+tcp://stratum.bitcoin.cz:3333 -u MyUserName.redfuries -p x -S bigpic:all --api-listen --api-port 4030 --api-allow W:192.168.1.50

My computer's IP is 192.168.1.50 on my local network, so I should have access. What do I need to do in SSH or my browser to see the instance of BFGminer running?

you could run a seperate instance of BFGminer in the background on minera, as I did for my dual mining on page 66 ish of Minera thread, you put the startup command into the rc.local settings on the dashboard settings page.

Essentially it would be

screen -dmS bfgminer /var/www/minera/minera-bin/bfgminer -o -u -p -S antminer:all --set-device antminer:clock=x0781 --api-listen --api-port 4030 --api-allow W:192.168.0.0/24

That will start bfgminer seperately behind the minera dashboard, with an antminer U1 at 1.8GHs, with the api set on port 4030 (so as not to interfere with the CPUMiner running on Minera) and allowing full control of the api from the 192.168.0.* network.

Obviously change the -S antminer:all --set-device antminer:clock=x0781 for settings that work for your device.

Yes, I know. I have fun tinkering with this stuff. I'm also not liking LTC at the moment. When I first started mining it, it was on it's way up to $12. Now it's <$2. And the difficulty seemed to really shoot up. And there's absolutely no "buzz" about it. Everything seems to be about BTC. So I thought I'd focus all my miners on BTC for a while.

How did you come up with 300W for running 4 Gridseed 5 Chips miners? In BTC only mode, I thought these things used 60 watts each. That would be 240 + a couple of watts for the Raspberry Pi. I'll have to break out the old "Kill A Watt" and take a reading.

SOME of my electricity is free. I sold a hot tube I wasn't using anymore for $2,000. With half of that money I designed and built an 810 watt solar system. On sunny days (we have a lot of them here in Southern California) I'm generating over 400 watts from 9am to 3pm. I'm planning on expanding this system later this year.

I hope you're just doing this for fun, because these are still more effective mining Scrypt than SHA256.  They were nearly outdated on SHA256 when they were released nearly a year ago(wow, it's been a year already!), and consuming 300W to get 26GH is fruitless.  Even if you have free power, you're still better off pointing these towards a Scrypt coin...

That makes sense. That's why I couldn't get it to work.

But can't I just SSH to Minera and start a regular CGminer (or BFGminer) and control the Red Furies from there? I've been trying to do this, but I can't get it to work.

i believe the dmaxl zeus is built with only Gridseed orb and Zeusminer drivers enabled, you would have to rebuild the miner with other drivers enabled to make it work.
(Its been built that way due to issues enabling all drivers at once)

At one point I was running my Antminer U1 on the SHA instance with my orbs, so had to rebuild dmaxl zeus with Icarus drivers enabled otherwise it wouldnt detect.

Now that I have my Gridseed 5 Chip miners mining away at Bitcoin with a few extra USB ports on my powered hub, I thought "Why not plug in the Red Furies I have laying around."

They light up and look like they are ready to mine (the hub should have plenty of power to run these), but CGminer (Dmax Zeus fork) doesn't see them.

I tried adding "--enable-bitfury" to the Extra Options field, but it returns "--enable-bitfury: unrecognized option" in the Real Time Log.

Does anyone know a way for CGminer (Dmax Zeus fork) to see my Red Furies on the hub along with the Gridseed 5 Chips?

But what would I run the proxy on? Another computer? Another Raspberry Pi? (I do have B+ on order. Should be delivered Monday.)
Would it be worth running another computer just get a lower error rate? What does a Raspberry Pi B+ burn?... 1.5watts? 2watts?
I guess it might be worth it.

I also found that if I ran a BFGMiner proxy to connect to my pool of choice, then pointed my Minera with 10x Gridseeds on it at the Proxy, i would get much lower HW errors. Probably because I left the Diff at 1.

My testing results...

These numbers are for all 4 Gridseed 5 Chip miners, after 16 minutes of mining.

Frequency....Shares......GH/s...Hardware
................Accecpted...............Errors
750...............293.......23.24....27.05%
775...............252.......23.44....24.70%
800...............277.......24.38....20.62%
825...............281.......25.14....19.43%
850...............326.......25.91....26.13%
875...............172.......14.15....32.59%

Wow! These numbers are all over the place. I think 16 minutes is too short of a run time to get a good feel for what's best.

I got more accepted shares at 750 than I did at 775. But that could be due to luck and with a longer run time things would even out.

And they don't like 875 AT ALL!!!!

It looks like I need to focus on and around 850. I'll do more tests with much longer run times, and change the frequency by 12.5.

yup that would be it, unfortunately they do run high errors on SHA256, at anything above the default 600Mhz clock.

  I got it working!!! 

After quite a bit of searching and a whole lot of reading, I got it to work.

I'm mining Bitcoins using a Raspberry Pi with Minera 0.4.0, and 4 Gridseed 5 Chip miners.

On the settings page, I set the mining software to CGminer (Dmax Zeus fork), and in the Extra Options field I put...
--sha256 --scan-serial gridseed:auto --gridseed-options freq=800

At this frequency, each miner is mining at ~6GH/s. I guess that's OK.

BUT... I'm getting a lot of hardware errors. 20.62%.

I'm not sure why the hardware error rate is so high. I'm trying different frequencies now. (with 15minute runs)

Thank you Axiste!
I think the post you're talking about is on page 66.
That's good news, but it's above my skill level.
You talk about how you had to rebuild CGminer-Dmax-Zeus and you got it to dual mine. That was back with Minera 0.3.4. Would the newer 0.4.0 with CGminer (Dmax Zeus fork) already have what it needs, or do I still need to rebuilt it? I hope not, because I don't know how to do that.

If CGminer (Damx Zeus fork) in Minera 0.4.0 is ready to go, what do I need in the command line to make it work? I don't really want to dual mine.... Just sha256 mine only.

I'm trying to mine Bitcoin, in Slush's Pool, with 4 Gridseed 5 Chip miners.

It can be done, you need to use CGMiner Dmaxl Zeus. If you look about page 67 in the Minera thread I show how I ran both Bitcoin mining and Scrypt mining on the Gridseed orbs at the same time, on Minera.

You can still do bitcoin mining with them now.

On the BFGminer 5.0 thread, it says that it has drivers for Gridseed in scrypt mode. So I don't think that BFGminer will run Gridseed miners in sha256. 

I know there was a modded version of CGminer 3.8.5 that worked with Gridseed miners in sha256, but it's only for Windows or Mac. 

So now I'm thinking it just can't be done on a Raspberry Pi with Minera. 

I don't want to run a full sized (or laptop) computer just to mine a little Bitcoin. If I can't do it with my Raspberry Pi, then I'll just mine Litecoin with these Gridseed 5 Chips and my Raspberry Pi.

Minera is GREAT on the Raspberry Pi! It's the best with CPUminer and my Gridseed 5 Chips mining Litecoin. The "auto tuning frequency" is really working well. It's squeezing out highest frequency for each gridseed 5 Chip miner, while keep the "hardware errors" very low (<1%).   

Thanks for the reply michelem.
Remove "--scrypt" from where? The Extra Options field? I don't have it in there.

When I've tried to mine with BFGminer, I've tried it with nothing in the Extra Options field. I've also tried it with this in the Extra Options field...

-S gridseed:all --set-device gridseed:clock=750 --failover-only

With this line in the Extra Options field, BFGminer does run, but it can't find my Gridseed 5 Chips miners. I SSH to my Raspberry Pi and did a "screen -r" to see that BFGminer is running, but it says "NO DEVECES FOUND". I tried adding devices by pressing "M" and then "+", but it still can't find them.

I think I'm missing something in the Extra Options field.

I never used them to mine BTC but I know CPUMiner doens't support it, it is for scypt only mining so don't use it.

With cg/bfgminer you should only remove the --scrypt option. If you are getting 300+Kh/s you are not mining SHA256.

OK... I got it to work, a little.... Or at least try to mine.

They seem to be mining really slow. Each Gridseed 5 Chip is supposed to mine Bitcoin at 11GH/s, but I'm only getting 339KH/s with the frequency set at 800MHz.

Setting the mining option in Minera to CPUminer (no added commands), it does try to mine, but EVERYTHING is rejected by the pool. Here is some of the miner log...

[2015-01-08 21:48:39] DEBUG: reject reason: Share is above target
[2015-01-08 21:48:39] Rejected 333f0a0b GSD 3@1
[2015-01-08 21:48:39] DEBUG: reject reason: Share is above target
[2015-01-08 21:48:40] Rejected 334827a6 GSD 1@1
[2015-01-08 21:48:40] DEBUG: reject reason: Share is above target
[2015-01-08 21:48:42] Rejected 33447403 GSD 0@1
[2015-01-08 21:48:42] DEBUG: reject reason: Share is above target
[2015-01-08 21:48:44] New Job_id: 44209 Diff: 32 Work_id: 6b9e459b
[2015-01-08 21:48:46] Rejected 99b4d4cd GSD 2@3
[2015-01-08 21:48:46] DEBUG: reject reason: Share is above target
[2015-01-08 21:48:46] Rejected 00134c57 GSD 3@0
[2015-01-08 21:48:46] DEBUG: reject reason: Share is above target
[2015-01-08 21:48:47] Rejected 001cbca1 GSD 1@0
[2015-01-08 21:48:47] DEBUG: reject reason: Share is above target
[2015-01-08 21:48:48] Rejected 999c1e93 GSD 2@3
[2015-01-08 21:48:48] DEBUG: reject reason: Share is above target

Should there be something in the extra command line?
A little help please.

If I use BFGminer without the scrypt option, then what options (if any) should I use?

I'm using Minera 0.4.0 on a Raspberry Pi. I've tried all the different mining software in the Minera settings. I tried CPUminer, BFGminer, CGminer, and CGminer (Dmax Zeus fork) all with no extra commands.

I sure like Minera over MinePeon. I sure would like to get these Gridseeds mining Bitcoins without using a desktop or laptop computer.

What miner software do you use, you should try bfgminer without the scrypt option or try to look at http://getminera.com/help

I'm using Minera 0.4.0 on a Raspberry Pi (B 512) and 4 Gridseed 5 Chip miners. I can get this to all work great mining Litecoin. But I can't get it to mine Bitcoin.

Every time I try mining Bitecoin, the Dashboard locks up and no work is being done (according to the mining pool).

Can Minera 0.4.0 on a Raspberry Pi B with 4 Gridseed 5 Chip mines be configured to mine Bitcoin only?