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

[boxuser]

can you please use something faster to host the files, it took me like 20mins to dl, i felt like im running over an 56k modem

[BrandonMcPherson]

Holy smokes, boxuser, how did you survive the hell of waiting...did you say 20 minutes? Heck, that's enough time for you to write your own free software that ungrateful and entitled gits can complain about.

[Anonymailer]

hehe nicely put BMcP!

It downloads in about a second for me - has anyone else had this problem?

[BrandonMcPherson]

No, it's definitely slow for me here in the States, BitBacco. Unusually slow, even, but I've somehow managed to persevere each time. No doubt they will sing songs of my bravery and fortitude...

[Anonymailer]

No, it's definitely slow for me here in the States, BitBacco. Unusually slow, even, but I've somehow managed to persevere each time. No doubt they will sing songs of my bravery and fortitude...

Damn, the host must be throttling it… I'll move the files over to a new server. Sorry about that in the meantime!

[Anonymailer]

Version 1.4.27 released on a new server, so downloads should be faster now!

- Fixes several bugs
- Adds spoken warnings of 0 hash rate and pool authorisation failure - preferences for warnings to follow
- Prevents quit while miners are running

Please let me know if anyone else is having Check for Updates grey out when clicked and fail to act…

[Anonymailer]

The MacMiner github has been updated, so this is a good opportunity for any of you Mac devs out there to get involved!
https://github.com/fabulouspanda/MacMiner

[inevertell]

Hi BitBacco

I've been using macminer for the mini-setup (2 jala, 20 BE) with macminer without issue for months now.

I was recently given 1 Red Bitfury usb miner.

I haven't been able to get it running with macminer under the FPGA/ASIC Device miner with the rest of my miners. It does not detect it.

I can however run a window of CG miner and it will detect and hash with the bitfury device without issue. The only issues I run into is that I need to run the 2 separate windows, not such a big deal at all.. but also in the CGminer window it is constantly spitting out this type of error ( its still trying to initialize the BEs and Jala even though they are mining already.)

 [2013-12-17 14:09:25] BitForceSC detect (253:37) failed to initialise (incorrect device?)                    
[2013-12-17 14:10:53] Icarus detect (253:21) failed to initialise (incorrect device?)                    
 [2013-12-17 14:10:53] Icarus detect (253:20) failed to initialise (incorrect device?)                    
 [2013-12-17 14:10:54] Icarus detect (253:19) failed to initialise (incorrect device?)                    
 [2013-12-17 14:10:54] Icarus detect (253:16) failed to initialise (incorrect device?)                    

Combined I still get the proper hashrate reported as far as I can tell, could these errors be slowing me down at all? Could they be avoided somehow? Can I get the bitfury device to run under BFGminer (FPGA/ASIC window) with all my other devices?

I've tried the -S bigpic:all command and when I do this, none of the devices are detected at all.

Anyways, any ideas?
Thanks

MacPro
OS X Mountain Lion (cannot upgrade to mavericks yet)

[Anonymailer]

Hi BitBacco

I've been using macminer for the mini-setup (2 jala, 20 BE) with macminer without issue for months now.

I was recently given 1 Red Bitfury usb miner.

I haven't been able to get it running with macminer under the FPGA/ASIC Device miner with the rest of my miners. It does not detect it.

I can however run a window of CG miner and it will detect and hash with the bitfury device without issue. The only issues I run into is that I need to run the 2 separate windows, not such a big deal at all.. but also in the CGminer window it is constantly spitting out this type of error ( its still trying to initialize the BEs and Jala even though they are mining already.)

 [2013-12-17 14:09:25] BitForceSC detect (253:37) failed to initialise (incorrect device?)                    
[2013-12-17 14:10:53] Icarus detect (253:21) failed to initialise (incorrect device?)                    
 [2013-12-17 14:10:53] Icarus detect (253:20) failed to initialise (incorrect device?)                    
 [2013-12-17 14:10:54] Icarus detect (253:19) failed to initialise (incorrect device?)                    
 [2013-12-17 14:10:54] Icarus detect (253:16) failed to initialise (incorrect device?)                    

Combined I still get the proper hashrate reported as far as I can tell, could these errors be slowing me down at all? Could they be avoided somehow? Can I get the bitfury device to run under BFGminer (FPGA/ASIC window) with all my other devices?

I've tried the -S bigpic:all command and when I do this, none of the devices are detected at all.

