Hello @echosat1,Hi @CaseySJ, happy new year and happy (past) 3rd anniversary of your incredible guide!
I'm on OC076 & Monterey 12.0.1 for some time, had some bluetooth issues so it wasn't really working properly, especially after wake up from sleep it would disconnect and connect after login to desktop -> disable bluetooth -> enable bluetooth.
Some days ago I upgraded to Monterey 12.1 and now I have another problem: whenever wake from sleep happens "bluetoothd" process is working like crazy and fans are spinning so fast as if I'm rendering something. After I disable and enable back the bluetooth from the menubar that the craze is over. I don't know if this is happening because of BrcmPatchRAM, OC or macOS Monterey 12.1.
I had my VtD disabled and "DisableIOMapper" was also checked off since November. Today I enabled DisableIOMapper and i think bluetooth problem with connecting (especially after waking) is solved, I'll let you know if I'll have that problem anymore. But my problem with the intense bluetoothd process continues.
Do you have any ideas what should I try? Today OC077 will be released I think, so I will migrate to that but I don't think that will solve anything really.
It is not it. All 3 SSD operate correctly on Z590 and Z690.
But this topic has signed me that the problem is somewhere else.
The issue is likely your Intel 660P. You could try installing NVMEfix.kext to see if it helps > https://github.com/acidanthera/NVMeFix I actually had tried NVMEfix.kext when I was still using the 660p. Then I switched to a WD SN750 and the same problems ended up appearing. Just yesterday I'd...www.tonymacx86.com
SSD NVME was on the processor line, hence the "CPU Fatal Error".
View attachment 538549
I gave SSD to the second slot and the problem solved.
Probably Big Sur has a problem with such a configuration. On Catalina it works almost a year.
Changed the BIOS from 7 to 9 and lifted the system from Catalina to Big Sur.
There was Clover on Catalina. At Big Sur Opencore. But he was hanging at Opencore on Catalina too.
Now it works, but when I put in a second M.2 SSD, it's also a panic kernel after a few minutes.
Hello @andypeterguitar,Hey guys, new to the forum here. I'm currently trying to get Mojave to work with my Z390 Designare with OpenCore. I downloaded the 0.7.6 EFI folder and made sure to set SecureBootModel to Disabled. When I try and boot it goes to the Apple logo with no loading bar and stays there. I had tried removing SSDTs/Drivers/Kexts that weren't applicable to Mojave (10.14.6) but keep getting stuck at the Apple logo. I tired older EFI files for OpenCore 0.7.1 & 0.6.6 & 0.6.1 with all the same issues. I also made sure to set the Device Info/ settings to iMac19,1
I wanted to stay on Mojave due to music software/hardware that I currently use. Any guidance would greatly be appreciated !
- What is the make/model of each NVMe SSD?
Yes, 2 times
- Have you tried CMOS Reset?
- Is there a hardware problem with the NVMe SSD? If you have another computer, does this NVMe SSD work correctly on that system? (If you have external enclosure for NVMe SSD, you can connect it to the same computer or another computer via USB.)
Yes I looked at the screenshots. The MOTU is physically connecting, but the driver is not. If the failure occurs with AppleVTD either enabled or disabled, then I know it's tempting to flash the firmware. You're welcome to try that, but do understand the risks involved.
Please take extreme care when attaching and detaching the SOIC8 clip to the Winbond ROM chip. If you're near-sighted, remove glasses or contact lenses so you can focus easily at close range. Steady hands and good lighting are also essential, as is extreme patience!Ok i will flash it. Fingers crossed
most exciting moment when the 3 dumps all have the same hashPlease take extreme care when attaching and detaching the SOIC8 clip to the Winbond ROM chip. If you're near-sighted, remove glasses or contact lenses so you can focus easily at close range. Steady hands and good lighting are also essential, as is extreme patience!
Flashrom may not find the device right away. It may be necessary to gently wiggle and/or reattach the SOIC8 clip and try several times before a connection with the chip is established. This is certainly not a process to be rushed!