Hervé

Possibly, Redo your mapping and verify your SSDT tables are adequate/appropriate.

-> Thread moved to relevant hardware support section; this is not a thread about hardware information. Please make every effort to post in the appropriate forum sections and to use punctuation, not just post in a single extended sequence of words! This is totally unreadable and such posts/threads be deleted without prior notice in the event of re-occurence. Assuming you've followed all the necessary recommendations posted at ITLWM, you can always try and re-apply the Windows driver for the card in the hope that it'll reload the firmware onto the card if that's what's gone sideways. But you may have to consider that the card is either suffering from a bad connection (try and clean the cards connector and the slot) or simply got defective (it happens). Check if the Bluetooth module is seen or not in SysInfo->Hardware->USB. If it's not, as per in Windows, you have a hardware-related issue. it's probably not the case but do check that Bluetooth did not get somehow disabled in BIOS settings.

No such thing as a Latitude "E7480", there are only Latitude 7x80. Renaming thread and adjusting contents + moving thread to the Latitude 7000 Series section. Grab the PS2/I2C kexts from EFI folders posted in existing Latitude 7280/7480 threads and adjust your bootloader's config accordingly.

I don't recall needing to set or select Legacy Boot option to boot the GrubShell USB key on my Latitude E7270 but if @BillDH2k managed to do it on his Latitude 7400, I can't see why you couldn't...

DVMT must indeed be set to 64MB minimum to be able to obtain 4K output. 4K cannot be achieved with DVMT set to 32MB. See our published article on the matter: https://osxlatitude.com/forums/topic/17804-dvmtstolenmemfbmemcursormem-why-do-we-patch-these-for-broadwell-and-later There's normally no need to set DVMT to more than 64MB/96MB.

I'd advise to set hibernatefile before you remove the sleep image file; to ensure it stays gone if nothing else. You probably ought to revisit your DSDT patches. You've injected quite a lot of patches for USB but did you try things out without any of those?

You should delete the sleepimage file in /var/vm -it often leads to trouble at wake- and ensure Power Management settings point to null device for the hibernate file. Basically, I suggest you follow the recommendations posted in our FAQ topic. MBP7,1 should be the ideal target SMBIOS site you have a Penny C2D platform but if you feel your laptop works better with a different one, then use whatever suits you. Re: USB ports, sounds like you need to do or redo the mappings when you switch SMBIOS. Also remember that: OHCI = USB1.x UHCI = USB1.x EHCI = USB2.0 XHCI = USB3.x With Big Sur, Apple started to drop some older USB technologies so Big Sur and later versions require what is called the USB HID fix to circumvent the USB-related issue. This is mostly applicable to older systems like C2D/C2Q platforms but I found it also applicable to more recent platforms like, say, Skylake when fitted with hardware accessories based on older USB technology (eg: touchscreens). You've made no mention of it but I can only assume you use the OCLP app to patch your unsupported platform; latest versions are supposed to somehow address the USB1.1 issues but I've not read about it yet so I don't know how applicable this may be for your old laptop.

It's not meant for Hackintosh but for real Mac computers; hence why you have to use it with outmost care...

Thanks for posting the specs; a very old laptop indeed. You should be using SMBIOS of MacBookPro7,1 rather than MBP6,2 which was a 1st gen Arrandale platform. Also note that OpenCore does not properly care for CPU power management of pre-SandyBridge systems. As such you may want to consider switching to Clover (r5150 or later for instance). Re: wake issue, did you disable hibernation? It's enabled by default and certainly needed to be disabled on most platforms in the past and still today. You may lookup our dedicated thread on the matter in our FAQ section. Re: DSDT, don't hesitate to list the various patches you applied/implemented; this is not something we'll be able to guess. One final comment about your OC config and the graphics properties you inject, I'm not sure you got that right. The IO location you specified looks erroneous to me; but it sure does not prevent you to gain graphics acceleration according to your IOReg. For your info, your nVidia dGPU is PCI0.PVGA.GFX0 so the correct device location is "PciRoot (0x0)/Pci(0x1, 0x0)/Pci(0x0,0x0)". You should therefore adjust your config to remove what I believe to be a typo of some sort in your config:

Can you please post the full specifications of this computer? Is it a desktop or a laptop?

According to kronokernel, patch for BCM43224 still works in Monterey (or, at least, it did in the summer of 2021 and Monterey beta days): https://forums.macrumors.com/threads/macos-12-monterey-on-unsupported-macs-thread.2299557/post-30034783 https://forums.macrumors.com/threads/macos-12-monterey-on-unsupported-macs-thread.2299557/post-30038647 I've not looked at what the OCLP solution does in that respect but, assuming it breaks the seal and somehow copies the necessary kext in /L/E or /S/L/E for caching, then the on-the-fly patch (in the bootloader's config file) would work. You'd have to target MacBookAir5,2 or MacBook7,1 for OCLP to install the necessary kext and patch macOS accordingly.

Then I guess the old patched kext has had its time... Try OCLP as alternative.

It was mentioned on p1 but macOS OTA updates require that your booted system complies with a set of pre-requisites: SMBIOS of a fully supported Mac model (unsupported models will not attract updates) no -no_compat_check boot arg no Apple_Internal SIP flag enabled (5th bit of csr_active_config parameter). See our SIP-related FAQ topic for details These apply to systems using Clover. For systems using OpenCore, I vaguely remember that there's another pre-requisite around SecureBootModel or something of that essence; you'll have to look that up. You may therefore need to have 2 x configs at hand to be able to obtain and install Ventura updates on your unsupported platform: your current config and a specific "supported model" config (eg: MBP14,1 SMBIOS, no -no_compat_check, SIP=0xFEF) that you'll use exclusively for updates. Given that you're running Ventura on a Haswell Latitude E5440 with HD4400 graphics, you used OCLP patching to apply root patching and gain graphics acceleration. Make sure the option you selected/unselected in the tool do not prevent OTA updates. Check out the tool's documentation. On a real Mac, default parameter for the targeted system do support OTA updates, but that's real Mac...

Updated for 2023.

https://dortania.github.io/Getting-Started-With-ACPI/Universal/smbus.html Consider it entirely optional; if, in your own particular case, it breaks sleep just get rid of it. 'never used it on any of my Hacks.

So, what you actually do is binary patch the AirPortBrcm4360 PlugIn of that IO802Catalina kext, right? What patch do you apply? For what target SMBIOS model?

Where are you with your current config ? Are you sure you have the best possible settings in place?

You'd have to explain in details the various steps you followed to try and recover support for your DW1520 card in Monterey but, as stated here several years ago, Big Sur dropped support for Broadcom BCM43224 chipset so follow the suggested/recommended procedure to try and regain support for your card.

You're not using a suitable SMBIOS for your laptop. For some strange reason, you've opted for MB11,1, i.e. a Haswell platform that does not carry Ivy Bridge (Capri) HD4000 graphics nor supports CPU PM for Ivy Bridge CPUs. MBP11,1 being a Haswell platform with Haswell (Azul) graphics, there's just not a chance in the world that OCLP will apply HD4000 patching for such a target profile. Please follow the recommendations you're given and read the OCLP documentation to try and understand what it does (bearing in mind it's made for real Mac computers, not for Hackintosh). Until you do so, you're wasting your time and ours.

Can't really help much without proper troubleshooting info. You asked if the method I described in my E6230 guide would work on the E6530 and I said "try it", not "grab everything meant for the E6230 and apply it". You said you had Big Sur running on that E6530 before; well, take that setup and adjust it for Ventura by adding the kexts and config changes I described in my E6230 guide: AppleIntelCPUPowerManagementClient kext (of Monterey origin) pre-patched AppleIntelCPUPowerManagement kext (of Monterey origin) if you use those (something entirely optional), updated FakePCIID + FakePCIID_XHCIMux kexts, the old versions causing KP CryptexFixup kext AMFIExemption kext -crypt_force_avx and amfi_get_out_of_my_way=1 boot args SMBIOS MBP14,1 of course, it's advisable to update Lilu & its PlugIns to latest versions so that you run versions that support Ventura (but really should go without saying) I don't even know if you're using Clover or OpenCore but assuming you use the former, follow the method described in my E6230 guide and have a dedicated MBP14,1 config file to start with. Also make sure your nVidia dGPU remains fully disabled. Once you run OCLP, do target the SMBIOS of your original bootloader's config, whether it be MBP9,x or MBP10,x. I've no idea on the matter and you've not be forthcoming with any specific info on anything. All in all, just try and apply good common sense. Once you've completed the OCLP root patching, you simply reboot and run with the same config file you used for Big Sur. Do not go for Ventura 13.3 beta, stick to mainstream releases. Maybe you should have experimented with Monterey to begin with, at least for the OCLP patching if nothing else..

My E6230 pack contains patched DSDT, SSDTs or kexts that apply to the E6230; they do not apply to your E6530 especially as it's a model with NVIDIA graphics and totally different CPU. It should be obvious not to re-use the E6230 pack "as is" on your E6530 and you should re-use the ACPI patched tables and most kexts (eg: for USB ports) you were previously using on your E6530.

So... you installed Ventura Ok, albeit without graphics acceleration, right ? you applied the OCLP root patches with the settings detailed in my E6230 guide ? on reboot, blank screen when graphics are supposed to initialize ? You'll have to be more specific and, say, post your (default) config as I suspect you got something incorrect there. Possibly a mismatch between the SMBIOS in your config and the target SMBIOS (MBP10,2) selected in the OCLP settings. If your config is not set with the same SMBIOS as selected in the patcher, I don't think it'll work... It should be obvious but maybe you missed that essential point.

We still get the question regularly so a FAQ topic seems appropriate... Injecting a laptop built-in screen's EDID information in OS X/macOS is sometimes required when the freshly installed OS does not display the desktop properly on screen due to incorrect detection of the screen's hardware properties/capabilities (frequencies, size, etc.). The following describes one easy way to collect a screen's EDID info through an off-the-shelf Windows app but they're are several other methods too (see this somehow complicated method in this deprecated thread for instance): I can recommend Monitor Asset Manager. I've used it several times in the past. Very simple to use and works without failure. You'll get the EDID info at the very bottom of the application's main window where it is displayed as a long string of comma separated hexadecimal values. This is what you need to collect and edit to remove all commas and spaces. You may then inject the resulting raw long string of hexadecimal characters as device property in the iGPU settings of your bootloader's config: AAPL00,override-no-connect <EDID's hexadecimal string> DATA See the WEG User Manual for reference

Ok, you misunderstood a few things: You do not patch a framebuffer's connector to set an external screen in mirror mode; that's done from the booted OS, either from the Display Preference Panel or with keyboard shortcuts ([COMMAND-low brightness] combination). Make sure you remove those incorrect patches in your bootloader config. The only patch you ought to have is to set con1 to HDMI type (00080000) in order to gain HDMI audio output. Framebuffer connectors effectively define physical video outputs. Grabbing your screen EDID from IOReg to then inject it in your bootloader's config is utterly useless; you effectively inject what the system natively detects. See this FAQ topic for details of the procedure to follow.

Try it!