Trying to change frequency on antrun.de, fine with Frequencies up to 250MHz but at 275MHz and above I get Please provide valid input.
Rich
Hi Rich, Thanks for the info! I sent a bugfix and some additional stuff to ammi. |
|
|
|
Where abouts do you put the --suggest-diff 64 (is that how you enter it aswell?)?
Put it in the password field. Separate the password and the parameter with a blank:  --suggest-diff 22
Not to low? (no alt coin) I don't know what the right diff is for our speed. Ckpool automatically set the diff to 8 for my hashing rate. That's what I have set now.. The picture is older, with a higher diff.. What do you use? |
|
|
|
Where abouts do you put the --suggest-diff 64 (is that how you enter it aswell?)?
Put it in the password field. Separate the password and the parameter with a blank: --suggest-diff 22
|
|
|
|
Hi all, ckpool has some problems. Some miners went offline or switched to failover pool. Please don't forget to set it all back to ck, once the site's problems are gone...  |
|
|
|
That is not fair, joining and immediately capturing the first place   |
|
|
|
Endlich gefällt mir die Tabelle  |
|
|
|
I have added to the Cron Job that restarts the Miner a write to a file on the R1, so I already have the info on when the restarts occur. Actually the restarts are not, for me, the biggest problem. It is that, at frequencies above 200MHz, sometimes restarting cgminer does not restart the hashing, but doing a Save & Apply, which I thought just restarted cgminer does get it hashing again. Sometimes it needs a reboot to get things going again. Sometimes I have to take the frequency back to 200Mhz and then do a Save & Apply at the higher frequency.
Sorry if the above is a bit complicated, but you get the gist of what I am fighting with. I am however not at all Unix / Openwrt wise so I am sure that there is more that could be logged that would help the process?
Rich
Maybe someone could find the commands which gets executet, when changing something related to cgminer and clicking "Save and apply". Edit: Just some words regarding the chart, you can "zoom in" with selecting an area you're interrested in. Click and hold down your mouse button while dragging to either one side. On the right upper side, buttons will appear for paning and resetting. I don't know if the spikes are for real. The chart is based on the 'hashrate1m' value. The 5 minute values gives a much smoother result. It's up to you... |
|
|
|
Thank you guys for your pics and thanks Rich for your measurements! Always interresting to see. I am not sure about the restarts because I am rarely home to monitor it
For addressing the random restart bug, I'm programming some stats about every single device's hashrate. Maybe we can see restarts in the charts. But how does such a restart normally occur? Will it start with mining again as soon as it's finished booting up? On Antrun.de the stats gets fetched (only) every 10 minutes, so if the device is mining again after a very short time, let's say 30 seconds, I highly doubt that we could see such restarts in the charts, as they will probably vanish in the values as "noise". The resolution is just to low.. Lowering the timeout between the refresh rounds could solve this problem. Less than a minute won't help, as the ckpool stats itself gets refreshed every minute (I think?). And we have to keep an eye on the traffic to the ckpool. Edit: Why don't you install a script on a second computer in your network, send pings to the R1 every couple seconds and log about it? |
|
|
|
|
{"hashrate1m": "53T", "hashrate5m": "48.2T", "hashrate1hr": "42.1T", "hashrate1d": "17.8T", "hashrate7d": "3.41T", "lastupdate": 1461236027, "shares": 505947308, "bestshare": 2.111.866.006.674227, "bestever": 2111866006}
|
|
|
|
I have just run RichBC 2 at 275MHz for nearly an hour without any restarts. 15.1GH/s, Core Voltage set to 0.68v. Had a single hardware error, so not bad. Am going to turn it back down to 250MHz for overnight and am then away for a few Days, so will leave it down as I prefer to be here when it's being pushed. However bodes well for the future, 300MHz here we come. Rich Not sure what is going on with elokk, but when checking my hash his seems very high? So either he is pushing things as well or there is a problem? Like to see people tweeking this little bastards towards their limits Would be nice if you could post some power and temperature measurements. Yes, the hashrate seems to be very high, at least for a non (heavily) overclocked R1. I'm sure elokk can clarify this. |
|
|
|
What your thinking on graphs? Individual graphs or a single graph with every one on it? I would quite like to see a Hash rate graph, particularly as my miner restarts so frequently. The best share perhaps does not seem dynamic enough to warrant a graph?
I think hash rate graphs could be useful, but like Rich said I don't think a graph of best shares would really convey anything meaningful.
I made an example chart out of test data: http://m.imgur.com/E8H4uiPTurns out all racers on one chart gives no advantage. Even without the spikes eliminated. Too much lines with almost identical values, not enough colors to represent each racer individually. It gets worse as more players join... My suggestion: One chart on the front page (or no chart at all) with one value line. Overall hashrate seems to be the most interresting parameter here. Second, if you click on a racer's name, it will open the stats of all workers of that racer in a new tab. Thoughts? Suggestions? |
|
|
|
OK I have pushed RichBC 2 up to 250Mhz, switching off the wireless seems to have helped with restarting, which happens every 30 Minutes or so. Not quite sure why this should help, but assume the processor has more time for hashing? I am next going to disable the U3 / Compac support to see if that helps some more? The pull down menu for frequency setting might need to be extended.... Rich Hehe, extending is not a problem Just tell me the steps i should add, as they are not round numbers. If I would integrate graphs into the site, which info would you guys want to see? Hashrate 1m over one day? Or bestshare, so that changes in the ranking would be visible longer? Would like to hear your opinions. |
|
|
|
Imagine if our R1 Race, is renamed to "Small Miner Race" - R1 and Gekkos.... I wonder if a few R1 performs better than Gekkos? Yeah, I was thinking about this too. Just a single-chip-device-run. But to keep it separate has it's own allure. |
|
|
|
ich frag "citronick" noch ob er die 0,5 BTC zurück will oder mit 5 THs bei uns einsteigt....
Also sobald ich ein Feedback habe gebe ich bescheid...
Da wäre nice. Die Coins von dir und cagrund sind ja schon auf dem Weg/am Ziel. Dann könnten wir ja evtl. bereits heute Abend starten  |
|
|
|
Wir werden nie eine Punktlandung schaffen, ich hab jetzt mal stand gestern die 0.003 BTC pro THs und Tag angenommen und die plus die 3% zahlen wir ein. Wenn wir glück haben reicht es 35 Tage, wenn wir pech haben und der Preis steigt, reicht es 25 Tage Werden wir dann sehen. Wenn wir starten poste ich mal ein Bild / Text von der Order dann seht ihr es wie viel als Fee draufgegangen ist und wie viel wir als Rental verwenden (plus ab und zu mal ein Bild von der Order wie der Speedverlauf ist... Viele Grüße Willi PS: Ich finde die Longtime Race voll geil, hoffen wir das unser BestShare nicht im Keller kleben bleibt PPS: das Datum 1.5. ist nur eine Annahme, wir starten auch gerne schon heute Abend ;-) Super, so machen wir das. Melde mich, sobald die Coins unterwegs sind. |
|
|
|
Very nice to see that list growing. Already 20 racers! We should do such a run for Gekko Compacs too |
|
|
|
|
Hallo Willi
Danke für die Infos wegen den Fees.
Wie wollen wir das machen mit dem Einzahlen? Du hast ja jetzt einen ungeraden Betrag einbezahlt. Evtl. steigt der Kurs ja aber auch noch etwas an bis zum Ende des Monats.
Wäre es nicht am einfachsten, wenn jeder runde Beträge einbezahlt (5 TH = 0.5 BTC, 10 TH = 1 BTC)? Oder legen wir nach, falls wir nicht auf insgesamt 30 Tage kommen sollten?
Ich schicke meinen Coin am Abend auf die Reise.
Einen schönen Tag wünsch ich euch.
Gruss
minibit
|
|
|
|
v13 is now online
Trend-Arrows are now working and it looks great :-)
Frequency-Change now works with BTC-Adress only - no worker extension needed
Have fun and thanks for being part of antrun.de
If you have more than one device, you have to insert the btc address with worker extension. |
|
|
|
|
Show Posts
