can i use my saphire R9 390 Nitro to mining etherum ?
yes you can. you will get about 28-29mhs
Topic: ethminer-0.9.41-genoil-1.1 - page 53. (Read 397360 times)
yes you can. you will get about 28-29mhs
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.
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
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.
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 i use my saphire R9 390 Nitro to mining etherum ?
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.
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.
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...
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.
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.
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
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.
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, 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 ..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'
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
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.
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 ..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'
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
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.
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...
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.
Is 1.1 out of beta now?
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
can this version 1.1.0 be tested by the general public if were can it be downloaded from
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 ..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'
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.
Are you kidding me?, it took only 2 seconds to generate a 1.5GB DAG?? holy FUCK!, that awesome Genoil, genius!.
previous version generating it on the flash drive took me 23 minutes
awesome!
previous version generating it on the flash drive took me 23 minutes
awesome!
Two is pretty good. I do it in... I think like four-ish seconds, but I have 4 GPUs in it.
3 x GTX 970 Gigabyte, impressive perfomance, and it is not the CPU (a tiny low power AM1 2Ghz quadcore APU), man i gotta learn to code cuda/ocl ... i never got past C
but i will start dedicate more time on this.Actually, this kernel is a MASSIVE pain in the ass to make faster. It doesn't react to most of what you do, and the AMD OCL compiler is having none of this shit - hates the algo so much that it tends to erroneously compile your shit FAR more than usual. So, small tweaks aren't gonna fly with this one.
To get my speed increases, I first had to rewrite Ethash entirely in a different way - which got me the very first substantial increase. After that, I just said fuck it - the compiler is too much of a pain in my ass, so I modified Genoil's Ethminer implementation to load binaries. After that, I dropped to GCN assembly to continue working, where I can control things a little better.
One of my tricks will work on CUDA, and I don't think it's been done yet - but another, the shuffle, has been done on it.
Are you kidding me?, it took only 2 seconds to generate a 1.5GB DAG?? holy FUCK!, that awesome Genoil, genius!.
previous version generating it on the flash drive took me 23 minutes
awesome!
previous version generating it on the flash drive took me 23 minutes
awesome!
Two is pretty good. I do it in... I think like four-ish seconds, but I have 4 GPUs in it.
3 x GTX 970 Gigabyte, impressive perfomance, and it is not the CPU (a tiny low power AM1 2Ghz quadcore APU), man i gotta learn to code cuda/ocl ... i never got past C
but i will start dedicate more time on this.Actually, this kernel is a MASSIVE pain in the ass to make faster. It doesn't react to most of what you do, and the AMD OCL compiler is having none of this shit - hates the algo so much that it tends to erroneously compile your shit FAR more than usual. So, small tweaks aren't gonna fly with this one.
To get my speed increases, I first had to rewrite Ethash entirely in a different way - which got me the very first substantial increase. After that, I just said fuck it - the compiler is too much of a pain in my ass, so I modified Genoil's Ethminer implementation to load binaries. After that, I dropped to GCN assembly to continue working, where I can control things a little better.
Part of what he has done has already been in the CUDA kernel for about a year (because in CUDA this is much much easier). It gave a 3% performance increase.
Indeed. I'm patching out the offending marker instructions by paw now - but it's tedious as HELL. I can't quite regex it, but since there's a lot of loop unrolling in this portion, there's a LOT to patch.
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 ..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'
Running on Mint 17.3, all other versions worked prior.
Jump to: