Hervé

No, no, no, that won't work. 1st I don't even know why you'd use the El Capitan pack for Sierra but, most importantly, you just can't take a bootpack tuned for a Dell Latitude D830, apply it to a totally different computer and expect things to work. There's far too much stuff specific to the D830 in that pack that's neither relevant nor suitable for your Acer computer. I only made reference to the Dell guides for the general steps involved with regards to the installation process, not to use their bootpacks! Go for High Sierra and we'll try to work out a dedicated Clover pack for you. Do not use any Clover version from r5123 to r5126, these are troublesome.

You're gonna have to tell us more. You're trying to install Sierra but with what? What bootloader (Enoch? Clover?)? What pack? Can't see why you'd use boot arg nv_disable=1 on a laptop with a Tesla dGPU expected to be natively supported...

Don't hesitate to post your OpenCore EFI (Config, ACPI + kexts folders) for the benefit of the community.

MacBook9,1 SMBIOS + SKL framebuffer 0x191E0000 for Intel HD515 graphics, it would seem; correct ?

It would really be appreciated if people who use OpenCore would take the time to read the documentation posted at Dortania's. These people must have spent hours to write it and it is excellent. Common courtesy would be to refer to it.

Yes, see our FAQ section. To verify cache update, check presence of CodecCommander kext in Sysinfo->Software->Extensions; it should show there...

CodecCommander always required to be cached before, it never injected. Try to cache it from /L/E as per previous macOS versions.

I would never recommend nor encourage to use the patched DSDT of the E6230 on an E6530 nVidia. Quite the contrary. With regards to dead internal-USB devices or freezes upon wake, it's likely to be a consequence of inadequate settings on USB ports definition and associated power + side effect of injecting SSDT tables that may clash with patches present in the E6230 DSDT (EC, PNLF, etc.). I'm myself to post a further refined E6230 OC pack in the next few days, the aim being to get rid of the patched DSDT and use SSDTs only. I can have a look at your EFI folder & DSDT but I would need you to: run on latest BIOS post your extracted raw set of ACPI tables (the thing obtained by pressing [F4] at Clover main menu)

Looks more like a corrupt installation; try a fresh one on a separate disk or partition. Failing that, investigate eventual faulty hardware somewhere.

You meant Latitude 5480, right? If so, I don't believe anyone has found a solution to date.

Maybe, no way to say for sure.

Core2Duo P7350 is Penryn-3M and GeForce 9300M GS is Tesla G98. This kind of platform should fully support El Capitan but also Sierra and High Sierra since the CPU has SSE4.1 instructions set. I'd go for the latter. You could even push for Mojave with Tesla-specific special patches and Catalina with Dosdude1's patcher. You can read about those in our Graphics section. But that's maybe for a future stage as it gets a little complicated when High Sierra will fully and natively support your graphics card. Download a copy of High Sierra off Apple (via AppStore or Apple download links) and make your USB installer with basic settings. Look at "Our Picks" side panel on forum main page for that. You can look at fine tuning your build for Ethernet, wireless, audio, card reader, etc. once you've finished the macOS installation. You may consult these old guides for general guidance in the process; obviously the pack are not for you but you can extract the core kexts from them (FakeSMC, Lilu, WEG). https://osxlatitude.com/forums/topic/12479-dell-latitude-d630-with-core2duo-nvidia-quadro-nvs-135m-el-capitansierrahigh-sierramojavecatalina/ https://osxlatitude.com/forums/topic/10370-dell-latitude-d830-with-core2duo-and-nvidia-quadro-nvs-135m-mavericksyosemiteel-capitansierrahigh-sierramojave/ The one thing that will not be supported for certain is your Intel wireless card and it'll have to be replaced by a supported model. Plenty to choose from and you may consult our inventories published in the Wifi section to that effect. Good luck.

Big Sur brought significant changes to the way kexts operate with the kernel and further tightened filesystem protection. It's now most difficult for anyone to make any changes to /S/L/E folder. As such, kexts should be considered cacheable only from /L/E. To repair permissions after any any kext addition, removal or modification in /L/E, type the following Terminal commands: sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo touch -f /L*/E* ` To rebuild the cache, type the following Terminal commands sudo kextcache -i / -> will invoke the required kmutil command sudo kcditto For additional information on the commands: man kmutil man kcditto

Please consult the available documentation. Thank you.

No, E5550 is a Broadwell platform when your E5540 is a Haswell one. So they're of different chipset families, different CPU families, different iGPU families. As such, the EFI meant for an E5550 will contain configuration elements not suitable for your E5540 (graphics property injection SMBIOS, etc.) and your Hack would not work. On the other hand you can seek inspiration from existing packs and threads relating to other Haswell Latitude laptops such as the E6x40 or E7x40. By far and large, all these will share similar not to say near-identical configuration, the only differences being on the hardware accessories side (eg: LAN, audio, card reader, etc.). I strongly recommend you start here...

We'd all be grateful if you'd go easy on the permanent quoting; it really isn't necessary and quite messy. I gave you packs, obviously without the CPU PM ssdt since I could not guess what CPU you had. As clearly stated, they're not full OC EFI folders! If you tried to boot with nothing else, you indeed must have failed miserably... All you have to do is make your OC EFI folder following Dortania's current documentation and then, update it with the stuff in the packs I gave you. Then add your CPU PM ssdt and update the config accordingly. I thought it would have been common sense and easily understood. With OC 0.6.3, your default EFI updated with my pack's contents and SMBIOS MBP10,2, you'll be able to install Big Sur 11.0.1 as shown in my E6230 detailed guide. Good luck!

