OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 297.

narousberg

legendary

Activity: 1754

Merit: 1007

Quote from: jesse11 on June 12, 2013, 05:29:37 PM

Here, give this a shot

C:\cgminer\cgminer-nogpu.exe -o [pool]:[port] -u [username].[worker] -p [password] --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S //./COM3 -S //./COM4 -S //./COM5 -S //./COM6

this dont help. Same problem. Cgminer answer with -S unrecognized option

jesse11

sr. member

Activity: 333

Merit: 250

Ants Rock

Here, give this a shot

C:\cgminer\cgminer-nogpu.exe -o [pool]:[port] -u [username].[worker] -p [password] --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S //./COM3 -S //./COM4 -S //./COM5 -S //./COM6

narousberg

legendary

Activity: 1754

Merit: 1007

HI guys
I have tryed cgminer 3.2.1 for my ZTEX 1.15y on Windows 7
WinUSB driver installed with Zadig.
But i have a problem to start cgminer with more then 4 boards. Program dont want start if i connect 5 and more boards.
Please help

bitcoindaddy

hero member

Activity: 481

Merit: 500

current cgminer (git):

SEM: Icarus USB failed to release '/tmp/cgminer-usb-2-7' err (11) Resource temporarily unavailable

on USB block erupter

Edit: the worst part isn't the fact that there are zombies, it's that sometimes, one stops working, the green light comes on, and it never recovers again.

[2013-06-12 18:30:14] AMU0: Comms error (werr=-9 amt=0)
[2013-06-12 18:30:14] AMU 0 failure, disabling!
[2013-06-12 18:30:14] Thread 0 being disabled
[2013-06-12 18:30:16] AMU0: Comms error (rerr=-9 amt=0)
[2013-06-12 18:30:16] SEM: Icarus USB failed to release '/tmp/cgminer-usb-2-3' err (11) Resource temporarily unavailable
[2013-06-12 18:30:16] FAIL: USB remove not already in use (2:3)

turtle83

sr. member

Activity: 322

Merit: 250

Supersonic

Quote from: The00Dustin on June 12, 2013, 03:47:49 PM

Quote from: The00Dustin on June 12, 2013, 03:45:44 PM

Quote from: turtle83 on June 12, 2013, 03:43:02 PM

Right, i use "--failover-only", and then "switchpool" command to set which pool i want to mine at. The logs and display show that its only mining the pool i want it to. and if this pool is down, it failsover to something else. Works like i want it to, I dont "feel" there is any issue in terms of payouts or smthn...

I believe failover-only still communicates with the failover pools. You can verify this with netstat. Switches depend on OS and what you know about the output / want to see.

More importantly, if it wasn't communicating with them, then it wouldn't know the difficulty, defeating what you are trying to do to begin with. IOW, for what you are trying to do to possibly work, all but the "currently active" pool would need to be disabled, and you would need to poll the difficulty from the wallets, all of which would need to be accessible from your polling application (either locally or over the network).

Hmm makes sense http://pastie.org/private/c2qa7mv7dsncpnyxkcryoa is from a pool thats not "currently active".

Code:

 'Status': u'Alive',
 'Stratum Active': False,

When i switch to this pool it uses stratum only. But here its showing it as Alive, and stratum to be inactive. Will need to tcpdump to see if difficulty info is being passed along for inactive pools or not.

I have been using wallet to get difficulty information, but would like to remove wallet dependency. I use raspberry pi to mine which is incapable of running wallets. Currently i run the wallet on my desktop, but I want to shut down the desktop for few weeks.

The difficulty from block explorer sites (basically getdifficulty method) shows the difficulty of the last block mined, not the current network difficulty.

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: The00Dustin on June 12, 2013, 03:45:44 PM

Quote from: turtle83 on June 12, 2013, 03:43:02 PM

Right, i use "--failover-only", and then "switchpool" command to set which pool i want to mine at. The logs and display show that its only mining the pool i want it to. and if this pool is down, it failsover to something else. Works like i want it to, I dont "feel" there is any issue in terms of payouts or smthn...

I believe failover-only still communicates with the failover pools. You can verify this with netstat. Switches depend on OS and what you know about the output / want to see.

