Catalina Install Problem

[scottkendall]

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.

I do not use either of the beast apps but Multibest is post install application so I am not sure why it would be affecting your install. If you use Unibeast it should make you a nice installer, once done you should use Multibeast to install Kexts on your USB EFI partition after you get everything sorted you should transplant your EFI from the USB over to your system.

 

[Tango2]

If you use Unibeast it should make you a nice installer, once done you should use Multibeast to install Kexts on your USB EFI partition after you get everything sorted you should transplant your EFI from the USB over to your system.

UniBeast did exactly that. Once done, I was attempting to install kexts onto my system EFI partition. Nowhere in the instructions here did it say to put them on the USB EFI partition and transplant them over (that I saw at least). Based on my experience, that may have worked because it seemed that MultiBeast would run successfully everywhere except my system partition until I made it read-write.

What is the best method to experiment with kexts? I think I'm missing at least one as my audio device is not recognized.

 

[scottkendall]

UniBeast did exactly that. Once done, I was attempting to install kexts onto my system EFI partition. Nowhere in the instructions here did it say to put them on the USB EFI partition and transplant them over (that I saw at least). Based on my experience, that may have worked because it seemed that MultiBeast would run successfully everywhere except my system partition until I made it read-write.

What is the best method to experiment with kexts? I think I'm missing at least one as my audio device is not recognized.

I put them in my EFI folder clover/kext/other on my boot drive or if I am trying new stuff on a USB clover/kext/other. With the way that Apple is locking the OS out it is much easier to try new/update kexts in that manner. In addition you do not have to do anything other than copy and paste them. Either way is fine and some wold recommend you put them in L/E I just find that to be a hassle.

 

[Tango2]

I appreciate all the help you've provided so far. Can you point me in the right direction as to the proper order to troubleshoot these hardware/driver issues as well as any other performance tuning?

The first thing I was attacking was my ethernet driver. I'm loosing internet connectivity after the computer goes to sleep. Rebooting fixes the problem. The AppleIntelE1000e.kext is what is getting reported under the Ethernet Controller in the system report. Previously, I had the IntelMausiE1000e.kext in my EFI Folder on my last working install (making the assumption that was the kext being used, but not confirmed). I tried deleting the AppleIntelE1000e.kext from the OS L/E folder and replacing with the IntelMausiE1000e.kext. Ethernet worked, but system report did not show a kext loaded, and I still had the same problem after sleeping. I went back to the AppleIntelE1000e.kext, but maybe I'm taking things out of order. I still need to better understand all of the options in the clover config.plist file as well as the DSDT stuff.

Any pointers on at least a roadmap of where to start?

 

[scottkendall]

I appreciate all the help you've provided so far. Can you point me in the right direction as to the proper order to troubleshoot these hardware/driver issues as well as any other performance tuning?

The first thing I was attacking was my ethernet driver. I'm loosing internet connectivity after the computer goes to sleep. Rebooting fixes the problem. The AppleIntelE1000e.kext is what is getting reported under the Ethernet Controller in the system report. Previously, I had the IntelMausiE1000e.kext in my EFI Folder on my last working install (making the assumption that was the kext being used, but not confirmed). I tried deleting the AppleIntelE1000e.kext from the OS L/E folder and replacing with the IntelMausiE1000e.kext. Ethernet worked, but system report did not show a kext loaded, and I still had the same problem after sleeping. I went back to the AppleIntelE1000e.kext, but maybe I'm taking things out of order. I still need to better understand all of the options in the clover config.plist file as well as the DSDT stuff.

Any pointers on at least a roadmap of where to start?

Since you have an NUC:

[Guide] Intel Broadwell NUC5 using Clover UEFI (NUC5i5MHYE, NUC5i3MYHE, etc)

Could you please help me, I have the same problem. With hdmi i only get 30 hz. So I want to use displayport to get 60 hz. The first thing i tried was to change the framebuffer-con2-enable value from 1 to 0 but the signal was lost during boot. The second i tried was to change all three values...

www.tonymacx86.com