npolite Posted February 18, 2021 Author Share Posted February 18, 2021 I had pulled the drive since the one I currently have was Mojave. I thought that was an issue. I can't get the installer to work without a drive? I just wanted to get into the GUI to see if it works before swapping the drive. Link to comment Share on other sites More sharing options...
Moderators Jake Lo Posted February 18, 2021 Moderators Share Posted February 18, 2021 When I said not detecting drive, I meant the USB installer. Did you try the new Config file? Link to comment Share on other sites More sharing options...
npolite Posted February 18, 2021 Author Share Posted February 18, 2021 Trying now. Will update in a few minutes. Here is the latest. Link to comment Share on other sites More sharing options...
npolite Posted February 20, 2021 Author Share Posted February 20, 2021 Is it possible that the two bootloaders somehow are running simultaneously and causing the booting issue for the installer? The reason I ask is because while I have been trying some different configurations, I have not touched my original Clover bootloader for Mojave since I installed it. Verbose was turned off. Now when I boot Mojave it is showing the verbose. Something in one of the USB bootloader is causing changes to the Mojave installer. Link to comment Share on other sites More sharing options...
Administrators Hervé Posted February 20, 2021 Administrators Share Posted February 20, 2021 No, that's impossible. What you're dealing with is NVRAM. Link to comment Share on other sites More sharing options...
npolite Posted February 27, 2021 Author Share Posted February 27, 2021 Still not sure what is going on. I was able to use this EFI for a 5430 and was able to install Big Sur installed. I was even able to get this to boot and at least sound is working. The only problem is that the system is really slow. I then over-wrote the EFI that was updated by Jake and it doesn't seem to work. If anyone is able to see what might be causing the slowness I can try to edit the 5430 and see if I can get further. Thanks Link to comment Share on other sites More sharing options...
Administrators Hervé Posted February 27, 2021 Administrators Share Posted February 27, 2021 Obviously it's quite a bad idea to use the EFI folder of an Ivy Bridge laptop on a Haswell one. So don't. Not the same chipset, CPUs, CPU power management, etc. Link to comment Share on other sites More sharing options...
npolite Posted February 28, 2021 Author Share Posted February 28, 2021 I tired a E6540 EFI and while I was able to get the installer working, when it tries to go into the first bootup, the screen goes dark. I can hear Siri so it seems that it is in. I checked the config.plist and see the correct value of 0600260A which is needed for my i5 Haswell. Can someone review my config.plist in this EFI and see what could be wrong? EFI.zip Link to comment Share on other sites More sharing options...
Administrators Hervé Posted February 28, 2021 Administrators Share Posted February 28, 2021 Could gain from clean-up. Patched DSDT already injects all graphics properties in a XDSM method so why do you re-inject in OC config? Patched DSDT already contains a PNLF device so why use a SSDT-9 (strange name by the way) to inject PNLF? Patched DSDT contains an EC device (for PNP0C09) so why inject the SSDT-EC? Don't use FakePCIID_Intel_HDMI_Audio; it's deprecated and you already inject Lilu + AppleALC. No need for AICPUPM patch on a Haswell platform; that patch is for Sandy Bridge and Ivy Bridge platforms only. Using OCC app, reselect MacBookPro11,1 profile to regenerate SMBIOS. You probably should try without your patched DSDT, I think it clashes with the rest of your OC setup. Link to comment Share on other sites More sharing options...
npolite Posted February 28, 2021 Author Share Posted February 28, 2021 Thanks for the help. Not sure if I got everything you mentioned (I don't know a lot about this). When I booted up I am not getting "Couldn't alloc class AppleIntelpchseriesahci" Attached is my updated EFI Edit: I tried the patched CtlnaAHCIPort.kext but still getting the same error message. E5540_2020_02_28-1.zip Link to comment Share on other sites More sharing options...
Recommended Posts