Recent content by kentval

Just a hail and farewell here. I've been on this forum for over a decade now. As for myself, I was the first thirdparty developer ever hired by Apple Computer, back in 1978, so I've been around the block. I'm 75 now, and my body-parts are suffering a bit of wear and tear. But I still love...

bump/update to this: I just now tried with 12.3.1, and managed to get all the way through the install. It seems to me that 12.3.1 fixed the issue, at least for me. Now I have to decide if I want to cancel my Studio order... :cool:

First failure in 6 or 7 years. Tried update and full installer. Boots to about 1/3 Apple logo thermometer, and just hangs. Maybe its the Gods telling me to buy a M1 Studio.. or just a good excuse... :-)

All of this discussion is anecdotal, as is this: I have the Samsung EVO 970 as my boot. I installed 12.1 yesterday. My cold boot time ("cold" = machine is OFF) to the finder desktop used to be 2:12. Now it's 2:45. I don't really consider that "fatal" or worth spending the $$ and energy to...

Me too. Thanks!

OK... here's why I ask about TRIM being "broken" (as in "does absolutely nothing at all") on the 970. What, exactly does that sentence above mean? The original issue is here: https://github.com/acidanthera/OpenCorePkg/blob/0.6.8/Docs/Configuration.tex#L2592-L2632 It says: " On several...

There are several threads surrounding the Monterey/NVMe issues, and in particular the Samsung 970 EVO. I'd like to know if I clearly understand the issue with the 970. 1) The issue is ONLY long boot times because of TRIM. Once booted, the system runs fine. Is that correct? 2) TRIM still works...

Yep. The issue for hackintosh is apparently Trim duration leading to long load times. I personally don't care about adding a minute or two to the boot time, if it leads to a complete trim at boot... so I set my SetApfsTrimTimeout quirk to 4294967295. I am still, however, going to wait for the...

Just to close the circle, it (the bricking) was a problem with T2 firmware and Apple has today (11/5/21) released a fix, apparently embedded in the latest Monterey download.

Good point. Obviously Monterey is NRPT (Not Ready for Prime Time.)

I have no way of knowing if this is associated with the 970 issue, but Monterey has its share of serious problems: https://www.macrumors.com/2021/11/01/macos-monterey-bricking-older-macs/ Think I'll wait and see if a solution shows up here later... (yeah: I have a 970...)

solved. I had to set the Quirk DisableRtcChecksum to true.

Thaks for your patience and courtesy. I have the ones you have and a few more: prev-lang:kbd ota-updateType ota-controllerVersion multiupdater-state multiupdater-retry-limits efi-boot-device-data efi-boot-device efi-backup-boot-device-data efi-backup-boot-device SystemAudioVolumeDB...

Thanks to one and all. So judging by what I read here, "Clean" really means "reset" as they both do the same thing. Resetting the NVRAM can be problematic, having been there and done that. It may require, for example, booting from some other device and setting the boot device back to the...

Thanks... that would be my guess too. But I was hoping to find someone who actually knows. ClearNvram would be a good thing, depending on what it does not clear :-)