Hervé

Please specify your computer model and its specs. Ideally, publish those in your signature like most people do.

OP's obviously got a 7480 with the QHD touchscreen... See the product's documentation on Dell web site.

You should also remove these kexts found in the original pack you got from Github: IOGraphicsFamily -> can't imagine what this would do; a patched version used to be required many years ago to fix the garbled Apple logo at boot time but it's long been deprecated CPUFriend + CPUFriendDataProvider -> the data kext would be specific to the OP's i5-8265U and should therefore be re-generated for your own CPU. Then, of course, update all other kexts to latest version.

Yup, just download latest OC version and make your own EFI using the guidance posted at Dortania. All required kexts are known by now, the E6440 is an old Haswell laptop with all fitted hardware fully documented. Tons of threads about this model on the forum too.

Seeing what you currently inject for iGPU properties, did you try the settings recommended in the Whatevergreen User Manual instead? Probably a good starting point as an alternative to this which clearly is incorrect: And experiment with other framebuffers such as 0x3EA50009 to begin with.

Please post your laptops spec, ideally add them in signature. Several people encountered difficulties with Whiskey Lake models/platforms.

For your signature: click on your account name at top of forum Window, then go to Account Settings->Signature. About your graphics setup: Strange that you opted for MBP15,2 (a Coffee Lake model) on your Kaby Lake/HD620 laptop when you'd be expected to use MBP14,1 (a Kaby Lake model)l. I invite you to try it out. KBL framebuffer 0x59160000 certainly is correct for KBL HD620 and your connector patches are all good though con0's is not required since you inject the exact same thing as what's natively defined in the framebuffer. You correctly swap connector's type for HDMI and DP given that, in the vanilla FB, con1 is DP and con2 is DP: ID: 59160000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x00000B0B 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: 0x00000800, flags: 0x00000187 - ConnectorHDMI 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00080000 87010000 You could also experiment with KBL FB 0x591B0000 (it's the recommended one for KBL HD620). It requires patching con1 alldata to same as FB 0x59160000 or you won't get HDMI output of course: ID: 591B0000, STOLEN: 38 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000130B TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 136 MB, MAX OVERALL: 137 MB (144191488 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 [2] busId: 0x04, pipe: 10, type: 0x00000800, flags: 0x00000187 - ConnectorHDMI [3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 02040A00 00080000 87010000 -> Needs to be patched to 01050900 ... 03060A00 00040000 87010000 -> can stay as is afaik, no need to patch to 0204... I've never seen anyone injection a pci-asm-default value for an iGPU. Did you try HDMI output without injecting this parameter? Where did you get the idea to inject a different framebuffer-flags value from? How did you choose the value?

What's your CPU/iGPU? What SMBIOS do you use? What iGPU properties do you inject?

Indeed, once you increase DVMT to 64MB or 96MB in BIOS, the fbmem + stolenmem patches become irrelevant and even counter productive since they usually aim to reduce the default values of the selected framebuffer so that the sum of them remains below 32MB. In your case, it looks like 64MB is the max value you can set for DVMT pre-allocated memory. May be you can experiment with DVMT total values (256/128/Max).

Did you check the default DVMT settings of your 7480? Under macOS, DVMT must usually be set to 64MB or 96MB to obtain 4K output; afaik, you won't get it if DVMT is set to 32MB even if you patch the DVMT settings (fbmem + stolenmem) through properties injection. With DVMT set to 64MB or 96MB (BIOS mod through Grubshell, see our FAQ topic on the matter or my E7270 guide), I can get 4K @24-30Hz out of HDMI and 4K@60Hz out of mDP on my Skylake/HD520 E7270 laptop. Can't see why it'd be different on your 7480, unless it's the TB port that's causing the issue under macOS of course. Don't hesitate to post a zipped copy of your bootloader's EFI folder so that we can check your settings. Do post your system's specs in signature since they're are 6th gen and 7th gen 7480...

Sorry, don't understand what you mean. In Ventura, you hide or show such OS-related menu bar icons from System Settings->Control Centre. It's not an app icon that goes away once you close the app. If you've no options to hide/shows this icon in the Control Centre, I'm afraid you'll have to live with it. It'll only go if the hardware goes... I'm not 100% sure of this but this icon may appear due to some properties you inject in your bootloader's config. I'm thinking specifically about the "unknown" piece of hardware that's listed... You'd have to post a zipped copy of your bootloader's EFI for us to check this out. What's the issue of having the icon displayed anyway?

No, it's not for an SD card. In Ventura, SD cards appear as memory card icons on the desktop just as with previous OS X/macOS versions. They're considered as storage devices, just like USB disks or USB keys: @Hecatomb This menu bar icon usually is for an ExpressCard (54 or 34). See this thread where ExpressCard USB3.0 controllers were discussed. Can't remember if he same applies to USB-c devices (other than USB-c disks/keys of course). Post a zipped copy of an extracted IOReg (using IORegistryExplorer App) and of a saved System Report. It's probably some other odd piece of hardware on the motherboard. I've recently read somewhere of recent Hackintosh computers that displayed the same behaviour; can't remember if these were desktops or laptops. Anyway, if you have no ExpressCard or PCIe hardware that would explain this, just see if you can disable the option that displays this in the menu bar from System Settings->Control Centre.

I don't have them at hand, please use the forum Search facility. And, in case you had not noticed, we also have a dedicated section dedicated for full installation guides (only)...

To me, there are several things incorrect in your OC setup and I'd start by removing the following kexts from your config + kexts folder: CpuTscSync HibernationFixup Can't see why you'd need them. I never did. Some of your iGPU property injections appear quite odd to me too, but that's not something likely to prevent the laptop from shutting down, only cause issue with HDMI output. Most 7490 were fitted with 8th gen Kaby Lake R CPUs and therefore use MacBookPro15,2 SMBIOS. Your config shows you've opted for MacBookPro14,2 SMBIOS, i.e. a 7th gen Kaby Lake model. You need to post your system's specs, ideally add them in signature like most people do here.

Lobby section is for personal introduction. Moving this thread to appropriate Latitude 7000 Series support section. Please make every effort to post in the appropriate sections of the forum. By cooler, you mean the fan? There are several existing threads about the Latitude 7490 on our forum; read them up and check the various bootloader packs posted in them. Yours is probably incorrect but, until you actually post a zipped copy of it... who knows? I had that laptop for a couple of years and ran Mojave and Calalina on it; 'never had any issue of any kind with it as a Hackintosh, certainly not with shutting it down.

Released Jul 27th, 2022. Build 22A5311f. Ok on my Skylake/HD520 Latitude E7270 with exact same/unmodified Clover r5148 setup previously used for 13.0 beta 3. Status recap: graphics acceleration with some minor defects brightness control touchscreen HDMI output mini-DP output audio (incl. HDMI & DP audio) LAN wireless & Bluetooth (BCM9460CS2) touchPad USB ports sleep & wake SD card reader

Ace! What's new compared to the existing guides and existing EFI/bootpacks such as those posted by Jake Lo here?

@Saqer1111 Click on View button at top left corner and select View all devices. What kind of disk do you have in that E6440? Regular SATA-III 2.5" HDD? SATA-III 2.5" SSD? mSATA SSD in mSATA slot? You'll have to set disk mode to AHCI in BIOS or it just won't work. Are you using a full vanilla USB installer or a distro which may be missing files and drivers? There are several threads about the E6440 on the forum, I'm sure several of them provide copies of EFI folder you may be able to re-use, partially or fully.

Target macOS release: Monterey 12.x Finally got round to do it! This is an OpenCore-based installation using the vanilla method detailed below: Working: full graphics acceleration on GT730 -> with Kepler patch since there are no drivers natively provided in Monterey, Apple having dropped all nVidia dGPUs on RX560 -> OOB multi-display (with Lilu + WEG): on GT730 -> DVI + HDMI OOB, VGA with NVCAP value 050000000000FFFFFFFF00000000000E00000000 on RX560 -> DVI + HDMI + VGA OOB audio, including HDMI, microphone input and headset output (with AppleALC + all layouts or VoodooHDA) FastEthernet LAN connection (with 82566MM or AppleIntelE1000 kext, patched if necessary for PCI id 8086:10c0) 19-in-1 card reader OOB CD/DVD RW drive OOB front and rear USB ports (OOB) partial CPU power management with OpenCore, legacy Core2Duo platform oblige (LFM + HFM only since OpenCore does not generate C States/P States) sleep (Energy Saver settings, Apple menu, PWR button) & wake (PWR button, USB keyboard/mouse) USB or Wireless keyboard and mouse (with IOHIDFamily's isSingleUser function OpenCore patch) Not working: N/A Not tested: N/A GeekBench v4.4.4 (64bit) gives a 3900+ rating with MacPro3,1 SMBIOS: This old desktop PC only operates in legacy BIOS mode, not UEFI. This is a problem for installing Monterey from scratch with a USB installer because, in legacy BIOS mode, OpenCore does not appear capable to dynamically obtain the volume UUID of the temporary macOS installer partition/volume (created during the installation process) and properly define an essential parameter called msu-product-url. This causes the installation process to fail proper execution and, instead, triggers computer reset + continuous boot loop of the temporary volume, the installation therefore never reaching completion. The workaround to this problem is detailed below. When installing Monterey, the temp installation will be created on the target disk/partition volume whose UUID can be readily obtained and passed through NVRAM parameter msu-product-url to the installation process. This was described in this thread by pac-man at InsanelyMac, credits to him. Basically, the UUID of the target Monterey volume is obtained through the diskutil line command and the resulting value is used to create a fully-defined path for the temp installation volume that is stored in NVRAM parameter msu-product-url. This NVRAM parameter is essential to complete the installation process. Please note that installing Monterey on this old desktop PC takes some time to complete (even on a SATA SSD) so set aside an hour or two... 1) Preparation OpenCore needs to be setup in legacy mode to boot the Vostro 200 computer, lack of UEFI BIOS mode oblige. This is well documented on the Dortania OpenCore GitHub repo which I invite everyone to refer to. the OC 0.8.2 pack provided below may be used on a USB key or the existing disk's EFI partition as bootpack to reboot the system during the Monterey installation phases, then boot Monterey once it has been fully installed. key elements to note in that config are: the IOHIDFamily kext patch applied to the _isSingleUser function; it's required to obtain working USB keyboard & mouse, they don't work without the patch. This is detailed in the Dortania's documentation. additional msu-product-url parameter to be added under NVRAM->7C436110-AB2A-4BBB-A880-FE41995C9F82 UUID UUID as per pac-man's thread at InsanelyMac. 2) 12.x USB installer creation Using a USB key of 16GB minimum, create a Monterey USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Catalina installation package (eg: /Applications if freshly downloaded) <USB key> = name of formatted USB volume (eg: USB_8GB) The process will take several minutes. Once completed: mount the USB installer's EFI partition. If it does not exist, create it (size 200MB, format FAT32). unzip the following OpenCore bootpack and copy the resulting EFI folder + boot file to the root of the mounted EFI partition: Vostro200_Monterey_OC_0.8.2_Pack.zip 3) 12.x installation boot the Monterey USB installer. at the OpenCore picker, select the "Install macOS Monterey" entry. proceed with installation, creating & formatting the target Monterey installation through Disk Utility as/if required. on 1st reboot, do not boot the newly created Macintosh HD or macOS installer partition but boot the Monterey USB installer again. Open up Terminal and collect the volume UUID of the target partition in order to store additional NVRAM parameter msg-product-url into your OC config. Note down the value returned by the command: diskutil info /Volumes/<name of target Monterey disk/partition> | grep "Volume UUID" | awk '{print $3}' Open up your OC config file and, under NVRAM->7C436110-AB2A-4BBB-A880-FE41995C9F82, add msu-product-url <obtained UUID value>/macOS%2520Install%2520Data STRING Save your OC config and reboot At the OC picker, select the Macintosh HD or macOS installer partition. The Monterey installation will now resume. The process normally requires to boot this temp partition twice only; however, should it hang or freeze, reboot that partition as many times as required until the OC Picker offers you the final Monterey partition with the name you initially created it with. Reboot this final partition until you reach Monterey 1st boot. 4) Post-installation tuning once the Monterey installation has completed and Monterey first boots, complete the initial configuration tuning. Here too, this may take an unusual and very long time, especially with a natively unsupported graphics card like a Kepler one; just hang in there. once at the Monterey desktop, mount your disk's EFI partition and copy the OpenCore EFI folder as necessary/appropriate in order to boot Monterey via OpenCore. proceed with usual macOS fine-tuning (wireless setup, hibernation disabling, refresh of serial numbers, etc.). If running Monterey on an unsupported graphics card (eg: nVidia Tesla/Kepler card), install the necessary drivers to obtain graphics acceleration. This can be done manually (only for the expert), with OCLP (recommended) or other existing tool. I apply OCLP root patches for my Kepler card. Reboot into your finalised Monterey installation.

-> Moved to proper hardware support section and specified the hardware in thread tile... Broadcom BT module of DW1820A is not well supported. You're most unlikely to get it working and if you do, it'll hardly work reliably. 'been there and gave up in the end.

You must have missed that you just can't boot a macOS installer that way; you must 1st create the installer on your USB key, then install the bootloader (OpenCore or Clover), then the relevant bootlick (bootloader config file + Hackintosh-relevant patched ACPI tables + kexts). You create a macOS USB installer using the createinstallmedia command (details on the Net or in our numerous guides) off an existing Hack or Mac. If you only have Windows, lookup the dedicated thread in our FAQ section.

Fix your USB ports, make the required mappings.

Of course you can edit the config. You must do it since it does not match your actual hardware.

Unless you too have a Broadcom BCM4352 wireless card, you need to adjust this OC setup.

Post your zipped EFI folder.