Contribute
Register

pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

Thanks for that update.
I've copied the UUID and serials, but (admitting my ignorance) I'm fuzzy on what you mean by "system definition" - is that somehow different from copying the whole of my SMBIOS and replacing yours?

System definition as in iMacPro1,1 or iMac19,1 or iMac18,3, etc.

Yes, copy your entire SMBIOS section and replace mine.
 
done. Also deleted your properties and added mine (all one of it), and ...
your USB is:
USB = {
AddClockID = YES;
FixOwnership = YES;
HighCurrent = YES;
Inject = NO;
};

whereas mine is
USB = {
FixOwnership = YES;
Inject = YES;
};

change to mine, or use yours?
 
done. Also deleted your properties and added mine (all one of it), and ...
your USB is:
USB = {
AddClockID = YES;
FixOwnership = YES;
HighCurrent = YES;
Inject = NO;
};

whereas mine is
USB = {
FixOwnership = YES;
Inject = YES;
};

change to mine, or use yours?

You can. It shouldn't matter too much either way...
 
OK... about to put in the altered config.plist and give it a go. Before I do, however, I'd like to ask about the "new NVRAM" you mentioned. I notice that your drivers do not include EmuVariableUefi.efi, which got installed when I chose the Clover with emulated pkg.
Comments?
 
OK... about to put in the altered config.plist and give it a go. Before I do, however, I'd like to ask about the "new NVRAM" you mentioned. I notice that your drivers do not include EmuVariableUefi.efi, which got installed when I chose the Clover with emulated pkg.
Comments?

If NVRAM is working, you don't need the NVRAM emulation driver...

If it all works, you should also uninstall the RC scripts.
 
OK... I gave the new config.plist a try. it got further than before. I got the famous series of purple lines on the vega card, but then, as it progressed further, the screen simply went black, and that was that. (Yeah, I should have verbosed it, but forgot...)
So I yanked it and rebooted to my Mojave Nvme, and discovered that the previous Catalina try managed to fully enable my SIP, which was off for Mojave. It took several reboots for the old config.plist to disable SIP again, and I'm now in the process of dealing with re-authorizing system extensions and getting myself back to normal.

Am I correct that SIP must be enabled for Catalina to run?

I can't test the NVRAM yet because I cannot yet boot into Catalina. I'm pretty sure this board does Not have native NVRAM...
 
OK... I gave the new config.plist a try. it got further than before. I got the famous series of purple lines on the vega card, but then, as it progressed further, the screen simply went black, and that was that. (Yeah, I should have verbosed it, but forgot...)
So I yanked it and rebooted to my Mojave Nvme, and discovered that the previous Catalina try managed to fully enable my SIP, which was off for Mojave. It took several reboots for the old config.plist to disable SIP again, and I'm now in the process of dealing with re-authorizing system extensions and getting myself back to normal.

Am I correct that SIP must be enabled for Catalina to run?

I can't test the NVRAM yet because I cannot yet boot into Catalina. I'm pretty sure this board does Not have native NVRAM...

SIP can be enabled or disabled. It's up to the user how they like their system. I've been leaving SIP enabled since Mojave.

The SIP setting is in your config.plist.

If you have hackintosh kexts in /Library/Extensions/, you need to delete them to use my EFIs. You should not be seeing purple lines. That was fixed long ago. It sounds like it may have booted in to Catalina but you just got black screen. Try unplugging and re-plugging your monitor cable from the video card.
 
Well, I'm 18 hours into trying to make this work, and I am going to have to give up and start all over again. No matter what I try to do, I either get the "prohibited" sign, or a progress bar that never seems to quit. Nothing I've tried works.

Can I use a UniBeast stick w/Catalina to install onto a drive that already has Mojave and many files on it?

If so, I'll try that. Then I'll probably wait for MultiBeast for Catalina.
 
Well, I'm 18 hours into trying to make this work, and am going to have to give up and start all over again. No matter what I try to do, I either get the "prohibited" sign, or a progress bar that never seems to quit. Nothing I've tried works.

Can I use a Unibeast stick w/Catalina to install onto a drive that already has Mojave and many files on it?

If so, I'll try that. Then I'll probably wait for MultiBeast for Catalina.

You should be able to use UniBeast.

Please provide verbose image to help diagnose the problem.
 
Hi again

You're a very patient human! :)

I have attached the verbose image, and the current EFI folder.

Here are the differences between my working Mojave and the troublesome Catalina:

---------Mojave boot (current setup):
drivers/uefi/
ApfsDriverLoader.efi
EmuVariableUefi.efi
FSInject.efi
HFSPlus.efi
OsxAptioFix2Drv-64.efi
SMCHelper.efi

kexts/other/
AppleALC.kext
FakeSMC_ACPISensors.kext
FakeSMC_CPUSensors.kext
FakeSMC_GPUSensors.kext
FakeSMC_LPCSensors.kext
FakeSMC.kext
IntelMausiEthernet.kext
Lilu.kext
USBPorts.kext
WhateverGreen.kext

acpi patched:
(empty)

config
Arguments = "dart=0 shikigva=16";


________________________________________________________________________

==========Catalina
drivers/uefi
ApfsDriverLoader.efi
AppleGenericInput.efi
AppleUiSupport.efi
FwRuntimeServices.efi
HFSPlus.efi
OcQuirks-4.efi
VirtualSmc.efi

kexts
AppleALC.kext
IntelMausiEthernet.kext
Lilu.kext
SATA-200-series-unsupported.kext
SMCProcessor.kext
SMCSuperIO.kext
USBPorts.kext
VirtualSMC.kext
VoodooPS2Controller.kext
WhateverGreen.kext

acpi patched:
SSDT-EC-USBX.aml
SSDT-Z390-RP05-SLOT4-TB3HP.aml

config:
Arguments = "-alcbeta -lilubetaall debug=0x100 keepsyms=1 -wegbeta -no_compat_check slide=0 -vsmcbeta";

device properties: removed
 

Attachments

  • IMG_2723.JPG
    IMG_2723.JPG
    1.1 MB · Views: 48
  • EFI.zip
    22.6 MB · Views: 67
Back
Top