Jump to content

SecureBootModel during install and post install: should it stay the same? I want updates to work


5 posts in this topic

Recommended Posts

Hi,

 

I have Sonoma 14.5 set up with Asus Z790 ProArt, 14700k, 6950xt, sn850x, as well as samsung 990 pro for windows (I dual boot). I am trying to understand the differences between SecureBootModel Default and Disabled.

 

I had heck of a time installing with Default, finally got things working with Disabled. But I understand we need Default to have updates work. 

 

So are we supposed to have an install and post install config?  I also noticed that during install I would get "you need firmware update to install to this volume" which I understood had to do with CustomSMBIOSGuid quirk.

 

I can't figure out how SecureBootModel is related to other quirks.  If I got things working fine with Disabled, then want to switch to Default, what other quirks do I need to be concerned about?

 

By the way my SMBIOS is iMacPro1,1.  As I understand this choice also impacts some of my decisions.

 

I attached current config with SecureBootModel Default, and previous config with Disabled.  I also modified some other settings such as CustomSMBIOSGuid AppleRTC, Firmware Volume, Third party drives.  The settings for these in previous version seemed to be how I needed for successful install. I changed them based on my understanding of security related settings (my understanding is not high!).

 

With that said, can someone do sanity check? Ideally i would prefer config to stay same. But trying to figure out what is actually needed for 1,1 to install successfully, get updates, and have minimal trouble with CMOS reset and BIOS updates.

 

Ideas?

 

thanks!

 

 

current config.plist config backup.plist

Link to comment
Share on other sites

  • 4 weeks later...

Your information is obsolete since Sonoma. SecureBootModel must be Disabled. And always was. It was an acidanthera trick for Monterey having no relation to any "secure boot".

Link to comment
Share on other sites

@bhuether You're going to learn very quickly that there are as many opinions as there are contributors.  Google is your friend and a good tool to use before posting questions.

Link to comment
Share on other sites

I have never had a successful boot with it set to Default. Would need to do serial port capture to better see the kernel verbose. From what I can see in video capture is boot gets pretty far, to XHCI controller initialization, then various setpowerstate calls, then reboot. This repeats over and over.

 

But for now I am not worried, everything works fine with SecureBootModel Disabled. Just odd that on several sites people are told to set to Default after Sonoma install.

Link to comment
Share on other sites

 Share

×
×
  • Create New...