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

[CaseySJ]

I tried it and the problem remains.

Is the Keychron connected via USB cable? There may also be a firmware update for this keyboard that is worth considering (from the keychron website). Not sure what else to suggest.

Also:
1)i'm on Monterey 12.3.1 and i deleted the SmallTree-Intel-211-82576 kext and removed it from the config.plist but the problem also remains when i tried to use the i211 ethernet (black screen and reboot).

Is AppleVTD enabled? If it is, AppleVTD will appear near the top of the device tree in IORegistryExplorer. In Big Sur and Monterey several drivers now require AppleVTD.

2)I also have Linux as a boot should i enable OpenLinuxBoot.efi or make any other changes for some reason?

Not necessary.

 

[cheliocentric]

Change SecureBootModel to Disabled:

Change SecureBootModel to Disabled:
View attachment 546907

One step further! Now the Apple-Logo appeared and after 30minutes it's still there.

 

[speedfreak990]

Is the Keychron connected via USB cable? There may also be a firmware update for this keyboard that is worth considering (from the keychron website). Not sure what else to suggest.


Is AppleVTD enabled? If it is, AppleVTD will appear near the top of the device tree in IORegistryExplorer. In Big Sur and Monterey several drivers now require AppleVTD.


Not necessary.

1)A keyboard firmware update did the job and now working as it should.
2)No it wasn't.I enabled VT-d in the BIOS and now i219 is working natively as a charm.

You really helped me!

One last thing when i log in in the Monterey the desktop icons appear first with black background and a small loading animation in the center for 1-2 seconds and then it shows the default background image.Do you have in mind why it does that?

 

[CaseySJ]

One step further! Now the Apple-Logo appeared and after 30minutes it's still there.

Because you have a Vega GPU, the boot argument agdpmod=pikera should be removed from NVRAM boot-args.

Also enable verbose mode from OpenCore boot picker to see where the boot process stops.

 

[cheliocentric]

Because you have a Vega GPU, the boot argument agdpmod=pikera should be removed from NVRAM boot-args.

Also enable verbose mode from OpenCore boot picker to see where the boot process stops.

I Manually deleted the Argument from NVRAM boot-args and now i get this: (Image below)

Heres's my EFI

 

[Feartech]

I Manually deleted the Argument from NVRAM boot-args and now i get this: (Image below)

Heres's my EFI

do you have FakeSMC,kext in /L/E folder?

 

[CaseySJ]

I Manually deleted the Argument from NVRAM boot-args and now i get this: (Image below)

Heres's my EFI

do you have FakeSMC,kext in /L/E folder?

@cheliocentric

If you were using Clover before, please boot back using Clover and follow steps 2 and 3 of this post:

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

The Hackintosh plugins are all in the OpenCore 0.6.2 update zip that CaseySJ made or you can just download them individually on Github. I have reinstalled fxfactorty version 7.1.7.. the spinning ball issue is still there in fcp title tab and sometimes in os also..it is annoying. Clover is my...

www.tonymacx86.com

If this is a brand new installation with OpenCore, we shouldn’t be using FakeSMC.

 

[cheliocentric]

@cheliocentric

If you were using Clover before, please boot back using Clover and follow steps 2 and 3 of this post:

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

The Hackintosh plugins are all in the OpenCore 0.6.2 update zip that CaseySJ made or you can just download them individually on Github. I have reinstalled fxfactorty version 7.1.7.. the spinning ball issue is still there in fcp title tab and sometimes in os also..it is annoying. Clover is my...

www.tonymacx86.com

If this is a brand new installation with OpenCore, we shouldn’t be using FakeSMC.

I followed the steps and I'm able to boot into Mojave via OpenCore now - it worked!

The system seems stable and all of my periphery works as usual.

Should I implement the EFI now into the Big Sur USB Install Disk and run it via the OpenCore-Picker?

 

[CaseySJ]

I followed the steps and I'm able to boot into Mojave via OpenCore now - it worked!

The system seems stable and all of my periphery works as usual.

Glad to hear it.

Should I implement the EFI now into the Big Sur USB Install Disk and run it via the OpenCore-Picker?

Installing Big Sur was the original problem so yes, please give this a try now.

 

[cheliocentric]

Glad to hear it.


Installing Big Sur was the original problem so yes, please give this a try now.

I mounted the Install-USB-flashdisk, implemented my EFI into it and booted from it in OpenCore.

Then this happened: (Image below)

it's stuck