Terk, thanks for settling the score of the unexchanged balance. I had figured that was just coins that had died but glad to see that there is progress to be made there. Perhaps it's less of an issue to me because my balance stuck unexchanged is literally just .002. So. Not too concerned about $0.90 Even though I dont have volt-modded Gridseeds, I have over-clocked them, and one of them gave 0 hardware errors at 950, so...it would do me well to be able to target individual units for specific clock speeds, or, as you suggest, use auto-tuning software.
Not only can you target individual units with a clock speed, you can target individual CHIPS within those units with a clock speed. If you run the autotune, you can get the results per chip from the API. If you're comfortable mucking around with some basic PHP, here's a script that will, based on autotune results, give you a command line string to start up your miner with the per chip settings. https://bitcointalk.org/index.php?topic=482352.msg6603449#msg6603449 |
|
|
|
|
Confirmed 3x on my end. Apologies for feeding the trolls.
|
|
|
|
The transaction fee setting in our client software wasn't adjusted properly for the chunk size and so we are lower priority in the blockchain right now. You will all get your payments, it will just take a few hours  This is one of the many reasons we get started with the process early in the day. Thanks for the update. As long as the payment clears by midnight there are zero complaints from me. |
|
|
|
I have been mining with Gridseeds, run by PC, using bfgminer.
Now I am trying to learn to mine using Raspberry Pi.
I have tried the GAWminers img, and the Zoomhash img, and I have built several Raspbian Wheezy systems myself. I have tried installing a python stratum proxy. I have used cgminer and bfgminer. I get the same results no matter what I do:
I connect to a pool, I get no Accepts. (I have tried various pools, including this one, but I mainly use a different pool so I can watch my dashboard on it to see hashrate...)
I restart the miner, sometimes I get one (1) Accept, then no more.
One time, using cgminer, I got quite a few Accepts in a row. In fact, I got 32 Accepts each time my work was accepted. When the number of Accepts got to 1072, it stopped. (I realize 1072 is not a multiple of 32, I'm just telling the truth...)
I am not looking for anybody to help me debug and such, I am just hoping that my situation rings a bell with you.
Try Minera which uses Sandor's modded, autotuning CPUminer. been using it for 3 gridseed 5chips and it's wonderful. |
|
|
|
I use standard bitcoin-qt wallet i see the payament but unconfirmed too by quite 2 hours, but new blocks in the blockchain were found between the announcment and now.... something wrong with the pbmining tx ?
Looks like this might be a little stingy on the transaction fee again.... We had that issue before. If it doesn't confirm by midnight I trust your previous compensatory offer stands? I sure hope it confirms today I wanted to order some gridseeds with that... |
|
|
|
|
This is great!
All sandor's wonderful branch of CPUminer was missing was a web interface and this is really spectacular.
I'd love to see a reading of the raspberry pi temp on there. Just gives me an approximation of the ambient temp near my rigs.
Thanks mate.
--Jon
|
|
|
|
I've been using auto-tune on a test rig for a few days and it's been rock solid. Thanks so much to Sandor for all the hard work. This is really shaping up to be the best mining software for GSDs out there. As I understand it, I can harvest the auto-tune results of per chip frequency values from the API. I can use toxic0n's PHP script to do that. But it looks like the frequency specification is on a per device node basis. I suspect that the dev nodes can change when rebooting, or if you add or remove GSDs. It seems to me that in order to really make auto-tune useful, you need to be able to specify the frequencies on a per serial number basis, not per device node. And as cool as toxic0n's script is, I think that cpuminer should output the results of auto-tune so that it can be easily used for future launches. So here's the features that I'd like to see to round out auto-tune: - Add something in the main GUI indicating the status of auto tune. It would be nice to have an idea of how far it has to go without using the --debug option and scanning the log output.
- Add the option to specify the frequency by GSD serial number so that it will always work for known units, regardless of the order of device discovery.
- When quitting cpuminer and autotune is done, output the command line options that could be used in subsequent launches. Ideally this would be the serial number based frequency specification.
Sandor, thanks in advance for thinking about these features. Thanks for the suggestions. The JSON array has the dev node as key, but serial string is included as one of the values, so you can compare against that. I think it would also be helpful if you could specify the autotune start frequency per-device. I don't know how feasible this would be but this would help minimize any inefficiency caused by the auto tune process, and I think it would also help to get more accurate tuning. |
|
|
|
|
did you try just sudo reboot?
|
|
|
|
How do I contact the guys at cleverming for problems?
Terk, the admin, checks in on this thread so it's one place to start. You could also try twitter: https://twitter.com/CleverMining |
|
|
|
|
I'll let it keep running for a while but methinks autotune is not working in this build. An hour and all the cores still at baseline... Lets see what happens overnight.
EDIT: The exact second I post this, boom: [2014-05-08 23:32:41] 0@1: Set GC3355 core frequency to 875Mhz
Disregard.
|
|
|
|
anyone mining on here with volt-modded gridseeds using hashra?
I was using hashra, but i'm using Sandor's modded CPUminer with autotune. Always hashes faster than hashra. |
|
|
|
You know, I'm frustrated with the delays - frustrated as all hell just like the rest of us. But honestly? 150W for 120GH is pretty palatable. It's barely above the power consumption of the antminer S2 - and I don't doubt that these numbers can be improved upon. The compensation package for batch one should be 2x the units. No question about that. I can get a 180gh antminer for less than what I paid for this 100gh x1. Hell - I already did. But like, the power consumption seems pretty decent and I bet the final numbers will be better S2 is $2500 for 1th or $2.5/gh
BA is $6000 for 3.6th or $1.7/gh
Where the hell are you getting that 3.6th number from? Didn't they say they've got 120gh a chip? The x3 would get 2400th in that case, no? $2.5/gh in that case..... |
|
|
|
depends what is your btc balance needs to be at min .01 for automatic withdraw to work..
Icon
The second I posted I got a payment, Yes I was well over the 0.01, Not sure what the delay was. I've seen this too, here's my two cents - for whatever reason their autopayouts are at "arbitrary times" - so if you hit .01 just after the cutoff one day and then the next day the payout is much later in the day - you can theoretically spend about 47 hours above the threshold with no payout. |
|
|
|
You just need a webserver with php installed and put that script in your /var/www directory and give it a .php extension sudo apt-get install lighttpd php5-cgi
sudo service lighttpd force-reload By the way in case anyone gets a 403 error right off the bat accessing the PHP you might also need to enable cgi sudo lighty-enable-mod fastcgi
sudo lighty-enable-mod fastcgi-php
sudo service lighttpd force-reload
That made it work for me! |
|
|
|
I didn't want to do autotune every time the miner restarted and manually entering the values every time was tedious. For some reason, the device names changed after upgrading the miner version.
I wrote a little PHP script that will query all the frequencies for the chips and format them into a command string to use with cpuminer. Now I can just wait for the autotune to finish and then copy and paste the output into the command string.
Wow, that's neat. But I have a couple of questions. How can you tell when the auto tune process is complete? Never mind. Looks like you have to pass the --debug option. Does any other factor affect auto-tuning, like a coin switch on a multi-pool? I'm just wondering if it makes sense to bypass auto tuning in all cases, or if it's better to leave it on and let it react to pool changes. Sorry in advance if I don't understand how the auto tune feature really works. Auto tune isn't going to affect or be affected by any pool changes - all it's really doing is optimizing the settings for your specific hardware, and those settings will be the same regardless of pool or coin. Basically, each gridseed chip on the miner can be told to run at a different rate. Higher rates mean more hashpower, but too high for the chip and you'll just get errors and not actually see any results for your hashpower. The simplified explanation of how auto tune works is it slowly increases the operating speed of each chip until it starts to see errors and then backs off a bit until the error rate is stable. The result is your hardware will be operating at the highest speed it is capable of without producing errors. I thought it was a gimmick when I first started using it - my miner would autotune and stay at 850 where i started it - BUT when I bought two more, one comfortably runs at 930-950 sometimes nudging above 400kh. Go figure. Anyway - once you autotune once, the numbers per device and chip are basically established and aren't going to really change boot to boot. The idea is by starting with those instead of autotuning, you aren't wasting time running at subprime efficiency until the tuning process completes. |
|
|
|
Serial string is added to display when built from the last commit.
Nice! I was going to suggest that feature. Thanks mate. |
|
|
|
Today we have confirmed 85Ghash per chip on the the 140A board.
We have scheduled to assemble the 200A board tomorrow at the SMT factory.
Not bad, Glad to hear it. Hope you can start shipping soon! |
|
|
|
|
I have a card for 1.4 but I wasn't running it because I have one gridseed that runs well at 1000mhz while the rest need 850 - so I was using an auto-tuning image to achieve that.
Now that hashra supports per-device speed I'll give it a shot but I was hoping to set up the card before even booting it. Not a big deal though! Thanks.
|
|
|
|
|
Is there a D/L link for 1.4.5 anywheres?
|
|
|
|
I tried this to start the good miner on a higher frequency, but when I loaded the TUI they all still showed 850mhz sudo screen -dmS 0 ./minerd-gc3355 --gc3355=/dev/ttyACM0,/dev/ttyACM1,/dev/ttyACM2 --gc3355-freq=/dev/ttyACM0:1000 --gc3355-autotune --freq=850 --url=stratum+tcp://useast.wafflepool.com:3333 --userpass=redacted:pass Im thinking that the --freq flag overrides the -gc3355-freq flag? I thought the more specific one wins in that fight but should I try this instead? EDIT: This one just defaults them all to 600mhz... sudo screen -dmS 0 ./minerd-gc3355 --gc3355=/dev/ttyACM0,/dev/ttyACM1,/dev/ttyACM2 --gc3355-freq=/dev/ttyACM0:1000,/dev/ttyACM1:845,/dev/ttyACM2:855 --gc3355-autotune On which version is that? It always picks the most specific frequency, works fine here. Raspberry Pi, 0.9d. I guess I should probably update to 0.9e and retest but I thought the only update there was for blades. Edit: Same behavior on 0.9e. |
|
|
|
|
Show Posts
