Gigabyte Z390 M Gaming build with working NVRAM

[pastrychef]

12-12

I recently killed my original LGA1156 build but am now back up and running thanks to your thread! So far everything is working perfectly, but similarly to this post, the "Processor" and "Graphics" info is incorrect in the "System Information" and "System Report" windows. Processor should be 3.6 Ghz 8-Core Intel Core i7 and Graphics should be Sapphire Pulse RX 570 4 GB. GeekBench 5 shows the correct CPU information but lists GPU as ???, although it does list the Compute Device correctly.

I know that the "System Report" can be edited as described in your subsequent post, but I was wondering if you had since learned if this could be corrected without having to edit the "System Report" window?

I am using your "EFI Clover r5126 Z390M v4" EFI folder and am running Catalina 10.15.7. I took the supplied config.plist from your EFI folder and used Clover Configurator to generate a unique Serial, Board Serial, and SmUUID.

Thanks again for helping to get my Hack back up and running!

Bruno

Please see post #3. Follow instructions on "How to populate System Information > PCI" to fix your graphics card identification.

I don't know why it's identifying your CPU incorrectly.

 

[gotoh]

12-12


Please see post #3. Follow instructions on "How to populate System Information > PCI" to fix your graphics card identification.

I don't know why it's identifying your CPU incorrectly.

I had the same issue with Clover for my MSI RX 580 and I thought it was time to switch from clover to OpenCore.
The file you posted for the latest OpenCore did the trick and so far it's working perfectly !
Thanks a lot Pastrychef

 

[Mr.-T-from-B]

I do need some help. I used pastrychefs opencore EFI (0.6.3 v2) folder to test, if this would work with my Catalina installation. I changed all the post install parameters to my meet my computers, put the EFI folder on an USB stick and launched my install from the USB stick. Everything booted fine.

I had some issues with the USB ports (USB 2.0 receiver for the keyboard did not work in the standard port anymore) and the Fenvi Bluetooth / Wifi Card (Broadcom BCM94360) did not work at all. So I decided to go back to Clover and restart Catalina.

Since I did that the LAN and WiFi is not properly working. Anything locally works and some sites on the Internet. Luckily tonymac86.com still works . However when I open e.g. Apple.com or Google.com I am getting an Error: ""Error code: SSL_ERROR_RX_RECORD_TOO_LONG" in Firefox or a similar one in any other browser.

Resetting the NVRAM did not help. The weird thing is that, when I start Windows, I have the same problem now.

My impression is that the MAC address of the Ethernet adapter got somehow corrupted. However, the MAC address showing in the systemreport is still the old one. My Router does show this one as well, but the computer gets blocked by the router after a while which can happen only, if the MAC address is not known. Still the Router does not show a new unknown device.

Did anybody experience something similar while testing opencore? Any idea how I can fix this?

Thanks in advance!

Mr T. from B.

 

[rbellonmartinez]

After several macbook pro's, I have assembled my first hackintosh...

Following the opencore installation guide, I've got no problems. Thanks to this thread, I managed to improve the setup. Wow!

Thanks for the info!!!

 

[ibruno]

12-12


Please see post #3. Follow instructions on "How to populate System Information > PCI" to fix your graphics card identification.

I don't know why it's identifying your CPU incorrectly.

Thanks so much for the reply! I'll go try that right now.

One more question; my main HDD is an NVMe 970 EVO, and I also have a SATA 860 EVO (P0) and SATA 840 EVO (P1) connected as well.

To help troubleshoot I would like to boot into the SATA drives at the Clover Startup Screen. However every time I reboot, I never get to the Clover Boot Screen; I go straight to the Apple Logo. It's great that it's that fast, but it would help to troubleshoot if I could get into the other drives. I've tried changing the boot order in BIOS and changed the timeout to -1 in config.plist, but my hack always boots into the NVMe 970, even though the other two SATA drives are bootable clones with working EFI folders. I know they work because if I physically remove the NVMe 970, I can boot into the Clover Boot Menu and have access to the SATA drives.

What can I do to stop from booting straight into the Apple logo and pause at the Clover Boot Screen?

Thanks again,

Bruno

 

[pastrychef]

I do need some help. I used pastrychefs opencore EFI (0.6.3 v2) folder to test, if this would work with my Catalina installation. I changed all the post install parameters to my meet my computers, put the EFI folder on an USB stick and launched my install from the USB stick. Everything booted fine.

I had some issues with the USB ports (USB 2.0 receiver for the keyboard did not work in the standard port anymore) and the Fenvi Bluetooth / Wifi Card (Broadcom BCM94360) did not work at all. So I decided to go back to Clover and restart Catalina.

Since I did that the LAN and WiFi is not properly working. Anything locally works and some sites on the Internet. Luckily tonymac86.com still works . However when I open e.g. Apple.com or Google.com I am getting an Error: ""Error code: SSL_ERROR_RX_RECORD_TOO_LONG" in Firefox or a similar one in any other browser.

Resetting the NVRAM did not help. The weird thing is that, when I start Windows, I have the same problem now.

My impression is that the MAC address of the Ethernet adapter got somehow corrupted. However, the MAC address showing in the systemreport is still the old one. My Router does show this one as well, but the computer gets blocked by the router after a while which can happen only, if the MAC address is not known. Still the Router does not show a new unknown device.

Did anybody experience something similar while testing opencore? Any idea how I can fix this?

Thanks in advance!

Mr T. from B.

OpenCore should not affect your browsers, especially your Windows browsers. Something else is messing your system up.

The reason why you had issues with USB is because your motherboard is different. You will need to create your own USB ports kext for your motherboard and replace mine.

