Search content
Sort by

Showing 10 of 10 results by dr.
Post
Topic
Board Mining (Altcoins)
Re: [CPU-XMR] JerryMiner
by
dr.
on 19/10/2017, 22:43:48 UTC
What version of the processor (full)?
Launch parameters.
The exact number of hashes per second on my miner and on others (and the number of threads).
In general, this is strange.
Sure, here:

w/o AES-NI @Intel Xeon E5540:
your miner v1.1.0 ~117-128h/s:
Code:
cryptonight-64 -o stratum+tcp://europe.monero.miningpoolhub.com:20580 -u drigger.%computername% -p x -t 16
cpuminer-opt v3.7.0 ~148-160h/s:
Code:
cpuminer -a cryptonight -o stratum+tcp://europe.monero.miningpoolhub.com:20580 -u drigger.%computername% -p x -t 16

w/ AES-NI @Intel i5-2500K OC:
your miner v1.1.0 ~96-112h/s:
Code:
cryptonight-64 -o stratum+tcp://europe.monero.miningpoolhub.com:20580 -u drigger.%computername% -p x -t 3
xmr-stak-cpu 1.3.0-1.5.0 ~240-254h/s:
Code:
"cpu_threads_conf" :
[
   { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 1 },
   { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 2 },
   { "low_power_mode" : false, "no_prefetch" : true, "affine_to_cpu" : 3 },
],
"use_slow_memory" : "never",
"nicehash_nonce" : false,
"aes_override" : true,
"use_tls" : false,
"tls_secure_algo" : true,
"tls_fingerprint" : "",
"pool_address" : "europe.monero.miningpoolhub.com:20580",
"wallet_address" : "drigger.drHome",
"pool_password" : "x",
"call_timeout" : 10,
"retry_time" : 10,
"giveup_limit" : 0,
"verbose_level" : 4,
"h_print_time" : 300,
"daemon_mode" : true,
"output_file" : "",
"httpd_port" : 0,
"prefer_ipv4" : true
Post
Topic
Board Mining (Altcoins)
Re: [CPU-XMR] JerryMiner
by
dr.
on 19/10/2017, 20:23:09 UTC
At the moment this is the fastest xmr miner implementation for cpu
Actually, it is not, at least for now Wink
cpuminer-opt is ~1.5x faster w/o AES-NI and xmr-stak-cpu is almost 2x times faster w/ AES-NI on my Intel CPUs.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.5.2 (Linux / Windows)
by
dr.
on 19/10/2017, 02:17:33 UTC
dstm, Sorry for being persistent, but is there any way to use your miner with a proxy? EWBF, ccminer and, basically, any other miner I've used worked flawlessly with my HTTP proxy server.

Don't hesitate to ask Smiley

Could you please describe in more detail how you setup your proxy - I'll try to reproduce why it isn't working.
Sure. I'm using latest 3proxy, my current config looks like this

Has all internet access pass trough the proxy? i.e. is everything else blocked?
Nope, there are some basic service ports opened (i.e. 23, 80, 443 etc. + a couple of special ports, like 20017, which I'm using in a config I've posted earlier), but everything else is closed.
So if there's a need to connect to some exotic pool ports like 3333 etc., I have to individually re-route specific miners through the proxy.

This is why it's not working, you have to open 3443 for zm. Zm won't work if it can't submit dev fee shares.
Thanks! That's exactly what I thought the reason was, actually Wink
You should mention it somewhere in description here, could be useful for other people using port forwarding/proxy.
However, for people like me (with isolated local networks, limited number of open ports and no access to external port management) - there is another issue. It seems you've hardcoded pool addresses for devfee, so they don't actually went through proxy even if I forward the right port (3443 in my case). I've managed to solve it easily by additionally remapping local port AND pool hostname (3proxy+edited windows hosts file, in my case). Hope it also come in handy for others...
Post
Topic
Board Mining (Altcoins)
Re: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.5.2 (Linux / Windows)
by
dr.
on 18/10/2017, 22:25:31 UTC
dstm, Sorry for being persistent, but is there any way to use your miner with a proxy? EWBF, ccminer and, basically, any other miner I've used worked flawlessly with my HTTP proxy server.

Don't hesitate to ask Smiley

Could you please describe in more detail how you setup your proxy - I'll try to reproduce why it isn't working.
Sure. I'm using latest 3proxy, my current config looks like this

Has all internet access pass trough the proxy? i.e. is everything else blocked?
Nope, there are some basic service ports opened (i.e. 23, 80, 443 etc. + a couple of special ports, like 20017, which I'm using in a config I've posted earlier), but everything else is closed.
So if there's a need to connect to some exotic pool ports like 3333 etc., I have to individually re-route specific miners through the proxy.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.5.2 (Linux / Windows)
by
dr.
on 18/10/2017, 21:10:11 UTC
Can you give example of batch file?

timeout 15
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
zm --server eu1-zcash.flypool.org --port 3333 --cuda_devices 0 1 2 3 4 --user t1JjQf4RUWSNxmEzsr2sbTJE34ghtAQ5ztE.gsmp106 --pass x --templimit 81 --log 2 --pec
All lines except the last are for amd. They has no sense for nvidia.

Also, this last line contains EWBF parameters (--cuda_devices == --dev, --templimit ~= --temp-target, log and pec) that will not work with dstm's ZCash miner Wink
Post
Topic
Board Mining (Altcoins)
Re: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.5.2 (Linux / Windows)
by
dr.
on 18/10/2017, 20:57:47 UTC
dstm, Sorry for being persistent, but is there any way to use your miner with a proxy? EWBF, ccminer and, basically, any other miner I've used worked flawlessly with my HTTP proxy server.

Don't hesitate to ask Smiley

Could you please describe in more detail how you setup your proxy - I'll try to reproduce why it isn't working.
Sure. I'm using latest 3proxy, my current config looks like this:
Code:
internal 192.168.0.7
external xxx.xxx.xxx.104
nserver 8.8.8.8
nscache 65536

auth none
log
tcppm -ixxx.xxx.xxx.104 20017 eu1-zcash.flypool.org 3333
tcppm -i192.168.0.7 20017 eu1-zcash.flypool.org 3333

maxconn 2047
proxy
admin -p8081
, where 20017 is one of my internal open ports, xxx.xxx.xxx.104 and 192.168.0.7 are external and internal IPs of my DMZ server.

My zm batch file looks like this:
Code:
@echo off
cd /d %~dp0

:start
zm --server xxx.xxx.xxx.104 --port 20017 --user t1xxxxxxxxxxxxxxxxxxxxxxxx.%computername% --pass z
ping 127.0.0.1 > nul
goto start
Post
Topic
Board Mining (Altcoins)
Re: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.5.2 (Linux / Windows)
by
dr.
on 18/10/2017, 20:15:17 UTC
dstm, Sorry for being persistent, but is there any way to use your miner with a proxy? EWBF, ccminer and, basically, any other miner I've used worked flawlessly with my HTTP proxy server.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.5.2 (Linux / Windows)
by
dr.
on 18/10/2017, 15:42:55 UTC
Working fine and gives higher hashrate than EWBF (W10.16299.19, NVD387.92, eu1-zcash.flypool.org). Tested with under/overclocked GTX10603GB/6GB, GTX1070, GTX1080.
Although, it also gives me "connection error 100061" when using proxy, which is kinda sad =(
Post
Topic
Board Mining (Altcoins)
Re: excavator - multi-algorithm advanced NVIDIA CUDA miner [1.1.0a]
by
dr.
on 10/03/2017, 18:16:48 UTC
Thanks for reply, already done that  Wink
Post
Topic
Board Mining (Altcoins)
Re: excavator - multi-algorithm advanced NVIDIA CUDA miner [1.1.0a]
by
dr.
on 10/03/2017, 16:25:42 UTC
Having issues when trying to mine equihash on nanopool, any advices on how to fix?
Code:
excavator -a equihash -s zec-eu1.nanopool.org:6666 -u ***:z -p 0 -d 2 -cd 0 -cd 0
Code:
==================== www.nicehash.com ====================
         Excavator v1.1.0a GPU Miner for NiceHash.
    Copyright (C) 2017 NiceHash. All rights reserved.
  Developed by djeZo with help and contributors of code:
    pallas, Vorksholk, bitbandi, ocminer
==================== www.nicehash.com ====================

[19:16:51][0x000028c8][info] Log started
[19:16:51][0x000028c8][info] Miner starting up, press [CTRL + C] to quit
[19:16:51][0x000028c8][info] net | Connecting to zec-eu1.nanopool.org:6666
[19:16:52][0x00002830][info] net | Connected!
[19:16:52][0x00001824][info] device#0 | Initializing thread #0 GPU#0 GeForce GTX 1080
[19:16:52][0x00001d60][info] device#1 | Initializing thread #1 GPU#0 GeForce GTX 1080
[19:16:52][0x00002830][warning] net | Net error: JSON member "result" not expected type: Array
[19:16:53][0x00001824][info] device#0 | Algorithm: CUDA-equihash parameters: M=1
[19:16:54][0x00002830][info] net | Authorized as ***
[19:16:55][0x00001d60][info] device#1 | Algorithm: CUDA-equihash parameters: M=1
[19:16:56][0x00002830][warning] net | Net error: JSON member missing: "error"
[19:16:58][0x00002830][warning] net | Net error: JSON member missing: "error"