Anyways, any ideas?
Thanks

MacPro
OS X Mountain Lion (cannot upgrade to mavericks yet)

Unfortunately the little fury driver is broken in bfgminer for Mac so for now cgminer is the only way to go. if you identify the device as per here:
http://fabulouspanda.co.uk/macminer/docs/devices.html

I believe you can set
-S /dev/cu.yourdevice

in cgminer and it should stop looking for others

[nwoolls]

Unfortunately the little fury driver is broken in bfgminer for Mac so for now cgminer is the only way to go.

I can hash using a Red Fury on OS X with bfgminer without any issues. What problems have you found? There's an article with instructions here.

[Anonymailer]

MacMiner 1.5 has been released featuring

An updated GUI

Preferences for spoken warnings

fixes several important bugs

The further features I have intended for this version will be released in the style of previous MacMiner versions, in frequent minor updates.

[Anonymailer]

Unfortunately the little fury driver is broken in bfgminer for Mac so for now cgminer is the only way to go.

I can hash using a Red Fury on OS X with bfgminer without any issues. What problems have you found? There's an article with instructions here.

That's not true of versions newer than bfgminer 3.6
The last version of MacMiner with bfgminer 3.6 was 1.4.25 so you could actually use the backends from that version or that version on it's own - it's still up on the downloads page of the website

[inevertell]

Hi BitBacco

I've been using macminer for the mini-setup (2 jala, 20 BE) with macminer without issue for months now.

I was recently given 1 Red Bitfury usb miner.

I haven't been able to get it running with macminer under the FPGA/ASIC Device miner with the rest of my miners. It does not detect it.

I can however run a window of CG miner and it will detect and hash with the bitfury device without issue. The only issues I run into is that I need to run the 2 separate windows, not such a big deal at all.. but also in the CGminer window it is constantly spitting out this type of error ( its still trying to initialize the BEs and Jala even though they are mining already.)

 [2013-12-17 14:09:25] BitForceSC detect (253:37) failed to initialise (incorrect device?)                    
[2013-12-17 14:10:53] Icarus detect (253:21) failed to initialise (incorrect device?)                    
 [2013-12-17 14:10:53] Icarus detect (253:20) failed to initialise (incorrect device?)                    
 [2013-12-17 14:10:54] Icarus detect (253:19) failed to initialise (incorrect device?)                    
 [2013-12-17 14:10:54] Icarus detect (253:16) failed to initialise (incorrect device?)                    

Combined I still get the proper hashrate reported as far as I can tell, could these errors be slowing me down at all? Could they be avoided somehow? Can I get the bitfury device to run under BFGminer (FPGA/ASIC window) with all my other devices?

I've tried the -S bigpic:all command and when I do this, none of the devices are detected at all.

Anyways, any ideas?
Thanks

MacPro
OS X Mountain Lion (cannot upgrade to mavericks yet)

Unfortunately the little fury driver is broken in bfgminer for Mac so for now cgminer is the only way to go. if you identify the device as per here:
http://fabulouspanda.co.uk/macminer/docs/devices.html

I believe you can set
-S /dev/cu.yourdevice

in cgminer and it should stop looking for others

.

Thanks for the quick help!

I am trying now to identify the device, but I cannot see it in my list of cu.* devices

