Hervé

If you use a USBPorts kext previously created with a different SMBIOS, yes, that's perfectly normal. Why? Because your mapping of USB ports no longer matches what you created. So you either: 1) revert to MBP11,x SMBIOS you previously used and add boot arg -no_compat_check or: 2) re-create your USBPorts kext with hackintool.

Obviously, Atheros40 kext is for Atheros cards and would therefore be of no use at all for a Broadcom card! Try this.

@tanya, you did not inject the properties I recommended. In addition, you've entered a totally invalid property "layout-id" which you should remove. Make sure you inject the following properties: AAPL,ig-platform-id 00001219 DATA framebuffer-patch-enable 01000000 DATA framebuffer-fbmem 00009000 DATA framebuffer-stolenmem 00003001 DATA framebuffer-pipecount 3 NUMBER framebuffer-portcount 4 NUMBER framebuffer-memorycount 3 NUMBER framebuffer-con1-enable 01000000 DATA framebuffer-con1-alldata 01050900000800008701000002040A00000400008701000003060A000004000087010000 DATA hda-gfx onboard-1 STRING and add the following boot arg to your NVRAM section, it's mandatory: agdpmod=pikera Of course, you may also experiment with the ig-platform-id value JakeLo gave in his post.

Copy the contents of the attached zip pack to your Clover EFI folder. It's very basic and, on the understanding that Acer Aspire 6930g is fitted with a Synaptics Touchpad, I've included the kexts than Dinesh developed and posted here. Aspire_6930G_10.13_Clover_Pack.zip We may need to revisit this if yours has an ALPS Touchpad because Acer's web site shows this as possible hardware too... One thing I'll ask you to do when you next boot your Clover USB installer is to press [F4] once you get to clover main menu. This will dump your BIOS tables to the ACPI/origin folder of the USB key. Zip that origin folder and post it so that we look at your DSDT and assess need for patching.

@Jorge1964, you need to understand that installing Big Sur requires something like 3 or 4 phases: you boot your USB installer, prepare your target disk/partition in Disk Utility (scheme + format) and complete 1st installation phase where all packages get copied to the target disk 1st reboot of the target partition (not the USB installer) where Big Sur packages will get properly installed on the target disk/partition 2nd reboot where the Big Sur installation completes 3rd reboot that gets you to the completed Big Sur installation and 1st boot system finalisation (setting of language/keyboard/user account/etc.) As JakeLo mentioned, it looks like you never went past phase #1...

Having the Clover EFI folder at the root level is not an issue; you may now check if Clover boots or not (you won't go very far but you'll see if USB key is now bootable). I'll prepare a basic pack that, hopefully, will allow you to proceed with installation, pending post-install tuning.

Did you or did you not install the OpenCore EFI folder to your target disk's EFI partition?

Did you try your Big Sur disk via F12 boot menu? That would normally be expected to add an entry in the UEFI boot list. Also check if you have Secure Boot set somwhere in your BIOS as you would probably need to have that disabled.

Same on my 7490, BIOS UEFI menu doesn't look anything like that. I never had to manually specify any UEFI path to boot, these were automatically added. @Jorge1964, you've got to make sure you place your OpenCore EFI folder in the SSD EFI partition. Of course, you have to mount it 1st and you can do that with various tools such as Clover Configurator, OpenCore Configurator, EFIMounter or manually through Terminal commands. See here for instance.

You need to: inject additional properties for the desired output ports (i don't think you need to inject device-id 1B19 by the way) change SMBIOS from Mac mini8,1 (a Coffee Lake model) to iMac 17,1 (a Skylake model). add boot arg agdpmod=pikera to bypass the native graphics output restrictions that apply to the selected (SMBIOS) Mac model Refer to the link I posted here. You'll then have everything.

Obviously, yes; it says so on your screenshot: "Set the order BIOS searches devices..." You will want OpenCore as #1. And you may want to remove the UEFI Boot path security to avoid the associated hassle, but it's up to you really.

@tanya please consult our FAQ section re your questions about iMessage, Facetime, etc. Thank you.

@Jorge1964, Your queries have been split to their own thread to avoid polluting @tanya's own research/advanced thread. With regards to target disk/partition, once you've booted the Big Sur installer: partition scheme: GPT (not MBR) format: HFS+, i.e. OS X Extended (Journaled) or APFS The installer will automatically convert partition to APFS if necessary. You cannot do any of this from Windows.

That's not exactly the reason why but Lion and later are indeed beyond your reach. Please consult the links I posted above. Thank you.

You won't get much assistance (if any at all !) re: installation of Leopard; it's far too old and we never supported 10.5 here anyway so you'd have to try your chances at other places like InsanelyMac. Given that the thread you found shows @TheNuutti8 had managed to install SL 10.6.8 on his Prescott-based 7100, try that, obviously it'll work! Apart from the CPU, specs of your 7100 should be identical. Since the vanilla kernel does not support P4 CPUs, use good old Nawcom's ModCD to install Snow Leopard (we've got a copy of ModCD on the forum); from memory, it uses legacy/modded kernel by default. It's what @TheNuutti8 had done. Most things should work Ok in 32bit kernel mode, but probably not in 64bit mode (eg: AC97 audio). The nVidia G210 should be supported OOB in SL; on the other hand, no support whatsoever for integrated GMA900 graphics of i915G chipset (not GMA950 as stated initially since that came with 945G chipset)... Good luck!

Unrelated to ProBook 650 -> moved to own thread.

Answers here and/or here. Do think of using the forum Search facility before posting. Note that you wouldn't be able to do much with such obsolete hardware and the old OS/software it'd support; even old Web browsers will be incompatible with many if not most of today's Internet web sites. Oh, and note that old (Prescot) Pentium 4 530 is 32bit, not 64bit... I would not waste my time trying to install Mac OS X on this old thing if I were you.

These (old) HotPlugging patches for AHCI disks will indeed be of no use if there is no initial support for your ICH10 SATA controller in AHCI mode. Their own stated description says all about their purpose... P43 chipset supports ICH10 (base) and ICH10R controller, so depending on which you have you could be lucky or unlucky. As described in ICH10 datasheet, ICH10 (base) does not natively support AHCI capability; it's conditional... Booting with your disk externally attached to a USB port, you may use Terminal commands to read the various registers that report of disk mode capability and status (you'll need to install tools such as the old lspci toolkit if you can find such stuff in 64bit). But even if the controller were to be returned as AHCI capable, you may find it difficult if not impossible to set it so given that BIOS does not offer the mode... This reminds me of the (fun) days when several of us Hackintoshers were trying to set the ICH7-M controller of the good old Latitude D620/D820 laptops to AHCI but miserably failed. BIOS would not offer the option it even if the controller was technically capable. You'd find threads/posts about this here with a little search. Anyhow, you could easily check the operating mode through any existing Windows or OS X/macOS installation. If disk runs in AHCI mode, it'll show in Windows Device Manager or SysInfo->Hardware->SATA. If your ICH10 only operates in IDE mode, you'll find AppleAHCIPort won't load, so HotPlug patch won't even apply... Rest assured that old Intel I/O controllers from ICH8 to ICH10 remain supported in Big Sur in AHCI mode (cf. Info.plist of AppleAHCIPort kext). It's a long time since I last checked but 'm pretty sure there's been no native support for legacy IDE mode in macOS these last few years in which case you could try and inject one of those old AppleIntelPIIXATA kexts from a previous version; no guarantee whatsoever that it would work... All in all, I'm pretty certain that the bottom line is: no AHCI, no Big Sur on internal disk. Last macOS version with an AppleIntelPIIXATA kext was Mojave 10.14.6; see attached IOATAFamily kext where you'll find the PlugIn; but no entry for ICH10 so you may have to create/add one... IOATAFamily.kext_Moj10.14.6.zip Of course, the best solution would be to opt for one of those supported PCIe SATA-III add-on controller cards. Would avoid all issues and give you full 6.0Gbits/s speed (ICH10 is SATA-II, i.e. 3.0Gbits/s only). Final word about the nVidia patching documentation you've referred to: it's applicable to nVidia dGPUs that are supported by the underlying OS! Not the case here and you must know that Tesla GPUs were dropped with Mojave which means there are no longer any drivers for these... Replace your card if you want to run Catalina/Big Sur.

Can you clarify the situation regarding this Big Sur attempt? Your system freezes whilst booting the USB installer? You have completed the 1st stage of initial installation and system freezes on 1st reboot? You have fully completed the installation and all subsequent reboots freeze as per screenshot? To be honest, I don't even know if Big Sur can be succesfully installed on a Wolfdale platform; I only briefly tried on my old Vostro 200 and failed. Big Sur won't support your old Telsa Geforce 210 card for sure, it'll have to go...

No, no, no, that won't work. 1st I don't even know why you'd use the El Capitan pack for Sierra but, most importantly, you just can't take a bootpack tuned for a Dell Latitude D830, apply it to a totally different computer and expect things to work. There's far too much stuff specific to the D830 in that pack that's neither relevant nor suitable for your Acer computer. I only made reference to the Dell guides for the general steps involved with regards to the installation process, not to use their bootpacks! Go for High Sierra and we'll try to work out a dedicated Clover pack for you. Do not use any Clover version from r5123 to r5126, these are troublesome.

You're gonna have to tell us more. You're trying to install Sierra but with what? What bootloader (Enoch? Clover?)? What pack? Can't see why you'd use boot arg nv_disable=1 on a laptop with a Tesla dGPU expected to be natively supported...

Don't hesitate to post your OpenCore EFI (Config, ACPI + kexts folders) for the benefit of the community.

MacBook9,1 SMBIOS + SKL framebuffer 0x191E0000 for Intel HD515 graphics, it would seem; correct ?

It would really be appreciated if people who use OpenCore would take the time to read the documentation posted at Dortania's. These people must have spent hours to write it and it is excellent. Common courtesy would be to refer to it.

Yes, see our FAQ section. To verify cache update, check presence of CodecCommander kext in Sysinfo->Software->Extensions; it should show there...