Jump to content
WarDoc

WhatEverGreen Support Topic

1,037 posts in this topic

Recommended Posts

what about playing Netflix on safari? do you see black window s+ green artifacts? while it's playing fine on firefox for example. obviously using Shiki + lilu

disable iGPU or use shiki.kext with shikigva=1 boot argument to use online render instead of offline.

Share this post


Link to post
Share on other sites
Advertisement

Hi I have an AMD 580 8 GB running with WhateverGreen.kext 1.04 and Lilu.kext 1.17 on Sierra 10.12.6

It is running fine. No Clover injection or anything else on Z270X-Gaming 5 Gigabyte mobo.

 

Now I want to add another 580 8 GB and then OSX just won't boot.

BIOS, Clover and OSX starts fine but when it comes to sending signal to screen it stops and ends with almost black screen.

 

Does anyone has an idea how to fix this? Or point me to an direction?

I have searched myself but can't find anything yet.

 

Using Clover_v2.4k_r4200

 

Thanks!

Got this thing running on High Sierra with Whatevergreen and Lilu and SMBIOS MacPro 6.1

Runs fine and all 36 units running. Have to do some real life test but I consider this as solved.

Thanks!

Share this post


Link to post
Share on other sites

disable iGPU or use shiki.kext with shikigva=1 boot argument to use online render instead of offline.

thank you for the tip.

I cannot disable igpu because I need quick sync.

tried with shikigva=1 and this is result: Netflix gives me error and now even youtube video have problems with green artifacts.

 

​that's strange because I was used with Sierra + Nvidia pascal to have Netflix working with same config.plist and same kexts combo

Share this post


Link to post
Share on other sites

thank you for the tip.

I cannot disable igpu because I need quick sync.

tried with shikigva=1 and this is result: Netflix gives me error and now even youtube video have problems with green artifacts.

 

​that's strange because I was used with Sierra + Nvidia pascal to have Netflix working with same config.plist and same kexts combo

did you install the supplemental update for High Sierra?

since this update Netflix don't work anymore and with iGPU get the green artifacts but only on Netflix.youtube works good and iTunes works fine without shiki.kext used the Offline decoder.

I don't no if it's possible to fix the green artifacts by patching the AppleGVA.framework via shiki.kext or so.

Share this post


Link to post
Share on other sites

did you install the supplemental update for High Sierra?

since this update Netflix don't work anymore and with iGPU get the green artifacts but only on Netflix.youtube works good and iTunes works fine without shiki.kext used the Offline decoder.

I don't no if it's possible to fix the green artifacts by patching the AppleGVA.framework via shiki.kext or so.

 

yes, I did the supplemental update.

and now, even my photo app get my hack freezing, like steam game app.

I get green artifacts when using shikigva=1, otherwise youtube runs perfectly.

​I can play Netflix well with firefox. issue only with safari

Share this post


Link to post
Share on other sites

Amazing it slept! Of course I want to see more, here is the faq bit im interested in:

 

How do I get HDMI audio to work?

In general it should be enough to rely on WhateverGreen automatic HDAU correction. It renames the device to HDAU, and injects missing layout-id and hda-gfx (starting with onboard-2) properties. This will not work well with two or more cards of different vendors (e.g. NVIDIA and ATI/AMD), please manually inject the properties in such a case. For identifiers not present in AppleHDAController and AppleHDA you have to add necessary kext patches, see AppleALC example for 290X

 

It's not worked. There is no nvidia card btw. Is it because of the already present dsdt edit for hdmi audio? Need I remove that or the latter here identifiers not present? How does one go about getting that going through clover injection? I may find the parts for the kexts but not sure on clover.

Share this post


Link to post
Share on other sites

Is device id 0x67C7 supported by Apple? It’s the Radeon Pro WX 5100 and a Polaris 10 spec card with less stream processors. Similar to the Radeon Pro 570. I see the WX 7100 in the whatevergreen code, but not the WX 5100. (I have the card btw if I need to test anything). If it does not work, I'll order a WX 7100.

 

More Info Bios

More Info General

 

 

//Edit

 

I tried with lilu and whatevergreen but it's not recognized. The device id is in AMDRadeonX4250.kext listed though.

 

Got it working by adding device id '67C0' as mask 'device-id' in a ssdt.

 

 

post-18792-0-09806200-1507621628_thumb.png

Share this post


Link to post
Share on other sites

Hi everyone,

 

I've just installed High Sierra on my hackintosh yesterday and everything seems to be working fine except for the fact that I can't get DVI output on my ASUS Radeon HD 7770 2GD5. HDMI works fine (I can't test the DisplayPort output because I don't have a DP cable lying around) but both DVI ports give me a black screen. The monitor is detected properly by macOS, but nothing is displayed, even if I boot with a single monitor plugged into the DVI port.

 

