Hervé

HFSPlusmodule is Apple's own driver. VBoxHFS is open-source and said to be slower. Yes, booting only from Preboot is perfectly normal. You can have a look at the Clover Discussion thread at IM if you want.

No such device in your posted IOReg... What's the device address shown in Windows?

Bluetooth injector presence or absence should be of no influence on the Wifi service. Bluetooth is USB-based, Wifi is PCIe-based.

A simple look at the Dell support web site would have shown this Haswell laptop is fitted with a good old 'legacy' Synaptics touchpad. I2C hardware came with much later generations... https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=9nnk9&oscode=w764&productcode=inspiron-15-3542-laptop&lwp=rt https://dortania.github.io/OpenCore-Install-Guide/prerequisites.html#prerequisites "[CRUCIAL] Know your hardware"

True, I need to add that HFSPlus module should be manually added with later versions of Clover. It's just that it used to be included before (not any more) and, in my case, I updated Clover from previous versions so the (old) module remained in place. You got to make sure you use the correct version though, it's kinda faint in my memory but I think I remember about one HFS driver being preferable to another which could cause slow boot (something like Apple vs non Apple maybe, I've forgotten). So it really depends where you got yours from. I've added the original Clover module to the guides. Edit: re: slow driver, it's something along the lines as detailed here.

Everything should work fine except the I2C TouchPad which may still have limited support only and the SD card reader which may no be supported at all depending on the exact model.

I looked at the patch you took inspiration from and can only make the following comments: it's something dating back to 2016 it's something that applied to an Asrock Skylake desktop motherboard I'm not entirely convinced that the patch that consists of simply removing the entire method _L6F is fully applicable to your Dell Comet Lake laptop but Ok if you've established your high CPU utilisation derived from the same problem of having kernel_task process running at 100% CPU load of course. Did you see a similar ACPI _L6F related error message in your boot log? I really must ask what makes you so sure about your statement re: bugged UEFI firmware... Anyway, as a simpler alternative to DSDT patching, I would suggest that, in you Bootloader config, you simply rename method _L6F to XL6F (or _L6X) through the following ACPI patch/renaming: Find (Hex): 5F4C364600 Replace (Hex): 584C364600 (or 5F4C365800) because _Lxx methods are for interrupts xx (in hex). The only way you could remove method _L6F from ACPI through an SSDT would be to replace the entire _GPE scope that contained the method by a new one that would not contain it. It's feasible of course but really complicated (several instances of Scope (_GPE) in your DSDT, need to rename all methods and/or variables the scopes contain, etc.) when you may simply isolate/void method _L6F through the above renaming. Of course, you could also consider renaming _L6F to, say, XXXX to be more radical: Find (Hex): 5F4C364600 Replace (Hex): 5858585800 Failing that, just use a patched DSDT where method _L6F has been removed.

I've no issue booting and running Monterey 12.2 on my E7270 with the DW1820A and the usual device property injections. I use Clover though, not OpenCore. In your particular case, I think the issue comes from your OC config. I don't know what version you use but the OC devs keep changing things every month and I was recently led to believe that STRING value type is no longer supported and requires to be replaced by hexadecimal DATA value type. If it were indeed the case, it could explain why you were not able to inject the required properties and, as a result, the freeze during startup... But rest assured that, at the time of writing, there is no incompatibility between all existing Monterey versions and the DW1820A which remains 100% supported as per under previous macOS versions.

1st and foremost, post your full system's specs. A copy of that config of yours would very obviously be a plus... HD4000 graphics are natively supported with the relevant settings: Capri framebuffer 0x01660003 for LoRes screens or 0x01660004 for HiRes screens + suitable SMBIOS such as MBP9,2 or MBP10,2. follow the process you seem to know about tap to click is not enabled by default. Check your TrackPad PrefPane. Make sure you use the appropriate Alps PS2 controller on your E6430 (i.e. Dr Hurt's, available off the dedicated thread on the matter)

The instructions I posted are based on Terminal/line commands. I also gave you this link in answer to your post at IM. You may simply follow the process described for HD3000 tuning. Make sure you follow it to the letter. If you use OC, just adapt your config so that you may boot in single-user mode.

Correct; macOS has no support for integrated graphics of Intel 11th gen CPUs. See our compatibility-related threads: https://osxlatitude.com/forums/topic/2998-min-requirements-for-os-xmacos https://osxlatitude.com/forums/topic/8238-supportedunsupported-gpus-graphics-cards

Identify your hardware specs. Build your own bootpack from other Haswell-based Latitude E5x40/E6x40/E7x40. i5-4310u includes HD4400 iGPU.

Using an AR9462 card in a Hackintosh is a punishment in itself...

No, you have not. You need declare RP05 AND its PXSX child as external. Ok, it's the SSDT table that you've named ARPT. And I'm pretty sure you need to use SCOPE for your target rather than DEVICE since we're dealing with existing ACPI objects, not new ones you wish to create. Original objets need to be renamed if you wish to replace them by new entries, otherwise your code is just ignored as I suspect yours is ('noticed the " 1 table load failures" error message?). Hence why renaming such as X--- or ---X can be found in Bootloader's configs to accompany pathed SSDTs. Eg: _OSI renamed to XOSI, OSID renamed to XSID, HPET renamed to XPET, etc. that complement specific patched SSDTs that redefine the original objects. To me, your SSDT should look like: external (xxxx.RP05.PXSX, DeviceObj) Scope (xxxxx.RP05.PXSX) { Method (_DSM, 4, NotSerialized) { [...] } } assuming, of course, that there's no existing _DSM method under RP05.PXSX in your vanilla DSDT.

Best thing really is to replace that Atheros AR9462; they're totally crap under macOS. Failing that, with the specific rewritten kext for AR9462: https://github.com/khronokernel/IO80211-Patches

If you wish to try the SSDT method, you need to declare device PXSX as eternal too because it already exists in the DSDT. If you don't declare it as external, your DSDT basically attempts to create a duplicate of a valid existing one and this is rejected. And, of course, if you inject AirportBrcmFixup or rename your wireless ACPI device as seems to be the case, device PXSX gets renamed to ARPT... So, you're basically shooting blanks for the time being. NB: as per our published rules, no systematic quoting to post replies please. Forum offers Reply boxes at the bottom of every page for that very specific purpose so please use that.

Posted config file appears incorrect and cannot be opened with usual OC tools. Line 1246 carries a syntax error/ <string><>/string> Should be! <string></string> According to the IOReg screenshot you posted, none of the desired properties appear injected for the DW820A at the desired location 1C,0. That explains why you're not able to boot unless you disable wireless in BIOS. So, there's definitely something wrong in your config file. Check it out thoroughly and use the config verification tools. Please note that you should not require AirportBrcmFixup nor its PlugIns for the DW1820A, even in. Monterey.

Failing that, you may use the kexts I provided in the bootpack of my E7270 guides. Basic features only (tap to click, 2-finger scrolling, no trackpad PrefPane) but 100% operational otherwise.

We have a dedicated thread on the matter in our FAQ section. Look it up. It won't give you the specifics for your E6420 but certainly all the necessary pointers for creating a macOS USB installer from Windows. Please note that HD3000 iGPU was last officially supported in macOS High Sierra 10.13 which goes back to 5 years ago so the ageing Sandy Bridge E6x20 are no longer a great platform to run as Hackintoshes. This is worsen by the poor/buggy support of HD3000 graphics since OS X El Capitan 10.11/macOS Sierra 10.12.

No HDMI output registering...

Apart fom the weird value shown for iGPU subsystem id, all looks ok to me. What were your settings at the time you took this IOReg? Was HDMI monitor plugged in?

The iGPU properties injected in @Vonjy's Clover config are odd and contradictory: device location is incorrectly entered (though it probably works due to values being <10) framebuffer port count set to 2 yet there's a patch for a 3rd one This needs be revisited and configured with correct syntax and meaningful parameters: 1) iGPU device location PciRoot(0x0)/Pci(0x2,0x0) 2) iGPU properties AAPL,ig-platform-id 00001659 DATA device-id 16590000 DATA framebuffer-patch-enable 1 NUMBER framebuffer-stolenmem 00003001 DATA framebuffer-fbmem 00009000 DATA framebuffer-unifiedmem 00000080 DATA framebuffer-con1-enable 1 NUMBER framebuffer-con1-type 00080000 DATA // but this is usually to support HDMI audio, not HDMI per sé 3) SMBIOS Check whether MBP14,3 is more appropriate than MBP14,1.

Ok, something's lost in translation here because what you write does not make much sense. Being a piece of Apple hardware, Broadcom-based BCM94360CD remains supported OOB and 100% operational in Big Sur and Monterey, i.e. without any sort of particular settings or add-on kexts. At the risk of paraphrasing you, I know because that's what I use in my Latitude E6230 running Big Sur. It also worked 100% and OOB in Monterey during the short time I tested that version on the E6230. Of course, your BCM94360CD does not need your Intel card to be installed for its Bluetooth module to work, that really goes without saying. What you experience must obviously be a conflict of some sort due to hardware competition and/or incorrect settings, either in your OC config and/or BIOS. You can only expect one card to provide the wireless and/or Bluetooth service(s), not both cards. I remember that, when I had my Latitude E6440, it came fitted with an unsupported (at that time) Intel combo Wifi/BT card that I kept in place despite adding an Atheros wireless-only card into the 2nd mini-PcIe slot. Bluetooth was enabled in BIOS and, obviously, could only be available from the Intel card. I found that it was natively but only partially supported in OS X (very limited functionalities) and came to complement the wifi service offered by the Atheros card. In that situation, I got wireless through the Atheros card and Bluetooth through the Intel card, there was no conflict. If you have competing hardware that offer same services, you'll experience conflicts. Not so much for wireless here because the Intel card needs specific drivers when the Apple card does not, so as long as you do not install the itlwm drivers, you'll be Ok. For Bluetooth, things are different because the technology is not PCIe based but USB based and the chipsets fitted to the cards may be natively supported by macOS. In addition, when Bluetooth's availability is controlled through BIOS settings, this usually applies to the hardware fitted into WLAN slot or the built-in module. For instance, in my E6230 (and it was the same for my E6220 when I still had one), if I enabled Bluetooth in BIOS, it applied to the small DW3xx modules and I found these could take precedence and overcome my BCM94360CD cards. Again, I strongly advise you to remove your Intel card and all add-on kexts/ACPI patches/config settings for wireless and Bluetooth. Also check your BIOS settings for Bluetooth. If you insist on keeping your Intel card in place in the WLAN slot (but I can't see any valid reason to do so), make sure Bluetooth is disabled in BIOS and you should then be good to go with all wireless and Bluetooth services available and operational through the Apple BCM94360CD. BIOS Bluetooth settings apply to what Dell sometimes refer to as "internal module" and, in your particular case, you may want to keep it disabled to avoid all possible confusion and hardware conflict (it'll basically disable the USB functionality of the WLAN slot). Afaik, the BCM94360CD will still provide you Bluetooth services with the option disabled in BIOS. One word of caution with regards to Monterey: despite the use of Apple hardware, Bluetooth may still be a little glitchy/buggy in Monterey but it's something specific to that version of macOS and, if it's been more or less fixed on real Macs, things remain a little itchy on Hackintosh systems. You can read it all on the various Hackintosh forums.

https://openintelwireless.github.io/IntelBluetoothFirmware/FAQ.html#what-additional-steps-should-i-do-to-make-bluetooth-work-on-macos-monterey I really can't see why you'd keep the Intel card alongside the Apple BCM94360CD which is 100% supported OOB. In addition, having 2 x cards that basically provide the same type of services really is a bad idea. I suggest you remove the Intel card and all add-on kexts/ACPI patches/config settings you have in place for wireless and bluetooth. You do not need anything with the Apple card.

Just add this IOHIDFamily patch to you OC config: https://dortania.github.io/OpenCore-Install-Guide/extras/big-sur/#keyboard-and-mouse-broken