Request MacMiner support for OSX Mavericks 10.9.1

DocGamboa1 . · February 2014

Can someone give some assistance, I'm running OSX Mavericks 10.9.1 and MacMiner 1.5.17 (1517c), I download the zip file and added it to my applications folder because when I initially ran it, it ran but when I tried running it in FPGA/ASiC, it tried running but gave a statement that no such file existed. I've tried everything..Can someone assist?

[2014-02-19 17:32:16] /Applications/MacMiner.app/Contents/Resources/bfgminer/bin/bfgminer: -c: JSON decode of file '/Users/Library/Application Support/MacMiner/bfgurls.conf' failed

unable to open /Users/Library/Application Support/MacMiner/bfgurls.conf: No such file or directory

FabulousPanda · February 2014

That file is created when you set up a bitcoin pool in the Preferences window found in the MacMiner menu at the top of the screen. What ASIC are you using?

DocGamboa1 . · February 2014

@ FabulousPanda - I'm using 3/1.6 Gh/s Antminers and 2 356 Mh/s Blockerupter.

FabulousPanda · February 2014

Cool, is it all working fine? Did you install the silabs serial usb driver?

DocGamboa1 . · February 2014

@ FabulousPanda - Damn..This is crazy, I was going to answer you question on my set-up in Preferences which I had already done initially and couldn't understand why it wasn't running and giving me that message but then something told me to take the Http:// out and low and behold. It works!!

Now I want to over clock my Antminers and BlockErupters. Please assist if you can. Thanks a million!

FabulousPanda · February 2014

That's weird, maybe there was a space or some other special character in there?

In the miner settings panel for ASIC window put this in the manual flags:

--set-device antminer:clock=x0781

change the end to 0881 or 0981 to over clock higher but make sure to cool it properly!

FabulousPanda · February 2014

*Meant to say you can't over clock BE unfortunately, not without desoldering and resoldering anyway!

DocGamboa1 . · February 2014

@ FabulousPanda - Awesome.. Are are the relative hash rates for the clock rates you gave, 0881 and 0981?

FabulousPanda · February 2014

This is what is supposed to happen, but it seems to always be fairly close to 2GH regardless, just minor changes in reality:

For 1.6 GH/s, use 0781 (this is the default)
For 1.8 GH/s, use 0881
For 2.0 GH/s, use 0981
For 2.2 GH/s, use 0A81

DocGamboa1 . · February 2014

@ FabulousPanda - Again, awesome..But I have another problem because I've been running my miner for about 15 mins., it's hashing away, showing accepted shares on the miner but when I log onto the pool website, it shows accepted shares but not posting unconfirmed rewards as it was doing before with other miners. It's almost as if I'm just hashing and nothing happening.

FabulousPanda · February 2014

If you start the miner again does the beginning of the log look as though it's connecting to the pool correctly? I'm guessing maybe it's just not long enough to show the unconfirmed reward yet, if it's showing accepted shares and the expected hash rate.

DocGamboa1 . · February 2014

@ FabulousPanda - It appears to be connected correctly because it shows the shares receiving but it doesn't show the unconfirmed rewards as it has before with other miners. Also, is the over clocking of the ant miners permanent until changed or does it revert back to default when and if you use another miner? How do you know if the over clock took effect because it's kind of hard to tell because the hash rate fluctuates in the window?

FabulousPanda · February 2014

Do you know how long it took to show unconfirmed rewards before? What pool is it? The over clock is just for the session you're running. I guess the best way to see if it works is to get the average speed over time from the pool - it seems to go from 1950MHish to about 2100MH at 0A81 so it definitely doesn't match what it's said to be doing.

DocGamboa1 . · February 2014

@ FaulousPanda - I'm using SlushPool, I restarted the miner and still not posting in "unconfirmed reward" as it has in the past with other miners, giving it a bit of time to see if that's it. Also, in the string you gave me for the over clocking, is the "X" before the numbers necessary because I've seen this used as well?--set-device antminer:freq=0781

FabulousPanda · February 2014

Does it say how long the average round time is? It won't show unconfirmed rewards till a round is finished. It's been a while since I used slush though.

The without the x was from nwoolls' branch of bfgminer before it officially supported antminer, if you run without the x now you'll get this:

AMU 0: Applying rule antminer:clock=0781: invalid clock: '0781' data must be prefixed with an x

DocGamboa1 . · February 2014

Slush Pool current round is at 4:43:14, and I've been logging on and off trying to get this to work properly. Thanks for the input on the "x" factor, you're Fabulous man.

FabulousPanda · February 2014

If that means 4 hours I guess you have a little time to wait for unconfirmed rewards - Thanks Doc

DocGamboa1 . · February 2014

Okay, I will wait and see what happens. By any chance, is there a way to permanently over clock the ant miner so that you don't have to do it per session and use it on multiple miners?

FabulousPanda · February 2014

I'm afraid not, but MacMiner will remember for you

Howdy, Stranger!

Quick Links

Categories

Request MacMiner support for OSX Mavericks 10.9.1

Comments

Leave a Comment