The New Beginner's Guide to USB Port Configuration

Important Update: June 2023 From Big Sur 11.3 on the built-in OpenCore XhciPortLimit quirk no-longer worked as described. This became a known "bug", though in reality it was Apple changing their internal code, making a simple "peek and poke" to keep it operating, a difficult task. However, with...

www.tonymacx86.com

 

[pastrychef]

Thanks so much for the reply! I'll go try that right now.

One more question; my main HDD is an NVMe 970 EVO, and I also have a SATA 860 EVO (P0) and SATA 840 EVO (P1) connected as well.

To help troubleshoot I would like to boot into the SATA drives at the Clover Startup Screen. However every time I reboot, I never get to the Clover Boot Screen; I go straight to the Apple Logo. It's great that it's that fast, but it would help to troubleshoot if I could get into the other drives. I've tried changing the boot order in BIOS and changed the timeout to -1 in config.plist, but my hack always boots into the NVMe 970, even though the other two SATA drives are bootable clones with working EFI folders. I know they work because if I physically remove the NVMe 970, I can boot into the Clover Boot Menu and have access to the SATA drives.

What can I do to stop from booting straight into the Apple logo and pause at the Clover Boot Screen?

Thanks again,

Bruno

After powering up your system, seem the F12 key to get to the BIOS boot menu. Then select the drive that has your Clover EFI.

 

[tedyun]

The easy way is just download my OpenCore 0.6.3 EFI and grab the SSDT and kext and add it to your EFI. It should work OOB.

The default ACPI path should work for your motherboard, same as mine. Therefore, nothing to change in the code itself.

You can confirm by looking in IORegistryExplorer and compare with the .dsl file... Below, you can see in IORegistryExplorer shows /_SB/PCI0@0/XHC which is the same as \_SB.PCI0.XHC in MaciASL.
View attachment 495773
View attachment 495774



If you want to compile the .dsl file yourself, it's easy.

1. Open the .dsl file in MaciASL.
2. Go to the menu bar, click File and select Save As.
3. In the window that pops open, select File Format: ACPI Machine Language Binary and click save.
4. Done.

@pastrychef

Well -- I just went through Hell and back with this. After I tried the kext and SSDT, my rig stopped auto sleeping! I had this problem before during one of the betas, and after wracking my brain for a couple of weeks, I couldn't solve the problem. But it seemed to resolve after the next beta release, and it was fine even after the official release on Thu.

After I installed the kexts for the 1-button wake, my system couldn't auto-sleep anymore. It could command sleep and schedule sleep perfectly fine.

A fresh install of Catalina is fine, but when I upgrade that to Big Sur, the problem was back again. I cleared the CMOS and NVRAM, deleted the power settings multiple times.

Finally, I was poking around Hackintool and I noticed the disksleep was set to 10 min, and I was testing my system sleep at 5 min. So I set the disksleep at 4 min, and lo and behold, it auto-sleeps again! So for now, I think the disks have to power down before the system sleeps.

What is strange to me is that it was working fine, but then when I put in the kext and SSDT it seemed to break it.

Anyway, I was wondering if you could take a look at your settings for disksleep, displaysleep and sleep. And I'd be interested in your thoughts on this. I don't know why it is different in Big Sur. I don't know what I had disksleep set at before, but I've never played around with it.

Thanks!
Ted

 

[alittlesound]

Hello @pastrychef! You helped me get my computer up and running about 8 months ago on clover and I am looking to switch it over to open core, I downloaded the 0.6.3 v2 and made a duplicate of my system drive and put that on its efi but when I try to boot I just get the apple screen no loading bar and the fans shut off like nothing is happening. With your folder, since I am running the same mobo, same everything else should it be as simple as just adding that efi folder? Is there anything else I need to sort? I also could not figure out how to add -v from the open core picker screen and could not find anything online to tell me how so I could not see what it was stopping at (it stops pretty immediately). I updated the BIOS to F9L as well. Beyond that I am running the igpu on the 9900k so I believe some frame buffer edits need to be made as well - you were kind enough to give me the config.plist for the clover build that sorted that. I had hoped it was going to be as easy as swapping efi folders but nothing is easy with hackintoshes lol Any help is greatly appreciated

 

[pastrychef]

@pastrychef

Well -- I just went through Hell and back with this. After I tried the kext and SSDT, my rig stopped auto sleeping! I had this problem before during one of the betas, and after wracking my brain for a couple of weeks, I couldn't solve the problem. But it seemed to resolve after the next beta release, and it was fine even after the official release on Thu.

After I installed the kexts for the 1-button wake, my system couldn't auto-sleep anymore. It could command sleep and schedule sleep perfectly fine.

A fresh install of Catalina is fine, but when I upgrade that to Big Sur, the problem was back again. I cleared the CMOS and NVRAM, deleted the power settings multiple times.

Finally, I was poking around Hackintool and I noticed the disksleep was set to 10 min, and I was testing my system sleep at 5 min. So I set the disksleep at 4 min, and lo and behold, it auto-sleeps again! So for now, I think the disks have to power down before the system sleeps.

What is strange to me is that it was working fine, but then when I put in the kext and SSDT it seemed to break it.

Anyway, I was wondering if you could take a look at your settings for disksleep, displaysleep and sleep. And I'd be interested in your thoughts on this. I don't know why it is different in Big Sur. I don't know what I had disksleep set at before, but I've never played around with it.

Thanks!
Ted

I never messed with that setting and have always left it at its default setting.


When you say the system doesn't auto-sleep, does the system even attempt to sleep and instantly wake up or does it never attempt to go to sleep at all?