Search results

You do have to add the kext to the config.plist. Here's what I added in the kext section: <dict> <key>Comment</key> <string></string> <key>MaxKernel</key> <string></string> <key>PlistPath</key>...

Unfortunately, it appears that on this site, I can't even mention the name of the site in question. It begins with an r and is a VERY well known discussion site. The thread title is "is Power Management configurable on Monterey for SandyBridge CPU". Google should find it for you. There are links...

The link that I originally posed describes what happens - basically the problem with 12.3 is that Apple changed the way that the power management scheme is recognized to be more based on the CPU. ASPP-Override effectively reverts that change

I have used ASPP-Override.kext and that seems to be working for me. I did post links yesterday, but it appears that despite being a member here since forever, my post was deleted.

Attached. I no longer have that system, but this is the most recent version of the config file that I used. Note serial numbers, etc erased

Updated both my Sandy Bridge and Haswell systems using OC 0.7.4. All smooth other than the Haswell system needing it's system definition changed from iMac15,1 to 17,1.

You need to update your config file. For reasons unknown, 0.7.3 breaks compatibility with previous versions. See here: https://www.tonymacx86.com/threads/how-to-opencore-0-7-2-0-7-3-differences.315596/

Yes, well done. Good build.

Well, the first thing to attend to is that according to those error messages the NvmExpressDxe.efi driver isn't where it should be.

I think the easiest way for you to get something working will be to use an existing working config file, then modify that for your specific needs.

I'd suggest that you try with the config file in my original "Sandy Bridge/Z68" post above. The config file you posted has a number of patches that I don't think you should have.

Not really - I didn't do anything special; it just worked. But I would guess it must have something to do with your systems definition. Probably sensors not showing as expected.

No, works for me

Nothing - just ran trimforce You should be able get the trim status from:

Works fine for me with a Samsung 850

Boot using the dual BIOS feature, then reflash.

Ok, I tried the 0.6.3 beta. In my case, the old 0.6.2 config.plist worked without change. My config.plist did not use MemoryFormFactor

A URL for the reference manual would be useful.

Sorry, I don't know. But I think the warning would be a very good idea.

FYI, I filed a bug report - it was instantly closed, on the basis that this is a BIOS problem. I do think that the guides should be updated to specifically warn of the Haswell issue, but it doesn't look like that's going to happen.