GIGABYTE GA-Z270X-Designare with Mojave 10.14.6

[BillieJo]

Maybe an idea to post a screengrab or list of the *efi files in the driverUEFI folder (or Drivers/UEFI).

OK.
Screen grab coming up as soon as I reboot the Hack.

Maybe an idea to post full Problem Reporting Files, if possible. That nothing we suggest works is a big surprise.

How do I post a Full Problem Reporting Files?

 

[BillieJo]

OK.
A few screen shots attached.
I read the post about Problem Reporting Files.
I downloaded it but it would not run.
Again, It sounds so simple but I'm probably doing something wrong.
I copied and pasted the command into the terminal.
Take a look....
What did I do wrong?

 

[BillieJo]

I tried it again.
I have no idea at all what I'm doing.
Where is the file?

 

[BillieJo]

OK.
If you thought editing audio wave forms was hard.

When do I press F4?
After I pick the HD to boot from?

 

[BillieJo]

I've rebooted this machine 3 times following the instructions in the terminal.
I've booted pressing F4 and I've booted pressing Fn+F4.
Running gen_debug gives me the same result.
I don't understand any of this and I need to stop for the evening and go spend time with the family.

 

[BillieJo]

@pastrychef @UtterDisbelief
I guess not being a real computer code person it seems funny that I didn't know F4 meant Boot in Safe Mode.
Not one to give up, I looked it up.
Files attached.

 

[BillieJo]

Here's another screen shot.

 

[BillieJo]

My brain is twitching.
While booting in safe mode I noticed one of the other boxes was ticked.
So searched and found the thread below. Now I'm sure this is completely unrelated to the problem I'm having but there are some notes that are strikingly familiar.

VESA mode through "nv_disable=1" also doesn't work for me. I've got a setup with the integrated graphics enabled (HD630), a primary AMD RX 580 and a secondary NV GTX 1070. Booting with either 14,2 or the more fitting 18,3 only results in a black screen.
Same IGPU, same graphics card, same SMBIOS.
Coincidence?
nv_disable=1 not forcing nvidia card into VESA mode in High Sierra Beta 5 (Clover +4152)

 

[UtterDisbelief]

My brain is twitching.
While booting in safe mode I noticed one of the other boxes was ticked.
So searched and found the thread below. Now I'm sure this is completely unrelated to the problem I'm having but there are some notes that are strikingly familiar.

VESA mode through "nv_disable=1" also doesn't work for me. I've got a setup with the integrated graphics enabled (HD630), a primary AMD RX 580 and a secondary NV GTX 1070. Booting with either 14,2 or the more fitting 18,3 only results in a black screen.
Same IGPU, same graphics card, same SMBIOS.
Coincidence?
nv_disable=1 not forcing nvidia card into VESA mode in High Sierra Beta 5 (Clover +4152)

Okay, thanks for the upload.

It tells us quite a lot - not the whole story because the Problem Reporting Files aren't complete - but something at least. There is no Clover folder tree or *.ioreg export file (only a text version).

So what we can see thus far probably won't cure your problems if we remedy them but ...

Let's start with kexts:

You should not have any third-party kexts - Lilu, Whatevergreen, AppleALC and USBInjectAll - in System/Library/Extensions. Remove them and rebuild your kext-caches with Terminal:

sudo kextcache -i /

You also have duplicates in Library/Extensions and EFI/CLOVER/kexts/Other - the trouble here is that they are not the same versions! Another big no-no.

You do not need GenericUSBXHCI.kext
You do not need XHC-unsupported.kext

You still have AptioMemoryFix-64.efi in place. Did you test with OsxAptioFix2Drv-64.efi?

Command-lines in place:
Boot args: dart=0 -alcbeta -lilubetaall keepsyms=1 -wegbeta -no_compat_check debug=0x100 -vsmcbeta -disablegfxfirmware . I would try with just: dart=0 then maybe add keepsyms=1 if there's no joy.

As for your question about the "nv_disable=1" command-line. This is only relevant to builders with a NVidia GPU. It keeps the card in VESA mode (or doesn't if it doesn't work etc) so that the web-drivers aren't loaded and potentially cause problems. For your RX580 this doesn't apply. Believe it or not your GPU is classed as just about 'native'.

 

[BillieJo]

@UtterDisbelief
OK. Before I do anything, Do I need to keep adding @... for you to see these posts?
When @pastrychef sent his last EFI folder, I unzipped it and moved it from the downloads folder to my desktop, where it still is.

Then I mounted the hidden EFI partition and deleted that EFI folder.
He asked me to change one text for another text, which I did and then put the newly modified folder into the EFI partition. It was copied over. I umounted (I'm using Clover Config to do this) the partition and rebooted.

Screen shot attached below.
You can see the OsxAptioFix2Drv-64.efi is in the folder not the AptioMemoryFix-64.efi.
So that confuses me.

Besides the 4799 folder, did any of those screen shots tell you anything else?

I will now TRY to fix things per your instructions above.