Hervé

Ok, no display registers other than your TV screen on port #4 (Display-D@3). NVCAP shows the following value: 050000000000ffffffff00000000000e00000000 There are a few things you can try regarding this EFI string and your Clover config: inject it as is. It goes into the Properties [Hex] field in Clover Configurator. I'd save it into a separate config that you call from Clover main menu. You can then post a new IOReg after rebooting with the EFI string applied. I don't recommend this because the string contains an entire set of nVidia properties and they don't really apply to your laptop. you inject the NVCAP it contains after decoding the string. It's the NVCAP that defines the dGPU output ports. If you use old 32bit tools such as EFIStudio, you can decode the EFI string and you'll see it's as follows: nVidia_properties.plist.zip EFIStudio.zip Basically, it injects the following properties: where you can clearly see an injected NVCAP value of: 0500000000000100060000000000000F00000000 Also to be noticed and noted: built-in LCD set to boot display built-in LCD EDID injection

@wowww Congrats, well done. Which tools did you use to obtain your EDID info and which one got you the adequate one?

I know of 2 x Sonix cameras fitted to the E6230 as indicated in my E6230 guide: one with dev id 0x648b and one with dev id 0x6449. Experience has shown me that not all Sonix cameras of the Latitude E6xxx series are supported. For instance: Sonix camera 0x6433 fitted to the E6x20 series won't work as stated here Sonix camera 0x643f fitted to the E6x30 series works OOB as stated here Sonix camera 0x648b fitted to the E6x30 series works OOB as stated here Sonix camera 0x649d fitted to the E6x40 series works OOB as stated here Afaik, model 0x6449 suffers from the same issue as model 0x6433. Unfortunately, these cameras either work OOB or they don't. There are no drivers or kexts for such USB devices. Yours is being properly detected on its USB-internal port but just isn't supported. It had previously been discussed several years ago, here for instance. There appears to be no problems with the Sunplus Innovation Technologies models on the other hand.

Boot without the iGPU id faking, take an IOReg with IOregistryExplorer app, zip to and post it. A question though: how did you install Big Sur? With what?

Possibly. You would have to disable Optimus, boot with an external screen connected and take an IOReg that we can then have a look at in order to identify the built-in LCD if it registers against a port. In case you need to get in remotely via VNC, 1st ensure you enable Screen Sharing via Sharing PrefPane. We can have a look at the guy's EFI in order to inject the associated NVCAP in your config.

I would stay away from this offered setup; the ACPI patching part is frightening and the patched SSDT tables messy...

You enter the whole set of hexadecimal obtained as EDID from Windows or whatever you used to extract it. It's the data provided at the bottom of that Nuevo document de texto.txt text file: Raw data 00,FF,FF,FF,FF,FF,FF,00,36,7F,03,90,08,00,00,00,00,01,01,03,80,00,00,FF,2F,00,00,A0,57,49,9B,26, 10,48,4F,00,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,66,21,56,AA,51,00,1E,30,46,90, 14,00,00,00,00,00,00,18,00,00,00,FC,00,4E,6F,74,65,62,6F,6F,6B,50,61,6E,65,6C,00,00,00,FD,00,3B, 3C,2F,30,09,01,00,00,00,00,00,00,00,00,00,00,10,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,09 You take all the hexadecimal data, remove the separating commas and enter the complete set of bytes in a single long chain of data: AAPL00,override-no-connect 00FFFFFFFFFFFF0036 ....... 0000000009 DATA

Look up the documentation that goes with those Synaptics I2C kexts; usually there are PlugIns for the various brands and you'd need to remove Alps Plugins if you used those for instance. Can't say more, haven't done much experimentation since the Latitude 5490 that I no longer have and I never spent much time on it.

Tried Optimus disabled + virtual display device then?

again... You can inject EDID info through a device property against your iGPU, i.e. alongside what you currently inject (i.e. ig-platform-id and device-id). Look it up in the WhateverGreen User manual. You may also want to connect a VGA monitor if you have that around you and, hopefully, get the macOS desktop or whatever on screen. VGA usually is supported OOB on laptops with HD4400 graphics (they're the lucky ones!) By the way, what do you mean by "I get a black screen with script loaded"?

No, I2C is not a brand of Touchpads... https://en.wikipedia.org/wiki/I²C Look up Synaptics I2C kexts... if that exist.

No quoting to post replies please; especially if you use Google translator... Just use the Reply box at the bottom of our pages. As a newcomer, I also invite you to read our published rules so that you get familiar with them. Setup is incorrect in a few respects, most of them minor: you use old versions for some of your kexts; update them to the latest versions (eg: Whatevergreen) you've enabled _OSI to XOSI renaming but not the SSDT-XOSI table; these go together... you have some unnecessary kernel quirks enabled (eg: AppleCpuPmCfgLock which is for Sandy/Ivy Bridge) The one thing you must do is update Lilu & WhateverGreen to the latest version. At your next reboot, make sure you Reset NVRAM at the OC Picker. If you still get back screen, you could require to inject your screen's EDID. You can obtain it from Windows with some tools that you can Google for.

Anything is possible, but that does not really help, does it? Did you check the info of the TrackPad driver for Latitude 5510 in the support section of Dell's web site? Edit: Ok, here goes... PCI id 0488:121f -> It's a Synaptics Touchpad.

Afaik, if you want to run only with the nVidia dGPU, you need to disable Optimus. At least that how things worked on the old E6x20/E6x30. With Optimus disabled, the Intel iGPU was off/unused. But then, most of you guys just get a blank built-in LCD which suggests it is not wired to the dGPU.

There is absolutely no need to patch the Haswell framebuffer memory size on Haswell mobile HD4x00. The only thing that needs patching is the HDMI connector if HDMI output is to be used (or system will freeze/crash). The other thing that may need patching is the cursor memory size (to be set to 9MB) if glitches are experienced. The correct settings required to obtain graphics acceleration on Haswell laptop with HD4200/4400/4600 graphics are: 1) use of Lilu + Whetvergreen kexts (WEG normally takes care of iGPU ACPI device renaming to IGPU). 2)injection of the following properties against iGPU@2 (i.e. location PciRoot(0x0)/Pci(0x2,0x0) in Device Properties section of the bootloader config): AAPL,ig-platform-id 0600260A DATA device-id 12040000 DATA 3) SMBIOS of MacBookAir6,2 or MacBookPro11,1 This being, said, please post: 1) your full systems hardware specs. Add them in your signature like most of us do, as expected. 2) a zipped copy of the OC or Clover EFI folder you're using. 3) the version of the bootloader you're using. 4) the target macOS version you try to install/run.

Look under IGPU@2 (HD4600 iGPU) and under GFX0@1 (nVidia dGPU). Again, a built-in LCD registers as AppleBacklightDisplay. External monitors register as AppleDisplay. For iGPUs, connected screens are listed under the various connectors (=output ports) con0/con1/con2/con3 (the various FB@x). For nVidia dGPUs, connected screens are listed under the various connectors (=output ports) A/B/C/D (the various NVDA,Display-A/B/C/D@x). Good thing that the dongle was dead cheap, eh? NB: I noticed you use SMBIOS MBP11,5 rather than MBP11,3. Strange choice given that former is fitted with an AMD dGPU when latter is fitted with an nVidia Kepler dGPU. I'd have opted for the latter.

Check your IOReg; built-in LCD registers as an AppleBacklightDisplay... This kind of generic devices are not so much HDMI dummies but display simulators/virtual displays. I don't think it makes your nVidia K4100M prime GPU for the built-in LCD. To me, it's just a temporary cosmetic thingie whilst the virtual display device is connected. You just need to look at what SysInfo->GraphicsDisplays actually shows under the HD4600 iGPU: ain't that the built-in LCD??? What's listed under the nVidia dGPU ? As for display mirroring, remember that it mirrors the built-in LCD on external screens, not the other way round.

Given that the Latitude 3470 is a Skylake platform, what you probably should not do is patch the connector pipe to 0x12 and flags to 87010000 (those are typical Haswell HD4x00 properties), so I would remove the associated properties injection from your OC config, keeping only the connector type patch/property. If Webcam is USB-internal, it will either work OOB or not at all so no-one will be able to help you further on that point. Re: audio, try and experiment by adding CodecCommander kext. You can Google for it or look for it in the various packs of my various guides.

IOReg shows external monitor connected to con1 (as is the norm), not con2, and the connector-type is already set to HDMI type 00080000. Therefore all looks Ok on that front.

I've compared your DSDT with that of my Skylake E7270 and it's the same ACPI code throughout for AC and BATx devices. Try and adjust your OC config as follows: disable GPRW renaming disable SSDT-GPRW.aml

So you know what to do then...

What's the exact model? It could be one of those unsupported ones. Also try the NVMEFix kext, you never know. https://dortania.github.io/Anti-Hackintosh-Buyers-Guide/Storage.html

SSDT-XOSI is unrelated; keep it. That table's purpose is to set OSYS to the highest possible Windows version equivalent and ensure things such as USB3 is enabled on older systems or that brightness keys will work.

Can you extract your DSDT with maciASL and post it? You run latest BIOS 1.16.1 of March 2021 when Jake ran with BIOS 1.15.0 when he posted his guide back in February. Out of interest, I'd try to downgrade BIOS, you never know... But, Jake may tune in on the matter and he'll be able to assist you a lot better given that I've no such laptop whilst he does.

Ok, so Comet Lake platform with Intel UHD Graphics for 10th gen CPUs, i.e. UHD 620, not HD 520 which is a Skylake iGPU. Of course, you need to enable WhateverGreen to obtain graphics acceleration; don't disable it. Which version of OC are you using? Remove/disable XhciPortLimit quirk, that'll cause problems. I recommend you follow the Dortania's guidance for CML/UHD620 laptops as you're clearly missing some essential settings in your config. For instance, if you do inject the correct graphics framebuffer layout, you're not injecting fake id 0x3E9B as is expected. https://dortania.github.io/OpenCore-Install-Guide/config-laptop.plist/coffee-lake-plus.html