Hello everyone again! I need help with "Catalina" installation. I already had "Mojave" installed. I guess something wrong with my EFI partition because every time I see
You can review my current EFI folder. As you can see I have installed Windows also. I'm afraid to clear that partition because Windows configuration will be lost.
During "Catalina" installation, I just recreated AFP partition where "Catalina" was installed.
So the question is how to correctly remove previous Clover bootloader to make possible "Catalina" installation and restore Windows record after?
I created a bootable USB using the OC EFI folder.
Thanks in advance!
Mount the EFI partition on your USB Boot drive and replace the EFI folder with this one. Boot from it and use it to install, if there is an existing OS X installation or a useable partition it should install, if not that is something you will have to work out. You can always back up and reinstall OS X and Windows
For those with the Z390P Prime and the blank screen on BIOS I managed to fix it, by enabling emulated NVRAM & refreshing the bios for windows (touch wood...) it's been good for a little while now, thought that I would come back and share.
Guide for emulated NVRAM:
Mount the EFI partition on your USB Boot drive and replace the EFI folder with this one. Boot from it and use it to install, if there is an existing OS X installation or a useable partition it should install, if not that is something you will have to work out. You can always back up and reinstall OS X and Windows
Hello, Leesureone.
Thank you for the answers. Finally, I was able to install Catalina from scratch only. More specifically, using Clover but not OC. OC was constantly getting stuck during the first load. Now I have clean installed MacOS. I have not installed Windows yet. There is another issue about Sleep mode on my MacOS now. It can not wake up after each time I try to use "Sleep" mode. The computer reboots and says to me there was an error.
I tried to fix this by the ways described in the first post of the current article.
There was one red line that highlighted the "proximitywake" param in "Hackintool" application.
Now
but the OS behavior hasn't changed.
Is there any other possible way to fix that issue?
Thank you!
Update
I noticed, the issue occurs when I try to switch on the monitor manually. Windows activated it automatically after any key on the keyboard is pressed. It looks like PC starts working (coolers and all lights turn on) except the monitor. It stucks in that middle state until the monitor power button is pressed. After that, rebooting with the following
BSD process name corresponding to current thread: WindowServer
Boot args: keepsyms=1
Mac OS version:
19G73
Kernel version:
Darwin Kernel Version 19.6.0: Sun Jul 5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64
Kernel UUID: 783946EA-6F11-3647-BF90-787AEA14B954
__HIB text base: 0xffffff8000100000
System model name: iMac18,1 (Mac-4B682C642B45593E)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hello, Leesureone.
Thank you for the answers. Finally, I was able to install Catalina from scratch only. More specifically, using Clover but not OC. OC was constantly getting stuck during the first load. Now I have clean installed MacOS. I have not installed Windows yet. There is another issue about Sleep mode on my MacOS now. It can not wake up after each time I try to use "Sleep" mode. The computer reboots and says to me there was an error.
I tried to fix this by the ways described in the first post of the current article.
There was one red line that highlighted the "proximitywake" param in "Hackintool" application.
Now
but the OS behavior hasn't changed.
Is there any other possible way to fix that issue?
Thank you!
Update
I noticed, the issue occurs when I try to switch on the monitor manually. Windows activated it automatically after any key on the keyboard is pressed. It looks like PC starts working (coolers and all lights turn on) except the monitor. It stucks in that middle state until the monitor power button is pressed. After that, rebooting with the following
BSD process name corresponding to current thread: WindowServer
Boot args: keepsyms=1
Mac OS version:
19G73
Kernel version:
Darwin Kernel Version 19.6.0: Sun Jul 5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64
Kernel UUID: 783946EA-6F11-3647-BF90-787AEA14B954
__HIB text base: 0xffffff8000100000
System model name: iMac18,1 (Mac-4B682C642B45593E)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Are you using ModMike's EFI folder? Sleep/Wake problems are typically tied to the USB Port Limit in OS X. You will need to evaluate if you have a port limit patch in place in your config.plist or an SSDT or kext in place that defines the correct ports to use. See here from page one on the Catalina 15.6 Update:
Please post help requests in the Catalina Desktop Support Forum section (not in this thread).
Pre Update Notes:
- This update may break some of your Catalina functions, like audio. Make sure you backup first.
Here's the step by step way to update: Backup your current installation using Carbon Copy Cloner or SuperDuper;
Update to the latest Clover
See the tonymacx86 Clover Builds (in Download menu) to update Clover.
If you are updating from 10.15.5, then you don't need to apply any new Port Limit Removal Patches. If you are updating from macOS before Catalina, apply any 10.15.0 Port Limit Removal Patches. Better yet, if you have created a SSDT-USB, then you're all set.
Important Update: June 2023 From Big Sur 11.3 on the built-in OpenCore XhciPortLimit quirk no-longer worked as described. This became a known "bug", though in reality it was Apple changing their internal code, making a simple "peek and poke" to keep it operating, a difficult task. However, with...
Are you using ModMike's EFI folder? Sleep/Wake problems are typically tied to the USB Port Limit in OS X. You will need to evaluate if you have a port limit patch in place in your config.plist or an SSDT or kext in place that defines the correct ports to use. See here from page one on the Catalina 15.6 Update:
Please post help requests in the Catalina Desktop Support Forum section (not in this thread).
Pre Update Notes:
- This update may break some of your Catalina functions, like audio. Make sure you backup first.
Here's the step by step way to update: Backup your current installation using Carbon Copy Cloner or SuperDuper;
Update to the latest Clover
See the tonymacx86 Clover Builds (in Download menu) to update Clover.
If you are updating from 10.15.5, then you don't need to apply any new Port Limit Removal Patches. If you are updating from macOS before Catalina, apply any 10.15.0 Port Limit Removal Patches. Better yet, if you have created a SSDT-USB, then you're all set.
Yes. I used the EFI folder from the current attachments. All I did additionally was update the kexts to the new versions via the way described in the current thread (in Clover). I Didn't install any additional extensions or something. Clover already is up to date. All kexts are up to date. I have MacOS 10.15.6 (19G73) installed from scratch. If I understand correctly, I have to install "Port Limit Removal" path, right?
Yes. I used the EFI folder from the current attachments. All I did additionally was update the kexts to the new versions via the way described in the current thread (in Clover). I Didn't install any additional extensions or something. Clover already is up to date. All kexts are up to date. I have MacOS 10.15.6 (19G73) installed from scratch. If I understand correctly, I have to install "Port Limit Removal" path, right?
Yes. I used the EFI folder from the current attachments. All I did additionally was update the kexts to the new versions via the way described in the current thread (in Clover). I Didn't install any additional extensions or something. Clover already is up to date. All kexts are up to date. I have MacOS 10.15.6 (19G73) installed from scratch. If I understand correctly, I have to install "Port Limit Removal" path, right?
With this guide and on 10.15.6 on Asus Strix Z390-F, when I resume from sleep the iGPU is not sending any signal to the display and this is what I have in the logs:
Code:
2020-07-27 10:37:29 +0200 Failure Failure during wake: HECI(),RP17(),RP21(IONVMeController),RP01(),LPCB(SMCSuperIO) : Some drivers failed to handle setPowerState
2020-07-27 11:02:25 +0200 Failure Failure during sleep: 0x3405F9000000012 : Informing clients about upcoming changes
With this guide and on 10.15.6 on Asus Strix Z390-F, when I resume from sleep the iGPU is not sending any signal to the display and this is what I have in the logs:
Code:
2020-07-27 10:37:29 +0200 Failure Failure during wake: HECI(),RP17(),RP21(IONVMeController),RP01(),LPCB(SMCSuperIO) : Some drivers failed to handle setPowerState
2020-07-27 11:02:25 +0200 Failure Failure during sleep: 0x3405F9000000012 : Informing clients about upcoming changes
Unfortunately, nope. I'm on vacation now. I didn't have a chance to investigate the issue more because my computer at home. But I agree with you about monitor signal. The system crashes when I try to switch on the monitor by pressing the power button. It didn't respond otherwise. It looks like all other components and devices start correctly (external connected USB devices, motherboard, e.t.c). I noticed all indicator lights started to flash except the monitor.
With this guide and on 10.15.6 on Asus Strix Z390-F, when I resume from sleep the iGPU is not sending any signal to the display and this is what I have in the logs:
Code:
2020-07-27 10:37:29 +0200 Failure Failure during wake: HECI(),RP17(),RP21(IONVMeController),RP01(),LPCB(SMCSuperIO) : Some drivers failed to handle setPowerState
2020-07-27 11:02:25 +0200 Failure Failure during sleep: 0x3405F9000000012 : Informing clients about upcoming changes
I don't see anything in that failure to wake that is related to display or graphics. I think its related to incorrect USB configuration and your system will not power back up correctly. Its pretty easy now to create your own SSDT or USBPorts.kext using Hackintool. I could send what I use for the "e" and "i" boards but not sure it would work, take the time to follow the guid below and I'd bet your issue goes away.
Important Update: June 2023 From Big Sur 11.3 on the built-in OpenCore XhciPortLimit quirk no-longer worked as described. This became a known "bug", though in reality it was Apple changing their internal code, making a simple "peek and poke" to keep it operating, a difficult task. However, with...
I don't see anything in that failure to wake that is related to display or graphics. I think its related to incorrect USB configuration and your system will not power back up correctly. Its pretty easy now to create your own SSDT or USBPorts.kext using Hackintool. I could send what I use for the "e" and "i" boards but not sure it would work, take the time to follow the guid below and I'd bet your issue goes away.
Important Update: June 2023 From Big Sur 11.3 on the built-in OpenCore XhciPortLimit quirk no-longer worked as described. This became a known "bug", though in reality it was Apple changing their internal code, making a simple "peek and poke" to keep it operating, a difficult task. However, with...
If you could you share the one for the "e" variant it would be awesome, thanks in advance. Maybe the entire ACPI folder would be even more useful. I have the "f" which is the same minus the BT/WiFi module so I imagine it should work just the same.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Backup your current installation using Carbon Copy Cloner or SuperDuper;
