ASUS Z390-A + 9700k + Vega 64 0.6.2 11.0.1

[fgxr8]

using the efi you have provided i cna boot initially into the installer, select my ssd as the install location
however after it copies all. the files it restarts upon restarting when i choose to go into the installer to complete the process i get the kernel panic screen

can load catalina fine.

I have the same issue with OC i made following the guide and clover, can always boot into the intial part to copy the files, upon reboot im never able to get into the second phase of the setup


*edit the reason im trying this efi is that the z390-a and my strix 390f are virtually identical boards with same usb layout.

I have tried multiple people's efi and i get the same error, able to boot to setup initially then bootloop/ kernel panic after the initial phase. my understanding with hackintosh so far is that if you are able to boot into the installer then you are able to to boot into the hackintosh, as any errors present in the config would prevent you from reaching the installer itself.

 

[scottkendall]

When you boot the installer are you using the EFI on the USB? When you boot the Hard drive from the picker are you still booting from the EFI on the USB?

You need to make sure that you are using the same EFI each time, if you are booting from your Catalina EFI after the install copies files then that is likely your problem.

 

[fgxr8]

Yeh ofcourse, i press f8 to boot from usb efi everytime
Its a weird issue, looking at few other forums it seems like its something to do with slide value and some memory thing. However im not that advanced to figure it out.

 

[scottkendall]

Yeh ofcourse, i press f8 to boot from usb efi everytime
Its a weird issue, looking at few other forums it seems like its something to do with slide value and some memory thing. However im not that advanced to figure it out.

I do not really know much about fixing slide values but other things you can do that might help with this are update your bios? Enable 4g Decoding, disable CSM, Disable Parallel/Serial Ports, Disable IGPU until the install is complete, Turn your LED lighting off. Outside of the enabling 4G decoding that allows larger memory maps the rest of the items will help shrink your memory map hopefully allowing you to complete your install. I had a z170 MSI board that would not boot if I had a PCI-E wifi card installed.

 

[fgxr8]

Ok I made a new OC efi (boots Catalina fine)

I then installed Big sur to an external hard drive (lacie 2gb with my MacBook Pro ) via usb3 ,
and then using the new OC efi I plugged the external drive into my desktop I'm able to boot into it!

but using the same efi and trying to install big sur on my internal name gives the error above.


*so from troubleshooting perspective:
-my efi is correct its capable of booting both Catalina and Big sur
-my hardware is ok, miso ok as Catalina runs fine, got big sur booted fine via an external hdd

so what the hell is going on

 

[Douirc]

You had a patch for RTC in both Kernel and in ACPI I deleted them both and then added back the one in ACPI that was built into the OC configurator.

I changed Misc--> Security ---> Securebootmodel---> Disable <--- this is likely your issue.

I also copied my kexts to your folder just to make there was nothing wrong with the ones you had.

Try booting with the Attached EFI from a USB after you get it booting then you can fiddle with the differences and what you do not like about what I did if anything.

bingo bango! working like a champ, thank you!

My SMCProcessor and SMCSuperIO kexts were in the VirtualSMC Plugins directory. Better to put it in kext root folder and update the config.plist or leave it inside VirtualSMC? Or does it not really matter?

For some reason the RTC patch in your OC Configurator still causes my Z390-A EUFI to boot in SAFE mode. Should I use my patch but put it in the ACPI or leave it in Kernel?

OC Configurator:
<dict>
<key>Comment</key>
<string>Fix RTC _STA bug</string>
<key>Count</key>
<integer>0</integer>
<key>Enabled</key>
<true/>
<key>Find</key>
<data>oAqTU1RBUwE=</data>
<key>Limit</key>
<integer>0</integer>
<key>Mask</key>
<data></data>
<key>OemTableId</key>
<data></data>
<key>Replace</key>
<data>oAqRCv8L//8=</data>
<key>ReplaceMask</key>
<data></data>
<key>Skip</key>
<integer>0</integer>
<key>TableLength</key>
<integer>0</integer>
<key>TableSignature</key>
<data>RFNEVA==</data>
</dict>

My RTC Patch:
<dict>
<key>Base</key>
<string></string>
<key>Comment</key>
<string>AppleRTC patch</string>
<key>Count</key>
<integer>1</integer>
<key>Enabled</key>
<true/>
<key>Find</key>
<data>dTMPtw==</data>
<key>Identifier</key>
<string>com.apple.driver.AppleRTC</string>
<key>Limit</key>
<integer>0</integer>
<key>Mask</key>
<data></data>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string>18.5.0</string>
<key>Replace</key>
<data>6zMPtw==</data>
<key>ReplaceMask</key>
<data></data>
<key>Skip</key>
<integer>0</integer>
</dict>

 

[scottkendall]

Ok I made a new OC efi (boots Catalina fine)

I then installed Big sur to an external hard drive (lacie 2gb with my MacBook Pro ) via usb3 ,
and then using the new OC efi I plugged the external drive into my desktop I'm able to boot into it!

but using the same efi and trying to install big sur on my internal name gives the error above.


*so from troubleshooting perspective:
-my efi is correct its capable of booting both Catalina and Big sur
-my hardware is ok, miso ok as Catalina runs fine, got big sur booted fine via an external hdd

so what the hell is going on

The fact it boots Catalina has nothing to do with Big Sur they are totally different animals. So From a troubleshooting perspective, your EFI is not capable of booting Big Sur since it is not booting Big Sur. If Big Sur is booting from an External drive just fine but does not boot from the internal then it sounds like a User error or some kind. Maybe you should look around the forums for someone having a similar issue as you because your error is not the same as the OP's.

Maybe you should go grab pastrychiefs OC 6.2 directly from his z370 build and try it out.

 

[scottkendall]

bingo bango! working like a champ, thank you!

My SMCProcessor and SMCSuperIO kexts were in the VirtualSMC Plugins directory. Better to put it in kext root folder and update the config.plist or leave it inside VirtualSMC? Or does it not really matter?

For some reason the RTC patch in your OC Configurator still causes my Z390-A EUFI to boot in SAFE mode. Should I use my patch but put it in the ACPI or leave it in Kernel?

I guess they are not the same patch I just saw RTC and figured they were doing the same thing and possibly causing the issue. So I removed the one but now that I look at it they are clearly different doing different things so I would keep it where you had it. As for the SMC plugins I have them in the root I also moved them because that is where I have them and it works. As for the plugins, you can try different things, but as for the RTC patch, I would put yours back where it came from in the Kernel.

 

[Douirc]

I guess they are not the same patch I just saw RTC and figured they were doing the same thing and possibly causing the issue. So I removed the one but now that I look at it they are clearly different doing different things so I would keep it where you had it. As for the SMC plugins I have them in the root I also moved them because that is where I have them and it works. As for the plugins, you can try different things, but as for the RTC patch, I would put yours back where it came from in the Kernel.

I put the kexts in root...figured it's easier to remember to update with future releases. And for the RTC, I left it in Kernel.

On another note, I noticed NVRAM isn't remembering my last choice from the boot menu. It keeps reverting to the first choice in the list and I have manually select macOS. Know how to fix that?

 

[scottkendall]

I put the kexts in root...figured it's easier to remember to update with future releases. And for the RTC, I left it in Kernel.

On another note, I noticed NVRAM isn't remembering my last choice from the boot menu. It keeps reverting to the first choice in the list and I have manually select macOS. Know how to fix that?

are you selecting your startup drive in System preferences?