Stuck on [EB|#LOG:EXITBS:START] for Somona but works on Monterey. Upgrading BIOS to latest will break Monterey with same error

[GameX]

Hello! (EFI is attached)
First thing, hardware:

AMD Ryzen 9 3950X 3.5 GHz 16-Core Processor
Corsair H100i RGB PLATINUM 75 CFM Liquid CPU Cooler
MSI MAG B550 TOMAHAWK ATX AM4 Motherboard
G.Skill Trident Z RGB 64 GB (2 x 32 GB) DDR4-3600 CL18 Memory
Samsung 860 Evo 1 TB 2.5" Solid State Drive
Western Digital Black 4 TB 3.5" 7200RPM Internal Hard Drive
WD Blue 6TB 3.5" 5400 RPM SATA
Corsair RMx (2018) 850 W 80+ Gold Certified Fully Modular ATX Power Supply
Gigabyte Radeon RX 5700 XT 8 GB GAMING OC
LG WH16NS40 Blu-Ray/DVD/CD Writer
Asus DRW-24B1ST/BLK/B/AS DVD/CD Writer
Phanteks PH-ES614PC_BK ATX

This Hackintosh has been working since Catalina, then Big Sur, then Monterey. When Somona was released, figured I'd simply copy the SSD EFI to the Somona newly created USB and just to see if I got lucky, and then got stuck on [EB|#LOG:EXITBS:START] for the first time, then stayed on Monterey.

Trying more seriously today and started the EFI from scratch again (since I succeeded for Big Sur and Montery once, Dortania guide wasn't new to me and I redownloaded the new files and kexts it from scratch, updated OpenCore debug on the USB and restarted the Plist, applied the new kernel patches from scratch, only reused the SMBIOS.

Stuck at the same error on the Somona USB [EB|#LOG:EXITBS:START].

I'd like to ask is USB mapping necessary for a first boot? I don't remember doing it for Monterey and it works (I have trouble understanding the process even with USBToolbox in Windows, I have too many ports and a hub... might be easier to unplug all the extras and test lol). Could this be the problem ?

Following Dortania guide, in the BIOS:

Secure Boot and CSM are disabled, HCI/XHCI Hand-off enabled, UEFI Mode, SATA Mode: AHCI. I've experiemented with Above 4G Decoding (it's listed as "Above 4G Memory/Crpto Currency mining" in BIOS) ON and OFF, which turning ON also turn on the Re-Size Bar Support. I thought this would work but no.

Then I upgraded the BIOS to the latest (7C91vAI 2025-05-20) and same message again.
Somehow the new BIOS broke Monterey, getting stuck on that same message again (and booting Monterey from OpenCore on the SSD, not the USB!). I haven't touched the Monterey EFI. I've tried turning on 4G Decoding again, but I only way I could fix Monterey was downgrading BIOS back to 7C91vA12020-07-03 (OLD - but it works lol). I remember I struggled with Big Sur as well, I believe I had to downgrade the BIOS to process, but that was a few years ago.

Considering Monterey fail to boot on the latest BIOS, could this be related to why Sonoma fails as well? I'm not sure.

Thank you,

 

[Shaneee]

Your config had a structure error where the Kernel section was included within Misc. This should fix it.

 

[GameX]

LOL, you're right, I feel so dumb (USUALLY I can do better !! HAHA)
Now stuck at IOPCIConfigurator::configure()] PCI configuration PCI0 (yes AppleMCEReporterDisabler is in Kexts and Plist)

I believe we can close the thread (?) as this is something else (and maybe I can figure it out HAHA satisfying when I do). I've turned on Above 4G memory, got a little further and screen went black, no log on the USB, no response (hem, either GPU or Kernel Panic?). Turning 4K on would also break Monterey until I turn it off too. I would update the BIOS again as it has more options, but doing so make Monterey usuable (no idea why) and makes it much more difficult to edit the EFI from Windows and mount the EFI (I managed but it's no fun).

I'll look into it more, I might be able to manage (unless you already know haha) thanks !!
If I find out, I'll update this thread.

EDIT:
The error before black screen is "vfs_xattr: doubleagentd port not valid" like 20 times. I do have AppleMCEReporterDisabler but on second thought, it might be USB mapping, never completed it (as I said, I have too many ports. I might unplug most of them, the hubs and see if that's that first)

EDIT 2:
Updating the BIOS to latest would bring Somona stuck at the same position (I suppose Monterey as well), EB|#LOG:EXITBS:START, I assume this is something to do with my BIOS options but..... I'm confused hehe, I might simply roll back the BIOS again until I progress, but I have good hope.

 

[GameX]

If I may bump the thread, I managed to get quite far (somewhat?).

Updated to latest BIOS, which obviously broke Monterey on [EB|#LOG:EXITBS:START] with an EFI that was functional on old BIOS.
I managed to make it progress by disabling above 4G in BIOS, disable Re-Size Bar Support, npci=0x2000 as bootargs and SetupVirtualMap to True, actually manages Monterey to get quite far in the boot process.

Either it simply reboot, or crash on this, "still waiting for root device" just after this line. I have wondered if it's because I haven't done USB mapping but I don't understand, as this is simply a SATA 3.5" drive that worked on the latest BIOS. I unplugged all USB devices minus keyboard, unplugged my PCI WiFi card and my USB splitters as well but no. Also tried with the 2 Blu-Ray internal drives. It can't find the SATA drive I guess....?

I tried CtlnaAHCIPort as well (not SATA Unsupported).

I think Lilu dev: @ found dead pci device GFX0 is interesting, but GPU was working on old BIOS. What would this has to do with "still waiting for root device" ?



Somona on the USB has different errors. This could be because of USB mapping? At least it no longer get stuck at [EB|#LOG:EXITBS:START] now hm.



Thank you again

 

[Nortek]

Danke. Bei mir bootet er mit dem neuesten Bios update. Im Bios „Above 4G Memory/Crpto Currency Mining“ auf disable setzen. npci=0x3000 als Bootargs und SetupVirtualMap auf True gesetzt. Ja, es liegt am USB Mapping. Danke

 

[GameX]

I actually suceeded !
boot-args: v keepsyms=1 agdpmod=pikera npci=0x3000 debug=0x100 alcid=1

As recommended Above 4G Memory/Crpto Currency Mining disabled.
I was probably only missing SetupVirtualMap=True and definitely agdpmod=pikera. Of course I had a black screen otherwise.
And it actually was Sequoia, not Somona lol OOPS (I jumped from Monterey and mixed the version names, very sorry). I later got stuck on another error after the 2nd installation reboot to "macOS Installer" (bootloop, mach reboot, I saw no kernel panic), I unplug every USB hub, kept only the boards on the motherboard and tried to map them again on Windows.

Then I unplugged my 2 Blu-Ray drives and my other HDDs and I got it booting (not sure why........ heh. Wish I knew). Again, as for Monterey being unable to boot from the SSD again I'm very curious, perhaps it was USB mapping (even tho it was on a SATA HDD), but I installed Sequoia over it so I won't know hehe (I do have a backup of the Monterey partition). Latest BIOS as well.

Thank you again