Topic: Mac miner front-ends to Diablo and RPC - page 2. (Read 181588 times)

I have these exact same questions and it seems they haven't been answered yet in this thread. Just got my Macbook and would like to mine some coins, but the processes takes up too much power, leaving the rest very sluggish. Anyone care to help?

Any chance of this being updated soon?

when logged in as a regular user in OSX it starts to open but fails.
I switched over to an admin accout and it gave me the
-DL from web do you want to run- question,
after pressing ok it started went into terminal and started running.

I'm on a 4yr old Mac Book Pro.  I get about 4mhash/s.  When I was in bootcamp with win xp I got 5mhash with the guiminer.

I might be getting a real mining rig soon.

Is that option even available as an option on desktop machines? (Mac Pros and iMacs).  The dim key doesn't do anything here, and I can't find an option in the sys prefs.  I'm getting quite good at hitting Control+C in the terminal when I need an interrupt which is at least letting me work on the same machine.  Totally disruptive to mining though.

My old NVidea 8800 didn't didn't get as much hashing done, although while hashing, it didn't seem to interfere with the screen UI as much as my faster ATI5870 card.  I still don't quite understand why.  Maybe because it was just working less?

I’m trying to hook it into the same API that dims your screen (right before the screensaver kicks in). In other words, it will be configurable in the same way as your power settings.

Its 15 sec average/forever avg.

Also, you can set -w all you want. Most OSX users say anything but default is slower for them.

Great news!

I wonder if it would be possible for the user to input the idle detection time?  Sometimes a minute would be all that it needs to crank back up to 100%.  Other times, when I'm seriously working on the machine I might want to kick it back to 10 or 15 minutes idle wait so as not to interfere.  Of course right now, I have the option of turning it off completely although still with the excitement of not receiving my first bitcoin yet, I'm tolerating a very sluggish screen.  

I'm on a MacPro 8-core on OSX 10.6.7 with an ATI 5870 with an Artic Cooler.  I must say it is rather disappointing to see only 156 Mhash/sec when others on the PC are reporting easily more than double (and someone claimed 421).  It would be nice if there were some options to optimize performance on the Mac to squeeze a 'bit' more performance (sorry).

EDIT I just installed the latest version DiabloMiner-GPU-Bitcoin-miner-20110618.zip and at first I thought I saw an increase in speed.  I saw number over 205,000 that really excited me.  Then, slowly it started dropping down.  Now it seems to be running about the same rate as before.  I see 156,000/160,000 khash/sec

btw, why the fraction?  What do the two numbers mean?

Are there any ways to set the vector worksize to 128?  Might this not provide some advantage?

I have a partially working implementation of idle detection that will—at the cost of mining performance—prevent the miner from using too much system resources when the machine is in use. This is not fully working yet, but I’ll get there.

Another small update with some crash fixes. (Thanks for reporting it when you run into problems.) Downloads.

Increase -f, it expects a multiple or divisior of 60. Also, that 5870 can easily do >350 mhash/sec... OSX really sucks.

Also while running Diablo on a MacPro with a 5870 (@160k hash/s rate), my UI screen is sluggish.  When I move windows around, they are very jerky whereas when Diablo is off, they are smooth.  Is there a way to give priority to the US of the open appwhen its being used?

With my previous graphics card (NVidia8800), the UI operations seemed to be smoother, although the hash rate was 1/10.

Hey just tried the lastest version and it crashes when I try to run it:


DiabloMiner-exe: line 175:   618 Segmentation fault      java -Xmx16m -cp target/libs/*:target/DiabloMiner.jar -Djava.awt.headless=true -Djava.library.path=target/libs/natives/macosx com.diablominer.DiabloMiner.DiabloMiner -u $diablominer_username -p $diablominer_userpass -o $diablominer_hostname -r $diablominer_hostport
Did something go wrong? Relaunch and enter the Set up wizard by pressing 1 and Enter during start-up, and check your configuration.
logout




Also I am only getting about 160Kh/s with my 5870. I wanted to try to enable vectors and set the worksize to 128 but when I try to run the miner from the command line with the -w 128 and -v settings it doesn't seem to do anything. Any advise?

Posted a small update.

Next I will work on automatically recovering from crashes, and catching more exceptions.

You're on one of those hybrid dual Nvidia setups. You can't force one on or the other. Use -D to force it to use the right one (starts at 1).

This is what shows up in my terminal at the moment.  Is there a way to utilize both GPUs at the same time?  If not, is there way to just use my 9600M GT for mining and not the 9400M?  I can't seem to get it to stop using the 9400M.

Sounds like user error.

What is this message I am getting on the easier (not so easier) DIABLOMINER gui interface for Java?

[6/9/11 9:34:19 AM] ERROR: Can't connect to Bitcoin: Bitcoin returned unparsable JSON


I cant find a real GUI for cooperative mining on MacOSX

Feature request:
Diablominer keeps crashing every few hours. (Apparently thanks to Apple's poor OpenCL implementation.) Would it be possible to have your front-end check every few minutes if the process is alive and restart the miner if it wasn't killed manually?

Anyway nice job with the app. Makes things really easy.

(Posted with bugmenot.com user/pass to avoid registration.)

batkiller, I sent you a personal message with information on how to get some more debug information. Please respond to that message and I’ll see what I can do.

Thanks for the reply! No, there's nothing... as soon as I hit 'enter' or wait the 15 seconds, the terminal window immediately disappears. The only information in the system log is that a new process was started, and then 2 seconds later the process died. Is there a way to force the terminal window to stay open so I can see any error messages? I know how to do that when issuing a command, but not from within the rpcminer app (or its menu).