Bitcoin Forum
November 12, 2018, 09:25:51 PM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
   Home   Help Search Login Register More  
Pages: « 1 ... 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 [456] 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 ... 846 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1  (Read 5766257 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
loshia
Legendary
*
Offline Offline

Activity: 1610
Merit: 1000


View Profile
March 19, 2013, 03:01:04 PM
 #9101

Guy's

I have posted this before and i am posting it again.

Today i found a block and and cgminer api stats Found Blocks equals to 0. It happened two or three times since my last post about it.

something happened from 2.10.5 onwards

PS:

To all of you who use cgminer - Do you see Found Blocks >0 when you know you have found a block with versions 2.10.5 onward

Thanks!
 
It's the same counter used to display when you get the exit summary as is used to display it in the API.
Of course, if you zero the stats - that gets zeroed also.

Kano,
I have not zeroed the stats. I will check it out on exit when i do upgrade cgminer. I am sure that there is something wrong. Anyway, I will let you know what info i get on exit

Best

Please help the Led Boy aka Bicknellski to make us a nice Christmas led tree and pay WASP membership fee here:
https://bitcointalk.org/index.php?topic=643999.msg7191563#msg7191563
And remember Bicknellski is not collecting money from community;D
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Nemo1024
Legendary
*
Offline Offline

Activity: 1596
Merit: 1004



View Profile WWW
March 19, 2013, 08:44:03 PM
 #9102

I am the author of Bitcoin Miners in Tray, a Windows universal front-end for coin miners:
https://bitcointalk.org/index.php?topic=149442.msg1642010#msg1642010
http://stanislavs.org/bitcoin-miners-in-tray-miner-gui-manager/

When testing it with CGMiner, I discovered a bug in how CGMiner outputs lines on stdout. First of all CGMiner needs to be started with -T to disable ncurses, which is fine.

The output on stderr is also written correctly, so that the front-end gets an event after each line that is sent to stderr stream from CGMiner.

stdout, on the other hand is not flushed after each line, so that the front-end gets all text on stdout redirection in one huge chunk at the moment when CGMiner stops and closes its streams.

The only workaround is to use --verbose and read what should have been on stdout from stderr, living with that huge text dump when CGMiner stops.

Could those, who are maintaining CGMiner fix this issue, applying the same writing strategy to stdout as is done to stderr?


“Dark times lie ahead of us and there will be a time when we must choose between what is easy and what is right.”
“We are only as strong as we are united, as weak as we are divided.”
“It is important to fight and fight again, and keep fighting, for only then can evil be kept at bay, though never quite eradicated.”
Humanxlemming
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250



View Profile
March 19, 2013, 08:48:21 PM
 #9103

Got to say I have tried loads of other software for mining and this has got to be my favourite Cheesy

 Cool Keep up the awesome work Cool
Thanks Smiley it's a labour of love (and anger and hatred and frustration and trolling and headache and heartache and pain at times).

Without all your work think about how many people would not be mining.
Never give up Smiley
Marrs
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
March 19, 2013, 09:17:15 PM
 #9104

I am the author of Bitcoin Miners in Tray, a Windows universal front-end for coin miners:
https://bitcointalk.org/index.php?topic=149442.msg1642010#msg1642010
http://stanislavs.org/bitcoin-miners-in-tray-miner-gui-manager/

When testing it with CGMiner, I discovered a bug in how CGMiner outputs lines on stdout. First of all CGMiner needs to be started with -T to disable ncurses, which is fine.

The output on stderr is also written correctly, so that the front-end gets an event after each line that is sent to stderr stream from CGMiner.

stdout, on the other hand is not flushed after each line, so that the front-end gets all text on stdout redirection in one huge chunk at the moment when CGMiner stops and closes its streams.

The only workaround is to use --verbose and read what should have been on stdout from stderr, living with that huge text dump when CGMiner stops.

Could those, who are maintaining CGMiner fix this issue, applying the same writing strategy to stdout as is done to stderr?



I run cgminer inside a GUIMiner derivative, and I haven't noticed any problems such as the one you're describing.

Try adding -l 1 (lower-case-L one) to your startup parameters.
kano
Legendary
*
Offline Offline

Activity: 2632
Merit: 1059


Linux since 1997 RedHat 4


View Profile
March 19, 2013, 09:22:30 PM
 #9105

...

I tried a cpu litecoin mining software, and the speed from the mining software does pretty much match with the pool speed.

Does anyone have this strange effect too, or knows what the reason could be?
 
CPU mining is not supported ...

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
kano
Legendary
*
Offline Offline

Activity: 2632
Merit: 1059


Linux since 1997 RedHat 4


View Profile
March 19, 2013, 09:28:01 PM
 #9106

Guy's

I have posted this before and i am posting it again.

Today i found a block and and cgminer api stats Found Blocks equals to 0. It happened two or three times since my last post about it.

something happened from 2.10.5 onwards

PS:

To all of you who use cgminer - Do you see Found Blocks >0 when you know you have found a block with versions 2.10.5 onward

Thanks!
 
It's the same counter used to display when you get the exit summary as is used to display it in the API.
Of course, if you zero the stats - that gets zeroed also.

Kano,
I have not zeroed the stats. I will check it out on exit when i do upgrade cgminer. I am sure that there is something wrong. Anyway, I will let you know what info i get on exit

Best
If you check the API and the Summary at the end when you exit, they will be the same.
The variable that stores the block counter is the same one both pieces of code use.

I did notice yesterday that ... 9 months ago Tongue ... ckolivas added a pool block counter that also keeps track of blocks per pool - that I've never added to the API - it's now in my ... todo list Smiley

Pool: https://kano.is Here on Bitcointalk: Forum BTC: 1KanoPb8cKYqNrswjaA8cRDk4FAS9eDMLU
FreeNode IRC: irc.freenode.net channel #kano.is Majority developer of the ckpool code
Help keep Bitcoin secure by mining on pools with full block verification on all blocks - and NO empty blocks!
Nemo1024
Legendary
*
Offline Offline

Activity: 1596
Merit: 1004



View Profile WWW
March 19, 2013, 10:57:04 PM
 #9107

I am the author of Bitcoin Miners in Tray, a Windows universal front-end for coin miners:
https://bitcointalk.org/index.php?topic=149442.msg1642010#msg1642010
http://stanislavs.org/bitcoin-miners-in-tray-miner-gui-manager/

When testing it with CGMiner, I discovered a bug in how CGMiner outputs lines on stdout. First of all CGMiner needs to be started with -T to disable ncurses, which is fine.

The output on stderr is also written correctly, so that the front-end gets an event after each line that is sent to stderr stream from CGMiner.

stdout, on the other hand is not flushed after each line, so that the front-end gets all text on stdout redirection in one huge chunk at the moment when CGMiner stops and closes its streams.

The only workaround is to use --verbose and read what should have been on stdout from stderr, living with that huge text dump when CGMiner stops.

Could those, who are maintaining CGMiner fix this issue, applying the same writing strategy to stdout as is done to stderr?


I run cgminer inside a GUIMiner derivative, and I haven't noticed any problems such as the one you're describing.

Try adding -l 1 (lower-case-L one) to your startup parameters.


Thanks for the tip. Specifying -l 1 starts producing a consistent output. Interestingly, giving any other value than 1 will lock output on stdout until cgminer is stopped, at which time a lot of the output is dumped to the pipe. Something is definitely wrong. Only CGMiner (and pooler's cpuminer, but in that case on stderr) display this problem. poclbm, rpcminer and phoenix seem to work fine.

Here is output with -l 2 (output from my front-end is green, stderr is red, stdout is blue):

19.03.2013 23:49 [Litecoin with CGMiner (NVidia)]: Launching 'cgminer.exe --scrypt -o http://coinotron.com:8322 -u user -p pass -I d -T -l 2'
19.03.2013 23:49 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:49:59] Started cgminer 2.11.3
19.03.2013 23:49 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:49:59] Probing for an alive pool
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:02] Long-polling activated for http://coinotron.com:8322/LP

