AudioGod's Aorus Z390 Pro Patched DSDT Mini Guide and Discussion

[Tiem]

5 minutes ago, AudioGod said:

You could create a ssdt to block it off from macOS I guess or thinking about it you could block it in the device properties in the config possibly?

 

Looks like OC has the Kernel > Block Properties feature.

[AudioGod]

16 minutes ago, Tiem said:

Looks like OC has the Kernel > Block Properties feature.

Yes that’s what I’m talking about, plop it in there and I think it should block it.

 

also there’s a block in device properties too.

one of them should do the trick, I’ve never tried myself.

 

use hackintool and extract your devices to a plist and then open it and pull the WiFi from it and paste it into the blocked section under device properties in your Oc plist and restart. (If you try it let me know if it worked as it’s a complete guess from me there but that should do it)

 

 

@Tiem dont you just use the t919 in windows?

i have my onboard card disabled permanently and use my combo card for all os. It’s not bt5 but it’s fine and just works. I’m happy with that.  

Edited April 28, 2020 by AudioGod

[Tiem]

1 hour ago, AudioGod said:

use hackintool and extract your devices to a plist and then open it and pull the WiFi from it and paste it into the blocked section under device properties in your Oc plist and restart. (If you try it let me know if it worked as it’s a complete guess from me there but that should do it)

 

 

@Tiem dont you just use the t919 in windows?

i have my onboard card disabled permanently and use my combo card for all os. It’s not bt5 but it’s fine and just works. I’m happy with that.  

Ok, I'll give it a shot and let you know. I want to boot into macOS first with it enabled and see what happens. Maybe both can coexist.

 

The T919 is a POS. The connection is way too flakey. Ya it works. It does. But compared to a native Mac or even the Intel CNVi from what I'm seeing, it's overpriced garbage. Especially on the BT module. The native card on the z390 is night and day difference.

[AudioGod]

4 minutes ago, Tiem said:

Ok, I'll give it a shot and let you know. I want to boot into macOS first with it enabled and see what happens. Maybe both can coexist.

 

The T919 is a POS. The connection is way too flakey. Ya it works. It does. But compared to a native Mac or even the Intel CNVi from what I'm seeing, it's overpriced garbage. Especially on the BT module. The native card on the z390 is night and day difference.

As you already know I have never been a fan of the T919 or one to recommend it so yeah I totally get you there bud. 
 

good luck with your quest.  

[Tiem]

Just now, AudioGod said:

As you already know I have never been a fan of the T919 or one to recommend it so yeah I totally get you there bud. 
 

good luck with your quest.  

Ya with good reason. I wouldn't recommend it either. I cringe when I see it in every write-up. It's the go-to now. Wifi, get a T919 

[AudioGod]

Just now, Tiem said:

Ya with good reason. I wouldn't recommend it either. I cringe when I see it in every write-up. It's the go-to now. Wifi, get a T919 

I reckon that’s only because it’s easy to get hold of anywhere on amazon or Ali Barbara around the world so I think it’s more down to a lack of choice there really. I god dam hope that’s the reason anyway...lol

[Tiem]

8 minutes ago, AudioGod said:

I reckon that’s only because it’s easy to get hold of anywhere on amazon or Ali Barbara around the world so I think it’s more down to a lack of choice there really. I god dam hope that’s the reason anyway...lol

Ya maybe. It's a dead simple solution, just a {censored} one.

 

So ya, no issues booting with Wifi enabled in the BIOS. macOS doesn't even see the onboard CNVi chip anyway.

[kiko89]

Hi guys!

 

I changed from clover to opencore and took advantage to install 10.15.3 because i think 10.15.4 isn't a good update (for me problem with NVME despite nvmefix kext and problem with BT of fenvi, so i'll wait 10.15.5).

I have only one problem: icloud keychain doesn't work.

I see only 20 password but i have about 420 password.

In the other clover hack with 10.15.4, no problem.

1. Do any of you know what the problem is?

2. Another question: is there any way to verify that MSR unlocked correctly? I ask this because despite having removed the motherboard battery before fresh install, I saw that the profile remained in bios memory.

 

Thank you so much

[AudioGod]

26 minutes ago, kiko89 said:

Hi guys!

 

I changed from clover to opencore and took advantage to install 10.15.3 because i think 10.15.4 isn't a good update (for me problem with NVME despite nvmefix kext and problem with BT of fenvi, so i'll wait 10.15.5).

I have only one problem: icloud keychain doesn't work.

I see only 20 password but i have about 420 password.

In the other clover hack with 10.15.4, no problem.

1. Do any of you know what the problem is?

2. Another question: is there any way to verify that MSR unlocked correctly? I ask this because despite having removed the motherboard battery before fresh install, I saw that the profile remained in bios memory.

 

Thank you so much

Sign out of your icloud and back in again and make sure your keychain selected in iCloud and it should see them. If it doesn’t then no idea I’m afraid as it has nothing to do with any revision of macOS or any of my EFIs.

 

if you saved the profile to the motherboard so you can load it back in anytime you want it will always be there Even if you pull the battery. But if you didn’t save it as a profile then you either didn’t remove the battery for long enough or left the mains power in there. That’s the only possible reasons for all of the above,

 

i hope that helps buddy and more thing, what you said about 10.15.4 is also pure nonsense sorry lol

Edited April 29, 2020 by AudioGod

[kiko89]

8 minutes ago, AudioGod said:

Sign out of your icloud and back in again and make sure your keychain selected in iCloud and it should see them. If it doesn’t then no idea I’m afraid as it has nothing to do with any revision of macOS or any of my EFIs.

 

if you saved the profile to the motherboard so you can load it back in anytime you want it will always be there Even if you pull the battery. But if you didn’t save it as a profile then you either didn’t remove the battery for long enough or left the mains power in there. That’s the only possible reasons for all of the above,

i hope that helps and what you said about 10.15.4 is also pure nonsense sorry lol

Ok i'll try to sign out and sign in but i think it depends on 10.15.3 because no problem with 10.15.4. 

Anyway I will do without the keychain because I want to understand if with 10.15.3 I no longer have problems with the NVME and BT. I didn't have these problems before doing the update 10.15.4 (I read that real macs also have problems with this version).

I understand that in your case the 10.15.4 didn't give you any problems, but in 1/2 week I can tell you if I am right in saying that 10.15.4 isn't a good update.

If it goes well, I'll update to 10.15.4 with hope of no longer having problems.

I'm using yours OC 0.5.7 EFI if it seems to be going really well! You are the BEST! 

[AudioGod]

5 minutes ago, kiko89 said:

Ok i'll try to sign out and sign in but i think it depends on 10.15.3 because no problem with 10.15.4. 

Anyway I will do without the keychain because I want to understand if with 10.15.3 I no longer have problems with the NVME and BT. I didn't have these problems before doing the update 10.15.4 (I read that real macs also have problems with this version).

I understand that in your case the 10.15.4 didn't give you any problems, but in 1/2 week I can tell you if I am right in saying that 10.15.4 isn't a good update.

If it goes well, I'll update to 10.15.4 with hope of no longer having problems.

I'm using yours OC 0.5.7 EFI if it seems to be going really well! You are the BEST! 

Awesome bro you enjoy.

Every revision has it faults and that’s why new ones come along but believe me everybody on here bar the Mojave users are all on 10.15.4 and nobody’s complaining here I’m afraid.

[n19htz]

Anybody ever had or could get a guess of why my ALL usb stop working after some hours of computer work (~48hrs), its just stops to work causing my input divices to freeze. But the computer itself continue to work just normally, I can even connect to it via ssh and do staff as normally as I would. Before that everyhting works just completely fine. My system is Aourus Pro (without wifi), i5 9600K, Radeon RX 580 8 GB Armor, RAM 32 GB 2666, SSD NVMe Samsung 970 Pro  512GB.

Any help would be appreciated.

