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

[DPattee]

1.4.17 has just been released and should fix this issue, please let me know!

[/quote]

I am encountering a crash every couple seconds on my 10.7.5 MacMini -actually according to crash report, MacMiner has crash over 7000 times since I left it running last night. 1.4.16 was the first version I tried, and I just updated to 1.4.17 with the same issue. With just the default BFG Miner running there is no crash. But, if I stop that and start up the FPGA/ASIC Miner the crashes immediately start.

I've set the FPGA?ASIC options to 'disable GPU' and set the devices to -S /dev/cu.usbserial-FTWWMIYE which is the corrent name for my butterfly single.

Even with all the crash popups, the app continues to run in the background. The FPGA/ASIC Miner log window continues to update - the hashrate number updates and new lines are added to the log, the accepted/rejected numbers update, but the Temperature shows nothing.

Not sure where in the logs would be somethign useful, but an example snip is

Code:

 [2013-11-02 09:37:44] Error trying to wake notifier
 [2013-11-02 09:37:44] Error trying to wake notifier
 [2013-11-02 09:37:44] Stratum from pool 0 requested work update
 [2013-11-02 09:37:44] BFL 0: Opened /dev/cu.usbserial-FTWWMIYE
 [2013-11-02 09:37:44] 0 gpu miner threads started
 [2013-11-02 09:37:44] -1 cpu miner threads started, using SHA256 'fastauto' algorithm.
 [2013-11-02 09:37:44] Stratum authorisation success for pool 2
 [2013-11-02 09:37:44] Pool 2 http://p2pool.beehost.org:9332 alive
 [2013-11-02 09:37:44] Pool 2 is hiding block contents from us
 [2013-11-02 09:37:44] Closing socket for stratum pool 2
 [2013-11-02 09:37:45] Staged work underrun; increasing queue minimum to 2
 [2013-11-02 09:37:45] Staged work underrun; increasing queue minimum to 3
 [2013-11-02 09:37:45] Staged work underrun; increasing queue minimum to 4
 [2013-11-02 09:37:48] New best share: 2
 [2013-11-02 09:37:49] Stratum from pool 0 requested work update
 [2013-11-02 09:37:49] API running in IP access mode on port 4028

And there is not much info in the crash report, just the generic 'exc_bad_access (sigsegv)'


 

[BrandonMcPherson]

Installing it now.

[BrandonMcPherson]

BitBacco, I've been running 1.4.17 for 90 minutes with no problems. Before this update, it manifested after 20-30 minutes, so yay!

Thanks for the fix.

[Anonymailer]

BitBacco, I've been running 1.4.17 for 90 minutes with no problems. Before this update, it manifested after 20-30 minutes, so yay!

Thanks for the fix.

Awesome, thanks for the update!

1.4.17 has just been released and should fix this issue, please let me know!

I am encountering a crash every couple seconds on my 10.7.5 MacMini [in FGPA/ASIC Window]
[/quote]
Ah, thanks for the bug report, it seems the api data retrieval script is crashing every time it's run on 10.7, I'll get that fixed ASAP!

[Anonymailer]

-10.7 crashes-

1.4.18 out now just stops FPGA/ASIC Window from crashing for 10.7 but the table view isn't loading on that OS version and I'm looking in to it

[DPattee]

1.4.18 out now just stops FPGA/ASIC Window from crashing for 10.7 but the table view isn't loading on that OS version and I'm looking in to it

I've been running the new version since yesterday, and no crashes. Thanks

[BrandonMcPherson]

Has anyone tried running Blue Fury USB miners on their Mac with MacMiner?

[Anonymailer]

Has anyone tried running Blue Fury USB miners on their Mac with MacMiner?

I've not heard anyone talk about it but the version of bfgminer included does have bit fury support - I just can't find the info on whether they need usb-serial drivers installed - anyone know that?

[BrandonMcPherson]

I know just enough to be dangerous.

In the Windows and Linux-centric discussions about the Blue Fury miners, there are frequent mentions of difficulty running BEs and the BF miners at the same time.  There are also frequent complaints about them not performing at their rated hashing levels (the makers have posted screenshots with them working as they should under particular Linux distributions).

I was not able to ascertain the answer to your question, BitBacco, but that doesn't necessarily mean it wasn't there.

[Anonymailer]

I know just enough to be dangerous.

In the Windows and Linux-centric discussions about the Blue Fury miners, there are frequent mentions of difficulty running BEs and the BF miners at the same time.  There are also frequent complaints about them not performing at their rated hashing levels (the makers have posted screenshots with them working as they should under particular Linux distributions).

I was not able to ascertain the answer to your question, BitBacco, but that doesn't necessarily mean it wasn't there.