19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: Stopping miner...
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Thread 0 being disabled
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09]
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: Summary of runtime statistics:
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Started at [2013-03-19 23:50:02]
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Pool: http://coinotron.com:8322
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Runtime: 0 hrs : 0 mins : 6 secs
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Average hashrate: 1.9 Kilohash/s
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Solved blocks: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Best share difficulty: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Queued work requests: 1
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Share submissions: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Accepted shares: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Rejected shares: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Accepted difficulty shares: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Rejected difficulty shares: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Hardware errors: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Efficiency (accepted / queued): 0%
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Utility (accepted shares / min): 0.00/min
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Work Utility (diff1 shares solved / min): 0.00/min
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Discarded work due to new blocks: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Stale submissions discarded due to new blocks: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Unable to get work from server occasions: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Work items generated locally: 4
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Submitting work remotely delay occasions: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] New blocks detected on network: 1
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Summary of per device statistics:
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] GPU0 (2s):0.000 (avg):1.886Kh/s | A:0 R:0 HW:0 U:0.0/m I: 8

19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:49:59] Started cgminer 2.11.3
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:49:59] Probing for an alive pool
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:02] Long-polling activated for http://coinotron.com:8322/LP
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Thread 0 being disabled
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09]
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: Summary of runtime statistics:
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Started at [2013-03-19 23:50:02]
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Pool: http://coinotron.com:8322
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Runtime: 0 hrs : 0 mins : 6 secs
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Average hashrate: 1.9 Kilohash/s
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Solved blocks: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Best share difficulty: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Queued work requests: 1
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Share submissions: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Accepted shares: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Rejected shares: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Accepted difficulty shares: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Rejected difficulty shares: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Hardware errors: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Efficiency (accepted / queued): 0%
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Utility (accepted shares / min): 0.00/min
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Work Utility (diff1 shares solved / min): 0.00/min
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Discarded work due to new blocks: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Stale submissions discarded due to new blocks: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Unable to get work from server occasions: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Work items generated locally: 4
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Submitting work remotely delay occasions: 0
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] New blocks detected on network: 1
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] Summary of per device statistics:
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:50:09] GPU0 (2s):0.000 (avg):1.886Kh/s | A:0 R:0 HW:0 U:0.0/m I: 8

19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: Shutdown signal received.
19.03.2013 23:50 [Litecoin with CGMiner (NVidia)]: Miner stopped.


And here is output with -l 1:
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: Launching 'cgminer.exe --scrypt -o http://coinotron.com:8322 -u user -p pass -I d -T -l 1'
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:16] Started cgminer 2.11.3
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:16] Probing for an alive pool
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:17] Long-polling activated for http://coinotron.com:8322/LP

19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:16] Started cgminer 2.11.3
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:16] Probing for an alive pool
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:17] Long-polling activated for http://coinotron.com:8322/LP
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: (1s):955.0 (avg):1.510Kh/s | Q:1  A:0  R:0  HW:0  E:0%  U:0.0/m
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: (1s):1.646K (avg):1.776Kh/s | Q:1  A:0  R:0  HW:0  E:0%  U:0.0/m
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: (1s):2.516K (avg):2.193Kh/s | Q:1  A:0  R:0  HW:0  E:0%  U:0.0/m
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: (1s):2.436K (avg):2.219Kh/s | Q:1  A:0  R:0  HW:0  E:0%  U:0.0/m
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: (1s):2.108K (avg):2.068Kh/s | Q:1  A:0  R:0  HW:0  E:0%  U:0.0/m
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: (1s):1.901K (avg):1.962Kh/s | Q:1  A:0  R:0  HW:0  E:0%  U:0.0/m

19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: Stopping miner...
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:25] Thread 0 being disabled
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: (1s):1.766K (avg):1.897Kh/s | Q:1  A:0  R:0  HW:0  E:0%  U:0.0/m
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26]
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: Summary of runtime statistics:
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Started at [2013-03-19 23:52:17]
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Pool: http://coinotron.com:8322
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Runtime: 0 hrs : 0 mins : 8 secs
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Average hashrate: 1.9 Kilohash/s
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Solved blocks: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Best share difficulty: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Queued work requests: 1
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Share submissions: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Accepted shares: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Rejected shares: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Accepted difficulty shares: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Rejected difficulty shares: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Hardware errors: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Efficiency (accepted / queued): 0%
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Utility (accepted shares / min): 0.00/min
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Work Utility (diff1 shares solved / min): 0.00/min
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Discarded work due to new blocks: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Stale submissions discarded due to new blocks: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Unable to get work from server occasions: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Work items generated locally: 4
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Submitting work remotely delay occasions: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] New blocks detected on network: 1
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Summary of per device statistics:
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] GPU0 (1s):0.000 (avg):1.897Kh/s | A:0 R:0 HW:0 U:0.0/m I: 8

19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:25] Thread 0 being disabled
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26]
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: Summary of runtime statistics:
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Started at [2013-03-19 23:52:17]
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Pool: http://coinotron.com:8322
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Runtime: 0 hrs : 0 mins : 8 secs
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Average hashrate: 1.9 Kilohash/s
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Solved blocks: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Best share difficulty: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Queued work requests: 1
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Share submissions: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Accepted shares: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Rejected shares: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Accepted difficulty shares: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Rejected difficulty shares: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Hardware errors: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Efficiency (accepted / queued): 0%
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Utility (accepted shares / min): 0.00/min
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Work Utility (diff1 shares solved / min): 0.00/min
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Discarded work due to new blocks: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Stale submissions discarded due to new blocks: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Unable to get work from server occasions: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Work items generated locally: 4
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Submitting work remotely delay occasions: 0
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] New blocks detected on network: 1
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] Summary of per device statistics:
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: [2013-03-19 23:52:26] GPU0 (1s):0.000 (avg):1.897Kh/s | A:0 R:0 HW:0 U:0.0/m I: 8

19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: Shutdown signal received.
19.03.2013 23:52 [Litecoin with CGMiner (NVidia)]: Miner stopped.


“Dark times lie ahead of us and there will be a time when we must choose between what is easy and what is right.”
“We are only as strong as we are united, as weak as we are divided.”
“It is important to fight and fight again, and keep fighting, for only then can evil be kept at bay, though never quite eradicated.”
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2702
Merit: 1145


Ruu \o/


View Profile WWW
March 19, 2013, 11:08:24 PM
 #9108

I'm guessing you're talking about windows. Windows does random things with the logging output it seems. Gotta love its (arse)soul.

Developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org, 1% Fee Solo mining at solo.ckpool.org
-ck
Marrs
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
March 19, 2013, 11:59:38 PM
 #9109

I'm guessing you're talking about windows. Windows does random things with the logging output it seems. Gotta love its (arse)soul.

Seems like a dotNet issue, since Python on windows handles it fine.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2702
Merit: 1145


Ruu \o/


View Profile WWW
March 20, 2013, 12:15:39 AM
 #9110

I'm guessing you're talking about windows. Windows does random things with the logging output it seems. Gotta love its (arse)soul.

Seems like a dotNet issue, since Python on windows handles it fine.

No dotNet in the posix c code that is cgminer.

Developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org, 1% Fee Solo mining at solo.ckpool.org
-ck
Marrs
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
March 20, 2013, 12:21:15 AM
 #9111

I'm guessing you're talking about windows. Windows does random things with the logging output it seems. Gotta love its (arse)soul.

Seems like a dotNet issue, since Python on windows handles it fine.

No dotNet in the posix c code that is cgminer.

I'm saying the problem with Nemo's dotNet-based front-end is a dotNet issue, since a GUIMiner, a similar Python/Win32 front-end does not have the same problem.
Nemo1024
Legendary
*
Offline Offline

Activity: 1596
Merit: 1004



View Profile WWW
March 20, 2013, 08:57:46 AM
 #9112

I'm guessing you're talking about windows. Windows does random things with the logging output it seems. Gotta love its (arse)soul.

Seems like a dotNet issue, since Python on windows handles it fine.

No dotNet in the posix c code that is cgminer.

I'm saying the problem with Nemo's dotNet-based front-end is a dotNet issue, since a GUIMiner, a similar Python/Win32 front-end does not have the same problem.


Then this is inconsistent. I am only observing this issue with CGMiner and cpuminer (from which CGMiner was forked). Poclbm, rpcminer, as well as some other command-line tools, which I ran for test purposes from my front-end (like ping.exe -t) are handled just fine, with output showing just when it is expected.

“Dark times lie ahead of us and there will be a time when we must choose between what is easy and what is right.”
“We are only as strong as we are united, as weak as we are divided.”
“It is important to fight and fight again, and keep fighting, for only then can evil be kept at bay, though never quite eradicated.”
tacotime
Legendary
*
Offline Offline

Activity: 1484
Merit: 1000



View Profile
March 20, 2013, 04:52:44 PM
 #9113

Does anyone else get about 5% invalids using the new cgminer and high thread concurrencies?  Gonna switch my 7950s back to reaper for now until I figure this out.

Code:
XMR: 44GBHzv6ZyQdJkjqZje6KLZ3xSyN1hBSFAnLP6EAqJtCRVzMzZmeXTC2AHKDS9aEDTRKmo6a6o9r9j86pYfhCWDkKjbtcns
bicer
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
March 21, 2013, 12:41:46 AM
 #9114

For some reason cgminer is "consuming" all available ports when run with '--fix-protocol' and p2pool on local machine. Not sure if one of distro updates is causing this or misconfiguration somewhere. Tried cgminer versions all the way back to 2.7.4 and Python 2.7 and 2.6.
Anyone got idea what could be the cause? Below is part of very long list of netstat -tnp

