Mike Ranger Posted November 19, 2019 Share Posted November 19, 2019 Does CPUFriend provide the same performance as the previous Kernel Patches? My 6900k would only full perform with full XCPM functionality with the patches. Will try that thanks. Link to comment Share on other sites More sharing options...
canyondust Posted November 19, 2019 Share Posted November 19, 2019 12 hours ago, nmano said: Thanks All OC ITs worked now. Kernel ->Patch kexts patching not work please look my config I am using patched AppleHDA.Device IDS patch not work. How to enable xcpm_core_scope_msrs Find 31D2E851 FDFFFF Replace 31D29090 909090 config.plist This is handled by section 7.7 in the configuration.pdf. There are quirks for those (7.7.1, and 7.7.2) But as stated in the doc, definitely try to patch your CFG LOCK. not to go back to that 'other' site, but here is a detailed description of the process: edit: corrected the document section numbers. 2 Link to comment Share on other sites More sharing options...
pitrysha Posted November 19, 2019 Share Posted November 19, 2019 1 hour ago, Mike Ranger said: Does CPUFriend provide the same performance as the previous Kernel Patches? My 6900k would only full perform with full XCPM functionality with the patches. Will try that thanks. Will provide. Only you need to download PMdr.kext for Broadwell my intended for Haswell Link to comment Share on other sites More sharing options...
Ellybz Posted November 19, 2019 Share Posted November 19, 2019 @nmano That patch is unnecessary on Gigabyte X299. Sleep/wake functions works perfectly with the "AppleXcpmCfgLock" quirk. 1 Link to comment Share on other sites More sharing options...
AudioGod Posted November 19, 2019 Share Posted November 19, 2019 (edited) Hi All, Can anybody help me with a few problems I'm having with my OC EFI please? Its perfect for Catalina but if I try and boot into windows it BSODS my system instantly and reboots into my bios. (ACPI Bios Error) also I have blessed my windows path and in the boot options I have it listed as 1. bootcamp, 2. Catalina, 3. Recovery, 4. windows 10, How do I remove option 1 (bootcamp) and 3 (Recovery) so its just showing as Catalina and Windows 10 (Catalina being the top and default boot option)? Im really green when it comes to OC but im trying to learn so if anybody can help me or Evan better take a look as my EFI or DSDT and correct it for me that would be just Awesome of you. Im hoping somebody can help. Thanks in advance Guys, Edited November 19, 2019 by AudioGod 1 Link to comment Share on other sites More sharing options...
nmano Posted November 19, 2019 Share Posted November 19, 2019 (edited) Hi All Fixed this type 2 Error remove slide=0 Add darkwake=8 -v keepsyms=1 debug=0x100 npci=0x2000 darkwake=8 type 2 Error X99 motherboard. Thank you. Edited November 20, 2019 by nmano Link to comment Share on other sites More sharing options...
Maf3r0 Posted November 20, 2019 Share Posted November 20, 2019 22 hours ago, ken394 said: https://github.com/InsanelyHack/Emulated-NVRAM Despite tip from @ken394 (thanks) I'm still completely lost about emulated nvram I've read many stuff but is so controversial. If anybody successfully got nvram emulated, please take a look (thanks too) at this configurations that, according to this, are supposed to be set: EFI Driver: FwRuntimeService.efi Booter/Quirks: • AvoidRuntimeDefrag: YES, • DisableVariableWrite: YES -- and -- NO (those two options was described) • EnableWriteUnprotector: YES Note: With DisableVariableWrite as NO I get KP at shutdown/restart. Misc/Security: ExposeSensitiveData: 3 NVRAM: LegacyEnable: YES and finally: Generate nvram.plist: Run at Terminal: sudo defaults write com.apple.loginwindow LogoutHook /path/to/LogoutHook.command… According to this guide "This will create a new folder, which dumps the basic output. And you'll find a plist file named nvram.plist. Place this in the root of your EFI Folder" — but I cannot find this folder… in fact, I don't know even if that was created. 1 Link to comment Share on other sites More sharing options...
mhaeuser Posted November 20, 2019 Share Posted November 20, 2019 @Maf3r0 And you have actually adapted that last command with a *valid* path to the command file? Link to comment Share on other sites More sharing options...
nmano Posted November 20, 2019 Share Posted November 20, 2019 X99 motherboard with 5960X Now I have Pci configuration begin This kext patch not work OC I don’t know how to find Max & MinKernel Base: Comment: 5960XPatch Count: 1 Enabled: YES Find: 483D0000 0040 Identifier: com.apple.driver.IOPCIFamily Limit: Mask: (LEAVE THIS EMPTY) MaxKernel MinKernel Replace: 483D0000 0080 ReplaceMask: (LEAVE THIS EMPTY) Skip: Please help Thank you. Link to comment Share on other sites More sharing options...
pitrysha Posted November 20, 2019 Share Posted November 20, 2019 nmano I like in the picture 1 Link to comment Share on other sites More sharing options...
justin Posted November 20, 2019 Share Posted November 20, 2019 21 minutes ago, nmano said: X99 motherboard with 5960X Now I have Pci configuration begin This kext patch not work OC I don’t know how to find Max & MinKernel Base: Comment: 5960XPatch Count: 1 Enabled: YES Find: 483D0000 0040 Identifier: com.apple.driver.IOPCIFamily Limit: Mask: (LEAVE THIS EMPTY) MaxKernel MinKernel Replace: 483D0000 0080 ReplaceMask: (LEAVE THIS EMPTY) Skip: Please help Thank you. Your patch is to rename H=@ to H=, right? there are probably many H=@, so try Count=0 1 Link to comment Share on other sites More sharing options...
Maf3r0 Posted November 20, 2019 Share Posted November 20, 2019 3 hours ago, Download-Fritz said: @Maf3r0 And you have actually adapted that last command with a *valid* path to the command file? I think so… I've past this code to terminal: sudo defaults write com.apple.loginwindow LogoutHook (until space) and then drag LogoutHook.command (from Finder) into Terminal to complete code with file path. After that: Enter, password, and done… Nothing happens on Terminal or Finder. Is that right? Thanks for assistance!!! Link to comment Share on other sites More sharing options...
pitrysha Posted November 20, 2019 Share Posted November 20, 2019 nmano Try it like this 1 Link to comment Share on other sites More sharing options...
rottenpants Posted November 20, 2019 Share Posted November 20, 2019 (edited) Hey all. Im trying to convert from clover to opencore but so far im having no luck. I get a acpi error related to EC and IGPU, i also renamed EC0 to EC and GFX0 to IGPU in the config. Laptop HP pavilion CPU: i7 8550U Kabylake R GPU: UHD 620 + Nvidia card 16GB ram Thanks DSDT.aml config.plist Edited November 20, 2019 by rottenpants Link to comment Share on other sites More sharing options...
nmano Posted November 20, 2019 Share Posted November 20, 2019 5 hours ago, pitrysha said: nmano Try it like this @pitrysha I try every thing Still PCI configuration Begin Can you make sample efi I will check Thank you. Link to comment Share on other sites More sharing options...
pitrysha Posted November 20, 2019 Share Posted November 20, 2019 nmano I posted 20-23 posts back. 1 Link to comment Share on other sites More sharing options...
nmano Posted November 21, 2019 Share Posted November 21, 2019 8 hours ago, pitrysha said: nmano I posted 20-23 posts back. I check but I miss that. Link to comment Share on other sites More sharing options...
zzz3z Posted November 21, 2019 Share Posted November 21, 2019 (edited) Does anyone succeeded with GPU---UHD 620. Can you post your config.plist. I can boot osx 10.14.6/10.15 without inject DeviceProperties. When I inject DeviceProperties as <0900a53e>, it boot failed. config.plist Edited November 21, 2019 by zzz3z Link to comment Share on other sites More sharing options...
nmano Posted November 21, 2019 Share Posted November 21, 2019 (edited) Hi All X99 System Still PCI Configuration begin Edited November 21, 2019 by nmano Link to comment Share on other sites More sharing options...
pitrysha Posted November 21, 2019 Share Posted November 21, 2019 Did you assemble OpenCore according to the instructions? Are all traces of CloverBootloader deleted? Added EC0 RTC0 SMBUS SSDT? In the download you can see FakeSMC Clover EFI 1 Link to comment Share on other sites More sharing options...
nmano Posted November 21, 2019 Share Posted November 21, 2019 (edited) 3 hours ago, pitrysha said: Did you assemble OpenCore according to the instructions? Are all traces of CloverBootloader deleted? Added EC0 RTC0 SMBUS SSDT? In the download you can see FakeSMC Clover EFI Clover work good.I try OC. can you make sample EFI for X99 Thank you. Edited November 21, 2019 by nmano Link to comment Share on other sites More sharing options...
nmano Posted November 21, 2019 Share Posted November 21, 2019 (edited) I can 100%confirm open core kext patch not work. Kernel->patch->5960X patch-not work Edited November 21, 2019 by nmano Link to comment Share on other sites More sharing options...
birdbird Posted November 22, 2019 Share Posted November 22, 2019 (edited) Is there a resource describing what settings OpenCore needs for SIP/CSR on Catalina? My understanding was that OpenCore allows running full SIP while loading kexts via Lilu. Is this true? Did this change with Catalina? Thanks in advance. Edited November 22, 2019 by birdbird Link to comment Share on other sites More sharing options...
canyondust Posted November 22, 2019 Share Posted November 22, 2019 1 hour ago, birdbird said: Is there a resource describing what settings OpenCore needs for SIP/CSR on Catalina? My understanding was that OpenCore allows running full SIP while loading kexts via Lilu. Is this true? Did this change with Catalina? Thanks in advance. That is true. I’m injecting kexts with OC in high Sierra with SIP fully enabled. 1 Link to comment Share on other sites More sharing options...
birdbird Posted November 22, 2019 Share Posted November 22, 2019 21 minutes ago, canyondust said: That is true. I’m injecting kexts with OC in high Sierra with SIP fully enabled. Well it's good to know what I don't have to try to fix! Now if I only knew why the audio isn't working, lol Uh, now it seems like I'm booting to black screens for some reason... that and occasional kernel panics... odd. Also, it seems the that either the Marvell "GSATA" chipset or the Windows SSD attached to it were the cause of the horribly long wait for the boot screen. Are there resources on how to research/report this? Link to comment Share on other sites More sharing options...
Recommended Posts