Hervé

Guys, please refrain from using quotes to post replies. Forum provides a Reply box at bottom of pages.

-> moved from Feedback section (where it had nothing to do) to appropriate Dell Latitude E7xxx support section. Please make every effort to post in the right place.

As long as the actual data occupied less than the target disk size, you should be Ok with any cloning or backup utility/program. The simplest manner of all is to make a dmg image of your HDD partition through Disk Utility (from, say, your booted USB installer), then restore that image onto the target SSD.

The same way you initially did.

What's the reference/part number of the card? Kepler-based GT710 are supported OOB up to current Catalina. Same applies to other GK208-based GT720/GT730. If it's a Fermi model, it's of no use. Kepler cards Kepler 2.0 cards Kepler 700 Series (desktop) Kepler 2.0 700 Series (desktop)

Intel i5-3570 is indeed fitted with HD2500 iGPU. That's unsupported as posted in our unsupported GPUs thread. There is no patch or workaround whatsoever. You'd have to replace your current CPU by a model with HD4000 iGPU or install a supported PCIe graphics card.

In the absence of any information such as laptop specs, stuff you used to build your installer (bootloader, bootpack, etc.), it's going to be impossible to assist you. All I can suggest is that you consult the existing threads related to Precision 3510 posted in this very section.

According to your IOReg, SD card reader is Realtek RTS525a. Please refer to our recent News article on our Home page and/or our dedicated recent thread in the SD card reader forum section. No guarantee that the recently developed kext will kick your card reader to life but it should. With regards to USB, there are a number of mistakes with your setup: your Skylake laptop has no USB2.0 hub (only USB3), i.e. no EHCx controllers. As such: delete those EHCx to EH0x renaming you've configured in your Clover config file delete those SSDT-EH0x tables you're injecting through ACPI/patched you're not using USBInjectAll kext + SSDT-UIAC table or USBPorts kext download Hackintool app and generate your USBPorts kext + SSDT-UIAC.aml table use either USBInjectall + SSDT-UIAC.aml together or USBPorts kext on its own Once you've done that, your USB ports should work properly. With regards to LCD screen brightness, please post an IOReg before and after sleep/wake so that we compare iGPU data.

https://osxlatitude.com/forums/forum/161-faqs-tutorials/

Is this a distro installation?

Here, promoted in Our Picks list on home page.

Indeed, those devices are clearly disabled in BIOS. Not visible in either IOReg extracts.

It's exactly as we suspected: your wireless card IS NOT located @1D,0; you got that completely wrong. That location is that of your Realtek LAN card! As such, your property injection is useless. Once you temporarily remove your IO80211Family kext and boot with the card fully enabled in BIOS, we'll be able to identify its correct location in IOREg. And it'll probably be one of the locations Jake Lo mentioned in his 1st reply...

Please post a zipped IOReg extract; I too suspect an incorrect IO address for your card. If you're unable to boot with the card enabled or use your Hack long enough to take the IOReg extract, make a backup of /S/L/E/IO80211Family kext somewhere safe and remove the kext from /S/L/E. Then repair permissions and reboot.

I don't think you understood what I suggested, so let me try and clarify... Context: your Clover config renames Embedded Controller ACPI device EC0 to EC (as is required for Catalina) your laptop boots Catalina Ok with BIOS 01.09.01 your laptop hangs whilst booting Catalina with BIOS 01.11.01 My suspicion: BIOS 01.11.01 may use a different name than EC0 for the Embedded Controller Further tests: revert to BIOS 01.09.01 and temporarily disable EC0 to EC renaming reboot and see if laptop hangs at same place as with BIOS 01.11.01 if it does, upgrade to BIOS 01.11.01 and dump your ACPI tables by pressing F4 at Clover main menu check the name of the Embedded Controller device in dumped tables of BIOS 01.11.01 adjust your Clover renaming patch as/if necessary

Your config did not contained the correct compatibility statement: you specified pci14e4,43a0 when our guide (on which daliansky's blog is actually based) clearly stated to use pci14e4,4353 or pci14e4,4331 in order to bypass AirPortBrcmNIC kext. This does not match what you actually posted above... By declaring compatibility with pci14e4,43a0, you actually totally annuled the desired bypass objective and, instead, returned macOS to load AirPortBrcmNIC since that's where 14e4:43a0 is declared alongside DW1820A's own id 14e4:43a3... Try this revised version: config.plist.zip

Did you check your Embedded Controller device in ACPI/DSDT? You apply EC0 to EC renaming but since you updated your BIOS, did you check if the device name remained the same? You could easily verify the behaviour by disabling the EC0 to EC renaming from Clover main screen Options menu with BIOS 01.09.01 and check if it hangs at the same place...

KP on AirPortBrcmNIC -> clearly the device properties injected in Clover are not used. They're either incorrectly applied (eg: wrong PCI target as suggested by Jake Lo) or conflict with AirportBrcmFixup which I clearly recommended NOT to use in our BCM4350 guide.

KP on KBL graphics framebuffer. Try -disablegfxfirmware boot arg during installation/upgrade.

Basically, you're trying to cache VirtualSMC and it appears unsupported/incompatible with your Hack for whatever reasons (kext version, bootloader config, applied patches, etc.). I'd switch to FakeSMC instead (and ACPIBatteryManager of course). And you appear to have the same with WEG. You really need to update your add-on kexts to latest versions before you upgrade to Catalina! You're right to cache your kexts from /L/E.

And don't forget the Embedded Controller patch as detailed in our promoted thread (see Our Picks column). Imperative for Catalina.

@bluedogmike, please post your debug files.

Indeed, your Clover config injected properties to avoid the system freeze/CPU hogging with the DW1820A. Now that you've replaced the DW1820A by a fully natively supported card, you can removed those injected properties from your Clover config.

You could try the hard way and follow the same process as detailed in my Latitude D630 guides for High Sierra, Mojave or Catalina: Obviously, some of the files won't be re-usable (like the DSDT or kexts related to specific hardware like LAN card) but the overall process can be applied. Or there is the easy way where you just follow the recent guides posted at InsanelyMac. A simple forum search on E6410 threads or a basic Google search will lead you there. Of course, High Sierra is the last macOs version that supports your Tesla graphics natively and to the full. Mojave and Catalina require the specific tricks detailed on the guides to support Tesla graphics in OpenGL-only mode (no support for Metal). NB: as per our published rules, no references to distros please; stay away from them, they're full of crap.

Incorrect settings, you should: remove Generate C States and Generate P States (these are for C2D, C2Q, 1st gen Core CPUs) enable PlugInType and that's it, nothing else. No need to enable NoOemTableId or NoDynamicExtract afaik.