Anonymailer (OP)
|
|
May 09, 2014, 01:22:35 AM |
|
The RemoteCommands endpoint should also be passed a MachineName on the QueryString: http://www.mobileminerapp.com/#api{Root URL}/RemoteCommands?emailAddress={Email Address}&applicationKey={Application Key}&machineName={Machine Name}&apiKey={API Key} Whoops, sorry! I think you should notify people of this Nate, I only just changed this the other day as the email you sent on the 5th said "You should no longer send the MachineName as an argument in the URL query string. Instead you should provide the MachineName on the JSON object you are sending via HTTP POST." In retrospect obviously this didn't apply to the commands - I'll fix ASAP!
|
|
|
|
nwoolls
|
|
May 09, 2014, 03:24:08 AM |
|
The RemoteCommands endpoint should also be passed a MachineName on the QueryString: http://www.mobileminerapp.com/#api{Root URL}/RemoteCommands?emailAddress={Email Address}&applicationKey={Application Key}&machineName={Machine Name}&apiKey={API Key} Whoops, sorry! I think you should notify people of this Nate, I only just changed this the other day as the email you sent on the 5th said "You should no longer send the MachineName as an argument in the URL query string. Instead you should provide the MachineName on the JSON object you are sending via HTTP POST." In retrospect obviously this didn't apply to the commands - I'll fix ASAP! Good call - I'll send out a note. The change was specifically about the "Statistics API" but, in hindsight, that's not super clear. The change is only for that specific endpoint.
|
MultiMiner: Any Miner, Any Where, on Any Device | Xgminer: Mine with popular miners on Mac OS X
|
|
|
Anonymailer (OP)
|
|
May 09, 2014, 01:44:08 PM |
|
Good call - I'll send out a note. The change was specifically about the "Statistics API" but, in hindsight, that's not super clear. The change is only for that specific endpoint.
Yeah, I should have checked the website, sorry about that! A fixed version is out now, tested a little better This version also adds a Gridseed setting to CPU miner so those gridseed owners who've been using that should either switch to bfgminer with GPU window (recommended) or change the CPU miner settings from scrypt (Litecoin etc.) to Gridseed (scrypt)
|
|
|
|
Anonymailer (OP)
|
|
May 12, 2014, 08:01:10 PM |
|
1.5.20 updated to a final hopeful most stable version and beta versions will resume shortly. This is a bug fix release for two known issues.
|
|
|
|
Anonymailer (OP)
|
|
May 13, 2014, 11:45:50 PM |
|
There is an incredible 200Gh BTC Mining and 24Mh LTC mining still going on on the old pool server - if that's you, and your address isn't showing up at pool.fabulouspanda.co.uk on the relevant graphs page - please restart your miners!
|
|
|
|
DanZaph
|
|
May 17, 2014, 10:59:59 PM |
|
1.5.20 updated to a final hopeful most stable version and beta versions will resume shortly. This is a bug fix release for two known issues.
I tried 1.5.20gm and it does not work with a BFJ Jalapeño and a ASCI Block Erupted cube. Just moving back to 10.5.18e does work. No need to fix for me.
|
|
|
|
Anonymailer (OP)
|
|
May 24, 2014, 07:41:23 AM |
|
I think there are some problems with the representation of what's going on under the hood in the latest MacMiner, please be sure to give it a minute and check the API output window to see whether that's the issue!
|
|
|
|
Anonymailer (OP)
|
|
May 27, 2014, 02:29:57 AM |
|
1.5.21b1 is up now which mostly just updates bfgminer to the long awaited version 4
|
|
|
|
DanZaph
|
|
May 29, 2014, 08:47:19 PM |
|
1.5.21b1 is up now which mostly just updates bfgminer to the long awaited version 4
I have been mining fine with MacMiner 1.5.18e, ASIC Block Erupter Cube and BFL Jalapeño. Just updated to MacMiner 1.5.21b1 and it does mine, takes about 3 minutes to get started, if it starts, but there is no display of hash rate Accepted to Rejected. I am using the BTC Guild pool. I don't see any advantage to update. What am I missing? What can I do to help get this resolved. Is there a way to see the actual BFGMiner, CGMiner and CPUMiner command string sent so I can verify direct operation?
|
|
|
|
Anonymailer (OP)
|
|
May 29, 2014, 09:10:36 PM |
|
1.5.21b1 is up now which mostly just updates bfgminer to the long awaited version 4
I have been mining fine with MacMiner 1.5.18e, ASIC Block Erupter Cube and BFL Jalapeño. Just updated to MacMiner 1.5.21b1 and it does mine, takes about 3 minutes to get started, if it starts, but there is no display of hash rate Accepted to Rejected. I am using the BTC Guild pool. I don't see any advantage to update. What am I missing? What can I do to help get this resolved. Is there a way to see the actual BFGMiner, CGMiner and CPUMiner command string sent so I can verify direct operation? There are definitely issues with the stats reporting in the miner window although what I'm seeing isn't as bad as what you are it is due to be replaced when I have time, sorry about that! The main change is in the backend as bfgminer has been updated to version 4 - I wonder whether the cube you have has something to do with the difference in what we're seeing as I don't have one, but am using a jalapeño. The only way to check the actual command right now would be to check the source code - I'll consider that a feature request and feed it out to the log! The actual commands are as simple as possible, they load the conf file and any manual flags set, if a device is selected it'll use something like -S bfl:all with the relevant device inserted. It could be worth running with the bfgminer 4 included in the latest version at the command line and comparing that to the .18e version?
|
|
|
|
kinless
Newbie
Offline
Activity: 1
Merit: 0
|
|
May 29, 2014, 10:36:45 PM |
|
Hey y'all,
Newbie miner here. I just got set up with the latest Mac Miner beta (1.5.21b), using the standard Fabulous Panda server for BTC mining. Running on a 2008 Mac Pro using just the CPU Miner (minerd) at a seemingly speedy 3500 khash/s x 8 cores. So it appears to be working...
My only question, in the CPU Miner window, after it's been running for a while (up to an hour), the big number at the top stays at {0}KH and the status is stuck on "Starting..." even after I eventually stop the mining process. From the other miner windows, I would think there should be some Accepted/Rejected stats, but it never displays any of that. Is the Accepted/Rejected numbers relevant to the CPU Miner method? I couldn't find anything on the usual FAQ pages to address this. I just want to make sure all this CPU grinding is actually doing something useful.
Thanks.
|
|
|
|
Anonymailer (OP)
|
|
May 29, 2014, 11:06:06 PM |
|
Hey y'all,
Newbie miner here. I just got set up with the latest Mac Miner beta (1.5.21b), using the standard Fabulous Panda server for BTC mining. Running on a 2008 Mac Pro using just the CPU Miner (minerd) at a seemingly speedy 3500 khash/s x 8 cores. So it appears to be working...
My only question, in the CPU Miner window, after it's been running for a while (up to an hour), the big number at the top stays at {0}KH and the status is stuck on "Starting..." even after I eventually stop the mining process. From the other miner windows, I would think there should be some Accepted/Rejected stats, but it never displays any of that. Is the Accepted/Rejected numbers relevant to the CPU Miner method? I couldn't find anything on the usual FAQ pages to address this. I just want to make sure all this CPU grinding is actually doing something useful.
Thanks.
Hey, The problem you're having is that the share difficulty for BTC relative to the power of any CPU these days means that you're solving work so slowly statistics can't be generated by the usual means - you'd be better off mining something like Vertcoin!
|
|
|
|
Anonymailer (OP)
|
|
June 05, 2014, 07:19:12 PM |
|
You may have noticed Apple's release of a new programming language called Swift. I'm going to be exploring moving MacMiner over, so in the meantime you can check out 'SwiftMiner' - right now I'm cheating and incorporating a lot of Obj-C code in a Swift app, but I'll be changing that very soon and this may be of interest as a very basic bfgminer GUI http://downloads.fabulouspanda.co.uk/SwiftMiner.app.zipAs essentially a version of MacMiner without any features, SwiftMiner currently uses less system resources than MacMiner.
|
|
|
|
jedimstr
|
|
June 09, 2014, 02:23:25 AM |
|
Any chance of getting a version of cpuminer included that supports X11? The 3 git repositories I found with various X11 versions of minerd aren't compiling correctly for me on my Mac and can't find any binaries anywhere.
|
|
|
|
Anonymailer (OP)
|
|
June 09, 2014, 03:50:44 PM |
|
Any chance of getting a version of cpuminer included that supports X11? The 3 git repositories I found with various X11 versions of minerd aren't compiling correctly for me on my Mac and can't find any binaries anywhere.
Can you relink me please? I was going to take a look at the kernels as no-one is having any luck compiling for Mac - I'm a bit broke and busy atm but I'll hopefully give it a shot this evening if I get the chance!
|
|
|
|
jedimstr
|
|
June 09, 2014, 07:17:27 PM |
|
Any chance of getting a version of cpuminer included that supports X11? The 3 git repositories I found with various X11 versions of minerd aren't compiling correctly for me on my Mac and can't find any binaries anywhere.
Can you relink me please? I was going to take a look at the kernels as no-one is having any luck compiling for Mac - I'm a bit broke and busy atm but I'll hopefully give it a shot this evening if I get the chance! Here are the two most popular ones: For AES-NI supporting processors: https://github.com/elmad/darkcoin-cpuminer-1.3-avx-aesFor other processors: https://github.com/ig0tik3d/darkcoin-cpuminer-1.2cThis is an older version that some have gotten further with on a Mac: https://github.com/ig0tik3d/xcoin-cpuminerI haven't seen any proof that anyone with a Mac has gotten any of these builds running. I certainly haven't and after hours trying to compile these myself I'm throwing up the white flag. I hope you have more luck.
|
|
|
|
Anonymailer (OP)
|
|
June 11, 2014, 08:34:47 AM |
|
I went at the most recent project expecting to run in to the same kernel issues as before, but it seems to have compiled without issue! I ran a quick test with a dark coin p2pool node but didn't check on any stats on the pool end. It seemed to be solving shares fine, started like so ./minerd -o http://drk.p2pool.n00bsys0p.co.uk:7903 -u test -p test -a X11 Chuck this in any existing MacMiner.app (keeping the base x11cpuminer directory in the Resources folder) http://downloads.fabulouspanda.co.uk/x11cpuminer.zipLet me know how you get on!
|
|
|
|
jedimstr
|
|
June 12, 2014, 04:23:29 AM |
|
I went at the most recent project expecting to run in to the same kernel issues as before, but it seems to have compiled without issue! I ran a quick test with a dark coin p2pool node but didn't check on any stats on the pool end. It seemed to be solving shares fine, started like so ./minerd -o http://drk.p2pool.n00bsys0p.co.uk:7903 -u test -p test -a X11 Chuck this in any existing MacMiner.app (keeping the base x11cpuminer directory in the Resources folder) http://downloads.fabulouspanda.co.uk/x11cpuminer.zipLet me know how you get on! Thanks, but that means it will only work correctly for more recent Mac's using i5 or i7 chips due to the use of AES-NI if you used the most recent version 1.3, so if you ever include that with the core build of MacMiner, you may want to make note of that.
|
|
|
|
Anonymailer (OP)
|
|
June 12, 2014, 07:42:37 AM |
|
Thanks, but that means it will only work correctly for more recent Mac's using i5 or i7 chips due to the use of AES-NI if you used the most recent version 1.3, so if you ever include that with the core build of MacMiner, you may want to make note of that.
Are you sure it's only supposed to work with those processors, or whether it's optimised for AES-NI? My test was on an aluminium Mac Pro and it seemed to mine fine so I wonder whether it works without that optimisation on other machines…
|
|
|
|
|
|