Hervé

Erm... all you have to do is add the single necessary ACPI patch in your bootloader config (1 line if you use Clover Configurator or OpenCore Configurator).

Well, if you think the touchscreen is that Intel Sensor, did you try the USB HID Fix I mentioned above?

I don't see much difference in IOReg... Question: if this is the Bluetooth module of your Intel 7260 wireless card, is this the touchscreen?

'same as Jake for me: 'could not see any USB-based touchscreen in your extracted IOReg. Unless I missed something, I didn't see any confirmation that touchscreen was working on the XPS 12 9Q33 with Jake's 2017's bootpack you just linked. Do you see your touchscreen in SysInfo->Hardware->USB or can you post a SysInfo extract? If it's USB based, you need to ensure you've properly mapped all your USB ports and, if it does not natively work under Monterey but is visible in Sysinfo, you may need to apply the USB HID Fix (described here if you're using Clover or at Dortania if you're using Opencore).

Absolutely correct, I had forgotten! https://osxlatitude.com/articles/news/macos-monterey-is-out-r44/ https://support.apple.com/en-us/HT212551 https://everymac.com/systems/by_year/macs-released-in-2015.html

Check the SMBIOS in use; you need one of a model compatible with Monterey. Typical Haswell MBP11,1 is not compatible; you need to select Broadwell (eg MBP12,1) Haswell MacBookPro11,4 SMBIOS minimum to get Monterey upgrade offered.

You're using a rather odd framebuffer layout for your 10th gen Comet Lake UHD620 graphics: you opted for unusual 7th gen Kaby Lake framebuffer 0x591C005, something listed in the Whatevergreen user manual for UHD 617. ID: 591C0005, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00A30702 TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes) Model name: Intel UHD Graphics 617 Camellia: CamelliaV3 (3), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000003C7 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000003C7 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 C7030000 02040A00 00040000 C7030000 Any reason why don't you use the recommended settings for a Comet Lake laptop? https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md https://dortania.github.io/OpenCore-Install-Guide/config-laptop.plist/coffee-lake-plus.html

Don't know what you were possibly expecting with old Chameleon boot option cpus=1 but whatever; you got it sorted, that's all that matters.

Does not look different to me. Properties injection for DW1820A don't look like they're being injected. If you disable Wireless in your BIOS settings, there should be a difference... In addition, what are the reasons for using: SKL framebuffer 0x191B0000 rather than 0x19160000? SSDT-AC + SSDT-DMAC + SSDT-MCHC-SBUS + SSDT_OCWorkDell patched tables? add-on kexts such as FeatureUnlock + Intel & Broadcom Bluetooth firmware + NoTouchID + Sinetek-rtsx + VoodooI2C + CPUFriend? Your SSDT-EC-USBX_Laptop patched table looks wrong to me and could also cause a system freeze. I suggest you download the table from Dortania's web site. I have a much simpler set of ACPI tables and kexts on my E7270 and all works perfectly well. Looks like you've thrown all sort of (inappropriate) things at your E7470. I would suggest you seek inspiration out of Jake's guide: https://osxlatitude.com/forums/topic/9179-dell-latitude-e7x70-clover-and-opencore

See my reply in your identical thread posted at IM: screenshot shows a reference to Broadcom card 14e4:43a3. OpenCore config shows properties for a DW1820A commented out. If you have a DW1820A in that E7470, you must inject the properties that fake BCM4360 and disable ASPM or you'll indeed encounter system freeze at startup. See our detailed thread about BCM4350-based cards in our R&D->Wireless section. Looks like you modified your OC config before or after updating to 12.1

There's nothing strange, just a total lack of understanding and knowledge on the matter. There's no secret and if you don't try (to understand), you don't get (knowledge)... Simply copying stuff in the blind leads nowhere, you got that proven if nothing else. Don't hesitate to Google for info on framebuffer, graphics memory, picture size or colour depth. Eg: https://www.quora.com/How-can-the-size-of-the-VRAM-determines-the-resolution-and-color-depth-of-the-monitor

Of course it works! Why do you say it's strange? And if it works, isn't it obviously kosher ?

It appears you've not realised that framebuffer-patch-enable is a boolean flag (so set it to 0 or 1 and type NUMBER rather than 8 x bytes with type DATA) and that, by setting it to 0 (i.e. FALSE), you actually disable patching. As such, all subsequent framebuffer patches in your config are rendered useless (but probably not connector patches since these have their own boolean flags)... 4K output usually requires that framebuffer memory be a minimum given size and usually greater than 32MB (I don't know the exact minimum value). Such requirements do normally imply that framebuffer memory settings be left untouched. Instead, your framebuffer patches basically limited framebuffer memory (stolenmem) to 19MB which would explain why you could not obtain 4K output. Such patch is only required (and usually accompanied by cursor memory patch too) if DVMT pre-allocated memory is set to to 32MB in BIOS and the selected OS X/macOS framebuffer default memory settings (stolenmem + fbmem) exceeds 32MB, in which case KP occurs if no patches are applied (cf. Firewolf's 2015 explanations). This usually applies to laptops only, desktops (recent/modern ones) very frequently allowing to adjust DVMT settings in BIOS. You inject/select the expected CFL framebuffer layout 0x3E9B007 which defines/sets/uses 57MB of framebuffer memory (stolenmem) and no cursor memory (fbmem ID: 3E9B0007, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00801302 TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes) Model name: Intel UHD Graphics 630 Camellia: CamelliaDisabled (0), Freq: 0 Hz, FreqMax: 0 Hz Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x000003C7 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000003C7 - ConnectorDP [3] busId: 0x06, pipe: 8, type: 0x00000400, flags: 0x000003C7 - ConnectorDP 01050900 00040000 C7030000 02040A00 00040000 C7030000 03060800 00040000 C7030000 so framebuffer memory is indeed >32MB by default. Given that you do not encounter a KP when you boot without framebuffer patches (i.e. no memory patches), it's fair to conclude that your desktop's default or current DVMT pre-allocated memory is set to at least 64MB (you may be able to check the exact value in BIOS settings or by checking BIOS info through GrubShell). So, indeed, do not apply any framebuffer patches (or limit it to VRAM (unifiedmem) patch), only connector patches if required (for instance to enable HDMI audio output by setting the relevant connector to HDMI type 00080000). I'm not sure all the connector patches you've configured are desired, necessary, suitable or useful though... I invite you to read the Whatevergreen User Manual and a recent article I posted at IM on the matter of DVMT pre-allocated memory/framebuffer memory settings & patches. https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md https://www.insanelymac.com/forum/topic/349132-what-are-dvmt-stolenmem-fbmem-cursormem-and-why-do-we-patch-these-for-broadwell-and-later/?tab=comments#comment-2768210

You may find useful to consult the various threads available at IM that detail the OC changes from one version to the next. https://www.insanelymac.com/forum/782-opencore-releases/

Then you have incorrect settings to fix at lower level; check the SMBIOS set in your config so that it is one compatible with High Sierra; check your BIOS settings (disk in AHCI mode for instance).* You said you followed Jake's guide to the T; which mode, UEFI or legacy? Please be very specific in everything you do and state.

Screensize should be irrelevant. Did you reformat the target disk HFS+ with partition scheme GUID through Tools->Disk Utility once you reached the macOS installation screen? It's the 1st thing to do before you proceed with the installation. Assuming you have an SSD, you will want AFPS. Boot pack is for models with BIOS version A19 or higher, is this your case?

By the way, BCM94360CD is BT4.0, not BT5.0.

As per our published rules which I invite you to read before anything else, no links or references to distros. As a newbie to the Hackintosh world, you're gonna have to go through the pain of educating yourself through much reading, much trying, much failing, much trying agin and so on. There's no other way. We do not support nor welcome shortcuts of distros which are more evil than good. Good places to consult are our Guides and FAQ forum sections. We have several guides for other Broadwell Latitude models that include E5x50 and E7x50 laptops. If you use the forum Search facility, I'm sure you'll also find plenty of threads relating to the E5x50 family.

You're highly unlikely to find a laptop that meets all this nowadays. In recent years, the trend has heavily shifted towards low-power and slim/light platforms. Today, laptops with extra slot for a 2.5" hard drive/SSD usually are 15.6" or larger models. Those don't fall into the slim and light weight category, more into the bulky and heavy one... Upgradable dGPUs, kind of deprecated these days; it was something usually restricted to mobile workstations in the form of MXM modules but I don't think this kind of technology remains much in use today. And even in the days where this was available in laptops, MXM modules were often limited to specific offerings by the manufacturer due to proprietary design. So upgradability was very limited and usually to 2 to 3 dGPUs, 4 if you were lucky.. Examples: Dell Precision M4800/M6800. https://dl.dell.com/content/manual32906200-dell-precision-mobile-workstation-m4800-owner-s-manual.pdf?language=en-us&ps=true The last 14.1" Dell mobile workstations were the old Merom/Penryn C2D-based Precision M2300 and M2400. Former was nothing but a Latitude D630 with a better nVidia dGPU (Quadro FX 360M) than the standard/regular one (Quadro NVS 135M). Latter was the same as the Latitude E6400, also with a better nVidia dGPU (Quadro FX 370M) rather than the standard/regular one (NVS 160M). All subsequent Dell mobile Precision workstations are 15.6" and 17". https://en.wikipedia.org/wiki/Dell_Precision#Dell_Precision_Mobile_Workstations Keep looking for the rare beast!

Very old stuff my E6440 guide and research work but, yeah, those were the days... Yes, this is the kind of adapter you need though you should be able to find it for much cheaper. Look it up. To illustrate why you should feel safe about the BCM94360CD on a mini-PCIe adapter re: space/size:

Of course you need a mini-PCIe adapter board for an Apple BCM94360CD card; please refer to our dedicated thread on the matter as stated above. We also have a couple of inventories re: compatible/non-compatible cards. They cannot be exhaustive of course but look these up. Mini-PCIe slots and cards have been deprecated since circa 2015 so you're highly unlikely to find what you wish for (a Big Sur compatible mini-PCIe card with BT 5.0). As for Apple, they've long stopped using mini-PCIe cards in favour of their own proprietary interface...

Well it does say DW1550 on it, doesn't it? But, unlike an Apple Card, it does not work OOB though... I've checked size of Apple's BCM94360CD on its mini-PCIe adapter (my leftover from the E6220 I sold last year) and it does fit exactly the size of a full-size mini-PCIe wireless card so I'd go for that.

Here is that old thread re: E6440 mini-PCIe slots: https://osxlatitude.com/forums/topic/10117-half-size-pci-wifibluetooth-card-for-airdrop Meantime, on the Net...

As they say in the Dortania documentation, get to know your hardware 1st and foremost... There are no M.2 slots in the Latitude E6440. Otherwise you'd have had no need for your mini PCIe-to-M.2 adapter (just for antenna adapters). Do consult the E6440 owner's manual or Dell's own support forum where this was discussed many years ago. The Latitude E6440 has 3 x mini-PCIe slots: 1 x full size (WWAN) which is combo PCIe/USB/mSATA (the one to use for a combo wifi+BT card) and 2 x half-size (WLAN + 2nd one under the WWAN slot). I know, I once had an E6440. I'm pretty sure we also have at least 1 old thread in which I actually illustrated those slots. Do use for forum Search facility... Space is a little tight for a BCM94360CD in the E6440 but I think it would fit in the WWAN slot. I'll give you the card's measurements. Re: Apple BCM94360CD, please refer to the dedicated thread we published back in 2014 in our R&D forum section. Another alternative to your defective BCM94360NG installation is to opt for a BCM4352-based mini-PCIe card such as the DW1550. It's supported in Big Sur and I understand it remains so in macOS Monterey, so...

-> moved to Wireless & Bluetooth support section. It's not a Latitude E6xxx related matter. No need for any kexts in OS X/macOS for this card, it's 100% natively supported even for Bluetooth. Regarding your signal-related issue, it could be a defective adapter board if you connected your laptop's antennas to the adapter's IPEX connectors and the BCM94360BG card to the adapter's MHF4 connectors (you did make those, right?). I assume you did make all the necessary antenna connections but I'd start by checking they're all properly made and nothing is loose. Careful with those MHF4 antennas, they can be tricky to put in place and the connectors tend to be fragile. An Apple BCM94360CD in a mini-PCIe adapter would have been a much better and much cheaper choice in your E6xxx laptop, whatever the model (all models have the required 4 x antenna wires). That card performs much better than any Fenvi BCM94360NG and with the added benefit of using IPEX connectors... Perfect for older laptops fitted with mini-PCIe WLAN slots/cards.