Bitcoin Forum
May 03, 2024, 02:25:27 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 [561] 562 563 564 565 566 567 568 569 »
11201  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 14, 2011, 10:43:02 AM
Make install doesn't work, sorry. Just make it in its own directory and run it from there. Make sure to do ./configure again after you install any new libraries etc.
11202  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 14, 2011, 08:15:18 AM
Quote from: d3m0n1q_733rz on July 14, 2011, 08:11:04 AM
Question about the GPU computing source code:  What method is being used to move data between the CPU and the GPU?  If using a caching method, you've created a slight bottleneck.  Since the GPU memory is non-cachable, using a caching method will cause a major slowdown.  Granted, I'm not awfully familiar with GPU computing code, it is certainly something to keep in mind.
Hardly any data is actually moved between the gpu and the cpu. It would be extremely unlikely to be creating a bottleneck.
11203  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 14, 2011, 05:30:55 AM
Quote from: bmgjet on July 14, 2011, 03:25:19 AM
Nice,Think I found my new default miner Wink

First try letting it use all default settings it would only get 209 mhash/s

Then using -n -w 128 -I 9 options got it up to 263 mhash/s
Then replacing poclbm and phatk110711 with the modded phatk brang the speed back up to where phoenix was with spikes going 2mhash/s faster.
You cannot replace the kernels in cgminer with other kernels. They are incompatible. You will get mostly rejects and errors if you do that. The cgminer included kernel is the most advanced available phatk kernel at the moment anyway.
11204  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 14, 2011, 01:36:37 AM
There's something wrong with the increment of work in the cpu miner thread. Working on it...
11205  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 13, 2011, 11:28:20 PM
Quote from: ewal on July 13, 2011, 10:07:12 PM
I was giving this a test run today and coincidentally had a complete internet connectivity failure for 3-4 hours due to problems with my ISP.   Because the ISP problem was long, I would expect that there were not only network connectivity problems but that also at some point DNS requests started failing as well because the cache expired and it couldn't do new lookups.  Obviously, during the Internet downtime, the miner wasn't working, but after the ISP problems resolved themselves, cgminer did not recover.  I had to kill it and start it again for it to start working.  I didn't think to copy the then-current screen output, but I do remember that the screen was filled with messages about the miner being idle for more than 60 seconds (that was recently added to address OpenCL or the GPU breaking).   

