 Show Posts
|
|
Pages: [1]
|
This version is not so easy to use because you have to adjust "-h" and "-dmem" values often, I will try to improve it soon.
1. "-dmem 1" requires twice more memory, make sure you have enough virtual memory. For example, if you have 6 GPUs 8GB, set virtual memory to 6*8=48GB.
2. Check how much memory miner allocates, it shows something like "(Memory used: 5128MB)", make sure you have this memory on your GPU.
3. You can see low hashrate if you use almost all memory on GPU, try to reduce "-h" value a bit.
Guys if you are getting the "GpuMiner dk2an0 failed" error, be sure to note Claymore's comments above. I was initially getting the same error with my RX480 8GB rig. Lowering to -h 1024 will solve the issue but make the program only see 4GB on my cards. After changing page file to 48GB, the miner runs beautifully with default -h and -dmem settings. Ellesmere RX480 8GB, same modded BIOS, default miner settings: CryptoNote Miner 9.7 - 850 H/s CryptoNote Miner 10 - 987 H/s Thanks Claymore! |
|
|
|
Error 43 is answered 176 times on just this subforum...there is a search field on forums
top right corner
If you're referring to later drivers blocking modified BIOS, I've run latest ati patcher with all attributes "found" and successfully patched, restarted and the error is still present. I do think the memory labels in BIOS editor showing up scrambled is a sign that this could be a new revision that the usual tools don't 100% work with. I've also tried the old Catalyst 16 driver with the Safe Mode - F7 then patcher trick without success. |
|
|
|
I have a rig of 6 Dell RX480 reference cards, and when I flash the BIOS in the OP I get the Code 43. I've tried old Catalyst 16 drivers as well as 17.7.1, both with BIOS signature patched by atikmdag-patcher, but the card I flash refuses to work (detected in device manager but Code 43) until I flash back to stock. Another potentially related issue - when I tried using PolarisBiosEditor 1.4 to create a modded BIOS myself, the memory speed labels seem like random numbers and not normal speed numbers that I see in tutorials. Any help would be greatly appreciated and ETH donations considered. Screenshot of PolarisBiosEditor: https://www.dropbox.com/s/ein29jlupex4hk3/BIOS%20Editor%20SS.png?dl=0Stock BIOS: https://www.dropbox.com/s/6qnkb6dwzufv7gd/stock0.rom?dl=0 |
|
|
|
|
I currently have a rig with Asrock BTC Pro 2.0 and 6x Dell RX 480 (reference?) cards. Do I only need one dummy HDMI plug for the card that's plugged (via riser) into the x16 slot, or need to buy six dummy plugs?
|
|
|
|
Finally I can test and confirm that AMD has fixed the issue with slowdown at high DAG epochs for Vega/Polaris/Fiji cards. They are going to release new drivers in a few days.
Have you heard any new updates from AMD since? Wondering if they're having last minute issues with the release. I'd like to avoid using an unofficial user-modded driver. Separately, I just assembled an AMD rig with 6x RX480, and I'm new to AMD, would folks mind educating me as to the following: 1) Is BIOS modding still the way to go for under-volting and optimizing memory timings? Or can a lot of that be achieved with the latest Wattman? 2a) If BIOS mods are still the way to go, I read that as of a certain Catalyst version it won't work with modified BIOS, so does that mean when the new Catalyst with DAG fix releases, it won't work with the BIOS mods? How will we be able to use the new driver with DAG fix AND run with modded BIOS? 2b) If Wattman can largely achieve power reduction and improved Apologies in advance if this issue has been widely discussed, I didn't see directly relevant results with the preliminary Google searches I've done thus far. 1) Yes, BIOS modding is the way to go! But make sure you know what you are doing, ok? 2) With recent drivers, you'll need to patch to them otherwise they won't work with the modded BIOS. Check it out: https://www.monitortests.com/forum/Thread-AMD-ATI-Pixel-Clock-Patcher3) With current drivers, WattTool is the best choice to undervolt/underclock your rigs. Get it here: http://www.overclock.net/t/1609782/watttool-a-simple-tool-that-combines-overclocking-with-vrm-monitoring-tweaking-for-rx-400-series4) WattMan sucks...  Thank you guys so much! |
|
|
|
Finally I can test and confirm that AMD has fixed the issue with slowdown at high DAG epochs for Vega/Polaris/Fiji cards. They are going to release new drivers in a few days.
Have you heard any new updates from AMD since? Wondering if they're having last minute issues with the release. I'd like to avoid using an unofficial user-modded driver. Separately, I just assembled an AMD rig with 6x RX480, and I'm new to AMD, would folks mind educating me as to the following: 1) Is BIOS modding still the way to go for under-volting and optimizing memory timings? Or can a lot of that be achieved with the latest Wattman? 2a) If BIOS mods are still the way to go, I read that as of a certain Catalyst version it won't work with modified BIOS, so does that mean when the new Catalyst with DAG fix releases, it won't work with the BIOS mods? How will we be able to use the new driver with DAG fix AND run with modded BIOS? 2b) If Wattman can largely achieve power reduction and improved Apologies in advance if this issue has been widely discussed, I didn't see directly relevant results with the preliminary Google searches I've done thus far. |
|
|
|
How's v9.8 on gtx1070? Better?
I had a near 0.7mh/s jump on GTX1070 going from 9.6 to 9.7, but 9.8 is simply to fix the interface with latest 17.7.2 Catalyst, not supposed to have improved performance. |
|
|
|
Finally I can test and confirm that AMD has fixed the issue with slowdown at high DAG epochs for Vega/Polaris/Fiji cards. They are going to release new drivers in a few days.
When new drivers come out, will it work if i just copy OpenCL DLLs into miner folder? I don't think so, the changes at the driver level. Did AMD provide you with both Windows/Linux fixed drivers or just windows? I test everything in Windows 7/10 currently, I don't have any info about new Linux drivers. Within 24 hours I will release new version with Vega support and fan/overclock management for 17.7.2 drivers, for Windows. I will release Linux version a bit later. Amazing news, thanks! Quick question - am I understanding correctly that 17.7.2 does not yet contain the hashrate drop fix, which is coming in the next driver release in a few days. And that is a separate matter than the next release of Claymore Miner that you're working on, which will add Vega support and fix management for driver versions 17.7.2 going forward. Thus, to mine with Polaris without hashrate drop and full management ability, you need both the next AMD driver release and next Claymore miner? |
|
|
|
|
