Hervé

IOReg is of absolutely no use if you disable Wireless in BIOS...

@Baio77 Please keep this thread on-topic.

Works for me on my Latitude E7270 in Monterey with just the properties injection stated in point #3 of the last post in the BCM4350 thread. No add-on kext or injector whatsoever. Basically, all that I really need in Clover is: compatible pci14e4,43a0 STRING pci-aspm-default 0 NUMBER the rest being purely cosmetic. Try without ACPI AirportFix. In fact, one must wonder if you really need all those ACPI patches and renamings in your Clover config. Boot args are questionable also (especially the useless & duplicated Yosemite-only kext-dev-mode=1). Post an IOReg extract.

The posted "EFI SHUTDOWNFIX" contains an OC config file that does not call on the Fix-Shutdown-USB-SSDT. Yet, the patched tile is in the ACPI folder. Is that omission deliberate? Table won't get loaded unless specified in the OpenCore config file. But I'm not sure this will actually fix your shutdown issue. The patched table calls on an external function that must of course be defined elsewhere in your vanilla tables.

Original thread was getting really messy with 3rd party acting as intermediaries and turning off-topic so it's moved to a dedicated thread with direct input/feedback from system's owner. As previously indicated/provided by @Jake Lo: Dortania guide : https://dortania.github.io/OpenCore-Post-Install/usb/misc/shutdown.html You'll need both of the *.aml files and add the 2 patches to your config.plist Jake provided the files in the following attachment: ShutdownFix.zip @Mr_T_aus_B please list your system's specs, ideally add them in signature.

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...