Solved Installation reboot issue with Ventura and Opencore 0.8.9

[Byteme9999]

I'm having an issue with trying to install Ventura with OpenCore 0.8.9 on a clean 2nd non NVme SSD. This SSD is completely clean, all I have done is added a GUID Partition table and created a OSX Partition (Using Disk Utility) of 250GB.

The issue I'm having is the installation gets to about 12 Minutes left and then reboots, however when I select Mac Installer from the OpenCore menu it just reboots and the Mac Installer option is gone. If I reboot again OpenCore only has the option to start all over again. I have tried this about 3 times, but can never get past this point.

Asrock B450m Pro (Above 4G on, Resizable Bar on, CSM off)
Ryzen 3600
Radeon RX 6600 8GB
32 GB 3000 DDR4
1 TB NVme SDD (WIndows 10 only)
1 TB SSD (250GB Ventura, 250GB MXLinux, 500GB shared space)

 

[Byteme9999]

I was able to get MacOS Ventura installed and running. However, the installation process did not create a bootable EFI Partition on the drive. Is this normal? Should I have created one myself prior to doing the install? Is it possible to create one after the fact?

 

[Byteme9999]

Actually, I do have a 200Mb EFI partition, just no files related to MacOS are there

 

[Edhawk]

1. The installation of macOS on a Hack will not create a Bootable drive.
   1. You need to format the drive before macOS is installed using Disk Utility, which is available as part of the macOS installation wizard.
   2. If you want to use more than one OS/data store on the drive you need to create these additional partitions when you format the drive.
   3. So in your case you would want to initially format the drive as MacOS Extended, i.e. HFS+ with 3 partitions, sized to suit your future requirements.
2. Once the 3 x partitions and the drives hidden EFI Partition have been created. you can then change the formatting of the individual partitions.
   1. So the first 250GB partition would be Erased and a new APFS Container created in its place. This would be for macOS.
   2. The second 250GB partition would be left as is, until you undertake the Linux installation.
      1. This partition would be erased/split/formatted to suit the version of Linux you want to run.
   3. The third partition can be erased and formatted as ExFat or any other format you choose in Linux or macOS.

To make the drive bootable you need to mount the Hidden EFI partition and copy the OpenCore EFI folder from your USB installation drive to the main drives EFI Partition.

 

[Byteme9999]

1. The installation of macOS on a Hack will not create a Bootable drive.
   1. You need to format the drive before macOS is installed using Disk Utility, which is available as part of the macOS installation wizard.
   2. If you want to use more than one OS/data store on the drive you need to create these additional partitions when you format the drive.
   3. So in your case you would want to initially format the drive as MacOS Extended, i.e. HFS+ with 3 partitions, sized to suit your future requirements.
2. Once the 3 x partitions and the drives hidden EFI Partition have been created. you can then change the formatting of the individual partitions.
   1. So the first 250GB partition would be Erased and a new APFS Container created in its place. This would be for macOS.
   2. The second 250GB partition would be left as is, until you undertake the Linux installation.
      1. This partition would be erased/split/formatted to suit the version of Linux you want to run.
   3. The third partition can be erased and formatted as ExFat or any other format you choose in Linux or macOS.

To make the drive bootable you need to mount the Hidden EFI partition and copy the OpenCore EFI folder from your USB installation drive to the main drives EFI Partition.

Everything is working expect the part about booting without the USB. I have copied the EFI folder from my USB to the EFI Partition but it doesn't show up in the boot list when I boot and press F11 (what loads the EFI Boot loaders on my B450 motherboard). I see Windows, Linux and USB (when it's in) but not OpenCore.

Not sure it's relavent, but I can mount the EFI partition (200mb ESP, Boot flags) in Linux but I can seem to in MacOS Ventura. Not sure why. Trying to see if I can add the OpenCore bootloader to Grub2.

 

[Edhawk]

It should show in the boot menu/bios as 'UEFI..... ' followed by the manufacturers name for the drive.

