Hervé

Thread sanitised and locked to avoid further mixing of OpenCore and Clover, causing confusion on what was effectively an OC-related thread.

Can't be done from either OS disk utility/disk management tools. These can only reduce (or increase) a partition size from its end but they cannot move a partition which is what you'd need here. According to what you described, your disk is organised as follows: 1st partition with OS X El Capitan 2nd partition with Windows 10 Partitions cannot be split across separated disk areas so what you effectively need to do here is: reduce Win10 partition move reduced Win10 partition to end of disk recover the space liberated between end of OS X partition and moved/reduced Win10 partition to reallocate to OS X partition You'll have to look for dedicated 3rd party apps such as GParted, Paragon and many others to do this. The only other alternative would be to make an image of your Win10 installation (or clone the partition) before you delete the 2nd partition from El Capitan Disk Utility app, after which you would be able to re-create a smaller 2nd partition on which you'll restore your Win10 image.

Yes, you're one of many with such issues. It's not a straight update given that r5125 brings changes for Big Sur and you need to take Quirks and new drivers into consideration. So, unless you intend to run Big Sur now, stick to r5119.

No, Jake gave you the correct values to reflect your Skylake iGPU rather than the Kabylake iGPU of the OP. Use them.

Yes, the SSDT table generated for any given CPU can of course be re-used on any Hackintosh fitted with the exact same CPU model, i.e. no need to regenerate when you already have the applicable (generated) SSDT. The platform on which you generate the CPU power management SSDT does not really matter. By default (i.e. without any parameters), the script generates a table for the host's CPU and active SMBIOS data (Mac model + board-id) but, if you've installed the complete package with CPU models database, you can add parameters to target a totally different CPU & Mac model. All parameters and instructions are explained in the documentation available on that GitHub repo or if you type: ./ssdtPRGen.sh -help For instance: 1) to generate the SSDT for an i7-3540M CPU fitted to an Ivy Bridge laptop running OS X/macOS with MBP10,2 SMBIOS ./ssdtPRGen.sh -target 1 -p i7-3540M -m MacBookPro10,2 -b Mac-AFD8A9D944EA4843 2) to generate the SSDT for an i5-5300U CPU fitted to a Broadwell laptop running OS X/macOS with MBP11,2 SMBIOS ./ssdtPRGen.sh -target 3 -p i5-5300U -m MacBookPro11,2 -b Mac-E43C1C25D4880AD6 You can get board-id of any Mac Model from Clover Configurator app, SMBIOS tab.

Re: DrHurt's VoodooPS2 kext, you were meant to take it from here: https://osxlatitude.com/forums/topic/8285-refined-alps-touchpad-driver/ Use the kext's version recommended in post #1 and do consider generating your USBPorts kext with Hackintool app as I experienced a TrackPad issue last year in relation to that matter as detailed here.

aka Telit LN930. 4G LTE 100Mbps WWAN module (M.2 format). Given that it is based on an Intel XMM 7160 chipset, I'd say there is very little chance -not to say zero- that'll be supported as a WWAN interface. We've certainly never discussed this module here in the past. I expect you'd have to dig into its specs, work out its various operating modes and then experiment with potential WWAN module profiles (from CellPhoneHelper kext) if any were applicable at all (but I doubt it)... http://www.adaptivemodules.com/assets/telit/Telit-xN930-Hardware-User-Guide.pdf You say it is seen as a WLAN card -which I very much doubt- but maybe it's actually seen as a dial-up modem. It may work that way.

Yes and you can look that up, it's well documented in numerous places/threads/posts. Your Crucial model is not affected.

Clover setup shows several mistakes. For instance, you've installed SMCHelper.efi driver (which is only required if you use FakeSMC kext) when you use VirtualSMC set of kexts. If you want built-in ALPS TrackPad to work and be recognised, you need to use Dr Hurt's VoodooPS2Controller kext. It's available in Dr Hurt's dedicated thread and in the Clover packs posted in the various guides we have for the E7x50 models. I can't remember which ALPS version these E7x50 are fitted with but I don't remember specific issues with them when I had an E7250 in my hands. Re: SSDT, if you're talking about the CPU power management one, you have to make sure you use one that was generated for your own specific CPU. If you (re)use an existing one meant for a different CPU mode, you'll encounter trouble, of course. If in doubt, boot without such SSDT and generate your own one using Pike R Alpha's well-known and good old generator script.

I suggest you investigate what a DW1506 card is based on.

I'm pretty certain you will not get your AR9485 to work in High Sierra, Mojave or Catalina but you're free to go ahead and knock yourself out at it. There is no such thing as "no way to replace" the wireless card and a replacement Broadcom model would cost you peanuts!

We already have such threads for E6530 and E6430s. I suggest you refer to them.

You may use any of those guides, your specs are roughly the same as any other E7440 (4th gen Haswell CPU with HD4200/4400/4600 graphics). You should consider replacing the DW1506 wireless card by a fully compatible model. All those AR9485/9565-based cards usually are a headache in recent macOS version given that the specially-written driver they require no longer seems to work properly. Note that there is no such thing as the AR5B125 kext you mentioned. Then, given that Apple abandoned all support for Atheros cards, I strongly suggest you switch to a supported Broadcom card. Dell Dock should be working, at least partially. I certainly could use it for OS X/macOS with my E6440 when I had it and it still works with my E6220/E6230. It really depends for you want to use it for.

Why do you want to install such an old OS X version when this laptop fully supports macOS High Sierra? As for the set of kexts required for this model, I'm pretty sure you'll find them in existing threads or JakeLo's multi-platform guides. Look those up.

I'd avoid Clover r5125 (got lots of problems on older systems with it) and stick to r5122 at the latest for the time being. Using a USB installer built on an MBR partition is not an issue at all. I've looked at your patched DSDT but, unless I missed something, I could not find any difference to the vanilla BIOS table. If that's confirmed, it's useless and you can remove it. You may try this slightly revised config and remove NullCPUPowerManagement of course; it's not required. config.plist.zip

Correct.

What's the exact model of NVME SSD installed in that 7400? Some models are not macOS compatible (eg: Samsung PM981, Micron 2200s).

You may look into this and/or other similar threads on the matter: https://www.insanelymac.com/forum/topic/345492-guide-unlocking-cfg-with-opencore-and-cfglockefi/

Then use the forum Search facility. There are dozens of threads regarding the Ivy Bridge E6x30 Series and several guides too, including full installation guides for Catalina. Please refer to them.

Here you go... Set your BIOS to UEFI mode, your disk to AHCI mode and install Clover in the manner described here. Copy the file & folders included in the zip attached below to the CLOVER folder of your EFI folder/partition. EFI_Inspiron_5548.zip

Avoid Clover r5120, r5124 or r5125 for the time being. You may use versions such as r5119 or r5122 safely. The bootpack you used is obviously totally outdated for Catalina and needs to be entirely revisited. I'll try and post one asap. Meantime, what you could do is dump your BIOS ACPI tables by pressing F4 when you get to the Clover main screen as you try and boot macOS. Those tables will go to the CLOVER/ACPI/origin folder. Zip it and post a copy. Ideally, update your BIOS to the latest version beforehand.

What kind of error are you talking about? Are you running off the last BIOS for your laptop? Is disk mode set to AHCI rather than RAID? Please post zipped/compressed copy of the Clover pack you're using.

I you look into that patched SSDT, you'll see that it applies to iGPU/dGPU graphics components. It is to be compared to the raw/extracted SSDT table called SSDT-2-SaSsdt.aml. You'll see that the patched SSDT renames the HDMI audio device from BOD3 to the desired HDAU and the iGPU device from GFX0 to the desired IGPU, injecting the HDMI audio capability through a _DSM method at the same time.

From memory, Touchscreen are USB-based so start with USBInjectAll kext then use Hackintool to generate your USBPorts kext that will fully define all your USB ports. NB: thread moved from Installation Guides to appropriate Support section. Please make every effort to post in the correct forum section in the future.

I understand you need to reset NVRAM after each change made to your OC config/setup, so make sure to do that...