|
Genoil (OP)
|
 |
May 22, 2016, 06:22:41 PM |
|
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. |
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
BTC: 1Nu2fMCEBjmnLzqb8qUJpKgq5RoEWFhNcW
|
|
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
hawkfish007
|
|
May 22, 2016, 09:30:34 PM |
|
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?
|
|
|
|
|
adamvp
|
|
May 23, 2016, 12:35:34 AM |
|
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?...
-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  |
I am looking for signature campaign pm me |
|
|
bensam1231
Legendary
 Offline
Activity: 1750
Merit: 1024
|
|
May 23, 2016, 11:21:16 AM |
|
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?...
-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. |
I buy private Nvidia miners. Send information and/or inquiries to my PM box.
|
|
|
ShodanPT
Newbie
Offline
Activity: 4
Merit: 0
|
|
May 23, 2016, 04:17:34 PM |
|
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.
|
|
|
|
|
|
Genoil (OP)
|
|
May 24, 2016, 12:55:47 PM |
|
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  |
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
BTC: 1Nu2fMCEBjmnLzqb8qUJpKgq5RoEWFhNcW
|
|
|
adaseb
Legendary
Offline
Activity: 3738
Merit: 1708
|
|
May 24, 2016, 12:57:13 PM |
|
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 So during DAG change it shouldn't crash? |
|
|
|
|
Genoil (OP)
|
|
May 24, 2016, 01:10:06 PM |
|
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 So during DAG change it shouldn't crash? haven't tested that yet. |
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
BTC: 1Nu2fMCEBjmnLzqb8qUJpKgq5RoEWFhNcW
|
|
|
|
maxvall
|
|
May 24, 2016, 03:15:48 PM |
|
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!  Thanks! I'll test it ASAP. |
|
|
|
|
scryptr
Legendary
Offline
Activity: 1793
Merit: 1028
|
|
May 24, 2016, 03:35:10 PM |
|
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 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 |
|
|
|
|
Genoil (OP)
|
|
May 24, 2016, 03:55:32 PM |
|
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 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 |
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
BTC: 1Nu2fMCEBjmnLzqb8qUJpKgq5RoEWFhNcW
|
|
|
restless
Legendary
Offline
Activity: 1151
Merit: 1001
|
|
May 24, 2016, 04:18:31 PM |
|
Is there Windows build?
|
|
|
|
|
|
Genoil (OP)
|
|
May 24, 2016, 04:20:40 PM |
|
Is there Windows build?
Yes in the releases folder of 110 branch (CUDA compute 5.2 only, OpenCL AMD+ NVidia) |
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
BTC: 1Nu2fMCEBjmnLzqb8qUJpKgq5RoEWFhNcW
|
|
|
restless
Legendary
Offline
Activity: 1151
Merit: 1001
|
|
May 24, 2016, 04:36:26 PM |
|
|
|
|
|
|
scryptr
Legendary
Offline
Activity: 1793
Merit: 1028
|
|
May 24, 2016, 04:40:41 PM |
|
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
|
|
|
|
|
Genoil (OP)
|
|
May 24, 2016, 04:47:18 PM |
|
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
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. |
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
BTC: 1Nu2fMCEBjmnLzqb8qUJpKgq5RoEWFhNcW
|
|
|
jstefanop
Legendary
Offline
Activity: 2090
Merit: 1396
|
|
May 24, 2016, 06:50:22 PM |
|
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 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! ℹ 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] |
|
|
|
|
Genoil (OP)
|
|
May 24, 2016, 07:01:47 PM |
|
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.
|
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
BTC: 1Nu2fMCEBjmnLzqb8qUJpKgq5RoEWFhNcW
|
|
|
jstefanop
Legendary
Offline
Activity: 2090
Merit: 1396
|
|
May 24, 2016, 07:13:45 PM |
|
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 |
|
|
|
|
Genoil (OP)
|
|
May 24, 2016, 07:27:20 PM |
|
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. |
ETH: 0xeb9310b185455f863f526dab3d245809f6854b4d
BTC: 1Nu2fMCEBjmnLzqb8qUJpKgq5RoEWFhNcW
|
|
|
|
