Hervé

Re: USB mouse, assuming the device is fully working/not defective, you need to ensure you've mapped all your USB ports, internal and external. You may use tools such as Hackintool to that effect or follow the USB mapping guidance available in the Dortania documentation. You should also consult the extensive literature posted by @tanya about her own Latitude 3400. She certainly achieved great success.

Try and experiment with the various CFL mobile device ids and mobile layout ids specified in the WEG user manual. You may find a combination that works. Failing that, you may also try the settings that applied to 8th gen Kaby Lake R platforms like the Latitude 7490. This being said, there are several people who posted about their Latitude 7400 laptop also fitted with Whiskey Lake i7-8665u CPU. If you run a search for 7400-related threads/posts on the forum, you'll find a few. Afaik, they all had graphics acceleration fully running with CFL layout 0x3E9B, CFL fake iGPU id 0x3E9B and MBP15,2 SMBIOS. You've got to properly configure the properties you inject of course, it clearly was not the case in the last screenshot posted by @tommyluco ("deviceID" instead of "device-id"). This particular post is pretty limpid on the matter to me.

If Firewolf's kext results in KP, try the previous kext developed by Cholonam's. Both normally support Realtek RTS525A readers. Re: brightness keys, your DSDT shows: 1) usual BRT6 brightness control method for Dell laptops Method (BRT6, 2, NotSerialized) { If (LEqual (Arg0, One)) { Notify (LCD, 0x86) } If (And (Arg0, 0x02)) { Notify (LCD, 0x87) } } 2) BRT6 called from EV5 method as usual Method (EV5, 2, NotSerialized) { \_SB.PCI0.GFX0.BRT6 (Arg0, Arg1) } 3) EV5 called from SMEE if OSID returns a value greater of equal to 0x20 as usual Method (SMEE, 1, NotSerialized) { Store (Arg0, Local0) Store (GENS (0x11, Zero, Zero), Local0) If (LGreaterEqual (\_SB.OSID (), 0x20)) { If (And (Local0, 0x04)) { EV5 (One, Zero) } If (And (Local0, 0x02)) { EV5 (0x02, Zero) } } If (And (Local0, 0x08)) { Store (GENS (0x1D, Zero, Zero), Local0) EV15 (Local0, Zero) } } 4) SMEE called from SMIE method as usual Method (SMIE, 0, NotSerialized) { Store (GENS (0x10, Zero, Zero), Local0) If (And (Local0, 0x04)) { SMEE (Local0) } If (And (Local0, 0x02)) { EV7 (Zero, Zero) } If (And (Local0, 0x08)) { EV9 (Zero, Zero) } If (And (Local0, 0x40)) { EV8 (Zero, Zero) } If (And (Local0, 0x80)){} If (And (Local0, 0x10)){} } 5) SMIE called from NEVT method as usual Method (NEVT, 0, NotSerialized) { Store (ECG1 (), Local0) Store (ECGD (), Local1) Store (Add (ShiftLeft (Local1, 0x10), Local0), Local2) [...] If (And (Local0, 0x80)) { SMIE () } } So, given that all is exactly as per other previous generations of Latitude (E6x30, E6x40, E7x50, E7x70, etc.), you can apply the same patches as we've detailed in our various guides: 1) in your bootloader ACPI config rename OSID to XSID -> to avoid bug after _OSI renaming rename _OSI to XOSI -> to bypass _OSI rename "BRT6,2" to "BRTX,2" -> to bypass vanilla BRT6 method 2) inject the following SSDT tables: SSDT-BRT6.aml -> injects new BRT6 method with correct key values for brightness control SSDT-XOSI.aml -> ensures OSID returns the required value You'll find those in, say, my E7270 guide. You should then have working brightness keys

Yes, though it's always better to obtain the IOReg extract from an app like IORegistryExplorer than provide a text-based one that is most difficult to analyse. Did you use this? https://osxlatitude.com/forums/topic/10209-how-do-i-generate-debugging-files/?tab=comments#comment-97908

