Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[jimbojingle]

Thanks Casey, that worked great for me.

Can you confirm that Apple TV does not work with iMac 19,1 but does work with iMac 1,1 or is there another fix?

Please see this at the top of Post 1:


View attachment 552277

Thanks, Casey.

That worked for me. I have Ventura Public Beta running.

Is there a fix for Apple TV not working properly? I had to change my Monterey build to iMacPro 1,1 but not sure if that is the recommended fix.

Cheers

 

[CaseySJ]

Thanks Casey, that worked great for me.

Can you confirm that Apple TV does not work with iMac 19,1 but does work with iMac 1,1 or is there another fix?

Thanks, Casey.

That worked for me. I have Ventura Beta running.

Is there a fix for Apple TV not working properly? I had to change my Monterey build to iMacPro 1,1 but not sure if that is the recommended fix.

Cheers

Glad to hear it. You are correct about needing iMacPro1,1 or MacPro7,1 for AppleTV. Please see:

WhateverGreen/FAQ.Chart.md at master · acidanthera/WhateverGreen

Various patches necessary for certain ATI/AMD/Intel/Nvidia GPUs - WhateverGreen/FAQ.Chart.md at master · acidanthera/WhateverGreen

github.com

 

[R-88]

Hi CaseySJ,

I found a way to get back to the old BIOS F20 But the issue still persist plus I got another issue as you know we have two LAN on this motherboard (Intel 219 & 225) when I was on the BIOS screen I found both got the same Physical MAC address. It's really weird . I went back to Windows 11 and the same situation - one same Mac address for both Intel LAN (Intel 219 & 225). I don't how I can fix that, too. So I had to update back again to F21 to see if it will be resolved but it didn't. Still same issues plus this new issue.

View attachment 541195
View attachment 541196

View attachment 541197

View attachment 541198

Hi mishealgouhar,
I also have the Z490 Vision D and I have the same problem with the Mac address of the two LAN cards, that is, they have the same MAC address in the BIOS, in fact even on Windows 11 I can use them one at a time .... You have solved this problem simply flashing the previous version of the BIOS? I currently have the F21. Let me know please.

 

[jimbojingle]

Glad to hear it. You are correct about needing iMacPro1,1 or MacPro7,1 for AppleTV. Please see:

WhateverGreen/FAQ.Chart.md at master · acidanthera/WhateverGreen

Various patches necessary for certain ATI/AMD/Intel/Nvidia GPUs - WhateverGreen/FAQ.Chart.md at master · acidanthera/WhateverGreen

github.com

View attachment 552317

Thanks for confirming and for the useful information provided.

 

[CaseySJ]

** OpenCore 0.8.3 was released 12 hours ago. **
HackinDROM should be able to perform the upgrade.​

 

[Lensjocky]

** OpenCore 0.8.3 was released 12 hours ago. **
HackinDROM should be able to perform the upgrade.​

HackinDROM should and did! Safety updated & booted into 0.8.3 with no drama.

 

[bricknewer]

Hi Casey,

I just tried upgrading from OC 0.6.6 to 0.8.2 using your mini guide. When booting, none of my APFS volumes appeared in OC. After adding ApfsDriverLoader.efi I was able to see my boot volume again. As far as I understand aren't APFS drivers included in OpenCore already? Any idea why I would now need to add this driver after upgrading to OC 0.8.2?

Additionally, after updating OC to 0.8.2, HackinDROM seems to think my system is still using OC 0.6.6, while it shows OC 0.8.2 next to my install volume. Pictures attached for clarity.

Trying to make sure things are solid and not too janky before upgrading from Catalina to Monterey so I can use my 6600 XT.

Thank you!

 

[Feartech]

Hi Casey,

I just tried upgrading from OC 0.6.6 to 0.8.2 using your mini guide. When booting, none of my APFS volumes appeared in OC. After adding ApfsDriverLoader.efi I was able to see my boot volume again. As far as I understand aren't APFS drivers included in OpenCore already? Any idea why I would now need to add this driver after upgrading to OC 0.8.2?

Additionally, after updating OC to 0.8.2, HackinDROM seems to think my system is still using OC 0.6.6, while it shows OC 0.8.2 next to my install volume. Pictures attached for clarity.

Trying to make sure things are solid and not too janky before upgrading from Catalina to Monterey so I can use my 6600 XT.

Thank you!

if you set the following:

<key>MinDate</key>
            <integer>-1</integer>
            <key>MinVersion</key>
            <integer>-1</integer>

that will be fine for Catalina

remove ApfsDriverLoader.efi

 

[CaseySJ]

Hi Casey,

I just tried upgrading from OC 0.6.6 to 0.8.2 using your mini guide. When booting, none of my APFS volumes appeared in OC. After adding ApfsDriverLoader.efi I was able to see my boot volume again. As far as I understand aren't APFS drivers included in OpenCore already? Any idea why I would now need to add this driver after upgrading to OC 0.8.2?

Additionally, after updating OC to 0.8.2, HackinDROM seems to think my system is still using OC 0.6.6, while it shows OC 0.8.2 next to my install volume. Pictures attached for clarity.

Trying to make sure things are solid and not too janky before upgrading from Catalina to Monterey so I can use my 6600 XT.

Thank you!

Hello @bricknewer,

Because you're upgrading from a particularly old version of OpenCore, it's quite possible that the NVRAM section in your original config.plist is missing some configuration parameters. HackinDROM does not modify those parameters; it simply carries those settings forward.

If you can make a copy of your 0.8.3 config.plist, remove serial numbers from PlatformInfo --> DataHub section, and post that file, I can take a look.

 

[bricknewer]

if you set the following:

<key>MinDate</key>
            <integer>-1</integer>
            <key>MinVersion</key>
            <integer>-1</integer>

that will be fine for Catalina

remove ApfsDriverLoader.efi

This worked! Thank you! You mentioned it'll be fine for Catalina, but are these settings okay for Monterey?

Hello @bricknewer,

Because you're upgrading from a particularly old version of OpenCore, it's quite possible that the NVRAM section in your original config.plist is missing some configuration parameters. HackinDROM does not modify those parameters; it simply carries those settings forward.

If you can make a copy of your 0.8.3 config.plist, remove serial numbers from PlatformInfo --> DataHub section, and post that file, I can take a look.

Attached, thank you! The config.plist file is from before making the changes suggested by Feartech above, btw.