Hervé

If you already have High Sierra, then it's a "simple"' matter of following the 1st gen Intel HD guide and adjusting the graphics settings for 10.13 and your screen resolution. Discussions about support for 1st gen Intel HD graphics started on p68 in the bible thread. Read on, I'm sure details are provided throughout the subsequent pages. https://www.insanelymac.com/forum/topic/286092-guide-1st-generation-intel-hd-graphics-qeci/?page=68

No such files and/or folders were posted here. Looks like the only proper guide we have for this model is Jake Lo's Mavericks guide which dates back to many years ago. T410s is an ageing laptop with 1st gen Intel HD graphics iGPU or Tesla nVidia graphics dGPU. As you probably know, this iGPU always required specific tuning to be supported on Hackintosh and this support was only under conditions (see Bible on 1st gen Intel HD at InsanelyMac). 1st gen Intel HD graphics are last officially supported in macOS High Sierra; abandoned in Mojave/Catalina due to lack of support for Metal as are nVidia Tesla GPUs and Intel HD3000. There are tricks that can be implemented to obtain partial and OpenGL-only graphics acceleration on those dropped GPUs. My advice would be to go for macOS High Sierra to begin with and build a working Clover setup before you attempt any more recent versions like Mojave or Catalina. Please post your laptops full hardware specs (CPU, graphics, screen resolution, audio, LAN, wireless, etc.) and we'll try and help you build a Clover setup. Is the BIOS legacy only or does it support UEFI mode?

I've never seen anyone booting Clover via OC ! Anyway, your OC setup is clearly what's causing your issue since you do not experience it when booting Clover directly. I'd say some incorrect settings under the Kernel section.

The FB mem. size patch is detailed in our HD4000 patching guide In the R&D->Graphics forum subsection. You can look it up. I've never used OC myself but you would implement the patch either as a property injection under DeviceProperties (may be difficult for you) or as a kext patch under Kernel->Patch (you have existing patches you can refer to).

Startup and shutdown glitches, you'll have to live with. They're totally negligible and can be ignored. For the other stuff you've filmed, you may try the Capri framebuffer memory size reduction from 16 MB to 8MB. I could not see any Capri FB patching in your OC config so no idea which patches your meant above...

For the sake of clarity: posts relating to Catalina were split to their own thread here. Clover r5119 Catalina EFI folder attached to Baio77's original (Catalina) thread here. this thread, obviously relating to Big Sur beta, was moved to this macOS Preview section. Guys, please refrain from mixing topics/versions, Catalina and Big Sur beta being 2 x different OS requiring very different configs to say the least!

Better later than never... As explained in past system/model-specific threads, there are further patches that may be used to modify the framebuffer memory size (useful on Latitude E6x30) and the VRAM allocation (nice to increase). Of course, WhateverGreen supports property injection (through DSDT/SSDT patches or bootloader configs) as a more efficient alternative to rather old-fashioned framebuffer kext binary patching. Those parameters are defined in the 2nd line of the sample Capri layouts we've illustrated throughout this thread (bearing in mind the reversed byte order of kexts' binary code). For instance: LoRes mobile layout 0x01660003: 03006601 01020402 00000004 00000001 00000060 10070000 HiRes mobile layout 0x01660004: 04006601 01030101 00000002 00000001 00000060 10070000 Desktop layout 0x0166000a: 0A006601 00020302 00000002 00000001 00000060 10070000 Desktop layout 0x0166000b: 0B006601 00020302 00000002 00000001 00000060 10070000 1) Framebuffer memory size: This is defined in the 4th 32bit parameter of the layouts. Default value is 0x01000000 (reversed code 00000001), i.e. 16777216 in decimal which, when divided by 1024*1024 (=1MBytes), equates to 16MB. Some laptops such as the Dell Latitude E6x30 models suffer from corrupt/garbled display on screen unless this value is reduced to 8MB, i.e. 0x00800000. The patch required to change this is: Find: xxxxxxxx [...] xxxxxxxx 00000001 xxxxxxxx [...] xxxxxxxx Replace xxxxxxxx [...] xxxxxxxx 00008000 xxxxxxxx [...] xxxxxxxx For instance, to reduce the FB mem. size of layout 0x01660003 to 8MB, use this patch: \/\/ Find: 03006601010204020000000400000001 Replace: 03006601010204020000000400008000 /\/\ Alternative property injection: framebuffer-patch-enable 1 NUMBER framebuffer-fbmem 00008000 DATA 2) VRAM allocation: This is defined in the 5th 32bit parameter of the layouts. In most recent versions of OS X/macOS, the default value usually is 0x60000000 (reversed code 00000060), i.e. 1610612736 in decimal which, when divided by 1024*1024 (=1MBytes), equates to 1536MB (i.e. 1.5GB). This is shared memory and systems with, say, 8GB of RAM, may want to increase this. The patch required to do this is: Find: xxxxxxxx [...] xxxxxxxx 00000060 xxxxxxxx [...] xxxxxxxx Replace xxxxxxxx [...] xxxxxxxx 000000YY xxxxxxxx [...] xxxxxxxx -> where YY = desired VRAM Qty Reminder: 256MB = 1000 0000 in hex 384MB = 1800 0000 in hex 512MB = 2000 0000 in hex 768MB = 3000 0000 in hex 1024MB = 4000 0000 in hex 1536MB = 6000 0000 in hex 1792MB = 7000 0000 in hex 2048MB = 8000 0000 in hex For instance, to increase VRAM allocation of layout 0x01660003 to 2048MB (i.e. 2GB), use this patch: \/ Find: 0300660101020402000000040000000100000060 Replace: 0300660101020402000000040000000100000080 /\ Alternative property injection: framebuffer-patch-enable 1 NUMBER framebuffer-unifiedmem 00000080 DATA Naturally, those framebuffer modifications can be combined in a single patch. For instance, to reduce FB mem. size to 8MB and increase VRAM to 2GB, layout 0x01660003 is patched as follows: \/\/ \/ Find: 030066010102040200000004000000010000006010070000 Replace: 030066010102040200000004000080000000008010070000 /\/\ /\ Alternative property injection: framebuffer-patch-enable 1 NUMBER framebuffer-fbmem 00008000 DATA framebuffer-unifiedmem 00000080 DATA