crw-rw-rw-  1 root  wheel   18,  51 17 Dec 12:00 /dev/cu.Bluetooth-Modem
crw-rw-rw-  1 root  wheel   18,  53 17 Dec 13:01 /dev/cu.Bluetooth-PDA-Sync
crw-rw-rw-  1 root  wheel   18,  47 17 Dec 13:01 /dev/cu.Bluetooth-Serial-1
crw-rw-rw-  1 root  wheel   18,  49 17 Dec 13:01 /dev/cu.Bluetooth-Serial-2
crw-rw-rw-  1 root  wheel   18,  57 17 Dec 16:23 /dev/cu.SLAB_USBtoUART    ( BLOCK ERUPTERS - 20 in total)
crw-rw-rw-  1 root  wheel   18,  59 17 Dec 16:23 /dev/cu.SLAB_USBtoUART29
crw-rw-rw-  1 root  wheel   18,  61 17 Dec 16:23 /dev/cu.SLAB_USBtoUART30
crw-rw-rw-  1 root  wheel   18,  63 17 Dec 16:23 /dev/cu.SLAB_USBtoUART31
crw-rw-rw-  1 root  wheel   18,  65 17 Dec 16:23 /dev/cu.SLAB_USBtoUART32
crw-rw-rw-  1 root  wheel   18,  67 17 Dec 16:23 /dev/cu.SLAB_USBtoUART33
crw-rw-rw-  1 root  wheel   18,  69 17 Dec 16:23 /dev/cu.SLAB_USBtoUART34
crw-rw-rw-  1 root  wheel   18,  71 17 Dec 16:23 /dev/cu.SLAB_USBtoUART35
crw-rw-rw-  1 root  wheel   18,  73 17 Dec 16:23 /dev/cu.SLAB_USBtoUART36
crw-rw-rw-  1 root  wheel   18,  75 17 Dec 16:23 /dev/cu.SLAB_USBtoUART37
crw-rw-rw-  1 root  wheel   18,  77 17 Dec 16:23 /dev/cu.SLAB_USBtoUART38
crw-rw-rw-  1 root  wheel   18,  79 17 Dec 16:23 /dev/cu.SLAB_USBtoUART39
crw-rw-rw-  1 root  wheel   18,  81 17 Dec 16:23 /dev/cu.SLAB_USBtoUART40
crw-rw-rw-  1 root  wheel   18,  83 17 Dec 16:23 /dev/cu.SLAB_USBtoUART41
crw-rw-rw-  1 root  wheel   18,  85 17 Dec 16:23 /dev/cu.SLAB_USBtoUART42
crw-rw-rw-  1 root  wheel   18,  87 17 Dec 16:23 /dev/cu.SLAB_USBtoUART43
crw-rw-rw-  1 root  wheel   18,  89 17 Dec 16:23 /dev/cu.SLAB_USBtoUART44
crw-rw-rw-  1 root  wheel   18,  91 17 Dec 16:23 /dev/cu.SLAB_USBtoUART45
crw-rw-rw-  1 root  wheel   18,  93 17 Dec 16:23 /dev/cu.SLAB_USBtoUART46
crw-rw-rw-  1 root  wheel   18,  95 17 Dec 16:23 /dev/cu.SLAB_USBtoUART47
crw-rw-rw-  1 root  wheel   18,  99 17 Dec 16:23 /dev/cu.usbserial-FTWINKIX (JALA 1 )
crw-rw-rw-  1 root  wheel   18,  97 17 Dec 16:23 /dev/cu.usbserial-FTWMMYGN (JALA 2)

It is currently hashing so it is definitely working.

Any other place I can find the name of the device? ls -l /dev/* didn't show me anything that was obviously the bitfury miner either.

[nwoolls]

Unfortunately the little fury driver is broken in bfgminer for Mac so for now cgminer is the only way to go.

I can hash using a Red Fury on OS X with bfgminer without any issues. What problems have you found? There's an article with instructions here.

That's not true of versions newer than bfgminer 3.6

[Anonymailer]

the problem with versions of bfgminer newer than 3.6 is specifically a conflict with BFL hardware - it works if you don't have any BFL plugged in.

But due to the error bfgminer 3.8.1 for mac was compiled without little fury driver for MacMiner

Can you paste the output of ls -l here please?

[nwoolls]

the problem with versions of bfgminer newer than 3.6 is specifically a conflict with BFL hardware - it works if you don't have any BFL plugged in.

Can you paste the output of ls -l here please?

I'm not running MacMiner or the MacMiner builds of bfgminer. I'm compiling them myself. Where do you want me to list directory contents?

[Anonymailer]

actually i was hoping to have inevertell post that - but seeing as you have one, what does it show up as in /dev/ ?

I'm referring to this issue:
https://github.com/luke-jr/bfgminer/issues/338

perhaps it's fixed by updating libusb to 1.0.2? I'll give that a shot

[jedimstr]

The conflicts between the RedFury and other devices like BFL also usually occurs with Block Erupters.

There are ways around that.. for instance, here's my Mac Pro running 44 Block Erupters, a RedFury, and a Bi*Fury all at the same time:



Let me know if you want to know how I did that

[XFox]

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.

That did the trick!
I was using the API Output window without starting the FPGA/ASIC Miner window first.
Thank you very much, it is working fine now with my KnCMiner October Mercury.

[Anonymailer]

The conflicts between the RedFury and other devices like BFL also usually occurs with Block Erupters.

I thought the conflict was fixed for BE? It was for me anyway… anyone who can figure the root cause of my problem before I do would be most appreciated