I have Lilu 1.2.0 and WhateverGreen 1.1.0 installed. Any ideas?

Share this post


Link to post
Share on other sites

Hi everyone,

 

I've just installed High Sierra on my hackintosh yesterday and everything seems to be working fine except for the fact that I can't get DVI output on my ASUS Radeon HD 7770 2GD5. HDMI works fine (I can't test the DisplayPort output because I don't have a DP cable lying around) but both DVI ports give me a black screen. The monitor is detected properly by macOS, but nothing is displayed, even if I boot with a single monitor plugged into the DVI port.

 

I have Lilu 1.2.0 and WhateverGreen 1.1.0 installed. Any ideas?

 

Try -raddvi, connector-priority, etc... Read the FAQ, read this topic...

Share this post


Link to post
Share on other sites

well initially sleep worked but nothing really changed except after trying out that example ssdt for r9 290x, it doesnt anymore.

made sure to remove all traces of it and the settings are the same as when sleep worked but it doesnt. This is an r9 290 and

have tried turning off the framebuffer "radeon" and removing the fakeid for sleep but that didnt help.

 

was also wondering if since the setup is using 10.11.6 that the hdmi audio does not work?

 

edit: ok i saw in the confirmation post it was 10.12.6/13 that the r9 290x worked with hdmi audio.

 

Still not sure what happened to the sleep all of a sudden... it worked the 1st time then stopped till the kexts went into 

"other" and was consistently working but not after trying that ssdt. now im stumped.

 

debug results in mostly this:

 

 cat /var/log/system.log | egrep '(WhateverGreen|Lilu)'

Oct 10 23:17:41 localhost kernel[0]: calling mpo_policy_init for Lilu

Oct 10 23:17:41 localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.1.7 (Lilu)

Oct 10 23:17:41 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.kext.AMDLegacySupport

Oct 10 23:17:41 localhost kernel[0]: Lilu: api @ failed to load com.apple.kext.AMDLegacySupport kext file

Oct 10 23:17:41 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.driver.AppleIntelKBLGraphicsFramebuffer

Oct 10 23:17:41 localhost kernel[0]: Lilu: api @ failed to load com.apple.driver.AppleIntelKBLGraphicsFramebuffer kext file

Oct 10 23:17:41 localhost kernel[0]: Lilu: patcher @ lookup patching applied only 0 patches out of 2

Oct 10 23:24:03 localhost kernel[0]: calling mpo_policy_init for Lilu

Oct 10 23:24:03 localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.1.7 (Lilu)

Oct 10 23:24:03 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.kext.AMDLegacySupport

Oct 10 23:24:03 localhost kernel[0]: Lilu: api @ failed to load com.apple.kext.AMDLegacySupport kext file

Oct 10 23:24:03 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.driver.AppleIntelKBLGraphicsFramebuffer

Oct 10 23:24:03 localhost kernel[0]: Lilu: api @ failed to load com.apple.driver.AppleIntelKBLGraphicsFramebuffer kext file

Oct 10 23:24:03 localhost kernel[0]: Lilu: patcher @ lookup patching applied only 0 patches out of 2

 cat /var/log/system.log | egrep '(AppleALC|Lilu)'

Oct 10 23:17:41 localhost kernel[0]: calling mpo_policy_init for Lilu

Oct 10 23:17:41 localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.1.7 (Lilu)

Oct 10 23:17:41 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.kext.AMDLegacySupport

Oct 10 23:17:41 localhost kernel[0]: Lilu: api @ failed to load com.apple.kext.AMDLegacySupport kext file

Oct 10 23:17:41 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.driver.AppleIntelKBLGraphicsFramebuffer

Oct 10 23:17:41 localhost kernel[0]: Lilu: api @ failed to load com.apple.driver.AppleIntelKBLGraphicsFramebuffer kext file

Oct 10 23:17:41 localhost kernel[0]: Lilu: patcher @ lookup patching applied only 0 patches out of 2

Oct 10 23:24:03 localhost kernel[0]: calling mpo_policy_init for Lilu

Oct 10 23:24:03 localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.1.7 (Lilu)

Oct 10 23:24:03 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.kext.AMDLegacySupport

Oct 10 23:24:03 localhost kernel[0]: Lilu: api @ failed to load com.apple.kext.AMDLegacySupport kext file

Oct 10 23:24:03 localhost kernel[0]: Lilu: patcher @ failed to init MachInfo for com.apple.driver.AppleIntelKBLGraphicsFramebuffer

Oct 10 23:24:03 localhost kernel[0]: Lilu: api @ failed to load com.apple.driver.AppleIntelKBLGraphicsFramebuffer kext file

 

