Topic: ethminer-0.9.41-genoil-1.1 - page 59. (Read 397360 times)
^ No
No more DAG? Does this mean I can throw the old 5850 back in there?
for some reason i only get 25mhs with 1.1
i'm getting 29mhs with 1.08
and with claymore i get 31mhs
i'm getting 29mhs with 1.08
and with claymore i get 31mhs
support stratum from dwarf?
nope.
RE: CPU usage: I'm considering rewriting the stratum client to be single threaded. I think that will reduce CPU load on simple CPUs.
RE: 1.0.9. I figured getting rid of the DAG would be a nice milestone to push the minor version number a notch
. 1.0.8 already runs on Pascal by the way. Just cmake with -DCOMPUTE=61 (CUDA 8 required) or use OpenCL. And use Linux for now to get a bit of hashrate.RE: deadlock: have pushed new src/binary that may resolve the deadlock. Still running a test.
support stratum from dwarf?
Hello Genoil,
Thank you for your great work!
I'm using version 1.10 x 6 AMD GPU setup on ubuntu 14.04.
Should I rollback my version of ethminer?
Thank you for your great work!
I'm using version 1.10 x 6 AMD GPU setup on ubuntu 14.04.
Should I rollback my version of ethminer?
It has a chance of deadlock in stratum mode. If it loads the GPUs and you use getwork, it should be fine
Hello Genoil,
Thank you for your great work!
I'm using version 1.10 x 6 AMD GPU setup on ubuntu 14.04.
Should I rollback my version of ethminer?
Thank you for your great work!
I'm using version 1.10 x 6 AMD GPU setup on ubuntu 14.04.
Should I rollback my version of ethminer?
found a bug in 1.1 cauisng it to hang after a random amount of blocks.. it's not production ready yet, stay tuned 
@jstefanop: during DAG generation ok. serialisation seems the bvest way forward then.
@jstefanop: during DAG generation ok. serialisation seems the bvest way forward then.
I just ran a little test on both Nvidia (CUDA) and AMD (OpenCL) where I switched between current and next DAG every 5 blocks. No problems whatsoever. I don't have a multi-card rig, but I don't see how that should be any different, other than maybe a bit of clutter in the log output while changing DAGs.
Unfortunately DAGs are created so fast that the custom pcie bus we are running all these GPUs on is getting overloaded and the OpenCL calls hang. I guess I got lucky and it started the first time but quickly crashed.
The only way to solve this issue is to implement the same serialization fix claymour did on his miner (i.e. generate DAGs one by one serially, and any OpenCL calls have to have a delay in them (especially when new work is pushed to all the GPUs). Unfortunately I don't think thats an easy fix with ethminer and how threaded it is.
FYI this wont effect most users running less than 6 GPUs
This on 1.1 i assume. There's not so much going over the bus, just about 50-100MB of DAG cache. When did it actually crash? During DAG generation or during mining? Because when mining, it;s not really that much different from 1.0.8, other than some code commented out. It must be something else then this, perhaps removing all this DAG crap opened up another weird ethminer bug.
no i have debugged the issues extensively and confirmed its a bug with how fglrx makes openCL calls with multiple GPUs (and its made worse with bridges we use). Here is an example of where it usually crashes
Code:
[OPENCL]:Printing program log
[OPENCL]:
[OPENCL]:Creating cache buffer
[OPENCL]:Creating DAG buffer
[OPENCL]:Loading kernels
[OPENCL]:Writing cache buffer
0%
67%
[OPENCL]:Creating buffer for header.
[OPENCL]:Creating mining buffer 0
[OPENCL]:Creating mining buffer 1
[OPENCL]:Generating DAG data
8%
42%
25%
50%
33%
67%
8%
75%
17%
0%
50%
33%
58%
42%
75%
17%
83%
25%
8%
92%
58%
42%
50%
67%
83%
25%
92%
33%
17%
67%
50%
58%
75%
33%
42%
25%
75%
58%
67%
83%
92%
42%
50%
33%
83%
ℹ 15:06:03|gpuminer0 set work to: #6a82dd23, target #0000000112e0be82
67%
92%
75%
50%
58%
ℹ 15:06:03|gpuminer1 set work to: #6a82dd23, target #0000000112e0be82
42%
75%
83%
92%
58%
67%
50%
ℹ 15:06:03|gpuminer2 set work to: #6a82dd23, target #0000000112e0be82
83%
ℹ 15:06:04|gpuminer3 set work to: #6a82dd23, target #0000000112e0be82
92%
67%
75%
58%
75%
83%
67%
92%
83%
75%
92%
83%
92%
[OPENCL]:
[OPENCL]:Creating cache buffer
[OPENCL]:Creating DAG buffer
[OPENCL]:Loading kernels
[OPENCL]:Writing cache buffer
0%
67%
[OPENCL]:Creating buffer for header.
[OPENCL]:Creating mining buffer 0
[OPENCL]:Creating mining buffer 1
[OPENCL]:Generating DAG data
8%
42%
25%
50%
33%
67%
8%
75%
17%
0%
50%
33%
58%
42%
75%
17%
83%
25%
8%
92%
58%
42%
50%
67%
83%
25%
92%
33%
17%
67%
50%
58%
75%
33%
42%
25%
75%
58%
67%
83%
92%
42%
50%
33%
83%
ℹ 15:06:03|gpuminer0 set work to: #6a82dd23, target #0000000112e0be82
67%
92%
75%
50%
58%
ℹ 15:06:03|gpuminer1 set work to: #6a82dd23, target #0000000112e0be82
42%
75%
83%
92%
58%
67%
50%
ℹ 15:06:03|gpuminer2 set work to: #6a82dd23, target #0000000112e0be82
83%
ℹ 15:06:04|gpuminer3 set work to: #6a82dd23, target #0000000112e0be82
92%
67%
75%
58%
75%
83%
67%
92%
83%
75%
92%
83%
92%
As you can see there is way to much I/O going on between 9 GPUs in short amount of time, which causes the openCL call hangs. The only fix until AMD decides to revamp the AMDGPU drivers is to serialize the OpenCL calls and make sure they don't overlap between GPUs.
btw i still have that heavy cpu utilization, but only when mining in stratum mode on some pool like cointron
same problem
I just want to say thank you so much Genoil for the continued support and the great update 
Nice work on the DAG creation!
Nice work on the DAG creation!
HOW DO I CLONE VERSION 110? --
I must have cloned the current version 1.0.8 from GIT. How do I clone the v110? I have researched, but am not familiar with "checkout" commands. Working in Linux, here. --scryptr
I must have cloned the current version 1.0.8 from GIT. How do I clone the v110? I have researched, but am not familiar with "checkout" commands. Working in Linux, here. --scryptr
cd cpp-ethereum
git checkout 110
I think, I tend to forget these things. If it doesn't work because you cloned the repo earlier, git pull first.
GIT CHECKOUT 110 WORKED--
And, I was able to correctly build pre-release v1.1. The generation of the DAG file directly on the GPUs took about 5 seconds, rather than minutes for on-disk generation. No more DAG directory to clean up! The version label was correct, and in place at program launch.
I did notice that the percentage completion display during DAG file generation scrolled down the screen instead of remaining in one spot. It went by with speed, however. Great job! Thank you... --scryptr
so i guess there will be no more 1.0.9 and pascal support will be added in the 1.2+ version
btw i still have that heavy cpu utilization, but only when mining in stratum mode on some pool like cointron
btw i still have that heavy cpu utilization, but only when mining in stratum mode on some pool like cointron
I just ran a little test on both Nvidia (CUDA) and AMD (OpenCL) where I switched between current and next DAG every 5 blocks. No problems whatsoever. I don't have a multi-card rig, but I don't see how that should be any different, other than maybe a bit of clutter in the log output while changing DAGs.
Unfortunately DAGs are created so fast that the custom pcie bus we are running all these GPUs on is getting overloaded and the OpenCL calls hang. I guess I got lucky and it started the first time but quickly crashed.
The only way to solve this issue is to implement the same serialization fix claymour did on his miner (i.e. generate DAGs one by one serially, and any OpenCL calls have to have a delay in them (especially when new work is pushed to all the GPUs). Unfortunately I don't think thats an easy fix with ethminer and how threaded it is.
FYI this wont effect most users running less than 6 GPUs
This on 1.1 i assume. There's not so much going over the bus, just about 50-100MB of DAG cache. When did it actually crash? During DAG generation or during mining? Because when mining, it;s not really that much different from 1.0.8, other than some code commented out. It must be something else then this, perhaps removing all this DAG crap opened up another weird ethminer bug.
I just ran a little test on both Nvidia (CUDA) and AMD (OpenCL) where I switched between current and next DAG every 5 blocks. No problems whatsoever. I don't have a multi-card rig, but I don't see how that should be any different, other than maybe a bit of clutter in the log output while changing DAGs.
Unfortunately DAGs are created so fast that the custom pcie bus we are running all these GPUs on is getting overloaded and the OpenCL calls hang. I guess I got lucky and it started the first time but quickly crashed.
The only way to solve this issue is to implement the same serialization fix claymour did on his miner (i.e. generate DAGs one by one serially, and any OpenCL calls have to have a delay in them (especially when new work is pushed to all the GPUs). Unfortunately I don't think thats an easy fix with ethminer and how threaded it is.
FYI this wont effect most users running less than 6 GPUs
I just ran a little test on both Nvidia (CUDA) and AMD (OpenCL) where I switched between current and next DAG every 5 blocks. No problems whatsoever. I don't have a multi-card rig, but I don't see how that should be any different, other than maybe a bit of clutter in the log output while changing DAGs.
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
awesome job! If this proves to be stable wont need claymour's miner to run my 9-10 GPU rigs
will definitely send some eth your way!Code:
ℹ 14:46:38|stratum Received new job #f89025a1
ℹ 14:46:38|gpuminer0 set work to: #f89025a1, target #0000000112e0be82
ℹ 14:46:38|gpuminer1 set work to: #f89025a1, target #0000000112e0be82
ℹ 14:46:38|gpuminer2 set work to: #f89025a1, target #0000000112e0be82
ℹ 14:46:38|gpuminer3 set work to: #f89025a1, target #0000000112e0be82
ℹ 14:46:38|gpuminer4 set work to: #f89025a1, target #0000000112e0be82
ℹ 14:46:38|gpuminer5 set work to: #f89025a1, target #0000000112e0be82
ℹ 14:46:38|gpuminer6 set work to: #f89025a1, target #0000000112e0be82
ℹ 14:46:38|gpuminer7 set work to: #f89025a1, target #0000000112e0be82
ℹ 14:46:38|gpuminer8 set work to: #f89025a1, target #0000000112e0be82
m 14:46:39|ethminer Mining on PoWhash #f89025a1 : 221.06MH/s [A25+0:R0+0:F0]
m 14:46:41|ethminer Mining on PoWhash #f89025a1 : 189.79MH/s [A25+0:R0+0:F0]
m 14:46:43|ethminer Mining on PoWhash #f89025a1 : 189.79MH/s [A25+0:R0+0:F0]
m 14:46:45|ethminer Mining on PoWhash #f89025a1 : 189.79MH/s [A25+0:R0+0:F0]
HOW DO I CLONE VERSION 110? --
I must have cloned the current version 1.0.8 from GIT. How do I clone the v110? I have researched, but am not familiar with "checkout" commands. Working in Linux, here. --scryptr
I must have cloned the current version 1.0.8 from GIT. How do I clone the v110? I have researched, but am not familiar with "checkout" commands. Working in Linux, here. --scryptr
cd cpp-ethereum
git checkout 110
I think, I tend to forget these things. If it doesn't work because you cloned the repo earlier, git pull first.
HOW DO I CLONE VERSION 110? --
I must have cloned the current version 1.0.8 from GIT. How do I clone the v110? I have researched, but am not familiar with "checkout" commands. Working in Linux, here. --scryptr
I must have cloned the current version 1.0.8 from GIT. How do I clone the v110? I have researched, but am not familiar with "checkout" commands. Working in Linux, here. --scryptr
damn it.
I stayed like 15min on https://github.com/Genoil/cpp-ethereum/tree/110 trying all possible links
Then just wrote /releases and voila :/ https://github.com/Genoil/cpp-ethereum/blob/110/releases/ethminer-0.9.41-genoil-1.1.zip
I stayed like 15min on https://github.com/Genoil/cpp-ethereum/tree/110 trying all possible links
Then just wrote /releases and voila :/ https://github.com/Genoil/cpp-ethereum/blob/110/releases/ethminer-0.9.41-genoil-1.1.zip
Jump to: