Recent content by Fraxinus

I've swapped the disks. Windows is now on my samsung NvME, Monterey is on a Samsung SSD. No slow boot with this configuration. You don't need to remove the NvME, but to boot on a different drive.

Update: Swapped drives from NvME to SSD (both Samsung), unsurprisingly the long boot time vanished with same conifg (except disabled NvMefix.kext on SSD config).

I've used NvMEfix.kext as well (MacOs 11 and MacOs 12), so this won't keep away the slow boot if you have a Samsung NvME. I guess this isn't connected to this Problem. I don't use any of these kexts as my NvME is formated in APFS.

I see. Did you use the Samsung for MacOS before any Monterey beta was introduced?

I'm quite sure that these slow boots are connected to the nvme Samsung drives and macOS Monterey. Wondering if there's possibly a connection about formatting the drive to HFs+ instead of APFS (just for Samsung disks, as I've read here,#50). With the same configuration did boot fast on Big Sur...

Yeah. Definitely a TRIM issue related to Monterey and Evo 970 Nvme. As far as I know you never should disable TRIM, otherwise you can damage your nvme-ssd.

It seems to be connected to Samsungs m.2 nvme. I'm not sure if a fresh install does change that behaviour. Did anybody find a workaround? Could we rename the Thread to something like: "samsung nvme and Monterey, extreme slow boot."?

Are there any webdrivers for Nvidia-cards for Mojave? As far as i know they don't exist, but i'm not up to date on this topic.

Same Samsung Nvme drive?

Do you use FileVault as well? ps my bootlog looks similar.

Same problem here. It takes my hack about 130 seconds to boot from the point of entering my password. I'm using FileVault and OC 0.7.3 and a m.2 Samsung 970 evo 1tb. No clue why the boot is so slow, used to work flawless with Big Sur.

I think you should be able to switch in-between, if you clean the nvram after reboot. On the other side, I've read that some persons had a mess after trying to do that. Maybe due to some bad configured clover and OpenCore.

Do you use OC 0.7.1? I've read in some Forum about theses settings: SecureBootModel = Disabled And if you're using FileVault; authenticated Restart should be active (Boolean = 1) For me these two changes made the update to Mac OS 12 beta work.

Hi. Nice, i really support your decision to change to OC. From my point of view OC does really work smooth. Why don't you first try to make a bootable Usb-stick (thumb-drive) with a working OC Efi and config.plist? After you've managed this, you then can safely migrate from Clover to OpenCore...

Updated with OC 0.6.9, no Issues. Thanks to all the developers! Ps. Seems like the annoying Checkbox asking to "enable Siri" at the end of the update is finally gone.