ethminer-0.9.41-genoil-1.1

[sorry2xs]

can this version 1.1.0 be tested by the general public if were can it be downloaded from

[jwon]

can this version 1.1.0 be tested by the general public if were can it be downloaded from

https://github.com/Genoil/cpp-ethereum/tree/110/releases

[bensam1231]

Is 1.1 out of beta now?

[parmatiya]

Is it possible to send out the miner hashing rates to a pool? I use the ethpool.org. I want to monitor my miners.

I have the same question.

[Genoil]

Is 1.1 out of beta now?

no. have a few things i want to add to it:

- try and reduce CPU usage of stratum client on low-end CPUs
- serialize DAG generation option.

the current source release on the 110 branch has a bit of code in it to test the first point. If you have a low end CPU (such as G1840) and experience high CPU usage, build from source and add -SV 2 option. Only to test if it lowers CPU usage, code is far from ready...

[BitMinerN8]

Genoil, I tried the new release, checkout the 110 branch.
Now I get a new error: [ 61%] Building NVCC (Device) object libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o
nvcc fatal   : Unsupported gpu architecture 'compute_61'

I'm getting this error too when trying to make the 110 branch with -DBUNDLE=cudaminer ..
Running on Mint 17.3, all other versions worked prior.

This is because the default list of supported compute platforms now includes Compute 6.1 for the 10x0 series. It requires CUDA 8 RC to build. If you don't want to install CUDA 8, you can add -DCOMPUTE=52 to the cmake line to support only Compute 5.2 devices,  -DCOMPUTE=30 to support only Compute 3.0 devices, and so on.

Ahh, thanks, makes sense now. Is there a way to support 3.5 and 5.0 on the -DCOMPUTE? For example if I have:
Listing CUDA devices.
FORMAT: [deviceID] deviceName

• GeForce GTX 780 Ti

        Compute version: 3.5
        cudaDeviceProp::totalGlobalMem: 3220504576
[1] GeForce GTX 750 Ti
        Compute version: 5.0
        cudaDeviceProp::totalGlobalMem: 2147287040

