Hervé

No need for -lilubetaall boot arg either.

Start by updating your add-on kexts to latest versions.

What Jake was asking you to do was disable the XhciPortLimit quirk in your config, i.e. unselect/untick/remove it ... https://dortania.github.io/OpenCore-Post-Install/usb/#macos-and-the-15-port-limit

Re: Intel Wifi cards, just consult the ILTWM site where you'll find the list of compatible cards. Statements such as "the original Intel card" are totally meaningless without any reference to the exact model. Questions about legality keep resurfacing every now and then. By now (2022) everything that needed to be said/written has been said/written; do as you wish, this forum certainly ain't a place to ask permission to build a Hackintosh, especially considering you've been Hackintoshing for over a decade... You've been a member since late 2020 so, if you've not done it yet, now is a good time to read our published rules and enlighten you on what's not allowed on the forum. 'never had any trouble injecting the SMBIOS details and I've always used random values for ROM rather than the host's MAC address. The Dortania guide looks pretty clear to me in that respect. As an experienced Hackintosher (over a decade), you should have no difficulty there. The Generate buttons do work in OCC -at least for me- (or in CC to that effect), maybe you need to update the version(s) you run. Chameleon is long dead, today only Clover and Opencore remain under active maintenance and development. You'd only use Chameleon for an (old) installation of an older OS X/macOS build certainly not for Monterey! As an experienced Hackintosher, you should long know this. Your questions re: cloning to appear linked to a desire of yours to build Hackintosh laptops for resale. Understand that we can't assist you on this matter. This community does not provide support for commercial activities around Hackintosh. And we're not going to help you make money out of free support.

It's indeed natively supported hence why I said it was unnecessary to inject it since it's the iGPU's native id... But I understand that you may nevertheless need to fake id 0x3E9B. Se here. For the rest, I invite you to read this: https://osxlatitude.com/forums/topic/8238-supportedunsupported-gpus-graphics-cards

Your iGPU device id injection is not only unnecessary but incorrect. Intel i7-10750H CPU integrates 10th gen UHD graphics (i.e. UHD 620) with iGPU id 0x9BC4. When you want to fake an iGPU id, you need to inject the id in the correct endianness for macOS, i.e. lowest significant byte 1st. Eg: 0x9BC4 is specified "C49B0000 DATA".

Your system's not crashing; just failing to initialise graphics due to incorrect settings. If DVMT is already preset to 64MB in BIOS, there's no need for you to patch framebuffer memory and DVMT in your config so get rid of those patches. You must however fake iGPU id 0x5916. For the rest, experiment with the various mobile KBL framebuffers if the recommended ones don't appear to work. Also make sure you use MacBook Pro15,2 SMBIOS. The following properties injection should suffice: AAPL,ig-platform-id 00001659 DATA // or maybe 00001B59 device-id 16590000 DATA framebuffer-con1-enable 01000000 DATA framebuffer-con1-type 00080000 DATA hda-gfx onboard-1 STRING Just in case, you may want to replace the disable-external-gpu property by boot arg -wegnoegpu. Also make sure Optimus is enabled in BIOS or you'd only run on the nVidia dGPU which will be unsupported.

Not for the device id, absolutely not. https://dortania.github.io/OpenCore-Install-Guide/config-laptop.plist/kaby-lake.html#deviceproperties

You're injecting incorrect properties for KBL R UHD620 iGPU: iGPU device id 0x87C0 is for Amber Lake iGPUs, not Kaby Lake Refresh... See the WhateverGreen user manual: https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md For Kaby Lake R platform with UHD620 graphics, you should be using: KBL framebuffer 0x591B0000 iGPU device id 0x5916 On my Kaby Lake R Latitude 7490 with UHD620 graphics, I was successfully using: KBL framebuffer 0x59160000 iGPU device id 0x5916 as described in my associated guide available here and only patched 2nd connector con1 for HDMI type (I don't fully understand why you inject properties for all 3 connectors con0, con1 and con2).

Wouldn't a copy of your EFI folder be more useful?

Also post your system's specs, ideally in signature. Only the Intel iGPU is supported in macOS, not the nVidia dGPU if you have that model. As Jake said, High Sierra is the last version to officially support HD3000 graphics. Patches are available for Mojave and Catalina that allow to run HD3000 graphics in OpenGL mode only (no Metal support) but it's not really recommended, HD3000 graphics being buggy enough when fully officially supported. Forget about Big Sur and Monterey though. Don't hesitate to consult our E6220 guide in the Guides section.

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#deviceproperties https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/intel-gpu.html#kaby-lake-refresh-coffee-lake-comet-lake-8xxx-9xxx-2 Comet Lake graphics

Touchscreens usually are USB-based. I found that, with my Skylake Dell Latitude E7270 laptop, touchscreen worked OOB up to Catalina. In Big Sur and later, Apple apparently dropped support for some legacy USB HID stuff (details of which elude me at this point) but I was able to recover working touchscreen after applying the USB HID Fix in my bootloader config.See here or at Dortania for details. For the rest, let's keep the thread on-topic please.

Don't use the 10.6.8 kernel for your 10.6(.0) installation. I doubt that'll work. Use the kernel for that version. Extract it from your Snow Leopard DVD/image. But you must be doing something wrong because making a USB installer with myHack does not require to manually add the kernel file at the root of the USB key (nor of the final installation).

Turing-generation nVidia GeForce GTX 1650 Ti is unsupported and must disabled. You can only run macOS with the UHD630 of this 10th gen Comet Lake platform. https://osxlatitude.com/forums/topic/8238-supportedunsupported-gpus-graphics-cards Please specify bootloader used (OpenCore vs. Clover) and post a zipped copy of your EFI folder. If using OpenCore, don't hesitate to follow the relevant guidance. https://dortania.github.io/OpenCore-Install-Guide/config-laptop.plist/coffee-lake-plus.html

You inject KBL framebuffr 0x591E0000 and Intel HD620 graphics in your config, so we'll assume your NUC is fitted with a Kaby Lake CPU. Ideally, do post your system's specs. Lack of video on this eDP-connected screen may result from a mix of incorrect settings with KBL framebuffer layout and SMBIOS: eDP connectors would usually be expected on Apple MacBook and iMac computers, not really on Mac mini. As such, try and target Kaby Lake MacBookPro or iMac models in your experimentations. regarding KBL framebuffers, you'll probably have to experiment with the various layouts available and listed in the Whatevergreen user manual. You opted for KBL framebuffer 0x591E0000 which is a mobile layout (connector type 02000000 for con0 output port) ID: 591E0000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000078B TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 103 MB, MAX OVERALL: 104 MB (109588480 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), 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: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00040000 87010000 but you also chose to patch the connectors. Any particular reason, especially for con0, the LVDS/eDP one for which you patched the pipe number? I'd have started with the default settings, only adjusting the relevant connector (most likely con1) to HDMI type if HDMI audio is expected out of it. With regards to 4K support, keep it mind that it's closely related to DVMT settings and you would usually need to have at least 64MB (if not 96MB) of pre-allocated memory assigned be able to gain 4K output under macOS. If you can set this directly in BIOS, great, if not, you'll have to consider settings it through Grub shell, having 1st identified the associated variable in BIOS code/tables. Given that your OC config shows no patching for DVMT or framebuffer memory, we can only assume that your current DVMT settings exceed the chosen framebuffer's 34MB requirements and is set to, at least, 64MB. You may also wan to add WEG boot arg igfxonln=1 to ensure all your video output ports are enabled. https://github.com/acidanthera/WhateverGreen

You've used the correct version of myHack for SL, right?

Thqt's the trouble with Baio77. He tends to provide stuff to test without any form of explanations. I'm not even sure he's working on your actual shutdown issue. He mentioned other things he wanted you to test in an erlier post, hence why I asked him to refrain from going off-topic.

The packs I posted were for SL 10.6.8. I checked them again (but it's been so long and I no longer have any D Series) and maybe you ought to remove the kext called Patched_10.7_AppleRTC.kext from the Extra/Extensions folder. Possible the patched Intel Framebuffer kext too, at least until you've updated to 10.6.8. Can't see anything else. You picked the correct pack re: screen resolution, right?

Don't remember ever seeing that kind of error with SL on a D620 before. Maybe your USB installer ain't that right... If you have a retail 10.6(.0) DVD, you may use Nawcom's modCD as an alternative. It'll get you to a minimal SL installation from which you can create your myHack installer and experiment again. The old app is available in our 3rd party apps forum subsection.

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.