 Show Posts
|
|
Pages: [1] 2 3 4 »
|
pls help
[2016-08-02 20:29:56] Unable to query number of CUDA devices! Is an nVidia dri
r installed?
ccminer-x64 -a lbry -o stratum+tcp://lbc.coinmine.pl:8787 -u sl000.1 -p x --show-diff --cpu-priority 4
make sure you are running the latest driver.. what driver version are you running? |
|
|
|
Hello,
Another bug this morning! Lyra2v2 and daggerhashimoto are mining at the same time. NiceHash miner 1.6.1.0 is not reporting anything, but on nicehash.com I am seeing both them mining. I will try to disable lyra2v2 and see if the problem with NiceHash miner not reporting anything will disappear.
BR...
This is a known bug and will be fixed shortly.. Thanks for reporting (: |
|
|
|
I have 2 tickets outstanding on the old stake pool. It used to have instructions on importing the key to your wallet. I cannot access it. All I can find is my publickey. I try the importpubkey command and keep getting an error. I'm afraid to upgrade and loose access to my coins. I have tried google, and cannot find instructions. Do I need to import some kind of private key, which I didn't record?
Do you still have access to you old wallet's log file? There's a small chance the key is in there and I can guide you on what to find. Just PM me. theLosers106. |
|
|
|
Yes, 1.6.1 now runs and properly benchmarks and manages DggerHashimoto, but it does not report on its operating page what that GPU is doing. It does, however, report that GPU's performance to NiceHash.
What do you mean by that? Maybe a screenshot or any other details is needed to understand better your problem. Thanks. |
|
|
|
Dear users, NiceHash Miner v1.6.0.0 released We strongly recommend all users to update to latest NiceHash Miner version 1.6.0.0.Version 1.6.0.0 brings: - Increased performance on NVIDIA mining by automatically setting optimized power state.
- Up to 20% faster Decred on NVIDIA GPUs.
- On-GPU DAG generation for DaggerHashimoto for much faster benchmarking and no more HDD needed.
- Added tooltips for relevant config settings.
- Numerous bugfixes and small improvements.
Download the full package, unzip & run. Keep on mining!  Best regards, NiceHash team What does it mean: Increased performance on NVIDIA mining by automatically setting optimized power state This gives more hash rate? In the folder I see file nvidiasetp0state.exe Should I run it manually? I run the miner without GUI through the bat file from the bin folder. On some algo it does give some extra performance. All you need is to enable it in the settings (set NVIDIAP0State to true by checking the checkbox). Your millage may vary so just benchmark once before enabling it and once more after enabling it and see if you like the speed difference. |
|
|
|
Download the full package[/url], unzip & run.
Wish I could, but your insistance on using broken github makes it impossible for me. Still waiting on a reply to my earlier question of "where can I get it that does NOT use github". Here ya go a Google Drive link: https://drive.google.com/open?id=0B6kB9L8GNvQwMlIxZU9LTjNzbGsThis is a beta build so if anything weird happens, please do report back. Thanks. |
|
|
|
Hello everyone, I downloaded the v1.6 miner earlier today and am now unable to mine Daggerhashimoto. I was able to with the previous version of the miner. The benchmarks run fine, but if I try to start mining, I get an "Unhandled Exception" error "Index was outside the bounds of the array" with these details:
____________________________
Plez Halp
GTX670 FTW x 2
Core i7 2700
latest drivers and cuda software.
Try that: https://github.com/nicehash/NiceHashMiner/issues/131#issuecomment-227743341 |
|
|
|
"Keep on hashing!"...!!!???
Maybe I'll do, but only after you straighten your brains and tell me in a whisper "secret" reason for cunning behavior of your software. json file: "DisableAMDTempControl": true, ... "Algorithms": [ { "Name": "x11", "ExtraLaunchParameters": "--keccak-unroll 0 --hamsi-expand-big 4 --nfactor 10 --xintensity 640 --thread-concurrency 0 -- worksize 64 --gpu-threads 1 --gpu-engine 800-1030,900-1040,900-1040,950-1080 --gpu-memclock 1250,1300,1300,1500 --auto-fan --auto-gpu --gpu-fan 80-90,53-68,53-68,47-62 --temp-cutoff 78,78,78,77 --temp-overheat 74,74,74,74 --temp-target 70,70,70,68 ", from log file: [2016-06-08 20:21:49] [INFO] [AMD_OpenCL] Starting miner: --gpu-platform 0 -k x11 --url=stratum+tcp://x11.eu.nicehash.com:3336 -- userpass=1Jgw5D3L1ALJXMxWF9mBnf3TvEFMTWBJk3.worker2:x --api-listen --api-port=4050 --keccak-unroll 0 --hamsi-expand-big 4 --nfactor 10 --xintensity 1024 --thread-concurrency 0 --worksize 64 --gpu-threads 1 --device 0,1,2,3 Here you can see that xintensity not 640, but 1024. Temperature control settings and fans are not included in the string to start. HOW SO ??. For whom you are preparing such surprises. Im sorry , ,maybe a stupid question.
There do i have to put --temp-target --gpu-fan and so on parameters in NiceHash Miner ?
If i put it in settings -> AMD_OpenCL tab in ExtraLaunch Parameters , like --temp-target 71 --gpu-fan 30-90 --temp-cutoff 85
miner doesnt start , window flashes and disappear. Tried to put it in config.json , same result.
What am I doing wrong ?
P.S. Log file
Restarting miner..
[2016-06-15 09:20:21] [INFO] [AMD_OpenCL] Starting miner: --opencl --opencl-platform 0 --erase-dags old --temp-target 71 -S daggerhashimoto.eu.nicehash.com:3353 -O 1HTgxSxA72oXp7wst4QvK8fwCoqqUkWfyF.worker1:x --dag-dir data\AMD_OpenCL --report-port 4050 --opencl-devices 0 1 2 3 4
[2016-06-15 09:20:21] [INFO] [AMD_OpenCL] NumRetries: 23
[2016-06-15 09:20:21] [INFO] [AMD_OpenCL] Shutting down miner
P.S. And plz tell me what is avarage speed mining daggerhashimoto on:
270x -?
280x -?
This is a known bug and will be fixed in the next version. Thanks for spotting it. theLosers106. |
|
|
|
NHM 1.5.1 stops working (no error message except that it has stopped working) about once every two days. This is true on two different systems.
Send your log file to nhm@nicehash.com when it happens so that it is easier to see what is happening. Thanks, theLosers106. |
|
|
|
Hello all,
Tried all versions of sgminer on different pools and always get this error:
[23:22:32] C:\Users\KOLJOM~1\AppData\Local\Temp\\OCL7132T5.cl:59:10: fatal error
: 'blake.cl' file not found
#include "blake.cl"
^
1 error generated.
error: Clang front-end compilation failed!
Frontend phase failed compilation.
Error: Compiling CL to IR
[23:22:32] Failed to init GPU thread 0, disabling device 0
[23:22:32] Restarting the GPU from the menu will not fix this.
[23:22:32] Re-check your configuration and try restarting.
Press enter to continue:
GPU is MSI 380 4G
Driver 16.5.3
Latest AMD driver have an error in OpenCL compiler and can't find files to include. Easiest solution just to revert drivers, i use 15.11, works best for me. BTW, for eveyrone who is saying: best algo, low temps. Are you all drunk? It is low temp just because miner written in a shitty way. Another fix would be to copy all the kernel files (.cl) to C:\Users\KOLJOM~1\AppData\Local\Temp folder.. should fix it too.. |
|
|
|
Since NICEHASH MINER uses ethminer to mine for ETH, and that now supports NVIDIA2, will nicehash be upgrading nicehash miner with the newest ethminer? It now only mines ETH on NVIDIA5.x GPUs on my systems.
BTW, nicehash miner is a WINNER all around.
What GPU are you thinking about using? ETH needs GPU with at least 2GB of VRAM. |
|
|
|
Hello guys,
I really don't want to bother anyone with newbie question, but does anyone have working rig with 6*750ti, nicehach miner and ethereum? I am struggling for a long time with configuration, ant would appreciate any help. For now, I am only asking if anyone got it working, and if anyone want to help me to get it working.
I must say that every other algo is working like a charm except ether.
Thanks...
You will have to change some setting.. try to follow this user's guide and see if that helps ( https://github.com/nicehash/NiceHashMiner/issues/87#issuecomment-212713258).. you might need to play around with the numbers.. theLosers106 |
|
|
|
Hmm, unfortunately there seems to be a small but annoying bug - if you start with clean NHM (without config) then the entered Bitcoin address is not stored in config.json and therefore not used in the benchmark. We'll release a bugfix soon, meanwhile just "Start" miner for a few moments (will start mining on first algo - X11), then Stop miner, close NHM. Then start NHM again and you should be able to run benchmark.
Did that. Ethereum is still not running in the benchmark.. I'll download it again. yes mine seems to be stuck on ethereum as well.. wonder if its timing out because its taking too long to download the dag.. Do you have to close yours with the Task Manager ? it says please wait.. been like that for over 10 minutes.. i pushed stop and it doesnt stop.. seems stuck. the system is idle.. ok edit. the app isnt writing to the directory.. its the problem with the bitcoin address.. i just restarted and now all the benchmarks are zero. going to try it as admin. edit 2, didnt work. i just manually set the eth benchmark and now it seems to be working. so once the dag was made you can benchmark.. so the work around would be to put a high number manually in, like 50000000 then hit start, let it make the dag and stop and it run the benchmark. To @Stein & @aarons6 : Ethereum takes a while to create the DAG file. It may take around 10 minutes on a relatively new CPU to create it. Then the benchmark would start and you should see some GPU usage. Regarding the Bitcoin address, it will be fixed soon. Thanks for the feedback |
|
|
|
Hi Nicehash
I have downloaded version 1.4.0.0 and run it, also setup my bitcoin address. When I run the benchmark it tests all available algorithms. once it gets to testing Ethereum on Nvidia 3x it just sits there saying "please wait" for quite a long while, even clicking "stop benchmark" doesn't change it, I have to close the miner with task manager. Is this a problem with the miner or is there a workaround. Any help would be appreciated.
Thanks.
Deanrie69
I have the same problem but with Nvidia5x
Benchmarking ethereum takes a while because it first needs to create the DAG file which usually takes about 10 minutes.. Then it will start benchmarking which takes a bit more time.. On slower nVidia3.X GPUs, I would just suggest skipping it unless you really want to but that's just my opinion.. |
|
|
|
cpuminer-opt v3.1.13 just released. Added support for a few dusty algos:
sha256d, scrypt, scryptjane and yescrypt.
If anyone knows of anywhere to pool test any of the remaining algos please let me know.
I'll even test you your address.
You can test scryptjane at YACoin pool: Miner config: -o stratum+tcp://yacoin.club:3433 -O alenevaa.CPU1:1 You can use 2 ports: - 3433 difficulty 1 - 3434 difficulty 0.25 If you miner doesn't support difficulty less than 1 - use port 3433 Thanks but scryptjane has been pool tested. When I said remaining algos I was referring to the ones that have not yet been tested in a live pool. Specifically they are X17, blakecoin, fresh, cryptolight, and bastion. I have not been able to find any pools offering to mine coins using these algos. Sorry for the confusion. For blakecoin you could use this pool: http://ny2.blakecoin.com/index.php?page=login |
|
|
|
It's this file -> eth-miner.conf |
|
|
|
Post you config.json file too.. might be the ports that is not setup correctly..
hmm) where is it? I don't have such file. not in /ethminer, not in /eth-proxy. by the way I use stratum and genoil miner on other RIG, and it work fine. I copy it to my current rig and get this problem. win 8.1 Should be the same folder as the proxy.. |
|
|
|
Stratum Proxy: C:\Users\user\Documents\new\eth-proxy>eth-proxy.exe
2016-03-09 14:00:08,443 WARNING proxy # Ethereum Stratum proxy version: 0.0.4
2016-03-09 14:00:08,443 WARNING proxy # Trying to connect to Stratum pool at eth
-ru.dwarfpool.com:8008
2016-03-09 14:00:08,443 WARNING proxy # Trying to connect to failover Stratum po
ol at eth-eu.dwarfpool.com:8008
2016-03-09 14:00:08,467 INFO stats # 1 peers connected, state changed 1 times
2016-03-09 14:00:08,473 INFO proxy # Connected to Stratum pool at eth-ru.dwarfpo
ol.com:8008
Unhandled error in Deferred:
2016-03-09 14:00:08,507 INFO proxy # MAIN NEW_JOB
2016-03-09 14:00:08,517 INFO stats # 2 peers connected, state changed 1 times
2016-03-09 14:00:08,517 INFO proxy # Connected to Stratum pool at eth-eu.dwarfpo
ol.com:8008
2016-03-09 14:00:09,227 INFO proxy # MAIN NEW_JOB
......
Ethminer: C:\Users\user\Documents\new\ethminer-genoil>ethminer --farm-recheck 200 -G -F ht
tp://127.0.0.1:8080/rig2 --dag-dir C:\Users\user\Documents\new\ethminer-genoil\dag0
Genoil's ethminer 0.9.41-genoil-1.0.3
=====================================================================
Forked from github.com/ethereum/cpp-ethereum
CUDA kernel ported from Tim Hughes' OpenCL kernel
With contributions from RoBiK, tpruvot and sp_
Please consider a donation to:
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
Found suitable OpenCL device [Hawaii] with 8589934592 bytes of GPU memory
miner 13:44:15|main Getting work package...
X 13:44:15|main Failed to submit hashrate.
X 13:44:15|main Dynamic exception type: class jsonrpc::JsonRpcException
std::exception::what: Exception -32603 : INTERNAL_ERROR: : <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request - Invalid Hostname</h2>
<hr><p>HTTP Error 400. The request hostname is invalid.</p>
</BODY></HTML>
JSON-RPC problem. Probably couldn't connect. Retrying in 1...
miner 13:44:17|main Getting work package...
X 13:44:17|main Failed to submit hashrate.
X 13:44:17|main Dynamic exception type: class jsonrpc::JsonRpcException
std::exception::what: Exception -32603 : INTERNAL_ERROR: : <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request - Invalid Hostname</h2>
<hr><p>HTTP Error 400. The request hostname is invalid.</p>
</BODY></HTML>
......
Direct connection (without proxy) to the pool work fine. Where is problem? Post you config.json file too.. might be the ports that is not setup correctly.. |
|
|
|
The new Nicehashminer is calculating wrong. The benchmark say both quark and ethereum has 71.000 kh/s, when I press start it goes to eth and starts mining. The problem is that I only get about 34.000 kh/s. This makes eth mining less profit than quark that run at 71.000 kh/s. I´m going back to last version that calculates profit correct.
What do you mean both get 71.000 kh/s (I'm assuming 71MH/s?) and suddenly you get only about 34.000 kh/s? Yes 71MH/s is 71000 kh/s. Benchmark show 71MH/s on both Quark and Eth. When I start the mining nisehashminer pick Eth as the most profitable and stars mining but I only mine with 34MH/s. At that speed its not the most profitable. The benchmark is reporting wrong speed and the fix is to manualy put in 34MH/s in the json and it now works as intended. May I know what Windows are you using? Win 10 There's someone else with this problem ( https://github.com/nicehash/NiceHashMiner/issues/36#issuecomment-193107134) This is most probably due to this problem reported by many users: https://forum.ethereum.org/discussion/comment/20468/#Comment_20468Some how the benchmark is reporting the wrong speed..  |
|
|
|
The new Nicehashminer is calculating wrong. The benchmark say both quark and ethereum has 71.000 kh/s, when I press start it goes to eth and starts mining. The problem is that I only get about 34.000 kh/s. This makes eth mining less profit than quark that run at 71.000 kh/s. I´m going back to last version that calculates profit correct.
What do you mean both get 71.000 kh/s (I'm assuming 71MH/s?) and suddenly you get only about 34.000 kh/s? Yes 71MH/s is 71000 kh/s. Benchmark show 71MH/s on both Quark and Eth. When I start the mining nisehashminer pick Eth as the most profitable and stars mining but I only mine with 34MH/s. At that speed its not the most profitable. The benchmark is reporting wrong speed and the fix is to manualy put in 34MH/s in the json and it now works as intended. May I know what Windows are you using? |
|
|
|
|
