Hervé

Split to own thread to avoid further polluting of @tanya's Mouse/TouchPad topic.

You may also revert SMBIOS to MBP9,2 or MBP10,2 and use -no_compat_check boot arg.

As announced a few days ago, we've now upgraded our site and deployed a new Theme. We hope you'll all like it. Not only does it give a nice refresh to the site, it also fixes a few bugs we'd been suffering from for some months. Site should also run a little quicker. Many thanks to @Leon, @Syonagar and @Bronxteck for a job well done! OSXL Crew

Specs and zipped EFI folder please. Laptop going to sleep at login screen is typical result of running with a CPU PM SSDT meant for a different CPU that fitted to the hosting laptop.

If you used a bootpack labelled "Optiplex9020_A20", it was meant for a model running BIOS A20 or above. Start by updating your BIOS to the latest version. If you want further assistance, you'll have to post your system's specs and a zipped copy of the pack you used or a link to it since it existing stuff.

System going to sleep at login is typical when CPU power management is not in place as is the case here: no CPU-specific generated SSDT, incorrect kernel quirks, incorrect SMBIOS. So: generate your CPU-specific power management SSDT using good old Pike R Alpha's generator script remove XCPM and Lapic kernel quirks, they don't apply to an Ivy Bridge platform change SMBIOS from Haswell MBP11,2 to Ivy Bridge MBP9,2 or MBP10,2 remove vsmcgen and -lilubeta boot arg/flag, I don't believe you need the former and latter is totally irrelevant now (Lilu fully supports Big Sur) And post your system's specs of course so we don't remain in the dark...

Yes, you can enable the debugging/debug files and/or look into macOS log files; but if your system is fully working, I would not worry about ACPI warnings or errors and just ignore them.

Dec. 2010-Dec. 2020 It's hard to believe that it's been 10 years already! What a road since the early days of Snow Leopard on the Latitude D430! To celebrate this, we've undertaken a small forum clean-up, implemented some optimisation on the hosting server side, upgraded the community board and splashed out on a new forum Theme. We hope you'll all enjoy it and thank you for your loyalty to OSXLatitude. OSXL Crew View full article

Indeed, all looking good. The only thing I notice is that your display is detected as an external screen rather than a built-in LCD as you can probably see in "About this Mac". But it's probably without consequence whatsoever. Replace that slow 5400rpm mechanical HDD by an SSD and this laptop should be a joy to use.

What about card reader or Webcam (USB internal devices)? According to your previous IOReg extract, it looks like they're fully working too, right? Maybe you can post a new zipped IOReg output + a zipped SysInfo output.

Please note that the iGPU properties injection in this OC config are arguable. I guess they derived from the initial settings used for HiRes Capri FB 0x01660004 that only natively supports 1 x LVDS display output (for built-in LCD) and for which additional display outputs, taken from the LoRes layout, were injected. Given their origin, these properties don't really do any harm to FB 0x01660003 but they're not required at all. One noticeable item is the absence of property injection for the Capri FB memory size (to reduce it from 16MB to 8MB). Only 2 x properties should be used for patching the Capri LoRes framebuffer: 1 x for FB memory size and 1 x for HDMI audio. The properties injection should therefore look like: AAPL,ig-platform-id 03006601 DATA framebuffer-patch-enable 1 NUMBER framebuffer-fbmem 00008000 DATA framebuffer-con1-enable 1 NUMBER framebuffer-con1-type 00080000 DATA A few other things look irrelevant, like the -lilubeta boot arg; but these things are probably inherited from a time where Big Sur was beta and not fully supported by our well-known add-on kexts. Things can however be cleaned up now.

More likely the card than the adapter... Anyway, you clearly have defective hardware, so nothing to do on the Hackintosh side so to speak.

You can seek inspiration in existing Latitude 7490/7400 guides and threads. But as usual, post your hardware specs (CPU, chipset, LAN, wireless, audio, USB, card reader, etc.); we actually recommend to add those in signature... Good luck!

For your Atheros AR8121/AR8113/AR8114 Fast or Gigabit Ethernet LAN card (1969:1026), try this kext: AttansicL1eEthernet.kext.zip

Leave /S/L/E alone and full vanilla as a general rule. If you want to cache kexts rather than inject them through Clover, use /L/E. Good that you got audio with VoodooHDA. It shows that you've got ALC888 audio codec so you could remove VoodooHDA to experiment with Lilu + AppleALC + various audio layouts (from the AppleALC wiki). Place this patched DSDT in the ACPI/patched folder of your Clover EFI and use this new config file (without nv_disable=1 ) Patched_DSDT_6930G.aml.zip config_nv#3.plist.zip

Sorry, my mistake... You'll have to add VoodooHDA before looking again in DPCIManager re: audio codec.

Remove VoodooTSCSync

DW1510 should work with this.

Try this new config (without boot arg nv_disable=1): config_nv#2.plist.zip Once you obtain graphics acceleration on that GeForce 9300M GS, you can expect the following GPU power states (GPU core/memory clocks in MHz): 169/100, 275/250, 500/400, 580/400 or something like that... This if you replace the FakeSMC of my initial pack with this revised version: FakeSMC.kext.zip Perfectly normal that you have no audio (among other things), it's not been looked into yet. Try to run DPCIManager old app, it may show the codec your Acer runs with. If not we'll just got for VoodooHDA later on.

Answer to #1 is a definite "No!", this is an old Broadcom card for an old and obsolete CD/C2D MacBook A1181 of some sort so you can forget about that card (A1185 is the actual battery for Mac model A1181 by the way!). If you've read our inventories + my previous answer, answer is obviously "Yes!" to the other 3...

You should consider replacing that card by a fully supported Broadcom model. These AR9462 (and other AR9485/AR9565) were only supported with a special re-written Atheros40 kext and support has always been sort of poor not to say inexistant since Catalina. Assuming your E7240 is fitted with a mini-PCIe slot, go for one of those DW1550, AW-CB123H or AW-CB160H. If you have a full size slot, you may even consider a real Apple card (eg: BCM94360CD) in an adapter.

If the card you're talking about is meant to be a real Apple card, then it obviously requires no additional kexts than what macOS natively provides... As such, remove any such kexts from /L/E and/or your EFI kexts subfolder as well as any mention to it in your OC config file. Reboot and make sure to Reset NVRAM. Now, it'd be greatly appreciated if you would provide some specific details about your trouble rather than "does not seem to work"... What's not working? wireless, Bluetooth, both? Do you see the wireless card (PCIe) + BT module (USB) in IOReg? An Apple card requires an adapter so that it can be fitted to a standard mini-PCIe slot or M.2 slot. What do you use in that respect and how is it fitted? Note that, a few years ago, fake Apple cards were sold from a large country in Asia. Therefore beware and check the wireless + BT pci ids of your device.

Ok, we'll probably have to look into injecting adequate properties for your nVidia dGPU afterwards. Once you've finished installing High Sierra, you may update all the way to Security Update 2020-006 (build 18G14042). Take an IOReg extract from IORegistryExplorer, zip it and post it here. Meantime, you may try this config. Place the unzipped file alongside your existing config and select it from Options->Config menu when you reach Clover's main boot screen. config_nv.plist.zip

You'll have to switch to OpenCore and follow the steps/guidance already available in the numerous Big Sur threads relating to Latitude 7480. Look these up.