Hervé

I understand that ALC3236 codec is ALC233; look that up in the AppleALC wiki and experiment with the various layout ids listed. https://github.com/acidanthera/applealc/wiki/supported-codecs Re: AR9565 wireless, those were never natively supported and required a specifically re-written Atheros40 kext. Then, performance was not great. Knowing that you'll probably have trouble getting this card to work under Big Sur, it'd be far better to replace it with a fully supported M.2 model. You can check these out in our wireless cards inventories and our M.2 wireless cards inventory, all available in our R&D->Wireless section.

You're using an EFI made for a different model that may not have the exact same hardware specs as your own particular laptop. You need to identify your audio codec and specify the make & model of your wireless card. Don't hesitate to open up your laptop to look at the label of the wireless card. Failing that, post an IOReg extract saved from IORegistryExplorer app.

OCC app gets aligned with versions of OpenCore. So, you must have a mismatch between the version of OCC you used and the OpenCore version you've installed. In most case, these warnings can be ignored but OpenCore can be subject to updates that completely modify the way parameters are defined. In rare cases, you could find yourself in a situation where a config file updated through OCC would no longer allow you to boot OpenCore due to changes in the config that aren't supported by an older version of OpenCore. For instance a config updated by OCC for OC 0.7.0 when installed OpenCore version is, say, 0.6.3 or 0.6.5. If you don't update OpenCore, don't update OCC either. Keep them aligned. Right now, you should probably update OpenCore to 0.7.0/0.7.1 and OCC to the latest available version, v2.44.0 at time of writing. Then stop there.

Usually, I turn TPM & USB Wake Support off.

Glad to see that you got graphics acceleration after entering the suggested properties in the correct reverse byte order.

It's 1st beta and Bluetooth is buggy, even for real Macs. So guys, just be patient.

Remember to post your system's specs in signature.

What else? Please note, that as far as I can see, trying to enable HDMI2.0 on hardware limited to HDMI1.4 is most likely useless...

I would not compare the settings of 8th gen Kaby Lake Refresh 7490 with those of 10th gen Comet Lake 7310. By all means, do post the list of setting you use because we don't necessarily know what the 7310 offers (I certainly don't). After you make changes to your OC config, you clear NVRAM, right? Which version of Catalina are you trying to install by the way? From memory, Comet Lake and Ice Lake are only supported from 10.15.3 or 10.15.4. Check it out in the Software section.

Your E5550 is a Broadwell laptop. Given that the tool you've opted for does not seem to support Broadwell mobile platforms (it appears it skips those and only supports High-End Desktop (HEDT) 140W 6/8/10-core Broadwell-E platforms which the E5550 sure ain't based on). I would therefore recommend that you leave that tool aside for the time being and follow the Dortania OpenCore documentation to build your setup. You may use OpenCore Configurator app (aka OCC) to create your OC config. I also invite you to read the existing guides for E5x50 models published in our Guides section and the existing threads about installing and running Big Sur on to the E5x50 laptops in this very section. My final recommendation would be that, if you're totally new to OC, you stick to Clover for the time being (update to r5133 or later) and experiment with OC on an external drive. This so that you don't totally lose dual boot or find yourself stuck with the potential side effects of OC in Win10.

i7-10610U is Comet Lake (not Whiskey Lake) so I don't think you're injecting the correct properties for your CML iGPU fake id and FB layout; according to the WEG user manual and the Dortania OC documentation, you should be using: ig-platform-id 0x3E9B0000 device-id 0x3E9B

OCLP 0.1.7 patcher has been released. It brings support for HD4000 graphics in Monterey beta1. https://forums.macrumors.com/threads/macos-12-monterey-on-unsupported-macs-thread.2299557/post-30014550 Make sure to enable automatic login quickly after 1st boot setup to avoid subsequent problems with the Windows server/graphics initialisation and consequential inability to complete the boot and reach desktop. Tested on my Latitude E6230 on an external USB disk. Runs at much higher CPU speeds than before and therefore very hot at times. Will probably have to experiment with CPUFriend on that front. Probably why system is unstable and keeps crashing with sudden complete reset after a while.

Please post your system's specs in signature. Also, please refrain from using quotes to post replies. As per our published rules which I invite you to read, please use the Reply box at bottom of each page. Try SKL layout 0x1916 instead of 0x191b + SMBIOS MBP13,1 instead of MBP13,3 to see if it makes any difference.

These tools are made for real Macs so the process does not fully apply to Hackintoshes on which you would boot with a usual bootloader setup and then apply the patcher to your build.

Some people reported slow boot with beta1. 1st workaround is to enable automatic login. https://www.insanelymac.com/forum/topic/348065-pre-release-macos-monterey/page/10/?tab=comments#comment-2760529 https://www.insanelymac.com/forum/topic/348065-pre-release-macos-monterey/page/11/?tab=comments#comment-2760595 2nd workaround is to replace your account's picture by a Memoji. https://www.insanelymac.com/forum/topic/348065-pre-release-macos-monterey/?do=findComment&comment=2760673

Enable automatic login and report.

Impossible to provide any form of assistance in such conditions... Please post your system's hardware specs. Specify the target macOS version (eg: Catalina 10.15.7, Big Sur 11.4) Specifiy the bootloader you're using and its version Post a zipped copy of your EFI folder with ACPI & kexts folder + config file Maybe you're re-using an EFI folder grabbed somewhere that includes settings for Intel wireless card; maybe you don't have such a card. Rule #1: know your hardware before you start anything.

No, it's the opposite: people who reported long boot had automatic login disabled and boot time got reduced by about 30s by enabling automatic login. I sure have it enabled. https://www.insanelymac.com/forum/topic/348065-pre-release-macos-monterey/?do=findComment&comment=2760529 https://www.insanelymac.com/forum/topic/348065-pre-release-macos-monterey/?do=findComment&comment=2760595 Did you try to switch FB layout as suggested ? Also, the empty SMBIOS fields in your posted config, that was deliberate, right? Please add your system's specs in signature.

My findings below. ACPI patch: you rename ECDV to EC when you actually inject the SSDT-EC-USBX table; renaming is therefore unnecessary and should be disabled/removed. you inject SSDT-HPET table yet not applying any renaming for HPET or its _CSR method. You would most likely need that for SSDT-HPET to have any effect. Device Properties: you inject SKL framebuffer layout 0x191b0000 for HD530. I would have expected 0x19160000. Are you getting graphics acceleration ? NVRAM: you'll probably have to add -lulibetaall and -wegbeta boot args to avoid system reset at boot time and KP after wake.

@PMD no such issue at all; in fact no issue whatsoever. Using Fenvi BCM94360NG which is fully supported OOB.

Obviously you open up your OC config with whatever tool you normally use (ProperTree, OpenCoreConfigurator, Xcode, etc.) and you disable the currently enabled XhciPortLimit parameter. It's as simple as that.

The only strange/incorrect things I notice are that: you inject CpuTscSync kext for your CPU. You failed to provide details specs about it, so can't say more but I doubt you'd need this on a dual or quad core processor. I'd disable this. you use MBA8,1 SMBIOS which, imo, is entirely inappropriate for your Broadwell laptop given that it's an Amber Lake Y/UHD617 Mac; you should have been using MBA7,x SMBIOS knowing that MBP12,1 is effectively the norm for Broadwell/HD5x00-6x00 laptops. Also, given that you appear to run on the Intel HD5x00 iGPU, why don't you disable the nVidia dGPU? If you do not use it, it's better to disable it to avoid draining your battery unnecessarily.

Make sure to Reset NVRAM each time you make a change to your OC config. If all that you did was add/delete the afore mentioned boot args, no reason why you would not boot back into Big Sur.

Given the continuing lack of clarity, same comments and questions as before: Webcam is USB internal and is therefore expected to be listed in SysInfo->USB. Is it the case? If it's not you still have not properly mapped your USB ports (I noticed you still have XhciPortLimit enabled). If it is, consider the webcam unsupported. You may also want to check that the camera works in, say, Windows to rule out a physical problem (bad connection, defective device). All in your hands...

2 x 1st comments: I don't think yo need that SSDT-ALC292 table. I don't think you ought to have those power settings defined under HDEF device in your patched DSDT. In your Clover config: remove -xcpm and kext-dev-mode=1 boot args; those are completely deprecated (kext-dev-mode=1 applied only to Yosemite!). InjectIntel and ig-platform-id no longer need to be enabled/defined with Lilu + WEG kexts; the patched DSDT also contains the properties injection required for Haswell HD4x00; no need to duplicate those settings everywhere. there are lots of kext patches that can be removed. The deprecated AppleHDA patches are disabled, just remove them; same applied to IOGraphicsFamily patches, totally deprecated Basically, do clean-up your config to return to a sound base without all those duplicates and unnecessary settings.