Search results

If you don't have a discrete GPU, there's no reason to use iMac18,2 or 18,3. The real iMac18,1 is the same thing as 18,2 or 18,3, just without an AMD GPU in them. Those system definitions will still be expecting the dGPU to be there, whether you disable the device in your DSDT or not, so...

If your profile is accurate, iMac18,1 is a better option for you. 18,2 and 18,3 have a dedicated GPU, which is why you see all the problems -- it's trying to use an AMD GPU that you do not have because on those models, the HD630 iGPU is only used for QuickSync and similar tasks, not video...

Yes. Serial numbers encode the model, location of manufacture, and year/week of manufacture. If you change anything in your SMBIOS information you must regenerate your serial # and check to make sure it's not one attached to a real Mac already, along with board ID and all other info.

This guide for the betas should still work fine with the final release.

Clean, successful update here. Multiple reboots, some with long pauses (45sec'ish). Just let it do its thing and came back a 10 minutes later to completion. OpenCore 0.5.1, latest Lilu, WhateverGreen, AppleALC, VirtualSMC.

https://www.tonymacx86.com/rules/ Also, see my earlier reply in this thread here: https://www.tonymacx86.com/threads/separate-data-partition-in-boot-drive-and-cant-install-supplementary-update.285278/post-2018751

You'd need a little more information than that. Which bootloader/version? What do you mean by "won't install"? What's the final error or message in verbose mode? EFI contents?

To expand on that a bit -- because Catalina now completely separates the system directories from data, and does so by making them separate APFS volumes within an APFS container and then mounting the system directories read-only, HFS+ is unlikely to ever be an option for Catalina installs; it's...

AFAIK, that's normal. On real Macs, as of Catalina nothing is supposed to touch the now-separate system partition in any way, period, except the OS update routines. If anything attempts to, it generates that error. Because this is supposed to, click "Install Anyway". The OpenCore boot...

And since it bears repeating -- the key word here is "begin". These patches are awesome for getting your ports all mapped out, but should probably not be relied upon for long-term use. Elsewhere in the OS internals, that 15-port limit is a fixed size array and these blow past the boundaries of...

Catalina changes how permissions to the system directories are handled. Before attempting any such change, you must remount the filesystem read-write. Hackintool can do this via the GUI, or you can do so in Terminal with: sudo mount -uw / killall Finder Reboot after your install to allow...

Correct: https://www.macrumors.com/2019/10/11/apple-seeds-macos-catalina-10-15-1-beta-1/

It's 64-bit for me.

Are you using the Lilu and Whatevergreen kexts? WG should take care of a bunch of compatibility issues with your GPU. If you change SMBIOS type (and you're right that iMac 18,3 or 19,2 is probably a better match), make sure to also update all the other data like serial number, board ID, and so...

Yes, the port limit patch works. But read the post I linked, it clobbers a fixed length array that macOS uses and can potentially write into areas of memory it's not supposed to. You should use it only to map out your ports so that you can create a proper SSDT that limits you to 15 ports...

(Some stuff collapsed so it fits on one page) What is your EC device, circled in my screenshot, called? It should just be "EC". It may be "EC0" or "ECDV", or even show up elsewhere in the list alphabetically as H_EC. If it is anything but just "EC", the error you're seeing will occur and you...

Is this an install on a system that was already working under Mojave? What does IORegistryExplorer say your EC device is called?

Your DSDT is not correct. Specifically, EC is called something else, like EC0. https://www.tonymacx86.com/threads/catalina-upgrade-stays-stuck-on-apple-load-bar-solved.284678/post-2013647

In general, you can check if you have any 32-bit applications by going to "About This Mac" (in the Apple menu), then "System Report..." Scroll down to the "Software" section and click on "Applications". Sort by the 64-bit column; you may have a couple things that say "no" directly from Apple...

Is it possible your GPU isn't turning down it's clock at all at idle? Maybe power management is not functioning -- have you seen / tried https://www.tonymacx86.com/threads/macos-native-discrete-gpu-power-management.247479/ ?