Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

@CaseySJ @Marcet
Please test this one

For the "Create EFI" feature :

- If I select an different OpenCore version the buttons are dimmed as if they are disabled, but they're not (just cosmetics, but disturbing). Moreover, there is a lack of contrast between enabled / disabled buttons due to transparency which makes difficult to differentiate them on light background.

- When I click on "Format Disk and Create EFI" it works if I choose OpenCore 0.6.6 (which is actually installed on my system). But, If I choose the latest release, it doesn't work. The result is an empty EFI partition.

"Update to 0.6.7" :

- If I want to update my 0.6.6 newly created USB Key, the Boot Arguments are not right.
"keepsyms=1 dart=0 debug=0x100 agdpmod=pikera alcid=11 shikigva=80 igfxfw=2"

I should have "keepsyms=1 dart=0 debug=0x100 agdpmod=pikera alcid=11 shikigva=128" as I've disabled my internal graphics card. (That's strange because the arguments are good when I click to the computer icon on the main window.

After editing the boot parameters, the update process went fine on the USB key.
I cannot reboot now, but I will test that later.
 
Hi guys!

I finished a Big Sure OC 0.6.6. clean install with OC Designare guide. Everything is well but...I use two monitors and the first monitor resolution is 1080p, is ok but the second monitor is 720p.If I turn off the second monitor and turn on, the macos recognize the better resolution and both monitors works on 1080p. Why is that?

I use two monitors with my setup, both 2560x1440, connected via Display Port to the RX580, and they both go to native resolution once the system has booted. During the up (up until midway through booting in MacOS), the boot monitor is at 720p or so, then it switches to the proper resolution.

I believe (but haven't bothered to redo the setup to test it, I just had used the HDMI cable initially), that using a HDMI cable to a single monitor (didn't have multiple monitors going initially), it started up and stayed at 2560x1440, both in booting into OC, as well as throughout the MacOS boot process.

If you aren't connected via HDMI, you might consider using that to connect to the monitors.

On an semi-related note, the RX580 card also notices on the fly when I connect/disconnect a 3rd display (a 4k tv via hdmi), just like a Mac should (along with the monitors layouts/resolutions)...
 
I use two monitors with my setup, both 2560x1440, connected via Display Port to the RX580, and they both go to native resolution once the system has booted. During the up (up until midway through booting in MacOS), the boot monitor is at 720p or so, then it switches to the proper resolution.

I believe (but haven't bothered to redo the setup to test it, I just had used the HDMI cable initially), that using a HDMI cable to a single monitor (didn't have multiple monitors going initially), it started up and stayed at 2560x1440, both in booting into OC, as well as throughout the MacOS boot process.

If you aren't connected via HDMI, you might consider using that to connect to the monitors.

On an semi-related note, the RX580 card also notices on the fly when I connect/disconnect a 3rd display (a 4k tv via hdmi), just like a Mac should (along with the monitors layouts/resolutions)...
I use Displayport cables. But my old Mojave install is recognize well this config. The Big sure boot is working native resolution for both monitor (1080p). And the welcome screen is changed 1080p and 720p. I try the SwitchResX prog, but is's the same. Turn off and on the monitor, and the resolution is well.
 
- If I want to update my 0.6.6 newly created USB Key, the Boot Arguments are not right.
"keepsyms=1 dart=0 debug=0x100 agdpmod=pikera alcid=11 shikigva=80 igfxfw=2"

I should have "keepsyms=1 dart=0 debug=0x100 agdpmod=pikera alcid=11 shikigva=128" as I've disabled my internal graphics card. (That's strange because the arguments are good when I click to the computer icon on the main window.
Boot arguments, Serials are extracted from selected EFI partitions config.plist and not from the system, this allows you to update any EFI if you select the correct build from your settings.
I'll add an option to edit boot args before the creation of the EFI.

- If I select an different OpenCore version the buttons are dimmed as if they are disabled, but they're not (just cosmetics, but disturbing). Moreover, there is a lack of contrast between enabled / disabled buttons due to transparency which makes difficult to differentiate them on light background.
theres GUI issues, honestly I didn't spent so much time on GUI.
Will fix it!

- When I click on "Format Disk and Create EFI" it works if I choose OpenCore 0.6.6 (which is actually installed on my system). But, If I choose the latest release, it doesn't work. The result is an empty EFI partition.
Unfortunelty im not able to reproduce this, could you please describe exactly how you got it
Thanks for the feedback Marcet!
 
Unofficial (!): It seems that we get Big Navi support!:headbang:

"AMD Big Navi 6800/6900 XT support in Apple Metal driver should be already available in Mac Os 11.3 beta 3, so they should be supported in the upcoming 11.3 stable update."

https://render.otoy.com/forum/viewtopic.php?f=7&t=75411&start=600#p397502

Octane is known for its GPU rendering solutions, also on MacOS.
That's great, if it happens. Unfortunately it's almost impossible to buy any AMD GPU. No stock. Prices are eye-watering. When I bought my RX480 years ago, it was fairly pricey even second hand because of the mining craze. But now prices are even more ridiculous.

You can get a M1 MacMini for the price of a consumer's graphics card...
 
Boot arguments, Serials are extracted from selected EFI partitions config.plist and not from the system, this allows you to update any EFI if you select the correct build from your settings.
I'll add an option to edit boot args before the creation of the EFI.
I suggest adding a checkbox to select the boot args from the system if checked.
What do you think about it ?

theres GUI issues, honestly I didn't spent so much time on GUI.
Will fix it!
I can understand that. Features first.

Unfortunelty im not able to reproduce this, could you please describe exactly how you got it
Humm, that's embarrassing. I was not able to reproduce it either.
Sorry about that.

Thanks for the feedback Marcet!
No problem, this app is a huge benefit to the community !
 
Unofficial (!): It seems that we get Big Navi support!:headbang:

"AMD Big Navi 6800/6900 XT support in Apple Metal driver should be already available in Mac Os 11.3 beta 3, so they should be supported in the upcoming 11.3 stable update."

https://render.otoy.com/forum/viewtopic.php?f=7&t=75411&start=600#p397502

Octane is known for its GPU rendering solutions, also on MacOS.
In 11.3 beta 3, device ID 0x73BF still exists only in AMDRadeonX6000Framebuffer.kext, but not in others such as AMDRadeonX6000HWServices.kext.
 
I have this configuration running - very nice! THANK YOU.

I was wondering if this setup would support an 8k screen via DP (at 60Hz probably)?
 
@Inqnuam I've installed version 1.1.2 RC2. It doesn't see my Big Sur disk.
 

Attachments

  • Screenshot 2021-03-09 at 15.20.14.png
    Screenshot 2021-03-09 at 15.20.14.png
    44.7 KB · Views: 65
Back
Top