Hervé

No ASF2-ralted power off then, which is re-assuring because these are a nightmare when it comes to root cause. So, other than the ACPI-related cause, nothing other than your own manual forced shutdown, at least for today. Regarding ACPI Power Management shutdown, my guess would be that it's due to excessive heat causing CPU to go into protection mode. Do you have any CPU T° monitoring in place at all like with HWMonitor app? You'll have to post a zipped copy of your OC EFI folder or, at least of that SSDT-5470 patched table of yours, for us to provide further assessment. Using these single SSDTs really is best avoided as, once again, likely to be proven more problematic than beneficial... Do you experience the same behaviour if you disable your (DW1820A) Wifi card in BIOS or physically remove it? I know you apply the required ASPM patch but...

Please don't quote messages to post replies; forum provides a Reply box at the bottom of each page. Your code is Ok but if you renamed your table, make sure you also rename it in your OC config and Reset NVRAM at OC Picker when you reboot. I've tested the stated principle on my own E7270 (with a different SSDT of course) and it works just fine.

RTC-related issue, causing CMOS reset and BIOS settings to return to default. There are bootloaders values you can use in your config to avoid that. It's documented in the OpenCore materials (GitHub repo and probably Dortania). Failing that, you'll find it somewhere on our forum (just can't remember where); from memory it's was something that propped up with Catalina 10.15.4. I probably listed the fix under the Software Matters section so look it up. The issue really depends on the platform you try to run macOS on so please post your system's specs, ideally add them in signature.

You would not have this kind of problem with Clover. However, with OpenCore, one solution to fix this is to apply an "If Darwin" condition to your SSDT so that it only applies to OS X/macOS and will be ignored when you boot any other OS. This may be done as follows: DefinitionBlock (<bla bla bla>) { External <bla bla bla> ... If (_OSI ("Darwin")) /* places SSDT code under condition of running OS X/macOS */ { Device (RMCF) { ... } Scope (_SB.PCI0.RP05.PEGP) { ... } ... ... ... Device (RMD3) { ... } } /* endif */ } In other words, you place all the code past the heading External declarations within this conditional section: If (_OSI ("Darwin")) { ... } and Bob's your uncle!

You should be able to get the brightness keys working by applying the ACPI patches described in the thread dedicated to that matter in our Technical info/R&D section. 'don't understand your issue. Won't work, no support for this type of hardware in macOS.

Check your BIOS logs. Any ASF2 related entries?

Your Maxwell Quadro M1200 (not M12000) appears correctly disabled since it's not visible in IOReg. But first thing first: please post your system's specs in order to confirm whether your Precision is indeed fitted with a Skylake CPU, not a Kaby Lake CPU. Right now, you seem to be confused on the matter. Your IOReg suggests to me you have a Skylake model (iGPU with device id 8086:191b = HD530). Regarding the (apparent) Intel HD 530 iGPU, despite running Big Sur and Monterey (you took your IOReg in Big Sur), not Ventura, you inject Kaby Lake properties (device id 0x5912 and KBL framebuffer 0x591b0000), not Skylake. You also use SMBIOS MBP14,3. If you have a Skylake CPU with HD530 graphics, this is incorrect given that Big Sur and Monterey are expected to run with SKL settings, not Kaby Lake HD6x0 settings (and you do not use WhateverGreen kext v1.6.X with boot arg -igfxsklaskbl). You also: inject boot arg agpdmod=vit9696 which is unlikely to be required inject a whole load of properties which, I think, is irrelevant: I certainly don't inject any if this on my Skylake/HD520 Latitude E7270 and HDMI output works just fine, I just need to inject the boot arg igfxonln=1 to retain built-in LCD when HDMI is connected. Assuming you indeed have a Skylake platform with HD530 graphics, you really should: revert to SKL properties injection (device-id likely not required, SKL framebuffer 0x191b0000 or 0x19160000); see the WEG manual here. remove the properties I've highlighted in red use SMBIOS MBP13,1 if applicable, patch your BIOS to set DVMT to 64MB so that you no longer need to patch fbmem and stolenmem in your config (and gain 4K output along the way). If you were to continue with Kaby Lake settings and retain KBL framebuffer 0x591b0000, please note that you'll have to: update Lilu and its PlugIns (AppleALC and -most importantly- WhateverGreen) to the latest versions and add boot arg -igfxsklaskbl to your config. patch connector con1 for HDMI output or it won't work. Patch is explained here. It's best to opt for KBL framebuffer 0x59160000 which natively supports HDMI output.

As Jake & I said, you need to Reset NVRAM after making changes to your OpenCore config. Only you can do it. Of course you need to have the necessary OpenCore EFI module installed in the Drivers folder. You can configure OpenCore to display this option in the Picker by enabling the module in your config or you can press [SPACE] at the Picker to obtain the option. You'll find tutos on YouTube if you care to search a little. I would also suggest that : you use the latest version of OpenCore you use the latest versions of your add-on kexts you never mix a kext and its PlugIns from a different version (or expect trouble); eg: VirtualSMC & PlugIns... If you want to continue engaging in building your own OpenCore setup, I strongly recommend you start by reading & learning about OpenCore. The Dortania documentation is a good place to start. Otherwise, you'll just continue to struggle to get anywhere... https://dortania.github.io/OpenCore-Install-Guide/ https://dortania.github.io

Did you Reset NVRAM from the OpenCore Picker (the OpenCore menu at startup)? It's essential/mandatory you do that after any OC config change.

You probably have an erroneous OC config file. Possibly a typo somewhere. Get it checked by the validator.

I'm not familiar with several of those patched SSDT tables you use. All I can suggest is that you compare with setups of other similar 5490 or 7490 posted on the forum.

Modernising this fairly old thread to update it for property injection with our beloved Clover/OpenCore bootloaders. As stated in the posts above, the alternative to DSDT patching (deprecated today), patched SSDT and/or kext patching (totally deprecated today and most difficult since Big Sur) is to simply inject the properties detailed above in the bootloader's config: identify card reader's location (with say IORegistryExplorer or bootloader's device detection) inject the compatible property as bare minimum, the rest being entirely optional and cosmetic Device: PciRoot(0x0,0x0)/Pci(0x--,0x--)[/Pci(0x--,0x--)] -> 3rd location may not be applicable Property: compatible pci14e4,16bc STRING -> mandatory AAPL,slot-name <specify your PCI slot here> STRING -> optional/cosmetic device_type <specify the device type here> STRING -> optional/cosmetic name <specify a device name here> STRING -> optional/cosmtic model <specify the model ref. here> STRING -> optional/cosmetic Clover example; under Devices section:

Yes, details of the necessary patch are posted in the thread dedicated to that matter; you'll find it in the Technical info/R&D -> Card readers section. It applies to all versions of OS X/macOS that the Sandy Bridge E6x30 laptops may run. Process could not be simpler: identify your card reader location in IOReg inject the necessary property in the Device Properties section of your bootloader's config For instance, if your card reader is under RP0x@1C,5->PXSX@0, your property patch would be: Device location: PciRoot(0x0)/Pci(0x1C,0x5)/Pci(0x0,0x0) Property key: compatible Property value: pci14e4,16bc Property type: STRING Do browse the forum and call on the forum Search facility for future inquiries.

It's supposed to... if you can get it out of AirPlane mode under macOS. See previous EM7455 thread in this particular section.

Could be result from all those power-related ACPI patches and patched SSDTs you' re using. Can't say I've seen or used them before on my Kaby Lake R/UHD620 Latitude 7490 when I had it. Why don't you try experimenting without those (SSDT-MethodS3-disable, SSDT-PTSWAKTTS and associated ACPI patches on the OC config)? I'm also surprised you run with MBP14,1 SMBIOS for that laptop, rather than MBP15,x.

Look at our WWAN section here for possible assistance re: WWAN module. But given the availability of data connection sharing on SmartPhones, I see very little use for WWAN modules these days; and these require a SIM card to be inserted in the laptop too.

No, VGA may somehow work (and only OOB) but feel free to knock yourself out at it!

macOS has had no official support for VGA since Ivy Bridge. Beyond Sandy Bridge (the last platforms for which Intel framebuffers connectors could be patched for VGA), the only platforms for which VGA is known to work properly (and OOB) for certain under macOS are Haswell laptops with HD4400 (not HD4600) graphics. For newer platforms (eg: Kaby Lake R laptops), VGA either works OOB -and sometimes only in mirroring/clone mode of another external screen- or not at all. There are no settings you can deploy to obtain VGA output per sé. Afaik, if VGA output does not work OOB, you'll never obtain it on your Skylake laptop. Here, you'll find details of the experiments I conducted several years ago with VGA output on a Kaby Lake R Latitude 7490, the analog port being available on a USB-c Dock, not as a built-in port of the laptop. Re: Bluetooth off your Intel AC 8260, you need to follow the guidance posted at ITLWM repo/web site. NB: I don't know where Dortania folks got the idea that, on Skylake platforms, VGA was treated as DP but that's news to me (and I've been hackintoshing and working on graphics settings for quite some time)! Probably resulted from the observation that a working VGA output registered in IO against a framebuffer connector of DP type but that's quite a shortcut to subsequently state that "VGA is treated as DP"... They occasionally write and affirm incorrect things or contradictory information. For instance, in the installation guide for Skylake laptops, they post settings for HD510 graphics, thereby wrongly indicating that HD510 is supported whilst, in their GPU buyers guide, they correctly state that HD510 is unsupported; macOS has indeed no support whatsoever for GT1 Intel iGPUs ! In the same respect, they state that VGA connector type 10000000 is unsupported in 10.8 and newer, yet I had no issue with such VGA patching of the SNB framebuffer up to High Sierra (and later) on the Sandy Bridge/HD3000 Latitude E6220 I previously owned.

You gotta do your homework. I see that you have Clover Configurator app so look out for its cousin OpenCore Configurator. Failing that, if you read the Dortania documentation, something you really should do, you'll find references to tools such as ProperTree or other plist editor (eg: Xcode, Plist Edit Pro, etc.). I also invite you to learn how to take screenshots in macOS, something detailed in the keyboard Preference Panel. Screenshots are a million times better than poor/unreadable shots from smartphones.

No need for the following iGPU properties on Haswell graphics: framebuffer-fbmem 00009000 DATA framebuffer-stolenmem 00003001 DATA Make sure to remove them, reboot and reset NVRAM at OC Picker before booting Big Sur. Re: wifi, no idea about the hardware you got in place so, you'll have to post full specifications of your (E5x40 ?) laptop, whatever that may happen to be. Now need to look into your patched DSDT and SSDT in case those add conflicting stuff for your graphics. Checking up your OC config, I see that you do not inject the patched DSDT; wise decision given that it probably contains erroneous stuff. I already noticed this patcher the iGPU: Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x06) { "AAPL,ig-platform-id", Buffer (0x04) { 0x06, 0x00, 0x26, 0x0A }, "hda-gfx", Buffer (0x0A) { "onboard-1" }, "AAPL00,DualLink", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 } }) } which is incorrect (missing fake id 0x0412 and DualLink property invalid on Haswell iGPU).

You post in the Latitude E5xxx Series; pease specify your laptop model. Haswell-based E5x40 I presume. Please post a zipped copy of your bootloader's config and, if possible, an IOReg extract + SysProfiler extract. Very little we can do without minium information and, in all likelihood, you have some incorrect settings.

Audio should work with the exact same settings you previously had for Monterey. There should be no issue at all on that matter. Same applies to brightness control. For Wifi and Bluetooth, you need to consult the information available on the ITLWM site. Development for Ventura remained at early alpha stage until very recently (I've not checked status for several weeks) so make sure to check the latest information published by the devs.

Re: sleep, follow the steps detailed in our FAQ topic on the matter. Basically cancel hibernation and revert to plain old sleep with deletion of the sleepimage file. I'm reviewing your setup and I can already see some stuff needing to be changed. For instance: 1) you patch fbmem which is wrong; no need for such patch on Ivy Bridge HD4000 so make sure to remove that property: framebuffer-stolenmem 00000004 DATA 2) never seen the need for SSDT-EC-USBX on an Ivy Bridge laptop; afaik, this is for Skylake and later platforms. 3) not sure you need the SSDT-GPRW either. 4) renaming device EC to ECDV normally suffices, I don't thing you need the SSDT-EC-LAPTOP table. 5) don't think you need those PICI and TIMR ACPI patches that I see in your config; need to check the HPET and RTC ones as they look a little unusual to me for the platform.

Quad core i7-3740QM CPU, DW1510 Wireless card, HD4000 with LoRes LCD screen (no nVidia dGPU), right?

Post a copy of your latest EFI folder. We've had plenty of threads and guides for these ageing E6x30 models for years so I'm surprised you have such issues with your Catalina build. You may also want to switch to Clover; it's a lot less daunting than OpenCore and works perfectly on those old Ivy Bridge laptops.