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

[Anonymailer]

That was 3.1.1; I'm pretty sure I fixed it in 3.1.2

Awesome, I'll roll out 3.1.3, thanks!

[1714954551]

1714954551

[1714954551]

1714954551

[1714954551]

1714954551

[wlwesq]

And the weirdness returns.

Earlier, I was trying to get the two USB miners set up with BFGMiner or FPGA/ASIC. In FPGA/ASIC I included this flag:

-S /dev/cu.SLAB_USBtoUART9 -S /dev/cu.SLAB_USBtoUART

because the -S all didn't work for me.

Well, today I restart the miner and it's only finding one of the two USB devices in BFGMiner and FPGA/ASIC. I pulled the one that is working (according to the LED) just to see if the other one went bad somehow. Nope, it too gets recognized and put to work.

The Mac System Profiler shows both devices being plugged in.

For grins, I tried -S all again, got nothing. Also tried "switching" the USBtoUART9 to the second flag in the command, didn't make a difference.

Not necessarily asking for a solution here (although I wouldn't kick one out of bed), but just wanted to provide the info in case it helps anyone else fill in any blanks.

[Anonymailer]

Sorry guys I've had a little crisis IRL but I'll get to updating things today or tomorrow.

The issue you're having sounds to me like the device got a different name on reconnect or restart, it's unusual to jump from no enumeration to number 9 so I'd guess it's changed to 1 or 2.


Just paste

ls -l /dev/cu.*

in Terminal and it should show you what's connected.

[wlwesq]

Now this is interesting.  When I paste ls -l /dev/cu.* into Terminal, it shows that I have a Bluetooth modem and a Bluetooth-PDA-Sync device attached. No Icaruses. Yet the miner is running one of them quite nicely.

[Anonymailer]

That is very strange. Does your account have admin privs? Maybe try adding sudo before ls -l /dev/cu.*

It's also worth running

sudo ls -l /dev/*

as it'll show up under another prefix, but you'll get a long list of stuff with that command!

[iamnightelf]

it's my understanding that cgminer has autodetect and will mine on the block erupters without drivers installed (at least that was my experience) so that probably explains how yours did too. BFGMiner will require drivers and flags to locate the miners.
Macminer uses BFG miner version 3.1.1 (which is a pain in the arse and should really be updated to version 3.1.3 asap). I personally run BFG miner 3.1.3 (command line from the terminal) with my erupters with great success but it required some extra steps to install properly.

Assuming you are running on a mac computer, right?

Here is what I did to get things running...

Pre-requisit: Install the CP210x USB to UART Bridge VCP Drivers from Silicon Labs located here: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

Then go to this website and follow the instructions there:
http://blog.nwoolls.com/2013/04/24/bitcoin-mining-on-mac-os-x-cgminer-bfgminer/
One note, when installing bfgminer run the command with the flag -head (i.e. brew install bfgminer -head to get a working 3.1.3 that will recognize the block erupters properly)

Good luck mate
If you found my post helpful pleae reward me with a donation of bitcoin at my address in my sig, thanks.

iamnightelf

[Luke-Jr]

Then go to this website and follow the instructions there:
http://blog.nwoolls.com/2013/04/24/bitcoin-mining-on-mac-os-x-cgminer-bfgminer/
One note, when installing bfgminer run the command with the flag -head (i.e. brew install bfgminer -head to get a working 3.1.3 that will recognize the block erupters properly)

Note the -head option means you will not be running 3.1.3, but the latest git code.
I try to keep this reasonably stable, but it is almost always far less tested than actual releases.
(But necessary for Erupters on Mac at the moment)

[Anonymailer]

Sorry again everyone, due to unexpected circumstances I have limited net connectivity right now!

Here's a version of bfgminer you can replace the existing version with, so replace

/Applications/MacMiner.app/Contents/Resources/bfgminer

with the bfgminer folder compressed here:

http://fabulouspanda.co.uk/macminer/downloads/bfgminer313dirty.zip

An updated beta version will be up very soon!

[iamnightelf]

Sorry again everyone, due to unexpected circumstances I have limited net connectivity right now!

Here's a version of bfgminer you can replace the existing version with, so replace

/Applications/MacMiner.app/Contents/Resources/bfgminer

with the bfgminer folder compressed here:

http://fabulouspanda.co.uk/macminer/downloads/bfgminer313dirty.zip

An updated beta version will be up very soon!

Even better! Thanks sir!
Now you can use the -S all flag for mining ALL devices (if you want to disable a device just put in the appropriate flag i.e. -G for no gpu, etc.)

I run with the following settings for cpu, gpu and multiple Block Erupters... -S all --no-submit-stale
Works beautifully for combined hashing, awesome!

[jedimstr]

Just got autoupgraded to the 1.4.4 beta and now I'm getting this:



For now my miners are "resting"... help?

Update: I had to downgrade to the stable 1.3.17 to get mining again. Copying the "dirty" bfgminer 3.1.3 linked above resulted in the same error as I got with the last beta, so had to re-install the 1.3.17 version again.

[stellan0r]

Had the same problem, but it is working with 1.3.17 on OS X 10.8.4 with a USB Block Erupter

Just got autoupgraded to the 1.4.4 beta and now I'm getting this:



For now my miners are "resting"... help?

Update: I had to downgrade to the stable 1.3.17 to get mining again. Copying the "dirty" bfgminer 3.1.3 linked above resulted in the same error as I got with the last beta, so had to re-install the 1.3.17 version again.

[Anonymailer]

Ah sorry again you can replace bfgminer with
http://fabulouspanda.co.uk/macminer/downloads/bfgminer313dirtyfixed.zip

and that should fix it for you! Will push 1.4.5 now.

Dirty indicates that the version has been taken from github directly rather than the main 3.1.3 version that Luke makes available. I will tend to use the stable versions but if there's a benefit in an update that hasn't been released yet I'll get  the code from head.

[iamnightelf]

Ah sorry again you can replace bfgminer with
http://fabulouspanda.co.uk/macminer/downloads/bfgminer313dirtyfixed.zip

and that should fix it for you! Will push 1.4.5 now.

Dirty indicates that the version has been taken from github directly rather than the main 3.1.3 version that Luke makes available. I will tend to use the stable versions but if there's a benefit in an update that hasn't been released yet I'll get  the code from head.

Odd, the old 'new dirty version' as well as the official 1.4.4 version worked fine for me. I am on a Late 2010 Mac Mini running 10.8.4.
Wonder what went wrong for the others, 1.3.17 always crashed on me when trying to mine with any number of block erupters, 1.4.3 worked but was picky with the flags (i.e. -S all wouldn't work...)
Also, I get no temp reading on 1.4.4, there isn't even any text in the window, it's just a large blank grey spot there under 'Accepted'...

[jedimstr]

Anonymailer: Thanks, the new dirty 3.1.3 with 1.4.4 works now.

iamnightelf: I'm running 10.8.4 as well, but on a Mac Pro. 

[Anonymailer]

Anonymailer: Thanks, the new dirty 3.1.3 with 1.4.4 works now.

iamnightelf: I'm running 10.8.4 as well, but on a Mac Pro. 

Thanks for your updates it's really useful in helping me get everything working right! I may end up quoting your setup

[jedimstr]

Anonymailer: Thanks, the new dirty 3.1.3 with 1.4.4 works now.

iamnightelf: I'm running 10.8.4 as well, but on a Mac Pro. 

Thanks for your updates it's really useful in helping me get everything working right! I may end up quoting your setup

Not a problem... let me know if you need more info about how MacMiner is running on my system.  Upgraded to 1.4.5 now without issue and am finally able to switch to -S all instead of explicit device initialization.

Just as an additional FYI, here are some of the settings I'm using for the FPGA/ASIC version of BFGMiner in MacMiner:

Manual Flags: -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100

Manual Config File settings (minus the pool and worker info):
"intensity":"4",
"gpu-engine":"950",
"gpu-memclock":"160",
"kernel":"diablo",
"kernel-path" : "/Applications/MacMiner.app/Contents/Resources/bfgminer/bin"

Running on OSX Mountain Lion 10.8.4 on a first gen Mac Pro 1,1 2x3Ghz CPU 16GB Memory
(identified as 2,1 with firmware flash and using Chameleon to load a 64bit EFI so I can use Mountain Lion+)

Miner Devices currently detected:                   
   0. OCL 0  (driver: opencl)  - ATI/AMD Radeon HD 5770                 
   1. ICA 0  (driver: icarus)   - ASICMiner USB Block Erupter                 
   2. ICA 1  (driver: icarus)   - ASICMiner USB Block Erupter

So far I have 6 more Erupters on the way, and going to order another 10 in a few days.
Also have a 7GH upgraded Jalapeño and a 25 GH Little Single from BFL on backorder (yes, yes, I know... *sigh).

Side Question:
Does anyone know how to disable the two Bluetooth items from the device list?

/dev/cu.Bluetooth-Modem      /dev/cu.Bluetooth-PDA-Sync

Not really causing any problems, but they show up in BFGMiner's startup as the software tries to ping both devices.  I tried disabling the corresponding checked item in the Bluetooth System Pref, but it won't stay deactivated... switching back and forth with pref panels shows it still active.

[btcmmm]

i got this

 B = EndianSwap(tmp);
                        ^~~~~~~~~~~~~~~~~~
<prog                   
 [2013-07-19 20:44:40] Failed to init GPU thread 0, disabling device 0                   
 [2013-07-19 20:44:40] Restarting the GPU from the menu will not fix this.                   
 [2013-07-19 20:44:40] Try restarting BFGMiner.   

om the menu will not fix this.
 [2013-07-19 20:44:40] Try restarting BFGMiner.
 [2013-07-19 20:44:40] 1 gpu miner threads started
 [2013-07-19 20:44:40] -1 cpu miner threads started, using SHA256 'scrypt' algorithm.
 [2013-07-19 20:44:40] Switching pool 0 http://p2pool.org:9327 to stratum+tcp://p2pool.org:9327

when i use litecoin minig. 0Khs. Replaced bfgminer with 3.1.3dirty


OSX 10.6.8 Macmini i7.

btc mining works.

[wlwesq]

How about app crashing after just starting mining with the CPU miner? Here's the short version of what the crash reporter generates:

Process:         MacMiner [9020]
Path:            /Applications/MacMiner.app/Contents/MacOS/MacMiner
Identifier:      com.fabulouspanda.macminer
Version:         1.4.5 (1405)
Code Type:       X86-64 (Native)
Parent Process:  launchd [203]
User ID:         501

Date/Time:       2013-07-19 14:59:12.834 -0400
OS Version:      Mac OS X 10.8.4 (12E55)
Report Version:  10
Sleep/Wake UUID: A4B38065-B8C3-4209-9C79-57390591AEFA

Interval Since Last Report:          120961 sec
Crashes Since Last Report:           105
Per-App Interval Since Last Report:  117 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      EB33D52C-4C2A-B49B-F33E-44B2D2576F15

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

VM Regions Near 0:
-->

I forget, what miner (bfg? cg? other?) runs in the CPUminer? Just making sure there's no conflict there. Thanks!

[XFox]

How about app crashing after just starting mining with the CPU miner?

I noticed it, too, but I reported it in the Newbies section since I couldn't already post here (it was my first post on the forum).

I forget, what miner (bfg? cg? other?) runs in the CPUminer? Just making sure there's no conflict there. Thanks!

AFAIK it's pooler's cpuminer.

[Anonymailer]

Thanks for the reports everyone!

On the poclbm front I'm actually going to remove that miner from the app as it has no real benefits over bfg/cg miner which use poclbm kernel as a backend, and poclbm is written in python which makes the downloads much larger due to the inclusion of a separate python framework built just for the app.

With regards to CPU Miner it is indeed Pooler's CPU Miner and I think the problem is either libz being linked to /opt/ or an incomplete implementation of CPU temp readings in the beta version - both work for me, but are those experiencing these crashes running 1.3 or 1.4?