-> moved to Monterey beta section where this thread belongs; please make sure to post in the forum's relevant sections. Thank you. With regards to your observations and experiments: 1) Monterey is at initial 1st Developper Preview stage at this point of time 2) Monterey carries no native support for HD4000 graphics that have now been officially dropped from macOS 3) HD4000 can only be supported after patching Monterey beta1 with tools such as OCLP v0.1.7 and later 4) Automatic login must be enabled after 1st boot and until you patch Monterey, failing what you end up with the graphics initialisation failure loop you currently experience I had already mentioned this in my Monterey beta1 thread posted in this very section. Please note that you're highly likely to experience reduced performance, very high temperatures and regular crashes with Monterey; it's very early stages and it does not run too great on dropped Ivy Bridge/HD4000 platforms for the moment. Best is to wait for subsequent beta versions and further development on the patching side.

Looking at your posted IOReg, I see that your SD card reader is a PCIe Realtek RTS525A (10ec:525a). As such, I expect the new beta driver recently offered by Firewolf to bring life to yours. Just try and inject it. On the brightness keys front, I would not expect much out of that kext mentioned at Dortania. To me, the existing solution of combined ACPI + SSDT patches is spread wide enough to pretty much vouch for it across the Latitude generations. I would therefore also expect that applying the documented method should work on your 7310 laptop too. But post your extracted BIOS tables so that we have a look, especially at your original DSDT.

There's renewed interest on the development of drivers for Realtek PCIe card readers and it's fantastics news! Last year, we reported here on Cholonam's work that, building on the original work of developper Sinetek, gave a new life to some of our Realtek card readers. It was pretty good stuff and allowed many of us with, say RTS525a card readers, to finally be able to use SD cards under macOS. Performance was however pretty limited. This year, Austere.J (aka Firewolf) has embarked on writing a brand new driver and, my God, is it good! The driver is under active development as we write but Austere.J has started on the RTS525a with super results and he's adding support for other Realtek RTS models too. 2 x major improvements compared to Cholonam's driver: the card reader is now reported as built-in in SysInfo the card's full performance is being achieved You can follow the on-going R&D here at Insanelymac and drivers are posted here on FireWolf's GitHub repo. Please join me in helping Austere.J in the testing and give him the support and thanks he deserves. View full article

I understand that ALC3236 codec is ALC233; look that up in the AppleALC wiki and experiment with the various layout ids listed. https://github.com/acidanthera/applealc/wiki/supported-codecs Re: AR9565 wireless, those were never natively supported and required a specifically re-written Atheros40 kext. Then, performance was not great. Knowing that you'll probably have trouble getting this card to work under Big Sur, it'd be far better to replace it with a fully supported M.2 model. You can check these out in our wireless cards inventories and our M.2 wireless cards inventory, all available in our R&D->Wireless section.

You're using an EFI made for a different model that may not have the exact same hardware specs as your own particular laptop. You need to identify your audio codec and specify the make & model of your wireless card. Don't hesitate to open up your laptop to look at the label of the wireless card. Failing that, post an IOReg extract saved from IORegistryExplorer app.

OCC app gets aligned with versions of OpenCore. So, you must have a mismatch between the version of OCC you used and the OpenCore version you've installed. In most case, these warnings can be ignored but OpenCore can be subject to updates that completely modify the way parameters are defined. In rare cases, you could find yourself in a situation where a config file updated through OCC would no longer allow you to boot OpenCore due to changes in the config that aren't supported by an older version of OpenCore. For instance a config updated by OCC for OC 0.7.0 when installed OpenCore version is, say, 0.6.3 or 0.6.5. If you don't update OpenCore, don't update OCC either. Keep them aligned. Right now, you should probably update OpenCore to 0.7.0/0.7.1 and OCC to the latest available version, v2.44.0 at time of writing. Then stop there.

Usually, I turn TPM & USB Wake Support off.

