[Minera v0.9.1] Your next mining dashboard - Antminer/CPUminer/CGminer/BFGminer

[qiqiji]

I found a issue due to Minera 0.3.5 with Raspberry B+ ( New version with 4 USB Ports )

When i power off ( from minera's web page or SSH then poweroff or halt ), after 10 to 15 second, Pi will auto poweron again

How ever, I test 2014-06-20 img form raspberrypi.org, not having this issue, and i manually install minera 0.3.5 and still not having this issue

I can't understand when you have the issue. But probably it's only an RPI config issue (wake up on lan?), nothing to do with Minera.

Now it's happens every time i try to shutdown the Pi no matter what IMG i use and the way i use ( from minera's UI or poweroff or halt ), and i test 6 of Raspberry Pi B+, it's all same! Is there anyone else use Raspberry Pi B+ here?

I think it's an RPI B+ issue, please check:

http://raspi.tv/2014/just-how-awesome-is-the-raspberry-pi-community-fixing-the-b-wont-shutdown-issue

Solved, i change a TF card and it won't happen again, old one is SanDisk 4G ( black, low-end ) , new one is SanDisk 8G ( red, high-speed )

And i think the link you gave talked about another issue ( use finger to touch GPIO to cause poweron ), but it's related to my issue, i can confirm that before i change the TF card, it happens, and after i change the TF card, it won't happen again too!

[1715020265]

1715020265

[idkzero]

Hi,

I have had problems with minera on the wifi level on my raspberry pi.  Minera would work find for maybe a day or 2 and wifi would lose connection and minera would sit there lifeless.  On my other raspberry's I have regular cgminer running and would re-ping for network connection over wifi and pick it up again with no problem.  But with minera, it would sit there dead.  Is there a way I can set up a job or something within minera to repick up network connection or reboot to start the jobs over again?

thank you for your time

[Axiste]

Log into the Minera dashboard and go to settings, there is an option to reboot after X hours. Put in how many hours you want, check the reboot box.

[DaveF]

OK, what the heck am I doing wrong?

1st off, did I read all 69 pages of this thread? Yes, sort of. I was dead tired by the time I finished at 2:30 this morning and might have missed something. So if I just flat out missed it, point it out to me let me have my Duh! moment.

Now to the problem, I have Minera running for 2 GS Blades and 3 Blizzards. The performance on the blades sucks. I have tried just about every setting I can think of and still crap. Plugging the USB hub into a Windows PC and running BFG all is good.

Any thoughts / settings / tweaks?

Quick edit: all the HW errors are from start up they do not go up in any meaningful way over 3+ hours.
-Dave

[Trimegistus]

OK, what the heck am I doing wrong?

1st off, did I read all 69 pages of this thread? Yes, sort of. I was dead tired by the time I finished at 2:30 this morning and might have missed something. So if I just flat out missed it, point it out to me let me have my Duh! moment.

Now to the problem, I have Minera running for 2 GS Blades and 3 Blizzards. The performance on the blades sucks. I have tried just about every setting I can think of and still crap. Plugging the USB hub into a Windows PC and running BFG all is good.

Any thoughts / settings / tweaks?

Quick edit: all the HW errors are from start up they do not go up in any meaningful way over 3+ hours.
-Dave

Are you setting the correct frequency for the blades?

Have you tried using cpuminer for the blades?

What about cgminer-zeus?

I gave up on bfgminer for my blades as it produces very high HW errors but I have been getting very stable results, both with cpuminer and with cgminer-zeus

[chadwickx16]

Dave,

I've been running my blades on Freq 838 on CPU miner at a solid 5.2MH+.

[herbiehasher]

Hello

For me with free power, it's more profitable to switch my 5chip gridseeds to dual mode from scrypt only.
I have gone and put the voltage to stock on 10 units, does minera support dual mining with the 5-chip gridseeds?

Thanks
Herb.

I hope to go from:

40 Mhash scrypt only

 to:

640 gighash sha-256 + 25 Mhash scrypt

may be more life left in these in dual or sha only mode.

On page 66 i detailed how i did dualmining with Minera. You will need to recompile cgminer-dmaxl-zeus for gridseed, then you manually set an instance of cgminer for sha256 to start via rc.local (in minera dashboard settings, near the bottom), then you set a scrypt instance as usual on mineras dashboard.

only the scrypt instance will be visible on the dashboard, you can monitor the sha instance via the api, ssh, or the command window in dashboard (essentially built in ssh)

i might be getting my terms wrong, but i have 10x 5chip minis and i get 3.6Mh scrypt only, or 60Gh Sha + 2.4Mh scrypt in dual mode.

Thanks for this.
Sorry for the little detail.  I have 80units in total, 70 at 49.9kohm resistor mod, 10 put to stock ready to try dual mode now.

[compumine]

Hey guys,

Anyone figured this out?  I'm trying to change the "altcoin prices" at the top from settings, but no matter what I chose, it's stays the same.  Only LTC/Doge/DRK are showing.  I can't seem to change them to anything else!!

Any ideas?  I'm using the most recent version.

[DaveF]

OK, what the heck am I doing wrong?

1st off, did I read all 69 pages of this thread? Yes, sort of. I was dead tired by the time I finished at 2:30 this morning and might have missed something. So if I just flat out missed it, point it out to me let me have my Duh! moment.

Now to the problem, I have Minera running for 2 GS Blades and 3 Blizzards. The performance on the blades sucks. I have tried just about every setting I can think of and still crap. Plugging the USB hub into a Windows PC and running BFG all is good.

Any thoughts / settings / tweaks?

Quick edit: all the HW errors are from start up they do not go up in any meaningful way over 3+ hours.
-Dave

Are you setting the correct frequency for the blades?

Have you tried using cpuminer for the blades?

What about cgminer-zeus?

I gave up on bfgminer for my blades as it produces very high HW errors but I have been getting very stable results, both with cpuminer and with cgminer-zeus

I can't get the Zeus to work with the cpuminer and can't get the blades to work with the cgminer-zeus.
BFG gets them both working but with the low speed for the blades.

-Dave

[Trimegistus]

I can't get the Zeus to work with the cpuminer and can't get the blades to work with the cgminer-zeus.
BFG gets them both working but with the low speed for the blades.

-Dave

I can't help you with the zeus, but I can share my current config for the blades:

Code:

su - minera -c "/usr/bin/screen -dmS cpuminer sudo /var/www/minera/minera-bin/minerd --gc3355=/dev/ttyACM0,/dev/ttyACM3 --gc3355-chips=40 --gc3355-timeout=120 --freq=820 --retries=1 -c /var/www/minera/conf/miner_conf.json"

Code:

su - minera -c "/usr/bin/screen -dmS cgminer sudo /var/www/minera/minera-bin/cgminer-dmaxl-zeus --usb 1:7,1:8 --retries=1 --scrypt --gridseed-options freq=825,chips=40 -c /var/www/minera/conf/miner_conf.json1"

The previous config selects two blades to work with a config file and a miner, and the other two to work with another miner and another config file.

These commands are in my rc.local file

Other options:

Code:

su - minera -c "/usr/bin/screen -dmS Nice /var/www/minera/minera-bin/minerd --gc3355=/dev/ttyACM0 --gc3355-chips=40 --gc3355-timeout=180 --freq=840 --retries=2 -c /var/www/minera/conf/miner_conf.json1"
sleep 10
su - minera -c "/usr/bin/screen -dmS Clever /var/www/minera/minera-bin/minerd --gc3355=/dev/ttyACM3 --gc3355-chips=40 --gc3355-timeout=180 --freq=840 --retries=2 -c /var/www/minera/conf/miner_conf.json2"
sleep 10
su - minera -c "/usr/bin/screen -dmS Waffle /var/www/minera/minera-bin/cgminer-dmaxl-zeus --usb 1:7 --retries=2 --scrypt --gridseed-options freq=840,chips=40 -c /var/www/minera/conf/miner_conf.json"
sleep 10
su - minera -c "/usr/bin/screen -dmS SGuild /var/www/minera/minera-bin/cgminer-dmaxl-zeus --usb 1:8 --retries=2 --scrypt --gridseed-options freq=840,chips=40 -c /var/www/minera/conf/miner_conf.json3"

4 miner processes for 4 different config files. It works like a charm  

With bfgminer:

Code:

/var/www/minera/minera-bin/bfgminer --retries=2 --scrypt --scan=all --load-balance --failover-only -S gridseed:all --set-device gridseed:clock=838 /var/www/minera/conf/miner_conf.json

or:

Code:

su - minera -c "/usr/bin/screen -dmS bfgminer /var/www/minera/minera-bin/bfgminer --scrypt -S gridseed:/dev/ttyACM1 --set-device gridseed:clock=820 --retries=2 -o stratum+tcp://[pool of choice]

or:

Code:

su - minera -c "/usr/bin/screen -dmS bfgminer /var/www/minera/minera-bin/bfgminer --scrypt --scan=all --set gsd:clock=820 --retries=2-o stratum+tcp://(pool of choice)

That's all I got but I have tested all these settings and they all work. Some better than others, but you know every blade is a diferent creature.

Good luck!

[DaveF]

And what is odd, running from the terminal it's all good.
Issuing the same command through the GUI and no.

-Dave

[subseaguru]

i have 2 pools as failovers, yet minera (or cpuminer) keeps changing pools automatically. i just checked the JSON and it shows extra command=false. im not sure why it keeps changing pools.

[coke15]

hi

new on minera

i have a black wido and the last img of minera on raspberry b.

pool setting ok,scan all,debug,root acces,try the 3 miners   ans still  NO DEVICE DETECTED?

how to recognize my blak widow?

than,ks

[kevin1234a]

Try changing your scripts. Got same issue where gridseed and zeus were not fetting detected. Changed to bfgminer and resilve issue

[coke15]

hi

changing script?
 i try with nothing :on windows i have --nocheck-golden --chips-count 64 --ltc-clk 328   but nothing on minera

[coke15]

hi

only work with zeus miner those arguments:

--scrypt --scan-serial /dev/ttyUSB0

no chips no ltc?

[nwoolls]

hi

only work with zeus miner those arguments:

--scrypt --scan-serial /dev/ttyUSB0

no chips no ltc?

Try:

Code:

--scrypt -S zus:all

[Vortex20000]

Thank you so much for this!

Works like a charm.

[Axiste]

michelem, on the settings page, there is a setting for auto-delay, to delay when the miner process is started, how is that implemented?
I was hoping to use it to allow my first cgminer-dmaxl to start in rc.local, which will pick up all my Gridseed minis in SHA256 mode, then have the Minera cgminer-dmaxl instance start say 1 minute later in scrypt mode.

It seems if I set a delay in settings, both my rc.local entry AND the minera instance get delayed exactly the same. So i then have to kill the scrypt instance (sometimes via the api instead of the minera menu as it wont always work, seems to be 50/50) once Scrypt is stopped, the SHA will generally pick up all the gridseeds over the next minute (hotplug for the win) and then i can start the scrypt instance again (works fine from the dashboard).

Note: the rc.local entry is via the minera dashboard option, as putting it directly into etc/rc.local gets overwritten on reboot ( i presume by minera dashboard)

[michelem]

michelem, on the settings page, there is a setting for auto-delay, to delay when the miner process is started, how is that implemented?
I was hoping to use it to allow my first cgminer-dmaxl to start in rc.local, which will pick up all my Gridseed minis in SHA256 mode, then have the Minera cgminer-dmaxl instance start say 1 minute later in scrypt mode.

It seems if I set a delay in settings, both my rc.local entry AND the minera instance get delayed exactly the same. So i then have to kill the scrypt instance (sometimes via the api instead of the minera menu as it wont always work, seems to be 50/50) once Scrypt is stopped, the SHA will generally pick up all the gridseeds over the next minute (hotplug for the win) and then i can start the scrypt instance again (works fine from the dashboard).

Note: the rc.local entry is via the minera dashboard option, as putting it directly into etc/rc.local gets overwritten on reboot ( i presume by minera dashboard)

rc.local is always overwritten by Minera, but you have the textarea on settings page to add your personal lines.

the delay option does only one simple thing: it changes the sleep time in the rc.local file, by default it's 5 seconds.

Code:

[...]
sleep 5
su - minera -c "/usr/bin/screen -dmS cpuminer /var/www/minera/minera-bin/minerd  --retries=1  -c /var/www/minera/conf/miner_conf.json"
[...]

If you have more then one miner starting from rc.local you should add sleep before each one.