[AudioGod]

8 minutes ago, n19htz said:

Anybody ever had or could get a guess of why my ALL usb stop working after some hours of computer work (~48hrs), its just stops to work causing my input divices to freeze. But the computer itself continue to work just normally, I can even connect to it via ssh and do staff as normally as I would. Before that everyhting works just completely fine. My system is Aourus Pro (without wifi), i5 9600K, Radeon RX 580 8 GB Armor, RAM 32 GB 2666, SSD NVMe Samsung 970 Pro  512GB.

Any help would be appreciated.

ahha yes indeed I can explain this to you.

Its the bios unfortunately. Myself, @texem and @WizeMan have been looking into this problem for a month or so now and it happens in windows too so I discovered only yesterday,

I have written to the gigabyte engineers about it already and I’m waiting to hear back from them and see what they say but there’s no fix and it’s totally random, it may happen after a few hours or even after a few weeks,

there’s nothing at all any of us can do to fix it unfortunately, it’s down to gigabyte now.

only happens with the pro board and not the master and I’m not sure if the WiFi variant or the pro is effected by it too. 
If a bios fix is created I shall post it up on here straight away,

Its not the biggest of deals though as it’s very infrequent and totally random so don’t stress yourself over it as it’s not your hacks fault.  

Edited April 29, 2020 by AudioGod

[n19htz]

6 minutes ago, AudioGod said:

ahha yes indeed I can explain this to you.

Its the bios unfortunately. Myself, @texem and @WizeMan have been looking into this problem for a month or so now and it happens in windows too so I discovered only yesterday,

I have written to the gigabyte engineers about it already and I’m waiting to hear back from them and see what they say but there’s no fix and it’s totally random, it may happen after a few hours or even after a few weeks,

there’s nothing at all any of us can do to fix it unfortunately, it’s down to gigabyte now.

only happens with the pro board and not the master and I’m not sure if the WiFi variant or the pro is effected by it too. 
If a bios fix is created I shall post it up on here straight away,

Its not the biggest of deals though as it’s very infrequent and totally random so don’t stress yourself over it as it’s not your hacks fault.  

 

Thanks for the quick response. I getting this freeze with constant basis on about 48hrs. Reboot resets the timer. Maybe consequence I don't know

[Alex1982]

Hi @AudioGod,I switched from Clover to OC using your OC EFI OC 057 Z390 Pro EFI 19,1 060420.zip - OpenCore v0.5.7, SMBios iMac19,1 (06/04/20). All things seems to be running smooth except one issue with Windows multi-boot: I unable to set Windows startup disk from macOS "Startup Disk" tool. I able to see and select Windows option in UI, but when I press "Restart" button I got the error: "The bless tool was unable to set the current boot disk"(please look at attached snapshots). Windows installed on separate SSD formatted as GPT for UEFI booting. EFI partition present on Windows disk. I already reset NVRAM after switching to OC. All other multi-boot stuff seems to be working fine:

1. I able to set macOS as startup disk in macOS "Startup Disk" tool

2. I can boot into Windows or macOS via OC boot picker without issues

3. From Windows BootCamp tool I can set macOS or Windows as startup disk without issues and OC boot selected OS

 

So the issue happens only when trying to set Windows as startup disk from macOS "Startup Disk" tool. It is quite annoying because the only way to set Windows as default OS for booting is manually select it first in OC boot picker, and after that set Windows as startup disk via Windows BootCamp tool. Under Clover I don't observe this issue.

[AudioGod]

2 minutes ago, AlexeyNikitin said:

Hi @AudioGod,I switched from Clover to OC using your OC EFI OC 057 Z390 Pro EFI 19,1 060420.zip - OpenCore v0.5.7, SMBios iMac19,1 (06/04/20). All things seems to be running smooth except one issue with Windows multi-boot: I unable to set Windows startup disk from macOS "Startup Disk" tool. I able to see and select Windows option in UI, but when I press "Restart" button I got the error: "The bless tool was unable to set the current boot disk"(please look at attached snapshots). Windows installed on separate SSD formatted as GPT for UEFI booting. EFI partition present on Windows disk. I already reset NVRAM after switching to OC. All other multi-boot stuff seems to be working fine:

1. I able to set macOS as startup disk in macOS "Startup Disk" tool

2. I can boot into Windows or macOS via OC boot picker without issues

3. From Windows BootCamp tool I can set macOS or Windows as startup disk without issues and OC boot selected OS

 

So the issue happens only when trying to set Windows as startup disk from macOS "Startup Disk" tool. It is quite annoying because the only way to set Windows as default OS for booting is manually select it first in OC boot picker, and after that set Windows as startup disk via Windows BootCamp tool. Under Clover I don't observe this issue.

Hmmmmm that’s strange, I personally always set it via the bootpicker myself. 
im not sure tbh if that’s a flaw in 0.5.7 or something else.

just tried it now and it worked for me but I’m testing 0.5.8 currently so it’s not a fair comparison.

il jump back to 0.5.7 in a little bit and see if it works for me and let you know straight away buddy.

 

is windows on it’s own disk?

[Alex1982]

@AudioGod, Yes, Windows installed on separate SSD formatted as GPT for UEFI booting

[AudioGod]

24 minutes ago, n19htz said:

 

Thanks for the quick response. I getting this freeze with constant basis on about 48hrs. Reboot resets the timer. Maybe consequence I don't know

Its  totally random and il tell you why I say that. I have only ever got it to happen once and only via windows, @texem has had it happen to him but only a few times so it’s very rare for him where as @WizeMan it happens more frequently but still in a random manor so it’s different for each user hence my term random. The latest beta bios even mentions it in the description but hasn’t fixed it.

 

3 minutes ago, AlexeyNikitin said:

@AudioGod, Yes, Windows installed on separate SSD formatted as GPT for UEFI booting

I shall try it on my end and report back to you my findings in the next 20 mins or so buddy. Won’t be long  

Edited April 29, 2020 by AudioGod

[Alex1982]

@eSaF, I waited enough time to Pin Wheel disappears but the issue is still here

[AudioGod]

1 minute ago, AlexeyNikitin said:

@eSaF, I waited enough time to Pin Wheel disappears but the issue is still here

Brb gonna try it now and find out, back in a mo

[AudioGod]

yep same for me here too. using 0.5.7 and 0.5.8 

No problems over here either 

hhhmmmmm

[WizeMan]

Do you have Paragon NTFS for Mac installed or something similar? The Bootcamp drive wasn't showing up at all at my hack and disabling Paragon NTFS fixed it. Maybe it's the same software causing issues to you @AlexeyNikitin

[Alex1982]

No, there are no such software installed. 

[Alex1982]

I just checked Windows disk with DiskUtility and it give me the next error:

This disk doesn’t contain an EFI system partition. If you want to start up your computer with this disk or include it in a RAID set, back up your data and partition this disk. : (-69767)
 

I run diskutil list and see that EFI partition present on Windows disk, but it is not on a first place(Windows Recovery partition on a first place): 

/dev/disk2 (internal, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                        *512.1 GB   disk2

   1:           Windows Recovery                         554.7 MB   disk2s1

   2:                        EFI EFI                     104.9 MB   disk2s2

   3:         Microsoft Reserved                         16.8 MB    disk2s3

   4:       Microsoft Basic Data Windows     

 

May be this is a cause of the issue?

[n19htz]

40 minutes ago, AudioGod said:

 

Its  totally random and il tell you why I say that. I have only ever got it to happen once and only via windows, @texem has had it happen to him but only a few times so it’s very rare for him where as @WizeMan it happens more frequently but still in a random manor so it’s different for each user hence my term random. The latest beta bios even mentions it in the description but hasn’t fixed it.

I wrote to gigabyte support about this problem as well. As myhackintosh is never goes off - the problem is very annoying  Anyway^ gonna post here when I get response from gigabyte.