Hervé

What are the other specs? Wifi? Disk?

8th beta released September 28th, 2021. Build 21A5534d. As per beta7, I had to temporarily use SMBIOS iMac17,1 to complete the upgrade and avoid the boot loop problem. Other than that, all Ok on my Latitude E7270 (Clover r5133) and Toshiba Satellite R50-B (OC 0.7.0).

https://osxlatitude.com/forums/topic/16757-solved-opencore-gui-not-showing/?tab=comments#comment-111632

https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.Chart.md

It depends entirely on the configuration parameters you're using. Monterey does not natively/officially support HD4000 graphics and Ivy Bridge platforms were dropped. As such, you have to adjust your config with a supported SMBIOS and you'll subsequently have to apply patching to obtain support for HD4000 graphics. Can't say more without more info from you at this stage.

No DRM fix for Netflix with Safari on Hackintosh laptops with Intel graphics, no. https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.Shiki.en.md https://dortania.github.io/OpenCore-Post-Install/universal/drm.html On my Haswell or Skylake Hackintosh laptops, trying to view Netflix contents in Safari immediately results in a "Error code S7706" message. On my Ivy Bridge/HD4000 Latitude E6230 I can watch Netflix contents in Safari 14.1.2 under Catalina 10.15.7 (build 19H1417) or Safari 15.0 under Catalina 10.15.7 (build 19H1419) for just over 1 x minute before the screen goes green irrecoverably. This is something Shiki used to be able to fix but it has not been the case for years. Apple TV works ok for watching movies. Certainly works on all my Ivy Bridge/Haswell/Skylake Hackintosh laptops. TV+ or TV Shows won't though.

Your screenshot shows that macOS is not even starting to load... You need to update your OC config so that it matches the v0.7.3 standards and requirements. That's the trouble with OpenCore, they change the way parameters and elements of the config must be defined and organised from one version to the other. Given that they release a new version every month, it can be a pain in the backside... There are threads at InsanelyMac that provide full recap of what's changed from version n to version n+1. I suggest you consult them all so that you suss out what you need to modify in your config. Do follow the monthly updates posted at Dortania too. https://www.insanelymac.com/forum/782-opencore-releases/ https://dortania.github.io

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/