Contribute
Register

Gigabyte Z390 M Gaming build with working NVRAM

Could it be power management?
The strangest thing that didn't happen in Mojave.
It is as if he went into sleep mode and never came back, but without having to "turn off" the system.
And to get back I have to turn off manually.

Do you get any kernel panic logs?

Please enter the following in Terminal and post the output:
Code:
pmset -g log | grep -i failure
 
Is there an issue in this build with wifi dropping its connection every few days? Once or twice a week the wifi says it has no network. Turning wifi off and on again clears it. Other things on the same wifi haven't dropped so I know it's not the wifi. (I can't rule out some sort of device interference though I haven't come up with anything). I have the very common Fenvi T919 PCiE card.

Update - this was just a router problem.
 
Last edited:
Is there an issue in this build with wifi dropping its connection every few days? Once or twice a week the wifi says it has no network. Turning wifi off and on again clears it. Other things on the same wifi haven't dropped so I know it's not the wifi. (I can't rule out some sort of device interference though I haven't come up with anything). I have the very common Fenvi T919 PCiE card.

I normally use Ethernet but I do have Wi-Fi enabled and connected to 5GHz 802.11ac for AirDrop. I have not noticed Wi-Fi connection dropping.
 
Is there an issue in this build with wifi dropping its connection every few days? Once or twice a week the wifi says it has no network. Turning wifi off and on again clears it. Other things on the same wifi haven't dropped so I know it's not the wifi. (I can't rule out some sort of device interference though I haven't come up with anything). I have the very common Fenvi T919 PCiE card.
This solved my wifi/handoff/mouse interference issues. Small cost but hugely effective

 
Hey, there! I followed your guide and used your config.plist for OpenCore 0.5.9 as a base (with some slight modifications...may or may not have screwed it up because of them, but I didn't change most of what was there, if anything...mainly only may have added a couple things, slight differences on kexts/drivers and put in my SMBIOS info), and I get this error at the bios splash screen. It's the Z390 M Gaming board. I've read about the data type 1 and 2 messages, but not this specific message. I'm trying to get OpenCore to recognize the NVMe drive I cloned from my Clover drive. The EFI on the NVMe drive is set up for OpenCore, with the same main partition as my Clover drive. If I boot through Clover, the drive shows up and boots fine (although slowly), even though it's an OpenCore EFI. But, if I try to give boot priority to the NVMe drive and boot through OpenCore, I get this error on the BIOS screen and the black OpenCore menu after doesn't list that drive, even though my Clover drives are listed.

"OCS: Failed to parse data field as value with type data and <qpWx3asni5u=> contents, context <ROM>"
 

Attachments

  • IMG_0083.JPG
    IMG_0083.JPG
    241.5 KB · Views: 45
Last edited:
Do you get any kernel panic logs?

Please enter the following in Terminal and post the output:
Code:
pmset -g log | grep -i failure
There was no Kernel Panic, and when I execute this command you entered, nothing appears.
 
Hey, there! I followed your guide and used your config.plist for OpenCore 0.5.9 as a base (with some slight modifications...may or may not have screwed it up because of them, but I didn't change most of what was there, if anything...mainly only may have added a couple things, slight differences on kexts/drivers and put in my SMBIOS info), and I get this error at the bios splash screen. It's the Z390 M Gaming board. I've read about the data type 1 and 2 messages, but not this specific message. I'm trying to get OpenCore to recognize the NVMe drive I cloned from my Clover drive. The EFI on the NVMe drive is set up for OpenCore, with the same main partition as my Clover drive. If I boot through Clover, the drive shows up and boots fine (although slowly), even though it's an OpenCore EFI. But, if I try to give boot priority to the NVMe drive and boot through OpenCore, I get this error on the BIOS screen and the black OpenCore menu after doesn't list that drive, even though my Clover drives are listed.

"OCS: Failed to parse data field as value with type data and <qpWx3asni5u=> contents, context <ROM>"

Please try with the default config.plist from my EFI. I think you messed up something in the config.plist.
 
There was no Kernel Panic, and when I execute this command you entered, nothing appears.

I don't know how to diagnose without any errors or kernel panics...
 
Please try with the default config.plist from my EFI. I think you messed up something in the config.plist.

Well, I didn't think that was it to begin with, but I went ahead and just straight up copied your efi with no modifications other than my smbios stuff and I turned off my internal graphics for good measure. I was using 19,1 and headerless igpu, but like I said, just went with everything your way. Selected boot priority to opencore, then the NVME drive I want to boot from, then other drives. Now instead of on the bios screen, i get that same error on its own black screen after that, and then the nice opencore boot screen appears. However, still no NVME drive. I can still see and boot it through clover though, so I guess worse comes to worse I can just keep doing that, but it seems kinda stupid. My only thought is that I screwed something up during the unlocking of the MSR, but I swear I followed your directions exactly.
 
The good news is, even with booting through clover, the system is blazing fast. Even faster than it was with my slightly modified settings under 19,1 so I feel like I'm getting closer, and probably will leave it like this on 1,1. Still no netflix in safari though lol. Not that I care that much. But I think my DRM gripe is never getting solved.
 
Back
Top