Topic: Mac OS X Resources & Howtos for Mining (Homebrew/DIY/Bin/Xcode Debugging) - page 5. (Read 64259 times)
November 27, 2013, 11:38:42 AM
Homebrew formulas, Shell scripts, and precompiled binaries have all been updated with bfgminer 3.7.0.
November 23, 2013, 01:06:20 PM
Homebrew formulas, Shell scripts, and precompiled binaries have all been updated with cgminer 3.8.3.
November 22, 2013, 10:58:32 AM
Some more information on getting BF1 sticks to work on OS X. As with the Erupter sticks, there is a driver that must be installed for bfgminer to work, and it must be unloaded in order for cgminer to work. With the Erupters these are the UART to USB drivers.
So, in order to get cgminer to detect the BF1 device on OS X, you must unload the following drivers (as stated by other users):
And, in order to get bfgminer to detect the BF1 device, you must load the same drivers:
After you do either you will have to unplug and replug in the BF1 device and then it should be detected by executing either miner with the -d? argument:
So, in order to get cgminer to detect the BF1 device on OS X, you must unload the following drivers (as stated by other users):
Code:
sudo kextunload -b com.apple.driver.AppleUSBCDC
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData
And, in order to get bfgminer to detect the BF1 device, you must load the same drivers:
Code:
sudo kextload -b com.apple.driver.AppleUSBCDC
sudo kextload -b com.apple.driver.AppleUSBCDCACMData
After you do either you will have to unplug and replug in the BF1 device and then it should be detected by executing either miner with the -d? argument:
Code:
bfgminer -d? -S bigpic:all
[2013-11-21 16:38:38] Started bfgminer 3.6.0
[2013-11-21 16:38:38] Devices detected:
[2013-11-21 16:38:38] 0. BPM 0 (driver: bigpic)
1 devices listed
Code:
cgminer -d?
[2013-11-21 16:49:06] Started cgminer 3.8.2
[2013-11-21 16:49:09] Devices detected:
[2013-11-21 16:49:09] 0. BF1 0 (driver: bitfury)
[2013-11-21 16:49:09] 1 devices listed
As another heads up, the ktext unload for cgminer will only last until you reboot, I won't tell you how I know, but trust me I know
November 22, 2013, 10:26:06 AM
I've updated my original post with a list to this new article on mining using Blue & Red Fury ASICs on OS X:
http://blog.nwoolls.com/2013/11/21/bitcoin-mining-on-mac-os-x-bitfury-asics/
http://blog.nwoolls.com/2013/11/21/bitcoin-mining-on-mac-os-x-bitfury-asics/
I will try it once I get home. I remember seeing a new modem driver under dev whenever I connected the BF1, and go away when unloading the drivers, but since I didn't load them back I couldn't make it work.
November 21, 2013, 07:54:34 PM
I've updated my original post with a list to this new article on mining using Blue & Red Fury ASICs on OS X:
http://blog.nwoolls.com/2013/11/21/bitcoin-mining-on-mac-os-x-bitfury-asics/
http://blog.nwoolls.com/2013/11/21/bitcoin-mining-on-mac-os-x-bitfury-asics/
November 21, 2013, 04:46:48 PM
And it does!
Code:
bfgminer version 3.6.0 - Started: [2013-11-21 22:07:55] - [ 0 days 00:01:10]
[M]anage devices [P]ool management [S]ettings [D]isplay options [H]elp [Q]uit
Connected to btc-eu.give-me-coins.com diff 4 with stratum as user xxxxxx
Block: ...bde80cb3 #270814 Diff:609M ( 4.36Ph/s) Started: [22:07:54]
ST:2 F:0 NB:1 AS:0 BW:[ 10/ 0kB/s] E:0.11 I:86.09uBTC/hr BS:477
1 | 2.47/ 2.40/ 2.19Gh/s | A:9 R:0+0(none) HW:2/5.4%
--------------------------------------------------------------------------------
BPM 0: | 2.43/ 2.40/ 2.21Gh/s | A:10 R:0+0(none) HW:2/5.3%
--------------------------------------------------------------------------------
Select processor to manage using up/down arrow keys
BPM 0 : | 1.53/ 2.29/ 2.48Gh/s | A:1 R:0+0(none) HW:0/none
Bitfury BF1 from BFMG
Serial: A49313136333516192D0
[D]isable [I]dentify
[Slash] Find processor [Plus] Add device(s) [Enter] Close device manager
[2013-11-21 22:08:43] Pool 0 is hiding block contents from us
November 21, 2013, 04:45:06 PM
Some more information on getting BF1 sticks to work on OS X. As with the Erupter sticks, there is a driver that must be installed for bfgminer to work, and it must be unloaded in order for cgminer to work. With the Erupters these are the UART to USB drivers.
So, in order to get cgminer to detect the BF1 device on OS X, you must unload the following drivers (as stated by other users):
And, in order to get bfgminer to detect the BF1 device, you must load the same drivers:
After you do either you will have to unplug and replug in the BF1 device and then it should be detected by executing either miner with the -d? argument:
So, in order to get cgminer to detect the BF1 device on OS X, you must unload the following drivers (as stated by other users):
Code:
sudo kextunload -b com.apple.driver.AppleUSBCDC
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData
And, in order to get bfgminer to detect the BF1 device, you must load the same drivers:
Code:
sudo kextload -b com.apple.driver.AppleUSBCDC
sudo kextload -b com.apple.driver.AppleUSBCDCACMData
After you do either you will have to unplug and replug in the BF1 device and then it should be detected by executing either miner with the -d? argument:
Code:
bfgminer -d? -S bigpic:all
[2013-11-21 16:38:38] Started bfgminer 3.6.0
[2013-11-21 16:38:38] Devices detected:
[2013-11-21 16:38:38] 0. BPM 0 (driver: bigpic)
1 devices listed
Code:
cgminer -d?
[2013-11-21 16:49:06] Started cgminer 3.8.2
[2013-11-21 16:49:09] Devices detected:
[2013-11-21 16:49:09] 0. BF1 0 (driver: bitfury)
[2013-11-21 16:49:09] 1 devices listed
November 21, 2013, 04:05:08 PM
I'll have too look for other drivers on the osx side.
As for the ubuntu vm, after installing bfgminer things look more promising:
I'll try and see if it works...
As for the ubuntu vm, after installing bfgminer things look more promising:
Code:
parallels@ubuntu:~/miners/bfgminer$ sudo ./bfgminer -d?
[2013-11-21 22:02:50] Started bfgminer 3.6.0
[2013-11-21 22:02:51] Devices detected:
[2013-11-21 22:02:51] Bitfury BF1 by BFMG (driver=bigpic; procs=1; serial=A49313136333516192D0; path=/dev/ttyACM0)
1 devices listed
I'll try and see if it works...
November 21, 2013, 03:49:26 PM
Just as a heads up, the only way I was able to get cgminer to see my BlueFury under Mac OS 10.7, 10.8 and 10.9 was to 'unload' the new USB modem
sudo kextunload -b com.apple.driver.AppleUSBCDC
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData
Hopefully this will save someone else a LOT of hair pulling
sudo kextunload -b com.apple.driver.AppleUSBCDC
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData
Hopefully this will save someone else a LOT of hair pulling
Finally have a BF1 (Red Fury on-loan) and can confirm this. Before doing this I would get the following error:
Code:
cgminer -d?
[2013-11-21 15:06:02] Started cgminer 3.8.2
[2013-11-21 15:06:03] bitfury detect (93:2) failed to initialise (incorrect device?)
[2013-11-21 15:06:04] Devices detected:
[2013-11-21 15:06:04] 0 devices listed
After unloading both kernel extensions and re-plugging the device cgminer was able to recognize it.
I tried that also. On cgminer (I have v. 3.6.6) I get this:
Code:
willy$ cgminer -d?
[2013-11-21 21:29:51] Started cgminer 3.6.6
[2013-11-21 21:29:51] Icarus detect (253:17) failed to initialise (incorrect device?)
I'm going to try on an Ubuntu virtual machine.... see what happens.
November 21, 2013, 03:36:51 PM
Just as a heads up, the only way I was able to get cgminer to see my BlueFury under Mac OS 10.7, 10.8 and 10.9 was to 'unload' the new USB modem
sudo kextunload -b com.apple.driver.AppleUSBCDC
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData
Hopefully this will save someone else a LOT of hair pulling
sudo kextunload -b com.apple.driver.AppleUSBCDC
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData
Hopefully this will save someone else a LOT of hair pulling
Finally have a BF1 (Red Fury on-loan) and can confirm this. Before doing this I would get the following error:
Code:
cgminer -d?
[2013-11-21 15:06:02] Started cgminer 3.8.2
[2013-11-21 15:06:03] bitfury detect (93:2) failed to initialise (incorrect device?)
[2013-11-21 15:06:04] Devices detected:
[2013-11-21 15:06:04] 0 devices listed
After unloading both kernel extensions and re-plugging the device cgminer was able to recognize it.
I tried that also. On cgminer (I have v. 3.6.6) I get this:
Code:
willy$ cgminer -d?
[2013-11-21 21:29:51] Started cgminer 3.6.6
[2013-11-21 21:29:51] Icarus detect (253:17) failed to initialise (incorrect device?)
[2013-11-21 21:29:51] Icarus detect (253:16) failed to initialise (incorrect device?)
[2013-11-21 21:29:51] Icarus detect (253:14) failed to initialise (incorrect device?)
[2013-11-21 21:29:51] Icarus detect (253:12) failed to initialise (incorrect device?)
[2013-11-21 21:29:51] Icarus detect (253:11) failed to initialise (incorrect device?)
[2013-11-21 21:29:51] Icarus detect (253:10) failed to initialise (incorrect device?)
[2013-11-21 21:29:51] Icarus detect (253:9) failed to initialise (incorrect device?)
[2013-11-21 21:29:51] Icarus detect (253:8) failed to initialise (incorrect device?)
[2013-11-21 21:29:51] Icarus detect (253:6) failed to initialise (incorrect device?)
[2013-11-21 21:29:52] Devices detected:
[2013-11-21 21:29:52] 0. GPU 0 (driver: opencl)
[2013-11-21 21:29:52] 1 devices listed
The 9 devices correspond to the Block erupters (I only use cgminer for LTC)
and on bfgminer:
Code:
iMac-de-willy:~ willy$ bfgminer -S all -d?
[2013-11-21 21:32:26] Started bfgminer 3.6.0
[2013-11-21 21:32:31] Read of fd 10 returned 0
[2013-11-21 21:32:38] Devices detected:
[2013-11-21 21:32:38] 0. ICA 0 (driver: icarus)
[2013-11-21 21:32:38] 1. ICA 1 (driver: icarus)
[2013-11-21 21:32:38] 2. ICA 2 (driver: icarus)
[2013-11-21 21:32:38] 3. ICA 3 (driver: icarus)
[2013-11-21 21:32:38] 4. ICA 4 (driver: icarus)
[2013-11-21 21:32:38] 5. ICA 5 (driver: icarus)
[2013-11-21 21:32:38] 6. ICA 6 (driver: icarus)
[2013-11-21 21:32:38] 7. ICA 7 (driver: icarus)
[2013-11-21 21:32:38] 8. ICA 8 (driver: icarus)
9 devices listed
iMac-de-willy:~ willy$ bfgminer -S bigpic:all -d?
[2013-11-21 21:35:03] Started bfgminer 3.6.0
[2013-11-21 21:35:04] Devices detected:
[2013-11-21 21:35:04] 0. OCL 0 (driver: opencl)
1 devices listed
iMac-de-willy:~ willy$ bfgminer -S BF1:all -d?
[2013-11-21 21:35:11] Started bfgminer 3.6.0
[2013-11-21 21:35:11] Devices detected:
[2013-11-21 21:35:11] 0. OCL 0 (driver: opencl)
I'm going to try on an Ubuntu virtual machine.... see what happens.
November 21, 2013, 03:07:09 PM
Just as a heads up, the only way I was able to get cgminer to see my BlueFury under Mac OS 10.7, 10.8 and 10.9 was to 'unload' the new USB modem
sudo kextunload -b com.apple.driver.AppleUSBCDC
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData
Hopefully this will save someone else a LOT of hair pulling
sudo kextunload -b com.apple.driver.AppleUSBCDC
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData
Hopefully this will save someone else a LOT of hair pulling
Finally have a BF1 (Red Fury on-loan) and can confirm this. Before doing this I would get the following error:
Code:
cgminer -d?
[2013-11-21 15:06:02] Started cgminer 3.8.2
[2013-11-21 15:06:03] bitfury detect (93:2) failed to initialise (incorrect device?)
[2013-11-21 15:06:04] Devices detected:
[2013-11-21 15:06:04] 0 devices listed
After unloading both kernel extensions and re-plugging the device cgminer was able to recognize it.
November 21, 2013, 02:52:39 PM
I have tried everything on my mac but bfgminer doesn't recognize the BlueFury.
I can see it on my system profiler, have installed the latest bfgminer from brew and unloaded the kext's but nothing.... I really don't know what else to do... :-(
I can see it on my system profiler, have installed the latest bfgminer from brew and unloaded the kext's but nothing.... I really don't know what else to do... :-(
Just a shot in the dark, but you may wanna give this a read http://blog.nwoolls.com/2013/07/01/bitcoin-mining-on-mac-os-x-asics/
this line caught my eye "if you are using bfgminer you must install the CP210x USB to UART Bridge VCP driver"
This advice is worth everything you paid for it, as I have yet to play with bfgminer
Yes, I followed all his posts regarding mac mining and everything worked like a charm. Had to install those drivers for the Block Erupters (which work fine by the way)....
I bought this BF1 afterwards and is driving me crazy!
November 21, 2013, 02:44:47 PM
I have tried everything on my mac but bfgminer doesn't recognize the BlueFury.
I can see it on my system profiler, have installed the latest bfgminer from brew and unloaded the kext's but nothing.... I really don't know what else to do... :-(
I can see it on my system profiler, have installed the latest bfgminer from brew and unloaded the kext's but nothing.... I really don't know what else to do... :-(
Open up terminal and type in:
Code:
bfgminer -o [your pool] -u [username] -p [passcode] -S bigpic:all
and see if that works.
I tried that also (just did it again just in case) and it only shows up the GPU
November 21, 2013, 01:42:18 PM
I have tried everything on my mac but bfgminer doesn't recognize the BlueFury.
I can see it on my system profiler, have installed the latest bfgminer from brew and unloaded the kext's but nothing.... I really don't know what else to do... :-(
I can see it on my system profiler, have installed the latest bfgminer from brew and unloaded the kext's but nothing.... I really don't know what else to do... :-(
Just a shot in the dark, but you may wanna give this a read http://blog.nwoolls.com/2013/07/01/bitcoin-mining-on-mac-os-x-asics/
this line caught my eye "if you are using bfgminer you must install the CP210x USB to UART Bridge VCP driver"
This advice is worth everything you paid for it, as I have yet to play with bfgminer
November 21, 2013, 11:11:26 AM
I have tried everything on my mac but bfgminer doesn't recognize the BlueFury.
I can see it on my system profiler, have installed the latest bfgminer from brew and unloaded the kext's but nothing.... I really don't know what else to do... :-(
I can see it on my system profiler, have installed the latest bfgminer from brew and unloaded the kext's but nothing.... I really don't know what else to do... :-(
Open up terminal and type in:
Code:
bfgminer -o [your pool] -u [username] -p [passcode] -S bigpic:all
and see if that works.
November 20, 2013, 03:17:03 PM
I have tried everything on my mac but bfgminer doesn't recognize the BlueFury.
I can see it on my system profiler, have installed the latest bfgminer from brew and unloaded the kext's but nothing.... I really don't know what else to do... :-(
I can see it on my system profiler, have installed the latest bfgminer from brew and unloaded the kext's but nothing.... I really don't know what else to do... :-(
November 18, 2013, 01:08:38 PM
Previous brew installs from your formulae for BFGMiner went off without a hitch, so I wonder if the latest update to libmicrohttpd kills this one. Cleared the download homebrew cache just to be sure it wasnt a corrupt download. Same issue with failing to make libmicrohttpd.
For the time being you can download the bfgminer.rb file and remove the libmicrohttpd dependency and then brew install the local file. It should work fine. I added the libmicrohttpd dependency so that bfgminer would build with stratum proxy support.
Compiled fine using the local rb without the libmicrohttpd dependency. Of course now BFGMiner fails to fully start, which is common for me if I don't physically pull USB cables from the hubs to redetect my BE's. Since I'm remote at the moment, I can't do this, so I'll get back to the thread later with results once I'm able to reset my hubs.
EDIT: Since my non-related issue is with USB BE's, I just started it with my lowly 5770 active instead and was able to start it up fine. So assuming the usual USB cable juggling goes fine later today, then bfgminer should be working fine.
That said, is there anything I can do to get libmicrohttpd to compile properly? Not that I currently need the built-in bfgminer stratum proxy at the moment, but I hate leaving things "undone" as it were. I have no ASICMiner Blades and I run my own P2Pool node, so it's really really not necessary, but I know it's just going to keep tickling the back of my neck.
November 18, 2013, 12:44:39 PM
Previous brew installs from your formulae for BFGMiner went off without a hitch, so I wonder if the latest update to libmicrohttpd kills this one. Cleared the download homebrew cache just to be sure it wasnt a corrupt download. Same issue with failing to make libmicrohttpd.
For the time being you can download the bfgminer.rb file and remove the libmicrohttpd dependency and then brew install the local file. It should work fine. I added the libmicrohttpd dependency so that bfgminer would build with stratum proxy support.
November 18, 2013, 12:42:39 PM
Ok, that last build didn't work out so well.
Uninstalled both bfgminer and libmicrohttpd and tried to brew install libmicrohttpd again.
Got this: https://dl.dropboxusercontent.com/u/11139673/debug/libInstallOut.txt
Previous brew installs from your formulae for BFGMiner went off without a hitch, so I wonder if the latest update to libmicrohttpd kills this one. Cleared the download homebrew cache just to be sure it wasnt a corrupt download. Same issue with failing to make libmicrohttpd.
Uninstalled both bfgminer and libmicrohttpd and tried to brew install libmicrohttpd again.
Got this: https://dl.dropboxusercontent.com/u/11139673/debug/libInstallOut.txt
Previous brew installs from your formulae for BFGMiner went off without a hitch, so I wonder if the latest update to libmicrohttpd kills this one. Cleared the download homebrew cache just to be sure it wasnt a corrupt download. Same issue with failing to make libmicrohttpd.
November 18, 2013, 12:19:04 PM
Main error looks like libmicrohttpd did not build
Here are two output files:
stderr: https://dl.dropboxusercontent.com/u/11139673/debug/brewDebugError.txt
stdout: https://dl.dropboxusercontent.com/u/11139673/debug/brewDebugFile.txt
Hope that helps
Here are two output files:
stderr: https://dl.dropboxusercontent.com/u/11139673/debug/brewDebugError.txt
stdout: https://dl.dropboxusercontent.com/u/11139673/debug/brewDebugFile.txt
Hope that helps
Didn't see much in the way of what caused the failure. Maybe try installing just libmicrohttpd with brew first?
Code:
brew install libmicrohttpd --debug --verbose
I had to brew unlink libmicrohttpd first, re-install it, traceback/ignore an error during make of libmicrohttpd, and then was able to brew upgrade bfgminer successfully.
Of course my remote connection to my Mac at home (I'm at work) decided to keel over, so... I'll let you know if bfgminer is able to startup successfully a little later.
Jump to: