OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[-ck]

Maybe it is somewhere here in this thread but there are so many posts that i would not find it in a day, so I will just ask.

Why there is so big difference in rejected ratio in CGMiner mining with intensity 13 and with intensity 20? I am mining DigitalCoin (crypt, 20s block time)
When i mine with I 13 my rejection ratio is ~0.5% @ 540kh/s per card.
When i mine with I 20 my rejection ratio is ~7.5% @ 700kh/s per card.

Why is there so big difference? It is caused by CGMiner, by Pool, by connection, ... ? Is there a way to lower rejection ratio with intensity 20?

At intensity 20 it takes forever for your GPU to return its results, so by the time it has returned them, fast chain changing altcoins are all onto their next block. This also explains why orphans are extremely common with fast block coins and why ultimately, they're crap since such a system provides no extra actual security (or fast confirmations since you can't trust any confirmations), just more chain fights.

[Wisher]

plz, help, how to run the autostart cgminer in ubuntu.

[Xmansk]

Maybe it is somewhere here in this thread but there are so many posts that i would not find it in a day, so I will just ask.

Why there is so big difference in rejected ratio in CGMiner mining with intensity 13 and with intensity 20? I am mining DigitalCoin (crypt, 20s block time)
When i mine with I 13 my rejection ratio is ~0.5% @ 540kh/s per card.
When i mine with I 20 my rejection ratio is ~7.5% @ 700kh/s per card.

Why is there so big difference? It is caused by CGMiner, by Pool, by connection, ... ? Is there a way to lower rejection ratio with intensity 20?

At intensity 20 it takes forever for your GPU to return its results, so by the time it has returned them, fast chain changing altcoins are all onto their next block. This also explains why orphans are extremely common with fast block coins and why ultimately, they're crap since such a system provides no extra actual security (or fast confirmations since you can't trust any confirmations), just more chain fights.

And why it takes forever? Why with I 13 it does not take forever? What is different?

[-ck]

Maybe it is somewhere here in this thread but there are so many posts that i would not find it in a day, so I will just ask.

Why there is so big difference in rejected ratio in CGMiner mining with intensity 13 and with intensity 20? I am mining DigitalCoin (crypt, 20s block time)
When i mine with I 13 my rejection ratio is ~0.5% @ 540kh/s per card.
When i mine with I 20 my rejection ratio is ~7.5% @ 700kh/s per card.

Why is there so big difference? It is caused by CGMiner, by Pool, by connection, ... ? Is there a way to lower rejection ratio with intensity 20?

At intensity 20 it takes forever for your GPU to return its results, so by the time it has returned them, fast chain changing altcoins are all onto their next block. This also explains why orphans are extremely common with fast block coins and why ultimately, they're crap since such a system provides no extra actual security (or fast confirmations since you can't trust any confirmations), just more chain fights.

And why it takes forever? Why with I 13 it does not take forever? What is different?

...you're turning the intensity up meaning your handing the GPU many many times more work. GPUs take work, work on it for a while and return results at the end, they're nothing like CPUs. Going up in intensity you're giving it many many many times more work (it's an exponential function to intensity).

[daemondazz]

Does anything need to be done with 3.1.1 for the USB Erruptor?

Code:

root@bitcoin-miner1:~# cgminer -V
cgminer 3.1.1
root@bitcoin-miner1:~# uname -a
Linux bitcoin-miner1 3.2.0-27-generic #43-Ubuntu SMP Fri Jul 6 14:25:57 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
root@bitcoin-miner1:~# cgminer -n
 [2013-06-12 20:04:10] CL Platform 0 vendor: Advanced Micro Devices, Inc.
 [2013-06-12 20:04:10] CL Platform 0 name: AMD Accelerated Parallel Processing
 [2013-06-12 20:04:10] CL Platform 0 version: OpenCL 1.2 AMD-APP (1016.4)
 [2013-06-12 20:04:10] Platform 0 devices: 1
 [2013-06-12 20:04:10]  0       Tahiti
 [2013-06-12 20:04:10] GPU 0 AMD Radeon HD 7900 Series  hardware monitoring enabled
 [2013-06-12 20:04:10] 1 GPU devices max detected
 [2013-06-12 20:04:10] USB all: found 6 devices - listing known devices
 [2013-06-12 20:04:10] No known USB devices
root@bitcoin-miner1:~# ls /dev/ttyUSB0
/dev/ttyUSB0

I'm running with

Code:

/usr/local/bin/cgminer --auto-fan --auto-gpu --syslog -T --gpu-engine 1100 --gpu-memdiff -150 -I 10 --icarus-options 115200:1:1 --icarus-timing 3.0=80 -o stratum+tcp://cryptominer.org:9332 -u xxxx -p xxxx

The machine also has a Gigabyte 9750 in it which is merrily hashing away.


EDIT: Nevermind, I missed the "-S /dev/ttyUSB0" - It appears to be working now.

[os2sam]

When I press Q to quit CGMiner 3.2.1 most of the time it crash's.  Once out of 3 or 4 times does it display the summary when pressing Q.

Win7 32bit running cgminer-nogpu.
Thanks,
Sam

[os2sam]

I'm trying to disable two AMU's, out of 4 total, in each CGMiner session.

"-d 0 -d 1 --remove-disabled" in the first session works fine.
"-d 2 -d 3 --remove-disabled" in the second session does not work.

when I run CGMiner-nogpu -n it says "failed to open, err -3"

It appears that you intend for CGMiner to be able to do this and I would like to run two sessions for two different pools.
Thanks,
Sam

[Xmansk]

And why it takes forever? Why with I 13 it does not take forever? What is different?

...you're turning the intensity up meaning your handing the GPU many many times more work. GPUs take work, work on it for a while and return results at the end, they're nothing like CPUs. Going up in intensity you're giving it many many many times more work (it's an exponential function to intensity).

So basically my higher hashrate at intensity 20 is caused because GPU use all availiabe resources to solve work so it solve more work, but it does not do it faster? If so, I should try to find highest possible hashrate at intensity 13.

[os2sam]

And why it takes forever? Why with I 13 it does not take forever? What is different?

...you're turning the intensity up meaning your handing the GPU many many times more work. GPUs take work, work on it for a while and return results at the end, they're nothing like CPUs. Going up in intensity you're giving it many many many times more work (it's an exponential function to intensity).

So basically my higher hashrate at intensity 20 is caused because GPU use all availiabe resources to solve work so it solve more work, but it does not do it faster? If so, I should try to find highest possible hashrate at intensity 13.

You probably should use trial and error find the intensity that gives you the best combination of hash rate, low error rate and best U:/WU:

[-ck]

I'm trying to disable two AMU's, out of 4 total, in each CGMiner session.

"-d 0 -d 1 --remove-disabled" in the first session works fine.
"-d 2 -d 3 --remove-disabled" in the second session does not work.

when I run CGMiner-nogpu -n it says "failed to open, err -3"

It appears that you intend for CGMiner to be able to do this and I would like to run two sessions for two different pools.
Thanks,
Sam

The --usb command gives you finer control over this. The --device command only takes one set of values now (-d 0-1 instead of -d 0 -d 1) and only works for usb devices since version 3.2.1, and it is a coarse command.

[os2sam]

I'm trying to disable two AMU's, out of 4 total, in each CGMiner session.

"-d 0 -d 1 --remove-disabled" in the first session works fine.
"-d 2 -d 3 --remove-disabled" in the second session does not work.

when I run CGMiner-nogpu -n it says "failed to open, err -3"

It appears that you intend for CGMiner to be able to do this and I would like to run two sessions for two different pools.
Thanks,
Sam

The --usb command gives you finer control over this. The --device command only takes one set of values now (-d 0-1 instead of -d 0 -d 1) and only works for usb devices since version 3.2.1, and it is a coarse command.

Ah, in other words RTFM .  I found the section in the readme and I'll give it a whirl tonight.
Thanks,
Sam

[os2sam]

The --usb command gives you finer control over this. The --device command only takes one set of values now (-d 0-1 instead of -d 0 -d 1) and only works for usb devices since version 3.2.1, and it is a coarse command.

I went ahead and tried it now.

"--usb 5:1,5:2" in one instance
"--usb 3:1,3:2" in the other instance

Both hashing away just fine.  Now I can more objectively compare pools.
Thanks,
Sam

[Tamis]

Are there any reasons to update from 3.1.1 to 3.2.1 if you are only using gpus ?

[bitcoindaddy]

The --usb command gives you finer control over this. The --device command only takes one set of values now (-d 0-1 instead of -d 0 -d 1) and only works for usb devices since version 3.2.1, and it is a coarse command.

I went ahead and tried it now.

"--usb 5:1,5:2" in one instance
"--usb 3:1,3:2" in the other instance

Both hashing away just fine.  Now I can more objectively compare pools.
Thanks,
Sam

Is that all that is necessary to run multiple instances or is there other "secret sauce"?  What do  the number mean?

[turtle83]

The --usb command gives you finer control over this. The --device command only takes one set of values now (-d 0-1 instead of -d 0 -d 1) and only works for usb devices since version 3.2.1, and it is a coarse command.

I went ahead and tried it now.

"--usb 5:1,5:2" in one instance
"--usb 3:1,3:2" in the other instance

Both hashing away just fine.  Now I can more objectively compare pools.
Thanks,
Sam

Is that all that is necessary to run multiple instances or is there other "secret sauce"?  What do  the number mean?

i believe the number is bus:device.

so "5:1" means device 1 on bus 5. on linux lsusb shows you the bus and device number for each usb device.

[salfter]

