Hervé

I'm pretty confident your issue derives from using that single unified SSDT which I believe to be incomplete. I would advise you gradually get rid of this SSDT and return to a more standard set of patched SSDTs. You'll then avoid such issues as that you currently encounter.

When it comes to USB ports power settings, your single SSDT contains the following code and nothing else:

        Device (USBX)
        {
            [...]

            Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
            {
                [...]

                Return (Package (0x08)
                {
                    "kUSBSleepPowerSupply", 
                    0x13EC, 
                    "kUSBSleepPortCurrentLimit", 
                    0x0834, 
                    "kUSBWakePowerSupply", 
                    0x13EC, 
                    "kUSBWakePortCurrentLimit", 
                    0x0834
                })
            }

E5470 is Skylake, right? On my Skylake E7270, I also inject the attached standard XHC/USB3.0 patched SSDT which defines the following power settings:

                "AAPL,current-available", 
                0x0834,                         
                "AAPL,current-extra", 
                0x0898,                         
                "AAPL,current-extra-in-sleep", 
                0x0640,                         
                "AAPL,max-port-current-in-sleep", 
                0x0834                         

Try and add that XHC patched SSDT to your setup.

SSDT_XHC.aml.zip

In all likelihood, it's a power related problem: the USB3.0 port(s) to which you hook your external disk do not draw sufficient power to the disk. If the disk's USB cable has a 2nd plug, plug it in; same if it has an external power supply. That would prove the power-related issue. You may then look into your USB3.0 ports injected properties in order to adjust them.

You've opted for one of those single SSDT to inject your ACPI patches; a particular member of this forum is very keen on this but it's not informative at all and it becomes quite unsuitable when it comes to troubleshooting; basically you just don't fully know what that kind of SSDT does because it ends up being a big bag of... <censored> stuff. I personally strongly discourage to follow that method. I think it's best to stick to individual and specific SSDTs that are simple to identify.

You need to ascertain which KBL framebuffer connector your various display ports attach to, whether the laptop's built-in ones or the Dock's. If multiple ports attach to the same connector, there's little chance you'll get them to work as independent displays simultaneously.

Post a new IOReg, your original one showed you were using incorrect settings (Haswell HD4600 properties injection).

Experienced the same behaviour with my 7490 when I had it: 3rd display off Dock only every worked in mirror mode because it grabbed the same connector as the 2nd display connected to laptop's HDMI port.

https://osxlatitude.com/forums/topic/11410-dell-latitude-7490-with-i7-8650u-intel-uhd-620-and-1920x1080-lcd-mojavecatalina/?do=findComment&comment=90288

Post your 7290 specs and zipped Clover/OpenCore EFI. Specify the exact bootloader version you're using.

Update the BIOS to latest version. A07 is too old.

Then, target those tty devices individually with your screen command. See if any gets you on the modem.

You're not targetting the correct device so you need to identify that 1st. Check the /dev directory to begin with...

You can't enter an AT command at the Linux prompt! You need to be connected through a terminal app to the serial port attached to the modem...

I never got round to work on getting the function keys fully operational so answer is no, not all function keys properly work. Audio only works with VoodooHDA, I never could get audio with AppleALC. That laptop is in semi-retirement, it's not a model that gets my liking and will probably get sold off sooner than later.

Latitude E5400/E5500 is an old Core2Duo laptop quite similar to old E6400 (Intel graphics) model. Those are fitted with Series 4 chipset graphics, i.e. Intel GMA 4500MHD which is totally unsupported. Lack of graphics acceleration makes this old laptop totally unsuitable as a Hackintosh.

1st thing to do when considering running OS X/macOS on a PC is gather the hardware specs and check if they're compatible/supported, the key elements being CPU and GPU.

See here:

https://osxlatitude.com/forums/topic/8956-e4200-e4300-e4310-why-these-make-unworthy-hackintoshes

https://osxlatitude.com/forums/topic/8238-supportedunsupported-gpus-graphics-cards

https://osxlatitude.com/forums/topic/2998-min-requirements-for-os-xmacos

I’ll try and have a go at it again; on my ToDo list among the many other things I need to do with Monterey.

No idea. It's a GCN 1.0 dGPU so it meets the official minimum requirement; that's all I can say. You'll have to suss out if its PCI id is supported by the built-in AMD drivers and the appropriate AMD framebuffer to use.

You have to use a supported SMBIOS (relevant Haswell/Broadwell/Skylake model minimum). The HD4000 patch will be required post-install. I had tried Monterey beta on my E6230 and it had many issues like overall lag (despite HD4000 patch), high CPU usage and high T°. Best avoided imo.

No Optimus per sé here since this is an AMD dGPU not an nVidia one. W5170M and R9 M375X are indeed very close, being based on GCN1.0 Tropo XT/XTX chipset respectively.

Of course, you need to adjust your config; that's the little pleasures every month with every new OC version.

https://www.insanelymac.com/forum/topic/349151-how-to-opencore-073-074-differences/

https://www.insanelymac.com/forum/topic/349485-how-to-opencore-074-075-differences/

i7-10510U CPU makes no difference, it integrates the same Comet Lake UHD 620 iGPU. nVidia MX250 being Pascal, it is also unsupported, same as the Maxwell MX110 mentioned on that GitHub repo. I don't know what you mean by "couldn't boot from the dmg file" but that's not something feasible at all. Do not use any pre-made macOS image obtained off the Web, download a genuine installation package from Apple directly. You'll find all the necessary links off "Our Picks" list on main page.

Given that you encounter issues after updating to OC v0.7.5, the 0.7.5 EFI may be useful too, woudn't you think? Also, did you retain graphics acceleration after the OC update? Did you make any assessment of your network (Wii?) operation?

See if the config settings detailed here can help you. Optiplex 7040 is same family/generation, isn't it?

Nothing wrong with the order of kexts shown at bottom of previous page.

All PlugIns are listed after their parent kexts.

Your IOReg shows next to nothing under device HDEF so, indeed you have no audio enabled. Assuming there's nothing in BIOS to block this, you should consider implementing the HPET IRQ patch. That should fix your audio issues.

https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-easy.html#so-what-can-t-ssdttime-do

Did you fix your config conflicts regarding codec layout id? Because the config you posted in port #1 showed:

1. codec layout 11 being injected in Device Properties
2. codec layout 3 being injected through NVRAM boot arg

You need to decide on one method or the other, not both and opt for the correct layout of course!

If it can be of any interest, you can check your original factory build on Dell support web site with your serial number.

It appears models with touchscreens are fitted with Alps v8 when non-touchscreen models have Alps v7.

A copy of the OpenCore EFI folder maybe? Which version of OpenCore? It's best to update to version v0.7.4 and adjust your config accordingly of course.

Can confirm that I occasionally experienced this with Windows when I had a Latitude 7490; can't remember if it happened under macOS too. All in all, it's a fairly forgettable model if you ask me.