Ventura on Supermicro X12SAP-TF, Xeon W-3323, RX6600

[Pinky80]

Greetings to All,

 

First off, I want to thank Balamut and Oldycat for their efforts at getting MacOS to run on this seemingly difficult PC build. THANK YOU!

 

I've built many PC's before, and have run MacOS on Dell laptops. And I'm currently running Ventura on an MSI-Z690 AlderLake. So I'm not a fresh noob at this, but my patience is wearing thin.

 

Moderators, can my post be added to the Ventura Install forum, and perhaps referenced to Balamut's and Oldycat's posts? It seems we're building a little Supermicro Workstation club.

 

I have run into some challenges that seem unique to my recipe and I would like to ask other folks for help.

 

Recipe:

Supermircro X12SPA-TF Motherboard - BIOS 1.4A

Xeon W-3323 CPU with MT turned on

MSI nVidia 3070ti (in slot disabled by DeviceProperties boolean in config file. Keeping this for Windows 10) Dual boot already non-issue.

XFS Radeon RX6600 GPU - This is for MacOS

64 gb ECC 3200 DDR4 RAM (Newegg special - no manufacturer name, tested 100% good with MemTest)

Sabrent Rocket Plus 4.0 NVME (Windows 10)

Sabrent Rocket 3.0 NVME (where I want MacOS installed)

  Both NVME drives are installed on the board's built in NVME Slots, which are bifurcated from the first (furthest away from CPU) PCI-E 16x slot.

 

 

Questions:

1). How do I correctly decode the Windows Device Location path to the MacOS hex code:

I have PCIROOT(50)#PCI(0200)#PCI(0000) from Windows,

My best guess for hex is: PCIROOT(0x50)/PCI(0x2,0x0)/PCI(0x0,0x0). I thinking I've got this wrong, which may be why I cannot get past the IOPCI error. I'll run this again and see if I can get a picture of the error I'm getting.

 

This Hex coding is eluding me at the moment. On my Alderlake setup, my Windows PCIROOT was a Zero, so it was easy to surmise Hex (0x0) for my first PCIROOT statement. Supermicro went a little unconventional on me.

 

2). My CPU is the Xeon W-3323, which has less cores than the W-3375 the big guys are running. And I've noticed in the posted config files that the Processor Type is 3842. Does this matter in regards to my setup versus the W-3375 recipes?

 

I have started my EFI raw from Opencore, using version 9.2. I have only modified my EFI and config to emulate Oldycat's posted EFI as closely as possible, with exceptions for my nVidia card, no WiFI (that comes later), and of course my Serial, etc.

 

I've hit a brick wall and am stuck.

 

Any suggestions or help will be welcomed. Attached are is my Config and EFI folder. Let me know what I got wrong there first. I'm going to post status updates and picts of errors soon. I just wanted to some attention here, LOL.

 

 

 

EFI.rar

[etorix]

Welcome here!

It is unfortunate you have to open a third thread for the same (uncommon) board, but you'll be allowed out of the sandbox once you have enough posts.

 

Re: 1) Pay attention to capitalisation: PciRoot(0x50)/Pci(0x02,0x0)Pci(0x0,0x0).

 

Re: 2) The CPU model should be irrelevant.

[etorix]

Another piece of advice: Simplify your EFI!

FakeSMC and VirtualSMC, two kexts for TSC sync, four for USB, kexts for i210 (should be built-in) and SmallTree, Realtek (the OS should have no use for the BMC NIC)… This makes it difficult to figure out what's going on, and is prone to errors and conflicts.

[Balamut]

15 hours ago, etorix said:

Another piece of advice: Simplify your EFI!

FakeSMC and VirtualSMC, two kexts for TSC sync, four for USB, kexts for i210 (should be built-in) and SmallTree, Realtek (the OS should have no use for the BMC NIC)… This makes it difficult to figure out what's going on, and is prone to errors and conflicts.

What he said.

I'd also suggest getting yourself a COM port to USB adapter and debug it. It's much easier to go over the text log file than try to develop Superman vision and catch the screen.

[Pinky80]

Well, I give up. My last attempt, I started over with a fresh config file, changes applicable to my dual GPU setup and dual NVME drives, and cleaned it up to make it simpler, meaning I took out anything Boolean set to False instead of enabled, and gave her a go. First boot, would not go past the ExitBS screen. I gave it an hour, knowing that there is a lag after that flag. I saw this on my Skylake/Ventura build. And no success. Rebooted only to get the same thing. Rebooted again and now no options for the OS showed up, just the EFI tools listed in the config file. Arg! I have been at this for weeks. So I’m putting this project on the shelf for a while, see if others smarter-than-me post similar builds, or if folks have moved on to Sapphire Rapids, or the next big Intel Core enhancement. My Alderlake is kicking butt with Ventura and Windows, so that will be my go to for a while. 
 

Thank you all for seeing my attempt and offering suggestions. Maybe the COM port idea might be useful later on. 

Edited June 11, 2023 by Pinky80
Revised Sapphire Lake to Sapphire Rapids