Hervé

OS X/macOS is not based on Linux and what you report is not a general issue affecting all Dell laptops. Did you try optional boot-args such as igfxonln=1 ? In all likelihood, this black screen on wake problem may be solved with some ACPI battery patch. Impossible to say more without any debugging info...

Post a zipped copy of your bootloader's EFI folder.

7th beta released September 21st, 2021. Build 21A5522h. Warning: the update will not go through on most people's Hack and will end up in an infinite boot loop unless SMBIOS is changed to that of specific Mac models. I do not have a list of SMBIOS with which the update goes through but iMac17,1 certainly is one. SMBIOS that do not allow the update to go through include: MBP11,x / MBP13,x / MBP16,x. After rebooting Monterey beta6 with iMac17,1 SMBIOS, I was able to complete the update on my Latitude E7270 (Clover r5133) and my Toshiba Satellite Pro R50-B (OC 0.70). Switching back to MBP13,1 and MBP11,x after the update caused no adverse affect to Monterey beta7. This beta7 also appears to sign the death of nVidia cards. GeForce and NVDA kexts are gone, meaning end of native support for Kepler GPUs.

Instructions are available in the Dortania OpenCore guide: https://dortania.github.io/OpenCore-Install-Guide/

The OC EFI I posted for the Vostro 200 is for a Core2Duo Vostro 200, not for a Sandy Bridge Optiplex 790. It's totally different hardware with nothing in common and certainly not the patched DSDT so you simply cannot re-use the OC Pack I had posted.

Well, the guide does stipulate that you 1st have to ensure you have (emulated) NVRAM working; if you do not, that command will be useless. You also have to make sure that your OpenCore setup does boot macOS; Catalina to begin with (as precaution) then Big Sur.

Clover r5139 is just as good. I've in fact updated just a few days ago after running on r5133 for months.

Looks like your USB installer is not bootable. Was the key formatted HFS, APFS or FAT32. How did you install Clover, with what selected options/settings? Edit: with regards to formatting the EFI partition FAT32, the Clover instructions have always worked for me:

I run Big Sur with OpenCore on my old C2D Vostro200 which is limited to legacy BIOS mode. You may refer to my Big Sur guide for reference on the OpenCore setup for desktop in legacy mode. https://osxlatitude.com/forums/topic/11148-dell-vostro-200-st-with-c2d-e8600xeon-x5270-geforce-gt730gt1030-high-sierramojavecatalinabig-sur/?do=findComment&comment=106757 This being said, the Optiplex 790's documentation clearly indicates UEFI BIOS mode is available so you should use that for both Clover and OpenCore. See p56 of the Optiplex 790's owner manual. This, unless you cannot boot a USB installer key in UEFI mode, something I experienced on Sandy Bridge Latitude E6220 laptop.

If it's a connected TV, go to Netflix directly on to and you'll probably get 4K.

There are DRM and browser issues to take into consideration. For many Hackintosh users, Netflix only streams out SD, not even HD! Safari usually isn’t supported and Chrome can be problematic too, forcing people to switch to alternatives such as Firefox or others. Did you consult the WhateverGreen documentation and/or use the shikigva boot arg?

Sorry but fix what? What's the problem?

The reverse works fine too. Just make sure you're on a full GPT partition scheme. On my Toshiba laptop, I installed macOS with OC on a disk with an existing Win10 installation and never lost anything. As long as you follow the recommendation/guidance (cf. Dortania OpenCore guide), you'll be Ok.

That's always a challenge. It's a TB3 port, right?

Dell Latitude E7270 (PCIe v3.0 x2 M.2 slot) with Toshiba RC100 M.2 2242 240GB NVME SSD (Gen3.1 x2)

Ok, things are a lot clearer to me now; what you described is 100% Ok and what I had written about the partition format can be ignored, it's obviously irrelevant. The name of your target partition induced me into error and I mistakenly thought you were making a fresh installation on a new "BS-SSD" partition from Catalina running on "CL-SSD". Indeed, having booted a separate Catalina build from the "BS-SSD" partition, I too would have expected the Big Sur installer to proceed as usual, except it may not like/accept your active SMBIOS because it's an upgrade, not a fresh installation. Try switching to a supported SMBIOS before running the Big Sur installer again from Catalina. To be honest, I can't remember doing this when I upgraded to Big Sur but it was version 11.1 back then, not 11.5.2 which may be less tolerant on that front. On the CPU power management front, does a table generated by Pike R Alpha's actually make any change? With Clover, you would probably notice better CPU power management with MacPro3,1 SMBIOS; I certainly do on my Vostro200 with the E8600 (and did too when I ran it with a Xeon X5270). Now that Clover has matured a lot on the Big Sur front, I should probably try and get that old Vostro to boot Big Sur with Clover like several of my other Hacks.

-> moved to the Dell desktop support section since this thread is not a guide... Hi @macnb Usually, this error message is returned if the target disk/partition is not of the expected format type; if it's formatted APFS, try to re-format it HFS+ and vice-versa. With regards to the manner in which I installed Big Sur, I believe my Vostro200 guide is crystal clear: I updated my existing Catalina build/partition of the time. No patch of any sort was made to my Big Sur installer. You don't seem to have chosen that specific route so, once you get past the disk/partition format hiccup, I expect you may encounter further problems subsequently like the boot loop known-issue mentioned in my Vostro200 guide. Correct me if I'm wrong but you do not appear to be upgrading your Catalina installation; instead, it looks like you run the Big Sur installation package from Catalina to build a fresh Big Sur installation on a dedicated separate partition. As explained in my Vostro200 guide, this does not work on legacy BIOS systems. You have to actually upgrade an existing Catalina build as detailed in my Vostro200 guide. If you wish to retain your existing Catalina build, I suggest you 1st make a temporary new Catalina installation on your target Big Sur partition and then upgrade that Catalina build to Big Sur. You may install 11.5.2 whilst retaining the SMBIOS of an unsupported iMac alongside the -no_compat_check boot arg. However, you won't be able to subsequently receive Big Sur updates as this requires the SMBIOS of a supported model. I therefore suggest you create a separate config with, say, iMacPro1,1 SMBIOS for the sole purpose of updates. For daily use you may return to iMac14,2 SMBIOS but it's of little/limited use given that OpenCore does not support CPU power management for these kind of Wolfdale/Harpertown C2D/C2Q/Xeon CPUs (no generation of P-States/C-States, unlike Chameleon/Clover). This is the sort of things I do on the Vostro200: SMBIOS iMac10,1 or MacPro3,1 for daily usage and iMacPro1,1 to update Big Sur. You're using old boot arg kext-dev-mode=1; most people still ignore that this was only ever required for Yosemite and has been of absolutely no use in subsequent OS X/macOS versions ever since. You can get rid of this but, of course, this deprecated boot arg causes no harm whatsoever.

You mean a macOS USB installer, right? https://manjaro.site/create-macos-big-sur-usb-installer-on-ubuntu/

When considering installing macOS on a PC, the 1st and essential step is to fully identify the hardware; that's what the Dortania guidance refers to as "Know your hardware". Ok for your audio codec (Realtek ALC255) and wireless card (Intel Wireless-AC 3160) but you need to identify the exact nature/model of Touchpad (Alps, Elan, Synaptics, etc.) and Ethernet/LAN controller (Realtek is just the manufacturer). This is mandatory to subsequently select the appropriate drivers. Various ways to achieve this: consult the manufacturer's documentation, including driver information Windows Device Manager (to identify Vendor + Device ids of hardware components) report from hardware information/auditing tools (such as DxDiag or otherwise) This being said, note that this Broadwell laptop is perfectly capable to run all recent versions of macOS. Most components are compatible but some may not be or may not be useable. I'm thinking especially about the nVidia GeForce 920M dGPU which, although compatible on paper since it's built on a Kepler chipset, may not be used (eg: possible black screen when running only on dGPU, no support for Optimus under macOS). We have a fairly detailed Hardware Technical Info section, it should be most useful that you consult it for guidance. With regards to creating a macOS USB installer, you'll find thorough details in all the recent installation guides we've posted in our Guides section (it's dedicated to that purpose and only to that). If you do not have access to a Mac or a Hack, you may consider building your USB installer from a VM or from Windows; You'll find info on the latter in our FAQ section which I invite you to consult to begin with. Finally, there are existing threads about that Inspiron 15 5558 model in this very section; I invite you to consult them too.

Can confirm this mod brings native support for 4K on the E7270 too. I'm using Clover so a simple cancellation of the fbmem/stolenmem iGPU properties injection from the Options menu was sufficient for testing. Here's 4K@60Hz out of 4K-capable miniDP-to-HDMI adapter (non 4K-capable miniDP adapters or cables only support FHD 1920x1080 res): Here's 4K@24-30Hz out of HDMI: NB: Ignore the SwitchResX stuff, it's leftover from previous attempts to get 4K running.

Nope, what you get/see is perfectly normal. Mainstream multi-core CPUs have always been reported as single CPUs with n cores, something that totally reflects the hardware. Here's my own i7-based E7270 SysInfo: In no way does "dual-core/4 threads CPU" mean 2 x processors and 4 cores; you misunderstood things.

What do you mean by "only boots for around 5-6mins"? Does the computer: complete the boot, reach the macOS desktop and then fail/crash/freeze after 5 to 6 mins? fails to complete the boot after waiting for 5 to 6 mins? Please describe the issue in details. Logs, copy of bootloader EFI folder, details of last action before the problem 1st occurred, etc. would be most useful if you want any sort of troubleshooting and assistance.

Yes, you're not the 1st one to report such behaviour with OpenCore; afaik, no such issue with Clover for what it's worth... But there's a good chance behaviour is linked to the value assigned to Scan Policy parameter. There's quite a lot of existing discussion on that kind of matter on various Hackintosh forums, especially at IM.

Could be a issue with the BIOS not being properly configured for macOS. Try and check that with those who hacked their 7530. Ideally, a dedicated thread on the matter would be great for the benefits of everyone.

So the culprit was AirPortBrcmFixup then; good to know the issue is fixed with a newer version. I saw it also fixed a similar issue with a BCM4352 card in another Hack of yours. I never used that Lilu PlugIn with my DW1820A cards; never needed it and, as stated in my BCM4350 guide, when I tested the card with that kext, I always experienced slightly degraded performance.