Pages:
Author

Topic: [ANN] ccminer 2.3 - opensource - GPL (tpruvot) - page 19. (Read 500113 times)

legendary
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
yep, its mainlined now
clg
newbie
Activity: 7
Merit: 0
Did the cuda-9 branch of the github get deleted or merged with the latest release?  I was able to compile the linux branch without issue using the 390 driver, but am not sure I'm getting the same hash rate I was before (too early in use to be sure).  Thanks!
sr. member
Activity: 487
Merit: 252
bou !
I am looking for the command that corresponds to -quitt ewbf, which serves to leave the ccminer in case of crash, but no answer ........
full member
Activity: 211
Merit: 119
Man is free at the moment he wishes to be.
I was just wondering if there is an option with ccminer like there is in cgminer to load balance across multiple pools

newbie
Activity: 1
Merit: 0
Hi, I have installed ccminer on my ubuntu step by step guided on github but when I'm runnung the app, I got 0.00H/s:
I have followed install file and install ccminer on ubuntu 16 but when I run ccminer It says .0.00H/s
```
./ccminer -a scrypt --url=stratum+tcp://stratum-ltc.antpool.com:8888 --userpass=user.worker:pass
*** ccminer 2.2.5 for nVidia GPUs by tpruvot@github ***
    Built with the nVidia CUDA Toolkit 8.0 64-bits

  Originally based on Christian Buchner and Christian H. project
  Include some kernels from alexis78, djm34, djEzo, tsiv and krnlx.

BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)

[2018-01-14 01:59:22] Starting on stratum+tcp://stratum-ltc.antpool.com:8888
[2018-01-14 01:59:22] NVML GPU monitoring enabled.
[2018-01-14 01:59:22] 1 miner thread started, using 'scrypt' algorithm.
[2018-01-14 01:59:24] Stratum difficulty set to 1024 (0.01562)
[2018-01-14 01:59:25] GPU #0: 32 hashes / 4.0 MB per warp.
[2018-01-14 01:59:25] GPU #0: Performing auto-tuning, please wait 2 minutes...
[2018-01-14 01:59:25] GPU #0: maximum total warps (BxW): 459
[2018-01-14 02:00:15] GPU #0: 950 MHz 50C FAN 0%
[2018-01-14 02:00:43] GPU #0:    0.00 hash/s with configuration F0x0
[2018-01-14 02:00:43] GPU #0: using launch configuration F0x0
[2018-01-14 02:00:43] GPU #0: Intensity set to 0, 0 cuda threads
[2018-01-14 02:00:43] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:00:47] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:00:51] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:00:55] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:00:59] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:03] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:07] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:11] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:15] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:19] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:23] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:27] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:31] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:35] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:35] GPU #0: 950 MHz 49C FAN 0%
[2018-01-14 02:01:39] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:40] Stratum difficulty set to 512 (0.00781)
[2018-01-14 02:01:43] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:47] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:51] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:55] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:01:59] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:03] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:07] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:11] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:15] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:19] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:23] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:27] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:31] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:35] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:39] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:43] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:47] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:48] scrypt block 1349785, diff 3541057.622
[2018-01-14 02:02:51] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:55] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:02:59] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:03:00] scrypt block 1349786, diff 3541057.622
[2018-01-14 02:03:03] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:03:07] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:03:11] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:03:15] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:03:17] GPU #0: 950 MHz 52C FAN 0%
[2018-01-14 02:03:19] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:03:23] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:03:27] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:03:31] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:03:35] GPU #0: ASUS 610M, 0.00 H/s
[2018-01-14 02:03:39] GPU #0: ASUS 610M, 0.00 H/s

```

What is problem?
legendary
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
"Could not resolve" means this url is dead
member
Activity: 81
Merit: 10
my server not work with mining monero
Mint 18 x64

 Stratum connection failed: Could not resolve host: pool.minexmr.com:4444,5555
 ...retry after 10 seconds
legendary
Activity: 3164
Merit: 1003



What could be causing this crash on line 219 ccminer-x64-2.2.2-cuda7.5? And when I click on close the program ...it will continue to mine.  It happens about once a day. Thx Smiley
Windows 8.1
jr. member
Activity: 119
Merit: 3
Hello @Epsylon3

I done some testing with CCminer 2.2.1, 2.2.2, 2.2.3, 2.2.4 & i was get something interesting with equihash algoritm

GPU: Gigabyte Windforce 2 NVIDIA GeForce GTX 1060 3GB (Samsung)
Video Driver:  388.71
OS: Windows 7 Service Pack 1

Msi Afterburner 4.4.2
Power Limit:   72% (86W)
Core Clock:    +170
VRam Clock:    +450 (not relevant for this algorit)

- Ccminer it make GPU clock usage to be: 1900-1940 Mhz with Power: 85-86W what result in 258-260 Sol/s

- Excavator v.1.3.8.a 1830-1880 Mhz with Power: 85-86W what result in ~280 Sol/s