Replace your Intel wireless card by a supported model.

Specs? Settings?

Location services requires wireless services to be active. It does not need to be connected if you have a wired/Ethernet connection to the Internet, but it needs to be on/enabled. Afaik, there is no issue with the Intel LAN card fitted to the E5450. For the wireless card, well, it's the same as usual... Bottom line is no Location services without a compatible wifi card.

Use cropped screenshots rather than poor quality SmartPhone pictures of your laptop screen. It's far better and far quicker. Consult your Keyboard PrefPane for guidance on the keystrokes.

Don't use r5120, stick to r5119. Latest Clover release appears buggy on the CPU power management side. You may find that, all of a sudden, it won't boot/reboot.

I don't know what you mean. It'll run Catalina Ok.

You may simply apply the EC patch to your existing patched DSDT, yes.

Your current setup dates back to 2017 and High Sierra, i.e. long before the new Catalina requirement was even identified. As such, the Embedded Controller patch could not have been applied. Check your DSDT as per the thread I referred to above and rename the device as/if necessary. I would also recommend that you switch from patched AppleHDA (which may no longer work in Catalina) to Lilu+AppleALC for audio.

I would suggest you 1st upgrade to Catalina and establish a working Clover config before even attempting a switch to OC. Please refer to the Catalina requirements thread pinned to Our picks list on main page. You'll most likely need to patch your Embedded Controller ACPI device. You'll also need to update Clover (go for r5119, not r5120 which is buggy/troublesome) and your add-on kexts (Lilu, WEG, AppleALC, etc.) before you actually upgrade to Catalina; make a backup for safety but you would normally be able to simply launch the downloaded Catalina app package to upgrade.

If your laptop is unstable and CPU running at high speed under Windows and macOS, I'd say you have a general issue that's not related to running macOS... There are obvious things to check such as state of fans (and cleaning if clogged by dust) and CPU/GPU thermal paste (and clean off if hardened to renew by high quality paste). Your BIOS settings may also be incorrect (make sure CPU speedstep is enabled). Then, there is the matter of properly configuring CPU power management under macOS. You'll have to specify your laptop model and post a copy of your bootloader config/zipped bootloader folder. If you've used the pack from a guide posted here, all should be in order. With regards to turning off Turbo boost, I've always believed it was a bad idea given the impact on performance but, several years ago, a forum member developed and posted a kext that disabled Turbo boost when running on battery. I don't know if that still works on more recent platforms but you can always look it up.

Try and rebuild your cache. i also suggest you look at the config posted in the pack I posted in my E7250 guide. I believe your Clover config is a little erroneous, especially on the CPU power management side. Your Hack may therefore run slower than it should.

As per our stated rules, we do not support those tools you chose to use. They have their own forum... We have several guides for Desktop in our Guides section and I invite you to refer tho them. BIOS version is usually of no influence on OS X/macOS installation on Dell computers. Lucahappy posted his working Clover config + EFI folder so, provided you use that and our no non-nense tools standard installation method, you should have no issue.

Make sure to use the SMBIOS of a MacBookPro model with an nVidia GPU. If necessary, don't hesitate to mix the main SMBIOS of a Catalina supported MBP with the board-id of an older MBP with an nVidia GPU.

Absolutely no need to drop those 2 x tables. KernelPm patch is now enabled by default in Clover. If you don't use XCPM, it's irrelevant and so, does not matter.

Could be the same issue as that of M4800/M6800 with HiRes eDP screens (>1920x1080) that are unsupported.

The same way it's been for years: you press F4 at clover main menu or through any iASL tool in High Sierra (with any patches you may apply through Clover).

Target macOS release: Sierra 10.14.x (all versions) For models with Penryn CPUs only Proceed with the knowledge that, Tesla GPUs lacking Metal compatibility, only OpenGL graphics acceleration can be achieved. It works Ok but graphics bugs and/or degraded performance may be noticeable especially with Finder or when watching a movie in Netflix (video may be slightly jerky). It's not entirely as smooth as in High Sierra. Working: OpenGL-only graphics acceleration with nVidia Quadro NVS 135m (after specific tuning) VGA output (display extension or mirroring) full audio, including jack microphone input and headset output (with VoodooHDA v2.8.x & AppleHDADisabler kexts in /L/E) built-in Gigabit Ethernet (with BCM5722D kext v2.3.6) DW360 bluetooth OOB native CPU speedstep (with SMC-tuned Kozlek's FakeSMC v6.13.1363 and MBP7,1 SMBIOS profile) native GPU throttling (with above AGPM-tuned Kozlek's FakeSMC) sleep through lid closure, Fn-Esc, Apple menu->Sleep, power button (Press ALT-CMD/Win-PWR or CTRL-PWR for power options menu) and energy savings settings (all with hibernation disabled) wake through lid opening and power button wireless with any compatible card battery management and monitoring (with ACPIBatteryManager kext v1.81.4) rear + right USB2.0 ports (with USBInjectAll kext v0.7.1) Not Working: CardBus/PC Card/PCMCIA (unsupported since SL 10.6.7) Not tested: Firewire 1394 SmartCard reader 1) 10.14 USB installer creation Using a USB key of 8GB minimum, create a Mojave USB installer through the following Terminal command: sudo <path>/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/<USB key> where: <path> = location of Mojave 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: install Clover bootloader on the USB installer with the following customised settings: Install Clover in the ESP Boot Sectors -> Install boot0af in MBR Clover for BIOS (legacy) booting -> Clover EFI 64-bits SATA BIOS Drivers, 64 bit -> ApfsDriverLoader / FSInject / HFSPlus / SMCHelper BIOS Drivers, 64 bit -> GrubEXFAT / GrubNTFS you may use version r5097 attached below or any subsequent version available at Dids' Github repo: Clover_v2.5k_r5097.pkg.zip once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the USB installer Clover Configurator.zip open this EFI partition and transfer the files & folders from the D830n Mojave Clover pack below to the EFI/Clover folder. This pack contains 2 x Clover config files: the default one with MBP7,1 SMBIOS which is required to gain CPU power management and a 2nd one called "config_MBP9,1" with MBP9,1 SMBIOS which is required for Mojave installation and updates D830n_10.14_Clover_Pack.zip copy High Sierra 10.13.6's telemetry plugin below to the root of your USB installer com.apple.telemetry.plugin.zip copy Mojave's PlaformSupport plist below (patched to support MBP7,1 platforms) to the root of your USB installer PlatformSupport.plist.zip copy Clover package + Clover Configurator app to the root of your USB installer for subsequent use later 2) Basic 10.14 installation (no Telsa dGPU support/no graphics acceleration) boot the Mojave USB installer at the Clover main menu, go "Options" then "Configs" and select "config_MBP9,1" (Press [ENTER] each time). Press [ESC] a couple of times to return to Clover main menu at the Clover main menu, select the "Install macOS Mojave" partition but don't press [ENTER] press [SPACE], select -v verbose option in the menu, then boot with the selected options proceed with installation, 1st creating & formatting the target Mojave partition through Disk Utility as/if required (GUID scheme, HFS (journaled) format) on 1st reboot, boot from the USB installer again and select "config_MBP9,1" config file again return to the Clover main menu and boot the freshly created "macOS Install from <target Mojave partition>" temporary partition repeat this reboot sequence until the temporary partition is no longer offered and only the target Mojave partition is offered, marking the effective completion of Mojave's installation reboot the USB installer as it if were the 1st time again (or the Recovery partition via the USB installer) and, once at the macOS installer main screen, open up Terminal from Utilities menu copy 10.13.6's telemetry plugin to Mojave's target partition to avoid SSE4.2-related KP/reset on Core2Duo at boot time (required after each update ) cp -Rf /Volumes/Image\ Volume/com.apple.telemetry.plugin /Volumes/<target Mojave partition>/System/Library/UserEventPlugins/ copy Mojave's patched PlatformSupport plist to Mojave's target partition to support booting Mojave with MacBookPro7,1 SMBIOS cp -f /Volumes/Image\ Volume/PlatformSupport.plist /Volumes/<target Mojave partition>/System/Library/CoreServices/ exit Terminal and restart your computer. Reboot the target Mojave partition via your USB installer with default config file. 3) Post-installation basic tuning Once the target Mojave partition has booted, complete the 1st boot system setup Once at the desktop, install Clover bootloader on the Mojave partition/disk with the customised settings listed above Once Clover is installed, launch Clover Configurator app and mount the freshly created EFI partition of the Mojave partition/disk Open this EFI partition and transfer the files & folders from the above D830n Mojave Clover pack to the EFI/Clover folder You may then reboot and verify that Mojave boots off your disk through Clover Copy High Sierra's telemetry plugin + patched PlatformSupport plist, available above, to the root of your Mojave partition/volume If you wish to cache add-on kexts rather than inject them through Clover at boot time, copy them to /L/E folder and rebuild your cache through the following Terminal commands: sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo touch -f /L*/E* sudo kextcache -i / 4) Post-installation graphics tuning Fine-tuning for natively unsupported Quadro NVS 135M Tesla discrete GPU may now complete using the files available in the package below, as derived from early findings with Mojave and the work done dosdude1 & AsiententBot at MacRumors & InsanelyMac: Tesla_10.14.zip Place an uncompressed copy of the above Tesla_10.14 folder to the root of your Mojave partition/volume Reboot in single-user mode (at Clover main menu, press [SPACE] and select -s option) At the single-user mode prompt, mount your Mojave volume: mount -uw / For Mojave 10.14.4 and later, remove GPUSupport + SkyLight + OpenGL + CoreDisplay vanilla frameworks: rm -Rf /S*/L*/PrivateFrameworks/GPUSupport.framework rm -Rf /S*/L*/PrivateFrameworks/SkyLight.framework rm -Rf /S*/L*/Frameworks/OpenGL.framework rm -Rf /S*/L*/Frameworks/CoreDisplay.framework For Mojave 10.14.4 and later, install 10.14.3's replacement frameworks: cp -Rf /Tesla_10.14/Frameworks/*.* /S*/L*/Frameworks/ cp -Rf /Tesla_10.14/PrivateFrameworks/*.* /S*/L*/PrivateFrameworks/ For all Mojave versions, Install the legacy kexts required for Tesla dGPU support: cp -Rf /Tesla_10.14/Extensions/*.* /S*/L*/E* chmod -Rf 755 /S*/L*/E* chown -Rf 0:0 /S*/L*/E* touch -f /S*/L*/E* Quit single-user mode and resume normal macOS startup: exit macOS Mojave should then complete full boot and now run with (OpenGL-only) graphics acceleration. Note that this entire graphics-tuning process will require to be repeated after each Mojave update. 5) Mojave update Mojave updates will only be offered, downloadable and installable if running with MBP9,1 SMBIOS, i.e. if booting with the "config_MBP9,1" config; this because Apple does not offer/support updates for unsupported models. Once a Mojave update has completed, the following fine-tuning must be completed through single-user mode: re-install High Sierra's telemetry plugin as detailed above re-install patched PlatformSupport plist as detailed above re-apply the graphics fine-tuning process detailed above Please note that all reboots must be done with "config_MBP9,1" Clover config until Mojave update and fine-tuning have been fully completed. Only then can Mojave be safely rebooted with its default MBP7,1 Clover config.