Fljagd Posted February 11, 2017 Share Posted February 11, 2017 OsxAptioFixDrv-64.efi.zip Hello, Works very well at home Thank you for extending the memory range This will save more than one And as you suggest it is desirable to put only the essentials when you install clover Emuvariable is not necessary 1 Link to comment Share on other sites More sharing options...
PMheart Posted February 11, 2017 Share Posted February 11, 2017 Hello, Works very well at home Thank you for extending the memory range This will save more than one And as you suggest it is desirable to put only the essentials when you install clover Don't install the AptioFix from Clover pkg!!! I've given a trick for that. Link to comment Share on other sites More sharing options...
Fljagd Posted February 11, 2017 Share Posted February 11, 2017 Don't install the AptioFix from Clover pkg!!! I've given a trick for that. Yes, I followed the procedure 2 Link to comment Share on other sites More sharing options...
mfc88 Posted February 11, 2017 Share Posted February 11, 2017 Just a heads up that when trying to install 10.12.3 on an empty NVMe, I kept getting kernel panics when using Clover r4003. Had to revert to ole trustee: r3859! Link to comment Share on other sites More sharing options...
mfc88 Posted February 11, 2017 Share Posted February 11, 2017 Update 2/11/17 @ 8:45AM: Since PMHeart has graciously provided a OsxAptioFixDrv with 512MB of free space, I've been allowed to continue to test a OsxAptioFixDrv.efi over the past 3 days. So far, I haven't had any stability issues with my current Clover revision. However, do note, that I was having stability issues when running Clover EFI r3899+, and therefore had to revert back to using what I've been using already: r3859. It may just be my particular setup doesn't like the newer Clover versions, but its hard to say which is at fault (Clover, my system or the efi). Anyway, update at your own risk. Added a new EFI folder called: EFI_ASUS-PRO-USB3.1_10.12.3_FIXDRV-512MB.zip which includes my EFI and the modded .efi. Also added some CPU PM links that help new comers with checking/setting up XCPM mode. Updated my EFI 10.12.3 post to reflect new changes. 1 Link to comment Share on other sites More sharing options...
mfc88 Posted February 11, 2017 Share Posted February 11, 2017 Switched over to AppleALC.kext + CodecCommander.kext from the RealtekALC.kext. This way, I don't have to worry about finding Clover AppleHDA patches to fix a non-functioning RealtekALC.kext with every upgrade! Click here for the AppleALC wiki Pretty simple to do:-> Download AppleALC master folder from github or, if you're lazy, download the precompiled version-> If downloaded source files from github, compile it using Xcode (simply press the build button)-> Locate compiled kext in: /Users/{Mac Username}/Library/Developer/Xcode/DerivedData/AppleALC-xxxxxxxxxxxxxxxxxxx/Build/Products/Debug/AppleALC.kext (the ResourceConverter is for debugging purposes, don't need it)-> Place the AppleALC.kext + CodecCommander.kext into EFI -> Clover -> Kexts -> Other Must do:-> Modify your DSDT.aml or create an SSDT-ALZA/HDAS.aml and SSDT-BR3A/BR2A/BR1A/PEG0/PEGP.aml to inject these attributes (note: Your compatible device and device IDs will be different, use Windows or Google to find yours -- also what audio layout ID you use will require some experimentation-- read the wiki for more information on supported audio layout IDs for your audio device): Info on editing the DSDT.aml and/or creating your own SSDT:- SSDT notes (also includes a DSDT.aml (DSDT-withoutSSDTs.zip) that doesn't require any additional SSDTs aside from Pike's CPU PM SSDT)- Info on GPU injection via DSDT- More info on GPU injection via DSDT- Info on GPU injection via SSDT The following code is incomplete, but it's there just to showcase what you'll want to include in your DSDT/SSDT (see my provided SSDTs in SSDT notes link for complete code): SSDT-ALZA.aml or SSDT-HDAS.aml or renamed DSDT.aml _.SB.PCI0.ALZA / _.SB.PCI0.HDAS ==> _.SB.PCI0.HDEF with the following filled in with your values: Scope (\_SB.PCI0) { Device (HDEF) { Name (_ADR, 0x001B0000) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x0A) { "model", Buffer (0x19) { "Realtek Audio Controller" }, "hda-gfx", Buffer (0x0A) { "onboard-1" }, "layout-id", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "compatible", Buffer (0x0D) { "pci8086,8d20" }, "PinConfigurations", Buffer (One) { 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } } SSDT-BR3A.aml (or where-ever your GPU is located: BR1A, BR2A, PEG0, PEGP...etc) or a renamed DSDT.aml at _.SB.PCI0.XXXX.H001 (HDA1) with the following filled in with your values Device (HDAU) { Name (_ADR, One) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store (Package (0x10) { "built-in", Buffer (One) { 0x00 }, "device-id", Buffer (0x04) { 0xBA, 0x0F, 0x00, 0x00 }, "name", Buffer (0x05) { "HDAU" }, "AAPL,slot-name", Buffer (0x07) { "Slot-1" }, "device_type", Buffer (0x06) { "AUDIO" }, "name", Buffer (0x05) { "HDAU" }, "hda-gfx", Buffer (0x0A) { "onboard-2" }, "reg-ltrovr", Buffer (0x08) { 0x00, 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } 1 Link to comment Share on other sites More sharing options...
Fergarth Posted February 12, 2017 Share Posted February 12, 2017 Drinking a good Gin and trying to figure out if there is any way to make it possible to use previous Nvidia Web Drives in Sierra 12.4, without being just through editing NVDAStartupWeb.kext Link to comment Share on other sites More sharing options...
mfc88 Posted February 12, 2017 Share Posted February 12, 2017 Drinking a good Gin and trying to figure out if there is any way to make it possible to use previous Nvidia Web Drives in Sierra 12.4, without being just through editing NVDAStartupWeb.kext Modify nmano's NVDA_WebStartup.Kext should be a simple swap Link to comment Share on other sites More sharing options...
Fergarth Posted February 12, 2017 Share Posted February 12, 2017 Modify nmano's NVDA_WebStartup.Kext should be a simple swap Ok and where can i find this kext? Can you give me a link? Link to comment Share on other sites More sharing options...
mfc88 Posted February 12, 2017 Share Posted February 12, 2017 Ok and where can i find this kext? Can you give me a link? What's the 10.12.4 OS build definition? 16...? Link to comment Share on other sites More sharing options...
Fergarth Posted February 12, 2017 Share Posted February 12, 2017 What's the 10.12.4 OS build definition? 16...?You mean to change the plist of NVDAstartupweb.kext to 16E? This I have done since version 12.4 beta 1, but in this case does not allow acceleration. My idea was to find another solution, try to find something in NvidiaWebDrive.pkg that can be edited ? Link to comment Share on other sites More sharing options...
mfc88 Posted February 12, 2017 Share Posted February 12, 2017 This... not sure if it's going to work... but give it a go... If it does, consider it a temporary solution. If not, don't use 10.12.4. Problem solved. GTX_Injector NVWEB.kext.zip 1 Link to comment Share on other sites More sharing options...
Fergarth Posted February 12, 2017 Share Posted February 12, 2017 This... not sure if it's going to work... but give it a go... If it does, consider it a temporary solution. If not, don't use 10.12.4. Problem solved. Thanks, will try ? Link to comment Share on other sites More sharing options...
Fergarth Posted February 12, 2017 Share Posted February 12, 2017 This... not sure if it's going to work... but give it a go... If it does, consider it a temporary solution. If not, don't use 10.12.4. Problem solved. This kext, does the same as I had already done manually. I have to wait for a new webdrive suitable for 12.4 ... But thanks anyway! Link to comment Share on other sites More sharing options...
mfc88 Posted February 12, 2017 Share Posted February 12, 2017 Warning: If you use a Logitech Performance MX mouse (or similar) and are using Logitech Control Center Driver 3.9.5.66 it will cause random reboots in 10.12.3! Symptoms: After 5-10 minutes, the mouse will freeze, then the system will reboot. Update 2/12/17 @ 9:30PM: OsxAptioFixDrv.efi: Sleep appears to be partially broken. Power nap works, but putting the Mac to sleep manually results in a black screen on wake up (no video signal). Also, power nap, while working, tends to mess up Keychain permissions. I'd avoid any sleep/nap features for the time being. Link to comment Share on other sites More sharing options...
mfc88 Posted February 17, 2017 Share Posted February 17, 2017 But after some tests I came to the conclusion that the system is more stable with the 4 XCPM patches. Running 10.12.3. Was able to remove some XCPM patches according to your EFI, however, I needed one extra to get CPU turbo boost across all States: F: 89D8C1E008B99901 R: B800FF0000B99901 C: xcpm performance fix 1 (wrsmr fix to get CPU max) © okrasit Without: With: 2 Link to comment Share on other sites More sharing options...
Fergarth Posted February 18, 2017 Share Posted February 18, 2017 In fact I'm not using this XCPM patch (xcpm performance fix 1) and my result looks good, with more C / P-States and more complete than yours. I just select "Sync All Cores" on bios and use MP61_freqV_w_iMac171.kext on S/L/E and I like the final result 1 Link to comment Share on other sites More sharing options...
Sygey02 Posted February 21, 2017 Share Posted February 21, 2017 Hi guys! can anybody confirm if this its correct power management? AppleIntelInfo.kext v2.2 Copyright © 2012-2017 Pike R. Alpha. All rights reserved enableHWP................................: 0 Settings: ------------------------------------------ logMSRs..................................: 1 logIGPU..................................: 0 logCStates...............................: 1 logIPGStyle..............................: 1 InitialTSC...............................: 0x2206678655c7 (1039 MHz) MWAIT C-States...........................: 8480 Processor Brandstring....................: Intel® Core i7-6850K CPU @ 3.60GHz Processor Signature..................... : 0x406F1 ------------------------------------------ - Family............................... : 6 - Stepping............................. : 1 - Model................................ : 0x4F (79) Model Specific Registers (MSRs) ------------------------------------------ MSR_CORE_THREAD_COUNT............(0x35) : 0xFFFFFF805CE05F00 ------------------------------------------ - Core Count........................... : 6 - Thread Count......................... : 12 MSR_PLATFORM_INFO................(0xCE) : 0x20080C3BF3812400 ------------------------------------------ - Maximum Non-Turbo Ratio.............. : 0x24 (3600 MHz) - Ratio Limit for Turbo Mode........... : 1 (programmable) - TDP Limit for Turbo Mode............. : 1 (programmable) - Low Power Mode Support............... : 1 (LPM supported) - Number of ConfigTDP Levels........... : 1 (additional TDP level(s) available) - Maximum Efficiency Ratio............. : 12 - Minimum Operating Ratio.............. : 8 MSR_PMG_CST_CONFIG_CONTROL.......(0xE2) : 0x3 ------------------------------------------ - I/O MWAIT Redirection Enable......... : 0 (not enabled) - CFG Lock............................. : 0 (MSR not locked) - C3 State Auto Demotion............... : 0 (disabled/unsupported) - C1 State Auto Demotion............... : 0 (disabled/unsupported) - C3 State Undemotion.................. : 0 (disabled/unsupported) - C1 State Undemotion.................. : 0 (disabled/unsupported) - Package C-State Auto Demotion........ : 0 (disabled/unsupported) - Package C-State Undemotion........... : 0 (disabled/unsupported) MSR_PMG_IO_CAPTURE_BASE..........(0xE4) : 0x0 - C-state Range........................ : 0 (C-States not included, I/O MWAIT redirection not enabled) IA32_MPERF.......................(0xE7) : 0xFF1686889E IA32_APERF.......................(0xE8) : 0x1055FBC302A MSR_0x150........................(0x150) : 0x20000000000 MSR_FLEX_RATIO...................(0x194) : 0xE0000 MSR_IA32_PERF_STATUS.............(0x198) : 0x27F700002800 ------------------------------------------ - Current Performance State Value...... : 0x2800 (4000 MHz) MSR_IA32_PERF_CONTROL............(0x199) : 0x3100 ------------------------------------------ - Target performance State Value....... : 0x3100 (4900 MHz) - Intel Dynamic Acceleration........... : 0 (IDA engaged) IA32_CLOCK_MODULATION............(0x19A) : 0x0 IA32_THERM_INTERRUPT.............(0x19B) : 0x0 IA32_THERM_STATUS................(0x19C) : 0x88460000 ------------------------------------------ - Thermal Status....................... : 0 - Thermal Log.......................... : 0 - PROCHOT # or FORCEPR# event.......... : 0 - PROCHOT # or FORCEPR# log............ : 0 - Critical Temperature Status.......... : 0 - Critical Temperature log............. : 0 - Thermal Threshold #1 Status.......... : 0 - Thermal Threshold #1 log............. : 0 - Thermal Threshold #2 Status.......... : 0 - Thermal Threshold #2 log............. : 0 - Power Limitation Status.............. : 0 - Power Limitation log................. : 0 - Current Limit Status................. : 0 - Current Limit log.................... : 0 - Cross Domain Limit Status............ : 0 - Cross Domain Limit log............... : 0 - Digital Readout...................... : 70 - Resolution in Degrees Celsius........ : 1 - Reading Valid........................ : 1 (valid) MSR_THERM2_CTL...................(0x19D) : 0x0 IA32_MISC_ENABLES................(0x1A0) : 0x850089 ------------------------------------------ - Fast-Strings......................... : 1 (enabled) - FOPCODE compatibility mode Enable.... : 0 - Automatic Thermal Control Circuit.... : 1 (enabled) - Split-lock Disable................... : 0 - Performance Monitoring............... : 1 (available) - Bus Lock On Cache Line Splits Disable : 0 - Hardware prefetch Disable............ : 0 - Processor Event Based Sampling....... : 0 (PEBS supported) - GV1/2 legacy Enable.................. : 0 - Enhanced Intel SpeedStep Technology.. : 1 (enabled) - MONITOR FSM.......................... : 1 (MONITOR/MWAIT supported) - Adjacent sector prefetch Disable..... : 0 - CFG Lock............................. : 0 (MSR not locked) - xTPR Message Disable................. : 1 (disabled) MSR_TEMPERATURE_TARGET...........(0x1A2) : 0x640A00 ------------------------------------------ - Turbo Attenuation Units.............. : 0 - Temperature Target................... : 100 - TCC Activation Offset................ : 0 MSR_MISC_PWR_MGMT................(0x1AA) : 0x402000 ------------------------------------------ - EIST Hardware Coordination........... : 0 (hardware coordination enabled) - Energy/Performance Bias support...... : 1 - Energy/Performance Bias.............. : 0 (disabled/MSR not visible to software) - Thermal Interrupt Coordination Enable : 1 (thermal interrupt routed to all cores) MSR_TURBO_RATIO_LIMIT............(0x1AD) : 0x2525282828282828 ------------------------------------------ - Maximum Ratio Limit for C01.......... : 28 (4000 MHz) - Maximum Ratio Limit for C02.......... : 28 (4000 MHz) - Maximum Ratio Limit for C03.......... : 28 (4000 MHz) - Maximum Ratio Limit for C04.......... : 28 (4000 MHz) - Maximum Ratio Limit for C05.......... : 28 (4000 MHz) - Maximum Ratio Limit for C06.......... : 28 (4000 MHz) IA32_ENERGY_PERF_BIAS............(0x1B0) : 0x5 ------------------------------------------ - Power Policy Preference...............: 5 (balanced performance and energy saving) MSR_POWER_CTL....................(0x1FC) : 0x2104005B ------------------------------------------ - Bi-Directional Processor Hot..........: 1 (enabled) - C1E Enable............................: 1 (enabled) MSR_RAPL_POWER_UNIT..............(0x606) : 0xA0E03 ------------------------------------------ - Power Units.......................... : 3 (1/8 Watt) - Energy Status Units.................. : 14 (61 micro-Joules) - Time Units .......................... : 10 (976.6 micro-Seconds) MSR_PKG_POWER_LIMIT..............(0x610) : 0x7FFD00014EA82 ------------------------------------------ - Package Power Limit #1............... : 3408 Watt - Enable Power Limit #1................ : 1 (enabled) - Package Clamping Limitation #1....... : 0 (disabled) - Time Window for Power Limit #1....... : 10 (2560 milli-Seconds) - Package Power Limit #2............... : 4090 Watt - Enable Power Limit #2................ : 1 (enabled) - Package Clamping Limitation #2....... : 1 (allow going below OS-requested P/T state setting Time Window for Power Limit #2) - Time Window for Power Limit #2....... : 3 (20 milli-Seconds) - Lock................................. : 0 (MSR not locked) MSR_PKG_ENERGY_STATUS............(0x611) : 0x8A2EF03F ------------------------------------------ - Total Energy Consumed................ : 141499 Joules (Watt = Joules / seconds) MSR_PKG_POWER_INFO...............(0x614) : 0x1700460 ------------------------------------------ - Thermal Spec Power................... : 140 Watt - Minimum Power........................ : 0 - Maximum Power........................ : 0 - Maximum Time Window.................. : 0 MSR_PP0_POWER_LIMIT..............(0x638) : 0x14FFD0 ------------------------------------------ - Power Limit.......................... : 4090 Watt - Enable Power Limit................... : 1 (enabled) - Clamping Limitation.................. : 0 (disabled) - Time Window for Power Limit.......... : 10 (10240 milli-Seconds) - Lock................................. : 0 (MSR not locked) MSR_PP0_ENERGY_STATUS............(0x639) : 0x0 MSR_TURBO_ACTIVATION_RATIO.......(0x64C) : 0x0 MSR_PKGC3_IRTL...................(0x60a) : 0x0 MSR_PKGC6_IRTL...................(0x60b) : 0x0 MSR_PKG_C2_RESIDENCY.............(0x60d) : 0x463B98A26AC MSR_PKG_C3_RESIDENCY.............(0x3f8) : 0x0 MSR_PKG_C6_RESIDENCY.............(0x3f9) : 0xB14B8EB0E40 IA32_TSC_DEADLINE................(0x6E0) : 0x22066B94879A CPU Ratio Info: ------------------------------------------ Base Clock Frequency (BLCK)............. : 100 MHz Maximum Efficiency Ratio/Frequency.......: 12 (1200 MHz) Maximum non-Turbo Ratio/Frequency........: 36 (3600 MHz) Maximum Turbo Ratio/Frequency............: 40 (4000 MHz) P-State ratio * 100 = Frequency in MHz ------------------------------------------ CPU P-States [ 37 (40) ] CPU C6-Cores [ 1 3 4 7 8 11 ] CPU P-States [ 20 37 (40) ] CPU C6-Cores [ 1 2 3 4 6 7 8 11 ] CPU P-States [ (12) 20 37 40 ] CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 10 11 ] CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ] CPU P-States [ (12) 20 33 37 40 ] CPU P-States [ (12) 20 21 33 37 40 ] CPU P-States [ 12 20 21 23 33 37 (40) ] CPU P-States [ (12) 20 21 23 24 33 37 40 ] CPU P-States [ 12 20 21 22 23 24 33 37 (40) ] CPU P-States [ (12) 19 20 21 22 23 24 33 37 40 ] CPU P-States [ 12 19 20 21 22 23 24 26 33 37 (40) ] CPU P-States [ (12) 19 20 21 22 23 24 26 28 33 37 40 ] CPU P-States [ (12) 19 20 21 22 23 24 25 26 28 33 37 40 ] CPU P-States [ (12) 19 20 21 22 23 24 25 26 28 30 33 37 40 ] CPU P-States [ 12 19 20 21 22 23 24 25 26 27 28 30 33 37 (40) ] CPU P-States [ 12 19 20 21 22 23 24 25 26 27 28 30 31 33 37 (40) ] CPU P-States [ 12 19 20 21 22 23 24 25 26 27 28 29 30 31 33 37 (40) ] CPU P-States [ (12) 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 37 40 ] CPU P-States [ 12 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 37 (40) ] CPU P-States [ (12) 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 37 40 ] CPU P-States [ 12 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 37 39 (40) ] CPU P-States [ 12 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 36 37 39 (40) ] CPU P-States [ (12) 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 39 40 ] CPU P-States [ (12) 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 ] CPU P-States [ 12 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 (40) ] bash-3.2# cat /tmp/AppleIntelInfo.dat Link to comment Share on other sites More sharing options...
Fergarth Posted February 21, 2017 Share Posted February 21, 2017 Hi guys! can anybody confirm if this its correct power management? In my opinion is not correct, there should be more steps in the last lines, especially the last should be all. And the line of your IPG in idle, should be in the minimum frequencies of the processor that is 1200MHz. But it's just my opinion... Speaking only of the last line, although not the only one that is not correct... This is what you have in the last line: CPU P-States [ 12 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 (40) ] This is what in my opinion you should have: CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 (40) ] 1 Link to comment Share on other sites More sharing options...
Sygey02 Posted February 21, 2017 Share Posted February 21, 2017 Hi Fergarth! Can you provide your clover folder to se watt settings do yo have ? or can you recommend some patches for this processor? Thx! Link to comment Share on other sites More sharing options...
Fergarth Posted February 21, 2017 Share Posted February 21, 2017 Hi Fergarth! Can you provide your clover folder to se watt settings do yo have ? or can you recommend some patches for this processor? Thx! Hi Sygey, I could leave my EFI here and I left it in other previous posts, but given the difference between our hardware, I think nothing would be compatible. Everything in my EFI is optimized specifically for my system... It would be advisable that someone with a board and processor just like yours could help... But about patches, these are the ones I use, but as I said before, they work together with the rest, DSDT, SSDT, bios configuration, and i don´t use NVMe SSD for now, etc... config.rar Link to comment Share on other sites More sharing options...
mfc88 Posted February 22, 2017 Share Posted February 22, 2017 Hi Fergarth! Can you provide your clover folder to se watt settings do yo have ? or can you recommend some patches for this processor? Thx! Head over to Pike's Universum (check the comments). I believe several other people have been asking questions regarding the "newer" Broadwell-E CPUs... 2 Link to comment Share on other sites More sharing options...
mfc88 Posted February 22, 2017 Share Posted February 22, 2017 Just a small update... Currently running all kexts in /System/Library/Extensions (no more kexts in EFI->Clover->kexts->10.12/other). According to Rehabman, this should survive upgrades as Apple doesn't touch non-Apple kexts. Been running this for about 3-4 days. So far, so good! Currently only experimenting with this on my test bench. Soooo... when it comes time to upgrade to 10.12.4, I'll do a follow up on how the update goes. 1 Link to comment Share on other sites More sharing options...
PMheart Posted February 22, 2017 Share Posted February 22, 2017 Just a small update... Currently running all kexts in /System/Library/Extensions (no more kexts in EFI->Clover->kexts->10.12/other). According to Rehabman, this should survive upgrades as Apple doesn't touch non-Apple kexts. Been running this for about 3-4 days. So far, so good! Currently only experimenting with this on my test bench. Soooo... when it comes time to upgrade to 10.12.4, I'll do a follow up on how the update goes. Why not use BrcmFirmwareRepo if you put all kexts into SLE, will be much more efficient.And also. Why did you still need USBInjectAll when you have got a proper injector kext (Assuming the XHCI-x99-Injector.kext) Thirdly. It seems that your AHCIPortInjector and AHCI_Intel_Generic_SATA.kext are the same? And therefore just keep one of them. Fourthly. Since you have put everything into SLE and just get rid of AppleALC IMHO. AppleALC can be not reliable in SLE and truthfully you have no need for it cuz you can also make a dummy next (like I did the dummy X86 kext for @Fergarth) + proper KextToPatch for AppleHDA (also maybe AppleHDAController if necessary) Sent from my iPhone 7 using Tapatalk Link to comment Share on other sites More sharing options...
mfc88 Posted February 22, 2017 Share Posted February 22, 2017 Why not use BrcmFirmwareRepo if you put all kexts into SLE, will be much more efficient. And also. Why did you still need USBInjectAll when you have got a proper injector kext (Assuming the XHCI-x99-Injector.kext) Thirdly. It seems that your AHCIPortInjector and AHCI_Intel_Generic_SATA.kext are the same? And therefore just keep one of them. Fourthly. Since you have put everything into SLE and just get rid of AppleALC IMHO. AppleALC can be not reliable in SLE and truthfully you have no need for it cuz you can also make a dummy next (like I did the dummy X86 kext for @Fergarth) + proper KextToPatch for AppleHDA (also maybe AppleHDAController if necessary) Sent from my iPhone 7 using Tapatalk -- BrcmFirmwareRepo??? Never heard of it. Can you expand on how to create it? -- USBInjectAll.kext injects just USB 2.0 ports, while XHCI-x99-Injector.kext injects 3.0 ports (per Rehabman's github). They work alongside SSDT-UAIC.aml If you have an X99-series chipset XHC controller, 8086:8d31, install XHCI-x99-injector.kext from the project as well. The USB3 drivers will not load without this injector kext.-- AHCIPortInjector/AHCI_Intel_Generic_SATA ... I'll have to look into removing them. I think I injected everything via SSDT anyway, so these are useless. Will have to test. -- AppleHDA patches broke in 10.12.3 for me. I had to remove them in order for the RealtekALC.kext to work (to even get HDMI audio). I can switch back to RealtekALC.kext, but I noticed it doesn't inject all possible devices (Digital Out, Internal Speakers, Line In and Line out). It only recognizes my m9xx (USB DAC) and my ASUS PB328Q monitor speakers. Link to comment Share on other sites More sharing options...
Recommended Posts