Contribute
Register

Catalina Install Problem

Joined
Dec 4, 2015
Messages
37
Motherboard
Intel NUC5i5RYH
CPU
i5
Graphics
Intel
Hey guys. Trying to do a clean install of the latest Catalina build on my NUC5i5RYH. I'm currently running 10.15.1 and can't update to 10.15.2 for some reason. The update never takes. Because of that, and a couple other strange issues I've been having lately, I wanted to do a clean install.

I'm following the latest Catalina install guide, have the bootable install media with Catalina on it. When attempting to boot from it, I get a few seconds in and get the "prohibited sign".

I don't have a great understanding of what's under the hood on the hackintosh to troubleshoot the problem enough.

What I've tried:
I used clover configurator to compare config.plist of my current EFI partition on my current booting drive to the new USB drive. I found some differences, and made the necessary updates. After saving the file and rebooting, I get to the same point in which I get the prohibited stop sign.

I'm thinking this may be a kext problem or something, but I'm not 100% sure how to address it.

Thanks!
 
Joined
Dec 4, 2015
Messages
37
Motherboard
Intel NUC5i5RYH
CPU
i5
Graphics
Intel
I'm not sure if this is helpful, but I just came across this debug log on my USB boot EFI partition. These are the last several lines prior to the end of the file:


81:530 0:029 Beginning FSInjection
81:575 0:045 Use origin smbios table type 1 guid.
81:607 0:032 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
81:636 0:029 ->Extra kext: EFI\CLOVER\kexts\Other\WhateverGreen.kext (v.1.3.5)
81:696 0:059 ->Extra kext: EFI\CLOVER\kexts\Other\VirtualSMC.kext (v.1.0.9)
81:726 0:030 ->Extra kext: EFI\CLOVER\kexts\Other\RealtekRTL8111.kext (v.2.2.2)
81:757 0:031 Skipping kext injection by OSBundleRequired : EFI\CLOVER\kexts\Other\RealtekRTL8111.kext
81:799 0:041 ->Extra kext: EFI\CLOVER\kexts\Other\Lilu.kext (v.1.4.0)
81:834 0:035 ->Extra kext: EFI\CLOVER\kexts\Other\IntelMausiEthernet.kext (v.2.5.0)
81:863 0:029 Skipping kext injection by OSBundleRequired : EFI\CLOVER\kexts\Other\IntelMausiEthernet.kext
81:892 0:029 ->Extra kext: EFI\CLOVER\kexts\Other\AtherosE2200Ethernet.kext (v.2.3.0)
81:922 0:029 Skipping kext injection by OSBundleRequired : EFI\CLOVER\kexts\Other\AtherosE2200Ethernet.kext
81:953 0:030 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Off
81:995 0:042 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10
82:024 0:028 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10_install
82:055 0:030 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.15
82:084 0:029 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.15_install
82:113 0:028 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.15.2
82:142 0:029 Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.15.2_install
82:195 0:052 Custom boot screen not used because entry has unset use graphics
82:225 0:030 Closing log



I'll be glad to post the entire file if that's helpful.
 
Joined
Jul 13, 2016
Messages
1,444
Motherboard
ASUS ROG STRIX Z370-F
CPU
I5-8600K
Graphics
RX580
Mac
Mac mini, Mac Pro
Mobile Phone
iOS
I'm thinking this may be a kext problem or something, but I'm not 100% sure how to address it.
If you think it is a kext problem get rid of all your kexts and leave only Lilu and VirtualSMC. In addition add -v to your boot arguments so that you can see what is actually causing the reboots.
 
Joined
Dec 4, 2015
Messages
37
Motherboard
Intel NUC5i5RYH
CPU
i5
Graphics
Intel
When you say get rid of all the kexts except those two, do you mean delete them or just disable them in the boot options?
 
Joined
Dec 4, 2015
Messages
37
Motherboard
Intel NUC5i5RYH
CPU
i5
Graphics
Intel
Also, the main reason I think it could be a kext problem is because the hardware boots fine with my existing install, but that may be a bad assumption
 
Joined
Dec 4, 2015
Messages
37
Motherboard
Intel NUC5i5RYH
CPU
i5
Graphics
Intel
Tried disabling all kexts with the exception of the two you recommended in the boot options. Had the same result. The verbose logs show:

AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for HS07 of 500 mWWakePower and 0 mWSleepPower

it is repeated every 2 seconds from before the prohibited sign and continues indefinitely after the prohibited sign.
 
Joined
Jul 13, 2016
Messages
1,444
Motherboard
ASUS ROG STRIX Z370-F
CPU
I5-8600K
Graphics
RX580
Mac
Mac mini, Mac Pro
Mobile Phone
iOS
Tried disabling all kexts with the exception of the two you recommended in the boot options. Had the same result. The verbose logs show:

AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for HS07 of 500 mWWakePower and 0 mWSleepPower

it is repeated every 2 seconds from before the prohibited sign and continues indefinitely after the prohibited sign.
Most people take a picture of their screen where the boot stops on the Verbose in addition there would be no prohibited sign if you used verbose boot and I meant remove them from the folder.
 
Joined
Dec 4, 2015
Messages
37
Motherboard
Intel NUC5i5RYH
CPU
i5
Graphics
Intel
Ok, progress. I kept experimenting to the point where it wouldn't even give much of a verbose output, so I rebuilt the USB drive using UniBeast. After doing so, it made it through the install with no problems.

I'm stuck again though... now, I can't get MultiBeast to save to my new Catalina SSD drive. It continually fails with the following log entries:


01/17/20 07:05:00 - Starting MultiBeast 11.3.0-4
01/17/20 07:05:47 - Installing 'Bootloaders > Clover UEFI Boot Mode'
01/17/20 07:05:59 - Install of 'Clover_v2.4k_r4934-UEFI.pkg' failed.
'installer: Package name is Clover v2.4k r4934 tonymacx86 UEFI
installer: Installing at base path /
installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. The package is attempting to install content to the system volume.)
'. Exiting.


I tried to successfully build the MultiBeast config to my other installed SSD drive, and it completes successfully. I am currently booting from the USB drive using the newly installed Catalina drive (if that makes sense). It seems that the drive is "locked" because Catalina is currently running from it, and that's why I can't install the boot loader, but maybe I'm wrong. Any ideas?
 
Joined
Dec 4, 2015
Messages
37
Motherboard
Intel NUC5i5RYH
CPU
i5
Graphics
Intel
I ended up getting a *mostly* working bootable Catalina on this hardware. I ended up starting the whole process from scratch, ended up in the same position where MultiBeast failed.

I read through the troubleshooting information and found a link that explained that in Catalina, the security defaults make the root of the system drive read only. After running "sudo mount -uw /" from a terminal prompt and running MultiBeast again, everything worked perfectly.

I posted a suggestion to add that in the steps in the main Catalina install guide, as from what I can tell that is required on all Catalina installs until the new version of MultiBeast is released, which I assume will perform that task behind the scenes.

Now I'm trying to get a couple hardware items working properly, the first being audio. No audio device is found. Tried a couple kexts, but I'm not 100% which one or if I'm doing it right. Slow going, but I'm learning.

What's more, hopefully this post will help someone else that is new at this.
 
Top