Bitcoin Forum
December 10, 2016, 03:09:40 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 [707] 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 ... 830 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.9.2  (Read 4825609 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.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
January 21, 2014, 12:17:59 AM
 #14121

Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected.


I'm seeing the same.  2xNanofury and 1xBitburner Fury.  cgminer 3.10.0 just quits at random intervals.  Running on Debian Wheezy on BeagleBone Black, and same issue on Debian Wheezy on PC.  cgminer runs for days on the same machine when not running the Nanofurys.


You see this comment earlier: ?

There's a bug in the 3.10.0 release that crashes when a device is (effectively) unplugged that was fixed immediately after in git, so grab a git tarball from master or build from git.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481339380
Hero Member
*
Offline Offline

Posts: 1481339380

View Profile Personal Message (Offline)

Ignore
1481339380
Reply with quote  #2

1481339380
Report to moderator
1481339380
Hero Member
*
Offline Offline

Posts: 1481339380

View Profile Personal Message (Offline)

Ignore
1481339380
Reply with quote  #2

1481339380
Report to moderator
1481339380
Hero Member
*
Offline Offline

Posts: 1481339380

View Profile Personal Message (Offline)

Ignore
1481339380
Reply with quote  #2

1481339380
Report to moderator
chek2fire
Legendary
*
Offline Offline

Activity: 1092


Ιntergalactic Conciliator


View Profile
January 21, 2014, 12:20:07 AM
 #14122

I have a Ubuntu Linux server with all the current updates, running a variety of miners plugged into it on cgminer 3.10.0

I plugged a nanofury NF1 into a usb hub that has a few block erupters in it and the NF1 would only mine at just less than1GH/s.

I removed the block erupters and the NF1 started mining at full speed. Even if I add just one block erupter the NF1 instantly halves it's speed. The block erupter mines at full speed only the NF1 is effected, neither reports any errors that I can see.The power pack for the hub is 2.1Amps so it should be able to handle that, so I think it might be a conflict of some sort.
Erupters run at usb1.1 speed and protocol and perhaps are having some communication interaction making everything work in the same crap manner - depends greatly on how usb hubs manage different speed devices. Try them on separate hubs.
Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected. Same setup runs bfgminer fine.




I run cgminer in xubuntu 13.10 and with 1 in usb of laptop and the other nanofury in a anker usb hub and i have no crashing problems. In the same hub i have a bifury and a redfury and all run perfect.

erk
Sr. Member
****
Offline Offline

Activity: 406



View Profile
January 21, 2014, 12:37:37 AM
 #14123

I have a Ubuntu Linux server with all the current updates, running a variety of miners plugged into it on cgminer 3.10.0

I plugged a nanofury NF1 into a usb hub that has a few block erupters in it and the NF1 would only mine at just less than1GH/s.

I removed the block erupters and the NF1 started mining at full speed. Even if I add just one block erupter the NF1 instantly halves it's speed. The block erupter mines at full speed only the NF1 is effected, neither reports any errors that I can see.The power pack for the hub is 2.1Amps so it should be able to handle that, so I think it might be a conflict of some sort.
Erupters run at usb1.1 speed and protocol and perhaps are having some communication interaction making everything work in the same crap manner - depends greatly on how usb hubs manage different speed devices. Try them on separate hubs.
Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected. Same setup runs bfgminer fine.




I run cgminer in xubuntu 13.10 and with 1 in usb of laptop and the other nanofury in a anker usb hub and i have no crashing problems. In the same hub i have a bifury and a redfury and all run perfect.

How strange, I even tried editing the driver and reducing the number of bits in case it was being overclocked too much by default.
I have tried Ubuntu 13.10 (on two machines) and Scientific Linux 6.4 and they all do it, my Nanofury is an NF1 as designed by vs3



chek2fire
Legendary
*
Offline Offline

Activity: 1092


Ιntergalactic Conciliator


View Profile
January 21, 2014, 12:40:00 AM
 #14124

I have a Ubuntu Linux server with all the current updates, running a variety of miners plugged into it on cgminer 3.10.0

I plugged a nanofury NF1 into a usb hub that has a few block erupters in it and the NF1 would only mine at just less than1GH/s.

I removed the block erupters and the NF1 started mining at full speed. Even if I add just one block erupter the NF1 instantly halves it's speed. The block erupter mines at full speed only the NF1 is effected, neither reports any errors that I can see.The power pack for the hub is 2.1Amps so it should be able to handle that, so I think it might be a conflict of some sort.
Erupters run at usb1.1 speed and protocol and perhaps are having some communication interaction making everything work in the same crap manner - depends greatly on how usb hubs manage different speed devices. Try them on separate hubs.
Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected. Same setup runs bfgminer fine.




I run cgminer in xubuntu 13.10 and with 1 in usb of laptop and the other nanofury in a anker usb hub and i have no crashing problems. In the same hub i have a bifury and a redfury and all run perfect.

How strange, I even tried editing the driver and reducing the number of bits in case it was being overclocked too much by default.
I have tried Ubuntu 13.10 (on two machines) and Scientific Linux 6.4 and they all do it, my Nanofury is an NF1 as designed by vs3





Maybe is the hub you are using?

-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
January 21, 2014, 12:40:40 AM
 #14125

I have a Ubuntu Linux server with all the current updates, running a variety of miners plugged into it on cgminer 3.10.0

I plugged a nanofury NF1 into a usb hub that has a few block erupters in it and the NF1 would only mine at just less than1GH/s.

I removed the block erupters and the NF1 started mining at full speed. Even if I add just one block erupter the NF1 instantly halves it's speed. The block erupter mines at full speed only the NF1 is effected, neither reports any errors that I can see.The power pack for the hub is 2.1Amps so it should be able to handle that, so I think it might be a conflict of some sort.
Erupters run at usb1.1 speed and protocol and perhaps are having some communication interaction making everything work in the same crap manner - depends greatly on how usb hubs manage different speed devices. Try them on separate hubs.
Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected. Same setup runs bfgminer fine.




I run cgminer in xubuntu 13.10 and with 1 in usb of laptop and the other nanofury in a anker usb hub and i have no crashing problems. In the same hub i have a bifury and a redfury and all run perfect.

How strange, I even tried editing the driver and reducing the number of bits in case it was being overclocked too much by default.
I have tried Ubuntu 13.10 (on two machines) and Scientific Linux 6.4 and they all do it, my Nanofury is an NF1 as designed by vs3
Which particular problem are you talking about now? The slowdown with erupters (chek2fire confirmed it worked better by running the erupter on a separate hub). Or the crashing at random intervals (which as I said is due to a bug in 3.10.0 from effectively unplugging of the device when conditions are flaky which is fixed in git post 3.10.0).

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
erk
Sr. Member
****
Offline Offline

Activity: 406



View Profile
January 21, 2014, 12:50:58 AM
 #14126


Which particular problem are you talking about now? The slowdown with erupters (chek2fire confirmed it worked better by running the erupter on a separate hub). Or the crashing at random intervals (which as I said is due to a bug in 3.10.0 from effectively unplugging of the device when conditions are flaky which is fixed in git post 3.10.0).

I took your advice and kept the nanofury away from other usb devices, but that didn't fix the crashing problem. My subsequent tests were with the nanofury alone and I used the usbutils.c file from github. Are there any other files I also needed to replace from github?



/EDIT
Ok, the plot thickens, the crash occurs after a stratum disconnect when the pool establishes contact again after a failover, normally you would get the testing stability message but it seg faults just before that gets displayed.

I tested it on a multi pool that does a short stratum disconnect every 20min when it coin switches, enough to trigger the failover.
omegaflare
Sr. Member
****
Offline Offline

Activity: 335


View Profile
January 21, 2014, 01:28:32 AM
 #14127

Sorry for being nooby, but I am not generating any hashes:



Currently mining TAG coins. I entered stratum+tcp URL including my username and password. Any ideas?

CPU: AMD FX 8150
GPU: Nvidia 760 GTX

LMK.

erk
Sr. Member
****
Offline Offline

Activity: 406



View Profile
January 21, 2014, 01:53:26 AM
 #14128

Sorry for being nooby, but I am not generating any hashes:



Currently mining TAG coins. I entered stratum+tcp URL including my username and password. Any ideas?

CPU: AMD FX 8150
GPU: Nvidia 760 GTX

LMK.
cgminer after version 3.7.2 wont mine TAG or any other scrypt coins.

doctormandrake
Sr. Member
****
Offline Offline

Activity: 434

Do what you will. Keep records.


View Profile
January 21, 2014, 06:45:05 AM
 #14129

...

asic and sha256 or asic and bitcoin only?
Altcoin discussion in here gets your post removed or deleted.

I didn't mention any altcoins, I asked a simple question. One that I thought was within the topic. Also, I noticed I was demoted from member to newbie after doing so. classy. anyway, I'll avoid this thread. Have a wonderful day. Happy hashing.

-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
January 21, 2014, 06:56:39 AM
 #14130

...

asic and sha256 or asic and bitcoin only?
Altcoin discussion in here gets your post removed or deleted.

I didn't mention any altcoins, I asked a simple question. One that I thought was within the topic. Also, I noticed I was demoted from member to newbie after doing so. classy. anyway, I'll avoid this thread. Have a wonderful day. Happy hashing.
No one affiliated with this thread has the ability to delete posts from it or demote you so whatever you saw was pure coincidence. Only forum and global mods could possibly do that.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
matt4054
Legendary
*
Offline Offline

Activity: 1134


BitcoinQueue.com


View Profile WWW
January 21, 2014, 07:00:47 AM
 #14131

Hey, I'm sorry for the missing log file and debugging etc. but I thought it was worth mentioning that:

ALL of my cgminer instances that were connected to BTC Guild, that is various versions from 3.0.x to the latest have crashed at the same time, approximately 06:31 GMT today 21 Jan 2014. I could see a "cannot parse output" and then a Segmentation Fault on the terminal just before crashing, while other instances just exited like they had received a SIGTERM, SIGKILL (or SIGSEGV?).

Even my Antminer S1 with factory built-in firmware running modified cgminer crashed, too. It also crashed on my KnC Miner, but this one is the only one that respawned automagically thanks to the init scripts and monitoring.

Has anyone else experienced this? I will cross-post it on BTC Guild topic. Thanks!

★ ⏳ BitcoinQueue.com β ★ 📈 Real-time Bitcoin Unconfirmed Transaction Queue Charts ⏳ ★ Forum Topic
doctormandrake
Sr. Member
****
Offline Offline

Activity: 434

Do what you will. Keep records.


View Profile
January 21, 2014, 07:36:18 AM
 #14132

...

asic and sha256 or asic and bitcoin only?
Altcoin discussion in here gets your post removed or deleted.

I didn't mention any altcoins, I asked a simple question. One that I thought was within the topic. Also, I noticed I was demoted from member to newbie after doing so. classy. anyway, I'll avoid this thread. Have a wonderful day. Happy hashing.
No one affiliated with this thread has the ability to delete posts from it or demote you so whatever you saw was pure coincidence. Only forum and global mods could possibly do that.

Ah, sorry to sound snarky then. I have had a long day and after checking this post I noticed the demotion, so may have reacted, instead of thinking things through more thoroughly.  So it is probably coincidence etc.  Anyways, the question I asked has since been clarified (a big bitcoin only on that one lol) So hopefully no one has taken offense, I was mayhaps a wee snippy as the reason I WAS asking was to be clear before making any posts, so as to keep anything on topic. Anyway, love cgminer, keep up the good work. Smiley

RaTTuS
Hero Member
*****
Offline Offline

Activity: 792


Bite me


View Profile
January 21, 2014, 08:55:34 AM
 #14133

Ah, sorry to sound snarky then. I have had a long day and after checking this post I noticed the demotion, so may have reacted, instead of thinking things through more thoroughly.  So it is probably coincidence etc.  Anyways, the question I asked has since been clarified (a big bitcoin only on that one lol) So hopefully no one has taken offense, I was mayhaps a wee snippy as the reason I WAS asking was to be clear before making any posts, so as to keep anything on topic. Anyway, love cgminer, keep up the good work. Smiley
offtopic but
https://bitcointalk.org/index.php?topic=423995.0 for demotion

In the Beginning there was CPU , then GPU , then FPGA then ASIC, what next I hear to ask ....

1RaTTuSEN7jJUDiW1EGogHwtek7g9BiEn
Buchi-88
Legendary
*
Offline Offline

Activity: 1092


My Solo Block: 401934


View Profile
January 21, 2014, 09:32:15 AM
 #14134

Good day,

after a Raspberry Pi Update:

Code:
sudo apt-get update && sudo apt-get upgrade
sudo apt-get install libusb-1.0
sudo apt-get install libudev-dev
sudo rpi-update
sudo reboot

I have problems with the stability from CgMiner 3.10.0 with the Antminer U1 with the "--icarus-timing long", before the update the Anminers run at 1,6 GH/s a whole week without problems?

The Pi hangup and only a supply out and in helps...

greets and thanks for the great work Wink


                ,╓▄▄▄▄▄▄▄▄▄╓                 
            ╓▄█████████████████▄╖           
         ╓▄█████▀▀'▒,,,,,╠'▀▀█████▄,         
       ,▓███▀╜,▄▄███████████▄▄,╙▀████╖       
      ▄███▀ ▄█████▀▀"``╙"▀▀█████▄ ▀███▄     
     ▓███╜╓████▀ ,▄▄█████▄▄, ▀████,╙███▌     
    ▓███`╔███▀ ╓▓███▀▀▀▀▀████╖ ▀███@"███▌   
   ]███▌┌███▌ ▐███         ███▄ ▐███ ▐███,   
   ▐███ ▐███ .███           ███  ███▌ ███▌   
   ▐███ ▐███ '███           ███  ███▌ ███▌   
   ]███@╙███@ ▀██▌        ,▄██▌ ▐███ ▐███`   
    ▓███ ▐███▄ ╙██▀╩     9███╜ ╔███▀,███▌   
     ████,╙███▌               ▓███╜,████     
      ▀███▄ ▀╜                 ▀▀ ▄███▌     
       ╙████▄,                 ╓▄████╜       
         ╙█████▄▄╓,       ,╓▄▄█████▀         
            ▀▀█████████████████▀▀           
                '▀▀▀▀▀▀▀▀▀▀▀'

CloakCoin |  Trustless Anonymous Cryptocurrency |  PoSA3
Forum | Bitcointalk | Twitter | Slack |  Facebook |  VK |  Reddit |  CloakTV |  Instagram |  IRC-Chat |  Faucet
HellDiverUK
Hero Member
*****
Offline Offline

Activity: 574


View Profile
January 21, 2014, 09:42:33 AM
 #14135

Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected.


I'm seeing the same.  2xNanofury and 1xBitburner Fury.  cgminer 3.10.0 just quits at random intervals.  Running on Debian Wheezy on BeagleBone Black, and same issue on Debian Wheezy on PC.  cgminer runs for days on the same machine when not running the Nanofurys.


You see this comment earlier: ?

There's a bug in the 3.10.0 release that crashes when a device is (effectively) unplugged that was fixed immediately after in git, so grab a git tarball from master or build from git.

Yes, I did thanks.  I'd recompiled from a fresh git clone. 

But, all that said, it looks like it might be an issue with BTCGuild.  cgminer only crashes when it's connecting to Guild, it's perfect on 3 other pools.   Problem has been reported on BTCGuild thread.
-ck
Moderator
Legendary
*
Offline Offline

Activity: 2002


Ruu \o/


View Profile WWW
January 21, 2014, 01:29:29 PM
 #14136

Yes, btcguild is a separate bug, sorry. BTCguild is the only pool that uses the redirect feature in stratum which was added blindly a long time ago when stratum support was first added and no pool used it. Cgminer's implementation is unfortunately buggy and the only workaround till I can fix it is to connect directly to btcguild's redirected url directly or use a different pool to avoid the crash.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
Pooled mine at kano.is, solo mine at solo.ckpool.org
-ck
HellDiverUK
Hero Member
*****
Offline Offline

Activity: 574


View Profile
January 21, 2014, 01:44:41 PM
 #14137

Yes, btcguild is a separate bug, sorry. BTCguild is the only pool that uses the redirect feature in stratum which was added blindly a long time ago when stratum support was first added and no pool used it. Cgminer's implementation is unfortunately buggy and the only workaround till I can fix it is to connect directly to btcguild's redirected url directly or use a different pool to avoid the crash.

Thanks. Smiley
kamyb
Newbie
*
Offline Offline

Activity: 4


View Profile
January 21, 2014, 04:17:50 PM
 #14138

This is the official thread for support and development of cgminer, the combined ASIC & FPGA bitcoin miner written in c, cross platform for windows, linux and OSX, with monitoring, fanspeed control and remote interface capabilities, completely overhauled based on the original code cpuminer.

This code is provided entirely free of charge by the programmer in his spare
time so donations would be greatly appreciated.

Help can also be obtained on IRC: irc.freenode.net #cgminer
READ THE README INCLUDED IN THE ARCHIVE BEFORE ASKING QUESTIONS WHICH CAN ALSO BE FOUND HERE:
http://ck.kolivas.org/apps/cgminer/README

Note that I can NOT provide personalised support via email or personal messages under normal circumstances so they will usually be ignored.
Apologies, but the demand is just far too great and I must prioritise my time.

All files available from here:
http://ck.kolivas.org/apps/cgminer

As a backup they can be downloaded here:
https://github.com/kanoi/cgminer-binaries

Debug builds are in http://ck.kolivas.org/apps/cgminer/debug/

.lrz files are compressed with lrzip http://lrzip.kolivas.org for much better compression and supports extreme encryption technology which is ideal for securing wallets.

LATEST RELEASE: 3.10.0
https://bitcointalk.org/index.php?topic=28402.msg4403012#msg4403012

Note that x86_64 binary is a 64 bit binary for UBUNTU 13.10.

Git tree:
https://github.com/ckolivas/cgminer

Latest git source tarball:
https://github.com/ckolivas/cgminer/tarball/master

Unofficial OSX binaries:
http://spaceman.ca/cgminer/

Features:
- Very low overhead free c code for Linux and windows with very low non-mining CPU and ram usage
- Stratum and GBT pooled mining protocol support
- Scaleable networking scheduler designed to scale to any size hashrate without networking delays yet minimise connection overhead
- long poll support - will use longpoll from any pool if primary pool does not support it
- Self detection of new blocks with a mini-database for slow/failing longpoll scenarios, maximum work efficiency and minimum rejects.
- Heavily threaded code hands out work retrieval and work submission to separate threads to not hinder devices working
- Caching of submissions during transient network outages
- Preemptive fetching of work prior to completion of current work
- Local generation of valid work (via stratum, GBT or ntime rollover) whenever possible, as supported on a per-work item basis
- Prevention of stale work submission on new block
- Summarised and discrete device data statistics of requests, accepts, rejects, hw errors and work utility
- Summary displayed when quitting
- Supports multiple pools with multiple intelligent failover mechanisms
- Temporary disabling of misbehaving pools rejecting all shares
- On the fly menu based management of most settings
- Trickling of extra work to backup pools if primary pool is responding but slow
- RPC +/- JSON interface for remote control
- Bitforce support - singles and minirig
- Icarus support
- Modminer support
- Ability to cope with slow routers
- Submit-old support
- X-Reject-Reason support
- Variable difficulty support
- Share difficulty reporting
- Target and block difficulty displays
- Block solve detection
- ASIC Avalon support
- Bitburner support
- Redfury/Bluefury USB stick support
- Bi*fury USB support
- BlackArrow Bitfury support
- BFL SC asic support
- Drillbit support
- Klondike support
- KnCminer support
- Hashfast support
- Nanofury support
- Minion support
- Direct USB communications
- Device hotplug
- Heavily featured RPC API
- Multicast support
- Proxy support
- Lots of other stuff I can't remember. See options.

Sample output:
Code:
cgminer version 3.7.2 - Started: [2013-11-10 19:17:46]
--------------------------------------------------------------------------------
 (5s):218.1G (avg):219.8Gh/s | A:310090  R:0  HW:6245  WU:3031.3/m
 ST: 2  SS: 0  NB: 9  LW: 302959  GF: 0  RF: 0
 Connected to au.ozco.in diff 10K with stratum as user ckolivas.0
 Block: 244bec03...  Diff:511M  Started: [20:38:47]  Best share: 2.87M
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BAJ 0:  max 57C 3.52V | 8.379G/8.472Gh/s | A: 10025 R:0 HW: 148 WU: 116.8/m
 BAS 0:  max 70C 3.27V | 63.73G/63.72Gh/s | A: 90019 R:0 HW:1881 WU: 870.3/m
 BAS 1:  max 69C 3.27V | 62.05G/62.11Gh/s | A: 90017 R:0 HW:1727 WU: 850.1/m
 AVA 0: 23C/ 47C 2280R | 81.24G/83.34Gh/s | A:120029 R:0 HW:2061 WU:1164.4/m
 BF1 0:                | 2.296G/2.278Gh/s | A:     0 R:0 HW: 432 WU:  32.1/m
--------------------------------------------------------------------------------
 [2013-11-10 19:17:47] Accepted b23f2ecd Diff 1/1 BAS 1 pool 0
 [2013-11-10 19:17:49] Accepted 03bcd8c0 Diff 68/1 AVA 0 pool 0
 [2013-11-10 19:17:49] Accepted b33b98ee Diff 1/1 BAS 0 pool 0
 [2013-11-10 19:17:49] Accepted 13a43229 Diff 13/1 BAS 0 pool 0
 [2013-11-10 19:17:49] Accepted 1bce6c19 Diff 9/1 AVA 0 pool 0
 
---
Pool menu:
Code:
0: Enabled Alive Quota 1 Prio 0: stratum+tcp://au.ozco.in:3333  User:ckolivas.0
1: Enabled Alive Quota 1 Prio 1: stratum+tcp://hash.mineb.tc:3333  User:ckolivas.0
2: Enabled Alive Quota 1 Prio 2: stratum+tcp://stratum.ozco.in:3333  User:ckolivas.0
3: Enabled Dead Quota 1 Prio 3: stratum+tcp://us1.eclipsemc.com:3333  User:ckolivas_0
4: Enabled Alive Quota 1 Prio 4: stratum+tcp://api-stratum.bitcoin.cz:3333  User:ckolivas.0
5: Enabled Alive Quota 1 Prio 5: stratum+tcp://stratum.btcguild.com:3333  User:ckolivas_0

Current pool management strategy: Failover
[F]ailover only disabled
Pool [A]dd [R]emove [D]isable [E]nable [Q]uota change
[C]hange management strategy [S]witch pool [I]nformation
Or press any other key to continue

Change settings menu:
Code:
[Q]ueue: 1
[S]cantime: 60
[E]xpiry: 120
[W]rite config file
[C]gminer restart
Select an option or any other key to return

Display menu:

Code:
[N]ormal [C]lear [S]ilent mode (disable all output)
[D]ebug:off
[P]er-device:off
[Q]uiet:off
[V]erbose:off
[R]PC debug:off
[W]orkTime details:off
co[M]pact: off
[L]og interval:5
[Z]ero statistics
Select an option or any other key to return


On exiting:
Code:
Summary of runtime statistics:

Started at [2011-07-19 14:40:09]
Runtime: 2 hrs : 31 mins : 18 secs
Average hashrate: 1680.1 Megahash/s
Queued work requests: 3317
Share submissions: 3489
Accepted shares: 3489
Rejected shares: 0
Reject ratio: 0.0
Hardware errors: 0
Efficiency (accepted / queued): 105%
Utility (accepted shares / min): 23.06/min

Discarded work due to new blocks: 0
Stale submissions discarded due to new blocks: 9
Unable to get work from server occasions: 16
Work items generated locally: 330
Submitting work remotely delay occasions: 33
New blocks detected on network: 10

Pool: http://ozco.in:8332
 Queued work requests: 3253
 Share submissions: 3426
 Accepted shares: 3426
 Rejected shares: 0
 Reject ratio: 0.0
 Efficiency (accepted / queued): 105%
 Discarded work due to new blocks: 0
 Stale submissions discarded due to new blocks: 9
 Unable to get work from server occasions: 15
 Submitting work remotely delay occasions: 33

Pool: http://bitcoinpool.com:8334
 Queued work requests: 64
 Share submissions: 63
 Accepted shares: 63
 Rejected shares: 0
 Reject ratio: 0.0
 Efficiency (accepted / queued): 98%
 Discarded work due to new blocks: 0
 Stale submissions discarded due to new blocks: 0
 Unable to get work from server occasions: 1
 Submitting work remotely delay occasions: 0

Summary of per device statistics:

 GPU 0: [419.9 Mh/s] [Q:913  A:901  R:0  HW:0  E:99%  U:5.96/m]
 GPU 1: [420.1 Mh/s] [Q:912  A:865  R:0  HW:0  E:95%  U:5.72/m]
 GPU 2: [420.5 Mh/s] [Q:908  A:865  R:0  HW:0  E:95%  U:5.72/m]
 GPU 3: [419.6 Mh/s] [Q:910  A:858  R:0  HW:0  E:94%  U:5.68/m]
---

Usage instructions:  Run "cgminer --help" to see options:

Usage: cgminer [-DdElmpPQqUsTouOchnV]

Options for both config file and command line:
--api-allow         Allow API access (if enabled) only to the given list of [W:]IP[/Prefix] address[/subnets]
                    This overrides --api-network and you must specify 127.0.0.1 if it is required
                    W: in front of the IP address gives that address privileged access to all api commands
--api-description   Description placed in the API status header (default: cgminer version)
--api-groups        API one letter groups G:cmd:cmd[,P:cmd:*...]
                    See API-README for usage
--api-listen        Listen for API requests (default: disabled)
                    By default any command that does not just display data returns access denied
                    See --api-allow to overcome this
--api-network       Allow API (if enabled) to listen on/for any address (default: only 127.0.0.1)
--api-mcast         Enable API Multicast listener, (default: disabled)
                    The listener will only run if the API is also enabled
--api-mcast-addr <arg> API Multicast listen address, (default: 224.0.0.75)
--api-mcast-code <arg> Code expected in the API Multicast message, don't use '-' (default: "FTW")
--api-mcast-port <arg> API Multicast listen port, (default: 4028)
--api-port          Port number of miner API (default: 4028)
--balance           Change multipool strategy from failover to even share balance
--benchmark         Run cgminer in benchmark mode - produces no shares
--compact           Use compact display without per device statistics
--debug|-D          Enable debug output
--device|-d <arg>   Select device to use, one value, range and/or comma separated (e.g. 0-2,4) default: all
--disable-rejecting Automatically disable pools that continually reject shares
--expiry|-E <arg>   Upper bound on how many seconds after getting work we consider a share from it stale (default: 120)
--failover-only     Don't leak work to backup pools when primary pool is lagging
--fix-protocol      Do not redirect to a different getwork protocol (eg. stratum)
--hotplug <arg>     Set hotplug check time to <arg> seconds (0=never default: 5) - only with libusb
--kernel-path|-K <arg> Specify a path to where bitstream files are (default: "/usr/local/bin")
--load-balance      Change multipool strategy from failover to quota based balance
--log|-l <arg>      Interval in seconds between log output (default: 5)
--lowmem            Minimise caching of shares for low memory applications
--monitor|-m <arg>  Use custom pipe cmd for output messages
--net-delay         Impose small delays in networking to not overload slow routers
--no-submit-stale   Don't submit shares if they are detected as stale
--pass|-p <arg>     Password for bitcoin JSON-RPC server
--per-device-stats  Force verbose mode and output per-device statistics
--protocol-dump|-P  Verbose dump of protocol-level activities
--queue|-Q <arg>    Minimum number of work items to have queued (0 - 10) (default: 1)
--quiet|-q          Disable logging output, display status and errors
--real-quiet        Disable all output
--remove-disabled   Remove disabled devices entirely, as if they didn't exist
--rotate <arg>      Change multipool strategy from failover to regularly rotate at N minutes (default: 0)
--round-robin       Change multipool strategy from failover to round robin on failure
--scan-time|-s <arg> Upper bound on time spent scanning current work, in seconds (default: 60)
--sched-start <arg> Set a time of day in HH:MM to start mining (a once off without a stop time)
--sched-stop <arg>  Set a time of day in HH:MM to stop mining (will quit without a start time)
--sharelog <arg>    Append share log to file
--shares <arg>      Quit after mining N shares (default: unlimited)
--socks-proxy <arg> Set socks4 proxy (host:port) for all pools without a proxy specified
--syslog            Use system log for output messages (default: standard error)
--temp-cutoff <arg> Temperature where a device will be automatically disabled, one value or comma separated list (default: 95)
--text-only|-T      Disable ncurses formatted screen output
--url|-o <arg>      URL for bitcoin JSON-RPC server
--user|-u <arg>     Username for bitcoin JSON-RPC server
--verbose           Log verbose output to stderr as well as status output
--userpass|-O <arg> Username:Password pair for bitcoin JSON-RPC server
Options for command line only:
--config|-c <arg>   Load a JSON-format configuration file
See example.conf for an example configuration.
--help|-h           Print this message
--version|-V        Display version and exit

USB device (ASIC and FPGA) options:

--icarus-options <arg> Set specific FPGA board configurations - one set of values for all or comma separated
--icarus-timing <arg> Set how the Icarus timing is calculated - one setting/value for all or comma separated
--usb <arg>         USB device selection (See below)
--usb-dump          (See FPGA-README)

See FGPA-README or ASIC-README for more information regarding these.


ASIC only options:

--avalon-auto       Adjust avalon overclock frequency dynamically for best hashrate
--avalon-fan <arg> Set fanspeed percentage for avalon, single value or range (default: 20-100)
--avalon-freq <arg> Set frequency range for avalon-auto, single value or range
--avalon-cutoff <arg> Set avalon overheat cut off temperature (default: 60)
--avalon-options <arg> Set avalon options baud:miners:asic:timeout:freq
--avalon-temp <arg> Set avalon target temperature (default: 50)
--bflsc-overheat <arg> Set overheat temperature where BFLSC devices throttle, 0 to disable (default: 90)
--bitburner-fury-options <arg> Override avalon-options for BitBurner Fury boards baud:miners:asic:timeout:freq
--bitburner-fury-voltage <arg> Set BitBurner Fury core voltage, in millivolts
--bitburner-voltage <arg> Set BitBurner (Avalon) core voltage, in millivolts
--klondike-options <arg> Set klondike options clock:temptarget

See ASIC-README for more information regarding these.


FPGA only options:

--bfl-range         Use nonce range on bitforce devices if supported

See FGPA-README for more information regarding this.


Cgminer should automatically find all of your Avalon ASIC, BFL ASIC, BitForce
FPGAs, Icarus bitstream FPGAs, Klondike ASIC, ASICMINER usb block erupters,
KnC ASICs, BaB ASICs, Hashfast ASICs and ModMiner FPGAs.

---

EXECUTIVE SUMMARY ON USAGE:

Single pool:

cgminer -o http://pool:port -u username -p password

Multiple pools:

cgminer -o http://pool1:port -u pool1username -p pool1password -o http://pool2:port -u pool2usernmae -p pool2password

Single pool with a standard http proxy:

cgminer -o "http:proxy:port|http://pool:port" -u username -p password

Single pool with a socks5 proxy:

cgminer -o "socks5:proxy:port|http://pool:port" -u username -p password

Single pool with stratum protocol support:

cgminer -o stratum+tcp://pool:port -u username -p password

The list of proxy types are:
 http:    standard http 1.1 proxy
 http0:   http 1.0 proxy
 socks4:  socks4 proxy
 socks5:  socks5 proxy
 socks4a: socks4a proxy
 socks5h: socks5 proxy using a hostname

If you compile cgminer with a version of CURL before 7.19.4 then some of the above will
not be available. All are available since CURL version 7.19.4

If you specify the --socks-proxy option to cgminer, it will only be applied to all pools
that don't specify their own proxy setting like above


After saving configuration from the menu, you do not need to give cgminer any
arguments and it will load your configuration.

Any configuration file may also contain a single
   "include" : "filename"
to recursively include another configuration file.
Writing the configuration will save all settings from all files in the output.

---
Also many issues and FAQs are covered in the forum thread
dedicated to this program,
   http://forum.bitcoin.org/index.php?topic=28402.0

The output line shows the following:
 (5s):223.5G (avg):219.6Gh/s | A:330090  R:0  HW:6904  WU:3027.6/m

Each column is as follows:
5s:  A 5 second exponentially decaying average hash rate
avg: An all time average hash rate
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 shares / minute

 AVA 0: 23C/ 47C 2280R | 77.10G/83.20Gh/s | A:120029 R:0 HW:2295 WU:1162.5/m

Each column is as follows:
Temperature (if supported)
Fanspeed (if supported)
A 5 second exponentially decaying average hash rate
An all time average hash rate
The number of accepted shares
The number of rejected shares
The number of hardware erorrs
The Work Utility defined as the number of diff1 equivalent shares / minute

The cgminer status line shows:
 TQ: 1  ST: 1  SS: 0  DW: 0  NB: 1  LW: 8  GF: 1  RF: 1

TQ is Total Queued work items.
ST is STaged work items (ready to use).
SS is Stale Shares discarded (detected and not submitted so don't count as rejects)
DW is Discarded Work items (work from block no longer valid to work on)
NB is New Blocks detected on the network
LW is Locally generated Work items
GF is Getwork Fail Occasions (server slow to provide work)
RF is Remote Fail occasions (server slow to accept work)

---
MULTIPOOL

FAILOVER STRATEGIES WITH MULTIPOOL:
A number of different strategies for dealing with multipool setups are
available. Each has their advantages and disadvantages so multiple strategies
are available by user choice, as per the following list:

FAILOVER:
The default strategy is failover. This means that if you input a number of
pools, it will try to use them as a priority list, moving away from the 1st
to the 2nd, 2nd to 3rd and so on. If any of the earlier pools recover, it will
move back to the higher priority ones.

ROUND ROBIN:
This strategy only moves from one pool to the next when the current one falls
idle and makes no attempt to move otherwise.

ROTATE:
This strategy moves at user-defined intervals from one active pool to the next,
skipping pools that are idle.

LOAD BALANCE:
This strategy sends work to all the pools to maintain optimum load. The most
efficient pools will tend to get a lot more shares. If any pool falls idle, the
rest will tend to take up the slack keeping the miner busy.

BALANCE:
This strategy monitors the amount of difficulty 1 shares solved for each pool
and uses it to try to end up doing the same amount of work for all pools.

---
LOGGING

cgminer will log to stderr if it detects stderr is being redirected to a file.
To enable logging simply add 2>logfile.txt to your command line and logfile.txt
will contain the logged output at the log level you specify (normal, verbose,
debug etc.)

In other words if you would normally use:
./cgminer -o xxx -u yyy -p zzz
if you use
./cgminer -o xxx -u yyy -p zzz 2>logfile.txt
it will log to a file called logfile.txt and otherwise work the same.

There is also the -m option on linux which will spawn a command of your choice
and pipe the output directly to that command.


If you start cgminer with the --sharelog option, you can get detailed
information for each share found. The argument to the option may be "-" for
standard output (not advisable with the ncurses UI), any valid positive number
for that file descriptor, or a filename.

To log share data to a file named "share.log", you can use either:
./cgminer --sharelog 50 -o xxx -u yyy -p zzz 50>share.log
./cgminer --sharelog share.log -o xxx -u yyy -p zzz

For every share found, data will be logged in a CSV (Comma Separated Value)
format:
    timestamp,disposition,target,pool,dev,thr,sharehash,sharedata
For example (this is wrapped, but it's all on one line for real):
    1335313090,reject,
    ffffffffffffffffffffffffffffffffffffffffffffffffffffffff00000000,
    http://localhost:8337,GPU0,0,
    6f983c918f3299b58febf95ec4d0c7094ed634bc13754553ec34fc3800000000,
    00000001a0980aff4ce4a96d53f4b89a2d5f0e765c978640fe24372a000001c5
    000000004a4366808f81d44f26df3d69d7dc4b3473385930462d9ab707b50498
    f681634a4f1f63d01a0cd43fb338000000000080000000000000000000000000
    0000000000000000000000000000000000000000000000000000000080020000

---

RPC API

For RPC API details see the API-README file

---

FAQ

Q: Can I mine on servers from different networks (eg xxxcoin and bitcoin) at
the same time?
A: No, cgminer keeps a database of the block it's working on to ensure it does
not work on stale blocks, and having different blocks from two networks would
make it invalidate the work from each other.

Q: Can I configure cgminer to mine with different login credentials or pools
for each separate device?
A: No.

Q: Can I put multiple pools in the config file?
A: Yes, check the example.conf file. Alternatively, set up everything either on
the command line or via the menu after startup and choose settings->write
config file and the file will be loaded one each startup.

Q: The build fails with gcc is unable to build a binary.
A: Remove the "-march=native" component of your CFLAGS as your version of gcc
does not support it.

Q: Can you implement feature X?
A: I can, but time is limited, and people who donate are more likely to get
their feature requests implemented.

Q: Work keeps going to my backup pool even though my primary pool hasn't
failed?
A: Cgminer checks for conditions where the primary pool is lagging and will
pass some work to the backup servers under those conditions. The reason for
doing this is to try its absolute best to keep the GPUs working on something
useful and not risk idle periods. You can disable this behaviour with the
option --failover-only.

Q: Is this a virus?
A: Cgminer is being packaged with other trojan scripts and some antivirus
software is falsely accusing cgminer.exe as being the actual virus, rather
than whatever it is being packaged with. If you installed cgminer yourself,
then you do not have a virus on your computer. Complain to your antivirus
software company. They seem to be flagging even source code now from cgminer
as viruses, even though text source files can't do anything by themself.

Q: Can you modify the display to include more of one thing in the output and
less of another, or can you change the quiet mode or can you add yet another
output mode?
A: Everyone will always have their own view of what's important to monitor.
The defaults are very sane and I have very little interest in changing this
any further.

Q: What are the best parameters to pass for X pool/hardware/device.
A: Virtually always, the DEFAULT parameters give the best results. Most user
defined settings lead to worse performance. The ONLY thing most users should
need to set is the Intensity for GPUs.

Q: What happened to CPU and GPU mining?
A: Their efficiency makes them irrelevant in the bitcoin mining world today
and the author has no interest in supporting alternative coins that are better
mined by these devices.

Q: GUI version?
A: No. The RPC interface makes it possible for someone else to write one
though.

Q: I'm having an issue. What debugging information should I provide?
A: Start cgminer with your regular commands and add -D -T --verbose and provide
the full startup output and a summary of your hardware and operating system.

Q: Why don't you provide win64 builds?
A: Win32 builds work everywhere and there is precisely zero advantage to a
64 bit build on windows.

Q: Is it faster to mine on windows or linux?
A: It makes no difference. It comes down to choice of operating system for
their various features. Linux offers much better long term stability and
remote monitoring and security, while windows offers you overclocking tools
that can achieve much more than cgminer can do on linux.

Q: My network gets slower and slower and then dies for a minute?
A; Try the --net-delay option.

Q: How do I tune for p2pool?
A: It is also recommended to use --failover-only since the work is effectively
like a different block chain, and not enabling --no-submit-stale. If mining with
a BFL (fpga) minirig, it is worth adding the --bfl-range option.

Q: I run PHP on windows to access the API with the example miner.php. Why does
it fail when php is installed properly but I only get errors about Sockets not
working in the logs?
A: http://us.php.net/manual/en/sockets.installation.php

Q: What is a PGA?
A: At the moment, cgminer supports 3 FPGAs: BitForce, Icarus and ModMiner.
They are Field-Programmable Gate Arrays that have been programmed to do Bitcoin
mining. Since the acronym needs to be only 3 characters, the "Field-" part has
been skipped.

Q: What is an ASIC?
A: They are Application Specify Integrated Circuit devices and provide the
highest performance per unit power due to being dedicated to only one purpose.

Q: Can I mine scrypt with FPGAs or ASICs?
A: No.

Q: What is stratum and how do I use it?
A: Stratum is a protocol designed for pooled mining in such a way as to
minimise the amount of network communications, yet scale to hardware of any
speed. With versions of cgminer 2.8.0+, if a pool has stratum support, cgminer
will automatically detect it and switch to the support as advertised if it can.
If you input the stratum port directly into your configuration, or use the
special prefix "stratum+tcp://" instead of "http://", cgminer will ONLY try to
use stratum protocol mining. The advantages of stratum to the miner are no
delays in getting more work for the miner, less rejects across block changes,
and far less network communications for the same amount of mining hashrate. If
you do NOT wish cgminer to automatically switch to stratum protocol even if it
is detected, add the --fix-protocol option.

Q: Why don't the statistics add up: Accepted, Rejected, Stale, Hardware Errors,
Diff1 Work, etc. when mining greater than 1 difficulty shares?
A: As an example, if you look at 'Difficulty Accepted' in the RPC API, the number
of difficulty shares accepted does not usually exactly equal the amount of work
done to find them. If you are mining at 8 difficulty, then you would expect on
average to find one 8 difficulty share, per 8 single difficulty shares found.
However, the number is actually random and converges over time, it is an average,
not an exact value, thus you may find more or less than the expected average.

Q: My keyboard input momentarily pauses or repeats keys every so often on
windows while mining?
A: The USB implementation on windows can be very flaky on some hardware and
every time cgminer looks for new hardware to hotplug it it can cause these
sorts of problems. You can disable hotplug with:
--hotplug 0

Q: What should my Work Utility (WU) be?
A: Work utility is the product of hashrate * luck and only stabilises over a
very long period of time. Assuming all your work is valid work, bitcoin mining
should produce a work utility of approximately 1 per 71.6MH. This means at
5GH you should have a WU of 5000 / 71.6 or ~ 69. You cannot make your machine
do "better WU" than this - it is luck related. However you can make it much
worse if your machine produces a lot of hardware errors producing invalid work.

---

This code is provided entirely free of charge by the programmer in his spare
time so donations would be greatly appreciated. Please consider donating to the
address below.

Con Kolivas <kernel@kolivas.org>
15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ

Hello,

I am running cgminer 3.7.2 on Mac Book Pro Mac OSX 10.5 and get following error "dyld: unknown required load command 0x80000022 Trace/BPT Trap".
I know its an old version of Mac machine but its lying unused and want to start GPU mining with this.

Help appreciated.

Regards
Kamyb
Karin
Member
**
Offline Offline

Activity: 109



View Profile WWW
January 21, 2014, 05:18:12 PM
 #14139

Hello,

I am running cgminer 3.7.2 on Mac Book Pro Mac OSX 10.5 and get following error "dyld: unknown required load command 0x80000022 Trace/BPT Trap".
I know its an old version of Mac machine but its lying unused and want to start GPU mining with this.

Help appreciated.

Regards
Kamyb
GPU mining requires OpenCL which wasn't added to Mac OS X until 10.6.  You may be able to mine with USB-based devices on your 10.5 machine though.

Easiest to use bitcoin/litecoin miner for Mac: AsteroidApp.com | @AsteroidApp | Bitcointalk forum thread
Unofficial cgminer for Mac OS X | sgminer for Mac OS X
rgr_rgr
Member
**
Offline Offline

Activity: 104


View Profile
January 21, 2014, 05:29:50 PM
 #14140

Yes, btcguild is a separate bug, sorry. BTCguild is the only pool that uses the redirect feature in stratum which was added blindly a long time ago when stratum support was first added and no pool used it. Cgminer's implementation is unfortunately buggy and the only workaround till I can fix it is to connect directly to btcguild's redirected url directly or use a different pool to avoid the crash.

I can confirm this bug, but for me this appears seldom.

I also have problems with another pool: http://elizium.name/ (p2pool). After minutes I get: ./cgminer: double free or corruption (!prev): 0x0a01f120 *** with backtrace.

Pages: « 1 ... 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 [707] 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 ... 830 »
  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!