Latest posts of: MScFW

Show Posts
Pages: [1]

Alternate cryptocurrencies / Mining (Altcoins) / Re: [Minera v0.3.1] Your next mining dashboard is here. CPUminer/CGminer/BFGminer.

on: July 15, 2014, 05:05:03 PM

Hi michelem, thanks for the update and the hard work. After the update via web ui I also did the manual update from git sources => now I'm on 0.3.1, and it seems like the cpuminer startup has a small issue. 3 out of 4 starts I have 2 instances of cpuminer running after a reboot. Of cause it's not working this way. Tried to change the startup delay from 1 to 5 sec, same thing. Do you have an idea what may cause this? bye MScFW

Economy / Service Announcements / Re: [ANN] MiningRigRentals.com - Many Algorithms / Web Pool Manager / Lowest Fees

on: July 07, 2014, 06:11:36 AM

Hi Miningrigrentals, for my understanding you system acts like a proxy between the pool and the rig, right? On the rig I get messages like "New Job_id: 7bbd Diff: 1024 Work_id: 38d4ea3b", so your proxy should be able to track the diff value. If the diff would now be presented in a chart, together with a line "Recommended Diff", like the "Advertised Hashrate", it would give both sides an indicator. Just my 2 ct. bye

Alternate cryptocurrencies / Pools (Altcoins) / Re: [POOL][Scrypt][Scrypt-N][X11][X13] Profit switching pool - wafflepool.com

on: July 06, 2014, 06:36:08 PM

I usually start with 850 MHz in "autotune" mode, after a couple of hours I use the "save current frequencies" to generate the required miner option. Something like:

Code:

--gc3355-freq=8D7830995748:850:0,8D7830995748:900:1,8D7830995748:875:2,8D7830995748:875:3,8D7830995748:875:4,6D7024984857:850:0,6D7024984857:875:1,6D7024984857:900:2,6D7024984857:875:3,6D7024984857:850:4,6D73109C4853:875:0,6D73109C4853:900:1,6D73109C4853:875:2,6D73109C4853:875:3,6D73109C4853:875:4,6D74216E4853:825:0,6D74216E4853:875:1,6D74216E4853:825:2,6D74216E4853:900:3,6D74216E4853:875:4,6D75227D4853:850:0,6D75227D4853:850:1,6D75227D4853:850:2,6D75227D4853:875:3,6D75227D4853:850:4,6D6E25A74857:875:0,6D6E25A74857:875:1,6D6E25A74857:850:2,6D6E25A74857:875:3,6D6E25A74857:875:4,6D75216D4853:875:0,6D75216D4853:875:1,6D75216D4853:875:2,6D75216D4853:875:3,6D75216D4853:875:4,8D7230965748:875:0,8D7230965748:850:1,8D7230965748:850:2,8D7230965748:900:3,8D7230965748:875:4,6D7838894857:875:0,6D7838894857:875:1,6D7838894857:875:2,6D7838894857:875:3,6D7838894857:850:4,6D7635624857:875:0,6D7635624857:875:1,6D7635624857:875:2,6D7635624857:875:3,6D7635624857:875:4

and finally I disable autotuning. As a result I've a very low HW-Error rate and devices already start with "best" option.

Economy / Service Announcements / Re: [ANN] MiningRigRentals.com - Many Algorithms / Web Pool Manager / Lowest Fees

on: July 06, 2014, 04:16:39 PM

I've a question/suggestion, as a "owner" I'm frequently seeing "customers" configuring their pool in a way that they do not end up in happy mining. Most of the time the diff/vardiff setting are going up to the moon and the hash rate / number of accepted shares is very very low. There are some basic checks when you add a pool to your list, but is it also possible to test or warn people using wrong diff settings? Because I don't see the settings and I don't know the pool, it's really hard to fix it! bye MScFW

Alternate cryptocurrencies / Pools (Altcoins) / Re: [POOL][Scrypt][Scrypt-N][X11][X13] Profit switching pool - wafflepool.com

on: July 06, 2014, 03:34:27 PM

Quote from: 5ick3uffalo on July 06, 2014, 02:50:34 PM Hi, to understand this little better technology wise. First i had only 5 Gridseeds, now 11 Gridseeds with one RasBerry PI mining on wafflepool. Before with 5 Gridseeds i was stable with 850 MHZ setting, now i can not go 850 MHZ anymore i would end up with a few hundered HW-Errors. It is other pools also. With 800 MHZ its perfecly fine with very few Hardware Errors. Has this to do because now the RasBerry must handle more Gridseeds now? And how many Gridseeds my RasBerry could handle maximum? 20? (11 Now) PS: I´m using hashra-image. Hi 5ick3uffalo, I had something similar issues a while ago. Unfortunately there is no easy - go that way - answer. Things I tried/changed with sucess: a reliable USB hub, may sound strange, but 3 out of 4 cheap ones didn't do the job very well in a 24x7 solution tried several PI solutions for Gridseed and finally found Minera (https://bitcointalk.org/index.php?topic=596620.0), based on CPUMiner - Autotuning support for the Minis - Autorestart of miner if a device stops I'm more than happy with it, 24, 48h with <1% HW-Errors and <1% rejects. But it doesn't like some pools! Added some additional safety lines to the PI system - slub_debug=FP in /boot/cmdline.txt - BMC2708 hardware watchdog, just in case I do no longer need a regular reboot. Give it a try (In v0.2.3 you can remove the donation pool from the UI) bye

Alternate cryptocurrencies / Mining (Altcoins) / Re: [Minera v0.2.3] Your next mining dashboard is here.

on: July 06, 2014, 11:30:13 AM

Quote from: FullBoat on July 06, 2014, 09:01:32 AM Quote from: mindtrip on July 05, 2014, 08:06:45 PM Just a general question is everyone running there Pi's in Stock mode? I tried today doing the Modest over clock and I am running 6 Gridseed Blades and my average Load is 0.24 which seems a little lower then on stock clock which was closer to 0.29 not a huge difference but its just as stable so I was wondering if there is really anything to gain from OCing the Pi possible the ability to handle more miners for those having trouble over 20 globes has anyone tried this out? I notice my Pi running Stock clock 16 Globes runs about 0.25 as my 15 min average From my understanding, it's not the speed that's stopping the Pi from controlling more, but the on-board memory. OCing the Pi really doesn't get you anything extra, except more heat maybe. You can try to reconfigure the memory usage by adding / changing "gpu_mem=16" in the "/boot/config.txt" file to only use 16M for the gpu.

Alternate cryptocurrencies / Mining (Altcoins) / Re: [Minera v0.2.2] Your next mining dashboard is here.

on: June 30, 2014, 06:45:12 PM