More importantly, if it wasn't communicating with them, then it wouldn't know the difficulty, defeating what you are trying to do to begin with. IOW, for what you are trying to do to possibly work, all but the "currently active" pool would need to be disabled, and you would need to poll the difficulty from the wallets, all of which would need to be accessible from your polling application (either locally or over the network).

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: turtle83 on June 12, 2013, 03:43:02 PM

Right, i use "--failover-only", and then "switchpool" command to set which pool i want to mine at. The logs and display show that its only mining the pool i want it to. and if this pool is down, it failsover to something else. Works like i want it to, I dont "feel" there is any issue in terms of payouts or smthn...

I believe failover-only still communicates with the failover pools. You can verify this with netstat. Switches depend on OS and what you know about the output / want to see.

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: ak49er on June 12, 2013, 03:30:59 PM

But he's only got one active pool at a time via the API, (at least I asusme it's just one pool), so does this warning still stand?

Depends on his definition of "active". If the other pools are all disabled and cgminer isn't communicating with them, it would work fine, in theory. However, in any other scenario, where cgminer is communicating with them, it will see new blocks that aren't part of the chain it is mining.

turtle83

sr. member

Activity: 322

Merit: 250

Supersonic

Quote from: ak49er on June 12, 2013, 03:30:59 PM

Quote from: crazyates on June 12, 2013, 02:46:11 PM

Quote from: turtle83 on June 12, 2013, 02:20:53 PM

I am using cgminer with multiple pools for different coins.

Taken straight from the first paragraph of the README:

Quote

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

But he's only got one active pool at a time via the API, (at least I asusme it's just one pool), so does this warning still stand?

Right, i use "--failover-only", and then "switchpool" command to set which pool i want to mine at. The logs and display show that its only mining the pool i want it to. and if this pool is down, it failsover to something else. Works like i want it to, I dont "feel" there is any issue in terms of payouts or smthn...

ak49er

sr. member

Activity: 672

Merit: 250

Buy, sell and store real cryptocurrencies

Quote from: crazyates on June 12, 2013, 02:46:11 PM

Quote from: turtle83 on June 12, 2013, 02:20:53 PM

I am using cgminer with multiple pools for different coins.

Taken straight from the first paragraph of the README:

Quote

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

But he's only got one active pool at a time via the API, (at least I asusme it's just one pool), so does this warning still stand?

turtle83

sr. member

Activity: 322

Merit: 250

Supersonic

Quote from: crazyates on June 12, 2013, 02:46:11 PM

Quote from: turtle83 on June 12, 2013, 02:20:53 PM

I am using cgminer with multiple pools for different coins.

Taken straight from the first paragraph of the README:

Quote

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).

crazyates

legendary

Activity: 952

Merit: 1000

Quote from: turtle83 on June 12, 2013, 02:20:53 PM

I am using cgminer with multiple pools for different coins.

Taken straight from the first paragraph of the README:

Quote

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

turtle83

sr. member

Activity: 322

Merit: 250

Supersonic

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.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: salfter on June 12, 2013, 11:13:01 AM

[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.

salfter

hero member

Activity: 651

Merit: 501

My PGP Key: 92C7689C

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.

turtle83

sr. member

Activity: 322

Merit: 250

Supersonic

Quote from: bitcoindaddy on June 12, 2013, 10:16:41 AM

Quote from: os2sam on June 12, 2013, 07:01:44 AM

Quote from: -ck on June 12, 2013, 06:26:17 AM

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.

bitcoindaddy

hero member

Activity: 481

Merit: 500

Quote from: os2sam on June 12, 2013, 07:01:44 AM

Quote from: -ck on June 12, 2013, 06:26:17 AM

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?

Tamis

sr. member

Activity: 476

Merit: 250

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

os2sam

legendary

Activity: 3586

Merit: 1099

Think for yourself

Quote from: -ck on June 12, 2013, 06:26:17 AM

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

os2sam

legendary

Activity: 3586

Merit: 1099

Think for yourself

Quote from: -ck on June 12, 2013, 06:26:17 AM

Quote from: os2sam on June 12, 2013, 06:05:59 AM

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

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 297. (Read 5806015 times)