Glad to see that you got graphics acceleration after entering the suggested properties in the correct reverse byte order.

It's 1st beta and Bluetooth is buggy, even for real Macs. So guys, just be patient.

Remember to post your system's specs in signature.

What else? Please note, that as far as I can see, trying to enable HDMI2.0 on hardware limited to HDMI1.4 is most likely useless...

I would not compare the settings of 8th gen Kaby Lake Refresh 7490 with those of 10th gen Comet Lake 7310. By all means, do post the list of setting you use because we don't necessarily know what the 7310 offers (I certainly don't). After you make changes to your OC config, you clear NVRAM, right? Which version of Catalina are you trying to install by the way? From memory, Comet Lake and Ice Lake are only supported from 10.15.3 or 10.15.4. Check it out in the Software section.

Your E5550 is a Broadwell laptop. Given that the tool you've opted for does not seem to support Broadwell mobile platforms (it appears it skips those and only supports High-End Desktop (HEDT) 140W 6/8/10-core Broadwell-E platforms which the E5550 sure ain't based on). I would therefore recommend that you leave that tool aside for the time being and follow the Dortania OpenCore documentation to build your setup. You may use OpenCore Configurator app (aka OCC) to create your OC config. I also invite you to read the existing guides for E5x50 models published in our Guides section and the existing threads about installing and running Big Sur on to the E5x50 laptops in this very section. My final recommendation would be that, if you're totally new to OC, you stick to Clover for the time being (update to r5133 or later) and experiment with OC on an external drive. This so that you don't totally lose dual boot or find yourself stuck with the potential side effects of OC in Win10.

i7-10610U is Comet Lake (not Whiskey Lake) so I don't think you're injecting the correct properties for your CML iGPU fake id and FB layout; according to the WEG user manual and the Dortania OC documentation, you should be using: ig-platform-id 0x3E9B0000 device-id 0x3E9B

OCLP 0.1.7 patcher has been released. It brings support for HD4000 graphics in Monterey beta1. https://forums.macrumors.com/threads/macos-12-monterey-on-unsupported-macs-thread.2299557/post-30014550 Make sure to enable automatic login quickly after 1st boot setup to avoid subsequent problems with the Windows server/graphics initialisation and consequential inability to complete the boot and reach desktop. Tested on my Latitude E6230 on an external USB disk. Runs at much higher CPU speeds than before and therefore very hot at times. Will probably have to experiment with CPUFriend on that front. Probably why system is unstable and keeps crashing with sudden complete reset after a while.

Please post your system's specs in signature. Also, please refrain from using quotes to post replies. As per our published rules which I invite you to read, please use the Reply box at bottom of each page. Try SKL layout 0x1916 instead of 0x191b + SMBIOS MBP13,1 instead of MBP13,3 to see if it makes any difference.

These tools are made for real Macs so the process does not fully apply to Hackintoshes on which you would boot with a usual bootloader setup and then apply the patcher to your build.

Some people reported slow boot with beta1. 1st workaround is to enable automatic login. https://www.insanelymac.com/forum/topic/348065-pre-release-macos-monterey/page/10/?tab=comments#comment-2760529 https://www.insanelymac.com/forum/topic/348065-pre-release-macos-monterey/page/11/?tab=comments#comment-2760595 2nd workaround is to replace your account's picture by a Memoji. https://www.insanelymac.com/forum/topic/348065-pre-release-macos-monterey/?do=findComment&comment=2760673

Enable automatic login and report.

Impossible to provide any form of assistance in such conditions... Please post your system's hardware specs. Specify the target macOS version (eg: Catalina 10.15.7, Big Sur 11.4) Specifiy the bootloader you're using and its version Post a zipped copy of your EFI folder with ACPI & kexts folder + config file Maybe you're re-using an EFI folder grabbed somewhere that includes settings for Intel wireless card; maybe you don't have such a card. Rule #1: know your hardware before you start anything.