- DTMS 5.8 GPU clock it goo to: 1830-1880 Mhz with Power: 85-86W what result in ~300 Sol/s

Well now what i will like to get is to see CCminer running on ~1900 Mhz with 86W on +300 Sol/s!!! so a tune like that can be that done in a future update ? if yes it will be damn greats  Roll Eyes

cheers
newbie
Activity: 2
Merit: 0
Hi all,

mb noob question, but how use failover pool in ccminer?
sr. member
Activity: 487
Merit: 252
bou !
thx , its work Smiley
legendary
Activity: 1797
Merit: 1028
hello

 sorry if I ask a stupid question,

but where do we put the worker name in ccminer? I have the 2.2.4 ccminer but in the readme I see no info on the worker.

IT DEPENDS ON THE POOL--

The worker name is placed according to pool-specific format.  It could be as follows:

  a) "-u USERNAME.WORKER"

  b) "-u WALLET.WORKER", or "-u WALLET/WORKER"

  c) "-u WALLET, -p WORKER,c=BTC,d=128"

where in example "c" the format works with YIIMP-style pools, and specifies coin and difficulty.  You'll need to consult pool documentation or the example files included within the CCminer archive for more variations.       --scryptr
newbie
Activity: 5
Merit: 0
Hi, is possible for ccminer to save a full log file?? Best is if i can set my prefered filename and directory.
I see no information in readme file.

i need a full log file for fine tuning and multi-gpu overclock.

Is possible to autostop miner when gpu crash ?

Thank you.
sr. member
Activity: 487
Merit: 252
bou !
hello

 sorry if I ask a stupid question,

but where do we put the worker name in ccminer? I have the 2.2.4 ccminer but in the readme I see no info on the worker.
member
Activity: 129
Merit: 11
Hashrate of card number #7 is always below average. I only see this with skein.
Replaced riser, PCI position...... to no evail

Maybe you have a monitor or a display port-vga converter connected to this card?
In this case, it will be slower than the rest
It's (linux) headless
newbie
Activity: 2
Merit: 0
Hashrate of card number #7 is always below average. I only see this with skein.
Replaced riser, PCI position...... to no evail

Maybe you have a monitor or a display port-vga converter connected to this card?
In this case, it will be slower than the rest
legendary
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
Hi,

Whats wrong with decred in 2.2.4?



nicehash use an unique special protocol for DCR and require their miner
member
Activity: 825
Merit: 18
MindMiner developer
Hi,

Whats wrong with decred in 2.2.4?

member
Activity: 129
Merit: 11
Mining Skein (NMS) on a 8GPU, 1080ti (Gigabyte Aorus), RIG:
Code:
[2018-01-09 08:43:25] GPU #6: Gigabyte GTX 1080 Ti, 822.21 MH/s
[2018-01-09 08:43:26] GPU #7: Gigabyte GTX 1080 Ti, 540.74 MH/s
[2018-01-09 08:43:27] GPU #0: Gigabyte GTX 1080 Ti, 829.26 MH/s
[2018-01-09 08:43:27] GPU #4: Gigabyte GTX 1080 Ti, 814.99 MH/s
[2018-01-09 08:43:27] GPU #3: Gigabyte GTX 1080 Ti, 829.01 MH/s
[2018-01-09 08:43:28] GPU #5: Gigabyte GTX 1080 Ti, 796.66 MH/s
[2018-01-09 08:43:28] GPU #1: Gigabyte GTX 1080 Ti, 817.42 MH/s
[2018-01-09 08:43:29] GPU #2: Gigabyte GTX 1080 Ti, 829.35 MH/s
[2018-01-09 08:43:29] GPU #6: Gigabyte GTX 1080 Ti, 830.06 MH/s
[2018-01-09 08:43:30] GPU #7: Gigabyte GTX 1080 Ti, 538.59 MH/s
[2018-01-09 08:43:30] GPU #3: 1948 MHz 3213.15 kH/W 257W 54C FAN 80%
[2018-01-09 08:43:31] GPU #0: Gigabyte GTX 1080 Ti, 825.22 MH/s
[2018-01-09 08:43:31] GPU #4: Gigabyte GTX 1080 Ti, 809.14 MH/s
[2018-01-09 08:43:31] GPU #3: Gigabyte GTX 1080 Ti, 814.39 MH/s
[2018-01-09 08:43:31] accepted: 19582/19591 (diff 5.516), 6277.25 MH/s yes!
[2018-01-09 08:43:32] GPU #5: Gigabyte GTX 1080 Ti, 800.12 MH/s
[2018-01-09 08:43:32] GPU #1: Gigabyte GTX 1080 Ti, 809.49 MH/s
[2018-01-09 08:43:33] GPU #2: Gigabyte GTX 1080 Ti, 832.50 MH/s
[2018-01-09 08:43:33] accepted: 19583/19592 (diff 7.522), 6276.70 MH/s yes!
[2018-01-09 08:43:33] GPU #6: Gigabyte GTX 1080 Ti, 821.11 MH/s
[2018-01-09 08:43:34] GPU #7: Gigabyte GTX 1080 Ti, 541.94 MH/s
[2018-01-09 08:43:35] GPU #4: Gigabyte GTX 1080 Ti, 808.11 MH/s
[2018-01-09 08:43:35] GPU #0: Gigabyte GTX 1080 Ti, 828.73 MH/s
[2018-01-09 08:43:35] GPU #3: Gigabyte GTX 1080 Ti, 831.86 MH/s
[2018-01-09 08:43:35] accepted: 19584/19593 (diff 5.165), 6284.99 MH/s yes!
[2018-01-09 08:43:36] accepted: 19585/19594 (diff 4.690), 6285.63 MH/s yes!
[2018-01-09 08:43:36] GPU #5: Gigabyte GTX 1080 Ti, 797.18 MH/s
[2018-01-09 08:43:36] GPU #1: Gigabyte GTX 1080 Ti, 820.37 MH/s
[2018-01-09 08:43:37] GPU #6: Gigabyte GTX 1080 Ti, 830.47 MH/s
[2018-01-09 08:43:37] GPU #2: Gigabyte GTX 1080 Ti, 830.60 MH/s
[2018-01-09 08:43:38] GPU #7: Gigabyte GTX 1080 Ti, 538.07 MH/s
[2018-01-09 08:43:39] GPU #4: Gigabyte GTX 1080 Ti, 811.61 MH/s
[2018-01-09 08:43:39] GPU #0: Gigabyte GTX 1080 Ti, 830.39 MH/s
[2018-01-09 08:43:39] GPU #3: Gigabyte GTX 1080 Ti, 829.54 MH/s
[2018-01-09 08:43:40] GPU #5: Gigabyte GTX 1080 Ti, 796.88 MH/s
[2018-01-09 08:43:40] GPU #1: Gigabyte GTX 1080 Ti, 816.00 MH/s
[2018-01-09 08:43:41] GPU #6: Gigabyte GTX 1080 Ti, 835.27 MH/s
[2018-01-09 08:43:41] GPU #2: Gigabyte GTX 1080 Ti, 825.18 MH/s
[2018-01-09 08:43:43] GPU #0: Gigabyte GTX 1080 Ti, 817.56 MH/s
[2018-01-09 08:43:43] GPU #4: Gigabyte GTX 1080 Ti, 812.48 MH/s
[2018-01-09 08:43:43] GPU #3: Gigabyte GTX 1080 Ti, 829.67 MH/s
[2018-01-09 08:43:43] GPU #7: Gigabyte GTX 1080 Ti, 541.50 MH/s
[2018-01-09 08:43:44] GPU #5: Gigabyte GTX 1080 Ti, 793.39 MH/s
[2018-01-09 08:43:44] accepted: 19586/19595 (diff 214.320), 6285.98 MH/s yes!
[2018-01-09 08:43:44] GPU #1: Gigabyte GTX 1080 Ti, 817.53 MH/s
[2018-01-09 08:43:45] GPU #6: Gigabyte GTX 1080 Ti, 831.20 MH/s
[2018-01-09 08:43:45] GPU #2: Gigabyte GTX 1080 Ti, 833.11 MH/s
[2018-01-09 08:43:46] accepted: 19587/19596 (diff 14.019), 6286.47 MH/s yes!
[2018-01-09 08:43:47] GPU #0: Gigabyte GTX 1080 Ti, 829.59 MH/s
[2018-01-09 08:43:47] accepted: 19588/19597 (diff 4.851), 6286.14 MH/s yes!
[2018-01-09 08:43:47] GPU #4: Gigabyte GTX 1080 Ti, 814.26 MH/s
[2018-01-09 08:43:47] GPU #3: Gigabyte GTX 1080 Ti, 831.35 MH/s
[2018-01-09 08:43:47] GPU #7: Gigabyte GTX 1080 Ti, 541.87 MH/s
[2018-01-09 08:43:48] GPU #5: Gigabyte GTX 1080 Ti, 794.58 MH/s
[2018-01-09 08:43:48] GPU #1: Gigabyte GTX 1080 Ti, 816.72 MH/s
[2018-01-09 08:43:49] GPU #6: Gigabyte GTX 1080 Ti, 832.66 MH/s
[2018-01-09 08:43:49] GPU #2: Gigabyte GTX 1080 Ti, 817.54 MH/s

Hashrate of card number #7 is always below average. I only see this with skein.
Replaced riser, PCI position...... to no evail

cmd-line: --algo=skein -o stratum+tcp://eu1.altminer.net:4933 -u ADDRESS.RIG1 -p c=NMS,d=4 --submit-stale --max-temp=65 --intensity=28 --api-bind=0.0.0.0:4068 --api-remote
legendary
Activity: 1484
Merit: 1082
ccminer/cpuminer developer
  -N, --statsavg        number of samples used to compute hashrate (default: 30)
Pages:
Jump to: