Hervé

That's the spirit; well done.

BCM4352 chipset is not supported OOB; it requires patching. Did you do that? Lookup the existing threads about DW1560, there are several in which you'll find all that needs to be done.

@Lin_25 Before anything else, please post your system's hardware specs (exact CPU model, iGPU model, audio codec, LAN, wireless, card reader, etc.). Latitude 5480 can be Skylake with HD5x0 graphics or Kaby Lake with HD6x0 graphics so settings would differ. Do also consult the numerous threads about the Latitude 5480 that are available in this very section.

Start here maybe: https://www.insanelymac.com/forum/782-opencore-releases/ Careful as you may not manage to get your BCM43224 wireless card working underMonterey... So proceed with the understanding that you're highly likely to require a change of wifi card.

No, as stated before, you need the SMBIOS of an Ivy Bridge model to obtain proper power management on an Ivy Bridge laptop. You may only use the MBP of a more recent model such as Broadwell MBP12,1 at initial installation (not mandatory thanks to -no_compat_check boot arg) and update (mandatory unless you apply tricks to your SMBIOS) for compatibility reasons with Monterey. Given the likely trouble you're likely to experience, I recommend sticking to Big Sur, the last macOS version too fully and natively support HD4000 graphics.

Make sure you reset NVRAM at next reboot after making your config changes.

I've just tried to boot Monterey 12.3.1 on my E7270 after re-instaling a DW1820A and all was Ok with Clover and the usual properties injection (same as you currently have in your OC config). As such, there's no issue using a DW1820A in 12.3.1 but it's your properties injection that must be the issue. I'm not 100% certain of this but I was somehow led to believe not that long ago that OC had changed and required DATA type device property injections only. Don't know if this is true but, if it were, the compatible and pci-aspm-default properties you currently inject for your DW1820A would need to be revised. Try and put your config through the OC checker/validator or convert all properties to DATA type. Try this: compatible 706369313465342c34336130 DATA pci-aspm-default 00000000 DATA

As a test, disable WLAN in BIOS; in case it's the DW1820A that causes the issue.

No KP on your screenshot, looks more like it's hanging. Why don't you post a zipped copy of your EFI folder. I has no issue on updating to 12.3.1 on my own E7270 but then again, I'm using Clover, not OpenCore.

You need to Google about M.2 slots; they're of different types with different keys (A, E, A+E, B, M, B+M) and for different usages: WLAN (typically A&E key), WWAN (typically B key), NVME/SATA (typically B&M key), etc. Meantime, you may look at this: https://www.delock.de/infothek/M.2/M.2_e.html Your adapter board can only go in your WLAN slot where your current Wireless card is.

None; but make sure you disable hibernation as per the details provided in the dedicated thread in our FAQ section.

If laptop has sufficient space for it, go for an Apple BCM94360CS2 on an M.2 adapter: https://osxlatitude.com/forums/topic/16122-apple-bcm94360cs2-in-hackintosh-laptops-a-great-possible-alternative-but Failing that, consult the list of M.2 cards posted in this very section.

As stated above, you should be using the SMBIOS of a MBP9,2 or MBP10,2; this will require to add boot arg -no_compat_check and will block all future updates OTA. For Monterey updates, you'd have to switch back to the SMBIOS of a supported model (the iMac SMBIOS you currently use or MBP11,4/5, MBP12,1, etc.).

You would need to details the particulars of that old installation if it had non-vanilla settings.

This an Ivy Bridge laptop, isn't it? If you use an SMBIOS different from MBP9.x, MBP10.x or MBA5.x, you won't have CPU power management working and are therefore likely to experience such issues as degraded performance and/or increased heat. Whatsapp and VS Code crashing -> could be linked to issues with Metal (remember that Monterey has no native support for HD4000 unlike Big Sur). As for battery management, well... I'm not sure it can work with the SMBIOS of a desktop but you'll sure need to inject a battery management kext.

I've doubled checked and there's nothing specific to 3rd party/add-on hardware in the patched DSDT. If you're on BIOS A20 and have the recommended settings in place, I'm a bit dry. Will have to make a new USB key to see.

Strange; let me check the patched DSDT. The alternative will be to use patched SSDT tables only, which is entirely feasible nowadays of course.

DSDT.dsl is the DSDT source code and of no particular use except if one wants to further patch the table. I only provided it to avoid the Intel iASL bug encountered if recompiling the table after direct modification of the .aml file. What BIOS version is your E6230 running? Patched DSDT is made from A19 so you gotta run that version at a minimum. As I said earlier, make sure you run on last version A20.

If you meant my E6230 Catalina guide, it contains a power management SSDT for i7-3540M CPU so you need to delete it and replace it by a table that suits your i5-3340M processor. It clearly says so in the guide. Given that I initially had an E6230 with that very specific i5 CPU, that table is available in the guides I posted for previous OS X/macOS versions up to Mojave but I attach a copy below. Feel free to rename the file as you wish. i5-3340M_ssdt.aml.zip

Without any form of info about what's on your USB device, no possible comment can be made. Boot in verbose mode to see where things hang. You mention Atheros and Intel WWAN but I guess you meant WLAN. That's unlikely to cause a reboot. If in doubt, simply disable WLAN/WWAN in BIOS. Talking of BIOS, do check that the settings are all appropriate (cf. our thread about recommended settings for the E6230). Also make sure you run on the latest version A20. Re: reboot after you've logged in, it may be due to the now-inappropriate CPU power management SSDT. I don't know what bootloader you use but if it's Clover, you may simply drop that add-on table through Clover's main menu at startup (Options->ACPI Patching menu). It'll completely bypass that table and you won't have proper CPU PM but will certainly avoid calling on invalid CPU steps.

@juhyh Re: battery, your EFI shows no kext for battery management; that's required. Try this one: ACPIBatteryManager.kext.zip Copy the unzipped kext to your kexts folder, add it to your existing OC config and reset NVRAM when you reboot. A few additional comments: until you identify your LAN card model, I don't think you need the 3 x Ethernet drivers you've included: AtherosE2200Ethernet + RealtekRTL8111 + IntelMausi. you probably don't need XHCI_unsupported either. in the same respect, AirportBrcmFixup is for Broadcom wireless cards. You have an Intel card, so that kext is not required. you inject AppleALC for audio and therefore require to identify your audio codec so that you subsequently inject the appropriate layout. You won't have any working audio until you do that.

Given that XPS 9370 is a laptop you had fully working under Catalina, how did you end up with: SMBIOS of Kaby Lake iMac18,3 desktop Mac? a totally unsuitable and useless headless (meaning no output video port) KBL framebuffer layout 0x59120003? ID: 59120003, STOLEN: 0 bytes, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00001000 TOTAL STOLEN: 1 MB, TOTAL CURSOR: 0 bytes, MAX STOLEN: 1 MB, MAX OVERALL: 1 MB Model name: Intel HD Graphics KBL Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 0, PortCount: 0, FBMemoryCount: 0 You need to go back to those settings you had in your previous build and that you posted at the bottom of the previous page. Please note that seeing UHD 620 reported with 31MB VRAM means you have no graphics acceleration. When graphics acceleration is in place, UHD620 graphics gets reported with 1526MB VRAM. Why you've ended up with a totally different setup is a mystery only you can explain. All you really had to do was upgrade your Catalina build and retain the same graphics settings. You know what to do now...

@juhyh please post your full system's hardware specifications: LAN, Wireless, audio codec, SD card reader, trackPad model, etc. An indication of the boo loader and bootloader version you've used would also be most useful. Add to that a zipped copy of the bootoloader EFI that you currently use. Without these, it's impossible to provide assistance.

Open up a new thread for this separate issue.