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 ...
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.
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 ...
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.
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
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.
to maps gpus i use this script:
cgminer -n option
Timeout /t 3600
Make it a .bat file and put it in the same folder as you cgminer, then you can tell witch gpu that is 0,1,2...
but you have to turn off power saving in windows to prevent you 280x form sleep, if you don't have a dummy-plug or an screen put to that device.
I used this guide for all start ...
cgminer is a command-line software.
Open a Terminal and change the working directory to where you have your cgminer executable with the cd command. For example, if you have it on the Desktop you have to use the following command: cd ~/Desktop (where ~ indicates your home directory).
Then, if necessary, mark it as an executable file with the chmod +x ...
I think these are the settings you are looking for. Changing "url" to "quota" and specifying the amounts in the format "AMOUNT;URL". It makes it easier to use percents, but it isn't a requirement. For example you could use a quota of 8 for pool1 and 2 for pool2.
"pools" : [
"quota" : "80;http://pool1",
"user" : "user1",
"pass" : "...
I recommend using bfgminer, and so does Butterfly Labs. Well, I guess they say cgminer will work, too :P.
The 4.10/4.3 branch, as well as the latest/master branch, work especially well with the Jalapeños and the Monarchs.
sudo apt-get install build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev ...
Have you tried the command -d 0,1, then setting your Thread Concurrency and Looup-gap and worksize for each device accordingly.
You need to tell CGMiner you have two GPUs and set the thread concurrency for them. For this, try a command like this: ./cgminer --scrypt -o stratum+tcp://my.pool.ip:xxxx -u myusername -p mypassword -d 0,1 -I 18,19 -g 1 -w 256 --...
Might as well give this old question an answer.
cgminer 3.7.2 (which was obsolete even when this question was asked) required scrypt to be enabled as a compile-time option with ./configure --enable-scrypt. The asker evidently did not enable it, which is why it does not work.
It appears that current versions of cgminer have removed scrypt support ...
Are you running "bitcoin-cli submitblock xyz" manually? You are not supposed to do this. Software does this. If you mine in a pool you don't even need to run bitcoind at all.
If you do want to run your own bitcoind node, don't mess with the blk*.dat files. You don't need to touch them. The bitcoind program is the only thing that needs to use them.
If you ...
Check your rpcallowip configuration, you will need to explicitly allow connections incoming to your RPC port from the network. If your local network for example is 192.168.0.x, the rpcallowip configuation in your bitcoin.conf will need to be 192.168.0.0/24 (this is CIDR notation).
Read the cgminer documentation about "solo mining". You'll need to install and set up bitcoind and sync the entire block chain, so see its documentation as well.
As far as payouts, note the --btc-address command line option to cgminer; that specifies the address to which the reward will be sent.
CGMiner no longer has support for GPU or CPU mining at all. You are currently not mining anything. In order to do GPU mining, you will need to either compile it yourself to support GPU mining or get an ASIC or get an older version of CGMiner that supports GPU mining or find a fork of it that supports GPU mining.