Search results

Mine is set to Disabled as well and my current EFI (0.7.4) on my Monterey test stick booted fine and fast. I'm confused which setting is best, there seem to be conflicting suggestions? Wanted to give the upgrade to Monterey a go this weekend.

Where is your OpenCore.efi? It's missing from the OC folder (0.7.4 EFI)

Yeah, a Samsung SSD 980.

Good thinking. The updates are so far and few between that I never really thought it's about them working to a full version.

Ha! I was right. Version 36d has been completely removed from the Gigabyte-site. It's 36e now. Don't have time to test it this weekend but nice to know it wasn't my system.

A pre-requisite? I'm not sure I totally understand? EDIT Because it annoyed me and I couldn't remember whether or not I had reset nvram, I decided to reflash 36d, redo all bios settings manually and reset nvram. It seems to have done the trick. Testing for stability now, but it boots. :) EDIT2...

Updating to the October 1st BIOS (36d) for my board made my install become unstable with identical bios settings. Panics upon boot but also sometimes mid boot. Weird. Reverted to the version I was running (36c) and going to leave it on that for now. ¯\(ツ)/¯

I've never had to look into that myself, but I imagine that is a good place to start. Make sure you're on the latest version.

My monitor (connected over DisplayPort) shows up as an audio device under Sound. It's fairly new so guess it announces itself as a capable output device to macOS, but that would depend on your monitor type.

Say friends, I use Photoshop 21.2.7 as my daily driver, but I just installed 22.5.0 to check out how it runs without any need for patching. It starts up fine but when I open files, there is this trapezoid artefact in the surrounding area. It's not present in 21.2.7 when I open the same files...

Would be nice if people took the time to report back. Perhaps pinned onder the pc case, drinking his urine to stay alive 😅 since June. Tragic!

Either change MinVersion / MinDate to -1 (from 0) or add the values required for Catalina. (MinVersion=1412101001000000 MinDate=20190820). It will then show up in the bootpicker menu.

I follow the same approach as Shaneee. I grab the compiled debug version (I like to see EVERYTHING! ;)) from Github. Use a dedicated USB boot stick to test my updated EFI to make sure haven't missed anything and it still actually boots. Only then do I copy the EFI to my actual boot drive. I use...

When my macOS nvme was getting too small for comfort I just used Clonezilla on a usb-stick to clone it to my new 1TB nvme. Trying to do it from inside a running operating system is hassle you can avoid that way.

Also check what is set under Preferences > Startup Disk under macOS. Every time I do an NVRAM reset it defaults to my Windows drive and I have to manually set it again.

Ha, you're right. I must check dates more often. It looked like a new post at first glance. 🤤

I don't see the Kernel Quirk ProvideCurrentCpuInfo enabled (True) or even present. Did you follow these instructions? Any boot will hang at exactly this point unless it is enabled and the core count is correctly provided. I manage to b0rk the procedure myself on first try. ;)

I always check the Configuration doc (like a good boy 😇😅) and it mentioned "strongly discouraged" but I think I'll just put -1 in there just in case drunk future me can't resist updating.

The guide says that using -1 is not recommended, but I wondered... I have set Mindate/MinVersion to Catalina values currently, but I might want to take the plunge into Big Sur at some point. Setting it to -1 now would allow me to run the update from within System Preferences at some future point...

I'll double check after my morning shift. You would still recommend against using the OpenCore HFS driver? Yeah, that driver is still very sucky. HfsPlus.efi is correctly referenced in the config and is in the Drivers folder. It's from June 7th, so pretty recent. The cpu patches are latest (same...