Topic: ethminer-0.9.41-genoil-1.1 (Read 397326 times)
works on new adrenaline drivers AMD rx 570 ?
Hello! I would be glad if someone could tell me what port should I use to monitor Ethminer?
this is the actual maintained version: https://github.com/ethereum-mining/ethminer
Does anyone know where I can get a question about this version of ethminer answered? I am trying to use the API to manage my miners remotely ethminer is not responding. Thanks.
And if anyone is interested, I have tested Claymore and ethminer extensively and I believe ethminer is actually better than Claymores when you do not have to pay the dev fee to Claymore. I base this conclusion on the reported results from the pool and not on the hash rate displayed by the miner. The shares submitted to the pools by the two miners is about the same but when you subtract the dev fee, ethminer comes out slightly ahead.
There are some variations depending on the pool and coin but in general, this is the result I have determined.
Genoil's ethminer does not have an AP for remote management as far as I can tell, but the newer version does. It works with Claymores ethman.exe but I canot get it to work with my own code. The ethminer API is supposed to be compatible with claymores miner but my TCP client works fine with Claymores, not with ethminer.
Too much info. I was just hoping to find someone can tell me how to make the API work.
much better performance on ETH/ETC than Claymore miner. thank you guys!
hiya all i was hoping any one can help me here:
i been using ethminer for about 2 month now with no issue only last week i started to have a problem with the miner keep crashing
saying unspicfic error lunch error line 300, i have to clue what is tht and i haven't changed my sitting at all since i started using this miner, any 1 have an idea what is tht error and what is line 300 referring to ?!
thnx in advance
i been using ethminer for about 2 month now with no issue only last week i started to have a problem with the miner keep crashing
saying unspicfic error lunch error line 300, i have to clue what is tht and i haven't changed my sitting at all since i started using this miner, any 1 have an idea what is tht error and what is line 300 referring to ?!
thnx in advance
this is the actual maintained version: https://github.com/ethereum-mining/ethminer
I noticed that recently, but it doesn't have some improvements that I made like share submission timers.
Code:
stratum B-) Submitted and accepted in 99 ms.
this is the actual maintained version: https://github.com/ethereum-mining/ethminer
As can be seen by the lack of activity in this thread, JW(Genoil) stopped maintaining this miner about a year ago.
I've recently resumed updates on my fork for Linux/AMD. CUDA and Windows is untested and no longer guaranteed to work.
https://github.com/nerdralph/ethminer-nr
A Linux binary can be found in the releases folder.
I've recently resumed updates on my fork for Linux/AMD. CUDA and Windows is untested and no longer guaranteed to work.
https://github.com/nerdralph/ethminer-nr
A Linux binary can be found in the releases folder.
Yes somebody is using still it 
I just trust this miner the most 
This miner is pretty old and there is a problem lately. On compute mode on Fury and Vega there is a hashrate drop after 3-4 hours of mining. Up to 30-40% drop that requires miner reboot to get full hashrate back. It reports full hashrate but on pool it is lower or stale shares increase a lot. Doesn't happen on Graphics Mode on Fury, but on Vega you can't switch modes... I no longer have this problem, miner works great.
Overall I like it, hashrates are good, 40mh/s no problem on Vega.
I just trust this miner the most Overall I like it, hashrates are good, 40mh/s no problem on Vega.
Are there here anyone still using this miner?
could someone post a comparision between Claymore, Sgminer and Genoil here?
Is it still worth miners attention or it should be definitelly strike off?
could someone post a comparision between Claymore, Sgminer and Genoil here?
Is it still worth miners attention or it should be definitelly strike off?
Hi!
I'm just getting started and would apppreciate some help.
I'm using a Geforce 1080TI.
So the best would be to mine with CUDA, right?
How can I change my .bat file to mine with CUDA?
My .bat looks like this at the moment:
ethminer -G -S coinotron.com:3344 -O username.workername:workerpassword
Thanks in advance,
Foong
I'm just getting started and would apppreciate some help.
I'm using a Geforce 1080TI.
So the best would be to mine with CUDA, right?
How can I change my .bat file to mine with CUDA?
My .bat looks like this at the moment:
ethminer -G -S coinotron.com:3344 -O username.workername:workerpassword
Thanks in advance,
Foong
If you type "ethminer -h" in the command line it will spit out a complete list of commands you can use. This should have what you are looking for.
Posted it here, for the record.
Code:
I:\ethminer-0.9.41-genoil-1.1.9>ethminer -h
Genoil's ethminer 0.9.41-genoil-1.1.9nr
=====================================================================
Forked from github.com/ethereum/cpp-ethereum
CUDA kernel ported from Tim Hughes' OpenCL kernel
With contributions from nicehash, nerdralph, RoBiK and sp_
Please consider a donation to:
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
Usage ethminer [OPTIONS]
Options:
Work farming mode:
-F,--farm Put into mining farm mode with the work server at URL (default: http://127.0.0.
1:8545)
-FF,-FO, --farm-failover, --stratum-failover Failover getwork/stratum URL (default: disabl
ed)
--farm-retries Number of retries until switch to failover (default: 3)
-S, --stratum Put into stratum mode with the stratum server at host:port
-FS, --failover-stratum Failover stratum server at host:port
-O, --userpass Stratum login credentials
-FO, --failover-userpass Failover stratum login credentials (opti
onal, will use normal credentials when omitted)
--share-timeout reconnect if no response to submitted share received within n ms (non-functi
onal - for testing)
-SP, --stratum-protocol Choose which stratum protocol to use:
0: official stratum spec: ethpool, ethermine, coinotron, mph, nanopool (default)
1: eth-proxy compatible: dwarfpool, f2pool, nanopool
2: EthereumStratum/1.0.0: nicehash
-SE, --stratum-email Email address used in eth-proxy (optional)
--farm-recheck Leave n ms between checks for changed work (default: 500). When using stratu
m, use a high value (i.e. 2000) to get more stable hashrate output
Benchmarking mode:
-M [],--benchmark [] Benchmark for mining and exit; Optionally specify block number to ben
chmark against specific DAG.
--benchmark-warmup Set the duration of warmup for the benchmark tests (default: 3).
--benchmark-trial Set the duration for each trial for the benchmark tests (default: 3
).
--benchmark-trials Set the duration of warmup for the benchmark tests (default: 5).
Simulation mode:
-Z [],--simulation [] Mining test mode. Used to validate kernel optimizations. Optionally
specify block number.
Mining configuration:
-G,--opencl When mining use the GPU via OpenCL.
-U,--cuda When mining use the GPU via CUDA.
-X,--cuda-opencl Use OpenCL + CUDA in a system with mixed AMD/Nvidia cards. May require setting
--opencl-platform 1
--opencl-platform When mining using -G/--opencl use OpenCL platform n (default: 0).
--opencl-device When mining using -G/--opencl use OpenCL device n (default: 0).
--opencl-devices <0 1 ..n> Select which OpenCL devices to mine on. Default is to use all
-t, --mining-threads Limit number of GPU miners to n (default: use everything available on s
elected platform)
--allow-opencl-cpu Allows CPU to be considered as an OpenCL device if the OpenCL platform suppor
ts it.
--list-devices List the detected OpenCL/CUDA devices and exit. Should be combined with -G or -U
flag
-L, --dag-load-mode DAG generation mode.
parallel - load DAG on all GPUs at the same time (default)
sequential - load DAG on GPUs one after another. Use this when the miner crashes during DAG
generation
single - generate DAG on device n, then copy to other devices
--cl-extragpu-mem Set the memory (in MB) you believe your GPU requires for stuff other than mini
ng. default: 0
--cl-local-work Set the OpenCL local work size. Default is 64
--cl-global-work Set the OpenCL global work size as a multiple of the local work size. Default i
s 4096 * 64
--cuda-extragpu-mem Set the memory (in MB) you believe your GPU requires for stuff other than mi
ning. Windows rendering e.t.c..
--cuda-block-size Set the CUDA block work size. Default is 128
--cuda-grid-size Set the CUDA grid size. Default is 8192
--cuda-streams Set the number of CUDA streams. Default is 2
--cuda-schedule Set the schedule mode for CUDA threads waiting for CUDA devices to finish
work. Default is 'sync'. Possible values are:
auto - Uses a heuristic based on the number of active CUDA contexts in the process C and th
e number of logical processors in the system P. If C > P, then yield else spin.
spin - Instruct CUDA to actively spin when waiting for results from the device.
yield - Instruct CUDA to yield its thread when waiting for results from the device.
sync - Instruct CUDA to block the CPU thread on a synchronization primitive when waiting fo
r the results from the device.
--cuda-devices <0 1 ..n> Select which CUDA GPUs to mine on. Default is to use all
General Options:
-v,--verbosity <0 - 9> Set the log verbosity from 0 to 9 (default: 8).
-V,--version Show the version and exit.
-h,--help Show this help message and exit.
Genoil's ethminer 0.9.41-genoil-1.1.9nr
=====================================================================
Forked from github.com/ethereum/cpp-ethereum
CUDA kernel ported from Tim Hughes' OpenCL kernel
With contributions from nicehash, nerdralph, RoBiK and sp_
Please consider a donation to:
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
Usage ethminer [OPTIONS]
Options:
Work farming mode:
-F,--farm
1:8545)
-FF,-FO, --farm-failover, --stratum-failover
ed)
--farm-retries
-S, --stratum
-FS, --failover-stratum
-O, --userpass
-FO, --failover-userpass
onal, will use normal credentials when omitted)
--share-timeout
onal - for testing)
-SP, --stratum-protocol
0: official stratum spec: ethpool, ethermine, coinotron, mph, nanopool (default)
1: eth-proxy compatible: dwarfpool, f2pool, nanopool
2: EthereumStratum/1.0.0: nicehash
-SE, --stratum-email
--farm-recheck
m, use a high value (i.e. 2000) to get more stable hashrate output
Benchmarking mode:
-M [
chmark against specific DAG.
--benchmark-warmup
--benchmark-trial
).
--benchmark-trials
Simulation mode:
-Z [
specify block number.
Mining configuration:
-G,--opencl When mining use the GPU via OpenCL.
-U,--cuda When mining use the GPU via CUDA.
-X,--cuda-opencl Use OpenCL + CUDA in a system with mixed AMD/Nvidia cards. May require setting
--opencl-platform 1
--opencl-platform
--opencl-device
--opencl-devices <0 1 ..n> Select which OpenCL devices to mine on. Default is to use all
-t, --mining-threads
elected platform)
--allow-opencl-cpu Allows CPU to be considered as an OpenCL device if the OpenCL platform suppor
ts it.
--list-devices List the detected OpenCL/CUDA devices and exit. Should be combined with -G or -U
flag
-L, --dag-load-mode
parallel - load DAG on all GPUs at the same time (default)
sequential - load DAG on GPUs one after another. Use this when the miner crashes during DAG
generation
single
--cl-extragpu-mem Set the memory (in MB) you believe your GPU requires for stuff other than mini
ng. default: 0
--cl-local-work Set the OpenCL local work size. Default is 64
--cl-global-work Set the OpenCL global work size as a multiple of the local work size. Default i
s 4096 * 64
--cuda-extragpu-mem Set the memory (in MB) you believe your GPU requires for stuff other than mi
ning. Windows rendering e.t.c..
--cuda-block-size Set the CUDA block work size. Default is 128
--cuda-grid-size Set the CUDA grid size. Default is 8192
--cuda-streams Set the number of CUDA streams. Default is 2
--cuda-schedule
work. Default is 'sync'. Possible values are:
auto - Uses a heuristic based on the number of active CUDA contexts in the process C and th
e number of logical processors in the system P. If C > P, then yield else spin.
spin - Instruct CUDA to actively spin when waiting for results from the device.
yield - Instruct CUDA to yield its thread when waiting for results from the device.
sync - Instruct CUDA to block the CPU thread on a synchronization primitive when waiting fo
r the results from the device.
--cuda-devices <0 1 ..n> Select which CUDA GPUs to mine on. Default is to use all
General Options:
-v,--verbosity <0 - 9> Set the log verbosity from 0 to 9 (default: 8).
-V,--version Show the version and exit.
-h,--help Show this help message and exit.
Hi!
I'm just getting started and would apppreciate some help.
I'm using a Geforce 1080TI.
So the best would be to mine with CUDA, right?
How can I change my .bat file to mine with CUDA?
My .bat looks like this at the moment:
ethminer -G -S coinotron.com:3344 -O username.workername:workerpassword
Thanks in advance,
Foong
I'm just getting started and would apppreciate some help.
I'm using a Geforce 1080TI.
So the best would be to mine with CUDA, right?
How can I change my .bat file to mine with CUDA?
My .bat looks like this at the moment:
ethminer -G -S coinotron.com:3344 -O username.workername:workerpassword
Thanks in advance,
Foong
17 seems realistic, but try it with claymore's miner also. That miner is under development, this one is abandoned.
Allright. I tried mining with Claymore, but it allways shut down with the error, that no pool could be found, because nanopool seems not to be able to login via adress.
Installed crimson 15.12 for it and wanted to go back to mining with genoil, but now only my 770 is found by start_opencl.bat. Before that it never started the 770 via opencl, only via cuda.
Restarted my PC several times, plugged the monitor into both GPU, so that the nano is active, but nothing changed.
Also what batch did you use for claymore?
Sorry for my late reply.
Fixed it till late noon and was so happy after I was successfull.
What i've done was, that I removed the 770 and started again mining with the r9 nano. For now I had stable 25-26 mh/s. Only thing that makes me wonder are the calculated hashrates from nanopool. Is it possible that nanopool calculates your hashrate with the shares you've found and not the hashrate the miner shows?
But nevermind. I think my problem was, that there wasn't enough space between the nano and the 770, that the nano went too hot and got a shortage in hashrates from that.
I just moved the 770 one slot downwards and use it now as active gpu. So now I can mine 24/7 and can play when i want.
There was just one setting I needed to add to the batch "--opencl-platform 1", because the miner still didn't recognized the r9 nano after mining with claymore.
To answer your question at last: i tried mining with the opencl.bat
Now I have a last question for you:
I am now thinking of building a mining rig, which gpu's shall I buy? Going for the 1060/1070 (or maybe the 1070ti after the release on 11/2?) or the rx 480/580?
17 seems realistic, but try it with claymore's miner also. That miner is under development, this one is abandoned.
Allright. I tried mining with Claymore, but it allways shut down with the error, that no pool could be found, because nanopool seems not to be able to login via adress.
Installed crimson 15.12 for it and wanted to go back to mining with genoil, but now only my 770 is found by start_opencl.bat. Before that it never started the 770 via opencl, only via cuda.
Restarted my PC several times, plugged the monitor into both GPU, so that the nano is active, but nothing changed.
Also what batch did you use for claymore?
17 seems realistic, but try it with claymore's miner also. That miner is under development, this one is abandoned.
Allright. I tried mining with Claymore, but it allways shut down with the error, that no pool could be found, because nanopool seems not to be able to login via adress.
Installed crimson 15.12 for it and wanted to go back to mining with genoil, but now only my 770 is found by start_opencl.bat. Before that it never started the 770 via opencl, only via cuda.
Restarted my PC several times, plugged the monitor into both GPU, so that the nano is active, but nothing changed.
nobody tells me how to run this uncompilable GENOIL on Linux.
no deb packets , no ready-to-go tar.gz archives nothing.
unsubscribing. Im waiting 50 days.
no deb packets , no ready-to-go tar.gz archives nothing.
unsubscribing. Im waiting 50 days.
Hello there.
I started mining eth yesterday.
My Rig is:
i7-4700k(stock, don't see the point to oc)
evga z97 ftw (as I understand the specs, it only has pcie x16 (8x) for one GPU and 4x for 2 GPU)
16gb DDR3 Crucial Ballistics CL11
Sapphire R9 nano (main GPU for mining)
MSI GTX 770 4GB (2nd mining GPU and for gaming)
Samsung 840 Pro
Windows 10 pro 64bit
I have two starting .bat. One for each GPU.
As I read in a few threads, MH/s with the R9 nano differs from 20-35 MH/s. I only get a maximum of 10,5 MH/s.
My start_opencl.bat for the R9 looks like this:
"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
ethminer.exe --farm-recheck 200 -G -S eth-eu1.nanopool.org:9999 -FS eth-eu2.nanopool.org:9999 -O YOUR_ADDRESS/YOUR_WORKER/YOUR_EMAIL"
Is there anything wrong in the batch? I just used the recommended config from nanopool.
On top of the low MH/s for the nano, they aren't even stable. It's just one second at around 10 MH/s and then one or even two seconds at 5 MH/s.
I know that the Gtx 770 isn't a great deal (around 2 MH/s), because of the high energy comsumption, but I am not paying for the electricity used and just wanted to mine as much as I can or use it for gaming and let only the nano mine.
Is it a problem with the bat, is the mainboard the problem with it's pcie or anything else?
I am thankfull for every help.
I can't see anything wrong in the batch, but 10MH seems really low for an r9 card. I'd say you should try it with an other ethereum algo based coin, and if you get the same rate, there is a bottleneck somewhere, maybe it's not engough power or something, especially when it drops to its half sometimes.I started mining eth yesterday.
My Rig is:
i7-4700k(stock, don't see the point to oc)
evga z97 ftw (as I understand the specs, it only has pcie x16 (8x) for one GPU and 4x for 2 GPU)
16gb DDR3 Crucial Ballistics CL11
Sapphire R9 nano (main GPU for mining)
MSI GTX 770 4GB (2nd mining GPU and for gaming)
Samsung 840 Pro
Windows 10 pro 64bit
I have two starting .bat. One for each GPU.
As I read in a few threads, MH/s with the R9 nano differs from 20-35 MH/s. I only get a maximum of 10,5 MH/s.
My start_opencl.bat for the R9 looks like this:
"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
ethminer.exe --farm-recheck 200 -G -S eth-eu1.nanopool.org:9999 -FS eth-eu2.nanopool.org:9999 -O YOUR_ADDRESS/YOUR_WORKER/YOUR_EMAIL"
Is there anything wrong in the batch? I just used the recommended config from nanopool.
On top of the low MH/s for the nano, they aren't even stable. It's just one second at around 10 MH/s and then one or even two seconds at 5 MH/s.
I know that the Gtx 770 isn't a great deal (around 2 MH/s), because of the high energy comsumption, but I am not paying for the electricity used and just wanted to mine as much as I can or use it for gaming and let only the nano mine.
Is it a problem with the bat, is the mainboard the problem with it's pcie or anything else?
I am thankfull for every help.
It's not sometimes. It is every second. But i saw that i used this night farm-recheck 2000. Maybe that was the problem. I changed it to 200 in my break and the stats from nanopool showing me now 17 MH/s still increasing.
I dind't changed the bat for the GTX 770 but same here, nanopool is saying that it's mining with 8,5 MH/s.
My PSU is the Corsair cs 750. I think this must be enough.
@patofet: so you recommend me to try the claymore miner? Maybe this is something that i can do after work.
Hello there.
I started mining eth yesterday.
My Rig is:
i7-4700k(stock, don't see the point to oc)
evga z97 ftw (as I understand the specs, it only has pcie x16 (8x) for one GPU and 4x for 2 GPU)
16gb DDR3 Crucial Ballistics CL11
Sapphire R9 nano (main GPU for mining)
MSI GTX 770 4GB (2nd mining GPU and for gaming)
Samsung 840 Pro
Windows 10 pro 64bit
I have two starting .bat. One for each GPU.
As I read in a few threads, MH/s with the R9 nano differs from 20-35 MH/s. I only get a maximum of 10,5 MH/s.
My start_opencl.bat for the R9 looks like this:
"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
ethminer.exe --farm-recheck 200 -G -S eth-eu1.nanopool.org:9999 -FS eth-eu2.nanopool.org:9999 -O YOUR_ADDRESS/YOUR_WORKER/YOUR_EMAIL"
Is there anything wrong in the batch? I just used the recommended config from nanopool.
On top of the low MH/s for the nano, they aren't even stable. It's just one second at around 10 MH/s and then one or even two seconds at 5 MH/s.
I know that the Gtx 770 isn't a great deal (around 2 MH/s), because of the high energy comsumption, but I am not paying for the electricity used and just wanted to mine as much as I can or use it for gaming and let only the nano mine.
Is it a problem with the bat, is the mainboard the problem with it's pcie or anything else?
I am thankfull for every help.
I can't see anything wrong in the batch, but 10MH seems really low for an r9 card. I'd say you should try it with an other ethereum algo based coin, and if you get the same rate, there is a bottleneck somewhere, maybe it's not engough power or something, especially when it drops to its half sometimes.I started mining eth yesterday.
My Rig is:
i7-4700k(stock, don't see the point to oc)
evga z97 ftw (as I understand the specs, it only has pcie x16 (8x) for one GPU and 4x for 2 GPU)
16gb DDR3 Crucial Ballistics CL11
Sapphire R9 nano (main GPU for mining)
MSI GTX 770 4GB (2nd mining GPU and for gaming)
Samsung 840 Pro
Windows 10 pro 64bit
I have two starting .bat. One for each GPU.
As I read in a few threads, MH/s with the R9 nano differs from 20-35 MH/s. I only get a maximum of 10,5 MH/s.
My start_opencl.bat for the R9 looks like this:
"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
ethminer.exe --farm-recheck 200 -G -S eth-eu1.nanopool.org:9999 -FS eth-eu2.nanopool.org:9999 -O YOUR_ADDRESS/YOUR_WORKER/YOUR_EMAIL"
Is there anything wrong in the batch? I just used the recommended config from nanopool.
On top of the low MH/s for the nano, they aren't even stable. It's just one second at around 10 MH/s and then one or even two seconds at 5 MH/s.
I know that the Gtx 770 isn't a great deal (around 2 MH/s), because of the high energy comsumption, but I am not paying for the electricity used and just wanted to mine as much as I can or use it for gaming and let only the nano mine.
Is it a problem with the bat, is the mainboard the problem with it's pcie or anything else?
I am thankfull for every help.
It's not sometimes. It is every second. But i saw that i used this night farm-recheck 2000. Maybe that was the problem. I changed it to 200 in my break and the stats from nanopool showing me now 17 MH/s still increasing.
I dind't changed the bat for the GTX 770 but same here, nanopool is saying that it's mining with 8,5 MH/s.
My PSU is the Corsair cs 750. I think this must be enough.
@patofet: so you recommend me to try the claymore miner? Maybe this is something that i can do after work.
I don'0t know why but when I'm using this miner sometimes some card give me low mh/s something like all gpu are in 31mh/s and one 20mh/s in the same conditions claymore give me all gpu 31mh/s
Hello there.
I started mining eth yesterday.
My Rig is:
i7-4700k(stock, don't see the point to oc)
evga z97 ftw (as I understand the specs, it only has pcie x16 (8x) for one GPU and 4x for 2 GPU)
16gb DDR3 Crucial Ballistics CL11
Sapphire R9 nano (main GPU for mining)
MSI GTX 770 4GB (2nd mining GPU and for gaming)
Samsung 840 Pro
Windows 10 pro 64bit
I have two starting .bat. One for each GPU.
As I read in a few threads, MH/s with the R9 nano differs from 20-35 MH/s. I only get a maximum of 10,5 MH/s.
My start_opencl.bat for the R9 looks like this:
"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
ethminer.exe --farm-recheck 200 -G -S eth-eu1.nanopool.org:9999 -FS eth-eu2.nanopool.org:9999 -O YOUR_ADDRESS/YOUR_WORKER/YOUR_EMAIL"
Is there anything wrong in the batch? I just used the recommended config from nanopool.
On top of the low MH/s for the nano, they aren't even stable. It's just one second at around 10 MH/s and then one or even two seconds at 5 MH/s.
I know that the Gtx 770 isn't a great deal (around 2 MH/s), because of the high energy comsumption, but I am not paying for the electricity used and just wanted to mine as much as I can or use it for gaming and let only the nano mine.
Is it a problem with the bat, is the mainboard the problem with it's pcie or anything else?
I am thankfull for every help.
I can't see anything wrong in the batch, but 10MH seems really low for an r9 card. I'd say you should try it with an other ethereum algo based coin, and if you get the same rate, there is a bottleneck somewhere, maybe it's not engough power or something, especially when it drops to its half sometimes. I started mining eth yesterday.
My Rig is:
i7-4700k(stock, don't see the point to oc)
evga z97 ftw (as I understand the specs, it only has pcie x16 (8x) for one GPU and 4x for 2 GPU)
16gb DDR3 Crucial Ballistics CL11
Sapphire R9 nano (main GPU for mining)
MSI GTX 770 4GB (2nd mining GPU and for gaming)
Samsung 840 Pro
Windows 10 pro 64bit
I have two starting .bat. One for each GPU.
As I read in a few threads, MH/s with the R9 nano differs from 20-35 MH/s. I only get a maximum of 10,5 MH/s.
My start_opencl.bat for the R9 looks like this:
"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
ethminer.exe --farm-recheck 200 -G -S eth-eu1.nanopool.org:9999 -FS eth-eu2.nanopool.org:9999 -O YOUR_ADDRESS/YOUR_WORKER/YOUR_EMAIL"
Is there anything wrong in the batch? I just used the recommended config from nanopool.
On top of the low MH/s for the nano, they aren't even stable. It's just one second at around 10 MH/s and then one or even two seconds at 5 MH/s.
I know that the Gtx 770 isn't a great deal (around 2 MH/s), because of the high energy comsumption, but I am not paying for the electricity used and just wanted to mine as much as I can or use it for gaming and let only the nano mine.
Is it a problem with the bat, is the mainboard the problem with it's pcie or anything else?
I am thankfull for every help.
Jump to: