Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

h9826790

macrumors P6
Apr 3, 2014
16,656
8,587
Hong Kong
I haven't used Martin's package in a long long while now, but if I recall correctly, it should allow for your NVME to mount and show as internal, and I also believe he might already include some code for the Titan Ridge SSDT in his package (though I may be mistaken).

Paging @h9826790

If not, then go to Page 1 of this thread > within the "Complete Your Setup" section > search for "Thunderbolt" > follow those instructions.

Oh yeah, also, all questions/support for Martin's package can take place within his thread as opposed to this one, though you could still ask some questions in here, since it IS still OpenCore.

Let's see what Martin says, but good choice and good luck!
Correct, my package has a SSDT included for flashed TR card (only for the card install in slot 4). The SSDT "switch" is at the beginning of the config, disabled by default. User can change the "false" to "true" to turn that on.

In any case, I still recommend the user read though cdf's instruction.

His problem most likely due to OCLP patched system kext for the GT120. Therefore, his OS now is locked to the GT120. Therefore, his RX580 can display by using the UEFI GOP during boot. But once swtich to the OS GPU driver, it failed to load the driver properly.

I think he can run OCLP again to un-do the root patches. This may be good enough to make the RX580 work.
 

Macschrauber

macrumors 68030
Dec 27, 2015
2,980
1,487
Germany
I live with both worlds. I use oclp and do some changes.

For example oclp does not give -no_compat_check to the boot-args. Should have an option in the gui.

I know this not an oclp thread :)
 

spacedcadet

macrumors regular
Mar 5, 2009
202
53
Hi, has anyone gone through this?
I have a MacPro 5.1 2012 with X5680, 64GB RAM, 500GB SSD Samsung 870 Evo SATA and Nvidia GT 120.
Using MacOS BigSur with OpenCore 0.8.8 and OCLP 0.5.3.
Yesterday my Sapphire RX 580 8GB Pulse arrived, and I installed it on the MacPro, but when I start MacOS, Apple Loading appears, when it finishes loading, instead of entering the user screen, it has a black screen.
Any idea?
Weird. I can't see recovery mode if my second smaller monitor is connected via DisplayPort to the Rx850. If I disconnect it then recovery shows in the main monitor (which is connected by DVI-D). From boot, Big Sur login and Apple progress bar always appear on my 2nd monitor when connected. Almost as if it expects the DisplayPort connection to be the main monitor. Log-in from sleep etc. reverts to main monitor once everything is running. Wonder if there's any relation between these issues?
 

AndyFST

macrumors newbie
Jan 29, 2023
7
0
Toronto, CANADA
I’m using Martin’s package untouched with Monterey and almost everything is running smoothly. I still can’t get a warm boot (restart) to load Monterey without bringing up the prohibitory symbol. Thunderbolt card is recognized (and flag set to true) but without a second boot I can’t get some of my Thunderbolt devices to mount. Is anyone else have an issue with warm boot?
 

cdf

macrumors 68020
Original poster
Jul 27, 2012
2,256
2,583
Is anyone else have an issue with warm boot?
Warm booting to get full Thunderbolt functionality (in particular, USB 3 tunneling) is a well known issue. On the other hand, a prohibitory symbol on every warm boot is definitely not normal: it is due to an OC misconfiguration or to a damaged macOS installation.
 

AndyFST

macrumors newbie
Jan 29, 2023
7
0
Toronto, CANADA
Warm booting to get full Thunderbolt functionality (in particular, USB 3 tunneling) is a well known issue. On the other hand, a prohibitory symbol on every warm boot is definitely not normal: it is due to an OC misconfiguration or to a damaged macOS installation.
Thank you cdf. Is there something specific in terms of open core configuration I can look at? I have installed the OS successfully direct from apple, and tried a few different versions with same results. As rebooting is normally required when installing an OS quite often I would get this prohibitory symbol during an install and then with cold boot it would continue to install with no issue. Is this why it may think the OS is damaged? I will try creating a fresh Monterey install tonight on a brand new internal ssd. I’m really not sure what else to check here.
 

cdf

macrumors 68020
Original poster
Jul 27, 2012
2,256
2,583
Is there something specific in terms of open core configuration I can look at?
Does the warm boot issue also occur with other OC-booted macOS installations? If so, then perhaps you could try a minimal config to rule out any issues. The basic config in post #1 with update option 1 (VMM flag) is about as minimal as you can get.

I have installed the OS successfully direct from apple, and tried a few different versions with same results. As rebooting is normally required when installing an OS quite often I would get this prohibitory symbol during an install and then with cold boot it would continue to install with no issue. Is this why it may think the OS is damaged?
If this has happened right from the beginning (even during the installation), then while the installation can certainly be damaged, the underlying issue is probably elsewhere.

I will try creating a fresh Monterey install tonight on a brand new internal ssd. I’m really not sure what else to check here.
Good idea. Hardware is certainly another possibility! In fact, from the additional info you've provided, I'm leaning towards that. Let us know how it goes.

There is an APPLE folder still left in the EFI from install with updates and files in there. Would this have any issue on warm boot in open core?
No you can just ignore this. This folder is created by the macOS installer for staging firmware updates (which get blocked by OC).
 

AndyFST

macrumors newbie
Jan 29, 2023
7
0
Toronto, CANADA
Interesting... I have 2 Mac OS versions currently installed in my cMP. Mojave is on an SSD using one of the PCI slots with an OWC card. I bought another SSD and adapter and installed it in the first SATA spot and installed Monterey. I was booting opencore off a USB but migrated it on to the SATA SSD with Monterey installed as everything appeared to be working. Currently using Martin Lo's package of OC 0.8.8 as I couldn't figure out which parts to take out/leave in the config to boot both Mojave and Monterey. When I cold boot everything works, but I tried a couple other situations:
Cold Boot Mojave -> Restart into Mojave = Monterey SSD missing from desktop (no incompatible disk alerts)
Cold Boot Mojave -> Restart into Monterey = prohibitory sign (as has been happening in all previous warm boots)
Cold Boot Mojave -> Restart into Mojave = again Monterey SSD not showing (no incompatible disk alerts)
The warm boot seems to make the internal SATA SSD disappear, however OC is present and using the version command in terminal from your first post it shows 88 installed. disk utility does not see the drive or terminal using the list command.
That sounds more like a hardware issue to me :(
I have a brand new Crucial SSD loaded in the 3rd SATA spot, it's erased and formatted as APFS ready for an install and at least it has been showing up consistently with every boot. I will do a deep NVRAM reset, re-install open core on a USB (if the internal SSD is the issue) and try a fresh install of Monterey to the new crucial drive and see if anything changes.
 

antonlinus

macrumors regular
Oct 10, 2019
100
16
i can't see external USBs in the boot picker anymore. i used different USBs and they work on other devices. What could be the issue here?
 

_LiveSorcerer_

macrumors newbie
Oct 10, 2018
25
4
Itu-SP/Brazil
Hi everyone, I'm not having as much luck with OCLP as I am with Martin's OC. I tried to boot MacOS with Martin's OC, without success, and I managed with OCLP, but I'm having a problem with the Boot Loading Apple not appearing when I restart, and I'm having to turn off the machine completely, wait 10 seconds and turn it on again. I'm still having a problem with the Titan Ridge that appears in the report but even connecting the TB3 device it doesn't recognize it. The following error occurs, when I have to initialize the system, after the reboot did not work.

panic(cpu 0 caller 0xffffff8010bcdd43): Kernel trap at 0xffffff8010b97182, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff80fffffe1c, CR3: 0x000000001565f000, CR4: 0x00000000000226e0
RAX: 0x0000000000000000, RBX: 0x0000000000000000, RCX: 0xffffff80153cb771, RDX: 0x0000000000000fee
RSP: 0xfffffff58cae29e0, RBP: 0xfffffff58cae3a60, RSI: 0x0000000000001011, RDI: 0x0000000000000000
R8: 0x0000000000000000, R9: 0x000000000000ff01, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x00000000000000f2, R13: 0xffffff80153c6000, R14: 0xffffff80fffffe1c, R15: 0xffffff80153c7021
RFL: 0x0000000000010246, RIP: 0xffffff8010b97182, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0xffffff80fffffe1c, Error code: 0x0000000000000002, Fault CPU: 0x0, PL: 0, VF: 1

Panicked task 0xffffff95c5425670: 136 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff90f9c86aa0, Frame : Return Address
0xfffffff58cae2390 : 0xffffff8010a7bebd mach_kernel : _handle_debugger_trap + 0x41d
0xfffffff58cae23e0 : 0xffffff8010bde5e6 mach_kernel : _kdp_i386_trap + 0x116
0xfffffff58cae2420 : 0xffffff8010bcd953 mach_kernel : _kernel_trap + 0x4d3
0xfffffff58cae2470 : 0xffffff8010a1ba70 mach_kernel : _return_from_trap + 0xe0
0xfffffff58cae2490 : 0xffffff8010a7c28d mach_kernel : _DebuggerTrapWithState + 0xad
0xfffffff58cae25b0 : 0xffffff8010a7ba46 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xfffffff58cae2610 : 0xffffff80113148b3 mach_kernel : _panic + 0x84
0xfffffff58cae2700 : 0xffffff8010bcdd43 mach_kernel : _sync_iss_to_iks + 0x2c3
0xfffffff58cae2880 : 0xffffff8010bcda26 mach_kernel : _kernel_trap + 0x5a6
0xfffffff58cae28d0 : 0xffffff8010a1ba70 mach_kernel : _return_from_trap + 0xe0
0xfffffff58cae28f0 : 0xffffff8010b97182 mach_kernel : _vc_display_lzss_icon + 0x2a2
0xfffffff58cae3a60 : 0xffffff80112d8946 mach_kernel : _PE_display_icon + 0x56
0xfffffff58cae3a80 : 0xffffff80112a7394 mach_kernel : _IOFindBSDRoot + 0x4d4
0xfffffff58cae3b00 : 0xffffff8011005309 mach_kernel : _set_rootvnode + 0x2909
0xfffffff58cae3e70 : 0xffffff8010ab2dcd mach_kernel : _max_valid_stack_address + 0x142d
0xfffffff58cae3fa0 : 0xffffff8010a1b19e mach_kernel : _call_continuation + 0x2e

Process name corresponding to current thread (0xffffff90f9c86aa0): kernel_task
Boot args: keepsyms=1 debug=0x100 -lilubetaall -btlfxallowanyaddr ipc_control_port_options=0 -nokcmismatchpanic -disable_sidecar_mac

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 21.6.0: Mon Dec 19 20:44:01 PST 2022; root:xnu-8020.240.18~2/RELEASE_X86_64
Kernel UUID: 33C30416-3302-3FFF-9686-A557DED28C5B
KernelCache slide: 0x0000000010800000
KernelCache base: 0xffffff8010a00000
Kernel slide: 0x0000000010810000
Kernel text base: 0xffffff8010a10000
__HIB text base: 0xffffff8010900000
System model name: MacPro5,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization
Hibernation exit count: 0

System uptime in nanoseconds: 62356280284
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000000e84b95868
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000019d1712e88 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: 0xffffff80f5bb1000 - 0xffffffa0f5bb1000
. PGZ : 0xffffff80f5bb1000 - 0xffffff80fdbb2000
. VM : 0xffffff80fdbb2000 - 0xffffff85c954b000
. RO : 0xffffff85c954b000 - 0xffffff876287e000
. GEN0 : 0xffffff876287e000 - 0xffffff8c2e217000
. GEN1 : 0xffffff8c2e217000 - 0xffffff90f9bb0000
. GEN2 : 0xffffff90f9bb0000 - 0xffffff95c5549000
. GEN3 : 0xffffff95c5549000 - 0xffffff9a90ee3000
. DATA : 0xffffff9a90ee3000 - 0xffffffa0f5bb1000
Metadata: 0xffffffa0f5bc1000 - 0xffffffa115bc1000
Bitmaps : 0xffffffa115bc1000 - 0xffffffa12dbc1000
 

sfalatko

macrumors 6502a
Sep 24, 2016
639
364
Interesting... I have 2 Mac OS versions currently installed in my cMP. Mojave is on an SSD using one of the PCI slots with an OWC card. I bought another SSD and adapter and installed it in the first SATA spot and installed Monterey. I was booting opencore off a USB but migrated it on to the SATA SSD with Monterey installed as everything appeared to be working. Currently using Martin Lo's package of OC 0.8.8 as I couldn't figure out which parts to take out/leave in the config to boot both Mojave and Monterey. When I cold boot everything works, but I tried a couple other situations:
Cold Boot Mojave -> Restart into Mojave = Monterey SSD missing from desktop (no incompatible disk alerts)
Cold Boot Mojave -> Restart into Monterey = prohibitory sign (as has been happening in all previous warm boots)
Cold Boot Mojave -> Restart into Mojave = again Monterey SSD not showing (no incompatible disk alerts)
The warm boot seems to make the internal SATA SSD disappear, however OC is present and using the version command in terminal from your first post it shows 88 installed. disk utility does not see the drive or terminal using the list command.
That sounds more like a hardware issue to me :(
I have a brand new Crucial SSD loaded in the 3rd SATA spot, it's erased and formatted as APFS ready for an install and at least it has been showing up consistently with every boot. I will do a deep NVRAM reset, re-install open core on a USB (if the internal SSD is the issue) and try a fresh install of Monterey to the new crucial drive and see if anything changes.
A couple of minor thoughts - first it is probably best to ask for help on Martin Lo's package in the dedicated thread. Second - Mojave does not understand the APFS format of Monterey so the disk will not show up. You should, however, get an error message about an incompatible disk when you get to the Mojave desktop on boot.

Not really solving your issues but maybe narrowing things down a bit.
 

zgagato

macrumors member
Nov 24, 2021
86
28
Can you help me guys? i have mohave 5.1 mp and had to come back to my flashed radeon 7950 because my rx580 died.
Now how to remove open core from the efi patition?
Just deleting oc and boot from efi part is enough?
do i have to rebless it?

thanks
 

roobarb!

macrumors 6502
Jul 30, 2009
277
185
Does anybody know where I can get a trustworthy copy of Monterey 12.3.1? I'm still experiencing unexpected black screen reboots with 12.6 and would like to experiment with the pre-AVX version.

Otherwise I may drop the Mac Pro to Big Sur now I've got this laptop set up with a dock. Graphics-wise the Radeon VII still thrashes this M1 Pro (and I can boot Windows on the MP5,1, woo) but the MacBook Pro is twice as fast multi-core and nearly three times faster single-core for the daily chew. And it saves my electricity bill, think it's using about 5 W. 😂

Found a little time to experiment this evening. I started from zero, followed the post 1 guide and made a completely new OpenCore EFI, just in case. Lovely. Booted new Monterey 12.6.3 installer, installed to an NVME drive just fine. Happy days.

System sat at the setup screen for forty minutes while I finished something up, then I set up my account. I did not set up iCloud - just a normal old local account with no online shenanigans.

Loaded System Preferences and went to adjust mouse tracking speed... black screen, reboot.

I'm creating a Big Sur 11.7.3 installer now to see if that survives longer and I'll follow the same process. I skipped Big Sur, so it'll at least be interesting to see it.

EDIT: Big Sur won't boot and it's time to stop, something about "AppleNVMe assert failed". Same OC which just installed Monterey. OpenCore does boot back into the black-screening Monterey though, where I got this report:

panic(cpu 0 caller 0xffffff800f4294c1): IOSCSIPeripheralDeviceType05::setPowerState(0xffffff9076c69b80 : 0xffffff8011880aea, 1 -> 4) timed out after 100679 ms @IOServicePM.cpp:5524
Panicked task 0xffffff95420e3670: 303 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff9077c5d000, Frame : Return Address
0xfffffff07e083a30 : 0xffffff800ec7bebd
0xfffffff07e083a80 : 0xffffff800edde5e6
0xfffffff07e083ac0 : 0xffffff800edcd953
0xfffffff07e083b10 : 0xffffff800ec1ba70
0xfffffff07e083b30 : 0xffffff800ec7c28d
0xfffffff07e083c50 : 0xffffff800ec7ba46
0xfffffff07e083cb0 : 0xffffff800f5148b3
0xfffffff07e083da0 : 0xffffff800f4294c1
0xfffffff07e083e00 : 0xffffff800f428c89
0xfffffff07e083e10 : 0xffffff800f44303e
0xfffffff07e083e50 : 0xffffff800f427ac8
0xfffffff07e083e70 : 0xffffff800eccef35
0xfffffff07e083ee0 : 0xffffff800ecd0002
0xfffffff07e083fa0 : 0xffffff800ec1b19e

Process name corresponding to current thread (0xffffff9077c5d000): kernel_task
Boot args: -v -no_compat_check chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21G419

Kernel version:
Darwin Kernel Version 21.6.0: Mon Dec 19 20:44:01 PST 2022; root:xnu-8020.240.18~2/RELEASE_X86_64
Kernel UUID: 33C30416-3302-3FFF-9686-A557DED28C5B
KernelCache slide: 0x000000000ea00000
KernelCache base: 0xffffff800ec00000
Kernel slide: 0x000000000ea10000
Kernel text base: 0xffffff800ec10000
__HIB text base: 0xffffff800eb00000
System model name: MacPro5,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: NO (0xe00002bc)
Hibernation exit count: 0

System uptime in nanoseconds: 2577038269397
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000002580373656e
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000030c2d713b0 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: 0xffffff807114b000 - 0xffffffa07114b000
. PGZ : 0xffffff807114b000 - 0xffffff807d14c000
. VM : 0xffffff807d14c000 - 0xffffff854814b000
. RO : 0xffffff854814b000 - 0xffffff86e114b000
. GEN0 : 0xffffff86e114b000 - 0xffffff8bac14b000
. GEN1 : 0xffffff8bac14b000 - 0xffffff907714b000
. GEN2 : 0xffffff907714b000 - 0xffffff954214b000
. GEN3 : 0xffffff954214b000 - 0xffffff9a0d14b000
. DATA : 0xffffff9a0d14b000 - 0xffffffa07114b000
Metadata: 0xffffffd116bed000 - 0xffffffd136bed000
Bitmaps : 0xffffffd136bed000 - 0xffffffd156bed000

last started kext at 32830848642: >DiskImages.SparseDiskImage 493.0.0 (addr 0xffffff80114b1000, size 8192)
last stopped kext at 1733126485834: >!A!IMCEReporter 115 (addr 0xffffff7fa75b8000, size 57344)
loaded kexts:
com.khronokernel.FeatureUnlock 1.1.2
as.vit9696.WhateverGreen 1.6.3
as.vit9696.Lilu 1.6.3
>DiskImages.SparseDiskImage 493.0.0
>DiskImages.ReadWriteDiskImage 493.0.0
>DiskImages.UDIFDiskImage 493.0.0
>DiskImages.RAMBackingStore 493.0.0
>DiskImages.HTTPBackingStore 493.0.0
>DiskImages.FileBackingStore 493.0.0
>AudioAUUC 1.70
>!AUpstreamUserClient 3.6.9
>!AMCCSControl 1.16
@kext.AMDFramebuffer 4.0.8
>!AMikeyHIDDriver 131
>AGPM 129
>!AMikeyDriver 340.2
@filesystems.autofs 3.0
>!AHDA 340.2
@kext.AMDRadeonX5000 4.0.8
@kext.AMDRadeonServiceManager 4.0.8
>!AGFXHDA 140.3
>!AGraphicsDevicePolicy 6.5.7
@AGDCPluginDisplayMetrics 6.5.7
>!ALPC 3.1
>pmtelemetry 1
|IOUserEthernet 1.0.1
>usb.!UUserHCI 1
>!AFWOHCI 5.7.5
>!AHV 1
>!ADiskImages2 126.141.2
@kext.AMD10000!C 4.0.8
>!A!ISlowAdaptiveClocking 4.0.0
>ACPI_SMC_PlatformPlugin 1.0.0
>!AFileSystemDriver 3.0.1
@filesystems.tmpfs 1
@filesystems.lifs 1
@filesystems.hfs.kext 583.100.10
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
>PioneerSuperDrive 533.120.2
|SCSITaskUserClient 456.140.3
@filesystems.apfs 1934.141.2
>AirPort.BrcmNIC 1400.1.1
>!I82574LEthernet 2.7.2
>!AAHCIPort 351.100.4
@private.KextAudit 1.0
>!ARTC 2.0.1
>!AHPET 1.8
>!AACPIButtons 6.1
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
>!A!ICPUPowerManagementClient 222.0.0
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 402
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
@Dont_Steal_Mac_OS_X 7.0.0
>!A!ICPUPowerManagement 222.0.0
@kec.!AEncryptedArchive 1
>DiskImages.KernelBacked 493.0.0
|IOAVB!F 1040.6
@plugin.IOgPTPPlugin 1040.3
|IOEthernetAVB!C 1.1.0
>!AHIDKeyboard 228.2
@kext.triggers 1.0
>DspFuncLib 340.2
@kext.OSvKernDSPLib 529
@kext.AMDRadeonX5000HWLibs 1.0
|IOAccelerator!F2 462.8
>!AAudioClockLibs 140.1
@kext.AMDRadeonX5000HWServices 4.0.8
>!ASMBus!C 1.0.18d1
>!AHDA!C 340.2
|IOHDA!F 340.2
|IOAudio!F 340.2
@vecLib.kext 1.2.0
>!ASMBusPCI 1.0.14d1
>!AGraphicsControl 6.5.7
|IO!BSerialManager 9.0.0
|IO!BPacketLogger 9.0.0
|IO!BHost!CUSBTransport 9.0.0
|IO!BHost!CUARTTransport 9.0.0
|IO!BHost!CTransport 9.0.0
>IO!BHost!CPCIeTransport 9.0.0
|IOFireWire!F 4.8.3
|CSR!BHost!CUSBTransport 9.0.0
|Broadcom!BHost!CUSBTransport 9.0.0
|Broadcom!B20703USBTransport 9.0.0
>!AIPAppender 1.0
|IONDRVSupport 597
@kext.AMDSupport 4.0.8
@!AGPUWrangler 6.5.7
@!AGraphicsDeviceControl 6.5.7
|IOGraphics!F 597
|IOSlowAdaptiveClocking!F 1.0.0
>IOPlatformPluginLegacy 1.0.0
>IOPlatformPlugin!F 6.0.0d8
>usb.IOUSBHostHIDDevice 1.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>usb.!UHub 1.2
>!ABSDKextStarter 3
|IOSurface 302.14
@filesystems.hfs.encodings.kext 1
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
|IONVMe!F 2.1.0
|IOSCSIMultimediaCommandsDevice 456.140.3
|IOBD!S!F 1.8
|IODVD!S!F 1.8
|IOCD!S!F 1.8
>!AXsanScheme 3
|IOAHCIBlock!S 333.140.2
|IOAHCISerialATAPI 270
|IO80211!FLegacy 1200.12.2b1
|IOSkywalk!F 1.0
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
|IOAHCI!F 297
>usb.!UEHCIPCI 1.2
>usb.!UUHCIPCI 1.2
>usb.!UUHCI 1.2
>usb.!UEHCI 1.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
|IOTimeSync!F 1040.3
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 9.0.0
|IOReport!F 47
$quarantine 4
$sandbox 300.0
@kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 533.120.2
|IOUSBMass!SDriver 210.120.3
|IOSCSIBlockCommandsDevice 456.140.3
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 456.140.3
>!AMobileFileIntegrity 1.0.5
$!AImage4 4.2.0
@kext.CoreTrust 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!ACredentialManager 1.0
>KernelRelayHost 1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AACPIPlatform 6.1
>!ASMC 3.1.9
|IOPCI!F 2.9
|IOACPI!F 1.4
>watchdog 1
@kec.pthread 1
@kec.Libm 1
@kec.corecrypto 12.0

Mean anything to you all? :)
 
Last edited:

roobarb!

macrumors 6502
Jul 30, 2009
277
185
Did you make sure to add AppleMCEReporterDisabler?

Yup, that's there and seems to be in the config just fine.

Weirdly, I can install Monterey with no issues, but trying to install Big Sur 11.7.3 gets me all sorts of nonsense. I made a new installer USB and it gets a good chunk of the way through the process, then after a reboot back into the installer it gives me this:

IMG_7639.jpeg

Same OC 0.8.8 and config allows installation of Monterey 12.6.3 to the same drive with no trouble.

I know I'm chasing two problems here - the black screen and reboot thing in Monterey is the one that's actually important. If that worked I'd not be bothered about Big Sur, it's just a test to see if it bombs in the same way at any point.
 

cdf

macrumors 68020
Original poster
Jul 27, 2012
2,256
2,583
then after a reboot back into the installer it gives me this
Hmm. I haven't touched Big Sur in a while. If SurPlus is still needed, then the kernel version settings might need an adjustment. As for the Monterey issue: would you mind posting your config just in case?
 

roobarb!

macrumors 6502
Jul 30, 2009
277
185
Hmm. I haven't touched Big Sur in a while. If SurPlus is still needed, then the kernel version settings might need an adjustment. As for the Monterey issue: would you mind posting your config just in case?

Ahh, SurPlus! I'll bet that's missing from my config - yes, it is. I'll add it and give Big Sur another test.

Don't mind at all, appreciate the help. Attached is my config as-is and working for Monterey, but with the weird black screen-reboot issue happening. It's basically vanilla except for the PowerPlay table for the Radeon VII and the catch-all internal drives patch. I've removed both of those with no change in behaviour.

EDIT: So strange, Big Sur installer now won't boot with those "AppleNVMe Assert failed" errors again. Typo in the config file. Always use plutil, kids! :D
 

Attachments

  • config.plist.zip
    5.6 KB · Views: 64
Last edited:

roobarb!

macrumors 6502
Jul 30, 2009
277
185
Not really seeing anything obvious here. Perhaps try disabling FeatureUnlock and AVXpel...

Thanks, I'll give that a go later on, see how Monterey behaves.

Big Sur installed fine in the end with the addition of SurPlus... but the completed installation will not boot. In verbose mode I can see it loads fine up to a point, then the text output becomes scrambled, then it begins boot-looping.

This is all with the same config file, by the way. Monterey boots fine every time.
 

antonlinus

macrumors regular
Oct 10, 2019
100
16
i can't see external USBs in the boot picker anymore. i used different USBs and they work on other devices. What could be the issue here?
does't anyone have a fix for this? I looked at a bunch of settings in my config.plist but could't spot anything that could prevent the USB booters not to show up in the OC boot picker. I tried different USB drives as well as different installers of win 10 and 11
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.