Please try disabling NVMeFix.kext in Kernel section of config.plist. This may or may not help — the last log entry in the video states that NVMeFix was started, and then no further logs are displayed.
Let’s also change SetApfsTrimTimeout to 0.
Dear
@CaseySJ
I
finally succeed to install Monterey. I was about to write you (to say that both
NVMeFix and
SetApfsTrimTiemout didn't work) when I saw
@shimala post below having a similar problem. Then I realized that while I did the BIOS update, I haven't checked if any settings were different! To my surprise, many settings were changed, I didn't expect it. I changed everything in the BIOS and successfully booted and installed Monterey (I'm writing from the new system right now), I'm glad it worked out.
I'm
so so sorry that I've been wasting your time and I feel so dumb for not checking every aspect as I should've! Lesson learned I guess!
The system is stable and running smoothly. I've noticed some issues but before addressing those, I've got some questions:
- do I need to do
steps 8 to 10 from
your guide? That would make sense, right? Even though, some points in
step 9 seem unnecessary such as the XhciPortLimit or GPUname (it's already stating Vega64)...
- When the system is stable and ready to be duplicated on the NVMe drive, I will also prepare a backup before doing the cloning. Can I follow
Step 11 (bootable backup) or should I follow another guide?
- I read at the beginning of the guide that Samsung NVMe should be avoided. I have since years a 970 EVO (not pro or normal) for my Mojave boot disk, is this gonna be a problem now?
Then I also got a couple of questions regarding my
config.plist. During our tests we:
- disabled NVMeFix.kext
- changed SetApfsTrimTimeout to 0
- set SecureBootModel to Default.
- set ResizeAppleGpuBars to -1.
- removed agdpmod=pikera.
Should I change any of those? I believe that
ResizeAppleGpuBars and
agdpmod=pikera are fine as it is.
