Hervé

Look at the usual place... https://github.com/OpenIntelWireless/itlwm

Generally speaking, generic/3rd party batteries tend to be utter crap and often seriously decline after only a few months. I guess you'll see soon enough. Not that many things you can do to optimise battery; you've already enabled low power mode but who knows if it's of any use on a Hack. Other possible actions to consider: reduce screen brightness adjust screen saver & sleep/hibernate settings revise CPU power settings (tuned CPUFriend kexts vs. native kernel CPU power management or vice versa) disable turbo boost on battery use SSD instead of mechanical HDD Battery settings may also differ according to SMBIOS/Mac model. That's about it...

@dadablaze No double/multiple posts on the forum please. See our published rules.

Nothing here for this laptop afaik. You'll have to make one up, starting with basic usual settings for a regular Kaby Lake/HD620 laptop, then adding whatever may be required for your hardware accessories (LAN, WLAN/Bluetooth, audio, SD card reader, etc.). Can't remember if Samsung PM961 SSD is supported, unlike its PM981/PM991 brothers which don't allow to install/run/boot macOS on them. SATA Express? Wow, can't be many machines fitted with that.

NB: This is a revival of the article I had initially published at InsanelyMac to answer recurring questions that had been raised in the Opencore thread that lives there. Posted October 2, 2021 The Dortania documentation refers to the DVMT pre-allocated memory or "stolen memory" when they mention "memory reserved for the iGPU". Years ago, @Firewolf described in details the relationship between stolen memory and DVMT pre-allocated memory on his blog: https://www.firewolf.science/2015/04/guide-intel-hd-graphics-5500-on-os-x-yosemite-10-10-3/ There's a more recent thread from him here: https://www.insanelymac.com/forum/topic/345377-surface-pro-patch-the-framebuffer-properly-to-get-rid-of-the-dvmt-assertion-patch/ It can be difficult to understand and differentiate DVMT pre-allocated memory, stolen memory, framebuffer memory, cursor memory, framebuffer size, cursor bytes, etc. And all of these have got nothing to do with VRAM of course... Some of us are familiar with the information provided by @Pike R Alpha many moons ago, the WhateverGreen User Manual or the Hackintool app though none of those clearly define what the various memory instances are. Several years ago, @Rehabman also attempted to explain this and his writings somehow collided with most people's comprehension of things. For instance, when @Pike, WhateverGreen or Hackintool refer to stolenmem and fbmem, @Rehabman spoke of framebuffer memory size and cursor bytes. In the case of the Haswell Azul framebuffer layouts, @Rehabman also spoke of the DVMT pre-alloc requirements when the others speak of stolenmem. Inevitably, this can lead to confusion... Definitions: See wikipedia and Google searches. VRAM = Video RAM. Common definition is that it stores the pixels and other graphics data rendered on a computer screen. DVMT = Dynamic Video Memory Technology. A technology used by Intel to dynamically allocate system memory to use as video memory to handle graphics. DVMT pre-allocated memory is the minimum amount, in multiples of 32MB, that will be allocated to the iGPU for handling graphics. By far and large, manufacturers set this to 32MB by default in BIOS (or certainly used to). Framebuffer = a memory buffer held in RAM and containing a bitmap of a video frame, i.e. all the data related to the pixels of an image to be displayed on screen (eg: colours, resolution, etc.). Stolen memory = basically, this is the same as the DVMT pre-allocated memory. As far as Apple's framebuffer drivers/kexts are concerned: framebuffer size (aka stolenmem for WhateverGreen*) = the size, in bytes, of a framebuffer layout (it may change according to image characteristics), as defined in the driver/kext. cursor bytes (aka fbmem for WhateverGreen*) = the size, in bytes, of a framebuffer layout's overlay used for handling mouse cursor (without modifying the framebuffer's data), as defined in the driver/kext. framebuffer VRAM (aka unifiedmem for WhateverGreen) = the max. amount, in bytes, of VRAM allocated by a framebuffer layout, as defined in the driver/kext (since Haswell and Yosemite, this usually is 1536MB). * As stated above, I believe that Whatevergreen only got it right for Haswell Azul framebuffer layouts with which stolenmem, fbmem and cursormem match their target. Thereafter, I'm of the opinion that WhateverGreen used incorrect names where stolenmem means the actual framebuffer size and fbmem means the actual cursor bytes (size), as stated by @Rehabman. Mac OS X/OS X/macOS graphics framebuffers: Let's start by looking at a few examples as illustrated in the WhateverGreen User Manual. 1) Haswell Azul mobile framebuffer 0x0a260006 (used for HD4200/HD4400/HD4600 iGPUs on laptops): ID: 0A260006, STOLEN: 32 MB, FBMEM: 19 MB, VRAM: 1536 MB, Flags: 0x0000000F TOTAL STOLEN: 52 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 116 MB, MAX OVERALL: 117 MB (123219968 bytes) Camellia: CamelliaDisabled (0), Freq: 2777 Hz, FreqMax: 2777 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000030 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP [2] busId: 0x04, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP 00000800 02000000 30000000 01050900 00040000 87000000 02040900 00040000 87000000 If we look inside the binary code of the Haswell Azul framebuffer kext, we'll find: 0600260A 01030303 00000002 00003001 00006000 00000060 D90A0000 D90A0000 00000000 00000000 00000800 02000000 30000000 01050900 00040000 87000000 02040900 00040000 87000000 FF000000 01000000 40000000 0F000000 01010000 04000000 00000000 0E000000 00000000 which translates to: 0600260A -> layout id (AAPL,ig-platform-id) 01 -> mobile type (framebuffer-mobile) 03 -> 3 x pipes (framebuffer-pipecount) 03 -> 3 x ports (framebuffer-portcount) 03 -> 3 x memories (framebuffer-memorycount) 00000002 -> 32MB stolen mem (framebuffer-stolenmem) // Rehabman's DVMT-prealloc requirement 00003001 -> 19MB FB mem (framebuffer-fbmem) // Rehabman's framebuffer size 00006000 -> 6MB Cursor mem (framebuffer-cursormem) // Rehabman's cursor bytes 00000060 -> 1536MB VRAM (framebuffer-unifiedmem) D90A0000 -> Backlight freq 2777MHz D90A0000 -> Max. backlight freq 2777MHz 00000000 00000000 00000800 02000000 30000000 -> port #1/FB@0: index 00, busid 00, pipe 0800, type 02000000=LVDS/eDP (framebuffer-con0-type), flags 30020000 01050900 00040000 87000000 -> port #2/FB@1: index 01, busid 05, pipe 0900, type 00040000=DP (framebuffer-con1-type), flags 87000000 02040900 00040000 87000000 -> port #3/FB@2: index 02, busid 04, pipe 0900, type 00040000=DP (framebuffer-con2-type), flags 87000000 FF000000 01000000 40000000 0F000000 01010000 04000000 00000000 0E000000 00000000 2) Broadwell BDW mobile framebuffer 0x1626006 (used for HD5300/HD5500/HD5600 iGPUs on laptops): ID: 16260006, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x00000B0B TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes) Camellia: CamelliaDisabled (0), Freq: 2777 Hz, FreqMax: 2777 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - ConnectorLVDS [1] busId: 0x05, pipe: 11, type: 0x00000400, flags: 0x00000507 - ConnectorDP [2] busId: 0x04, pipe: 11, type: 0x00000400, flags: 0x00000507 - ConnectorDP 00000800 02000000 30020000 01050B00 00040000 07050000 02040B00 00040000 07050000 If we look inside the binary code of the Broadwell BDW framebuffer kext, we'll find: 06002616 01030303 00002002 00005001 00000060 D90A0000 D90A0000 00000000 00000000 00000000 00000800 02000000 30020000 01050B00 00040000 07050000 02040B00 00040000 07050000 FF000000 01000000 40000000 0B0B0000 01010500 00000000 05000000 00000000 04000000 00000000 00000000 00000000 00000000 00000000 C8000000 which translates to: 06002616 -> layout id (AAPL,ig-platform-id) 01 -> mobile type (framebuffer-mobile) 03 -> 3 x pipes (framebuffer-pipecount) 03 -> 3 x ports (framebuffer-portcount) 03 -> 3 x memories (framebuffer-memorycount) 00002002 -> 34MB stolen mem (framebuffer-stolenmem) // Rehabman's framebuffer size 00005001 -> 21MB FB mem (framebuffer-fbmem) // Rehabman's cursor bytes 00000060 -> 1536MB VRAM (framebuffer-unifiedmem) D90A0000 -> Backlight freq 2777MHz D90A0000 -> Max. backlight freq 2777MHz 00000000 00000000 00000000 00000800 02000000 30020000 -> port #1/FB@0: index 00, busid 00, pipe 0800, type 02000000=LVDS/eDP (framebuffer-con0-type), flags 30020000 01050B00 00040000 07050000 -> port #2/FB@1: index 01, busid 05, pipe 0B00, type 00040000=DP (framebuffer-con1-type), flags 07050000 02040B00 00040000 07050000 -> port #3/FB@2: index 02, busid 04, pipe 0B00, type 00040000=DP (framebuffer-con2-type), flags 07050000 FF000000 01000000 40000000 0B0B0000 01010500 00000000 05000000 00000000 04000000 00000000 00000000 00000000 00000000 00000000 C8000000 3) Skylake SKL mobile framebuffer 0x19160000 (used for HD520/HD530/HD540 iGPU on laptops): ID: 19160000, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000090F TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes) Model name: Intel HD Graphics SKL 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 We can't look at the binary code of the Skylake SKL framebuffer because Apple changed the way things are coded inside but it basically translates as follows: 00001619 -> layout id (AAPL,ig-platform-id) 01 -> mobile type (framebuffer-mobile) 03 -> 3 x pipes (framebuffer-pipecount) 03 -> 3 x ports (framebuffer-portcount) 03 -> 3 x memories (framebuffer-memorycount) 00002002 -> 34MB stolen mem (framebuffer-stolenmem) // Rehabman's framebuffer size 00005001 -> 21MB FB mem (framebuffer-fbmem) // Rehabman's cursor bytes 00000060 -> 1536MB VRAM (framebuffer-unifiedmem) 6C050000 -> Backlight freq 1388MHz 6C050000 -> Max. backlight freq 1388MHz 00000800 02000000 98000000 -> port #1/FB@0: index 00, busid 00, pipe 0800, type 02000000=LVDS/eDP (framebuffer-con0-type), flags 98000000 01050900 00040000 87010000 -> port #2/FB@1: index 01, busid 05, pipe 0900, type 00040000=DP (framebuffer-con1-type), flags 87010000 02040a00 00040000 87010000 -> port #3/FB@2: index 02, busid 04, pipe 0a00, type 00040000=DP (framebuffer-con2-type), flags 87010000 With the exception of the Haswell Azul framebuffer, we can see that Broadwell BDW and Skylake SKL framebuffers define framebuffer size (WEG's stolenmem) and cursor bytes (WEG's fbmem) characteristics and no DVMT pre-allocated memory (i.e. proper stolen memory). This extends to Kaby Lake KBL framebuffers and later. In my opinion, it's fair to say that @Rehabman's description and wording are the most appropriate/best ones when the WEG view of things got somehow misled by following through on the Haswell framebuffer decoding. To me, there was some mixup, leading to confusion and the said confusion has remained ever since... Confusion... why? Because of several things: 1) the observation that the Haswell Azul framebuffers used on Hacks (0x0D220003 for desktops and 0x0A260006 for laptops) defined: a DVMT pre-allocated memory (= Stolen memory) size of 32MB a framebuffer size of 19MB a cursor bytes of 0MB (desktops) and 6MB (laptops; required to be increased to 9MB to fix a minor graphics glitch on some systems) 2) the observation that the Broadwell BDW framebuffers used on Hacks (0x16220007 for desktops and 0x16160006 for laptops) defined: no DVMT pre-allocated memory requirement at all framebuffer sizes of 38MB and 34MB respectively cursor bytes of 38MB and 21MB respectively 3) the observation that the sum of framebuffer size + cursor bytes must be lower than the size of the DVMT pre-allocated memory, failing which a KP occurs at graphics initialisation during startup/boot. 4) In the case of the Haswell Azul framebuffers: DVMT pre-allocated memory requirement is set at 32MB framebuffer size + cursor bytes = 19+0 | 19+6 (or 19+9) = 19MB | 25MB (or 28MB) which is lower than DVMT pre-allocated memory 32MB -> All is Ok by default. 5) In the case of the Broadwell BDW framebuffers: framebuffer size + cursor bytes for desktops = 38+38 = 76MB which is greater than the usual/default 32MB DVMT pre-allocated memory of most desktops, unless adjusted in BIOS framebuffer size + cursor bytes for laptops = 34+21 = 55MB which is greater than the usual/default 32MB DVMT pre-allocated memory of most laptops, unless adjusted in BIOS -> Not Ok by default, Kernel Panic (KP) encountered. 6) And the story is the same with subsequent Skylake, Kaby Lake, etc. framebuffers. Solution: 2 x solutions were engineered to address the issue of KP at graphics initialisation. increase the DVMT pre-allocated memory set in BIOS. Could be complicated and tricky for PCs that do not offer this in BIOS Setup but made easy with Grub Shell if DVMT pre-allocated memory can be identified in BIOS. This method is usually required to gain 4K output. patch the Broadwell, Skylake, Kaby Lake, etc. framebuffer layouts to reduce framebuffer size and cursor bytes so that the sum of them totals less than the usual default DVMT pre-allocated memory of 32MB. This solution does not usually support 4K output. Although some people do opt for the 1st solution, most people just adopt the 2nd one. How were the framebuffer patches derived? If we look at the framebuffer patches that are commonly and generally used, we can observe that they set: WEG's framebuffer-stolenmem property , i.e. framebuffer size to 0x01300000 = 19MB (DATA type set to 00003001) WEG's framebuffer-fbmem property, i.e. cursor bytes to 0x00900000 = 9MB (DATA type set to 00009000) i.e. the values typically used on laptops with Haswell iGPUs, this simply because 19+9=28MB which is < 32MB. This is where it all appears to come from. Is this correct? By far and large, it is. But the need to apply such framebuffer patches depends entirely on the host PC's default DVMT pre-allocated memory. On desktop and laptop PCs where DVMT pre-allocated memory can be adjusted in BIOS setup, the patches are unnecessary as long as the DVMT value that is set exceeds the total of the framebuffer size + cursor bytes of the selected/target graphics framebuffer. Typically, a value of 64MB or 96MB takes care of things perfectly, including 4K. Of course, those PCs manufactured with default DVMT pre-allocated memory set to 64MB or more are unlikely to encounter any issue at all. The framebuffer patches are also unnecessary if the default DVMT pre-allocated memory is increased either though BIOS binmod (difficult and risky) or through Grub shell mod (easy and quickly reversible). This is well illustrated on @Firewolf's blog, linked above (there are other places too such as @Jake Lo's FAQ item here). To give an example, on some Dell laptops (eg. Broadwell Latitude E7x50 or Skylake Latitude E7x70), DVMT pre-allocated memory can be increased by booting a Grub shell and entering the following command: setup_var 0x432 0x3 This sets DVMT pre-allocated memory parameter located at offset 0x432 to 96MB (0x1 for 32MB, 0x2 for 64MB, 0x3 for 96MB, etc.), the default setting for the laptop in this example being 32MB. This setting will remain valid/in place until BIOS is reset to default settings. It's required to obtain 4K output out of DP/HDMI. Of course, different computers will have different locations/offsets for DVMT pre-allocated memory. What should I do then? As stated above, the framebuffer patches apply to most if not all cases. But not for 4K output. Those who feel adventurous or who are computing-literate may opt for the BIOS adjustment alternative. In all cases, the 1st thing to do is to look at the default framebuffer size and cursor bytes settings of the targeted graphics framebuffer, then decide if the sum of them both fits or not in 32MB or any other value set in BIOS for DVMT pre-allocated memory. Can I use different values? Absolutely! As long as the golden rule is respected: framebuffer size + cursor bytes < DVMT pre-alloc mem or, in WEG's conventions, stolenmem + fbmem < DVMT pre-alloc mem. To give a practical example, I experimented on my Skylake/HD520 Dell Latitude E7270 Hackintosh laptop: default DVMT pre-allocated memory value set in BIOS: 32MB target SKL framebuffer layout: 0x19160000 default framebuffer size: 34MB default cursor bytes: 21MB sum of framebuffer size + cursor bytes: 55MB (i.e. > 32MB) Booting with default DVMT pre-alloc mem + no framebuffer patches -> KP/freeze Booting with default DVMT pre-alloc mem + framebuffer size 20MB + cursor bytes 12MB -> KP Booting with default DVMT pre-alloc mem + framebuffer size 19MB + cursor bytes 9MB -> Ok, full graphics acceleration, no 4K output Booting with default DVMT pre-alloc mem + framebuffer size 20MB + cursor bytes 10MB -> Ok, full graphics acceleration, no 4K output Booting with DVMT pre-alloc mem set to 64MB (Grub shell) + no framebuffer patches -> Ok, full graphics acceleration + 4K output Booting with DVMT pre-alloc mem set to 96MB (Grub shell) + no framebuffer patches -> Ok, full graphics acceleration + 4K output

