Cgminer litecoin mac os x
The first parameter to focus on is the -I parameter, or the intensity. With Bitcoin this parameter does help, but honestly not a ton. This is not the case with Litecoin mining.
On my system, is about the best I can do. The next parameter to focus on is the -w parameter, which specifies a worksize in multiples of 64 up to This parameter is what really makes a difference on my OS X rig:. The last parameter I want to note is —thread-concurrency. If cgminer or bfgminer are reporting hardware errors the HW number in the output this indicates that you need to make use of the —thread-concurrency parameter.
These are not hardware failures. You can find guidelines for the value to use here:. Ideal values are or Find your bus width here. The growing landscape of crypto-currency is fascinating from many perspectives.
If your interest is piqued and you are running OS X, hopefully you now have the information you need in order to get started mining this new form of currency. Starting with version 3. Additionally, bfgminer now requires an additional argument in order to enable GPU mining. If you wish to use bfgminer for GPU mining you will need to add the following argument:.
Thanks for the excellent guides on starting mining on a Mac. I have been trying it out over the weekend on a couple of different laptops, one Air and one Pro. Obviously, neither of them are heavy hitters but the experimentation is quite fun. I found MacMiner to be better than doing homebrew installs, surprisingly. It gives a cryptic OpenCL initialization error: Enqueueing kernel onto command queue.
Finally was able to get Cgminer to compile and install correctly for Lion.. Try a worksize of 64 instead of Also, try removing the lookup-gap. If things are stable then start upping the intensity. Thanks for the reply! If i take the intensity past 12 the computer freezes up: I read to add these lines in the terminal before the scrypt: Hey, I need some help. Thanks for the article. Where does one get a username and password for the Terminal commands please? Can I use this setup for Feathercoin?
How do I indicate it to mine feathercoin and not litecoin. It should work as long as your arguments are valid for Scrypt mining. Litecoin and Feathercoin should work the same. What sort of problems are you having? I have one problem proceeding with cgminer 3. This had me stumped for a couple of hours today. As can be seen here: When you try to install it you will get a SHA-hash error. Avalon 4 updates to use less power. Fix the BET driver not being able to restart a new instance when the first fails.
Basic FreeBSD compilation support. Other minor build changes and fixes for potential issues. Formatting fixes for miner. This has been proven effective at bringing back U1 miners that stop hashing. Hopefully this might increase compatibility with some USB3 hubs on windows and make it more reliable based on the changelogs I can see in libusb.
This is the reason for the minor version number update to 12 as it's quite a substantial code change, hopefully only for the better! Hopefully he can give us a summary of the changes there. This is useful if you are trying to determine if a device is dead for device reasons or simply isn't getting work from any pools. If "Last getwork" is not incrementing, there is no work for any devices. Note that the default was 54 so is now 50 to be in keeping with USB2 power limit standards.
The driver is otherwise unchanged so any other differences you see are pure variance. With water cooling they usually drop in temperature very rapidly. This can be configured with --hfa-temp-overheat -- Hashrate displayed will be based on valid shares returned so should more accurately represent what the pool will see you hashing at.
It will look very unstable initially. Earlier boards do have some loss so the previously displayed hashrate was always over. You can compare the total hashes estimated by this as "Calc hashcount" to compare with "Raw hashcount" the device has worked on in the API stats to see how they differ. Custom devices will come up with the generic HFA name. Note that if you are trying to select them with the --usb command, they are all seen as HFA due to the fact that cgminer can only tell them apart after they have been initialised and running.
More info about this from him hopefully.