12.0.1 version repeated 5 min boot up delay named ALUC

[6900Merc]

Hi
I'm going crazy tweaking the Opencore 0.75 config.plist to no result.
Below are screenshots of where it gets stuck for 5 mins on every reboot where its trying to:

ALUC:clientDied
ALUC:init
methodSetClientDomain entered
registerNotificationPort entered

over and over and over

Any ideas how to avoid with full reboot? (using Sleep succesfully, but I have dual boot for a reason, so full restart happens often)

What is this related to? Config.Plist or something inside Monteray (was never present Big Sur and before).
Is it hardware/ACPI or software/user/SMBIOS related?

Google nor OpenCore seem to have much when I search?

FYI, once it boots everything works great, as before, WIFI, Bluetooth, RX 6900, Apple Mouse, TrackPad, Sound, all USBs ....

 

[theruck]

its your Samsung NVMe drive. its known issue with 80 topics all around

 

[6900Merc]

Thanks for reply. Currently there is no Samsung NvME nor SSD connected. Only a Kingston SSD.

 

[FormerUser-400995]

Thanks for reply. Currently there is no Samsung NvME nor SSD connected. Only a Kingston SSD.

The slow boot you described is a symptom of the TRIM issue, noticeable when booting macOS (Monterey) on an APFS formatted NVMe SSD drive, so it's easy for casual users to jump to that conclusion.

Is your Kingston SSD an NVMe device?

If so, it could be that your drive is affected but not yet listed as such. On that same page is a description of the issue, and (if you scroll down) you will find instructions on how to test whether yours is among the unfortunates.

That said, and judging by the image posted, other factors are likely at play.

If you will post your config.plist (after removing personal system information), others will be more able to help determine whether your issue is hardware or configuration related.

Cheers.

 

[6900Merc]

Thanks, no, the Kingston is not an NVME device. It is a Kingston SSD.
It boots normally on Big Sur.

I'll replace the SSD to a different brand and report back.

If the next couple of Monterey updates don't improve things, I guess I ll go back to Big Sur.

 

[FormerUser-400995]

Thanks, no, the Kingston is not an NVME device. It is a Kingston SSD.
It boots normally on Big Sur.

I'll replace the SSD to a different brand and report back.

If the next couple of Monterey updates don't improve things, I guess I ll go back to Big Sur.

Forgive what may seem an unnecessary question, but just to clarify, you're saying that the Kingston you have is a normal SATA SSD drive, is that correct? - NVMe drives are also called SSD.

I personally use Samsung 860 EVO SATA drives which, apart from long being recommended, serve me adequately. The 870 EVO, being the latest incarnation, is probably a decent choice.

Cheers.

 

[theruck]

log show --predicate "processID == 0" | grep spaceman

run this and see how much time did TRIM took

 

[ChillyPenguin]

I'm getting the ALUC:clientDied loop on my new Monterey install. Same pattern as the original poster's:

ALUC:clientDied
ALUC:init
methodSetClientDomain entered
registerNotificationPort entered

The drive is a Western Digital WDS500G2B0A, which is not an NVME device, so I'm not sure it's the Trim issue. The Mac System Report shows that it's not enabled for Trim, in fact. None of the suggested fixes on that Dortania Trim thread made any difference anyway.

Eventually, after about 15 loops, and about 5 minutes, it does boot up Monterey. None of my internal drives are visible though - not even in the Disk Utility - except for the Monterey host drive itself.

Update - Solved!
It was the BlueTooth Injector, of all things, that was causing my problem.

Removing the entry Kernel->Add->IntelBluetoothInjector.kext from my config.plist fixed it.

 

[mantianxing]

I'm getting the ALUC:clientDied loop on my new Monterey install. Same pattern as the original poster's:


The drive is a Western Digital WDS500G2B0A, which is not an NVME device, so I'm not sure it's the Trim issue. The Mac System Report shows that it's not enabled for Trim, in fact. None of the suggested fixes on that Dortania Trim thread made any difference anyway.

Eventually, after about 15 loops, and about 5 minutes, it does boot up Monterey. None of my internal drives are visible though - not even in the Disk Utility - except for the Monterey host drive itself.

Update - Solved!
It was the BlueTooth Injector, of all things, that was causing my problem.

Removing the entry Kernel->Add->IntelBluetoothInjector.kext from my config.plist fixed it.

Thanks a lot for the resolution. I spent a lot of time checking my EFI, until I saw your reply, I disabled the bluetooth on the motherboard from bios setting, and it works so well now.