CMMChris Posted October 18, 2018 Share Posted October 18, 2018 No need to. Everything you need is on the picture. Link to comment Share on other sites More sharing options...
Max.1974 Posted October 18, 2018 Share Posted October 18, 2018 (edited) @Yangbe look in the past pages, because all you need to know was in there...including videos... If you wanted, post your config plist and I add for you... see: Edited October 18, 2018 by max.1974 Link to comment Share on other sites More sharing options...
CMMChris Posted October 20, 2018 Share Posted October 20, 2018 Another great Vega 64 PowerPlay Table for anyone to try out. Should be stable on most cards. Really low temperatures, no coil whine, great performance. Noticeably smoother UI performance due to higher base clocks. Voltage has been lowered significantly. Temps under load should not exceed 70°C and card stays silent. Fans will keep off during normal use. If they turn on they don't get very loud and turn off again after the card cooled down. PowerPlay Settings GPU Clocks: 1150 / 1200 / 1250 / 1300 / 1350 / 1400 / 1450 / 1500 GPU Voltage: 950 / 975 / 1000 / 1025 / 1050 / 1075 / 1100 / 1125 HBM2 Clock: 1045 HBM2 Voltage / Voltage Floor: 950 Min. Fan Speed: 100 (= Stop) Idle Fan Speed: 100 (= Stop) Target Fan Speed: 2600 Max. Fan Speed: 3000 Temperature Target: 55°C Power Target: 100% Use with Kext Injector See file attached. Use with own Kext Injector USE STOCK DRIVER SETTINGS + POWERPLAY TABLE! Don't use own settings like "PP_DisablePowerContaintment" and stuff like that. Refer to the original AMD10000Controller to check stock settings. tgIIAQBcAOEGAADuKwAAGwBIAAAAgKkDAPBJAgBkAAgA AAAAAAAAAAAAAAAAAAIBXABPAkYClACeAb4AKAF6AIwA vAEAAAAAcgIAAJAAqAJtAUMBlwHwSQIAcQICAgAAAAAA AAgAAAAAAAAABQAHAAMABQAAAAAAAAABCLYDzwPoAwEE GgQzBEwEZQQBAbYDAQGEAwAIYOoAAABAGQEAAYA4AQAC 3EoBAAOQXwEABAB3AQAFkJEBAAZssAEABwEIOMEBAAAA gAAAAAAAAMDUAQABAAAAAAAAAABI6AEAAgAAAAAAAAAA 0PsBAAMAAAAAAAAAAFgPAgAEAAAAAAAAAADgIgIABQAA AAABAAAAaDYCAAYAAAAAAQAAAPBJAgAHAAAAAAEAAAAA BWDqAAAAQBkBAACAOAEAANxKAQAAkF8BAAAACChuAAAA LMkAAAH4CwEAAoA4AQADkF8BAAT0kQEABdCwAQAGwNQB AAcACGw5AAAAJF4AAAH8hQAAAqy8AAADNNAAAARobgEA BQiXAQAG7KMBAAcAAWg8AQAAAQQ8QQAAAAAAUMMAAAAA AIA4AQACAAA0mAEABAAAAQgAmIUAAEC1AABg6gAAUMMA AAGAuwAAYOoAAJQLAQBQwwAAAgDhAACUCwEAQBkBAFDD AAADeP8AAEAZAQCIJgEAUMMAAARAGQEAgDgBAIA4AQBQ wwAABYA4AQDcSgEA3EoBAFDDAAAGAHcBAAB3AQCQXwEA UMMAAAeQkQEAkJEBAAB3AQBQwwAAARgAAAAAAAAAC+QS ZAAoCjcACgBUA5ABkAGQAZABkAGQAZABAAAAAAACAR4H 3ADcANwALAEAAFkAaQBKAEoAXwBzAHMAZABAAJCSl2CW AJBVAAAAAAAAAAAAAAAAAAAAAAACAtQwAAACEGDqAAAC EA== Use with Clover Device Properties B6020801 005C00E1 060000EE 2B00001B 00480000 0080A903 00F04902 00640008 00000000 00000000 00000000 00000201 5C004F02 46029400 9E01BE00 28017A00 8C00BC01 00000000 72020000 9000A802 6D014301 9701F049 02007102 02020000 00000000 08000000 00000000 05000700 03000500 00000000 00000108 B603CF03 E8030104 1A043304 4C046504 0101B603 01018403 000860EA 00000040 19010001 80380100 02DC4A01 0003905F 01000400 77010005 90910100 066CB001 00070108 38C10100 00008000 00000000 00C0D401 00010000 00000000 000048E8 01000200 00000000 000000D0 FB010003 00000000 00000000 580F0200 04000000 00000000 00E02202 00050000 00000100 00006836 02000600 00000001 000000F0 49020007 00000000 01000000 000560EA 00000040 19010000 80380100 00DC4A01 0000905F 01000000 08286E00 00002CC9 000001F8 0B010002 80380100 03905F01 0004F491 010005D0 B0010006 C0D40100 0700086C 39000000 245E0000 01FC8500 0002ACBC 00000334 D0000004 686E0100 05089701 0006ECA3 01000700 01683C01 00000104 3C410000 00000050 C3000000 00008038 01000200 00349801 00040000 01080098 85000040 B5000060 EA000050 C3000001 80BB0000 60EA0000 940B0100 50C30000 0200E100 00940B01 00401901 0050C300 000378FF 00004019 01008826 010050C3 00000440 19010080 38010080 38010050 C3000005 80380100 DC4A0100 DC4A0100 50C30000 06007701 00007701 00905F01 0050C300 00079091 01009091 01000077 010050C3 00000118 00000000 0000000B E4126400 280A3700 0A005403 90019001 90019001 90019001 90010000 00000002 011E07DC 00DC00DC 002C0100 00590069 004A004A 005F0073 00730064 00400090 92976096 00905500 00000000 00000000 00000000 00000000 0202D430 00000210 60EA0000 0210 My benchmark results: Geekbench OpenCL: 192,000 Points (average) Luxmark: 29,500 (average) Valley benchmark ran stable for 60 minutes with average GPU temperature being 69°C, fan speed was a low 1,800. Enjoy and let me know how this works for you guys! VegaTab_64.kext.zip 1 Link to comment Share on other sites More sharing options...
PPC Posted October 21, 2018 Share Posted October 21, 2018 What an adventure it is digesting all the different approaches and settings. I have used the config.plist method and it seems to work. My question is do the Property Values change based on the card you have? So far I don't recall anyone mentioning the: Asus Strix Vega 64 OC. Base clock: 1590 Memory clock: 945 Do I need different Property Values? BTW, I have no idea how to generate them. Thanks. Link to comment Share on other sites More sharing options...
douirc Posted October 21, 2018 Share Posted October 21, 2018 (edited) 17 hours ago, CMMChris said: Another great Vega 64 PowerPlay Table for anyone to try out. Should be stable on most cards. Really low temperatures, no coil whine, great performance. Noticeably smoother UI performance due to higher base clocks. Voltage has been lowered significantly. Temps under load should not exceed 70°C and card stays silent. Fans will keep off during normal use. If they turn on they don't get very loud and turn off again after the card cooled down. PowerPlay Settings GPU Clocks: 1150 / 1200 / 1250 / 1300 / 1350 / 1400 / 1450 / 1500 GPU Voltage: 950 / 975 / 1000 / 1025 / 1050 / 1075 / 1100 / 1125 HBM2 Clock: 1045 HBM2 Voltage / Voltage Floor: 950 Min. Fan Speed: 100 (= Stop) Idle Fan Speed: 100 (= Stop) Target Fan Speed: 2600 Max. Fan Speed: 3000 Temperature Target: 55°C Power Target: 100% Use with Kext Injector See file attached. Use with own Kext Injector USE STOCK DRIVER SETTINGS + POWERPLAY TABLE! Don't use own settings like "PP_DisablePowerContaintment" and stuff like that. Refer to the original AMD10000Controller to check stock settings. tgIIAQBcAOEGAADuKwAAGwBIAAAAgKkDAPBJAgBkAAgA AAAAAAAAAAAAAAAAAAIBXABPAkYClACeAb4AKAF6AIwA vAEAAAAAcgIAAJAAqAJtAUMBlwHwSQIAcQICAgAAAAAA AAgAAAAAAAAABQAHAAMABQAAAAAAAAABCLYDzwPoAwEE GgQzBEwEZQQBAbYDAQGEAwAIYOoAAABAGQEAAYA4AQAC 3EoBAAOQXwEABAB3AQAFkJEBAAZssAEABwEIOMEBAAAA gAAAAAAAAMDUAQABAAAAAAAAAABI6AEAAgAAAAAAAAAA 0PsBAAMAAAAAAAAAAFgPAgAEAAAAAAAAAADgIgIABQAA AAABAAAAaDYCAAYAAAAAAQAAAPBJAgAHAAAAAAEAAAAA BWDqAAAAQBkBAACAOAEAANxKAQAAkF8BAAAACChuAAAA LMkAAAH4CwEAAoA4AQADkF8BAAT0kQEABdCwAQAGwNQB AAcACGw5AAAAJF4AAAH8hQAAAqy8AAADNNAAAARobgEA BQiXAQAG7KMBAAcAAWg8AQAAAQQ8QQAAAAAAUMMAAAAA AIA4AQACAAA0mAEABAAAAQgAmIUAAEC1AABg6gAAUMMA AAGAuwAAYOoAAJQLAQBQwwAAAgDhAACUCwEAQBkBAFDD AAADeP8AAEAZAQCIJgEAUMMAAARAGQEAgDgBAIA4AQBQ wwAABYA4AQDcSgEA3EoBAFDDAAAGAHcBAAB3AQCQXwEA UMMAAAeQkQEAkJEBAAB3AQBQwwAAARgAAAAAAAAAC+QS ZAAoCjcACgBUA5ABkAGQAZABkAGQAZABAAAAAAACAR4H 3ADcANwALAEAAFkAaQBKAEoAXwBzAHMAZABAAJCSl2CW AJBVAAAAAAAAAAAAAAAAAAAAAAACAtQwAAACEGDqAAAC EA== Use with Clover Device Properties B6020801 005C00E1 060000EE 2B00001B 00480000 0080A903 00F04902 00640008 00000000 00000000 00000000 00000201 5C004F02 46029400 9E01BE00 28017A00 8C00BC01 00000000 72020000 9000A802 6D014301 9701F049 02007102 02020000 00000000 08000000 00000000 05000700 03000500 00000000 00000108 B603CF03 E8030104 1A043304 4C046504 0101B603 01018403 000860EA 00000040 19010001 80380100 02DC4A01 0003905F 01000400 77010005 90910100 066CB001 00070108 38C10100 00008000 00000000 00C0D401 00010000 00000000 000048E8 01000200 00000000 000000D0 FB010003 00000000 00000000 580F0200 04000000 00000000 00E02202 00050000 00000100 00006836 02000600 00000001 000000F0 49020007 00000000 01000000 000560EA 00000040 19010000 80380100 00DC4A01 0000905F 01000000 08286E00 00002CC9 000001F8 0B010002 80380100 03905F01 0004F491 010005D0 B0010006 C0D40100 0700086C 39000000 245E0000 01FC8500 0002ACBC 00000334 D0000004 686E0100 05089701 0006ECA3 01000700 01683C01 00000104 3C410000 00000050 C3000000 00008038 01000200 00349801 00040000 01080098 85000040 B5000060 EA000050 C3000001 80BB0000 60EA0000 940B0100 50C30000 0200E100 00940B01 00401901 0050C300 000378FF 00004019 01008826 010050C3 00000440 19010080 38010080 38010050 C3000005 80380100 DC4A0100 DC4A0100 50C30000 06007701 00007701 00905F01 0050C300 00079091 01009091 01000077 010050C3 00000118 00000000 0000000B E4126400 280A3700 0A005403 90019001 90019001 90019001 90010000 00000002 011E07DC 00DC00DC 002C0100 00590069 004A004A 005F0073 00730064 00400090 92976096 00905500 00000000 00000000 00000000 00000000 0202D430 00000210 60EA0000 0210 My benchmark results: Geekbench OpenCL: 192,000 Points (average) Luxmark: 29,500 (average) Valley benchmark ran stable for 60 minutes with average GPU temperature being 69°C, fan speed was a low 1,800. Enjoy and let me know how this works for you guys! VegaTab_64.kext.zip I'd like to give this a shot but am a complete N00b. Any instructions? Thanks! I'm running Mojave with ASRock Vega 64. Can I just copy/paste VegTab_64.kext to my EFI/CLOVER/kexts/Other folder? So I went ahead and put the kext in my efi/clover/kexts/other folder and the fan runs great on boot. I then tried running Cinebench to do a little stress testing. The temp goes up but the fan doesn't change speed. I read elsewhere there's a way to take the table from my Windows installation and insert into macOS. Is that correct? Would that give me a perfectly running card? Edited October 21, 2018 by douirc Link to comment Share on other sites More sharing options...
CMMChris Posted October 21, 2018 Share Posted October 21, 2018 (edited) My fan also doesn't spin up on Cinebench. Run Valley Benchmark for a while and it will start spinning. Mine turns on once the card reaches 72°C. Edited October 21, 2018 by CMMChris Link to comment Share on other sites More sharing options...
douirc Posted October 21, 2018 Share Posted October 21, 2018 7 hours ago, CMMChris said: My fan also doesn't spin up on Cinebench. Run Valley Benchmark for a while and it will start spinning. Mine turns on once the card reaches 72°C. Thanks for the info! Ran Valley in windowed while monitoring temp/RPM: 36/687 (idle) 40/700 50/700 62/800 65/900 70/1400 72/1500 73/1600 74/1700 (max) back to idle after GPU cools down. Slight coil whine while doing stuff but overall pretty darn good! Thank you @CMMChris Link to comment Share on other sites More sharing options...
douirc Posted October 21, 2018 Share Posted October 21, 2018 (edited) Here are my results on Win10. I guess the goal with VegaTab_64.kext is keep it cool and safe, not shoot for the limits. I'm ok with that anyway since I dual boot Win10 for gaming. Edited October 21, 2018 by douirc Link to comment Share on other sites More sharing options...
italeffect2 Posted October 22, 2018 Share Posted October 22, 2018 On 10/20/2018 at 3:33 AM, CMMChris said: Another great Vega 64 PowerPlay Table for anyone to try out. Should be stable on most cards. Really low temperatures, no coil whine, great performance. Noticeably smoother UI performance due to higher base clocks. Voltage has been lowered significantly. Temps under load should not exceed 70°C and card stays silent. Fans will keep off during normal use. If they turn on they don't get very loud and turn off again after the card cooled down. PowerPlay Settings GPU Clocks: 1150 / 1200 / 1250 / 1300 / 1350 / 1400 / 1450 / 1500 GPU Voltage: 950 / 975 / 1000 / 1025 / 1050 / 1075 / 1100 / 1125 Thanks for sharing this. I gave this a try and it was working great until my monitor went to sleep and the machine froze. Tested it for a few more hours today and had the exact same thing happen again. I had a similar result when I used VegaTab to create my own kext previously. Freezes with black or grey screen after a few hours. Not related to workload. Maybe once a day, totally random. No idea why. But monitor sleep worked fine. I went back to the original kext I was using, which is the RadeonVegaLowFansSpeed.kext originally from this thread. No freezes with that. OS 10.14 Gigabyte Radeon RX Vega 64 Gaming OC 8 GB Gigabyte Z270X-Gaming 5 i7 -7700k Link to comment Share on other sites More sharing options...
CMMChris Posted October 23, 2018 Share Posted October 23, 2018 If the card freezes you might need to increase voltages a bit or change the memory clock. Try lowering the memory clock to 1000MHz first and then check if freezes disappear. Link to comment Share on other sites More sharing options...
CMMChris Posted October 23, 2018 Share Posted October 23, 2018 (edited) Just figured out that the Vega driver provides much more data through terminal than just fan speed and temps. Here is a neat little command that displays fan speed in RPM and %, temperature, memory clock and GPU clock and refreshes the output every second: while sleep 1; do clear;ioreg -l |grep \"PerformanceStatistics\" | cut -d '{' -f 2 | tr '|' ',' | tr -d '}' | tr ',' '\n'|grep 'Temp\|Fan\|Clock'; done You can save this in a plain text file and make it executable. Then you just have to double click on it and terminal will open running the command. Enjoy! Edited October 23, 2018 by CMMChris 1 Link to comment Share on other sites More sharing options...
hugeschnauzer Posted October 25, 2018 Share Posted October 25, 2018 (edited) hi Guys. I've changed my RX580 to Vega64 and im still getting crashes on FCPX and Adobe Premiere on things like Scrubbing the timeline or tweaking color adjustments. The machine got black screen (no restart) and system freezes. I've done all kinds of changes in Clover, Igpu on off, ID change, etc When i run tests like unigine i see my fan speed doesnt change (50%max) but temps gets higher please help 8700k / Asus prime A z370 / 10.3.5 Edited October 25, 2018 by hugeschnauzer Link to comment Share on other sites More sharing options...
jpdut Posted October 25, 2018 Share Posted October 25, 2018 On 10/20/2018 at 3:33 AM, CMMChris said: Another great Vega 64 PowerPlay Table for anyone to try out. Should be stable on most cards. Really low temperatures, no coil whine, great performance. Noticeably smoother UI performance due to higher base clocks. Voltage has been lowered significantly. Temps under load should not exceed 70°C and card stays silent. Fans will keep off during normal use. If they turn on they don't get very loud and turn off again after the card cooled down. PowerPlay Settings GPU Clocks: 1150 / 1200 / 1250 / 1300 / 1350 / 1400 / 1450 / 1500 GPU Voltage: 950 / 975 / 1000 / 1025 / 1050 / 1075 / 1100 / 1125 HBM2 Clock: 1045 HBM2 Voltage / Voltage Floor: 950 Min. Fan Speed: 100 (= Stop) Idle Fan Speed: 100 (= Stop) Target Fan Speed: 2600 Max. Fan Speed: 3000 Temperature Target: 55°C Power Target: 100% Use with Kext Injector See file attached. Use with own Kext Injector USE STOCK DRIVER SETTINGS + POWERPLAY TABLE! Don't use own settings like "PP_DisablePowerContaintment" and stuff like that. Refer to the original AMD10000Controller to check stock settings. tgIIAQBcAOEGAADuKwAAGwBIAAAAgKkDAPBJAgBkAAgA AAAAAAAAAAAAAAAAAAIBXABPAkYClACeAb4AKAF6AIwA vAEAAAAAcgIAAJAAqAJtAUMBlwHwSQIAcQICAgAAAAAA AAgAAAAAAAAABQAHAAMABQAAAAAAAAABCLYDzwPoAwEE GgQzBEwEZQQBAbYDAQGEAwAIYOoAAABAGQEAAYA4AQAC 3EoBAAOQXwEABAB3AQAFkJEBAAZssAEABwEIOMEBAAAA gAAAAAAAAMDUAQABAAAAAAAAAABI6AEAAgAAAAAAAAAA 0PsBAAMAAAAAAAAAAFgPAgAEAAAAAAAAAADgIgIABQAA AAABAAAAaDYCAAYAAAAAAQAAAPBJAgAHAAAAAAEAAAAA BWDqAAAAQBkBAACAOAEAANxKAQAAkF8BAAAACChuAAAA LMkAAAH4CwEAAoA4AQADkF8BAAT0kQEABdCwAQAGwNQB AAcACGw5AAAAJF4AAAH8hQAAAqy8AAADNNAAAARobgEA BQiXAQAG7KMBAAcAAWg8AQAAAQQ8QQAAAAAAUMMAAAAA AIA4AQACAAA0mAEABAAAAQgAmIUAAEC1AABg6gAAUMMA AAGAuwAAYOoAAJQLAQBQwwAAAgDhAACUCwEAQBkBAFDD AAADeP8AAEAZAQCIJgEAUMMAAARAGQEAgDgBAIA4AQBQ wwAABYA4AQDcSgEA3EoBAFDDAAAGAHcBAAB3AQCQXwEA UMMAAAeQkQEAkJEBAAB3AQBQwwAAARgAAAAAAAAAC+QS ZAAoCjcACgBUA5ABkAGQAZABkAGQAZABAAAAAAACAR4H 3ADcANwALAEAAFkAaQBKAEoAXwBzAHMAZABAAJCSl2CW AJBVAAAAAAAAAAAAAAAAAAAAAAACAtQwAAACEGDqAAAC EA== Use with Clover Device Properties B6020801 005C00E1 060000EE 2B00001B 00480000 0080A903 00F04902 00640008 00000000 00000000 00000000 00000201 5C004F02 46029400 9E01BE00 28017A00 8C00BC01 00000000 72020000 9000A802 6D014301 9701F049 02007102 02020000 00000000 08000000 00000000 05000700 03000500 00000000 00000108 B603CF03 E8030104 1A043304 4C046504 0101B603 01018403 000860EA 00000040 19010001 80380100 02DC4A01 0003905F 01000400 77010005 90910100 066CB001 00070108 38C10100 00008000 00000000 00C0D401 00010000 00000000 000048E8 01000200 00000000 000000D0 FB010003 00000000 00000000 580F0200 04000000 00000000 00E02202 00050000 00000100 00006836 02000600 00000001 000000F0 49020007 00000000 01000000 000560EA 00000040 19010000 80380100 00DC4A01 0000905F 01000000 08286E00 00002CC9 000001F8 0B010002 80380100 03905F01 0004F491 010005D0 B0010006 C0D40100 0700086C 39000000 245E0000 01FC8500 0002ACBC 00000334 D0000004 686E0100 05089701 0006ECA3 01000700 01683C01 00000104 3C410000 00000050 C3000000 00008038 01000200 00349801 00040000 01080098 85000040 B5000060 EA000050 C3000001 80BB0000 60EA0000 940B0100 50C30000 0200E100 00940B01 00401901 0050C300 000378FF 00004019 01008826 010050C3 00000440 19010080 38010080 38010050 C3000005 80380100 DC4A0100 DC4A0100 50C30000 06007701 00007701 00905F01 0050C300 00079091 01009091 01000077 010050C3 00000118 00000000 0000000B E4126400 280A3700 0A005403 90019001 90019001 90019001 90010000 00000002 011E07DC 00DC00DC 002C0100 00590069 004A004A 005F0073 00730064 00400090 92976096 00905500 00000000 00000000 00000000 00000000 0202D430 00000210 60EA0000 0210 My benchmark results: Geekbench OpenCL: 192,000 Points (average) Luxmark: 29,500 (average) Valley benchmark ran stable for 60 minutes with average GPU temperature being 69°C, fan speed was a low 1,800. Enjoy and let me know how this works for you guys! VegaTab_64.kext.zip I would like to say a HUGE Thank you for your work and generosity! VegaTab_64.kext has been the only to have stabilized my MSI Vega64 OC. Link to comment Share on other sites More sharing options...
douirc Posted October 25, 2018 Share Posted October 25, 2018 @CMMChris Can the POWERPLAY Table be extracted from Windows 10 and inserted into macOS Mojave for identical performance? Windows 10 runs my ASRock Vega 64 perfectly and would love to replicate in macOS if possible. Thanks! Link to comment Share on other sites More sharing options...
douirc Posted October 26, 2018 Share Posted October 26, 2018 (edited) 8 hours ago, meaganmargaret said: Quote Well, yes it can. The PP_PhmSoftPowerPlayTable doesn't show up normally, but if you download MSIAfterburner and load it up (your AMD Vega card does not have to be MSI, btw - my Vega 64 is an XFX), and go into settings and tick "show extended power adjusts" (Thanks Max!!), the PP_PhmSoftPowerPlayTable will show up in the registry. You will have to massage it some to get the tables to hex version (so that they will show up like the "B6020801 0050....., etc" like CMMChris shows a lot in his VegaTab kexts). Then you can convert them using a couple of different methods. Iodine131 outlined one method in this thread - check page 11 of this thread, his post dated June 21 for that method. If you add in the hex version using Xcode, and then save the file (info.plist), and then open that in Clover Configurator, it will show you the version (text) that usually starts with TGII.... Installed Afterburner but can't find an option under the General tab called Show Extended Power Adjusts. You also said the table will show up in Registry. How do I find that? The only reason I care is because CMMChris's kext causes coil whine after a few hours. Rebooting resolves it but I don't know if it's doing damage. Was hoping copy/pasting the powertable from win 10 to macOS would be the safest bet but after reading more posts in this thread, doesn't look like it's the perfect solution either. Edited October 26, 2018 by douirc Link to comment Share on other sites More sharing options...
hugeschnauzer Posted October 26, 2018 Share Posted October 26, 2018 Hi. I've tried VGTab-en without sucess. im getting frezes on Unigine Heaven test, FCPX, Premiere.. Tried lots of things and nothing. Is the AMD10000Controller.kext the solution? thanks! Link to comment Share on other sites More sharing options...
CMMChris Posted October 26, 2018 Share Posted October 26, 2018 (edited) @douirc A Windows PPT won't fix your coil whine. You also have the coil whine under Windows when your card is under load. The reason you hear it more under macOS is that the Vega card is used more intense for UI rendering. If you want to lower the coil whine you need to lower your GPU clock. I will post a PPT for you to try once I am on my hack. tgIIAQBcAOEGAADuKwAAGwBIAAAAgKkDAPBJAgCVAAgA AAAAAAAAAAAAAAAAAAIBXABPAkYClACeAb4AKAF6AIwA vAEAAAAAcgIAAJAAqAJtAUMBlwHwSQIAcQICAgAAAAAA AAgAAAAAAAAABQAHAAMABQAAAAAAAAABCCADhAOdA7YD zwPoAwEEAQQBAbYDAQGEAwAIYOoAAABAGQEAAYA4AQAC 3EoBAAOQXwEABAB3AQAFkJEBAAZssAEABwEI0EwBAAAA gAAAAAAAAByDAQABAAAAAAAAAABwpwEAAgAAAAAAAAAA iLwBAAMAAAAAAAAAAMDUAQAEAAAAAAAAAABEIwIABQAA AAABAAAAPDUCAAYAAAAAAQAAADw1AgAHAAAAAAEAAAAA BWDqAAAAQBkBAACAOAEAANxKAQAAkF8BAAAACChuAAAA LMkAAAH4CwEAAoA4AQADkF8BAAT0kQEABdCwAQAGwNQB AAcACGw5AAAAJF4AAAH8hQAAAqy8AAADNNAAAARobgEA BQiXAQAG7KMBAAcAAWg8AQAAAQQ8QQAAAAAAUMMAAAAA AIA4AQACAACghgEABAAAAQgAmIUAAEC1AABg6gAAUMMA AAGAuwAAYOoAAJQLAQBQwwAAAgDhAACUCwEAQBkBAFDD AAADeP8AAEAZAQCIJgEAUMMAAARAGQEAgDgBAIA4AQBQ wwAABYA4AQDcSgEA3EoBAFDDAAAGAHcBAAB3AQCQXwEA UMMAAAeQkQEAkJEBAAB3AQBQwwAAARgAAAAAAAAAC+QS AAAoCjcACgBUA5ABkAGQAZABkAGQAZABAAAAAAACAB4H 3ADcANwALAEAAFkAaQBKAEoAXwBzAHMAZABAAJCSl2CW AJBVAAAAAAAAAAAAAAAAAAAAAAACAtQwAAACEGDqAAAC EA== @hugeschnauzer If you get freezes you are using the wrong settings. Please tell me what card you have and which VGTab settings you use. Edited October 26, 2018 by CMMChris Link to comment Share on other sites More sharing options...
hugeschnauzer Posted October 26, 2018 Share Posted October 26, 2018 5 hours ago, CMMChris said: @douirc A Windows PPT won't fix your coil whine. You also have the coil whine under Windows when your card is under load. The reason you hear it more under macOS is that the Vega card is used more intense for UI rendering. If you want to lower the coil whine you need to lower your GPU clock. I will post a PPT for you to try once I am on my hack. tgIIAQBcAOEGAADuKwAAGwBIAAAAgKkDAPBJAgCVAAgA AAAAAAAAAAAAAAAAAAIBXABPAkYClACeAb4AKAF6AIwA vAEAAAAAcgIAAJAAqAJtAUMBlwHwSQIAcQICAgAAAAAA AAgAAAAAAAAABQAHAAMABQAAAAAAAAABCCADhAOdA7YD zwPoAwEEAQQBAbYDAQGEAwAIYOoAAABAGQEAAYA4AQAC 3EoBAAOQXwEABAB3AQAFkJEBAAZssAEABwEI0EwBAAAA gAAAAAAAAByDAQABAAAAAAAAAABwpwEAAgAAAAAAAAAA iLwBAAMAAAAAAAAAAMDUAQAEAAAAAAAAAABEIwIABQAA AAABAAAAPDUCAAYAAAAAAQAAADw1AgAHAAAAAAEAAAAA BWDqAAAAQBkBAACAOAEAANxKAQAAkF8BAAAACChuAAAA LMkAAAH4CwEAAoA4AQADkF8BAAT0kQEABdCwAQAGwNQB AAcACGw5AAAAJF4AAAH8hQAAAqy8AAADNNAAAARobgEA BQiXAQAG7KMBAAcAAWg8AQAAAQQ8QQAAAAAAUMMAAAAA AIA4AQACAACghgEABAAAAQgAmIUAAEC1AABg6gAAUMMA AAGAuwAAYOoAAJQLAQBQwwAAAgDhAACUCwEAQBkBAFDD AAADeP8AAEAZAQCIJgEAUMMAAARAGQEAgDgBAIA4AQBQ wwAABYA4AQDcSgEA3EoBAFDDAAAGAHcBAAB3AQCQXwEA UMMAAAeQkQEAkJEBAAB3AQBQwwAAARgAAAAAAAAAC+QS AAAoCjcACgBUA5ABkAGQAZABkAGQAZABAAAAAAACAB4H 3ADcANwALAEAAFkAaQBKAEoAXwBzAHMAZABAAJCSl2CW AJBVAAAAAAAAAAAAAAAAAAAAAAACAtQwAAACEGDqAAAC EA== @hugeschnauzer If you get freezes you are using the wrong settings. Please tell me what card you have and which VGTab settings you use. XFX Vega 64 8Gb Radeon 1000 3900 target 55% Thank u very much man!!! Link to comment Share on other sites More sharing options...
Max.1974 Posted October 26, 2018 Share Posted October 26, 2018 (edited) Very good Meagan!!! Im prefer use my to stable kexts. And one them its not so high performance, but im have stable fan on 700-1000 rpm. Another, with very good cooler and high performance stable on 1600-2200 rpm and 213000 bench. Im found this way, but im can't believe to much in VegaTab app... good for all that works fine...im use okrasit settings and little bit adjusts on regedit from Windows...Good news for all!! Im guess... Edited October 26, 2018 by max.1974 Link to comment Share on other sites More sharing options...
hugeschnauzer Posted October 26, 2018 Share Posted October 26, 2018 (edited) 4 hours ago, meaganmargaret said: I should note that the 30200 kext (the one labelled "best") matches the Windows built-in Vega configuration performance for a Vega 64 XFX card almost exactly. Fan speeds, Luxmark results, temps, pretty much the same. It might pull more power, but I can't tell. The 29500 kext has more moderate settings, with lower initial power (I think I set it to 100). Finally, I ran Heaven on both and some other tests, but I got a very good score with the 30200 kext (again the one labelled "best") at 1080p. On Heaven, it appears to run hot (according to Heaven), but the temps that I got from running the ioreg script in terminal were much lower......don't know why, but it completed Heaven just fine. Got a good Metal score on "compute" from Geekbench (around ~220000) Of course.....YMMV......we all understand that, right? Thank you very much!!! Used this kext inside Clover , but didnt get good resuklts in Cinebench .. around 20fps less.. any idea? Do i need the AMD10000Controller.kext change inside Extensions also? Im on Mojave Edited October 26, 2018 by hugeschnauzer Link to comment Share on other sites More sharing options...
CMMChris Posted October 26, 2018 Share Posted October 26, 2018 (edited) No, don't change system files. Might be overwritten by updates. Either inject your PPT by Kext or Clover Device Properties method. Put this inside your Clover config.plist as shown in the screenshot. <key>Properties</key> <dict> <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key> <dict> <key>PP_DisableClockStretcher</key> <integer>1</integer> <key>PP_DisablePowerContainment</key> <integer>1</integer> <key>PP_DisableVoltageIsland</key> <integer>0</integer> <key>PP_PhmSoftPowerPlayTable</key> <data> tgIIAQBcAOEGAADuKwAAGwBIAAAAgKkDAPBJAgCVAAgA AAAAAAAAAAAAAAAAAAIBXABPAkYClACeAb4AKAF6AIwA vAEAAAAAcgIAAJAAqAJtAUMBlwHwSQIAcQICAgAAAAAA AAgAAAAAAAAABQAHAAMABQAAAAAAAAABCCADhAO2A88D 6AMBBAEEAQQBAbYDAQGEAwAIYOoAAABAGQEAAYA4AQAC 3EoBAAOQXwEABAB3AQAFkJEBAAZssAEABwEIOMEBAAAA gAAAAAAAAMDUAQABAAAAAAAAAABI6AEAAgAAAAAAAAAA 0PsBAAMAAAAAAAAAAFgPAgAEAAAAAAAAAADgIgIABQAA AAABAAAAaDYCAAYAAAAAAQAAAPBJAgAHAAAAAAEAAAAA BWDqAAAAQBkBAACAOAEAANxKAQAAkF8BAAAACChuAAAA LMkAAAH4CwEAAoA4AQADkF8BAAT0kQEABdCwAQAGwNQB AAcACGw5AAAAJF4AAAH8hQAAAqy8AAADNNAAAARobgEA BQiXAQAG7KMBAAcAAWg8AQAAAQQ8QQAAAAAAUMMAAAAA AIA4AQACAACghgEABAAAAQgAmIUAAEC1AABg6gAAUMMA AAGAuwAAYOoAAJQLAQBQwwAAAgDhAACUCwEAQBkBAFDD AAADeP8AAEAZAQCIJgEAUMMAAARAGQEAgDgBAIA4AQBQ wwAABYA4AQDcSgEA3EoBAFDDAAAGAHcBAAB3AQCQXwEA UMMAAAeQkQEAkJEBAAB3AQBQwwAAARgAAAAAAAAAC+QS AAAoCjcACgBUA5ABkAGQAZABkAGQAZABAAAAAAACAB4H 3ADcANwALAEAAFkAaQBKAEoAXwBzAHMAZABAAJCSl2CW AJBVAAAAAAAAAAAAAAAAAAAAAAACAtQwAAACEGDqAAAC EA== </data> </dict> </dict> This should give you around 28k in Luxmark, 190,000 in Geekbench and a silent card. Edited October 26, 2018 by CMMChris Link to comment Share on other sites More sharing options...
hugeschnauzer Posted October 26, 2018 Share Posted October 26, 2018 (edited) 1 hour ago, CMMChris said: No, don't change system files. Might be overwritten by updates. Either inject your PPT by Kext or Clover Device Properties method. Put this inside your Clover config.plist as shown in the screenshot. <key>Properties</key> <dict> <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key> <dict> <key>PP_DisableClockStretcher</key> <integer>1</integer> <key>PP_DisablePowerContainment</key> <integer>1</integer> <key>PP_DisableVoltageIsland</key> <integer>0</integer> <key>PP_PhmSoftPowerPlayTable</key> <data> tgIIAQBcAOEGAADuKwAAGwBIAAAAgKkDAPBJAgCVAAgA AAAAAAAAAAAAAAAAAAIBXABPAkYClACeAb4AKAF6AIwA vAEAAAAAcgIAAJAAqAJtAUMBlwHwSQIAcQICAgAAAAAA AAgAAAAAAAAABQAHAAMABQAAAAAAAAABCCADhAO2A88D 6AMBBAEEAQQBAbYDAQGEAwAIYOoAAABAGQEAAYA4AQAC 3EoBAAOQXwEABAB3AQAFkJEBAAZssAEABwEIOMEBAAAA gAAAAAAAAMDUAQABAAAAAAAAAABI6AEAAgAAAAAAAAAA 0PsBAAMAAAAAAAAAAFgPAgAEAAAAAAAAAADgIgIABQAA AAABAAAAaDYCAAYAAAAAAQAAAPBJAgAHAAAAAAEAAAAA BWDqAAAAQBkBAACAOAEAANxKAQAAkF8BAAAACChuAAAA LMkAAAH4CwEAAoA4AQADkF8BAAT0kQEABdCwAQAGwNQB AAcACGw5AAAAJF4AAAH8hQAAAqy8AAADNNAAAARobgEA BQiXAQAG7KMBAAcAAWg8AQAAAQQ8QQAAAAAAUMMAAAAA AIA4AQACAACghgEABAAAAQgAmIUAAEC1AABg6gAAUMMA AAGAuwAAYOoAAJQLAQBQwwAAAgDhAACUCwEAQBkBAFDD AAADeP8AAEAZAQCIJgEAUMMAAARAGQEAgDgBAIA4AQBQ wwAABYA4AQDcSgEA3EoBAFDDAAAGAHcBAAB3AQCQXwEA UMMAAAeQkQEAkJEBAAB3AQBQwwAAARgAAAAAAAAAC+QS AAAoCjcACgBUA5ABkAGQAZABkAGQAZABAAAAAAACAB4H 3ADcANwALAEAAFkAaQBKAEoAXwBzAHMAZABAAJCSl2CW AJBVAAAAAAAAAAAAAAAAAAAAAAACAtQwAAACEGDqAAAC EA== </data> </dict> </dict> This should give you around 28k in Luxmark, 190,000 in Geekbench and a silent card. Will try man!!! so glad to hear that!! Im facing crashs since i bought the machine.!! Thank you very much. Really!! I wil, put this inside Clover, but what kext i do need to use? im on Mojave. Ok? Edited October 26, 2018 by hugeschnauzer Link to comment Share on other sites More sharing options...
hugeschnauzer Posted October 26, 2018 Share Posted October 26, 2018 (edited) 27 minutes ago, meaganmargaret said: Well, which one did you use? The 29K one or the 30 one? And 20fps less than what? What were you using that was 20fps more? And no you shouldn't change AMD10000Controller.kext. In fact, you should have a plain vanilla unmodified original AMD10000Controller.kext to use with these kexts...... This all depends on the method you use. Max prefers to modify AMD10000Controller.kext, and that's perfectly valid. But my method, and also Chris's method, best I can tell, is to leave AMD10000Controller.kext alone and just use VegaTab to create a kext to influence the performance of the Vega card in macOS, applying it either in Clover - Kexts - Other, or inserting the configuration generated by VegaTab via the Clover - Devices configuration page of Clover Configurator. The main reason I posted my kexts is because I have an XFX card, which has been denigrated in this forum, and other places, and little development has been done on it. I wanted an XFX Vega 64 working kext posted from a real user of an XFX Vega 64 card to be available for XFX Vega 64 owners. And both of the kexts I posted run well on my system and produce great results. Are they perfect? No, they are not. They produce respectable results. If you're not satisfied, then you should spend some time with VegaTab and see if you can produce a Kext that gives you the results you need. Good luck.....! Awesome Meagan!! No words to thank you all!! Its more logical for me to do not touch the extension, since it will be updated someday as Chris said. About my test (Cinebench 110fps / 20fps less) was using both kexts u post. The best one and another version. But i just used then inside EFI/CLOVER/KEXTS What do i need to do now? (im on Mojave. Ok?) 1 - Move VEGAbest to EFI/CLOVER/KEXTS 2 - Paste this inside Device Properties into Clover? (thanks 4 your time!) <key>Properties</key> <dict> <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key> <dict> <key>PP_DisableClockStretcher</key> <integer>1</integer> <key>PP_DisablePowerContainment</key> <integer>1</integer> <key>PP_DisableVoltageIsland</key> <integer>0</integer> <key>PP_PhmSoftPowerPlayTable</key> <data> tgIIAQBcAOEGAADuKwAAGwBIAAAAgKkDAPBJAgCVAAgA AAAAAAAAAAAAAAAAAAIBXABPAkYClACeAb4AKAF6AIwA vAEAAAAAcgIAAJAAqAJtAUMBlwHwSQIAcQICAgAAAAAA AAgAAAAAAAAABQAHAAMABQAAAAAAAAABCCADhAO2A88D 6AMBBAEEAQQBAbYDAQGEAwAIYOoAAABAGQEAAYA4AQAC 3EoBAAOQXwEABAB3AQAFkJEBAAZssAEABwEIOMEBAAAA gAAAAAAAAMDUAQABAAAAAAAAAABI6AEAAgAAAAAAAAAA 0PsBAAMAAAAAAAAAAFgPAgAEAAAAAAAAAADgIgIABQAA AAABAAAAaDYCAAYAAAAAAQAAAPBJAgAHAAAAAAEAAAAA BWDqAAAAQBkBAACAOAEAANxKAQAAkF8BAAAACChuAAAA LMkAAAH4CwEAAoA4AQADkF8BAAT0kQEABdCwAQAGwNQB AAcACGw5AAAAJF4AAAH8hQAAAqy8AAADNNAAAARobgEA BQiXAQAG7KMBAAcAAWg8AQAAAQQ8QQAAAAAAUMMAAAAA AIA4AQACAACghgEABAAAAQgAmIUAAEC1AABg6gAAUMMA AAGAuwAAYOoAAJQLAQBQwwAAAgDhAACUCwEAQBkBAFDD AAADeP8AAEAZAQCIJgEAUMMAAARAGQEAgDgBAIA4AQBQ wwAABYA4AQDcSgEA3EoBAFDDAAAGAHcBAAB3AQCQXwEA UMMAAAeQkQEAkJEBAAB3AQBQwwAAARgAAAAAAAAAC+QS AAAoCjcACgBUA5ABkAGQAZABkAGQAZABAAAAAAACAB4H 3ADcANwALAEAAFkAaQBKAEoAXwBzAHMAZABAAJCSl2CW AJBVAAAAAAAAAAAAAAAAAAAAAAACAtQwAAACEGDqAAAC EA== </data> </dict> </dict> Edited October 26, 2018 by hugeschnauzer 1 Link to comment Share on other sites More sharing options...
hugeschnauzer Posted October 26, 2018 Share Posted October 26, 2018 (edited) 41 minutes ago, meaganmargaret said: Either one will work: 1. Move the 30Best kext to EFI\Clover\Kexts\Other (or 10.14). Put it in the folder where all of your other kexts are.. OR Insert the values you have already in inside Device Properties.....what you have looks okay, but make sure you are using a text editor to do this. IF you intend to use Plist Editor Pro or Xcode, you can't use the TGII as this is text and won't work there (there you would have to use the hex version (B602....."). I don't think I still have the hex output for those two kexts that I posted. Either method will work, but just do one of the two. If you choose one and it doesn't seem to work, delete that method and use the other. For me, it's easier to just if I want to change or alter the performance of my card to just delete the kext from EFI\Clover\Kexts\Other (that's where I keep all of my Clover kexts), and replace it. But there are probably good reasons/arguments for doing it the other way too. And, I want to be very clear to everyone: The kexts I posted should work with an XFX Vega 64 card. I am not advocating the use of these kexts for any other card. Will they work with other Vegas? Probably, but they are configured and tested on my XFX Vega 64 card and so are specific to my XFX card.... Thanks Megan!!! I copied this text properly with plist into Config. but nothing changed. Doesnt mtter what i do... remove the kext, for example. I cant get the 130/140fps in cinebench anymore :-( Does it work on Mojave? what could be happening? Edited October 26, 2018 by hugeschnauzer Link to comment Share on other sites More sharing options...
hugeschnauzer Posted October 26, 2018 Share Posted October 26, 2018 (edited) 1 hour ago, meaganmargaret said: I don't use that method, so I can't help you as to why it didn't work. I am on Mojave, and using the method I use, (which is to copy the kext into EFI\Clover\Kexts\Other) these kexts work fine. I have tested them with Heaven, Luxmark, and Geekbench (compute). I work on this computer every day, and I've had no issues. The 30Best is the one I use, but if you're feeling like you want to be safer, you could use the 29300kext, or even use one of Chris's kexts (like the one he says give you 28000 on a Luxmark). Be careful with Plist Editor Pro if that is what you used. For that editor, you must have the hex version of the configuration data, and I don't have that. If you copied the TGII.... into Plist Editor Pro, it will fail. If you used TextWrangler, that would be okay, but then I really don't know what happened and why it wouldn't work. As I said in another post, I only copy the 30best kext into EFI/Clover/Kexts/Other, because for me, that is so very very very much easier. Much easier to change as well. If I were you, I would copy the current config.plist to another place (say on your desktop). Then I would take the remaining config.plist that should still be in your EFI folder and delete that insertion method entirely, (and I do mean ALL of it - every bit of it, all the tables you entered and devices for the Vega card) and copy the 30Best kext into EFI/Clover/Kexts/Other and reboot and test. (Remember, you have your original config.plist with all of your previous configuration data for the insertion method sitting on your desktop). If that works, then there is something wrong with your insertion method, and that you would have troubleshoot on your own. But to revert back to your insertion method, all you would have to do is remove the config.plist (the one that doesn't have the insertion method anymore) and replace it with the one (the config.plist that should still have your initial attempt using the insertion method) on your desktop. Okay, I've got things I need to work on, so I have to move on. Hope that's helpful..... I've tried both methods.. crashes again in FCPX... :-( In Unigine tests i see rpm changes The console error i get is: (com.apple.DumpGPURestart): Service only ran for 1 seconds. Pushing respawn out by 9 seconds. Edited October 26, 2018 by hugeschnauzer Link to comment Share on other sites More sharing options...
Recommended Posts