Hervé

You'll have to post a zipped copy of your bootloader EFI folder. Do specify the bootloader you're using and its version.

Ok, so I see that you've now switched to CFL mobile framebuffer 0x3E9B0000, faking iGPU is 0x039B and patched your framebuffer connectors from LVDS + 2 x DP: ID: 3E9B0000, STOLEN: 57 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000130B TOTAL STOLEN: 58 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 172 MB, MAX OVERALL: 173 MB (181940224 bytes) Model name: Intel HD Graphics CFL CRB Camellia: CamelliaDisabled (0), Freq: 0 Hz, FreqMax: 0 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 to 3 x HDMI: [3] busId: 0x04, pipe: 8, type: 0x00000800, flags: 0x000003C7 - ConnectorHDMI [1] busId: 0x01, pipe: 9, type: 0x00000800, flags: 0x000003C7 - ConnectorHDMI [2] busId: 0x02, pipe: 10, type: 0x00000800, flags: 0x000003C87 - ConnectorHDMI 03040800 00080000 C7030000 01010900 00040000 87010000 02020A00 00040000 87010000 Quite strange but I guess that as long as it works, all is well...

@Jazzoo For the benefits of other members, why don't you post the details of your changes and a zipped copy of your EFI folder?

Please post the hardware specs of your E7450, ideally put them in signature. Unlike NVME SSDs, there are usually no issues with SATA (or mSATA) SSDs and macOS on Hackintosh. Your issues probably result from some incorrect quirks in your OC config. Which pack did you use? You probably need to stick to those with versions 0.6.x. I would also suggest you check your BIOS settings and compare them with the ones I recommended for the E7250. In particular, make sure you set your E7450 in UEFI mode, that Legacy Option ROMs is set to enable and disk mode is set to AHCI. I'd also update your BIOS to latest version A24 if you're not already running it. https://osxlatitude.com/forums/topic/12177-e7250-bios-settings/#comment-93649 The E7x50 is starting to age but these Broadwell/HD5500 laptops are rock solid when it comes to installing and running macOS on them and everything is supported. Once you've checked your BIOS settings, you may want to give this Clover guide a try. Or Jake's own Clover guide too.

Intel Coffee Lake i5-9500T is fitted with UHD 630 iGPU, not HD 630. You opted for CFL framebuffer 0x093B0007 which is the recommended one for Coffee Lake desktops. https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md This CFL framebuffer defines 3 x DP ports by default: 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 You inject the following framebuffer patches: which change: connector type of con0 to HDMI (00080000) busid of con0 to 01 index of con2 to 02 pipe of con2 to 0A Alongside, you make injections for same values as natively defined in the framebuffer; these are therefore useless and should be removed: index of con0 set to 01 pipe of con0 set to 09 busid of con2 to 06 type of con2 to DP (00040000) I would suggest you remove all those connector patches and start again with the vanilla settings. Then try and identify which physical output goes against which connector in IOReg. But I would avoid ending up with 2 x connectors with same index; I fear that's wrong. With your current patches, you have the following connectors (i.e. video output ports) definition: [1] busId: 0x01, pipe: 9, type: 0x00000800, flags: 0x000003C7 - ConnectorHDMI [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x000003C7 - ConnectorDP [2] busId: 0x06, pipe: 8, type: 0x00000400, flags: 0x000003C7 - ConnectorDP 01010900 00080000 C7030000 02040A00 00040000 C7030000 02060A00 00040000 C7030000 Of course, conduct your experimentations by booting off a USB key so that you avoid breaking your existing OC setup in any way.

Only with OpenCore but this is Clover here, so no kext to declare in the config. There are elements of the Clover config available in the last posted EFI that need to be revised: boot args and ACPI dropped tables for instance but a few other things too: dropping SSDT CpuPm and Cpu0Ist is not required so those should be removed enabling C6 is not required and should be left disabled boot arg kext-dev-mode=1 is for Yosemite only; completely useless since any other OS X/macOSversion. I'd also try to switch from VirtualSMC & PlugIns to FakeSMC & PlugIns given that it seems you're experiencing trouble with former. There's also a good chance boot hangs because you're missing the USBInjectAll kext to support all your USB ports at startup; that can lead to having your USB installer not accessible during startup.

I don't believe the driver supports ALPS V8 properly; seems to stop at V7.

Can't see any of those new properties anywhere, no.

Open up your OC config file with apps such as OpenCoreConfigurator, ProperTree, PlistEditPro or Xcode. In Device Properties section, add the necessary properties. 1) for Audio, i.e. device at PciRoot(0x0)/Pci(0x1b,0x0), add: key: layout-id value: 12 type: NUMBER 2) for iGPU, i.e. device at PciRoot(0x0)/Pci(0x2,0x0), add: key: framebuffer-patch-enable value: 1 type: NUMBER key: framebuffer-fbmem value: 00008000 type: DATA Save your config, reboot, execute Reset NVRAM at OC Picker and restart; that's it. See here for details.

If you look into your BIOS Info you should see your audio codec. Afaik, audio codec of all E6x30 is IDT 92HD93; this works with Lilu + AppleALC kexts and layout-id 12. CodecCommander kext is usually required too. Your OC config is simply missing that layout injection, that's all. Graphics glitches are due to 16MB default Memory Size in the Capri Framebuffer and must be reduced to 8MB; just add the appropriate injections against iGPU at PciRoot(0x0)/Pci(0x2,0x0) in your OC config. See the various E6x30 guides already published on the forums and the numerous threads about E6x30 models with attached configs/EFI folders.

The make does not matter; the chipset does. Did you consult the inventory linked above?

AR5B22 is based on Atheros AR9462, a chipset that never was natively supported and required a re-written driver. Afaik, these cards never worked very well under macOS and, imo, are best avoided. https://osxlatitude.com/forums/topic/11138-inventory-of-supportedunsupported-wireless-cards-2-sierra-monterey

E6440's TouchPad works perfectly with Dr Hurt's driver. https://osxlatitude.com/forums/topic/8285-refined-alps-touchpad-driver/ Other kexts not required: NoTouchID, noVPAJpeg, Apple1GB, HibernationFixUp, HoRNDIS, 2nd USBInjctAll_v0.1.7,

Post yours, we'll try to fix whatever may be incorrect. add your system's specs too. Either in the post or, ideally, in signature.

Just revert to what you previously had then. For Intel Wireless, please follow the ITLWM process available here: https://openintelwireless.github.io

Looks like you re-used an existing EFI folder without modifying it to match your own hardware. You have an Intel wireless card so all those patching kexts for Broadcom Bluetooth are useless and you can remove them. Your config also contains many useless/inapplicable, sometimes overriding, properties injections; they're mostly cosmetic and should not cause problems but it'd be preferable to remove them to avoid all possible confusion and doubts on the matter. Better to stick to the essential and a minimal set of configuration before jumping into fancy stuff. Your boot issues probably result from incorrect quirks being set; do try and follow the Dortania guidance for Skylake laptops: https://dortania.github.io/OpenCore-Install-Guide/config-laptop.plist/skylake.html

A simple line stating Intel i5-6300U CPU with Intel HD 520 graphics would have sufficed... Anyway, so it's a 6th gen Skylake model, not 7th gen Kaby Lake as you incorrectly stated; not a small detail or small difference for sure... As they state in the Dortania guidance:

Ok, that confirms graphics initialisation issue and since I've just noticed you opted to inject IntelGraphicsFixUp kext for some reason, I suggest you remove that kext. It should not be required on an Ivy Bridge/HD4000 laptop.

@tanzahost please refrain from posting in multiple threads about the issues you encounter hackintoshing your 7480; I suggest you stick to this one. Please post the exact model of CPU, that'll determine your exact iGPU model. Intel HD graphics is insufficient. Look it up in your BIOS info.

I'm pretty sure that the error messages aren't an issue at all; it seems that you're just getting stuck at graphics initialisation. Not surprising if you're using that Yoga 13 EFI; it's just unsuitable. One thing I'd like to suggest is replace VirtualSMC & its plugIns by FakeSMC and its PlugIns. You can grab it in the various packs I posted in, say, my Dell Latitude E6230 guides.

There are many existing threads about Latitude 7480. If anything else guys, do post your system's specs. Those laptops exist in Skylake and Kaby Lake models... And no double post please (post deleted).

Check what SysInfo->Wifi reports in terms of reported connection speed and channel. It's probably worth experimenting with some of those AirportBrcmFixup boot args such as brcmfx-country=#a. https://github.com/acidanthera/AirportBrcmFixup

The Wifi part of the wireless card is PCIe based whilst the Bluetooth part is USB used. As such, slow Wifi performance cannot be linked to an issue with USB port mappings. What you see in Hackintool is normal, it's the speed of the USB devices, not the speed of the ports themselves.

I don't think it'd have any influence on Sleep/Wake but it certainly could on a boot time perspective but Samsung 970 Evo Plus was not natively supported unless firmware was updated; can't say which version but it'd be worth checking whether you run on the latest version or not: https://semiconductor.samsung.com/consumer-storage/support/tools/

Quick answer before I get the time look at your posted EFI + IOReg. Too much RAM (32GB) -> No. Slow Wifi (capped at 250Mbps) -> you're probably on a 2.4GHz network; you'll have to hook to a 5GHz network to get beyond this and reach up to 867Mbps I no longer have a 7490 but, during the time I had one, sleep/wake/restart never were a problem at all. Must be some incorrect settings or issues with the kexts you inject. I suspect ACPI patches and/or CPU power management. Start by disabling those CPUFriend kexts if you copied then from a repo rather than generate your own data (always a bad idea for the data kext, it has to match your CPU and desired power settings).