I can assure you that there is nothing in the kexts folder of the packs I posted that could be specifically for Clover. You know, kexts are the same whether you boot with Clover or OpenCore and the same goes for caching kexts from /L/E. On the other hand, the OC EFI you posted contains many incorrect items. ACPI: No patched DSDT. SSDT-EC which is Ok for older systems (up to Broadwell) such as your Ivy Bridge E6430. SSDT-EC-USBX which is for newer systems (Skylake and later) and therefore irrelevant for you. Delete this. SSDT-PM is for a quad-core i7-3740QM, I assume this is the CPU you have, therefore correct CPU PM SSDT; if not, you know the drill... Drivers: No need to include them all. You only need to use and declare those drivers you need: Audio (if you want startup chime), OpenRunTime, HfsPlus and, if you use the OC GUI, OpenCanopy. Kexts: Several conflicting drivers here... AirPortBrcmFixup vs. FakePCIID+FakePCIID_Broadcom_Wifi. Remove the latter 2, they've been kind of obsolete for some time now. USBPorts_E6430 vs. USBInjectAll. Remove the latter; it's either USBPorts or USBInjectAll+SSDT-UIAC (which you don't have). OC Config file: calls for a DSDT that's not there. does not call for the CPU PM SSDT that's in the ACPI folder. Therefore no CPU power management... Device Properties: injects correct properties for HiRes LCD but retains limitations to single display port (built-in LCD) only. Further properties are required if you want additional display ports, at least HDMI. Kernel: properly selects desired kexts and removes any contradictions mentioned above Drivers: setup only selects those you want but I don't know if you should have ApfsDriverLoader.efi rather than HfsPlus.efi. I actually wonder where your ApfsDriverLoader module is coming from. Clover? PlatformInfo: there is absolutely no reason why you would use the SMBIOS of Haswell MacBookPro11.1 when you should be using SMBIOS of Ivy Bridge MacBookPro9,2 or MacBookPro10,2. NVRAM: applies -igfxnohdmi. May be you want to revise this once you inject properties that'll support HDMI output. I can only suggest you use the packs I provided above given that current setup looks quite incorrect to me. A particular aspect to pay attention to is your CPU model and the CPU PM SSDT that you need to use or generate accordingly. I also strongly recommend that you post your E6430 specs so that we avoid wasting time on trying to provide assistance in the dark. It's highly desired to post such specs in signature...

You don't "patch ssdt". You generate your CPU-specific power management SSDT through well-known/good old Pike R Alpha's generator script. See here.

You have an i5-3340M but use the CPU power management SSDT generated for a quad-core i7-3630QM. remove that SSDT and generate your own one. remove that CpuTscSync kext too. It's not required. Adjust your OC config (Kernel section) accordingly. You'll find things will work much better afterwards...

I have repeatedly been able to install Big Sur on my E6230 with SMBIOS of unsupported MacBookPro9,2 and MacBookPro10,2 with -no_compat_check boot arg. The issue at hand must be something else. @leppy700m, post a zipped copy of your EFI folder so that we check it out. You may also refer to my E6230 guide for general guidance though I've left out some properties injection out of the OpenCore config given that they were already in the patched DSDT (ECDV->EC, EHCx->EH0x, IGPU properties, etc.). You may use these E6430 HD4000-only packs for your OpenCore setup; just copy the files and folders of the packs to the OC folder of your EFI partition/folder and replace any existing stuff. EFI_E6430_LoRes.zip EFI_E6430_HiRes.zip For an E6430 with nVidia graphics, enable Optimus in BIOS but disable the dGPU through DSDT/SSDT patching. JakeLo posted the necessary stuff in several E6x20/E6x30 NVS x200M threads. JakeLo will correct me if necessary. Meantime and/or in the interim, you may just boot with boot arg -wegnoegpu added to the NVRAM section. See here for more details.

What laptop? What setup? Please post a zipped copy of your OC EFI folder. Add your Hackintosh specs in signature.

@mefflecakes, Mario and I played on his Skylake Optiplex 7050 (i5-6600 CPU) with HD530 graphics. We 1st got HDMI + DP working with standard SKL platform-id 0x19120000, then HDMI+DP+DP, i.e. 3 x displays after injecting 4th connector 0306... Secret was to bypass restrictions imposed by AppleGraphicsDevicePolicy kext (a PlugIn of AppleGraphicsControl kext) with boot arg agdpmod=pikera. All details posted here.

LCDs with resolution up to 1440x900 require Capri platform-id 0x01660003 LCDs with resolution at or greater than 1600x900 require Capri platform-id 0x01660004 Other than that, outside the need to disable the nvidia dGPU (through a specific DSDT patch or, better, a specific SSDT), there should be no difference of settings to run any version of OS X/macOS supported on these laptops.

Graphics glitches affecting HD4600 usually are fixed by patching the Cursor Memory Size. By default, it is set to 6MB in platform id 0x0a260006 and needs to be changed to 9MB: framebuffer-cursormem 00009000 DATA See here as linked in the WEG manual. If you've not already done so, remember to disable your dGPU since it's not supported and will use battery power if left enabled/powered on...

Conflicting settings... IOReg shows you've injected Azul platform id 0x0a260005, which ain't really the expected value: (I'm also a little baffled by the 32bit ref in IORegistryExplorer status bar) This Azul platform injection is confirmed in your OC config in which you've also enabled your patched DSDT. In this patched DSDT, there is an XDSM method under the IGPU device in which HD4600 properties are injected, including the expected Azul platform id 0x0a260006! So choose the correct values and avoid mixing/duplicating things... If you inject properties through DSDT, don't redo it (and redo it with different values) in your OC config; and vice versa.