Contribute
Register

Gigabyte Z390 M Gaming build with working NVRAM

Hmm... Maybe try setting the following:

config.plist > UEFI > APFS > MinDate = "-1" (without the quotes)
config.plist > UEFI > APFS > MinVersion = "-1" (without the quotes)

For Bluetooth, if you are not using a natively supported Wi-Fi/Bluetooth card, you will need to BrcmPatchRAM and use BlueToolFixup.
Tried these options, but they don't seem to have any affect. I'll try and record the 0.8.1 verbose data output and compare it against a 0.7.9 run to see where divergence occurs.
 
pastrychef,
Let me start by thanking your for the helpful OC EFI examples. Your OC examples allowed me to get Big Sur running on my system after countless hours of tinkering. I had literally given up on Big Sur until I discovered your thread.

My GB 390m system is nearly identical to yours, but I ran into immediate trouble with 0.8.0. Multiple problems were affecting me, including an BIOS configuration issue and a Bluetooth module incompatibility. After stripping the machine, version 0.7.6 successfully booted and installed Big Sur.

Then I moved up to more recent versions. Version 0.7.9 will boot into Big Sur, but version 0.8.0 and 0.8.1 won't. The SerialInit item was removed from the 0.8.1 plist file, and verbose mode was added to the boot args. With 0.8.1 the machine comes up, then you select the Big Sub drive, and the boot fails right before the final shift into the progress bar. The verbose text flies by pretty quick, so I'll likely need record it to see if there are any obvious faults. It appears that my system behaves the same as joobuzz.
Despite not wishing you to have this trouble, I am somewhat relieved that the issue I am having is repeatable with another user. My issue sounds exactly like yours, and how you describe the boot process failing "right before the final shift into the progress bar" is exactly my experience. (also the verbose mode is very quick and on my 4k monitor the text is barely readable if videoed!).

To give you some context, I originally ran Catalina with OC 0.6.6 very successfully (I think around 2 years ago) on this board. The BIOS back then was F9g, and I used the depreciated Unlock MSR Using Grub Shell with success.

Then last year I updated to Big Sur on OC 0.7.4, keeping the BIOS at F9g. Everything still worked great, including Sidecar (using iMac19,1 profile).

I ran that system for a year (needed a stable build for work) and didn't decide to do any updates until recently (now the academic year is almost over). Over the last week I updated the BIOS to F9l (which is much better), and tested OC 0.7.9 - 0.8.1. When I discovered 0.8.0/0.8.1 not working, I queried it on this forum. Given 0.7.9 was working however, last night I tried installing Monterey on a separate SSD to my Big Sur drive. Despite one freeze during install (where I had to reset the computer), Monterey successfully installed. Everything appears to work fine as before, sleep/wake, Sidecar, airdrop and even that new feature in Monterey where you move the mouse over to the edge of the screen and it pops through into your iPad. As they say, it's like magic!!

Suffice to say, this build, thanks to Pastrychef, is very, very stable and reliable. Let's hope someone can get to the bottom of why the last two OC builds are not working.
 
Despite not wishing you to have this trouble, I am somewhat relieved that the issue I am having is repeatable with another user. My issue sounds exactly like yours, and how you describe the boot process failing "right before the final shift into the progress bar" is exactly my experience. (also the verbose mode is very quick and on my 4k monitor the text is barely readable if videoed!).

To give you some context, I originally ran Catalina with OC 0.6.6 very successfully (I think around 2 years ago) on this board. The BIOS back then was F9g, and I used the depreciated Unlock MSR Using Grub Shell with success.

Then last year I updated to Big Sur on OC 0.7.4, keeping the BIOS at F9g. Everything still worked great, including Sidecar (using iMac19,1 profile).

I ran that system for a year (needed a stable build for work) and didn't decide to do any updates until recently (now the academic year is almost over). Over the last week I updated the BIOS to F9l (which is much better), and tested OC 0.7.9 - 0.8.1. When I discovered 0.8.0/0.8.1 not working, I queried it on this forum. Given 0.7.9 was working however, last night I tried installing Monterey on a separate SSD to my Big Sur drive. Despite one freeze during install (where I had to reset the computer), Monterey successfully installed. Everything appears to work fine as before, sleep/wake, Sidecar, airdrop and even that new feature in Monterey where you move the mouse over to the edge of the screen and it pops through into your iPad. As they say, it's like magic!!

Suffice to say, this build, thanks to Pastrychef, is very, very stable and reliable. Let's hope someone can get to the bottom of why the last two OC builds are not working.
Based on your experience I built a Monterey install USB with a 0.7.9 EFI. The install went very smoothly with only a couple of reboots. I selected the installer drive option until the Monterey disk became available. After that, a copy of the 0.7.9 EFI was copied to the Monterey disk to make it bootable. Yeah!

As a test, I went back to my 'Install macOS Monterey' USB drive and switched it from 0.7.9 to to 0.8.1. That's the same EFI that was giving me problems earlier. Rebooted to the 0.8.1 install USB, selected the Monterey disk and it all worked.

On the Monterey disk, the 0.7.9 EFI was swapped with a 0.8.1 EFI. It boots up normally.

A few more tests need to be performed, but it seems as if 0.8.1 works when it's installed onto disk that's being used after a macOS install or on a disk that has a copy of macOS on it. My next test will be to see if a bare USB that only has 0.8.1 on it will let me boot properly. Well, the bare drive with 0.8.1 works with Monterey. More tests are needed.

OK - Conclusion:

My system has two drives:

a) BigSur with 0.7.9 EFI
b) Monterey with 0.8.1 EFI

Booting with 0.7.9 EFI: can run either OS version without issue
Booting with 0.8.1 EFI: only runs Monterey. It fails when trying to run BigSur.
 
Based on your experience I built a Monterey install USB with a 0.7.9 EFI. The install went very smoothly with only a couple of reboots. I selected the installer drive option until the Monterey disk became available. After that, a copy of the 0.7.9 EFI was copied to the Monterey disk to make it bootable. Yeah!

As a test, I went back to my 'Install macOS Monterey' USB drive and switched it from 0.7.9 to to 0.8.1. That's the same EFI that was giving me problems earlier. Rebooted to the 0.8.1 install USB, selected the Monterey disk and it all worked.

On the Monterey disk, the 0.7.9 EFI was swapped with a 0.8.1 EFI. It boots up normally.

A few more tests need to be performed, but it seems as if 0.8.1 works when it's installed onto disk that's being used after a macOS install or on a disk that has a copy of macOS on it. My next test will be to see if a bare USB that only has 0.8.1 on it will let me boot properly. Well, the bare drive with 0.8.1 works with Monterey. More tests are needed.

OK - Conclusion:

My system has two drives:

a) BigSur with 0.7.9 EFI
b) Monterey with 0.8.1 EFI

Booting with 0.7.9 EFI: can run either OS version without issue
Booting with 0.8.1 EFI: only runs Monterey. It fails when trying to run BigSur.
Wow!

That's really good to hear....I guess that's my evening decided then...!

I'll feedback when I've tried it.

What I really want to do is update my Big Sur install to Monterey...I wonder will 0.8.1 still work then. It looks like 0.8.1 has a problem with big Sur.


Btw, I know Pastry chef told me to forget about the Serialinit Debug line.... Did you get that error too and did you just delete that line from the config.plist file?

Anyone else have problems with OC 0.8.0 on a big Sur install?
 
Wow!

That's really good to hear....I guess that's my evening decided then...!

I'll feedback when I've tried it.

What I really want to do is update my Big Sur install to Monterey...I wonder will 0.8.1 still work then. It looks like 0.8.1 has a problem with big Sur.


Btw, I know Pastry chef told me to forget about the Serialinit Debug line.... Did you get that error too and did you just delete that live from the config.plist file?
run ocvalidiate on your config.plist

remove/add/amend as needed (check sample.plist) to sort out your errors
 
Wow!

That's really good to hear....I guess that's my evening decided then...!

I'll feedback when I've tried it.

What I really want to do is update my Big Sur install to Monterey...I wonder will 0.8.1 still work then. It looks like 0.8.1 has a problem with big Sur.


Btw, I know Pastry chef told me to forget about the Serialinit Debug line.... Did you get that error too and did you just delete that line from the config.plist file?

Anyone else have problems with OC 0.8.0 on a big Sur install?
Yep,

Just tried 0.8.1 with my Monterey install. Worked grand. Only thing I seem to be getting is the dialog box at boot which says your Mac did not shut down properly. Not sure why that is, but it's not that much of an issue. Thanks for your investigative work QuantumDog!
 
Yep,

Just tried 0.8.1 with my Monterey install. Worked grand. Only thing I seem to be getting is the dialog box at boot which says your Mac did not shut down properly. Not sure why that is, but it's not that much of an issue. Thanks for your investigative work QuantumDog!
navigate to Library/Logs folder and delete any files in there relating to Sleepwake, empty trash and reboot
 
Thanks. The Reset nvram button is no longer there in 0.8.1.
read my reply above

also:
new way of adding reset nvram
 
Back
Top