If you're familiar with the command line you can get it going from the latest posts in the bitcointalk.org MacMiner thread, otherwise the situation is that the backend miner is definitely working and it'll be built in to the MacMiner GUI in the next…
where you see tty.* and cu.* they're talking about the same devices in multiple locations but you almost certainly want to use cu.* not tty - no harm trying both though and you can also run ls -l /dev/tty.* to check on that one. I've never seen tty.…
The latest cgminers auto detect though may not be the case with this version, try adding -S all to the start command - have you found the device's path?
Yeah it looks familiar sorry guys wait a little while and I'll provide a binary for 10.7+ with the required libraries! If you want to make this version work you can use the install_name_tool to change /opt/local/lib/libcurl.4.dylib to use the versio…
Also, instead of trying to cd in Terminal, open a new Terminal window, drag the the cgminer binary itself (a black file called cgminer with no file extension) in to the Terminal so it shows it's path, then add
Did you try running the Mac cgminer? It should result in the same experience. Would be great to have someone who knows Terminal to check this, I don't have a device to test! Nonetheless, should find it's way in to the GUI soon.
Are you running 10.9 and did you try the cgminer for Mac file there? That wasn't there at the time of my original post. I have time I'll give it a shot compiling for 10.7+ tonight.
What settings are you using? Usually this means one of the devices is struggling. Try to remove any excess dust. It might be worth running them on individual processes so that one doesn't disturb the others.
MacMiner is currently having some trouble displaying stats due to a lot of recently implemented different backends and changing display conventions, but you can get an accurate display of stats in the API Output window for now!
One thing to keep in mind is that one GPU = one thread. all the kh are working towards one goal. with the cpu you have multiple threads, each working on separate work more slowly.
Please download this, decompress it and chuck it in MacMiner.app/Contents/Resources so you can then run MacMiner.app/Contents/Resources/sgminer/bin/sgminer
Note please ignore the two warnings that show immediately on …
If you have a chance to bug check the source of MacMiner at any point that would be HUGELY appreciated as there are quite a lot of issues yet to be fixed!
The cpuminer in that thread is the original pooler cpuminer which only supports SHA256 and original scrypt, but I'll look at recompiling the relevant miner with gcc. I suspect though the problem is to do with relatively low hash rate perhaps causing…
I had a very quick look at this last night before passing out and the initial signs were that it needs significant modification before playing nice. The corrections to the autogen file are fine, but we'll see where it goes from there - I'm hoping to…
P2Pool is quite complicated. You don't accrue balance, each share is like a lottery ticket, if one of the shares you solve is a winner you get a payout pretty immediately. Under 100kh/s on LTC those payouts are increasingly rare/unlikely.
Hmm, sorry for the bugs, MacMiner is using the latest bfgminer from github which must account for the bugs but it supports more devices than the last official version - hopefully this will get a bit more graceful soon!