(I would test, but I'm away from the rigs atm) Thanks.

[BitMinerN8]

Genoil, I tried the new release, checkout the 110 branch.
Now I get a new error: [ 61%] Building NVCC (Device) object libethash-cuda/CMakeFiles/ethash-cuda.dir/ethash-cuda_generated_ethash_cuda_miner_kernel.cu.o
nvcc fatal   : Unsupported gpu architecture 'compute_61'

I'm getting this error too when trying to make the 110 branch with -DBUNDLE=cudaminer ..
Running on Mint 17.3, all other versions worked prior.

This is because the default list of supported compute platforms now includes Compute 6.1 for the 10x0 series. It requires CUDA 8 RC to build. If you don't want to install CUDA 8, you can add -DCOMPUTE=52 to the cmake line to support only Compute 5.2 devices,  -DCOMPUTE=30 to support only Compute 3.0 devices, and so on.

Ahh, thanks, makes sense now. Is there a way to support 3.5 and 5.0 on the -DCOMPUTE? For example if I have:
Listing CUDA devices.
FORMAT: [deviceID] deviceName

• GeForce GTX 780 Ti

        Compute version: 3.5
        cudaDeviceProp::totalGlobalMem: 3220504576
[1] GeForce GTX 750 Ti
        Compute version: 5.0
        cudaDeviceProp::totalGlobalMem: 2147287040

(I would test, but I'm away from the rigs atm) Thanks.

Got in remote. -DCOMPUTE=52 seemed to work for both cards. (3.5 & 5.0)

[bensam1231]

Is 1.1 out of beta now?

no. have a few things i want to add to it:

- try and reduce CPU usage of stratum client on low-end CPUs
- serialize DAG generation option.

the current source release on the 110 branch has a bit of code in it to test the first point. If you have a low end CPU (such as G1840) and experience high CPU usage, build from source and add -SV 2 option. Only to test if it lowers CPU usage, code is far from ready...

Will Dual miner support be in this release? >>

[Genoil]

Is 1.1 out of beta now?

no. have a few things i want to add to it:

- try and reduce CPU usage of stratum client on low-end CPUs
- serialize DAG generation option.

the current source release on the 110 branch has a bit of code in it to test the first point. If you have a low end CPU (such as G1840) and experience high CPU usage, build from source and add -SV 2 option. Only to test if it lowers CPU usage, code is far from ready...

Will Dual miner support be in this release? >>

 

In other news, the GPU DAG generator just passed the DAG change in one piece. I was testing the simplified stratum client when I saw it reinitialize on-the-fly.

[malandante]

Is 1.1 out of beta now?

no. have a few things i want to add to it:

- try and reduce CPU usage of stratum client on low-end CPUs
- serialize DAG generation option.

the current source release on the 110 branch has a bit of code in it to test the first point. If you have a low end CPU (such as G1840) and experience high CPU usage, build from source and add -SV 2 option. Only to test if it lowers CPU usage, code is far from ready...

Will Dual miner support be in this release? >>

 

In other news, the GPU DAG generator just passed the DAG change in one piece. I was testing the simplified stratum client when I saw it reinitialize on-the-fly.

Good job! Is it stable for running it 24/7? How does it compare in terms of hashrate with claymore's?

Edit: phrasing

[Genoil]

I pushed a new 1.1.1 binary to the 110 branch. https://github.com/Genoil/cpp-ethereum/tree/110/releases

It has a simplified stratum client in an attempt to reduce CPU load on cheap CPUs. The work-timeout is disabled in this version as I've made it completely synchronous. Add -SV 2 to the command line to use it. The results aren't what I had hoped to achieve, but it does seem to use a bit less CPU. @Amph this latest build is even simpler than what I sent you but I don't think it'll make a big difference.

[bensam1231]

Is 1.1 out of beta now?

no. have a few things i want to add to it:

- try and reduce CPU usage of stratum client on low-end CPUs
- serialize DAG generation option.

the current source release on the 110 branch has a bit of code in it to test the first point. If you have a low end CPU (such as G1840) and experience high CPU usage, build from source and add -SV 2 option. Only to test if it lowers CPU usage, code is far from ready...

Will Dual miner support be in this release? >>

 

In other news, the GPU DAG generator just passed the DAG change in one piece. I was testing the simplified stratum client when I saw it reinitialize on-the-fly.

From what I hear with the 1080 in Ethereum, it performs about just as well as 970... So there is a lot more overhead available for new generation Pascal and a dual miner will be all the more desirable...

[barabeku]

I pushed a new 1.1.1 binary to the 110 branch. https://github.com/Genoil/cpp-ethereum/tree/110/releases

It has a simplified stratum client in an attempt to reduce CPU load on cheap CPUs. The work-timeout is disabled in this version as I've made it completely synchronous. Add -SV 2 to the command line to use it. The results aren't what I had hoped to achieve, but it does seem to use a bit less CPU. @Amph this latest build is even simpler than what I sent you but I don't think it'll make a big difference.

Can you help me to compile it latest version for k40 and m40 Teslas. im using CentOS.

[Keselencoey]

can i use my saphire R9 390 Nitro to mining etherum ?

[Genoil]

I pushed a new 1.1.2 binary to the 110 branch. https://github.com/Genoil/cpp-ethereum/tree/110/releases

Added mixed CL/CUDA mining, so you can mine both GPU types on a single ethminer instance. It's not possible to set different local/global work per GPU type yet. Will add that if there's any demand. I added this mostly to be able to build and test the DAG generation serialisation, because I have only 1 970 and 1 7950  .

To enable, replace -G or -U flag with -X.

[barabeku]

I pushed a new 1.1.2 binary to the 110 branch. https://github.com/Genoil/cpp-ethereum/tree/110/releases

Added mixed CL/CUDA mining, so you can mine both GPU types on a single ethminer instance. It's not possible to set different local/global work per GPU type yet. Will add that if there's any demand. I added this mostly to be able to build and test the DAG generation serialisation, because I have only 1 970 and 1 7950  .

To enable, replace -G or -U flag with -X.

can you please compile for cuda 6.5

[tolazy]

can i use my saphire R9 390 Nitro to mining etherum ?

yes you can. you will get about 28-29mhs

[induktor]

I pushed a new 1.1.1 binary to the 110 branch. https://github.com/Genoil/cpp-ethereum/tree/110/releases

It has a simplified stratum client in an attempt to reduce CPU load on cheap CPUs. The work-timeout is disabled in this version as I've made it completely synchronous. Add -SV 2 to the command line to use it. The results aren't what I had hoped to achieve, but it does seem to use a bit less CPU. @Amph this latest build is even simpler than what I sent you but I don't think it'll make a big difference.

Hi Genoil, thanks!!
Question what do you mean by work-timeout disabled?
it means that if the pool stops responding the miner will stop mining or not?

thanks
indkt

[BitMinerN8]

I pushed a new 1.1.2 binary to the 110 branch. https://github.com/Genoil/cpp-ethereum/tree/110/releases

Added mixed CL/CUDA mining, so you can mine both GPU types on a single ethminer instance. It's not possible to set different local/global work per GPU type yet. Will add that if there's any demand. I added this mostly to be able to build and test the DAG generation serialisation, because I have only 1 970 and 1 7950  .

To enable, replace -G or -U flag with -X.

Hi it seemed to compile ok, but I'm getting the following using -U

Code:

Using device: GeForce GTX 780 Ti (Compute 3.5)
Using device: GeForce GTX 750 Ti (Compute 5.0)
Cuda error in func 'set_constants' at line 143 : invalid device symbol.
Cuda error in func 'set_constants' at line 143 : invalid device symbol.
Segmentation fault

I compiled with:

Code:

git clone -b 110 https://github.com/Genoil/cpp-ethereum/ && cd cpp-ethereum && mkdir build && cd build && cmake -DCOMPUTE=52 -DBUNDLE=cudaminer .. && make -j8

That was working on 1.1.1 yesterday. Thanks for looking into it.

[Genoil]

I pushed a new 1.1.1 binary to the 110 branch. https://github.com/Genoil/cpp-ethereum/tree/110/releases

It has a simplified stratum client in an attempt to reduce CPU load on cheap CPUs. The work-timeout is disabled in this version as I've made it completely synchronous. Add -SV 2 to the command line to use it. The results aren't what I had hoped to achieve, but it does seem to use a bit less CPU. @Amph this latest build is even simpler than what I sent you but I don't think it'll make a big difference.

Hi Genoil, thanks!!
Question what do you mean by work-timeout disabled?
it means that if the pool stops responding the miner will stop mining or not?

thanks
indkt

The async stratum client has a feature where the miner reconnects or fails over when it has been mining on the same job for over x seconds. I didn't implement it in the new client.

I pushed a new 1.1.2 binary to the 110 branch. https://github.com/Genoil/cpp-ethereum/tree/110/releases

Added mixed CL/CUDA mining, so you can mine both GPU types on a single ethminer instance. It's not possible to set different local/global work per GPU type yet. Will add that if there's any demand. I added this mostly to be able to build and test the DAG generation serialisation, because I have only 1 970 and 1 7950  .

To enable, replace -G or -U flag with -X.

Hi it seemed to compile ok, but I'm getting the following using -U

Code:

Using device: GeForce GTX 780 Ti (Compute 3.5)
Using device: GeForce GTX 750 Ti (Compute 5.0)
Cuda error in func 'set_constants' at line 143 : invalid device symbol.
Cuda error in func 'set_constants' at line 143 : invalid device symbol.
Segmentation fault

I compiled with:

Code:

git clone -b 110 https://github.com/Genoil/cpp-ethereum/ && cd cpp-ethereum && mkdir build && cd build && cmake -DCOMPUTE=52 -DBUNDLE=cudaminer .. && make -j8

That was working on 1.1.1 yesterday. Thanks for looking into it.

It's kind of weird that that worked. Better for you to -DCOMPUTE=0 and remove Compute 6.1 from Cmakelists.txt in libethash-cuda folder.