CPU mining is no longer supported. See CGMiner FAQ:
Q: What happened to CPU mining?
A: Being increasingly irrelevant for most users, and a maintenance issue, it is
no longer under active development and will not be supported. No binary builds
supporting CPU mining will be released. Virtually all remaining users of CPU
mining are as back ends for illegal ...
When building the source use:
./configure --enable-cpumining && make
At the end of the configure stage you will see a list of what has been enabled, like this:
Configuration Options ...
Bitcoin Forum > Bitcoin > Mining > Mining software (miners) (Moderators: gmaxwell, MiningBuddy) > CGMINER ASIC FPGA miner monitoring fanspeed RPC linux/win/osx/mip/arm/r-pi 3.9.0
A: The number of Accepted shares
R: The number of Rejected shares
HW: The number of HardWare errors
WU: The Work Utility defined as the number of diff1 equivalent ...
I had the same problem and for me it worked to set the TERM variable to nothing directly before you execute cgminer. Like this in the cmd shell:
If you set it to "" (meaning nothing) in the system settings it will use the default value "c:\windows\system32\cmd.exe". You can check the the variable in the shell with:
Yes, this is related to GPU mining. From cgminer's README:
Intensity correlates with the size of work being submitted at any one
time to a GPU. The higher the number the larger the size of work.
Generally speaking finding an optimal value rather than the highest
value is the correct approach as hash rate rises up to a ...
Apparently I do not have enough points yet to give your answer a vote, but your solution also worked for me! Adding -T to the command line command did the trick. Not only do I now get a neat output of what is happening; the -T parameter also made the entire mining process actually work!
Before adding the -T command:
Screen flashed with the "Started CGMiner ...
My guess is that you did not launch cgminer with the --scrypt option. This is required to mine Litecoin, Dogecoin or any other scrypt coin. When mining scrypt coins that card should deliver ~100 Kh/s in your screen shot it shows Mh/s which would indicate that you are using SHA256 which is for Bitcoin.
You can run cgminer --help to see the options or you can just research them online. A good example is this website: https://github.com/pshep/cgminer
I've never done it but I think you can add a rotate option:
--rotate <arg> Change multipool strategy from failover to regularly rotate at N minutes (default: 0)
80% / 20% would be roughly 19 hours /...
This is probably because hackers install these miners on peoples computers without their knowledge or make a botnet of miners.
Solution to this is placing your miner to ignore-list or get another antivirus like Avira, Avg, or just switch to linux and no need for antivirus anymore.
When you mine solo (not in a pool) then your payout is entirely based on solving the current block in the blockchain before anyone else, and collecting the "bounty" on that block. In Bitcoin terms, the block bounty was 50 BTC at the start of the blockchain, and recently decreased to 25 BTC -- it will continue decreasing steadily until all BTC are mined.
to determine if they're being detected properly, use the 'lsusb' command.
Here's what they should look like if your system is detecting them properly (I run mine in a VM running Ubuntu:
$ sudo lsusb
[sudo] password for majorminer:
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
In my experience scrypt mining on GPUs is quite susceptible to cause HW errors and wrong nonces if the parameters are not chosen to match the GPUs the algorithm is run on. As the SCRYPT-README file of cgminer states:
The reason this is crucial is that too high an intensity can actually
be disastrous with scrypt because it CAN run out of ram. High
OpenCL is not supported on 3xxx series cards. Although it's not completely impossible to mine on a card that old it will be very difficult. Also, a card that old will produce less than 1 MH/s which will only be fractions of bitcoins. I wouldn't waste my time fighting the Radeon 3600.
If you are serious about mining check out the 5xxx and 7xxx series ...
Your intensity is very low (I:8) - dynamic intensity does not work well with scrypt. You will need to increase it manually. You can set a value to use when starting the program by adding --intensity 13 to your command line options/batch file. Replace the number 13 with the desired intensity. For a HD6850, I suggest you try values from 10 to 15.
I am using a slightly overclocked AMD 6850 and get around 270kh/s.
When running cgminer you need to set two environment variables. In windows I use a batch file with the following:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
Timeout is just there so it waits 10 seconds to make sure MSI Afterburner has overclocked the ...
If those are reasonably decent CPUs, they could be able to mine up to 20 Mhash/s each. Together, that's 20 Ghash/s, or the same as a small ASIC, and using massively more electricity.
As of december 2013, with the difficulty at 707408283, this means that you'd have approximately a 0.85% chance per month to win a block (worth 25 BTC).
Yes, the failover setting will tell cgminer to mine on a secondary pool when the first pool is unavailable.
Run cgminer with the following:
cgminer.exe --scrypt -o http://p2pool.org:9327 -u username -p password
--failover-only -o http://backuppool.org -u username -p password
This example mines LTC at p2pool and will mine at another pool of your ...
You can build your miner with a bash command:
$ while true; do bitcoin-cli -regtest generate 1; sleep 300; done
You'l get a block every 5'. If you want a better simulation of mainnet you could use a rndom sleep
The Utility defined as the number of shares / minute
Its the number of shares your miner is contributing per minute. If you're looking at the overall Utility values, its the combined number of shares all miners are contributing per minute.
H-not-zero means the hash of the header isn't zero for the first 32-bits. In other words, it indicates a share that was inherently invalid and could never have been valid. This is generally caused by overclocking, overheating, or undervolting. You can probably get these errors to go away by lowering the clock speed, raising the voltage, or improving your ...
You can use the cgminer -c (config option) to add multiple pools and set up quota system to mine a certain percentage on each pool.
From the CGMiner Readme:
"pools" : [
"url" : "poola:porta",
"user" : "usernamea",
"pass" : "passa"
"quota" : "2;poolb:portb",
cgminer's FPGA and ASIC support was originally taken from BFGMiner. Due to the maintainers of GPU mining being upset over the obsoletion of GPU mining, they forked the project and eventually (poorly) rewrote the FPGA/ASIC drivers. You are seeing the effects of that.
BFGMiner continues to maintain the original (working) drivers, but you will need to remove ...
You need to use cgminer-3.7.2 or earlier. For some reason, GPU mining was removed from subsequent versions.
Cgminer is the best available miner for your purposes. Con Kolivas is one of the world's great programmers, and we are lucky to be able to use his software.
Please also be sure to read the file SCRYPT-README to get reasonable performance.