The info is a little sparse I guess, it looks as though you may be able to use block erupter usbs and blue furies together but you can then no longer use -S all and you have to specify each device individually which would be a pain for anyone with huge arrays of these things around… If anyone gets the opportunity to find out please let us know how it goes for you!

[jedimstr]

I know just enough to be dangerous.

In the Windows and Linux-centric discussions about the Blue Fury miners, there are frequent mentions of difficulty running BEs and the BF miners at the same time.  There are also frequent complaints about them not performing at their rated hashing levels (the makers have posted screenshots with them working as they should under particular Linux distributions).

I was not able to ascertain the answer to your question, BitBacco, but that doesn't necessarily mean it wasn't there.

The info is a little sparse I guess, it looks as though you may be able to use block erupter usbs and blue furies together but you can then no longer use -S all and you have to specify each device individually which would be a pain for anyone with huge arrays of these things around… If anyone gets the opportunity to find out please let us know how it goes for you!

One of the change log items for the just released BFGMiner 3.5.0 says that the Scan for comm devices is handled once now and given to all specified drivers in this version.  Don't know if this means that LukeJR reworked the way the scan is done to get around this issue of specific drivers messing each other's all scan up or if it's not related.

[Anonymailer]

One of the change log items for the just released BFGMiner 3.5.0 says that the Scan for comm devices is handled once now and given to all specified drivers in this version.  Don't know if this means that LukeJR reworked the way the scan is done to get around this issue of specific drivers messing each other's all scan up or if it's not related.

It looks as though people are still having issues with -S all on 3.5 and to top it all giving it a shot on Mac OS it comes up with libusb errors - must be a result of the reworking of com devices - I've opened an issue on github - hopefully the next version will be a bit more co-operative!

[jedimstr]

One of the change log items for the just released BFGMiner 3.5.0 says that the Scan for comm devices is handled once now and given to all specified drivers in this version.  Don't know if this means that LukeJR reworked the way the scan is done to get around this issue of specific drivers messing each other's all scan up or if it's not related.

It looks as though people are still having issues with -S all on 3.5 and to top it all giving it a shot on Mac OS it comes up with libusb errors - must be a result of the reworking of com devices - I've opened an issue on github - hopefully the next version will be a bit more co-operative!

Yeah, just saw that...skip 3.5.0!!!  Looks like it won't connect to BE's at all.

[chorchonga]

Just downloaded latest MacMiner and I'm getting like 1Mhash, supposedly on Block Erupter, but I suspect it's using my GPU though I told it not to.  Will try latest stable version instead.

ETA: Still having the issue on last stable version.  Suggestions?  I did install the silabs driver and it's showing in my dev folder.

[Anonymailer]

Just downloaded latest MacMiner and I'm getting like 1Mhash, supposedly on Block Erupter, but I suspect it's using my GPU though I told it not to.  Will try latest stable version instead.

ETA: Still having the issue on last stable version.  Suggestions?  I did install the silabs driver and it's showing in my dev folder.

Did you set

-S all

in manual flags in the fpga/asic miner options window? Better to be on the 1.4 branch than the 1.3 branch now.

[chorchonga]

I set -S but not -S all.  Will try again!

[Anonymailer]

I set -S but not -S all.  Will try again!

Cool, that should do it - the next update will include a note in the text field there suggesting -S all!

[chorchonga]

Thanks, that was it!  Now I just need to tweak settings to max out the Mhash.

[BrandonMcPherson]

BitBacco, is there any way to load balance using MacMiner? I tried running two copies once, but they both called to the same instances of the command line engines. Which makes sense.

This isn't a big deal for me yet as I am a small fry, but it's been on my mind as I work on expanding my hashing power and I thought i'd ask.

Also, I have been able to use the FPGA/ASIC window to mine BTC and (at the same time) the CGMiner window to scrypt mine LTC. That's nifty, even if it was just to see if I could.

Lastly, 4.17 and 4.18 have both been rock solid.

[Anonymailer]

BitBacco, is there any way to load balance using MacMiner? I tried running two copies once, but they both called to the same instances of the command line engines. Which makes sense.

This isn't a big deal for me yet as I am a small fry, but it's been on my mind as I work on expanding my hashing power and I thought i'd ask.

Also, I have been able to use the FPGA/ASIC window to mine BTC and (at the same time) the CGMiner window to scrypt mine LTC. That's nifty, even if it was just to see if I could.

Lastly, 4.17 and 4.18 have both been rock solid.

if you add --load-balance  in miner options it makes some judgement of which pool to use based on efficiency, but I've heard it has some problems.

I should add the preference to set different config files for each window rather than one for each which should let you do what you want to.

Thanks for the reports, I'm hoping to make the 1.4 branch the old stable version to the forthcoming 1.5 branch!