I went to switch back to Bitcoin mining yesterday on a box that had been mining altcoins with cgminer 3.2.1 (built on an amd64 Gentoo box with a source tarball pulled from https://github.com/ckolivas/cgminer/archive/v3.2.1.tar.gz.  I have these pools configured in cgminer.conf:

Code:

"pools" : [
        {
                "url" : "stratum+tcp://mint.bitminter.com:3333/",
                "user" : "salfter_lanbox",
                "pass" : "**redacted**"
        },
        {
                "url" : "stratum+tcp://us.eclipsemc.com:3333/",
                "user" : "salfter_lanbox",
                "pass" : "**redacted**"
        }
]

The config file was unchanged from when I last used it.  cgminer 3.2.1 produces this error on startup:

Code:

 [2013-06-12 09:04:09] Started cgminer 3.2.1
 [2013-06-12 09:04:09] Started cgminer 3.2.1
 [2013-06-12 09:04:09] Loaded configuration file /home/salfter/.cgminer/cgminer.
conf
 [2013-06-12 09:04:10] Probing for an alive pool
 [2013-06-12 09:04:10] Failed to resolve (?wrong URL) us.eclipsemc.com:3333/
 [2013-06-12 09:04:10] Failed to resolve (?wrong URL) mint.bitminter.com:3333/

When I downgraded to cgminer 3.1.0, it runs like a champ.  I've used cgminer 3.2.1 to mine altcoins on stratum pools...but I just noticed that the URLs for those pools don't have trailing slashes, while the ones for the Bitcoin pools do:

Code:

salfter@lanbox ~ $ grep stratum .cgminer/cgminer.conf.*
.cgminer/cgminer.conf.bitcoin:         "url" : "stratum+tcp://mint.bitminter.com:3333/",
.cgminer/cgminer.conf.bitcoin:         "url" : "stratum+tcp://us.eclipsemc.com:3333/",
.cgminer/cgminer.conf.digitalcoin:              "url" : "stratum+tcp://dgcpool.com:3333",
.cgminer/cgminer.conf.digitalcoin:              "url" : "stratum+tcp://pool.digicoinpool.com:3344",
.cgminer/cgminer.conf.feathercoin:              "url" : "stratum+tcp://stratum.wemineftc.com:4444",
.cgminer/cgminer.conf.feathercoin:              "url" : "stratum+tcp://pool.fcpool.com:3334",
.cgminer/cgminer.conf.feathercoin:              "url" : "stratum+tcp://feathercoin.is-a-geek.com:3333",
.cgminer/cgminer.conf.litecoin:         "url" : "stratum+tcp://us.wemineltc.com:80",
.cgminer/cgminer.conf.litecoin:         "url" : "stratum+tcp://eu.wemineltc.com:3333",
.cgminer/cgminer.conf.worldcoin:                "url" : "stratum+tcp://wdc-eu.epools.org:3334",

I think cgminer 3.2.1 might not like the trailing slash, while previous versions didn't care.

[-ck]

[2013-06-12 09:04:10] Failed to resolve (?wrong URL) us.eclipsemc.com:3333/
 [2013-06-12 09:04:10] Failed to resolve (?wrong URL) mint.bitminter.com:3333/

Get rid of the trailing slashes.

[turtle83]

How to get the network difficulty per coin or pool?

I am using cgminer with multiple pools for different coins. Then using the API to control which pool is currently active (all sha256). But, I want to query a particular coins current difficulty. Is it possible?

the pool command gives output like http://pastie.org/private/c2qa7mv7dsncpnyxkcryoa for each pool. No difficulty.
the coin command gives

Code:

{u'COIN': [{u'Current Block Hash': u'xxxxSNIPxxxx',
   u'Current Block Time': 1371063749.732006,
   u'Hash Method': u'sha256',
   u'LP': True,
   u'Network Difficulty': 295934.4819144}],
 u'STATUS': [{u'Code': 78,
   u'Description': u'cgminer 3.1.1',
   u'Msg': u'CGMiner coin',
   u'STATUS': u'S',
   u'When': 1371064803}],
 u'id': 1}

Which i presume belongs to the current active pool (ppcoin).

Q1: Is it possible to get 'Network Difficulty' in pool output?
Q2: Is it possible to create our own "coin" objects and associate pools to a coin? If so how?

Apologies if its been asked before, i couldn't find a solution.

[crazyates]

I am using cgminer with multiple pools for different coins.

Taken straight from the first paragraph of the README:

Do not use on multiple block chains at the same time!

[turtle83]

I am using cgminer with multiple pools for different coins.

Taken straight from the first paragraph of the README:

Do not use on multiple block chains at the same time!

Hmm.. i thought adding "--failover-only" makes any pool mixup go away? havent noticed any issues doing it this way... and restarting cgminer takes minutes (~4 seconds per fpga each configured serially).