Search results

Post EFI here and let me have a look. AudioGod has been hit with lack of parts due to natural disaster and I aint just sitting down doing nothing

Try providing your config.plist

Updated to Monterey 12.1, Updated OC 0.7.6 and now has Resizable BAR Support both MacOS and Windows. AppleGPUBarSize = 0, GPUBarSize = -1 Updated various kexts along the way also.

Sorry-- apparently I thought I got it but I'm still experimenting. What I have figured out so far is that I have multiple USB controllers going on and have no idea why the AML file has two same XHC0 entries with inconsistent USB address syntax. Do give this a try and let me know (and how to test...

For Bluetooth issue-- assuming you have placed config.plist properly, all you have left to do is fully shut it down, power down (like PSU switch off or pull the plug) for 30 seconds, and then reboot, Reset NVRAM, and try it. And as for FixShutdown... I'm still experimenting it-- I don't even...

Has anyone ran into issue of opencore suddenly booting all on its own? Tried XhciPortLimit=true, DisableRtcChecksum=true, applying FixShutdown-USB-SSDT.dsl, compiled with my own USB XHC0 path (_SB.PCI0.GP13.XHC0) but all these won't do anything uwu Edit -- It seems the problem is getting...

Did a small update to add FixShutdown-USB-SSDT.aml to fix shutdown issue (sudden wake after shutdown, but it really didn't shutdown due to S5 callout issue. Noticed that my MB LEDs were still on even tho it was "powered down". Used USB Controller Path _SB.PCI0.GP13.XHC0 for compiling.

Confirmed working on Monterey with some tweaking. https://www.tonymacx86.com/threads/how-to-fix-aquantia-10-gb-ethernet-for-big-sur.305261/

Guess the lessons learned is do reset NVRAM religiously every time when you modify OC

Update-- BrcmPatchRAM has 2.6.1 available today. If you want to get Bluetooth to work again in Monterey, download BlueToolFixup from 2.6.1 version, and add that kext into OC Config.plist along with IntelBluetoothFirmware.kext and you should be good to go. Do not include...

BrcmPatchRAM version 2.6.1 is now available for download - Obtained BlueToolFixup.kext from there and the bluetooth now works well!

Super sucks. I'm sorry to hear that has happened to you. Best of luck with electronics recovery during this horrible time for purchasing...

I hope 4G Encoding is also disabled. The boot argument npci=0x2000 will cause boot to get stuck. Also IntelBluetoothInjector.kext also causes this, basing off from my Aorus X570 Xtreme

Bumping up to notify that Monterey is now running under OC 0.7.4 with some issues like Bluetooth and IntelSmallTree. SmallTree no big deal-- just activated Aquantia 10GbE instead. But Bluetooth is a bit annoying. Also anyone have idea on improving Airport speed? For 802.11AX performance is terrible.

Did you add any other kexts on top of what AudioGod had? Did you fill "Arch" parameter correctly?

Alright! Got it running! Will update my Success Stories for Aorus X570 Xtreme I still don't know why bluetooth is not working. If SmallTree is not working, then activate Aquantia 10GbE!

Welp— black screen for me… pikera or ignore both dont work

Is it possible to just upgrade from Big Sur then, given that it has OC 0.7.4 already installed and ready (and do some changes in some kexts)?

Okay-- I got it working again except Intel Bluetooth Drivers... Now only Bluetooth Firmware and Injector causing Kernel Panic. Will try not adding ExecutePath and try again... EDIT: Nope no matter what I do, as soon as I enable IntelBluetoothFirmware and IntelBluetoothInjector, the kernel...

Is your new EFI supposed to only work with Monterey, and not Big Sur? Should I postpone until Monterey becomes available? — EDIT: Turns out some of the kexts I’m trying to add is causing kernel panic: USBMap, NVMeFix, Airportltlwm, IntelBluetoothInjector, IntelBluetoothFirmware.. One of these...