It won't show as OpenCore in the Bios or Boot Menu, unless you set the Misc > Boot > LauncherOption as Full in your config.plist, as shown below.
Misc > Boot > LauncherOption = Full

 

[Byteme9999]

I think the issue might be that I created my Installation USB on Windows using Rufus and that it doesn't create the EFI/GUID Partition Table on the USB drive. So, I did copy over the EFI folder from the USB it's not the hidden one (because there isn't one).

That being said, I can boot into Ventura (via USB) and am trying to recreate the USB drive using the MacOS instructions so I can get the hidden EFI folder. However, my Ventura install keeps rebooting after about 10-15 minutes (not enough time to download the installer).

Here is the latest kernel panic:

panic(cpu 0 caller 0xffffff8012d485f3): Kernel trap at 0xffffff801313ce34, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000040000000010, CR3: 0x0000000021288000, CR4: 0x00000000003406e0
RAX: 0x0000000000000000, RBX: 0x0000040000000000, RCX: 0x0000000000000002, RDX: 0x0000000000000188
RSP: 0xffffffaccbdfbdb0, RBP: 0xffffffaccbdfbdb0, RSI: 0x0000040000000000, RDI: 0x0000040000000000
R8: 0x0000000000000004, R9: 0x0000000000000000, R10: 0x00000000000000ff, R11: 0x00000000000007fc
R12: 0x0000000000000001, R13: 0xffffffffc059c600, R14: 0xffffffffc059c600, R15: 0xffffff9028a0f500
RFL: 0x0000000000010206, RIP: 0xffffff801313ce34, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000040000000010, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 1

Panicked task 0xffffff99c0df5208: 220 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff94f4f3e598, Frame : Return Address
0xffffffaccbdfb790 : 0xffffff8012beb38d
0xffffffaccbdfb7e0 : 0xffffff8012d58ed6
0xffffffaccbdfb820 : 0xffffff8012d48120
0xffffffaccbdfb870 : 0xffffff8012b85951
0xffffffaccbdfb890 : 0xffffff8012beb66d
0xffffffaccbdfb980 : 0xffffff8012bead19
0xffffffaccbdfb9e0 : 0xffffff80133e072b
0xffffffaccbdfbad0 : 0xffffff8012d485f3
0xffffffaccbdfbc50 : 0xffffff8012d482e2
0xffffffaccbdfbca0 : 0xffffff8012b85951
0xffffffaccbdfbcc0 : 0xffffff801313ce34
0xffffffaccbdfbdb0 : 0xffffff8014af204a
0xffffffaccbdfbe10 : 0xffffff8014c8efb9
0xffffffaccbdfbe80 : 0xffffff8014a331e3
0xffffffaccbdfbed0 : 0xffffff80133144b4
0xffffffaccbdfbf20 : 0xffffff8013312dae
0xffffffaccbdfbf60 : 0xffffff80133123e7
0xffffffaccbdfbfa0 : 0xffffff8012b8519e
Kernel Extensions in backtrace:
com.apple.driver.AirPort.BrcmNIC(1400.1.1)[168E8B42-4E91-366A-AD27-78AF8BE04325]@0xffffff80149fa000->0xffffff8014f53fff
dependency: com.apple.driver.corecapture(1.0.4)[1EFC00FC-8337-39AF-B061-EDA1CB53C6E7]@0xffffff8015e4a000->0xffffff8015e6cfff
dependency: com.apple.driver.mDNSOffloadUserClient(1.0.1b8)[C3FDAE90-94DE-3A8C-97AF-DA3D79487FC3]@0xffffff8015652000->0xffffff8015656fff
dependency: com.apple.iokit.IO80211FamilyLegacy(1200.12.2b1)[8CB6AB86-0DC8-324C-A9F7-B46C452522DD]@0xffffff8014898000->0xffffff80149defff
dependency: com.apple.iokit.IONetworkingFamily(3.4)[ACD4449A-4F90-31DB-82AD-2F2B83D8F6E3]@0xffffff80153f8000->0xffffff801540efff
dependency: com.apple.iokit.IOPCIFamily(2.9)[802B9CA4-B851-396E-8DA4-B30E751EC48F]@0xffffff8015659000->0xffffff8015688fff
dependency: com.apple.iokit.IOSkywalkFamily(1.0)[337AFA35-6288-3EA9-BC6E-AA8E075EECF6]@0xffffff8015742000->0xffffff801576ffff

Process name corresponding to current thread (0xffffff94f4f3e598): kernel_task
Boot args: alcid=1 agdpmod=pikera

Mac OS version:
22D68

Kernel version:
Darwin Kernel Version 22.3.0: Mon Jan 30 20:42:11 PST 2023; root:xnu-8792.81.3~2/RELEASE_X86_64
Kernel UUID: 10E5D254-4A37-3A2A-B560-E6956A093ADE
roots installed: 0
KernelCache slide: 0x0000000012800000
KernelCache base: 0xffffff8012a00000
Kernel slide: 0x00000000128dc000
Kernel text base: 0xffffff8012adc000
__HIB text base: 0xffffff8012900000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 392796288100
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000005b747bb716
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x000000191a8aeaf0 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff84f2a4d000 - 0xffffffa4f2a4d000
. PGZ : 0xffffff84f2a4d000 - 0xffffff84f6a4e000
. VM : 0xffffff84f6a4e000 - 0xffffff89c2d81000
. RO : 0xffffff89c2d81000 - 0xffffff8b5c3e7000
. GEN0 : 0xffffff8b5c3e7000 - 0xffffff902871a000
. GEN1 : 0xffffff902871a000 - 0xffffff94f4a4d000
. GEN2 : 0xffffff94f4a4d000 - 0xffffff99c0d80000
. GEN3 : 0xffffff99c0d80000 - 0xffffff9e8d0b3000
. DATA : 0xffffff9e8d0b3000 - 0xffffffa4f2a4d000
Metadata: 0xffffff803fdb7000 - 0xffffff805fdb7000
Bitmaps : 0xffffff805fdb7000 - 0xffffff806bdb7000

 

[Edhawk]

That kernel panic image shows an issue with the Airport.BCM NIC kext. As far as I can see in the EFI you provided in post #1 you don't have that kext installed in your OC setup.

Have you added it recently?
Your motherboard doesn't have a built-in Intel WIFI/BT card.
Have you added a natively supported Broadcom BCM94360.... WiFi/BT card to the top PCIe x1 slot on your motherboard?

 

[Byteme9999]

I have ethernet (Realtek RTL8111H) on motherboard and a Fenvi FV-HB1200 (BCM94360CS2) PCie wifi card. Nothing else. I was able to get it stable, I reset NVRAM and turned off all ECO Power Mode stuff.
I still cannot understand why I can't get my Motherboards UEFI Boot menu to see the OpenCore bootloader. I copied the EFI Folder (from my Bootable MacOS USB) over to it but it just doesn't see it. It sees my Linux Bootloader (on same drive and has it's own folder in EFI Partition), but not OpenCore. Strange.

 

[Lorys89]

The problem is opencore 0.8.9, try with opencore 0.8.8 or 0.9.0 dev and see that solve

 

[Byteme9999]

I finally got it working. It was all in how I initially setup the drive. From the MacOS installer I first had to erase the drive completely with Format: MacOS Extended Journal and Scheme: Guid Partition Table. Doing this from Windows or Linux didn’t work. Then I installed MacOS Ventura with the configuration I posted earlier. Once it was completely installed and setup, I used MountEFI to mount the EFI created when I erased the disk. I copied over the EFT folder from my USB and it worked. Once booted back into MacOS, I used Disk Utility to adjust the MacOS partition (made it smaller to add room for Linux) and added a new one for MX Linux. Then I booted my MXLinux USB and using Gparted adjusted the new partition to meet MXLinux needs (it needs 100GB for Root and the rest for home). Installed MX Linux and now I can boot into both. Plus my NVme drive still has Windows 10 on it and it still works fine.

Thanks for the help!!!