Hervé

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.

I would have expected the TouchPad of the 7290 to be the same as the 7490's; try the VoodooPS2 kexts I had posted in the packs of my Latitude 7490 guides.

6th beta released August 30th, 2021. Build 21A5506j. Ok on my Latitude E7270 (Clover r5133) and Satellite Pro R50-B (OC 0.7.0).

You'd have to boot in verbose mode to see where boot process hangs.

What are those screenshots meant to show us? I'm seeing the icon of an external monitor, i.e. what would normally be shown as a 2nd display on a laptop or as main screen on a desktop or what you'd obtain with the SMBIOS of an iMac/MacPro. When running on a laptop with a MB/MBP SMBIOS, any properly detected built-in screen would be normally shown as a laptop screen. Could you remove those FakePCIID kexts and check if it makes any difference?

Not at all, I still used mine in Big Sur and it worked perfectly on the wireless side with the appropriate settings detailed in our BCM4350 guide. It’s the Bluetooth that kept giving me trouble so I eventually switched to a BCM94360NG which worked 100% and OOB though I found it’s wifi performance poorer than that of the DW1820A. As long as you inject the aspm related property, the DW1820A should work fine on the wireless side. However, if your card is also troublesome in Windows, you must consider a potential hardware-related issue (bad connection in the slot, defective card, broken antenna connectors, etc.).

Ok, will update the inventory then.

I understood BCM4352 no longer worked under Big Sur but, if it did, I would not have expected any Incompatibility between DW1560 and Monterey kexts. By all means, post a zipped copy of your bootloader’s EFI folder + extracted/saved IOReg.

It's impossible to answer your question which is the same as asking how long a piece of string is... Jake gave you a couple of methods to identify your codec, failing that, you may try and install VoodooHDA/AppleHDADisabler kexts through the method described here and check your codec id with apps such as DPCIManager.

Erm... it remains 100% available for download at the bottom of post #1 on p1 !

https://osxlatitude.com/forums/topic/10117-half-size-pci-wifibluetooth-card-for-airdrop1st basic rule re: Hackintoshing: get to know your hardware as they wrote at Dortania! E6440 takes full and 1/2 mini PCIe cards. It's not really a matter of picking a card compatible with the E6440 (there is no whitelisting so any mini PCIe cards can be fitted), it's a matter of picking the card compatible with the target version of macOS. There too, look this up in our FAQ and in our Tech Info/R&D->Wireless sections. Just browse and search a little really... Plenty of existing (old) threads on this very matter in E6xxx and Archive sections too. Eg: https://osxlatitude.com/forums/topic/10117-half-size-pci-wifibluetooth-card-for-airdrop

Do you use WEG boot arg igfxonln=1 ? Needed it on my Skylake E7270 or built-in LCD went off on plugging an HDMI display and/or after wake.

Replace that Intel card with a fully supported Broadcom model if you need Bluetooth services.

No need to switch to Clover, you can add the missing SSDT and adjust kexts set directly in OC; just modify your config file accordingly.

You'll find my (Clover) guide in the Guides section.

Would not open in OCC or ProperTree at my end but there's seems to be an issue with OC version anyway so clarification required.

Your posted OC config file appears corrupt...

Please search the forum before posting. Thank you. https://osxlatitude.com/forums/topic/10263-older-broadcom-cards-eg-bcm431x-unsupported-since-sierra https://osxlatitude.com/forums/topic/11138-inventory-of-supportedunsupported-wireless-cards-2-sierra-big-sur

Note that EDID's hexadecimal data must be entered without any spaces. They'll just automatically pop out afterwards.

Re: HD3000 VRAM, default behaviour in OS X/macOS is to allocate VRAM according to the amount of RAM fitted to the computer. https://support.apple.com/en-us/HT204349 If you want to allocate more VRAM, you can apply patches to the SNB kexts though there is very little to gain; certainly nothing from a performance point of view (HD3000 is a pretty poor iGPU) and it won't fix the memory leak bug that causes horizontal lines and artefacts across the screen over time, merely slow it down a little (only solution is to reboot). You'll find details of the VRAM patch in this thread at IM or in the Clover config I posted in my most recent E6220 guides (High Sierra and later). Reading through the IM thread, you'll find that there's no gain to be obtained past 1024MB of VRAM. Re: RAM, it's a little confusing because you entitled your thread with 4GB RAM and specified that in post #1. However your initial screenshot showed 8GB and you seem to state that you get 512MB VRAM allocated by default as is the case with 8GB RAM. If your laptop is only fitted with 4GB or RAM, I certainly would not go beyond 512MB for HD3000 VRAM ,for obvious reasons. If you have 8GB, yes you may allocate 1.5 or 2GB VRAM but, as stated above, 1GB really is sufficient.

Coming from Sierra (or earlier), many of us initially experimented or started with High Sierra in legacy HFS+ mode given that APFS was new and did not work extremely well on mechanical HDDs. However, as time passed and more users ran on SSDs, the installation in APFS mode gradually generalised. But rest assured that opting for no conversion works well and you can safely go for that. Subsequent macOS versions no longer offer this and APFS is sole standard mode. Running Mojave and later on HFS partitions requires tricks that are best avoided imo.