Hervé

@Nhật An Would you please detail what you did? Would be most useful for the community...

I experienced the same issue on a couple of my Hackintoshes (the Haswell Toshiba laptop and the old Penryn Vostro desktop): no update to Big Sur 11.2.1 offered on either system, despite using a Big Sur compatible/supported SMBIOS downloaded the 12GB Big Sur package from the AppStore on the Toshiba Hack and re-installed, only to end up with same 11.2 build 20D64 as before So, I started experimenting and, to me, it's related to OpenCore. I'm yet to establish whether it's related to the version of OpenCore, some incorrect settings in the config or some side effects from using OCC (or a mix of them all) but I can tell that the 11.2.1 update was offered to me on one the Haswell Toshiba Hack after reverting from OC 0.6.6 to OC 0.6.3. This is what I did: made a backup of active OC 0.6.6 EFI folder in the ESP took the original OC 0.6.3 EFI folder of my Ivy Bridge Latitude E6230 and replaced its ACPI tables + kexts by those required for the Toshiba Hack (as used with OC 0.6.6) replaced OCC v2.27.0.0 by v2.16.0.0 and adjusted the OC config with OCC to reflect what was required for the Toshiba laptop (ACPI/DeviceProperties/Kernel/PlatformInfo) as per what was used with OC 0.6.6 replaced the OC 0.6.6 EFI folder on the ESP of the Toshiba Hack by the modified OC 0.6.3 EFI folder (of E6230 origin) Rebooted into Big Sur 11.2 with this OC 0.6.3 setup and... Bingo! The update went ahead when I launched it and the Toshiba Hack is now running Big Sur 11.2.1.

Well done, I guess the boot arg was the key!

E6440 is fitted with Alps TouchPad that works perfectly with Dr Hurt's VoodooPS2Controller set of kext. Use version labelled R6 by Bronxteck as available in the dedicated thread in our R&D forum section.

For audio, just use AppleALC which is a plugin of Lilu. Look up the various layouts to try out on the AppleALC wiki and experiment. Google for AppleALC kext and you'll find all you need. You would only need to update Clover if you wanted, say, a bug fix or to run a more recent macOS version that requires a minimum version of Clover. Here too, you can look it up on the Web at places like Did's Github repo for instance.

1st of all, you should disable hibernation as explained in our FAQ section. 2nd, not much can be said without knowing the details of your setup (OS version, bootloader, zipped EFI folder, etc.)

New version v2.4 released. Aims to improve sleep/wake behaviour with RTS5227 reader.

https://osxlatitude.com/forums/topic/9966-how-do-i-disable-hibernation-for-sleep/?tab=comments#comment-71887

Nothing weird with having no Bluetooth working if that's what you meant. Would be a Qualcomm Atheros module too and those were also finicky when not plain unsupported. https://wikidevi.wi-cat.ru/Qualcomm_Atheros_QCNFA435 Replace that unsupported QCA card by a supported Broadcom model.

Correct. Maybe you can check if the freeze on wake still happens under 11.2 and OC. I suppose I'll have to try it out again with OC 0.6.6.

You're using an old Clover setup with old kexts and some incorrect settings, though none that would normally prevent proper macOS installation. Refresh all kexts to their latest versions.

follow the kextcache command with: sudo kcditto

Catalina now, so split to separate thread... I can't understand why your system would load (and crash) Broadcom wireless drivers when you stated you have an Intel wireless card in your Big Sur thread... If you want further assistance, please post a zipped copy of the EFI folder you use. Indicate which boot loader you use and which version.

As long as your i3 is fitted with HD4000 iGPU not HD2500, you're good to go up to current Big Sur. See our FAQ section re: making USB installer without a Mac or a Hack; then look up any existing guide for Ivy Bridge Latitude E5x30 or E6x30 laptops.

macOS normally runs perfectly and totally stable on these Broadwell laptops with all hardware fully supported.

Issues with disks in Media Bay have been discussed in the past, mostly for E6x30 if I recollect properly. Did you check these out? Basically, you need to patch AppleAHCIPort kext. You'll find details on the forum in threads such as these: https://osxlatitude.com/forums/topic/12639-solved-e6430-catalina-new-install-2nd-hdd-in-media-bay-not-readable https://osxlatitude.com/forums/topic/13202-solved-e6330-successful-upgrading-to-catalina-but-major-problems/ Can't say if the patch remains the same in Big Sur but look it up.

I don't usually use GB5 but I just got about the same results as you: 774 & 1703. I'm not sure there is much to say or conclude about those benchmarks. Here's what I obtained with GB4.4.4: Catalina/Clover: 3705, 7500 Big Sur/OpenCore: 3809, 7401 Big Sur/Clover: 3821, 7460 Strange about those graphics glitches you encounter in Mojave and Catalina. Not seen/experienced those. Did you have the Capri framebuffer memory patch in place? Anyway, water under the bridge if you're happy with Big Sur and it's fully functional with Clover

