Sorry guys I've had a little crisis IRL but I'll get to updating things today or tomorrow.
The issue you're having sounds to me like the device got a different name on reconnect or restart, it's unusual to jump from no enumeration to number 9 so I'd guess it's changed to 1 or 2.
Just paste
ls -l /dev/cu.*
in Terminal and it should show you what's connected.
Topic: The official MacMiner thread [BTC/LTC-CPU/GPU/FPGA/ASIC] - page 32. (Read 166740 times)
And the weirdness returns.
Earlier, I was trying to get the two USB miners set up with BFGMiner or FPGA/ASIC. In FPGA/ASIC I included this flag:
-S /dev/cu.SLAB_USBtoUART9 -S /dev/cu.SLAB_USBtoUART
because the -S all didn't work for me.
Well, today I restart the miner and it's only finding one of the two USB devices in BFGMiner and FPGA/ASIC. I pulled the one that is working (according to the LED) just to see if the other one went bad somehow. Nope, it too gets recognized and put to work.
The Mac System Profiler shows both devices being plugged in.
For grins, I tried -S all again, got nothing. Also tried "switching" the USBtoUART9 to the second flag in the command, didn't make a difference.
Not necessarily asking for a solution here (although I wouldn't kick one out of bed), but just wanted to provide the info in case it helps anyone else fill in any blanks.
Earlier, I was trying to get the two USB miners set up with BFGMiner or FPGA/ASIC. In FPGA/ASIC I included this flag:
-S /dev/cu.SLAB_USBtoUART9 -S /dev/cu.SLAB_USBtoUART
because the -S all didn't work for me.
Well, today I restart the miner and it's only finding one of the two USB devices in BFGMiner and FPGA/ASIC. I pulled the one that is working (according to the LED) just to see if the other one went bad somehow. Nope, it too gets recognized and put to work.
The Mac System Profiler shows both devices being plugged in.
For grins, I tried -S all again, got nothing. Also tried "switching" the USBtoUART9 to the second flag in the command, didn't make a difference.
Not necessarily asking for a solution here (although I wouldn't kick one out of bed), but just wanted to provide the info in case it helps anyone else fill in any blanks.
That was 3.1.1; I'm pretty sure I fixed it in 3.1.2 
Awesome, I'll roll out 3.1.3, thanks! 
-S all I think doesn't work at all on Mac but I really should take a look at the bfgminer code and see if that's something easily fixed.
It should work fine.Just autodetect won't work (ie, without any -S).
https://bitcointalksearch.org/topic/m.2715334
said it didn't work till he specified the device. Does the fpgautils.c check /dev/cu.*?
-S all I think doesn't work at all on Mac but I really should take a look at the bfgminer code and see if that's something easily fixed.
It should work fine.Just autodetect won't work (ie, without any -S).
When I tested it out by running in command line, -S all only activated the GPU.
Running ./bfgminer -S all -d? only showed 1 device (opencl).
So I had to specify each /dev/cu.SLAB_USBtoUART(X)
-S all I think doesn't work at all on Mac but I really should take a look at the bfgminer code and see if that's something easily fixed.
It should work fine.Just autodetect won't work (ie, without any -S).
https://bitcointalksearch.org/topic/m.2715334
said it didn't work till he specified the device. Does the fpgautils.c check /dev/cu.*?
-S all I think doesn't work at all on Mac but I really should take a look at the bfgminer code and see if that's something easily fixed.
It should work fine.Just autodetect won't work (ie, without any -S).
Ah sorry I need to update the FPGA/ASIC miner interface I haven't personally tested it thoroughly enough as I don't have FPGA/ASIC yet. For now you could leave GPU box checked and use custom flag -G to disable to GPU in one or the other. The config file needs to be changed not just for FPGA/ASIC miner but CG window too. next update!
One other problem with FPGA/ASIC miner as it stands is that it's currently only set up to display up to 4 devices temperatures. I'll get on that fast but you can run as many instances of MacMiner as you like as long as one of them is called MacMiner and in the Applications folder.
-S all I think doesn't work at all on Mac but I really should take a look at the bfgminer code and see if that's something easily fixed.
If I wasn't worried about temps I would probably keep it all in one window and keep an eye on the log and total hash rate. I'll make big improvements to running that way once my jalapeño ships (currently in production) and I'll apply those more important fixes sooner!
One other problem with FPGA/ASIC miner as it stands is that it's currently only set up to display up to 4 devices temperatures. I'll get on that fast but you can run as many instances of MacMiner as you like as long as one of them is called MacMiner and in the Applications folder.
-S all I think doesn't work at all on Mac but I really should take a look at the bfgminer code and see if that's something easily fixed.
If I wasn't worried about temps I would probably keep it all in one window and keep an eye on the log and total hash rate. I'll make big improvements to running that way once my jalapeño ships (currently in production) and I'll apply those more important fixes sooner!
What's the best way to run the following all connected to one Mac Pro:
Would it be better to have them all active through a single instance of the FPGA/ASIC Miner (really BFGMiner with selected Diablo kernel for the GPU) with one worker set or should I break the different systems into 2 or three instances of bfgminer with different worker settings for each instance? Outside of ability to see if one type of device is having problems, are there any speed benefits to separating the threads between multiple instances for each class/speed of device group?
Right now I'm using a single instance of the FPGA/ASIC miner for GPU and Block Erupters. I have to specify each device since autodetect and "-S all" did not work, and I'm using the recommended Icarus settings I've seen in other threads.
Also I noticed that when I have both BFGMiner and the FPGA/ASIC version running, they seem to use the same config file and settings instead of being isolated. For instance if you check the No GPU box in one, it's set for the other. Hardly ideal when you want to use both.
Thanks!
- one 5770 GPU inside the Mac
- 8x Block Erupters on an Anker Hub
- BFL SC ASICs (starting with an upgraded Jalapeño and also getting a 25GH box)
Would it be better to have them all active through a single instance of the FPGA/ASIC Miner (really BFGMiner with selected Diablo kernel for the GPU) with one worker set or should I break the different systems into 2 or three instances of bfgminer with different worker settings for each instance? Outside of ability to see if one type of device is having problems, are there any speed benefits to separating the threads between multiple instances for each class/speed of device group?
Right now I'm using a single instance of the FPGA/ASIC miner for GPU and Block Erupters. I have to specify each device since autodetect and "-S all" did not work, and I'm using the recommended Icarus settings I've seen in other threads.
Also I noticed that when I have both BFGMiner and the FPGA/ASIC version running, they seem to use the same config file and settings instead of being isolated. For instance if you check the No GPU box in one, it's set for the other. Hardly ideal when you want to use both.
Thanks!
Anonymailer, could you take a look at this thread:
https://bitcointalksearch.org/topic/m.2715334
I have tried to post here before for a couple of days but the damn forum software keeps giving me error messages (and I expect another one when I try to post this time!!!!)
Thanks!
https://bitcointalksearch.org/topic/m.2715334
I have tried to post here before for a couple of days but the damn forum software keeps giving me error messages (and I expect another one when I try to post this time!!!!)
Thanks!
Yeah it's a bit like switching to linux doing it that way, I'm glad it's helping people out
Thanks for making this my friend! All that homebrew stuff was confusing the hell out of me 
1.4.3 beta just released fixes and improves a few things, unfortunately the update mechanism is one of them as that was broken in the 1.4.2 beta so this one will need to be downloaded directly:
http://fabulouspanda.co.uk/macminer/downloads/MacMiner.app-1.4.3.zip
http://fabulouspanda.co.uk/macminer/downloads/MacMiner.app-1.4.3.zip
I think I'll go with a new window, it could be good to have all the miners together for people using more than one (like me!). Larger numbers of devices are a bit tricky but with a few sort options it should work well…
Either incorporated or a new window would work for me... as long as there was a way to see what devices are recognized/running, the HW errors, current Hashrates, what pool they're chugging for, and Accepted/Rejected.
Would there be an issue with a single shared window if you have multiple miners running, i.e. the ASIC/FPGA Miner for BTC and CPU Miner for LTC (probably a bad example since CPU miner would only be running on CPU threads)?
Actually, a separate window would probably work best for larger mining farms (like people with hubs full of Block Erupters).
Would there be an issue with a single shared window if you have multiple miners running, i.e. the ASIC/FPGA Miner for BTC and CPU Miner for LTC (probably a bad example since CPU miner would only be running on CPU threads)?
Actually, a separate window would probably work best for larger mining farms (like people with hubs full of Block Erupters).
Thanks for letting me know, I don't think 1.4 will spend quite as long in beta as 1.3 did! And thanks for ticking the profile box, that'll help me improve the recommended defaults
I will make sure to get individual device stats in there. What are the most important figures for you? Speed, accepts and rejects? At the moment I'm torn between adding each device to the specific miner window or having a new window with a summary of all devices regardless of which miner(s) you're using.
I will make sure to get individual device stats in there. What are the most important figures for you? Speed, accepts and rejects? At the moment I'm torn between adding each device to the specific miner window or having a new window with a summary of all devices regardless of which miner(s) you're using.
The 1.4.2 beta is running pretty well for me right now... the anonymous hardware and hash rate profile checkbox is checked so I hope that helps.
Feature Request: I see all these screenshots of BFGMiner and CGMiner on the commandline with some running stats in the header for processing devices (GPU, BFL, ICA, etc.) and their associated stats. Can we get that piped into the Header interfaces for MacMiner's BFG Miner and FPGA/ASIC Miner? That would help flag issues or slowdowns with individual Block Erupters or (if you were blessed by the Shipping Gods) a Jalapeno.
Thanks!
Feature Request: I see all these screenshots of BFGMiner and CGMiner on the commandline with some running stats in the header for processing devices (GPU, BFL, ICA, etc.) and their associated stats. Can we get that piped into the Header interfaces for MacMiner's BFG Miner and FPGA/ASIC Miner? That would help flag issues or slowdowns with individual Block Erupters or (if you were blessed by the Shipping Gods) a Jalapeno.
Thanks!
1.4.2 beta improves the recommended BFG settings introduced in 1.4.1
Please check the 'submit anonymous hardware and hash rate profile' box in the preferences window in order to help improve recommended values further!
Please check the 'submit anonymous hardware and hash rate profile' box in the preferences window in order to help improve recommended values further!
The just released 1.4 beta updates cpuminer to the latest version:
http://fabulouspanda.co.uk/macminer/downloads/MacMiner.app-1.4.zip
http://fabulouspanda.co.uk/macminer/downloads/MacMiner.app-1.4.zip
Ah, I didn't realise there had been big changes! If you'd like to use MacMiner with the latest version you can chuck a copy from here
http://sourceforge.net/projects/cpuminer/?source=dlp
in /Applications/MacMiner.app/Contents/Resources
called minerd
and it should still work, though I'm not sure what systems that version has been compiled for! I gave it a shot and it's running… same as before
http://sourceforge.net/projects/cpuminer/?source=dlp
in /Applications/MacMiner.app/Contents/Resources
called minerd
and it should still work, though I'm not sure what systems that version has been compiled for! I gave it a shot and it's running… same as before
Jump to: