Hervé

This is something that most of not all people should be able to do on their own; it's basic information seeking through Google and manufacturer's web site. People rely far too much on spoon-feeding and other people's assistance for the most basic stuff...

You may of course remove it if you wish; no need to pop questions for such trivial and obvious things.

EFI partitions can be mounted with apps such as OpenCore Configurator or EFI Mounter or Clover Configurator or a few others. But it's just as quick and easy to use Terminal... Just identify the partition disk/volume and mount it! diskutil list sudo diskutil mount /dev/<identified disk> Example: lat-7490:~ admin$ diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *512.1 GB disk0 1: EFI BOOT 523.2 MB disk0s1 2: Microsoft Reserved 134.2 MB disk0s2 3: Microsoft Basic Data Windows 398.0 GB disk0s3 4: Windows Recovery 972.0 MB disk0s4 5: Apple_APFS Container disk1 112.5 GB disk0s5 /dev/disk1 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +112.5 GB disk1 Physical Store disk0s5 1: APFS Volume Mojave - Data 53.2 GB disk1s1 2: APFS Volume Preboot 154.5 MB disk1s2 3: APFS Volume Recovery 529.0 MB disk1s3 4: APFS Volume VM 1.1 MB disk1s4 5: APFS Volume Macintosh 11.3 GB disk1s5 lat-7490:~ admin$ sudo diskutil mount /dev/disk0s1 Volume BOOT on /dev/disk0s1 mounted

Well, if the card is in a format normally supported by Big Sur, sorry, this beats me. Maybe something else in your config that I missed. There were a lot of ACPI patches and you also force injected kexts for some reasons. Good luck.

Proceed with caution; preferably on a separate disk or partition. Use OC off a USB key rather than overwrite your existing Clover EFI partition. But that's a matter for a separate thread.

Apart from this, can't see anything.

Your SSDT-SDCard table looks spot on and your screenshot, although providing very limited info, tends to indicate that all looks Ok on the IOReg front: the SD card reader is active at its usual location for an E6x30 and the macOS kext is loaded. Post a zipped saved output from IORegistryExplorer + a copy of your OC or Clover config if you want full confirmation. I'm tempted to say the SD card reader is Ok but the card you is defective or needs formatting. The O2 card reader of my E6230 works as usual in Big Sur and it's the same model as fitted to your E6530.

@mefflecakes, beyond the suggestions above, all I can offer is that you experiment with what I suggested in that post at IM and that I linked in my last post on the previous page.

Your IOReg shows exactly what would be expected: SKL platform 0x19120000 with 3 x display ports (dummy connector at FB@0 and DP connectors at FB@1 + FB@2). Interestingly enough, but as I thought, your HDMI screen registers against FB@1, i.e. connector 0105; it's got the wrong connector type so you'd never get any audio out but it seems to work Ok on the video front. ideally, you'd inject HDMI type (00080000) to that port/connector (con1). Given that, connecting a DP display to a DP physical port gives you no video, it'd be fair to assume that FB@2 (con2) has the wrong characteristics for your needs. We already know that it's got the correct type (00040000) so that leaves 2 x things to play with: it's own id (Index + Bus id) or pipe. Normally, you never have to modify the flags. I'd replace the connector's id from 0204 to 0306 using the index + busid properties. So, try to inject those properties under PciRoot(0x0)/Pci(0x2,0x0): framebuffer-con1-enable 1 NUMBER framebuffer-con1-type 00080000 DATA framebuffer-con2-enable 1 NUMBER framebuffer-con2-index 3 NUMBER framebuffer-con2-busid 6 NUMBER

Try to boot via single-user mode to rebuild the cache.

Use your USB installer key to boot into macOS. Sigh... Clover was so useful in that respect with its ability to choose all sorts of options, including config files, at boot time.

You said you had HDMI output... so use that! No need to wipe out anything or reinstall from scratch. Just experiment with properties injection in your config file.

No wish to repeat myself but you could try what I listed here. Your current properties injection apply to the framebuffer general parameters (StolenMem, FBMemSize), not the connectors (i.e. video output ports) themselves. That's what you need to work on. And, very obviously, if you want to add a 4th output port, you don't just stop at increasing the count to 4, you must also inject/define the 4th connector.

What does Hackintool show for graphics details? Try and post a compressed IORegistryExplorer output to check what you have under the IGPU device.

CPU model is of no influence here, except if you made use of a CPU-specific power management SSDT. But that's not the case in the pack posted by JakeLo where the generic SSDT-PLUG is provided instead. Post your full hardware specs, including model of wireless card. You may want to reset your BIOS to default and set it up again to be on the safe side of things. Thereafter, the 2 x essential settings are UEFI BIOS mode and disk in AHCI mode. Refer to this thread for guidance.

I think you may need Clover r510x minimum to boot later versions of Catalina. Certainly never used anything lower than Clover r505x with any of my Catalina installations. @nickelnoff, you should be able to replace the Clover boot files (bootx64, cloverx64) and .efi drivers from any computer/OS (even Windows) on your USB key. The hidden EFI partition is normally FAT32... Here are files for r5107 for instance (boots 10.15.7 without issues): r5107.zip

Try single-user mode (-s). Or through your USB installer if you still have it. Or the Recovery partition.

When you get to the Clover main menu, press F11 to reset NVRAM before you try to boot your macOS partition in verbose mode.

How about stating which Clover versions you went from and to? Not a good idea to go beyond r5122.

Try and add NoVPAJpeg kext to fix the freeze issue; you'll find it on the web or in the packs I posted in my Latitude 7490 guide.

As usual, please post your system's specs.

Oh yes! The very absence of a bluetooth card/module in the laptop... As JakeLo said, DW1510 is not a combo card and so, carries no BT module. I've modified your thread's title as a result... You may not be aware that, like many of its D Series or E6x20 predecessors, E6x30 laptops had an optional Bluetooth card too. It's a tiny flat rectangular part of approximately 40x10mm hooked by a cable to one of the motherboard's small pin connectors. I invite you to consult the owner and/or maintenance manual pertaining your laptop on Dell's web site (support section) to check out the matter. I expect your E6230 laptop to be fitted with such a module (DW380 carrying id 413c:8197) when your E6430 isn't. You'd quickly see this by consulting either your SysInfo->USB page or browse your IOReg with apps such as IORegistryExplorer. If you disable Bluetooth in BIOS, that applies to the built-in Dell module, not to any combo card that may be fitted to a mini-PCIe port. So, if you did that, you'd soon find out too... For instance: 'shows how much it pays to know the hardware specs of one's Hackintosh in details...

No reason to include any drivers related to any wireless card, we'll never know what these laptops are fitted with when people come to Hack them... As such, don't expect any. Re: headphones, have you cached CodecCommander kext from /L/E? The kext didn't use to support being injected...

As I said, the connector properties, not the framebuffer properties. I suggest you read the WEG documentation to familiarise yourself with the matter. https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md