princerock 0 Posted January 19 Share Posted January 19 Trying to install OC Big Sur on my E7440. First I followed the OC guide and created SSDT patches and config.plist manually. Got kernel panic and it doesn't launch the installer. Then I tried Jake's files from this post: No kernel panic and installer started. I want to find out what the differences are. I noticed the SSDT patches are quite different. For example, for CPU management Jake's patch has the following code: DefinitionBlock ("", "SSDT", 2, "CORP", "CpuPlug", 0x00003000) { External (_SB_.PR00, ProcessorObj) Scope (\_SB.PR00) So the CPU name is \_SB.PR00. However when I checked on my E7440 the CPU name is PR_.CPU0. Other SSDT patches have similar name discrepancies. I thought my names are right, yet my installer doesn't even start, while Jake's files are working out-of-box! My questions are: Are there any patch/code that is renaming all the devices? Or does my E7440 just have different BIOS names (maybe due to different BIOS versions)? I'm still trying to find out what the differences are between Jake's files and mine, but this first question really baffles me. Thanks! Quote Link to post Share on other sites
Moderators Jake Lo 1735 Posted January 19 Moderators Share Posted January 19 Post your files Quote Link to post Share on other sites
princerock 0 Posted January 20 Author Share Posted January 20 Jake, Attached are my files. Thank you! Quote Link to post Share on other sites
Moderators Jake Lo 1735 Posted January 20 Moderators Share Posted January 20 CPU0 is correct. Not sure how I end up with PR00. If you encounter KP, it might be due to somewhere else, not SSDT-Plug. What error are you encountering with your files? Try this version SSDT-PLUG.aml.zip Quote Link to post Share on other sites
princerock 0 Posted January 20 Author Share Posted January 20 Hi, Jake Thank you so much for checking my files! Attached is what I get when using this EFI. Not sure which one of the two is the real problem. Your files don't have these issues and can launch the installer. I found there is another name difference in SSDT-HPET.aml. I used SSDTTime to create this SSDT and the device name is (confirmed by manually checking the device manager as well): \_SB.PCI0.LPCB.HPET Your file has a slightly different name: \_SB.PCI0.LPC0.HPET For SSDT-EC.aml, I found my E7440 already has the correct name. Based on the OC tutorial it says: "PNP0C09 already named EC Congrats! No need to create an SSDT-EC! However you will still want USBX if you're Skylake or newer." Therefor I didn't insert a SSDT-EC.aml. Is this correct? Thanks, Quote Link to post Share on other sites
Moderators Jake Lo 1735 Posted January 21 Moderators Share Posted January 21 EC is actually ECDV in DSDT.aml, so it needs the rename and SSDT-EC.aml. I've made the changes using SSDTTIme to generate new files from the latest BIOS. New bootpack has been added to the guide. Quote Link to post Share on other sites
princerock 0 Posted January 21 Author Share Posted January 21 Thank you, Jake! I will check them out. Quote Link to post Share on other sites
princerock 0 Posted January 27 Author Share Posted January 27 Hi, Jake Your bootpack works great! Thank you again for fixing the files. Regarding the config.plist: Are all the entries in DeviceProperties->Add needed? Are they the same for all E7440 laptops or is there a way to create them for mine? Thanks, Quote Link to post Share on other sites
Moderators Jake Lo 1735 Posted January 27 Moderators Share Posted January 27 No, most are just for cosmetics exported from Hackintool.app under PCIe. You can export them from your system and replace into the Config, but make sure to keep the following which is pretty much all you need really: Audio // optional - can be left out too and only use alcid=12 as bootarg is enough Video Wifi //can be left off too if you have different wifi, mine is customized for DW1550 SDCard Basically anyone that has 'compatible' in it, should be saved, other than Video and Audio. The rest can go Quote Link to post Share on other sites
princerock 0 Posted January 27 Author Share Posted January 27 Great! Thanks, Jake. Just realize I get white noise with headphones. I've already used CodecCommander.kext. I only have layout-id listed in my Device Properties though. Maybe I need to add other entries too. Or is there something else that can affect this? The HDMI audio works fine. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.