Oct 10 23:24:03 localhost kernel[0]: Lilu: patcher @ lookup patching applied only 0 patches out of 2

 

Maybe its the igfx needs load first but this processors igfx causes clover not to load in this case maybe try with supported igfx?

Share this post


Link to post
Share on other sites

Try -raddvi, connector-priority, etc... Read the FAQ, read this topic...

 

I hadn't noticed connector-priority, and I'm not sure how to use/apply it. I tried adding -liludbg, -liludbgall, and -raddbg to see what the default value is in while booting but I'm not seeing anything and I can't find the boot log anywhere on my computer. I'm using CloverConfigurator because I'm quite new to this. How would I go about defining something in connector-priority?

Share this post


Link to post
Share on other sites

I hadn't noticed connector-priority, and I'm not sure how to use/apply it. I tried adding -liludbg, -liludbgall, and -raddbg to see what the default value is in while booting but I'm not seeing anything and I can't find the boot log anywhere on my computer. I'm using CloverConfigurator because I'm quite new to this. How would I go about defining something in connector-priority?

 

Try to read this topic carefully. It's only 14 pages. I already explained how to do this. 

Share this post


Link to post
Share on other sites

Hi @vandroiy2012

 

I'm just curious Is it possible to use lilu and whatevergreen on older hardware to boot into High Sierra? I tried and it will give me the black screen. I remember I've read about not using these kexts on older hardware in the read me on the whatever green on git hub.

They work fine on Sierra though.

 

My rig is: GA-EP45, Core 2 Duo E8400 and the GPU is Sapphire Radeon HD 7790 Dual-X 1GB.

 

Thanks for you support and your time man :)

Share this post


Link to post
Share on other sites

Hi @vandroiy2012

 

I'm just curious Is it possible to use lilu and whatevergreen on older hardware to boot into High Sierra? I tried and it will give me the black screen. I remember I've read about not using these kexts on older hardware in the read me on the whatever green on git hub.

They work fine on Sierra though.

 

My rig is: GA-EP45, Core 2 Duo E8400 and the GPU is Sapphire Radeon HD 7790 Dual-X 1GB.

 

Thanks for you support and your time man :)

Sorry. I don't have non-uefi hardware for tests, but on applelife.ru several users gave positive reports with non-uefi rigs and WhateverGreen.kext.

Share this post


Link to post
Share on other sites

Sorry. I don't have non-uefi hardware for tests, but on applelife.ru several users gave positive reports with non-uefi rigs and WhateverGreen.kext.

Thanks for your quick reply and the tip, I will check applelife.ru to see how they did it :)

 

Cheers

Share this post


Link to post
Share on other sites

Try to read this topic carefully. It's only 14 pages. I already explained how to do this. 

 

I think I might actually be retarded; I don't know how I didn't see your previous answer on connector-priority. However, I had no luck playing around with that. WhateverGreen is properly detecting all the ports (DP, HDMI, DVI, DVI) but I tried all 24 possible combinations and I wasn't able to get anything out of DVI, and I know the changes were applying since when I checked the log the priority numbers changed. The system is properly detecting the card (AMD Radeon HD 7770, device ID 683D) and both monitors. I'm terribly confused.

 

Thanks for being so patient with me, and I'm sorry for being so dumb.

Share this post


Link to post
Share on other sites

I think I might actually be retarded; I don't know how I didn't see your previous answer on connector-priority. However, I had no luck playing around with that. WhateverGreen is properly detecting all the ports (DP, HDMI, DVI, DVI) but I tried all 24 possible combinations and I wasn't able to get anything out of DVI, and I know the changes were applying since when I checked the log the priority numbers changed. The system is properly detecting the card (AMD Radeon HD 7770, device ID 683D) and both monitors. I'm terribly confused.

 

Thanks for being so patient with me, and I'm sorry for being so dumb.

 

Did you try -raddvi bootarg?

  • Fixes transmitter/encoder in autodetected connectors for multimonitor support (-raddvi)

Share this post


Link to post
Share on other sites

On a R9 290. For arbitrary fake id I use the pci address but not sure what else. I try custom properties

 

key: fake id

 

value: 0x67B01002

 

then there is type.. string, data or number for that value

 

what does putting radeon in the frame buffer section in clover do since its not one?

 

not sure if this will help the situation. Does the debug info from post #261 give a clue to what the cause of 

inoperability is?

Share this post


Link to post
Share on other sites

On a R9 290. For arbitrary fake id I use the pci address but not sure what else. I try custom properties

 

key: fake id

 

value: 0x67B01002

 

then there is type.. string, data or number for that value

 

what does putting radeon in the frame buffer section in clover do since its not one?

 

not sure if this will help the situation. Does the debug info from post #261 give a clue to what the cause of 

inoperability is?

 

It should be like that

post-1069282-0-43637900-1507763273_thumb.png

 

Just copy it

		<key>Arbitrary</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>Inject AMD Graphics properties</string>
				<key>CustomProperties</key>
				<array>
					<dict>
						<key>Key</key>
						<string>device-id</string>
						<key>Value</key>
						<data>
						sGcAAA==
						</data>
					</dict>
				</array>
				<key>PciAddr</key>
				<string>01:00.00</string>
			</dict>
		</array>

About choosing correct PciAddr look here http://www.insanelymac.com/forum/topic/325987-whatevergreen-support-topic/?p=2489296

 

And obligatorily disable clover ATI injection!!!

Share this post


Link to post
Share on other sites

Yep. Tried connector-priority with and without raddvi, no change.

 

Does your mainboard UEFI-capable? Does your card have UEFI VideoBIOS? If both questions "yes" try to disable CSM and make PCIe graphics card primary. If first question "yes" and second "no" try to find way to flash UEFI VideoBIOS in your card. Search Google how to flash UEFI GOP in AMD videocards. If first question "no" you could try different VideoBIOSes even from another vendor. Just make sure that type and amount of connectors, video memory and GPU/Memory frequencies will be equal to your card.

 

That's all i can suggest you.  

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By eliot6001
      I don't know whether my LAN device will work on MAC and Which version of mac but i still want to run MAC on my PC, Also i checked my CPU-GPU and it turned out that i can Run MAX High sierra but i realized that some people have trouble with Sound and Internet connection so Here's the NAME of my LAN device:
       
      PCI\VEN_10EC&DEV_8136&SUBSYS_012310EC&REV_05\4&45F2A70&0&00E1 as (LAN DEVICE took the name from device manager in  windows). 
      also from compatibleIds i got this:
      PCI\VEN_10EC&DEV_8136&REV_05
       
      Is it Supported on any version of macOS ?
    • By Aldaro
      I have been running macOS Mojave on my system for 3 months and everything was working pretty well.  After taking an update for clover, my entire system got wrecked, and I cannot even boot to an installation environment anymore (which I really need to do since I am starting back at square one).  I still have the old EFI folder backed up, but I know it'll only be a matter of time before Apple introduces an update that requires me to update Clover in order to work correctly.  I have tried all the available memory fixes, but none of them seem to work.  I was previously using the original osxaptiofix; so, I gave v2, and v3 a try, but to no success.  I read somewhere on the main discussion board for clover that AptioMemoryFix was no longer going to be supported and I therefor decided to skip over it (not to mention it isn't even available in newer clover installation packages).
       
      System specs:
      Motherboard: GIGABYTE Z390 M GAMING
      CPU Intel core i5 9600k @ stock 3.7GHz
      RAM 32GB DDR4 2667MHz
      GPU AMD Radeon RX 580 with 8GB of GDDR5
      SSD Intel 660p 512GB NVME
      NIC: Intel i210 10/100/1000 as it is natively supported in macOS
       
      I have been using the iMac 19,1 SMBIOs as I built this machine to match it as close as humanly possible.  As for my UEFI settings, I did the usual:
      Disabled Windows specific features and secure boot
      Enabled XHCI hand off
      Enabled Above 4G decoding
      Disabled onboard NIC since it is made irrelevant by my intel i210
       
      --INJECT KEXTS--
      FakeSMC
      Lilu
      WhateverGreen
      AppleALC
      USBInjectAll -- WITH PATCHED SSDT in /EFI/CLOVER/ACPI/patched
      Below are images of the errors I am receiving when trying to boot the macOS Mojave installer.
       
      with original osxaptiomemoryfix

       
      osxaptiofixv2

       
      osxaptiofixv3

       
      Anyway, if somebody can help me figure out what's going on, that'd be greatly appreciated.  My ultimate goal is to get an install with minimal clover patches as to be better prepared when the winds of change from Apple come roaring.
       
      p.s: I have also attached a copy of my EFI folder
       
       
      EFI.zip
    • By kalpesh2804
      Laptop Inbuilt Wifi and Battery Indicator not working in Catalina. (HP Pavilion 15t-au 100 Laptop)
       
       
      Laptop Config:
      HP Pavilion 15t-au100 * i7-7500u 2.90Ghz * Intel HD 620 Graphic Adapter * Intel Dual Band Wireless AC-3168 * Kingston SATA3 SSD 500 GB * HP Camera
    • By fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au)
      MBR installation on macOS Catalina (thanks to crazybirdy) - workaround!!!
      Mac Downloader (thanks to ricoc90)
       
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
×