Code:
tcp        0      0 127.0.0.1:9332          127.0.0.1:39383         ESTABLISHED 25198/python2.7    
tcp        0      0 127.0.0.1:9332          127.0.0.1:39355         ESTABLISHED 25198/python2.7    
tcp        0      0 127.0.0.1:39417         127.0.0.1:9332          ESTABLISHED 29338/cgminer      
tcp        0      0 127.0.0.1:39135         127.0.0.1:9332          ESTABLISHED 29338/cgminer      
tcp        0      0 127.0.0.1:39183         127.0.0.1:9332          ESTABLISHED 29338/cgminer      
tcp        0      0 127.0.0.1:39338         127.0.0.1:9332          ESTABLISHED 29338/cgminer      
tcp        0      0 127.0.0.1:39729         127.0.0.1:9332          ESTABLISHED 29338/cgminer      
tcp        0      0 127.0.0.1:9332          127.0.0.1:39739         ESTABLISHED 25198/python2.7    
tcp        0      0 127.0.0.1:9332          127.0.0.1:39492         ESTABLISHED 25198/python2.7    
tcp        0      0 127.0.0.1:39639         127.0.0.1:9332          ESTABLISHED 29338/cgminer      
gigica viteazu`
Sr. Member
****
Offline Offline

Activity: 456
Merit: 250

beast at work


View Profile
March 21, 2013, 11:01:50 AM
 #9115

what happened with 2.11.3 log format, why is not reporting hashrate anymore ?

BURST-3FDG-W622-8KAF-E52KP
flound1129
Hero Member
*****
Offline Offline

Activity: 938
Merit: 1000


www.multipool.us


View Profile
March 21, 2013, 05:37:09 PM
 #9116

cgminer is using about 25% cpu when mining bitcoin.. Uses 0% cpu when mining litecoin..

Is this normal?

Multipool - Always mine the most profitable coin - Scrypt, X11 or SHA-256!
Fiyasko
Legendary
*
Offline Offline

Activity: 1428
Merit: 1000


Okey Dokey Lokey


View Profile
March 21, 2013, 06:08:18 PM
 #9117

cgminer is using about 25% cpu when mining bitcoin.. Uses 0% cpu when mining litecoin..

Is this normal?

Nope!, I assume you have a quad core CPU? Check to see if you have the "100% cpu bug" by setting CGminer to just one core, If the one core is loaded up beyond 97%, Then you have the bug.
It might be nothing more than an SDK/Driver bug that is fixed with the newer drivers

http://bitcoin-otc.com/viewratingdetail.php?nick=DingoRabiit&sign=ANY&type=RECV <-My Ratings
https://bitcointalk.org/index.php?topic=857670.0 GAWminers and associated things are not to be trusted, Especially the "mineral" exchange
crazyates
Legendary
*
Offline Offline

Activity: 952
Merit: 1000



View Profile
March 22, 2013, 01:28:17 AM
 #9118

cgminer is using about 25% cpu when mining bitcoin.. Uses 0% cpu when mining litecoin..

Is this normal?
I hope you're not using the same Intensity for both BTC and LTC. Your -I for BTC should only be like -7.

Tips? 1crazy8pMqgwJ7tX7ZPZmyPwFbc6xZKM9
Previous Trade History - Sale Thread
ditchmagnet
Newbie
*
Offline Offline

Activity: 64
Merit: 0


View Profile
March 22, 2013, 02:51:37 PM
 #9119

Has intensity for LTC been fixed yet in 7xxx cards?  I much prefer cgminer over reaper, but I cant use it with my 7950 right now.
Marrs
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
March 22, 2013, 04:26:13 PM
 #9120

Has intensity for LTC been fixed yet in 7xxx cards?  I much prefer cgminer over reaper, but I cant use it with my 7950 right now.

I'm not sure what problem you're referring to, but for me, cgminer works at least as well as reaper for LTC mining.

With a GIGABYTE GV-R785OC-2GD clocked at 1150/1000, intensity 19, thread concurrency 27164, 1 gpu thread, I get pretty much the same hashrate with cgminer and reaper (~390kH/s).

I also played around with another configuration at intensity 13, thread concurrency 13632, and 2 gpu threads. With this, I get ~360kH/s in cgminer, and a hard crash requiring a reboot with reaper. With cgminer at this intensity, I *am* able to use the desktop for other purposes.

Interestingly, reaper in the first configuration uses ~1.7GB of system memory. cgminer in both configs uses ~40K...!

With my hardware, I don't see any reason to ever use reaper. YMMV with different hardware, of course.
Pages: « 1 ... 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 [456] 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 ... 846 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!