Is there Windows build?
Yes in the releases folder of 110 branch (CUDA compute 5.2 only, OpenCL AMD+ NVidia)
Topic: ethminer-0.9.41-genoil-1.1 - page 60. (Read 397387 times)
Yes in the releases folder of 110 branch (CUDA compute 5.2 only, OpenCL AMD+ NVidia)
Is there Windows build?
1.1 pre-release is out:
https://github.com/Genoil/cpp-ethereum/tree/110/
- no more DAG files (both CUDA/OpenCL)
- CUDA Compute 2.0 support is back
It looks like it's all working but I'm releasing early so you can help me test. Don't forget to remove your -E and -R params, that is all gone now.
CPU util seems down, RAM usage down of course. CPU validation is still in there, using the light cache.
no devfee, but do send me some ETH if you like it
https://github.com/Genoil/cpp-ethereum/tree/110/
- no more DAG files (both CUDA/OpenCL)
- CUDA Compute 2.0 support is back
It looks like it's all working but I'm releasing early so you can help me test. Don't forget to remove your -E and -R params, that is all gone now.
CPU util seems down, RAM usage down of course. CPU validation is still in there, using the light cache.
no devfee, but do send me some ETH if you like it
So during DAG change it shouldn't crash?
haven't tested that yet.
PRE-RELEASE BUILT AND RUNNING--
At least, the DAG file is being generated. I removed my "-E" and "-R" flags, but is there a flag for GPU DAG file generation, or is that feature on by default?
The version label is still set at 1.0.8, by the way. Early, but the only bug I see. --scryptr
You sure you checked out the right branch? Version is set to 1.1
And no there is no flag. To hell with dag files
1.1 pre-release is out:
https://github.com/Genoil/cpp-ethereum/tree/110/
- no more DAG files (both CUDA/OpenCL)
- CUDA Compute 2.0 support is back
It looks like it's all working but I'm releasing early so you can help me test. Don't forget to remove your -E and -R params, that is all gone now.
CPU util seems down, RAM usage down of course. CPU validation is still in there, using the light cache.
no devfee, but do send me some ETH if you like it
https://github.com/Genoil/cpp-ethereum/tree/110/
- no more DAG files (both CUDA/OpenCL)
- CUDA Compute 2.0 support is back
It looks like it's all working but I'm releasing early so you can help me test. Don't forget to remove your -E and -R params, that is all gone now.
CPU util seems down, RAM usage down of course. CPU validation is still in there, using the light cache.
no devfee, but do send me some ETH if you like it
So during DAG change it shouldn't crash?
haven't tested that yet.
PRE-RELEASE BUILT AND RUNNING--
At least, the DAG file is being generated. I removed my "-E" and "-R" flags, but is there a flag for GPU DAG file generation, or is that feature on by default?
The version label is still set at 1.0.8, by the way. Early, but the only bug I see. --scryptr
1.1 pre-release is out:
https://github.com/Genoil/cpp-ethereum/tree/110/
- no more DAG files (both CUDA/OpenCL)
- CUDA Compute 2.0 support is back
It looks like it's all working but I'm releasing early so you can help me test. Don't forget to remove your -E and -R params, that is all gone now.
CPU util seems down, RAM usage down of course. CPU validation is still in there, using the light cache.
no devfee, but do send me some ETH if you like it
Oh, Genoil, you are awesome! https://github.com/Genoil/cpp-ethereum/tree/110/
- no more DAG files (both CUDA/OpenCL)
- CUDA Compute 2.0 support is back
It looks like it's all working but I'm releasing early so you can help me test. Don't forget to remove your -E and -R params, that is all gone now.
CPU util seems down, RAM usage down of course. CPU validation is still in there, using the light cache.
no devfee, but do send me some ETH if you like it
Thanks!
I'll test it ASAP.
1.1 pre-release is out:
https://github.com/Genoil/cpp-ethereum/tree/110/
- no more DAG files (both CUDA/OpenCL)
- CUDA Compute 2.0 support is back
It looks like it's all working but I'm releasing early so you can help me test. Don't forget to remove your -E and -R params, that is all gone now.
CPU util seems down, RAM usage down of course. CPU validation is still in there, using the light cache.
no devfee, but do send me some ETH if you like it
https://github.com/Genoil/cpp-ethereum/tree/110/
- no more DAG files (both CUDA/OpenCL)
- CUDA Compute 2.0 support is back
It looks like it's all working but I'm releasing early so you can help me test. Don't forget to remove your -E and -R params, that is all gone now.
CPU util seems down, RAM usage down of course. CPU validation is still in there, using the light cache.
no devfee, but do send me some ETH if you like it
So during DAG change it shouldn't crash?
haven't tested that yet.
1.1 pre-release is out:
https://github.com/Genoil/cpp-ethereum/tree/110/
- no more DAG files (both CUDA/OpenCL)
- CUDA Compute 2.0 support is back
It looks like it's all working but I'm releasing early so you can help me test. Don't forget to remove your -E and -R params, that is all gone now.
CPU util seems down, RAM usage down of course. CPU validation is still in there, using the light cache.
no devfee, but do send me some ETH if you like it
https://github.com/Genoil/cpp-ethereum/tree/110/
- no more DAG files (both CUDA/OpenCL)
- CUDA Compute 2.0 support is back
It looks like it's all working but I'm releasing early so you can help me test. Don't forget to remove your -E and -R params, that is all gone now.
CPU util seems down, RAM usage down of course. CPU validation is still in there, using the light cache.
no devfee, but do send me some ETH if you like it
So during DAG change it shouldn't crash?
1.1 pre-release is out:
https://github.com/Genoil/cpp-ethereum/tree/110/
- no more DAG files (both CUDA/OpenCL)
- CUDA Compute 2.0 support is back
It looks like it's all working but I'm releasing early so you can help me test. Don't forget to remove your -E and -R params, that is all gone now.
CPU util seems down, RAM usage down of course. CPU validation is still in there, using the light cache.
no devfee, but do send me some ETH if you like it
https://github.com/Genoil/cpp-ethereum/tree/110/
- no more DAG files (both CUDA/OpenCL)
- CUDA Compute 2.0 support is back
It looks like it's all working but I'm releasing early so you can help me test. Don't forget to remove your -E and -R params, that is all gone now.
CPU util seems down, RAM usage down of course. CPU validation is still in there, using the light cache.
no devfee, but do send me some ETH if you like it
I just switched from QTMiner to genoil 1.0.9 and after 2 hours of running on ethermine.org I've gotten 2 stale shares and 35 good shares @20MH/s (AMD 380).
Is this normal?
After running QTMiner on 24H it didn't produce a single stale share.
Edit: PS: The stale shares are only reported in ethermine, in the console all shares are valid.
Is this normal?
After running QTMiner on 24H it didn't produce a single stale share.
Edit: PS: The stale shares are only reported in ethermine, in the console all shares are valid.
and I have to ask once again about failover exactly..
because I didn't notice the answer and I am stuck..
How to write failover command?
if I have fe: pool1 pool2 and pool3..
ethminer -G -S pool1 datas and?...
because I didn't notice the answer and I am stuck..
How to write failover command?
if I have fe: pool1 pool2 and pool3..
ethminer -G -S pool1 datas and?...
-S pool1 -FS pool2 -O credentials1 -FO credentials2.
You can omit -FO when it's identical to -O.
Thanks, I think it should be pin to first post
Weird the readme I have must be from a older version of the program. It doesn't list the FS command.
and I have to ask once again about failover exactly..
because I didn't notice the answer and I am stuck..
How to write failover command?
if I have fe: pool1 pool2 and pool3..
ethminer -G -S pool1 datas and?...
because I didn't notice the answer and I am stuck..
How to write failover command?
if I have fe: pool1 pool2 and pool3..
ethminer -G -S pool1 datas and?...
-S pool1 -FS pool2 -O credentials1 -FO credentials2.
You can omit -FO when it's identical to -O.
Thanks, I think it should be pin to first post
For some reason after upgrading to Crimson 16.5.2.1 or any version after 15.12, my 5 R9-390s mine slower from 148-150 MH/s to 120-124 MH/s, same thing happened w/ NH miner. However, Claymore dual miner was able to mine at the same speed. Can this be fixed?
Will their be any more updates to this miner? By this I mean for more management on how hard you can push your card to work. Like in Claymore's miner you can set how hard and by default cards are set to intensity of 9 and can do less to put less stress on card. Hoping you guys come up with something like this in the future.
Half global-work or grid size until you are satisfied. So 4096, 2048, 1024 etc.
I'll add a more traditional intensity parameter in an upcoming release.
Genoli the current failover doesn't work properly. When the main pool comes back up the miners don't swap back to the mainpool, they have to be reset.
It isn't built like that but I understand why you would like it to behave like that. I'll keep it in mind, thanks.
Yeah... Kinda important. Otherwise I have to take the backup stratum down to make them fall back to the primary stratum.
Genoli the current failover doesn't work properly. When the main pool comes back up the miners don't swap back to the mainpool, they have to be reset.
It isn't built like that but I understand why you would like it to behave like that. I'll keep it in mind, thanks.
and I have to ask once again about failover exactly..
because I didn't notice the answer and I am stuck..
How to write failover command?
if I have fe: pool1 pool2 and pool3..
ethminer -G -S pool1 datas and?...
because I didn't notice the answer and I am stuck..
How to write failover command?
if I have fe: pool1 pool2 and pool3..
ethminer -G -S pool1 datas and?...
-S pool1 -FS pool2 -O credentials1 -FO credentials2.
You can omit -FO when it's identical to -O.
I have crash on win10 home x64, i use ethminer-0.9.41-genoil-1.0.8 with nvidia gtx 950 with driver 365.19 .
.bat is :
ethminer -U -S eth-eu.dwarfpool.com:8008 -O 98F1563fF4bCAA650e7b1155a9fdC393dfBcE995.stratum --cuda-grid-size 8192 --cuda-block-size 128
.
.bat is :
ethminer -U -S eth-eu.dwarfpool.com:8008 -O 98F1563fF4bCAA650e7b1155a9fdC393dfBcE995.stratum --cuda-grid-size 8192 --cuda-block-size 128
.If you want to use Nvidia cards on Win10, you need an old driver, max. 350.12. Or use Win8.1, 7 or Linux.
--edit--
Forget the old driver. It won't recognize your 950. It can be done but is even more painful to get working.
I have crash on win10 home x64, i use ethminer-0.9.41-genoil-1.0.8 with nvidia gtx 950 with driver 365.19 .
.bat is :
ethminer -U -S eth-eu.dwarfpool.com:8008 -O 98F1563fF4bCAA650e7b1155a9fdC393dfBcE995.stratum --cuda-grid-size 8192 --cuda-block-size 128
.
I thought genoil miner doesn't support dwarfpool? .bat is :
ethminer -U -S eth-eu.dwarfpool.com:8008 -O 98F1563fF4bCAA650e7b1155a9fdC393dfBcE995.stratum --cuda-grid-size 8192 --cuda-block-size 128
.
I have crash on win10 home x64, i use ethminer-0.9.41-genoil-1.0.8 with nvidia gtx 950 with driver 365.19 .
.bat is :
ethminer -U -S eth-eu.dwarfpool.com:8008 -O 98F1563fF4bCAA650e7b1155a9fdC393dfBcE995.stratum --cuda-grid-size 8192 --cuda-block-size 128
.
.bat is :
ethminer -U -S eth-eu.dwarfpool.com:8008 -O 98F1563fF4bCAA650e7b1155a9fdC393dfBcE995.stratum --cuda-grid-size 8192 --cuda-block-size 128
. 
Will their be any more updates to this miner? By this I mean for more management on how hard you can push your card to work. Like in Claymore's miner you can set how hard and by default cards are set to intensity of 9 and can do less to put less stress on card. Hoping you guys come up with something like this in the future.
play with these --cl-global-work 4096 --cl-local-work 64
Jump to: