Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

OK @CaseySJ I got my backup restored to my internal drive and successfully booted. Per your earlier note, you requested a copy of my EFI before trying another upgrade to Monterey. (See attached). Serial Numbers removed.
Glad to hear it — backups are just so essential, particularly in the world of Hackintosh.

Will examine the EFI folder in a couple of hours (currently away from home).
 
Thanks. I'll give Monterey a shot.

I've updated or culled all 32bit apps from my work. Well, there are a couple minor exceptions but I'm going to have to move on.
I just went from Big Sur to Monterey with my Hack, mostly used for DAW purposes. I need to re-authorize lots of stuff, BT is not working properly, drivers will act weird sporadically, not very happy.

On the other hand, Big Sur has broken third party driver(kext) management. Also nasty.
 
OK @CaseySJ I got my backup restored to my internal drive and successfully booted. Per your earlier note, you requested a copy of my EFI before trying another upgrade to Monterey. (See attached). Serial Numbers removed.

Glad to hear it — backups are just so essential, particularly in the world of Hackintosh.

Will examine the EFI folder in a couple of hours (currently away from home).
Please try the attached EFI folder. Reminder to copy serial numbers back to PlatformInfo --> DataHub before use. Let's boot existing Big Sur with this folder first and make sure the following are all working:
  • Ethernet ports
  • WiFi
  • Bluetooth
  • Thunderbolt devices, if any
  • Sleep / wake
  • Reboot / Shutdown
If everything is okay, then we can begin the in-place upgrade once more to Monterey.
 

Attachments

  • EFI-jeff.m.ruth.zip
    45.5 MB · Views: 28
I just went from Big Sur to Monterey with my Hack, mostly used for DAW purposes. I need to re-authorize lots of stuff, BT is not working properly, drivers will act weird sporadically, not very happy.

On the other hand, Big Sur has broken third party driver(kext) management. Also nasty.
Regarding Bluetooth:
  • Have you tried a CMOS Reset?
    • This is done by shutting down the system, flipping power switch on PSU to OFF (yes, to OFF), then shorting the two designated pins on motherboard for about 3 seconds with a flathead screwdriver or other metal (conductive) object.
    • Then we flip power switch on PSU back to ON and boot the system. It should take you to BIOS Setup. We start with Load Optimized Defaults, then we configure the remaining BIOS parameters per Post 1.
    • At the OpenCore boot picker we can press and hold CTRL key while selecting the macOS boot volume. That will make it the default startup disk on future reboots.
    • Then see if Bluetooth behavior has improved...
 
Please try the attached EFI folder. Reminder to copy serial numbers back to PlatformInfo --> DataHub before use. Let's boot existing Big Sur with this folder first and make sure the following are all working:
  • Ethernet ports
  • WiFi
  • Bluetooth
  • Thunderbolt devices, if any
  • Sleep / wake
  • Reboot / Shutdown
If everything is okay, then we can begin the in-place upgrade once more to Monterey.
Hey @CaseySJ, everything checks out ok. The only thing I noticed that I get an error message during boot process when the Gigabyte logo pops up. ( OCS: No schema for LegacyEnable at 2 index, context <NVRAM>)

The other thing I noticed is my native macOS apps (Photos, Safari, etc) seem to be on a new version and I am unable to use them in BigSur
 
Regarding Bluetooth:
  • Have you tried a CMOS Reset?
    • This is done by shutting down the system, flipping power switch on PSU to OFF (yes, to OFF), then shorting the two designated pins on motherboard for about 3 seconds with a flathead screwdriver or other metal (conductive) object.
    • Then we flip power switch on PSU back to ON and boot the system. It should take you to BIOS Setup. We start with Load Optimized Defaults, then we configure the remaining BIOS parameters per Post 1.
    • At the OpenCore boot picker we can press and hold CTRL key while selecting the macOS boot volume. That will make it the default startup disk on future reboots.
    • Then see if Bluetooth behavior has improved...
Hi Casey. Do the memory locations for the BIOS screen setups live in the CMOS? Or is it elsewhere? I'm having BIOS-rot issues and I cleared the CMOS using the above method, but my BIOS memory presets remained. ???
 
Hey @CaseySJ, everything checks out ok. The only thing I noticed that I get an error message during boot process when the Gigabyte logo pops up. ( OCS: No schema for LegacyEnable at 2 index, context <NVRAM>)
We can ignore this for now; this will disappear once the next version of OpenCore Configurator is released. We can also manually remove the LegacyEnable entry from config.plist, but it’s safer to let the next version of OCC do that for us. We would just need to open config.plist in the new version, click on each page on the left side (ACPI, Booter, …) without making any changes, then save the file.

The other thing I noticed is my native macOS apps (Photos, Safari, etc) seem to be on a new version and I am unable to use them in BigSur
Not sure I follow. The backup disk should have Big Sur and the original Big Sur native apps. If the internal disk has Big Sur, but native apps from Monterey, then perhaps it means that this disk wasn’t erased when the backup disk was cloned back to the internal disk.

In other words, if the backup disk with Big Sur has no problems, then the internal disk — being an exact clone — should not have any problems either.
 
Hi Casey. Do the memory locations for the BIOS screen setups live in the CMOS? Or is it elsewhere? I'm having BIOS-rot issues and I cleared the CMOS using the above method, but my BIOS memory presets remained. ???
Our saved presets are fortunately not cleared after CMOS Reset, so we can certainly reload them.
 
We can ignore this for now; this will disappear once the next version of OpenCore Configurator is released. We can also manually remove the LegacyEnable entry from config.plist, but it’s safer to let the next version of OCC do that for us. We would just need to open config.plist in the new version, click on each page on the left side (ACPI, Booter, …) without making any changes, then save the file.


Not sure I follow. The backup disk should have Big Sur and the original Big Sur native apps. If the internal disk has Big Sur, but native apps from Monterey, then perhaps it means that this disk wasn’t erased when the backup disk was cloned back to the internal disk.

In other words, if the backup disk with Big Sur has no problems, then the internal disk — being an exact clone — should not have any problems either.
Hi @CaseySJ, not sure about the app version being outdated. However, I applied a Security Update again, and all is good. I went ahead and started the Monterey Upgrade process. But I think I am going to be running into the same issue I ran into before. I am stuck on the "About 9 minutes remaining" screen for about 25 min now. Ugh.
 
Hi @CaseySJ, not sure about the app version being outdated. However, I applied a Security Update again, and all is good. I went ahead and started the Monterey Upgrade process. But I think I am going to be running into the same issue I ran into before. I am stuck on the "About 9 minutes remaining" screen for about 25 min now. Ugh.
Let’s give it another 30 minutes.

If the in-place upgrade fails or stalls, let’s consider doing a fresh install. We can transfer apps and documents to the fresh system later using Migration Assistant — or manually. I’m concerned that there might be a third party driver in Big Sur that’s not compatible with Monterey.

A fresh installation requires us to create a USB install disk. There is a guide in this thread for doing that, which I can point out if you decide to go that route.
 
Back
Top