In contrast, the one machine that I was still running poclbm on recovered as soon as the Internet connection was back up.
Thanks. I was very aggressive with trying to make the idle threads restart and made it do it indiscriminately. I'll add some more logic to know that it's just the network down in the future and not restart the threads from scratch.
11206  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 13, 2011, 11:26:07 PM
Quote from: KJaneway on July 13, 2011, 08:51:47 PM
Code:
martin@latrop:~/cgminer/cgminer-1.2.4$ sudo make install
[sudo] password for martin:
Making install in lib
make[1]: Betrete Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/lib'
make  install-recursive
make[2]: Betrete Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/lib'
make[3]: Betrete Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/lib'
make[4]: Betrete Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/lib'
make[4]: Für das Ziel »install-exec-am« ist nichts zu tun.
make[4]: Für das Ziel »install-data-am« ist nichts zu tun.
make[4]: Verlasse Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/lib'
make[3]: Verlasse Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/lib'
make[2]: Verlasse Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/lib'
make[1]: Verlasse Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/lib'
Making install in compat
make[1]: Betrete Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/compat'
Making install in jansson
make[2]: Betrete Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/compat/jansson'
make[3]: Betrete Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/compat/jansson'
make[3]: Für das Ziel »install-exec-am« ist nichts zu tun.
make[3]: Für das Ziel »install-data-am« ist nichts zu tun.
make[3]: Verlasse Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/compat/jansson                              '
make[2]: Verlasse Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/compat/jansson                              '
make[2]: Betrete Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/compat'
make[3]: Betrete Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/compat'
make[3]: Für das Ziel »install-exec-am« ist nichts zu tun.
make[3]: Für das Ziel »install-data-am« ist nichts zu tun.
make[3]: Verlasse Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/compat'
make[2]: Verlasse Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/compat'
make[1]: Verlasse Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/compat'
Making install in ccan
make[1]: Betrete Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/ccan'
make[2]: Betrete Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/ccan'
make[2]: Für das Ziel »install-exec-am« ist nichts zu tun.
make[2]: Für das Ziel »install-data-am« ist nichts zu tun.
make[2]: Verlasse Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/ccan'
make[1]: Verlasse Verzeichnis '/home/martin/cgminer/cgminer-1.2.4/ccan'
make[1]: Betrete Verzeichnis '/home/martin/cgminer/cgminer-1.2.4'
gcc  -O3 -Wall -march=native -I/home/martin/AMD-APP-SDK-v2.4-lnx64/ -pthread -L/                              home/martin/AMD-APP-SDK-v2.4-lnx64/lib/x86_64/ -o cgminer cgminer-main.o cgminer                              -util.o cgminer-ocl.o cgminer-findnonce.o cgminer-sha256_generic.o cgminer-sha25                              6_4way.o cgminer-sha256_via.o cgminer-sha256_cryptopp.o cgminer-sha256_sse2_amd6                              4.o -lcurl -Wl,-Bsymbolic-functions -L/usr/lib/x86_64-linux-gnu compat/jansson/l                              ibjansson.a -lpthread -lOpenCL lib/libgnu.a ccan/libccan.a
cgminer-main.o: In function `submit_upstream_work':
main.c:(.text+0x194e): undefined reference to `wmove'
main.c:(.text+0x1961): undefined reference to `wattr_on'
main.c:(.text+0x1974): undefined reference to `wprintw'
main.c:(.text+0x1987): undefined reference to `wattr_off'
main.c:(.text+0x199a): undefined reference to `wmove'
main.c:(.text+0x19b0): undefined reference to `whline'
main.c:(.text+0x19c3): undefined reference to `wmove'
main.c:(.text+0x19db): undefined reference to `wprintw'
main.c:(.text+0x19e7): undefined reference to `wclrtoeol'
main.c:(.text+0x19fa): undefined reference to `wmove'
main.c:(.text+0x1a10): undefined reference to `whline'
main.c:(.text+0x1a26): undefined reference to `wmove'
main.c:(.text+0x1a3c): undefined reference to `whline'
main.c:(.text+0x1a88): undefined reference to `wmove'
main.c:(.text+0x1ace): undefined reference to `wprintw'
main.c:(.text+0x1ada): undefined reference to `wclrtoeol'
main.c:(.text+0x1ae6): undefined reference to `wrefresh'
main.c:(.text+0x1c2d): undefined reference to `wmove'
cgminer-main.o: In function `hashmeter':
main.c:(.text+0x212a): undefined reference to `wmove'
main.c:(.text+0x213d): undefined reference to `wattr_on'
main.c:(.text+0x2150): undefined reference to `wprintw'
main.c:(.text+0x2163): undefined reference to `wattr_off'
main.c:(.text+0x2176): undefined reference to `wmove'
main.c:(.text+0x218c): undefined reference to `whline'
main.c:(.text+0x219f): undefined reference to `wmove'
main.c:(.text+0x21b7): undefined reference to `wprintw'
main.c:(.text+0x21c3): undefined reference to `wclrtoeol'
main.c:(.text+0x21d6): undefined reference to `wmove'
main.c:(.text+0x21ec): undefined reference to `whline'
main.c:(.text+0x2202): undefined reference to `wmove'
main.c:(.text+0x2218): undefined reference to `whline'
main.c:(.text+0x225f): undefined reference to `wmove'
main.c:(.text+0x229f): undefined reference to `wprintw'
main.c:(.text+0x22ab): undefined reference to `wclrtoeol'
main.c:(.text+0x22b7): undefined reference to `wrefresh'
main.c:(.text+0x23e3): undefined reference to `wmove'
cgminer-main.o: In function `watchdog_thread':
main.c:(.text+0x2617): undefined reference to `wmove'
main.c:(.text+0x265e): undefined reference to `wprintw'
main.c:(.text+0x266a): undefined reference to `wclrtoeol'
main.c:(.text+0x2686): undefined reference to `wmove'
main.c:(.text+0x2699): undefined reference to `wattr_on'
main.c:(.text+0x26ac): undefined reference to `wprintw'
main.c:(.text+0x26bf): undefined reference to `wattr_off'
main.c:(.text+0x26d2): undefined reference to `wmove'
main.c:(.text+0x26e8): undefined reference to `whline'
main.c:(.text+0x26fb): undefined reference to `wmove'
main.c:(.text+0x2713): undefined reference to `wprintw'
main.c:(.text+0x271f): undefined reference to `wclrtoeol'
main.c:(.text+0x2732): undefined reference to `wmove'
main.c:(.text+0x2748): undefined reference to `whline'
main.c:(.text+0x275e): undefined reference to `wmove'
main.c:(.text+0x2774): undefined reference to `whline'
main.c:(.text+0x27b1): undefined reference to `wmove'
main.c:(.text+0x2800): undefined reference to `wredrawln'
main.c:(.text+0x2814): undefined reference to `wredrawln'
main.c:(.text+0x2859): undefined reference to `wresize'
cgminer-main.o: In function `log_curses':
main.c:(.text+0x3dad): undefined reference to `vwprintw'
main.c:(.text+0x3db9): undefined reference to `wrefresh'
cgminer-main.o: In function `main':
main.c:(.text+0x46cf): undefined reference to `delwin'
main.c:(.text+0x46db): undefined reference to `delwin'
main.c:(.text+0x46e0): undefined reference to `endwin'
main.c:(.text+0x46e7): undefined reference to `stdscr'
main.c:(.text+0x46ec): undefined reference to `wrefresh'
main.c:(.text+0x4a8b): undefined reference to `initscr'
main.c:(.text+0x4ab7): undefined reference to `newwin'
main.c:(.text+0x4ad1): undefined reference to `newwin'
main.c:(.text+0x4ae5): undefined reference to `idlok'
main.c:(.text+0x4af6): undefined reference to `scrollok'
main.c:(.text+0x4b07): undefined reference to `leaveok'
main.c:(.text+0x4b18): undefined reference to `leaveok'
main.c:(.text+0x4b74): undefined reference to `wmove'
main.c:(.text+0x4bc0): undefined reference to `wprintw'
main.c:(.text+0x4bcc): undefined reference to `wclrtoeol'
main.c:(.text+0x4bd8): undefined reference to `wrefresh'
main.c:(.text+0x4c13): undefined reference to `wmove'
main.c:(.text+0x4c26): undefined reference to `wattr_on'
main.c:(.text+0x4c39): undefined reference to `wprintw'
main.c:(.text+0x4c4c): undefined reference to `wattr_off'
main.c:(.text+0x4c5f): undefined reference to `wmove'
main.c:(.text+0x4c75): undefined reference to `whline'
main.c:(.text+0x4c88): undefined reference to `wmove'
main.c:(.text+0x4ca0): undefined reference to `wprintw'
main.c:(.text+0x4cac): undefined reference to `wclrtoeol'
main.c:(.text+0x4cbf): undefined reference to `wmove'
main.c:(.text+0x4cd5): undefined reference to `whline'
main.c:(.text+0x4ceb): undefined reference to `wmove'
main.c:(.text+0x4d01): undefined reference to `whline'
main.c:(.text+0x4d4b): undefined reference to `wmove'
collect2: ld returned 1 exit status
make[1]: *** [cgminer] Fehler 1
make[1]: Verlasse Verzeichnis '/home/martin/cgminer/cgminer-1.2.4'
make: *** [install-recursive] Fehler 1
martin@latrop:~/cgminer/cgminer-1.2.4$


You're missing the libncurses dev library.

sudo apt-get install libncurses-dev
11207  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 13, 2011, 01:04:49 PM
@Diapolo. The HW errors are to to do with loading the kernel and running the code asynchronously with a flush afterwards. Because there's a flush right at the start it seems to pick up crap left over from the last cl code lying around. Maybe a flush/finish before that will help those of you that are seeing that. The HW errors are harmless if they don't continue after startup.

Utility is simply how many accepted shares are returned per minute.
Efficiency is calculated as the number of accepted shares compared to the number of requested work items. (i.e. it is NOT the rejection rate, but lots of rejects will decrease it). Mining software that does not search the entire work space offered to it tends to have low efficiency (such as cpu mining which gives up long before it's finished searching all hashes).

As for the intensity. Yeah it's just -too long- in GPU space if you set it too high. That's why I recommend 8 max for most cards and 9 for 6990 only.
11208  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 13, 2011, 11:25:27 AM
Quote from: ancow on July 13, 2011, 11:16:53 AM
Just wanted to mention: in the README file, the forum link still points to the old thread.

Quote from: ckolivas on July 13, 2011, 10:57:39 AM
Both include the new dynamic feature. Disable for dedicated mining!
What does this "dynamic feature" do, exactly?

Thanks for the heads up.

Dynamic keeps an eye on how long the GPU code is executing for and makes sure it always returns within a time frame that will allow the screen to take focus and refresh at a reliable rate that is visible to the user. When your machine is not in use by you, the GPU code will be able to do much more execution during this time frame which will raise your mhash. When you start using your machine, even just moving the mouse, clicking windows, browsing, and especially with watching videos, gaming etc, it will execute less and less hashing code to ensure it returns the GPU for the user experience. Basically it's a dynamic mining process that should make it invisible to the user who actually uses the GPU for regular PC uses, but mines with all the excess GPU power available. The difference on my desktop is up to 15MHash more when it's idle, but it's much snappier when I actually use it.
11209  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 13, 2011, 10:57:39 AM
@d3m0n1q_733rz is that different to the existing "atom" asm code in cgminer? does it need specific cpu support, and if so I'll need to have it as a separate optional assembly miner.

New windows build.
http://ck.kolivas.org/apps/cgminer-1.2.4-win32.zip

New Source tarball.
http://ck.kolivas.org/apps/cgminer-1.2.4-1.tar.bz2

Both include the new dynamic feature. Disable for dedicated mining!

Discussed the other problem of TurdHurdur's (off the forum) and it turns out it was missing the kernel file because he had done "make install" which doesn't really work properly unless you run from the directory you install to. The files should be all together in the same directory.
11210  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 13, 2011, 09:12:30 AM
The windows build is never quite as good because of the mingw interface. I do know the CPU usage is much much higher as a result of the pthread library. Dunno what to do about that.
11211  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 13, 2011, 06:22:28 AM
Quote from: TurdHurdur on July 13, 2011, 06:09:46 AM
Alright I did typo the subdomain, this time there was a

Code:
[2011-07-13 02:06:45] Long-polling activated for http://uscentral.btcguild.com:8332/LP

before...

Code:
[2011-07-13 02:06:47] Attempting to restart thread 0, idle for more than 60 seconds

with the rest being the same.

Can you do the same with -D and -P and log all the output and either pastebin it or email me or something please? (feel free to XXX out your name and pass in the logs)
11212  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 13, 2011, 06:03:33 AM
Quote from: Diapolo on July 13, 2011, 06:01:27 AM
Sounds good, if I like CGMiner, is there any way to talk about (or edit in) new or some more init values for the kernel? I guess it could be tweaked some more for even higher performance Smiley.

Sure. Email me, post here or see me on IRC? I hang out in #bitcoin-mining and #ozcoin (the pool I use).
11213  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 13, 2011, 05:57:03 AM
Quote from: Diapolo on July 13, 2011, 05:50:57 AM
I didn't try this version, but perhaps someone can answer my questions.

1. Are OpenCK kernels editable (.cl file somewhere) or is it hard coded? If no, could you please make that an option or make it modular.
2. Are the OpenCL init values for the kernel editable? If no, could you please make that an option or make it modular.
3. How much CPU time is eaten for each GPU running?

Thanks,
Dia

The kernels are source kernels .cl, built once and then loaded as binaries from then on.
The init values are the same as those for phatk. Internally I modify the kernel to suit how my code expects output results and to patch properly with BFI INT, BITALIGN and VECTORS, and to support 4 vectors as well.
The CPU time is negligible unless you use a very low intensity level and then (paradoxically) it rises slightly because it loops more often. On my 4x6970 machine pushing 1690 Mhash/s it is using 8% cpu with the amd phenom throttled to 800Mhz.
11214  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 13, 2011, 05:40:33 AM
Quote from: TurdHurdur on July 13, 2011, 04:46:10 AM
Debian 6 built from git:

Quote
$ cgminer -o http://domain.tld:8332 -u X -p Y -d 0 -D
cgminer version 1.2.4
--------------------------------------------------------------------------------
Totals:
--------------------------------------------------------------------------------
GPU 0: [0.0 Mh/s] [Q:0  A:0  R:0  HW:0  E:0%  U:0.00/m]
GPU 1: [0.0 Mh/s] [Q:0  A:0  R:0  HW:0  E:0%  U:0.00/m]


--------------------------------------------------------------------------------

[2011-07-13 00:42:22] Attempting to restart thread 0, idle for more than 60 seconds
[2011-07-13 00:42:22] Failed to pthread_cancel in reinit_gputhread
[2011-07-13 00:42:22] Received kill message
[2011-07-13 00:42:22] Thread 0 restarted
[2011-07-13 00:42:22] Attempting to restart thread 1, idle for more than 60 secondsSegmentation fault

/var/log/messages:
Quote
Jul 13 00:42:22 debianminer2 kernel: [  385.148119] cgminer[6395]: segfault at 28 ip 00007f296cb02ed4 sp 00007f29620c9d20 error 4 in libpthread-2.11.2.so[7f296cafa000+17000]

Thanks. That doesn't look like it ever started mining. Were all the login parameters ok? Did debug show you any http error messages or the like? Unfortunately cgminer doesn't abort when it fails to connect right at the start and may just sit there looking stupid.
11215  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 13, 2011, 05:32:03 AM
Quote from: jgarzik on July 13, 2011, 05:28:33 AM
Thanks for taking over "the C miner" project!

You're most welcome. Thanks so much for the original stable working framework and all the cpu mining bits without which it would have taken me much longer (if ever) to get this far!
11216  Bitcoin / Mining software (miners) / Re: Official CGMINER thread - CPU/GPU miner in C for linux/windows on: July 13, 2011, 05:26:34 AM
Yes, I am the linux kernel scheduler guy, -ck Smiley

Updated git tree:
I've added dynamic adjustment of intensity for usage on a normal desktop. This flag is enabled by default and tests to ensure the GPU is constantly available for desktop use and will scale intensity down when you are watching a movie, gaming or just about any other intense GPU usage, and scale it up when otherwise idle. This is best disabled on dedicated miners:

The new option is:
--no-dynamic|-n     Disable dynamic adjustment of intensity which normally maintains desktop interactivity

The difference can be quite dramatic in terms of how much smoother the desktop is, and how much higher the throughput is when it's idle.
11217  Bitcoin / Mining software (miners) / Re: cgminer - CPU/GPU miner in C for linux/windows on: July 13, 2011, 03:04:42 AM
Generated a new thread making it the official CGMINER thread since it is the primary development now (and not cpuminer) and long since has become a project in its own right.

http://forum.bitcoin.org/index.php?topic=28402.0
11218  Bitcoin / Mining software (miners) / OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1 on: July 13, 2011, 03:02:53 AM
This is the official thread for support and development of cgminer, the ASIC bitcoin miner written in c, cross platform for windows, linux, OSX and other, with monitoring, fanspeed control and remote interface capabilities. There is NO SUPPORT for CPU, GPU or altcoin mining in this thread, nor older versions with that functionality, nor any support for unofficial forks of this code.

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 free 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 for DOWNLOAD from here:
http://ck.kolivas.org/apps/cgminer


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: 4.11.0 see:
https://bitcointalk.org/index.php?topic=28402.msg44103867#msg44103867

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/

NOTE: This code is licensed under the GPLv3. This means that the source to any
modifications you make to this code MUST be provided by law if you distribute
modified binaries. See COPYING for details.


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, including ultra low overhead solo mining
- 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
- Hexfury USB support
- Onestring miner support
- BlackArrow Bitfury support
- BFL SC asic support
- Drillbit support
- Klondike support
- KnCminer Saturn support
- KnCminer Jupiter support
- KnCminer Neptune support
- Hashfast support
- Nanofury support
- Minion support
- Antminer U1/2+ support
- Bitmine A1 support
- Avalon2/3 support
- Bitmain S1 support
- Cointerra support
- Dragonmint T1 support
- BFx2 support
- Spondoolies SP10 support
- Spondoolies SP30 support
- Rockminer R-Box support
- Hashratio support
- Avalon4/5/6/7 support
- Compac gekko support
- Direct USB communications
- Device hotplug
- Heavily featured RPC API
- Multicast support
- Proxy support
- Coinbase decoding
- Lots of other stuff I can't remember. See options.

Sample output:
Code:
  cgminer version 4.2.1 - Started: [2014-03-29 10:06:52]
--------------------------------------------------------------------------------
 (5s):4.300T (1m):4.324T (5m):4.240T (15m):4.219T (avg):4.242Th/s
 A:9885432  R:64389  HW:1749  WU:59420.7/m
 Connected to au.ozco.in diff 6.45K with stratum as user ckolivas.0
 Block: a1e68974...  Diff:5.01G  Started: [12:48:48]  Best share: 3.41M  
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
 0: ANU 0       :                         | 1.989G / 1.980Gh/s
 1: NF1 0       :                         | 2.417G / 2.404Gh/s
 2: BXM 0       :                         | 3.798G / 3.781Gh/s
 3: BXM 1       :                         | 3.879G / 3.867Gh/s
 4: BXF 0       :  45.9C                  | 4.959G / 4.908Gh/s
 5: CTA 013219f9: 850MHz 75.4C 0.68V      | 1.056T / 803.3Gh/s
 6: CTA 013219fa: 850MHz 116.1C 0.68V     | 643.6G / 805.5Gh/s
 7: HFS Random  : 645MHz  86C  37% 0.79V  | 1.314T / 1.369Th/s
 8: BF1 0d110c15:                         | 2.275G / 2.288Gh/s
 9: HFS IceDrill: 604MHz  86C  23% 0.80V  | 1.214T / 1.250Th/s
 
---
USB menu:
Code:
Hotplug interval:5
8 USB devices, 7 enabled, 0 disabled, 1 zombie
[S]ummary of device information
[E]nable device
[D]isable device
[U]nplug to allow hotplug restart
[R]eset device USB
[L]ist all known devices
[B]lacklist current device from current instance of cgminer
[W]hitelist previously blacklisted device
[H]otplug interval (0 to disable)
Select an option or any other key to return

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
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:
[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
[T]oggle status switching:enabled
w[I]descreen:disabled
[Z]ero statistics
[L]og interval:5


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

See README, FGPA-README and ASIC-README for more information regarding command line parameters.

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

Solo mining to local bitcoind:

cgminer -o http://localhost:8332 -u username -p password --btc-address 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ

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.

---
SOLO MINING

Solo mining can be done efficiently as a single pool entry or a backup to
any other pooled mining and it is recommended everyone have solo mining set up
as their final backup in case all their other pools are DDoSed/down for the
security of the network. To enable solo mining, one must be running a local
bitcoind/bitcoin-qt or have one they have rpc access to. To do this, edit your
bitcoind configuration file (bitcoin.conf) with the following extra lines,
using your choice of username and password:

rpcuser=username
rpcpassword=password

Restart bitcoind, then start cgminer, pointing to the bitcoind and choose a
btc address with the following options, altering to suit their setup:

cgminer -o http://localhost:8332 -u username -p password --btc-address 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ


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

Q: What should I build in for a generic distribution binary?
A: There are a number of drivers that expect to be used on dedicated standalone
hardware. That said, the drivers that are designed to work generically with
USB on any hardware are the following:

Code:
--enable-avalon
--enable-avalon2
--enable-avalon4
--enable-avalon7
--enable-bflsc
--enable-bitfury
--enable-cointerra
--enable-drillbit
--enable-hashfast
--enable-hashratio
--enable-icarus
--enable-klondike

Q: How do I use the --decode function to decode a pool's coinbase?
A: You need to have a bitcoind with server functionality and pass it the
credentials as the first pool in your config, and pass the pool's address that
you wish to decode as the second pool configured. Note the bitcoind NEEDS the
http:// prefix.

e.g.:
./cgminer -o http://localhost:8332 -u user -p pass -o solo.ckpool.org:3333 -u 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ --decode

---

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. Driver development for new ASIC only bitcoin hardware can be
suitably sponsored.

Con Kolivas <kernel@kolivas.org>
15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ
11219  Bitcoin / Mining software (miners) / Re: cgminer - CPU and GPU mining software on: July 13, 2011, 02:26:00 AM
Updated source tree and new source version:
http://ck.kolivas.org/apps/cgminer-1.2.4.tar.bz2

Changes in this version:
I've updated the jansson library to be in line with the current version (make sure to do ./autogen.sh again if you're building from git)
Fixed a bug where pools that return empty body http requests (such as bitcoinpool.com on longpoll requests) would crash.
Updated the display to make sure all the threads' progress is updated regularly.
Made the default display on the status line wider to not cut off last characters on high hash counts.

and most importantly:

Implemented a watchdog thread that keeps an eye on all the worker threads. If they are idle for more than a minute it restarts them completely. Hopefully this should address the GPU going idle issue since it re-initialises the card. I suspect that since both threads on the same GPU go idle at the same time that it's actually within the opencl code that there is an issue and I hope that it will respond to re-init.
11220  Bitcoin / Mining software (miners) / Re: cgminer - CPU and GPU mining software on: July 13, 2011, 12:35:28 AM
Quote from: ewal on July 13, 2011, 12:12:28 AM
Another question for you.  Does cgminer adapt to changing pool behavior on the fly?  For example, a long poll URL changing to a new URL.  Or X-Roll-NTime support appearing and disappearing from getwork to getwork.  In other words, does cgminer work well when pointed at a proxy where any given getwork request may be handled by one of several real pools with different capabilities.

I had some problems with DiabloMiner with that and so I currently stick with a bunch of individually started poclbm miners, but I am very interested in the idea of one miner per rig instead of multiple miners per GPU.
I'm really not sure how it would cope with that. I doubt it will handle it gracefully.
Pages: « 1 ... 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 [561] 562 563 564 565 566 567 568 569 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!