Can't see why the ALC293 audio of the E7450 wouldn't work with layout #11 like it does with ALC293 of the E7250. Try and add CodecCommander kext to work alongside Lilu + AppleALC. Make sure those are the latest versions too. Looking at your OC config, I see that you have arguable ACPI patches in place; for instance, you inject SSDT-EC.aml table (which is good) but you also apply the ACPI patch that renames device ECDV to EC; you should only use the former, not the latter which is now deprecated, especially as you end up with 2 x EC devices, so potentiel conflictual situation, wouldn't you say? Check your other ACPi patches too!

That statement in Dortania's documentation about OpenCore not needing a DSDT is a little confusing and misleading. Possibly something lost in translation as one may say... All bootloaders universally pull/read ACPI tables from BIOS (i.e. firmware). On paper, no Hackintosh bootloader needs a (patched) DSDT. It's just that over the years, ACPI patching developed greatly and what was done years ago through DSDT patching is nowadays done through dedicated SSDT patches that leave the loaded DSDT table more or less untouched. OpenCore came out at a time where such development had reached maturity, having already been vastly experimented and successfully used with Clover. That's for the story (or history)... Focusing back on the E6230, I detailed the patches implemented back in 2018 to A19's original DSDT in my E6230 BIOS settings thread, so you may indeed rework them out through SSDTs or pre-programmed patches of the bootloader. It wouldn't be too difficult, most of them are well known and documented. The only patch missing in that list for the brightness keys and details are available here, in my E7250 guide or here, in my 7490 guide (same patches applied throughout). Jake Lo has also published SSDT alternatives for this brightness keys patch. I was (and remain) too lazy to jump back into that and revisit, especially as Catalina or Big Sur work perfectly with my patched DSDT (even with OpenCore, Yes siree!). No issues and no worry to have on the matter.

Go back to the installer main screen and open up Disk utility to reformat your target partition HFS+, i.e. Mac OS Extended (Journaled). It can't be a new volume on an existing container, that only supports APFS format, it'll have to be a separate partition. Adjust your disk arrangement as required. Please note that, as stated in my guide, I reverted to Clover on what was an existing Big Sur installation made with OpenCore. I'm not 100% certain that you'll actually manage to complete a fresh Big Sur installation with Clover 5128 or r5129 (latter is also Ok to use and I've actually updated from r5128 to r5129). But give it a try, you'll soon find out. You say this is a fresh installation but you've actually downloaded Big Sur and initiated its installation from Mojave, not from a booted USB installer, haven't you?

As always, please post your detailed system's specs or add them in signature. We're in the dark without those! Difficult to make much out of those screenshots. KP seems to happen after "Still waiting for root device" which would suggest USB-related issue. You've placed USBInjectall in your kexts folder but you're not injecting it in your OC config, so... Please note that I'm pretty certain you're injecting the wrong ig-platform-id for your HD530 iGPU, usually it's just 0x19120000. You may refer to this InsanelyMac thread for reference. Injecting iGPU device-id may not be required either but it'll depend on the specifics of your CPU, so no further comment possible in the absence of detailed specs... I also suggest you follow the guidance posted at Dortania for Skylake desktop so that you have an ideally configured system. Good luck.

I'd say the boot loop may result from the known issue that usually only affects systems running in legacy BIOS mode only: missing UUID for temp installation volume in msu-product-url NVRAM parameter or missing parameter, presumably due to non-working NVRAM. It happened to me yesterday when updating my E6230 to Big Sur 11.2 and I messed up at some point with Clover. Various solutions: 1) fix NVRAM 2) manually inject the msu-product-url parameter in an NVRAM.plist file (very long shot; not sure that would work) 3) upgrade the existing Catalina installation following the process detailed here. Best thing to do is verify is that 1) your system runs in UEFI mode and 2) you have working NVRAM. Are you making a completely fresh Big Sur installation having wiped out your disk or or you upgrading your existing Catalina build? NB: can't understand why you downloaded Big Sur from a VM when you have Catalina installed.

Difficult to say much with so little information, including the hardware specs; "normal wifi card" is pretty meaningless... You should be using OpenCore current 0.6.5 version these days. Upgrade your E7450's BIOS to latest version if it does not already run it. Then reset BIOS settings to default and reconfigured along the lines of those I've described here for the E7250. @Jake Lo posted a fully detailed guide here; maybe you could have searched the forum before posting... His guide is based on OC 0.6.3 and 0.6.4 but you can re-use the settings (i.e. ACPI tables + kexts + config file) with OC 0.6.5. Consult Dortania's OpenCore documentation for detailed information on OpenCore. It's a must. Please note that once you initiate the Big Sur installation and system reboots, you must choose the temp "MacOS installer" (or whatever its name might be) partition/volume to complete the process until you're left with only the target partition you chose for Big Sur.

'remove the "boot flat" ? What's that? Or you meant the boot arg brcmfx-driver? Maybe your setup has other or conflicting arrangements somewhere for your wireless card.