Hi phiber, did you disable "Enable frequency auto tuning (--gc3355-autotune)" in settings? If you do a "screen -r" in a ssh session or in the local console short after restarting the miner (not the whole system, you can see the configuration during startup for a short while. bye MScFW

Alternate cryptocurrencies / Mining (Altcoins) / Re: [Minera v0.2.2] Your next mining dashboard is here.

on: June 28, 2014, 08:38:35 AM

Hi michelem, switching to CGminer or BFGminer instead of the CPUminer would turn Minera into "just another Raspery PI solution". I tried a lot of images based on several versions of these miners, not finding a better working setup. For me CPUminer has some nice features: autotuning for the Minis - haven't tried it my blades so far beside the switching issue it's way more stable than any of the other miners I've tested in combination with your ui and your monitoring option it's "just working" most important: it's clean and light - not overloading the PI like some other solutions From my point of view it would make sense to fix the CPUminer and improve the ui step by step - just my opinion. Looking for some unique features for the next releases: common dashboard for multiple Minera instances with control and not only status extending the summary for pool hashrate and last share information to show min/max/avg adding something to switch pools on profit ... bye MScFW

Alternate cryptocurrencies / Mining (Altcoins) / Re: [Minera v0.2.2] Your next mining dashboard is here.

on: June 27, 2014, 03:44:44 PM

Hi michelem,
hi all,
first I want to say that Minera is so far the most reliable/stable miner solution I've tried for my small Gridseed farm - great job, thanks michelem!

At the moment I'm using 2 Raspberry PIs, one managing 10 Gridseed Minis, the other one supporting 5 Gridseed Blades.

Even a good solution can be improved, that's the reason why I would like to share some of my findings and ideas.

1. Stability

With some hardware revisions and kernel version there is a reported issue with freezing systems. As already mentioned in most of the topics covering various Raspberry PI mining solutions, there is an easy workaround by adding an addional parameter to the "/boot/cmdline.txt" file:

Code:

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait slub_debug=FP

The "slub_debug=FP" will do the trick.

=> perhaps an option for the next release?

If this is not enough, or you are looking for an additional safety-line, unsing the build-in harware watchdog is an option. Unfortunately most available sources do not cover a small issue with defaults in the actual version 5.12 of the watchdog daemon. The watchdog in the BMC2708 is limited to ~16s timeout, but the default of the watchdog daemon seem to be 60s. If you want to give it a try, the following steps will do it, incl. a workaround for the timeout issue:

Code:

$ sudo modprobe bcm2708_wdog
$ echo "bcm2708_wdog" | sudo tee -a /etc/modules

$ sudo apt-get update
$ sudo apt-get install watchdog
$ sudo chkconfig --add watchdog
$ sudo chkconfig watchdog on

The configuration in "/etc/watchdog.conf" should look like this:

Code:

max-load-1              = 24
min-memory              = 1
watchdog-device = /dev/watchdog
realtime                = yes
priority                = 1
watchdog-timeout   = 10

The additional parameter "watchdog-timeout = 10" solved the problem on my systems.

The last step is starting/restarting the daemon:

Code:

$ sudo /etc/init.d/watchdog restart

=> could be added to the master image in one for the next releases?!?

Last bit is an automatic reboot every 12 hours, for that I added a line to "/etc/crontab":

Code:

...
5 */12 * * *    root    /bin/sync && /sbin/reboot
...

This will sync the SD card and rebbot the PI at 0:05 and 12:05 every day.

=> configuration through the web ui would be nice!

2. Pool Selection / NiceHash / Donation Pool

My two systems do NOT behave the same.

the Minis have not yet reached the "race condition" to end up with the last pool in the list
for my Blades this happened already several times - was Ok as donation for michelem, but should not be the default behaviour in the future.

Based on what I could track on my system, it's not just NiceHash, but NiceHash with the "p=x.y" option as password will more or less force the failure when the pools are changed too often. It also happend to me with ltcrabbits and a very low diff when switching to this pool, but only with the blades, not with the Minis!
The "cpuminer.log" shows the following:

Code:

[2014-06-26 23:21:17] stratum_recv_line failed
[2014-06-26 23:21:17] Stratum connection interrupted
[2014-06-26 23:21:17] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:21:17] stratum_recv_line failed
[2014-06-26 23:21:17] ...retry after 5 seconds
[2014-06-26 23:21:22] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:22] ...retry after 5 seconds
[2014-06-26 23:21:23] New Job_id: 2f41 Diff: 32 Work_id: 8ed3f9d6
[2014-06-26 23:21:25] New Job_id: 2f42 Diff: 32 Work_id: 8ed3f9d6
[2014-06-26 23:21:27] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:27] ...retry after 5 seconds
[2014-06-26 23:21:27] Rejected 600a447b GSD 7@15
[2014-06-26 23:21:27] DEBUG: reject reason: job not found
...
[2014-06-26 23:21:27] DEBUG: reject reason: job not found
[2014-06-26 23:21:32] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:32] ...retry after 5 seconds
[2014-06-26 23:21:32] Rejected a6714685 GSD 0@26
[2014-06-26 23:21:32] DEBUG: reject reason: job not found
[2014-06-26 23:21:32] stratum_recv_line failed
[2014-06-26 23:21:32] Stratum connection interrupted
...
[2014-06-26 23:21:47] Rejected ecdabe3d GSD 3@37
[2014-06-26 23:21:47] DEBUG: reject reason: low difficulty share of 0.000028805203748063583
[2014-06-26 23:21:47] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:21:48] stratum_recv_line failed
[2014-06-26 23:21:48] ...retry after 5 seconds
[2014-06-26 23:21:52] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:52] ...retry after 5 seconds
[2014-06-26 23:21:53] New Job_id: 2f93 Diff: 32 Work_id: 8ef195ed
[2014-06-26 23:21:57] submit_upstream_work stratum_send_line failed
[2014-06-26 23:21:57] ...retry after 5 seconds
[2014-06-26 23:21:58] Rejected 8674e16b GSD 4@21
[2014-06-26 23:21:58] DEBUG: reject reason: low difficulty share of 0.00002044789273909275
...
[2014-06-26 23:21:58] Rejected f34240a1 GSD 0@38
[2014-06-26 23:21:58] DEBUG: reject reason: low difficulty share of 0.0008953760268679294
[2014-06-26 23:22:00] Checking main pool: stratum+tcp://stratum.nicehash.com:3333
[2014-06-26 23:22:00] Stratum authentication failed
[2014-06-26 23:22:03] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:03] Rejected 6cdbeab1 GSD 7@17
[2014-06-26 23:22:03] DEBUG: reject reason: low difficulty share of 0.00002086725782000612
[2014-06-26 23:22:03] ...retry after 5 seconds
[2014-06-26 23:22:03] Rejected 600f3044 GSD 6@15
[2014-06-26 23:22:03] DEBUG: reject reason: low difficulty share of 0.000026977634249723677
...
[2014-06-26 23:22:03] Rejected b9a9127e GSD 2@29
[2014-06-26 23:22:03] DEBUG: reject reason: low difficulty share of 0.000020940332663484334
[2014-06-26 23:22:03] stratum_recv_line failed
[2014-06-26 23:22:03] Stratum connection interrupted
[2014-06-26 23:22:03] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:22:03] New Job_id: 2f42 Diff: 32 Work_id: 8efb367d
[2014-06-26 23:22:08] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:08] ...retry after 5 seconds
[2014-06-26 23:22:08] Rejected e678590b GSD 1@36
[2014-06-26 23:22:08] DEBUG: reject reason: job not found
...
[2014-06-26 23:22:08] Rejected 93459d49 GSD 5@23
[2014-06-26 23:22:08] DEBUG: reject reason: job not found
[2014-06-26 23:22:13] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:13] ...retry after 5 seconds
[2014-06-26 23:22:13] Rejected 8678f100 GSD 6@21
[2014-06-26 23:22:13] DEBUG: reject reason: job not found
[2014-06-26 23:22:13] stratum_recv_line failed
[2014-06-26 23:22:13] Stratum connection interrupted
[2014-06-26 23:22:13] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:22:13] stratum_recv_line failed
[2014-06-26 23:22:13] ...retry after 5 seconds
[2014-06-26 23:22:18] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:18] ...retry after 5 seconds
[2014-06-26 23:22:18] New Job_id: 2f94 Diff: 32 Work_id: 8f0a8598
[2014-06-26 23:22:23] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:23] ...retry after 5 seconds
[2014-06-26 23:22:23] Rejected 59afe1e6 GSD 7@14
[2014-06-26 23:22:23] DEBUG: reject reason: low difficulty share of 0.000038679563917316584
...
[2014-06-26 23:22:23] Rejected 59b0570a GSD 4@14
[2014-06-26 23:22:23] DEBUG: reject reason: low difficulty share of 0.000015259335727904784
[2014-06-26 23:22:28] Stratum detected new block
[2014-06-26 23:22:28] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:28] New Job_id: 2f95 Diff: 32 Work_id: 8f1429f3
[2014-06-26 23:22:28] ...retry after 5 seconds
[2014-06-26 23:22:28] Rejected 867d2d1d GSD 0@21
[2014-06-26 23:22:28] DEBUG: reject reason: job not found
...
[2014-06-26 23:22:28] Rejected b3366217 GSD 8@28
[2014-06-26 23:22:28] DEBUG: reject reason: job not found
[2014-06-26 23:22:33] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:33] Rejected b99a43d0 GSD 1@29
[2014-06-26 23:22:33] ...retry after 5 seconds
[2014-06-26 23:22:33] DEBUG: reject reason: job not found
[2014-06-26 23:22:33] Rejected c667315c GSD 9@31
...
[2014-06-26 23:22:33] Rejected c0006c5f GSD 4@30
[2014-06-26 23:22:33] DEBUG: reject reason: job not found
[2014-06-26 23:22:33] stratum_recv_line failed
[2014-06-26 23:22:33] Stratum connection interrupted
[2014-06-26 23:22:33] Starting Stratum on stratum+tcp://eu.ltcrabbit.com:3333
[2014-06-26 23:22:33] stratum_recv_line failed
[2014-06-26 23:22:33] ...retry after 5 seconds
[2014-06-26 23:22:38] submit_upstream_work stratum_send_line failed
[2014-06-26 23:22:38] ...retry after 5 seconds
[2014-06-26 23:22:38] stratum_recv_line failed
[2014-06-26 23:22:38] ...retry after 5 seconds

If have also seen crap strings as pool names in the screen session during this race, but could not capture this.
Remarks:

Gridseed Blades don't like very small diffs, like 32, best results for me in a range from 256 to 1024 for my setup.
Girdseed Minis will work with a diff of 32 already, better results within a range from 128 to 512, again in my setup
For me it seems to be a problem of the cpuminer, not linked to the Minera UI and/or the donation pool idea

It looks like the miners are not set to a default state during a pool switch, so the results may not fit to new jobs and will produce a high number of rejects.
If I understood right, cpuminer is using an array to store some additional data for each pool during runtime, based on the crap strings I have seen, I would not be surprised if there is a "buffer overflow", "pointer error" or a kind of type mismatch in this lately added part. If it comes to a pool switch followed by a larger number of rejects things will/may go wrong.
>> All mentioned as a person who can't really read and understand code, so maybe I'm totally wrong here. <<

Based on this problem I'm not using NiceHash with the "p=x.y" option, witch means I have to monitor manually or use only pools where I can define the minimum diff for each worker - not good.

Regards

MScFW

Pages: [1]