Very slow boot times

[DeadBread99]

macOS Version

Sequoia

What is your CPU's model?

AMD Ryzen 9 5900HX

Please describe the behaviour in detail.

When i activate the NootedRed Kext my boot times get really long to like 5-10minutes and normally its jus about 1 minute this also didnt happen on ventura just after i updated to sequoia

What should've happened instead?

It should boot just as fast as without the kext

If applicable, attach the .gpuRestart, .panic, etc file related to this issue.

No response

[github-actions]

Greetings. It seems like this is the first issue you open on this repository.

We are letting you know that these are for bug reports or feature requests. Most of the reports we receive in this GitHub Organisation are user errors.

For the sake of saving time, here are the most common cases:

• Outdated version of this kext.
• Conflicts with other kexts (e.g. WhateverGreen).
• Issues caused by other kexts like memory corruption (e.g. AirportItlwm).
• Intended behaviour by Apple (e.g. V-Sync or cursor rendering).
• Using cheap hacks like kext/library downgrades (e.g. OCLP, BFixup).
• Duplicate kexts.
• Malformed config.plist caused by configurator software (OCAT, OCC, etc).
• Lack of TSC synchronisation or use of badly programmed TSC kext (only use ForgedInvariant).
• Outdated macOS minor version (e.g. macOS 11.0.0 instead of latest).
• Using beta versions of macOS.
• Using the kext during installation or update. There is a Lilu bug which makes macOS stall during the last install phase.
• Incorrect SMBIOS. Please use iMac20,1, MacBookPro16,3, MacPro7,1 or iMacPro1,1.
• (e)DP link training failure. -NRedDPDelay will fix this as mentioned in the README. This is last resort, black screen can be caused by other factors mentioned.
• Insufficient VRAM size.

We will never support the use of configurator software, solutions like OCLP/BFixup, or using macOS beta versions.

This issue will be looked over by the respective maintainer when they can. In the meantime, look if you can resolve this yourself via checking the above.

Be patient, we are hobbyists.

[VisualEhrmanntraut]

@DeadBread99 Use the release build, not the debug one.

[DeadBread99]

I already do, also tried different versions but nothing changes

[VisualEhrmanntraut]

I don't know what to do in order to debug this

[VisualEhrmanntraut]

Maybe try -NRedDebug and see if there's anything going on while it's stuck

[jalavoui]

if this happens on desktop: open activity monitor - show all processes - sort by CPU
also check /Library/Logs/DiagnosticReports for hang cause

[VisualEhrmanntraut]

Timed out waiting for response.