The official MacMiner thread [BTC/LTC-CPU/GPU/FPGA/ASIC]

[BrandonMcPherson]

I'll take a look at the bfgminer output and see what I can do about having it say which specific pool is being used at any one time, hopefully that won't be a problem!

Thanks for considering it.

Shame about the Mh problem, I guess luke-jr wasn't really expecting people to be dealing with such low speeds any more..

Ouch! The truth hurts.

And yeah, that's a great point. The days of a KHash mattering even in scrypt mining are all but gone.

[XFox]

I have a Mac mini with a GeForce 320M… so it's actually quite hard to tell if the noise comes from the HD or GPU!
Nevertheless, I've just noticed that the buzz is emitted only if I check the Dynamic Intensity option.
When I uncheck that option I don't hear the buzz anymore, even if I set Intensity to a high value (for my machine), such as 4 or 5.

That's really strange, I'm not sure why it would be doing that! Are the noises more like fan noise or revving/clicking type noises (which come from HDD)?

It seems to me more like an HDD noise but I used sar to monitor disk I/O and I hear the buzz even when the "r+w/s" value is zero. I have to conclude that it comes from the GPU. That's not too bad, I'll stick with a set Intensity and let it go. Anyway, thank you very much for your interest!

[Anonymailer]

How odd. Well, a set intensity is probably a good way to go regardless!

1.4.24 is out now which updates cgminer to 3.8.4 but leaves bfgminer at 3.6 due to a bug in 3.7 and 3.8 with the little fury driver.

This release also fixes up the Add Networked Miner part of API Output to function properly, if still only for a single networked miner/computer. Anyone using that, let me know how you get on please!

[XFox]

1.4.24 is out now which updates cgminer to 3.8.4 but leaves bfgminer at 3.6 due to a bug in 3.7 and 3.8 with the little fury driver.

This release also fixes up the Add Networked Miner part of API Output to function properly, if still only for a single networked miner/computer. Anyone using that, let me know how you get on please!

What's happened to 1.4.23?
Anyway, 1.4.24 crashes at startup on my machine (Mac OS X 10.7.5).
Reading the crash log I noticed this error message:

Dyld Error Message:
  Library not loaded: @loader_path/../Frameworks/Sparkle.framework/Versions/A/Sparkle
  Referenced from: /Applications/MacMiner.app/Contents/MacOS/MacMiner
  Reason: image not found

[Anonymailer]

1.4.24 is out now which updates cgminer to 3.8.4 but leaves bfgminer at 3.6 due to a bug in 3.7 and 3.8 with the little fury driver.

This release also fixes up the Add Networked Miner part of API Output to function properly, if still only for a single networked miner/computer. Anyone using that, let me know how you get on please!

What's happened to 1.4.23?
Anyway, 1.4.24 crashes at startup on my machine (Mac OS X 10.7.5).
Reading the crash log I noticed this error message:

Dyld Error Message:
  Library not loaded: @loader_path/../Frameworks/Sparkle.framework/Versions/A/Sparkle
  Referenced from: /Applications/MacMiner.app/Contents/MacOS/MacMiner
  Reason: image not found

Thanks for pointing that out! I skipped .23 due to the stigma of the number 23 - I'm not a weird numbers person or anything and don't skip 13 but I figured I'd skip 23 for good luck - and it ends up having some weird compile time issue like that! 1.4.25 is the same version, archived the same way, but... working this time...

Let me know how you get on with that network miner

[Anonymailer]

After another person getting in touch it seems to be a problem with the update mechanism rather than the file itself - If you experience this problem please download MacMiner directly from http://fabulouspanda.co.uk/macminer/

edit:

It turns out the problem is that I had to change the way the Sparkle framework was signed after updating the developer environment to 10.9 and this means that users of up to and including version 1.4.22 will have to download the next version directly from the website. Very sorry about the hassle!

Now I know why Panic software's Transmit had the same problem recently!

[XFox]

It turns out the problem is that I had to change the way the Sparkle framework was signed after updating the developer environment to 10.9 and this means that users of up to and including version 1.4.22 will have to download the next version directly from the website. Very sorry about the hassle!

Just to let you know, my 1.4.22 (on Lion) updated just well to 1.4.25 with the automatic update function.

Let me know how you get on with that network miner

I'll try it tomorrow and let you know how it goes!

[BrandonMcPherson]

The automatic updater worked for me, too, BitBacco. Just FYI.

[Anonymailer]

Huh, I guess it remains a mystery. Thanks for the reports guys, please let me know if you do have the issue in any future updates…

[XFox]

I'll try it tomorrow and let you know how it goes!

No way, I've not been able to add a KnCMiner Mercury to the API Output window as a networked miner.
I have these lines in the cgminer configuration file on the miner:

Code:

  "api-listen": true,
  "api-allow": "W:0/0"

When I try to add the miner by IP or DNS name, nothing happens in the API Output window.
Should I see an error when it fails? Is there a log I can check?

[Anonymailer]

I'll try it tomorrow and let you know how it goes!

No way, I've not been able to add a KnCMiner Mercury to the API Output window as a networked miner.
I have these lines in the cgminer configuration file on the miner:

Code:

  "api-listen": true,
  "api-allow": "W:0/0"

When I try to add the miner by IP or DNS name, nothing happens in the API Output window.
Should I see an error when it fails? Is there a log I can check?

Huh that's no good, my config is like this
{
  "pools": [
    {
      "url": "http://pool.fabulouspanda.co.uk:9332/",
      "user": "yes",
      "pass": "indeed"
    }
  ],
  "api-listen": true,
  "api-allow": "W:0/0"
}

and if I add the IP 192.168.1.99 (where the miner is) and the port 4028 it works - did you enter the port? In future it will default to 4028 but right now it only works entered manually

The only place something might show up if not in the table is at the bottom of the log below where the verbose output might be showing up…

[XFox]

I have these lines in the cgminer configuration file on the miner:

Code:

  "api-listen": true,
  "api-allow": "W:0/0"

When I try to add the miner by IP or DNS name, nothing happens in the API Output window.
Should I see an error when it fails? Is there a log I can check?

Huh that's no good, my config is like this
{
  "pools": [
    {
      "url": "http://pool.fabulouspanda.co.uk:9332/",
      "user": "yes",
      "pass": "indeed"
    }
  ],
  "api-listen": true,
  "api-allow": "W:0/0"
}

Yes, mine has the same structure, I've only omitted the non relevant parts.

and if I add the IP 192.168.1.99 (where the miner is) and the port 4028 it works - did you enter the port? In future it will default to 4028 but right now it only works entered manually

Yes, I manually entered the port, without success.
I also entered the IP but could I enter the DNS name as well?

The only place something might show up if not in the table is at the bottom of the log below where the verbose output might be showing up…

I don't see any messages in the log.
I'll try again in the next days.

[Anonymailer]

I don't see any messages in the log.
I'll try again in the next days.

I'm aware of a bug where not normally formatted output can cause a freeze in refreshing the networked miner data, maybe that could have caused it? If that was the case restarting MacMiner should make it start showing up. Hopefully I'll have it worked out in the next version!

[XFox]

I noticed some contrasting information on the first post of the thread.
First you say:

The 1.4 branch updates bfgminer, cgminer and cpuminer to the latest version and allows it to work regardless of where MacMiner is on your system or what it's called

Then:

MacMiner MUST be in your Applications folder and named MacMiner.app to function properly

On another note, I'm using bfgminer to mine on TripleMining and I'm seeing a lot of these messages:

Code:

[2013-12-10 16:55:22] Pool 0 is hiding block contents from us
[2013-12-10 16:55:27] Pool 0 now providing block contents to us

Does anyone have a clue about what this alerts mean?

[Anonymailer]

Whoops! The next version :: should :: finish with the Applications folder requirement.

That Pool 0 is hiding block contents from us output it nothing to worry about, bfgminer constantly looks for work but pools aren't providing it constantly, they have a particular schedule.

[bitcoinmining]

thank you very much for sharing high-speed program running smoothly miner

[Anonymailer]

thank you very much for sharing high-speed program running smoothly miner

Thanks for your thanks

[Anonymailer]

1.4.26 Hopefully resolves the sometimes crashing at launch issue and

• updates bfgminer to 3.8.1 which required disabling the little fury driver (not sure fury worked in 3.6 anyway…)

• updates cgminer to 3.8.5

The MacMiner website at http://fabulouspanda.co.uk/macminer/ has been updated a bunch over the last week with a little more to come, the biggest change is the addition of forums, in not too long I'll be making a little announcement over there...

[XFox]

Hi Anonymailer,
I updated from 1.4.25 to 1.4.26 with the automatic update feature without stopping BFGMiner first and I ended up with two bfgminer processes, one of them "running in the wild" (i.e. its parent process has been changed to launchd).
It happened with the automatic update from 1.4.22 to 1.4.25, too, but I was unsure if it was reproducible so I didn't reported it the first time.
Obviously I can kill the bfgminer orphaned process using Activity Monitor but it would be nice if MacMiner would take care of the workers processes before updating itself.

[Anonymailer]

Sorry about that XFox, I'll get that fixed! On the upside, 1.4.26 should work outside the finder…

I meant to ask you, are you using FPGA/ASIC Miner window when trying to get network API output? At the moment API Output only shows up when that window is running but very soon that will be separated out.