Hervé

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.

Define "not working".

You need fully working Wireless + Bluetooth for Airdrop to work. Then set the suitable rights in Airdrop of course.

Webcam is USB based. Can't remember if there are a couple of different models that were fitted to the E6430 like there were on the E6420. As long as your USB ports are properly mapped, Webcam will work either OOB or not at all depending on the model. Look it up in SysInfo->Hardware-USB or in IOReg. In your case of an E6430 with a quad-core CPU, the best SMBIOS to use in my opinion Is MBP10,2 but BMP9,2 will do fine too (not MBP9,1 or MBP10,1 because these used a Kepler nVidia dGPU). Make sure you make your USB port mappings after you've selected your SMBIOS, the 2 are linked. Re: CPU power management, it does not look like you got it right: you sure generated the proper SSDT table with Pike R Alpha's generator script, but you've not enabled it in your OC config file...

Apparently it's a Latitude E6420... @VGX.SAM I wouldn't waste my time if I were you. Look at existing threads such as this. The Latitude E6240 is a Sandy Bridge laptop fitted with either HD3000 graphics or HD3000/nVidia NVS 4200M graphics (Optimus). Look up our Supported/unsupported GPU thread in our Graphics forum subsection. NVS4200M dGPU is of Fermi generation and was last supported in OS X El Capitan 10.11. E6x20 cannot run on this dGPU since macOS Sierra 10.12. HD3000 iGPU was last officially supported in High Sierra 10.13. Support may be extended beyond High Sierra but only in OpenGLmode (no support for Metal) through specific patches. In Mojave 10.14, the patches are fairly simple to apply. Things get far more complicated in Catalina 10.15 and require to use a dedicated patching tool (dosdude1's patcher) that, I think, limits the ability to apply Security Updates of 10.15.7 (I think one needs a separate tool for that). I understand patches were also made available for Big Sur 11 but I've no experience with those. Nothing suitable exists for Monterey which is a no go for HD3000 to date. Keep in mind that HD3000 is a fairly poor iGPU that suffers from buggy drivers beyond OS X Yosemite 10.10 leading to graphics defects/artefacts/gremlins on screen: over time you'll end up with black horizontal lines, pixelisation, corrupt pictures, etc. If running with max. RAM and therefore max. VRAM (8GB RAM-> 512MB VRAM) does improve things a little, there's no fix and all those require nothing but a reboot. Given the graphics bugs you'll experience, my recommendation is to go no higher than High Sierra or Mojave on this now-obsolete laptop. The prebuilt OpenCore EFI folder you use is unsuitable to your E6240; there are many things to review: kexts, ACPI tables, config. For instance, it injects inappropriate and unnecessary kexts (eg: AtherosE2200Ethernet and RealtekRTL8111 LAN drivers, NVMeFix kext) and tables. The config is also missing key elements, especially on the properties injection side (eg: nothing for graphics, audio, card reader, etc.). I don't know where you got this from but it's really not for your laptop. I invite you to refer to my E6220 guide for pointers and information. You'll see that, in my last contributions for Mojave and Catalina, there was no need for patched DSDT and that patched SSDTs sufficed. I must say that, for Catalina, I was unable to succeed in booting a Catalina USB installer for fresh installation; this despite my numerous efforts to do so and I think I ain't too bad at Hackintoshing... If you keep OpenCore as bootloader, make sure you specify the version you use or you'll have trouble getting the appropriate support because an OC config varies from one OC version to the next in accordance to the changes brought by the devs.

The EFI you seem to refer to is not for OC 0.7.9 but for a much older version of OpenCore; you'll have to build an OC 0.7.9 EFI, using the same principles as those used for the older one. But you cannot re-use the files.

No.

Follow the instruction available at OpenIntelWireless repo/site: https://openintelwireless.github.io Make sure you use the correct driver version for Catalina. Eg: https://github.com/OpenIntelWireless/itlwm/releases/tag/v2.1.0

Stick to MBP15,2 SMBIOS.

Please check and post your system’s specs because: nVidia Quadro K620 is Maxwell and therefore unsupported beyond High Sierra (with which it requires the nVidia Web Driver). Intel HD500 graphics is a low-end mobile iGPU of low-end Apollo Lake SOC platforms and unsupported under macOS. It cannot be what’s fitted to a Skylake workstation such as the Precision Tower 3620. 'should be something more like Intel HD530 (i3/i5/i7 Skylake CPU) or HD P530 (Xeon E3-12xx v5 Skylake CPU). Once you know what hardware you have, which is a pre-requisite, you may consult this thread: https://osxlatitude.com/forums/topic/8238-supportedunsupported-gpus-graphics-cards

Just ignore it.