Hervé

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

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: