Is this card only suitable for ethash?
Ethash right now most profitable, but 5700/5700XT capable to mine mtp on pair with 2060/2070 How's the hashrate for MTP? currently 2.9MH/s per 5700XT and 2.5MH/s per 5700 using wildrig multi. I'll have to give it a try. I only have the XT versions. Do you use F2Pool? What are optimal OC settings? I just entered 2.9 in whattomine and I'm not impressed at all with the results. |
|
|
|
Is this card only suitable for ethash?
Ethash right now most profitable, but 5700/5700XT capable to mine mtp on pair with 2060/2070 How's the hashrate for MTP? |
|
|
|
today I have bought nvidia GTX 1650 4GB ram
I have installed windows 10 and latest nvidia driver.
But when I run miner I get this, any idea how to solve this?
ETH: Authorized
Setting DAG epoch #291(3.27GB)...
Setting DAG epoch #291 for GPU0
Create GPU buffer for GPU0
CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
ETH: GPU0 0.000 Mh/s
ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
ETH: GPU0 0.000 Mh/s
GPU 0 failed
Setting DAG epoch #291 for GPU0
GPU 0, CUDA error 11 - cannot write buffer for DAG
GPU 0 failed
What version of claymore are you using? It sounds like 4GB isn't enough for the DAG since the current DAG is 3.27GB for ETH or 3.34GB for ETC. RedPandaMining recently posted a video on his Youtube Channel. https://www.youtube.com/watch?v=xRIX5mpVntk. |
|
|
|
I've installed 19.9.3 drivers and switched back to PM 4.7b from claymore's miner, now mixed rig is working flawlessly, thank you @PhoenixMiner. BTW claymore's miner consumed 10 watts less and hashrate was just 0.8 MH/s lower for RX 5700.
Any significant improvements? For me PM always was better, but previous version was unstable with 19.9.1 drivers and with 19.9.2 didn't work at all. Now it looks like stability problem solved, however i see one reboot during last night. Also i've noticed that 5700 card after some time begins to give +2 Mh/s, but after dag switching this speedup is gone and again after some time miner shows +2Mh/s until dag switch. I updated everything shortly after posting to see for myself. I figured that I could always revert back. I can say that it seems less stable in my experience. I didn't have any reboots (maybe one every three days or so) but since the updates my miner crashed slightly more than usual. Crashes (not reboots) at 11:53pm, 1:57am, 6:26am and at 9:10am. No reboots yet. I can't explain the crashes, I didn't do anything but install the updates. I'm considering on rolling back the drivers. |
|
|
|
I've installed 19.9.3 drivers and switched back to PM 4.7b from claymore's miner, now mixed rig is working flawlessly, thank you @PhoenixMiner. BTW claymore's miner consumed 10 watts less and hashrate was just 0.8 MH/s lower for RX 5700.
Any significant improvements? |
|
|
|
PhoenixMiner 4.7b (release candidate) is available https://bitcointalk.org/index.php?topic=2647654.msg52667354#msg52667354The release candidate of 4.7 is ready for download. You can download PhoenixMiner 4.7b from here: https://mega.nz/#F!jJkjyCbb!W6fA-w3XCpwvdC-uwPxSCg (MEGA) If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows): File: PhoenixMiner_4.7b_Windows.zip
===================================
SHA-1: 6168de64ca680b824fb3f63d2cebd30ee22dc0f2
SHA-256: c7aeb33c3d7a2354da0bb006c6280083239aa79e002185a5e3947811abbe6858
SHA-512: e00f6061cdcf2b20fe15937b9a146bc90bd8c8e653432271e9ada49b3c43970ae8ca0b0fbf275707f01fb13f4b0786bb7bfcaadbcf7d864d733745d2ae82cc19
File: PhoenixMiner_4.7b_Linux.tar.gz
====================================
SHA-1: 0f9e127ba6fab8d62049f45a8799d9b8b9e1da2e
SHA-256: 7e8359ce6322d6001b4f45be4959692d6e83a69b45882e6938f91cd782bf08ed
SHA-512: bc8a47249afa4220e19059c0e3319a268b521fdbfe5b67d4f80a7c64843b1174a0aa13a4cc1a275246e7dec2daed10d236ef7f13d4e9d0cbe9b4aad4be59142c
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
Here are the new features for this release: - New kernels for Navi (RX5700) with better stability. Should solve the freezing and restarts that some miners are experiencing with Navi cards
- Reduced VRAM usage for both AMD and Nvidia cards on Windows and Linux
- Added command-line option -config to load a config.txt file. This allows combining command-line options and config.txt file.
- Added support for mining QuarkChain (QKC) without DAG switching on devfee (use -coin qkc)
- Added support for the latest AMD Windows drivers 19.9.3
- Other small improvements and fixes.
When using the new -config option, please note the following: - The order of the options is important. For example, if we have a config.txt file that contains -cclock 1000 and we specify command line -cclock 1100 -config config.txt, the option from the config.txt file will take precedence and the resulting -cclock will be 1000. If the order is reversed (-config config.txt -cclock 1100) then the second option takes precedence and the resulting -cclock will be 1100.
- Only one -config option is allowed
- If you reload the config file with 'c' key or with the remote interface, its options will take precedence over whatever you have specified in the command-line.
|
|
|
|
So, my miner's motherboard died and SSD crashed. Got new motherboard and SSD today.
I had no backup of my previous system, so I reinstalled everything from scratch using latest versions.
Gigabyte GA-H110-D3A, 6x RX580 4GB
Before:
Win 10, I think build 1703 of 1709 (not sure)
AMD beta blockchain drivers
Claymore 11.9
Now:
Win 10 build 1903 (latest)
Latest AMD drivers
Claymore 15
Before I got +- 182MH/s ETH only (as expected for this rig), but now something like 72 (+-12 per card). Something's obviously off.
Quick suggestions on what I did wrong? Which OS version and driver version should I use? Thanks!
Sounds like compute mode is on. I think that you mean it sounds like it's on Graphics and not Compute. I'd also recommend trying the beta blockchain drivers again and see what the difference is. |
|
|
|
So basically we RX 5700XT users are stuck with ETHASH by Claymore now.
Using PhoenixMiner, somehow one of my two RX 5700 will crap out after sometimes and the one that is still mining will still be showing fully loaded after mining is stopped.
I have three XFX 5700XT cards and mining with PhoenixMiner 4.6c No problems here. Hashing at ~52 MH/s each. -tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -clKernel 1 -clNew 1 good for you. Maybe because I force copy PhoenixMiner 4.6c latest exe into nicehash miner plugin folder, it's not stable. Did you try running it without Nicehash? Personally, I don't use Nicehash, I might might on their pool if it's more profitable but I don't use their program. For profit switching I use Awesome Miner. |
|
|
|
So basically we RX 5700XT users are stuck with ETHASH by Claymore now.
Using PhoenixMiner, somehow one of my two RX 5700 will crap out after sometimes and the one that is still mining will still be showing fully loaded after mining is stopped.
I have three XFX 5700XT cards and mining with PhoenixMiner 4.6c No problems here. Hashing at ~52 MH/s each. -tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -clKernel 1 -clNew 1 |
|
|
|
So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go.
You mean a 10% gain? 50MH/s increased to 55MH/s is 10%. But I get your point. Yeah, sure. I tried all the settings you just did, and every time, the % gain was almost exactly offset by % invalid shares. However, I did not run very long tests, so it could be possible that pool-side effective hashrate might go up even with the incorrect shares, but I doubt it. All of my incorrect shares were from the same GPU (I have three) so it's possible that it's just my XFX GPU since it's also the GPU that won't let me clock past 900Mhz without the watchdog error. Thinking of returning it. But from 49.5 to 57 seems like an improvement to me. Once Claymore releases some Navi kernels for his software then we'll be in business for sure. Claymore has already released his version with Navi support. Quoting Claymore: ----------------------------------------------------- v15.0: - now miner supports up to #384 epoch (4GB DAG size). Note that previous versions support up to #299 epoch, you will not be able to use old versions after #299 epoch. - added support for Navi cards (ETH-only mode). - now miner sets environment variables automatically (required for 4GB AMD cards). - a few minor bug fixes and improvements. PS. AMD still has no public Navi drivers with DAG-fix, so currently 5700XT shows a very bad hashrate. But AMD already solved this issue and they promise to release public drivers soon... ----------------------------------------------------- What else do you expect from him, to start walking on water like Jesus did? I've removed the "-openclLocalWork 64" completely and I'm averaging 52 instead of 49.5 with ZERO errors or incorrect shares. PhoenixMiner says that the new kernel is included in the latest version. IF the developers coordinate and assist each other instead of competing against each other more can be accomplished. Granted I don't know if they do share tips with each other. Anyway, I still prefer Claymore... but so far Phoenix yields better results after this update. Not sure how he did it but it is an improvement nonetheless. I hope he can figure something out (and I'm sure he will) because I prefer Claymore. Why do you prefer Claymore? It is slower than PM on any GPU. It takes twice more devfee. Consumes less or equal power. What is more important than these three facts? Your emotional affection? Are you a female? WHAT THE HELL DOES IT MATTER AND WHAT IS IT TO YOU??? Mind your own business. If I like Coke over Pepsi, I'll drink Coke. If I like mustard on my hot dog, I'll take mustard on it. Last I knew I needn't explain my preferences or loyalty. I don't give a shit who or what you like, do I? What does my GENDER have to do with anything? Are you wanting to fucking ask me out? Will you try to date rape me or some shit? Fuck off! This loss of control obviously shows what your gender is. Don't worry! I date only normal female. You don't know shit. Mind your own business and stay on topic. But he right about PM. And here is only positives - less fee, faster speed, equal or less power with him... Regardless of the opinion, THIS thread is about Claymore and HIS development. Not PM. If you were to open a thread sharing work that you've dedicated several hours to (and profiting from for those hours) just for someone to post reason(s) not to support him and to support someone else's work, would that be appropriate? On top of that express an inappropriate, rude and sexist attitude toward another member? Sure, I posted the original statement about PM software being updated. Obviously, that wasn't the best idea since now it put this douchwad on my ignore list (because he is clearly out of line) but I shared that information to spur development on Claymore and to INFORM other members of the advancement. At no point was my intention to ever persuade or coerce anyone to switch to PhoenixMiner. He on the other hand appears to be doing exactly that... in Claymore's thread. Which is definitely inappropriate. If he is such a PM supporter then what the hell is he doing posting in this thread? The sexist comments that he was posting was not only off topic but also libel. He doesn't know shit about me or anyone else on here, no less to even assume what a "normal female" is. His comments were definitely inappropriate, sexist, libel, rude, inappropriate and definitely off topic. Such are nothing but counterproductive. |
|
|
|
So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go.
You mean a 10% gain? 50MH/s increased to 55MH/s is 10%. But I get your point. Yeah, sure. I tried all the settings you just did, and every time, the % gain was almost exactly offset by % invalid shares. However, I did not run very long tests, so it could be possible that pool-side effective hashrate might go up even with the incorrect shares, but I doubt it. All of my incorrect shares were from the same GPU (I have three) so it's possible that it's just my XFX GPU since it's also the GPU that won't let me clock past 900Mhz without the watchdog error. Thinking of returning it. But from 49.5 to 57 seems like an improvement to me. Once Claymore releases some Navi kernels for his software then we'll be in business for sure. Claymore has already released his version with Navi support. Quoting Claymore: ----------------------------------------------------- v15.0: - now miner supports up to #384 epoch (4GB DAG size). Note that previous versions support up to #299 epoch, you will not be able to use old versions after #299 epoch. - added support for Navi cards (ETH-only mode). - now miner sets environment variables automatically (required for 4GB AMD cards). - a few minor bug fixes and improvements. PS. AMD still has no public Navi drivers with DAG-fix, so currently 5700XT shows a very bad hashrate. But AMD already solved this issue and they promise to release public drivers soon... ----------------------------------------------------- What else do you expect from him, to start walking on water like Jesus did? I've removed the "-openclLocalWork 64" completely and I'm averaging 52 instead of 49.5 with ZERO errors or incorrect shares. PhoenixMiner says that the new kernel is included in the latest version. IF the developers coordinate and assist each other instead of competing against each other more can be accomplished. Granted I don't know if they do share tips with each other. Anyway, I still prefer Claymore... but so far Phoenix yields better results after this update. Not sure how he did it but it is an improvement nonetheless. I hope he can figure something out (and I'm sure he will) because I prefer Claymore. Why do you prefer Claymore? It is slower than PM on any GPU. It takes twice more devfee. Consumes less or equal power. What is more important than these three facts? Your emotional affection? Are you a female? WHAT THE HELL DOES IT MATTER AND WHAT IS IT TO YOU??? Mind your own business. If I like Coke over Pepsi, I'll drink Coke. If I like mustard on my hot dog, I'll take mustard on it. Last I knew I needn't explain my preferences or loyalty. I don't give a shit who or what you like, do I? What does my GENDER have to do with anything? Are you wanting to fucking ask me out? Will you try to date rape me or some shit? Fuck off! This loss of control obviously shows what your gender is. Don't worry! I date only normal female. You don't know shit. Mind your own business and stay on topic. |
|
|
|
So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go.
You mean a 10% gain? 50MH/s increased to 55MH/s is 10%. But I get your point. Yeah, sure. I tried all the settings you just did, and every time, the % gain was almost exactly offset by % invalid shares. However, I did not run very long tests, so it could be possible that pool-side effective hashrate might go up even with the incorrect shares, but I doubt it. All of my incorrect shares were from the same GPU (I have three) so it's possible that it's just my XFX GPU since it's also the GPU that won't let me clock past 900Mhz without the watchdog error. Thinking of returning it. But from 49.5 to 57 seems like an improvement to me. Once Claymore releases some Navi kernels for his software then we'll be in business for sure. Claymore has already released his version with Navi support. Quoting Claymore: ----------------------------------------------------- v15.0: - now miner supports up to #384 epoch (4GB DAG size). Note that previous versions support up to #299 epoch, you will not be able to use old versions after #299 epoch. - added support for Navi cards (ETH-only mode). - now miner sets environment variables automatically (required for 4GB AMD cards). - a few minor bug fixes and improvements. PS. AMD still has no public Navi drivers with DAG-fix, so currently 5700XT shows a very bad hashrate. But AMD already solved this issue and they promise to release public drivers soon... ----------------------------------------------------- What else do you expect from him, to start walking on water like Jesus did? I've removed the "-openclLocalWork 64" completely and I'm averaging 52 instead of 49.5 with ZERO errors or incorrect shares. PhoenixMiner says that the new kernel is included in the latest version. IF the developers coordinate and assist each other instead of competing against each other more can be accomplished. Granted I don't know if they do share tips with each other. Anyway, I still prefer Claymore... but so far Phoenix yields better results after this update. Not sure how he did it but it is an improvement nonetheless. I hope he can figure something out (and I'm sure he will) because I prefer Claymore. Why do you prefer Claymore? It is slower than PM on any GPU. It takes twice more devfee. Consumes less or equal power. What is more important than these three facts? Your emotional affection? Are you a female? WHAT THE HELL DOES IT MATTER AND WHAT IS IT TO YOU??? Mind your own business. If I like Coke over Pepsi, I'll drink Coke. If I like mustard on my hot dog, I'll take mustard on it. Last I knew I needn't explain my preferences or loyalty. I don't give a shit who or what you like, do I? What does my GENDER have to do with anything? Are you wanting to fucking ask me out? Will you try to date rape me or some shit? Fuck off! |
|
|
|
|
I have been playing around with these for most part of the day and started off by trying:
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -mode 1 -clKernel 3 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096
But I was getting between 30% to 50% incorrect shares.
I've tried slightly adjusting the -gt between 15 to 150 (even 0 or leaving it out completely) and it seemed to help slightly at ~115 but I was still experiencing a lot of incorrect shares.
Now... I've tried experimenting with -clKernel 3 but it always said that it was ignored.
I've tried:
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -clKernel 3 -clNew 1 -openclLocalWork 64
Which seemed a little better but I was still getting between 5% incorrect shares (about 1 out of every 15-20) but I was only yielding ~56MH/s. Not too bad...
So then I remove the -openclLocalWork...
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -clKernel 1 -clNew 1
I let this run for exactly 5 hours and 19 minutes.
Three XFX 5700 XT cards.
Accepted 318, Rejected 0, HW Errors 0
Averaging 52 MH/s for 156 MH/s combined and 277w combined (92w - 94w each)
You have to admit that these are very solid, stable and promising. Results of 52MH/s for 92w is 0.56MH/s per watt seems pretty efficient. Ideally I'd love to have a 500+MH/s Ethereum mining rig on a 1,000w PSU and I believe that it's achievable with these cards.
|
|
|
|
What else do you expect from him, to start walking on water like Jesus did?
I've removed the "-openclLocalWork 64" completely and I'm averaging 52 instead of 49.5 with ZERO errors or incorrect shares. PhoenixMiner says that the new kernel is included in the latest version. IF the developers coordinate and assist each other instead of competing against each other more can be accomplished. Granted I don't know if they do share tips with each other. Anyway, I still prefer Claymore... but so far Phoenix yields better results after this update. Not sure how he did it but it is an improvement nonetheless. I hope he can figure something out (and I'm sure he will) because I prefer Claymore. Well, the faster he can make his miner, the more dev fee he will collect. So yeah, I think optimizing the kernel would be worth it to him. I hope so. So... I let this run for exactly 5 hours and 19 minutes. Three XFX 5700 XT cards. Accepted 318, Rejected 0, HW Errors 0 Averaging 52 MH/s for 156 MH/s combined and 277w combined (92w - 94w each) This is my setting for PhoenixMiner: -tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -clKernel 1 -clNew 1 You have to admit that these are very solid, stable and promising. Results of 52MH/s for 92w is 0.56MH/s per watt seems pretty efficient. Ideally I'd love to have a 500+MH/s Ethereum mining rig on a 1,000w PSU and I believe that it's achievable with these cards. |
|
|
|
So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go.
You mean a 10% gain? 50MH/s increased to 55MH/s is 10%. But I get your point. Yeah, sure. I tried all the settings you just did, and every time, the % gain was almost exactly offset by % invalid shares. However, I did not run very long tests, so it could be possible that pool-side effective hashrate might go up even with the incorrect shares, but I doubt it. All of my incorrect shares were from the same GPU (I have three) so it's possible that it's just my XFX GPU since it's also the GPU that won't let me clock past 900Mhz without the watchdog error. Thinking of returning it. But from 49.5 to 57 seems like an improvement to me. Once Claymore releases some Navi kernels for his software then we'll be in business for sure. Claymore has already released his version with Navi support. Quoting Claymore: ----------------------------------------------------- v15.0: - now miner supports up to #384 epoch (4GB DAG size). Note that previous versions support up to #299 epoch, you will not be able to use old versions after #299 epoch. - added support for Navi cards (ETH-only mode). - now miner sets environment variables automatically (required for 4GB AMD cards). - a few minor bug fixes and improvements. PS. AMD still has no public Navi drivers with DAG-fix, so currently 5700XT shows a very bad hashrate. But AMD already solved this issue and they promise to release public drivers soon... ----------------------------------------------------- What else do you expect from him, to start walking on water like Jesus did? I've removed the "-openclLocalWork 64" completely and I'm averaging 52 instead of 49.5 with ZERO errors or incorrect shares. PhoenixMiner says that the new kernel is included in the latest version. IF the developers coordinate and assist each other instead of competing against each other more can be accomplished. Granted I don't know if they do share tips with each other. Anyway, I still prefer Claymore... but so far Phoenix yields better results after this update. Not sure how he did it but it is an improvement nonetheless. I hope he can figure something out (and I'm sure he will) because I prefer Claymore. |
|
|
|
So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go.
You mean a 10% gain? 50MH/s increased to 55MH/s is 10%. But I get your point. Yeah, sure. I tried all the settings you just did, and every time, the % gain was almost exactly offset by % invalid shares. However, I did not run very long tests, so it could be possible that pool-side effective hashrate might go up even with the incorrect shares, but I doubt it. All of my incorrect shares were from the same GPU (I have three) so it's possible that it's just my XFX GPU since it's also the GPU that won't let me clock past 900Mhz without the watchdog error. Thinking of returning it. But from 49.5 to 57 seems like an improvement to me. Once Claymore releases some Navi kernels for his software then we'll be in business for sure. |
|
|
|
Well... I hate to say this... but I'm getting 60MH/s using PhoenixMiner 4.6c now.
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096
~95 watts per card and 59C.
I like it a lot!
It seems to me that PM is optimized especially for 32 threads per work group and doesn't work correctly for more. So I think that this 60 MH/s is fake and that your -openclLocalWork 128 causes incorrect shares. I'm trying this: -tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -gt 100 -clKernel 3 -clNew 1 -openclLocalWork 64 And it's pretty solid. I'm only getting 56.6 though. No incorrect shares. ..for now. You are a great optimist. As stated, it still needs some tweaking but it's progress! I'm keeping it with these settings for now. Only 1 incorrect share out of 22 so far. So you have a 5% speed gain, but losing 5% to incorrect shares.... seems like a wash to me. Until the kernels are written for that worksize (if it's even possible), seems like using the default settings is the best way to go. You mean a 10% gain? 50MH/s increased to 55MH/s is 10%. But I get your point. |
|
|
|
Well... I hate to say this... but I'm getting 60MH/s using PhoenixMiner 4.6c now.
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096
~95 watts per card and 59C.
I like it a lot!
It seems to me that PM is optimized especially for 32 threads per work group and doesn't work correctly for more. So I think that this 60 MH/s is fake and that your -openclLocalWork 128 causes incorrect shares. I'm trying this: -tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -gt 100 -clKernel 3 -clNew 1 -openclLocalWork 64 And it's pretty solid. I'm only getting 56.6 though. No incorrect shares. ..for now. You are a great optimist. As stated, it still needs some tweaking but it's progress! I'm keeping it with these settings for now. Only 1 incorrect share out of 22 so far. |
|
|
|
Well... I hate to say this... but I'm getting 60MH/s using PhoenixMiner 4.6c now.
-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -acm -mi 12 -gt 126 -mode 1 -clKernel 1 -clNew 1 -clf 0 -lidag 1 -openclLocalWork 128 -openclGlobalMultiplier 4096
~95 watts per card and 59C.
I like it a lot!
It seems to me that PM is optimized especially for 32 threads per work group and doesn't work correctly for more. So I think that this 60 MH/s is fake and that your -openclLocalWork 128 causes incorrect shares. I'm trying this: -tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -gt 100 -clKernel 3 -clNew 1 -openclLocalWork 64 And it's pretty solid. I'm only getting 56.6 though. No incorrect shares. |
|
|
|
With -clKernel 3 and new founded -gt parameter (it differs from -clKernel 1) you can gain about 0,7-1MH/s additional speed...
And I recommend to find -gt parameter for each card individually, not using the same for all cards. Best of it can be differ even on two equal cards. Each changing of cclock or mclock leads to new best -gt parameter, just check it...
Yeah that didn't help at all with my incorrect shares. I removed the -gt parameter so it does it automatically. I'm going back to -clKernel 1 for the moment. Perhaps that will help. And it looks like I can remove the -acm since Compute Mode isn't needed for these cards. -tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 900 -amd -mode 1 -clKernel 1 -clNew 1 -openclLocalWork 64 Reduces my hashrate slightly and I'm 3 for 3 so far. It's been running for a couple of minutes and no incorrect shares. |
|
|
|
|
Show Posts