I get the impression you don't fully understand half of what you're doing/writing. 1) "BIOS patched to max 2048MB" ? Very much doubt you'd need to set DVMT to that much. I don't believe macOS framebuffers will make any use of that. 2) '#' character is used to comment something out in a bootloader's config and boolean values can be expressed as decimal NUMBER or 32bit hexadecimal DATA types (0 is 0 and 1 is 1, no matter the size of the data unit you opt for). You also need to understand that some of those injected properties are purely cosmetic (eg: labels, IO locations, slot names, etc.). 3) Your linked IOReg bears no relevance to the screenshots and OC EFI you posted (it shows Monterey kernel, MBP13,3 SMBIOS and SKL iGPU settings). To top it all, the Dortania display documentation you refer to is incorrect; most likely due to copy/paste errors. For instance, there's no such thing as device id 1b59006 for Intel HD 630 iGPU; trouble is that it is totally misleading and the Dortania folks are not (re)known for acknowledging and acting on requests for documentation adjustments. Looks like you're getting all confused (who wouldn't?). You need to do much further reading on the matter of properties injection and graphics settings. Or maybe it's time to give it a rest... I can suggest these links to begin with: https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units https://github.com/acidanthera/WhateverGreen https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md https://osxlatitude.com/forums/topic/8238-supportedunsupported-gpus-graphics-cards https://osxlatitude.com/forums/topic/17804-what-are-dvmt-stolenmem-fbmem-cursormem-why-do-we-patch-these-for-broadwell-and-later/ https://osxlatitude.com/forums/topic/17292-macos-ventura-130-beta1-early-feedback-and-findings https://osxlatitude.com/forums/topic/17587-how-to-spoof-hd520-to-hd620-in-monterey-in-preparation-for-ventura

Alternative links to https://xxxx can be macappstores://xxxx. Example for Ventura: macappstores://apps.apple.com/app/macos-ventura/id1638787999?mt=12

You need to understand that -no_compat_check boot arg applies to SMBIOS/Mac models dropped by the targeted macOS version. The parameter's sole purpose is to allow installing and/or booting a given macOS version on an officially unsupported platform; it's of no (direct) use for graphics acceleration. As such, it's entirely useless with SMBIOS MBP14,x, these Mac models remaining officially and fully supported under macOS Ventura. You would only use it with SMBIOS MBP13,x. Until now, unlike Haswell and Broadwell counterparts, Skylake systems have been able to obtain full graphics acceleration by using/faking KBL graphics with KBL SMBIOS and without any need for OCLP patching. Granted graphics acceleration has been difficult to obtain on HD 530 iGPU, not to say impossible on some platforms. You may consult the threads I had posted for Ventura beta (now in the Archive), my current E7270 guide or the initial Ventura beta thread at InsanelyMac. This being said, feel free to experiment with OCLP if you wish. The Precision 5510 EFI you've referred to clearly makes no use of stolenmem/fbmem patches/injections because DVMT already has the required value (64MB appears to be the default value according to your screenshot on p2). Do take good note that, if DVMT is set to 32MB, it is absolutely necessary to patch it for 4K output. Patching stolenmem and fbmem framebuffer properties won't do. That is clearly mentioned in Jake's FAQ on DVMT BIOS patching to which you had previously referred. In your case, you may experiment patching DVMT to higher values than 64MB. It also looks like you need to learn about the stolenmem/fbmem patches so you have some catching-up to do; it's been covered in all angles since 2015 when gurus such as Firewolf troubleshooted the issue of KP on Broadwell platforms due to DVMT vs. BDW framebuffer native settings. As for the RAM, it really is off-topic and unrelated to Hackintosh but it wouldn't be the 1st time Dell specs state something that's not entirely true on the matter (eg: good old Latitude D630/D830). How do you go about fitting 64GB of RAM? The answer is very likely to be so simple and obvious that it would leave you red-faced... Real question is whether you would need 64GB or not. But, again, off-topic, so let's close the subject.

SMBIOS for Hackintosh is basically a set of faked Mac computers hardware info (model, board id, serial number, etc, etc.) you inject to install and run OS X/macOS. There are various tools/apps to create/inject/update this if it's old/deprecated or if it needs to be changed to support a given macOS version (like after a new version drops older Mac models). OCC, CC, CLI tool (see Dortania documentation), etc. provide built-in SMBIOS generation facilities.

It probably will. Common sense dictates you experiment using a bootable USB key... As simple (and obvious) as that.

Experiment by yourself, you'll find out soon enough. The parameter usually applies to non-Metal GPUs and HD5500, albeit dropped in Ventura, is Metal compatible/capable though possibly not with Metal3.

You forgot the most important piece of information: details of your combo wifi/BT card.

We have a few guides for Sandy Bridge/HD3000 Dell Latitude models; look these up (eg: my Latitude E6220 guide). HD3000 graphics is last officially supported in macOS High Sierra. Thereafter, support can be provided with specific patches but limited to OpenGL mode only. HD3000 has no support for Metal and was already buggy on Hackintosh past OS X Yosemite 10.10 (over time: horizontal lines across the screen, pixelisation). Please note that this kind of platform is kinda obsolete for Hackintosh purposes given Apple's long abandonment for such 12yr old hardware. SSD can't be NVME since that the laptop is built on Intel QS67 chipset; so it can only be a good old SATA or mSATA model. Dell did not sold laptops with NVME-capable SSDs until Broadwell/Skylake generations.

As Jake said: leave SIP disabled (whether partially or fully), do not re-enable it (i.e. DO NOT set csr-active-config to 0). SMBIOS is irrelevant here, it's the OCLP patch for unsupported Haswell iGPU that requires SIP to be kept disabled.

Whilst these old Sandy Bridge E6x20 made great Hackintosh laptops in their days, they're unfortunately obsolete for recent versions of macOS given that Apple has long dropped support for HD3000 and nVidia Fermi graphics. Former was last officially supported in macOS High Sierra 10.13, latter in OS X El Capitan 10.11. Of course there are patches and various tools that'll bring back OpenGL-only support for HD3000 in Mojave and later but, since, Big Sur, such support is pretty poor and HD3000 was already buggy on Hackintosh laptops when it was still officially supported. You may refer to my old E6220 guide which goes up to Catalina (I subsequently sold the laptop). No such workarounds for the nVidia Fermi dGPU, it's a dead-end. If you insist on trying to run Monterey: make sure you install it without any config for HD3000, i.e. in VESA mode only. if you have a model with nVidia graphics, make sure you enable Optimus in BIOS (or laptop will only use nVidia dGPU) and disable the nVidia dGPU through a dedicated SSDT (available on the Net and Hackintosh forums through a Google search). Of course, Monterey will then run like crap due to lack of graphics acceleration. thereafter, install OCLP tool and apply only the graphics patches for HD3000. Make sure to install and boot Monterey with SMBIOS MacBookPro8,1 and the -no_compat_check boot arg. afaik, E6x20 laptops do not boot macOS USB installers when BIOS is set in UEFI mode, they only do so in Legacy mode. Once macOS is installed, you may change to UEFI mode and adjust your bootloader setup accordingly; it'll then work Ok. or you may simply opt to install say, High Sierra or Mojave, then upgrade to Monterey and apply the OCLP patch. That may be the easiest way to proceed. Good luck. Remember to post your E6520 specs in signature.

There's no official support for SKL HD5x0 graphics in Ventura. See our posted documentation in the hardware info section. You must use SMBIOS MBP14,1 + latest version of Lilu + Whatevergreen + inject the correct KBL graphics parameters. You may also consult my E7270 Ventura guide for pointers. See the Whatevergreen Github page + User Manual.

No, you did not, there's absolutely no SSDT that disables the dGPU and that's mandatory.

This is an E6530 with nVidia NVS 5200M which is totally unsupported beyond OS X El capiton 10.11. You have to enable Optimus in BIOS, then disable the nVidia dGPU through ACPI patching (DSDT or SSDT) to run solely on HD4000 iGPU. HD4000 is last officially supported in Catalina but remained natively supported in Big Sur with a little trick on the SMBIOS and boot arg side. It's unsupported with special patches in Monterey and, I guess, Ventura. Your OC config is largely unsuitable to old E6x30 Ivy Bridge laptops. You're trying to apply an config meant for Broadwell or later platforms and that's incorrect. For instance: the graphics properties you inject for HD4000 iGPU in your OC config are incorrect: no need to patch fbmem or stolenmem the way it's done for Broadwell iGPUs and later; all you need to patch is reduce fbmem from 16MB to 8Mb to avoid graphics corruption on screen. you've specified the target Capri framebuffer layout incorrectly; use little endianness, not big endianness. no such thing as I2C keyboard or TouchPad on on the E6x30; you need to use good old kexts for ALPS TouchPads. SMBIOS MBP11,1 is for Haswell/HD4x00 platforms, not for Ivy Bridge/HD4000 ones What version of macOS are you trying to install and run? Please try to, at least, provide the bare minimum required to obtain support. Do consult the various Latitude E6x30 guides available in our Guides section as well as the Hardware info section where you'll find information about supported platforms, supported macOS versions, etc.

Disk mode (RAID/AHCI/IDE) is something you set in BIOS. Do consult your product's documentation on Dell support web site.

Remove those manually, then reboot.

Weird, but the card certainly appears to be properly detected and registered when you inject the compatibility with pci14e4,43a0 statement. It's just that wireless is turned off. No way to turn it back on through the Wireless PrefPane?

That card is based on a chipset natively supported by macOS; as such, you should not require any add-on kexts to get it working.

Looks like you've retained settings for a DW1560 card in your configuration... You may want to review that. DW1830's PCI is 14e4,43ba remains natively supported by AirportBrcmNIC kext so I was not expecting you to require declaring compatibility with 14e4,43a0.

Not sure you need these boot args: agdpmod=vit9696 igfxagdc=0 Also try and add the ACPI patch that renames GFX0 to IGPU through Whatevergreen kext should normally take care of that.

@Senia Suazo Yes, those graphics settings are Ok but, if you've made changes to your OC config, remember to reset NVRAM from the OC Picker at next reboot.