Hervé

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.

1st of all, identify all your hardware specs. Then, you have no graphics acceleration, you missed that essential part... You have to install any Catalina versions past 10.15.3 with dosdude1's patcher. Your laptop will be kind of unusable without graphics acceleration. Then, after any Catalina update, you have to re-patch the system again; last time I checked, this could be most awkward/difficult with dosdude1's patcher but things may have evolved since. You may check that out at MacRumors where they have a dedicated thread for Catalina on unsupported platforms. Any Sandy Bridge/HD3000 platform falls into that category.

1st of all, post your specs so that we can ascertain your own situation, especially for wireless. You may also want to have a look at my E7270 guide to compare settings. I encounter none of the issues you've listed but I use far less kexts and a few more patched SSDTs of course. HDMI output always worked OOB for me (with the behaviour detailed in my guide) and I've only injected HDMI port type in order to gain HDMI audio output. Screen brightness works with SSDT-PNLF. Brightness keys work with the associated config settings + patched SSDT as detailed in a few posts and guide I posted. Can't see why you'd lose wireless after wake but Jake's EFI folder appears to inject properties for a DW1820A and you may not have such a card.

Looks like after registering in 2013, you were last a little active on the forum in 2017 until you returned today. You must have missed our site revamps of spring 2018 and end 2020.

I've re-enabled RSS with the following feeds: News & Articles (for News/Articles/Guides we post on OSXL Home page) Latest Topics (for last 10 new topics) Any other feed would be old/defunct/cached stuff and not subject to any update.

I'll see if we can re-enable some feeds.

I don't know what you're trying to say here... We publish news and articles whenever we have info to share but we've no active RSS feeds that push info out.

We've not had any RSS feeds for years...

Situation and behaviour regarding Optimus: disabled -> laptop runs on nVidia dGPU only. enabled -> laptop runs on Intel iGPU and nVidia dGPU; dual GPU switching mode on (but unsupported in OS X/macOS). Trouble is that Fermi chips such as the NVS 5200M have no proper support to no support at all in macOS since High Sierra. The buck stopped at Sierra. As such, you can only run Catalina on the Intel HD4000 iGPU. Given that Optimus has to be enabled to that effect, you need to disable the dGPU through ACPI patching in order to prevent it from draining on the battery unnecessarily. Your config shows that you correctly opted for the HiRes Capri Framebuffer 0x01660004 which is required for your HiRes screen 1600x900. This HiRes Framebuffer only offers 1 x video port by default for LVDS/eDP built-in screen so you'll also have to inject additional properties if you ever want to use external monitors (DVI, HDMI, DP; VGA unsupported). You'll find all the necessary details in the dedicated thread to HD4000 graphics available in our R&D->Graphics section. I also noticed you also opted for MBP11,1 SMBIOS; this is a Haswell model that does not require the -no_compat_check boot arg so you could delete that. The boot arg would only be necessary if you opted for an Ivy Bridge model such as MPB9,2 or MPB10,2. You'll also need additional ACPI tables/parameters in your config to trigger support for your keyboards brightness keys; you'll find all the necessary details in my E6230 guide.

You may try and extract your screen's EDID from Windows/Linux, then inject it into macOS through properties passed through your boot loader's config. https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md