Ploddles

5 minutes ago, rressl said:

I created it like this:

 

sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume

 

and then mount it with MountEFI.command

That should work fine if your USB stick was called MyVolume. After it ran did its name change to Install Catalina or something similar? Did it complete without any errors? There is an App you can use as well which will halt on any errors. Try THIS

3 minutes ago, rressl said:

@Ploddles

 

Thanks for uploading your configuration.

 

Unfortunately it doesn't work for me and when I boot from the USB stick I only get the selection "CleanNvram.efi" and "ResetSystem.efi".

 

What could be the problem? (CSM and Above 4G decoding is disabled)

It sounds like you haven't created a Catalina USB install stick. If you have, how did you create it?

@rressl

As requested attached is my latest EFI. You will need to enter your own details for serial number etc in config.plist - where I have put "Your Info Here".

It is best to just write in the thread rather than PM, others may be able to help with your questions/comments.

This is by no means complete and is just a work in progress but hopefully it will get you going.

@Jaidy there are a few updates from the last one here, including a couple of Gigabyte Xtreme specific SSDTs, thanks to @iGPU for these.

EFI.zip

10 minutes ago, fabiosun said:

I have updated to latest oc debug

latest drivers and kext (061)

I have a reboot after OS X choice

ok

i put back my working EFI

now everytime i choose OS X it boots in recovery mode

i obviously select OS X to boot and not recovery mode

luckily proxmox OS X starts fine

i have tried t clean nvram but always the same

 

I had this a year or so ago on a Z390 Designare. Clearing the BIOS and redoing the settings was the only way I recovered from it without having to reinstall. A few times I have had to clear NVRAM 3 times in a row without trying to boot an OS inbetween to get it fully back to normal.

1 hour ago, iGPU said:

 

The schema errors appear when your using a mis-configured config.plist file for the particular version of OC. (In other words, you've probably kept the same config.plist file yet swapped out different OpenCore.efi files that now have different entries.)

 

Another common OC mistake is to update parts of the OC folder and forget to also update the BOOT folder. All parts of OC's EFI folder need to be of same commit (well, not ACPI or Kexts folders).

 

I don't include HiiDatabase.efi in GitHub site, so declaring this is config.plist and not having in Driver's folder will give a critical halt. Most of the driver's are not necessary, and I've excluded them from the Driver's folder on purpose.

Attached is the config file I used with 0.6.1 Debug version built on 12 August. Pretty much my current config with bits disabled. Various bits still need to be added/removed etc, I'm slowly going through it to clean it up for my MB.

Thanks for having a look.

config.plist.zip

On 8/16/2020 at 5:57 PM, iGPU said:

 

I'll lay out the steps I went through to derive the MmioWhitelist. But first I want to say that aside from the slide value of 128, I'd tried various OC combinations to obtain native NVRAM including using the new SSDT-NVRAM. None worked. Only when combining the Quirks reported above and MmioWhitelist and using the SSDT-TRX40-NVRAM did native NVRAM work on bare metal.

 

Steps for deriving MmioWhitelist (make certain that you have an alternative bootable EFI, as you'll see below):

 

 

A. MmioWhitelist Determination

 

1. Run OC debug version (≥ v059; even if you can't fully boot into macOS, you'll have sufficient data written out on the next boot with a non-debug, working version).

   

 a. debug OC settings (spoiler):

  Hide contents

 

 

I'm not having much luck with this.

It halts on a critical error and the saved file does not have the MMIO info in it. I've tried with 0.5.9, 0.6.0 and 0.6.1 debug versions. Tried with and without the SSDTs and with and without the kexts.

Any suggestions as to what I am doing wrong?

Thanks.

opencore-2020-08-22-153125.txt.zip

6 minutes ago, Jaidy said:

that worked! Thanks a lot. Would you be following up on @iGPU's suggestions to create an updated EFI? If so, would you please post it here?

Which bit worked, sound or keyboard?

I will be updating my EFI (on a separate USB drive for testing first) but it will probably take me a while. Once I have it done I'll let you know. 🙂

Firstly, I've installed Big Sur on an old MacBook, 13" mid 2014 - so not the fastest machine out there, with only 8GB ram!!, and will next create a CCC image on a USB HD to then CCC to another NVMe on the TRX. I can then validate the new EFI for both Catalina and BS on the Xtreme. At some point I'll also have another look at liquidctl to see if it will play nicely with the RGB. It has just been updated to better work with the latest Gigabyte MBs that support Fusion 2 (Windows). I'm not that fussed about RGB but if it is there then there is another challenge and I like the odd challenge. Having been retired for some time I must keep the old brain cells working - I do voluntary work with the Ambulance Service now to keep me busy during the day but need more than that, hence moving onto the TRX from the 3 Intel Hacks I have built so far.

Cor, that was quick. Thanks very much.

@iGPU please find attached requested IOReg file for the Gigabyte Xtreme motherboard. We also need a different network kext as we have dual intel 10GB chipset. The (modified)  kext is attached.

@Jaidy, sound for me is working. I have not tested the onboard headphone jacks etc as I use a Dell AC511 USB Soundbar (it matches my Dell monitors and is designed to clip onto one of them. You could try changing from alcid=1 to alcid=11 or alcid=16 in the boot-args of your config.plist file. My previous Gigabyte boards (Z370 Gaming Ultra, Z390 Designare and Z390 Master all worked with either 11 or 16.

As for your keyboard, have you tried going to System Preferences - Keyboard and clicking "Change Keyboard Type..." It should then get you to press a key or two to verify it. I don't use a trackpad so can suggest anything for that.

Gigabyte-Xtreme.zip SmallTreeIntel8259x.kext.zip

Big Sur Beta 5 has been posted, for those who want to give it a try.

@Jaidy I've just checked the USB on my key ring and I have a copy of my EFI on that - I think it is the latest but if not I believe it does work on our MBs.

Let me know if you try it and it doesn't but here it is anyway. As I said, it still needs optimising and some kexts etc removing.

EFI.zip

20 minutes ago, Jaidy said:

Hi all,

I am thrilled to know that macOS now boots bare metal on AMD TR3 systems. Is the procedure to install roughly making a Catalina (or BS USB), putting the EFI folder in the EFI partition of the USB, installing MacOS, and then putting the EFI folder in the EFI partition on the installation disk?

 

I have followed this thread, and there doesn’t seem to be any special BIOS settings. Is there anything I have missed?

I have exactly the same Motherboard, Processor and Graphics Card as you.

If you can wait until tomorrow I can upload my EFI for you, you'll just need to add your Serial No, UUID etc.

As it stands it is fine for installing and running Catalina but will not allow installation of Big Sur. No doubt it can be optimised for Catalina/Big Sur but it would give you a head start on getting things done.

In the BIOS you need to disable CSM, Virtualisation and Above 4G Decoding. I have XMP set to Profile 1. That could also be optimised but at least allows things to work for now. If I remember I will save the BIOS settings to a file you could load and attach it with the EFI.

Yeah, finally got bare metal Catalina installed. 😀

Turns out that it didn’t like having 2 graphics cards in the machine during install - with just the one it flew along nicely. After the install I put the other one back in just to check but it didn’t miss a heart beat. The 2nd card was an Nvidia 1050, which I know can’t be used in Catalina but was installed for Proxmox when I was trying to get that to work and passing through the RX580.

i have the usual restart issue that everyone else seems to have,  but have now seen the other SSTDs that @iGPU has shared and also a new config file that works with Catalina and Big Sur. I will have a play with those later in the week. I did try an install of BS (with my Catalina config file) but that just hangs after the first reboot.

If anybody wants my IOReg file to look at to compare between different motherboards just let me know, I have the Gigabyte Xtreme.

There are a lot of files floating about in this thread and it can be hard to keep an eye on what is what and remember to update as things are discovered and files are modified. Would it be a good idea to have somewhere, maybe a sticky post or section in the downloads section, where new/updated files can be upload/downloaded to save everybody jumping  around looking for things and trying to remember what each one if for, eg common SSDTs for all boards and then those specific to MSI, Gigabyte etc etc? Just an idea but could be a pain to administer depending on how it is done.

Anyway, thanks for your help guys, glad to be finally up and running. Now to try the Adobe fixes later this evening.

8 minutes ago, TheDantee said:

I know I'm trying to load High Sierra I tried the EFI and got PCi error removed the npci boot argument and does the same thing loading bar almost finishes and then computer reboots..

Ah, OK. Good luck, you have got further than me so far. 🙂

20 hours ago, tsongz said:

@Ploddles - so during my time trying to tweak RTC settings, I ran into almost all the standard, default, issues, even when trying to boot off of a working EFI (USB). What the root cause of the issue was for me, was the BIOS settings (which gets reset when I have to clear CMOS due to hard shutdowns). And this was after having a working Installation.

 

Here's a few things to try:

- Clear your CMOS (if you have the button option on your mobo, save your BIOS settings on a USB, or as profile, unplug from wall, clear it with the button, then load it or manually check them again)

- CSM Disabled/4G Encoding Enabled (4G Encoding was disabled which caused my PCI error)

- Clear/Reset NVRAM - reboot, before attempting reinstall. Some cache of it may be left behind from previous installs? I can't verify this.

- If you haven't already, do a full disk erase before installing

 

  Reveal hidden contents

 

RTC Attempt

 

What I tried that didn't work (all in one go, bad idea, I know): 

- Enabling RTCMemoryFixup.kext

- Adding -rtcfx_exclude=80-FF in boot-args

- Enabling AppleRtcMemory

- Adding "56 57" to NVRAM > rtc-blacklist

 

Adobe Fixup Script

 

Run Step 1 and then Step 2 below in Terminal. Last Script is in case something breaks

 

Step 1

for file in MMXCore FastCore TextModel libiomp5.dylib; do
    find /Applications/Adobe* -type f -name $file | while read -r FILE; do
        sudo -v
        echo "found $FILE"
        [[ ! -f ${FILE}.back ]] && sudo cp -f $FILE ${FILE}.back || sudo cp -f ${FILE}.back $FILE
        echo $FILE | grep libiomp5 >/dev/null
        if [[ $? == 0 ]]; then
            dir=$(dirname "$FILE")
            [[ ! -f ${HOME}/libiomp5.dylib ]] && cd $HOME && curl -sO https://excellmedia.dl.sourceforge.net/project/badgui2/libs/mac64/libiomp5.dylib
            echo -n "replacing " && sudo cp -vf ${HOME}/libiomp5.dylib $dir && echo
            rm -f ${HOME}/libiomp5.dylib
            continue
        fi
        echo $FILE | grep TextModel >/dev/null
        [[ $? == 0 ]] && echo "emptying $FILE" && sudo echo -n >$FILE && continue
        echo "patching $FILE \n"
        sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x6A\x00|\x90\x90\x90\x90\x56\xE8\x3A\x00|sg' $FILE
        sudo perl -i -pe 's|\x90\x90\x90\x90\x56\xE8\x4A\x00|\x90\x90\x90\x90\x56\xE8\x1A\x00|sg' $FILE
    done
done

 

Step 2

 

[ ! -d $HOME/Library/LaunchAgents ] && mkdir $HOME/Library/LaunchAgents
AGENT=$HOME/Library/LaunchAgents/environment.plist
sysctl -n machdep.cpu.brand_string | grep Ryzen >/dev/null 2>&1
x=$(echo $(($? != 0 ? 5 : 4)))
cat >$AGENT <<EOF
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>mkl-debug</string>
    <key>ProgramArguments</key>
    <array>
    <string>sh</string>
    <string>-c</string>
        <string>launchctl setenv MKL_DEBUG_CPU_TYPE $x;</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
</dict>
</plist>
EOF
launchctl load ${AGENT} >/dev/null 2>&1
launchctl start ${AGENT} >/dev/null 2>&1

# Reboot after this step and it should work now. Sigh. Have to hard reboot unfortunately for me.

## Revert the previous script in case you brick something

for file in MMXCore FastCore TextModel libiomp5.dylib; do
    find /Applications/Adobe* -type f -name $file | while read -r FILE; do
        sudo -v
        [[ -f ${FILE}.back ]] && echo "found backup $FILE" && sudo mv -f ${FILE}.back $FILE
    done
done

AGENT=$HOME/Library/LaunchAgents/environment.plist
if [[ -f $AGENT ]]; then
    launchctl unload ${AGENT} >/dev/null 2>&1
    launchctl stop ${AGENT} >/dev/null 2>&1
    rm -rf $AGENT
fi

Script to Change your CPU Name in About this Mac for Cosmetic Reasons. Copy and paste this into a new file, cpu_name.sh - then run it with

sh cpu_name.sh. In case you want to have a different name, you can add it under the if block as a cpu_name="My Hackintosh" which will override the original variable. Should show after reboot. I set a custom name because "Ryzen" made it too long to display the full name.

 

 

#!/bin/bash

locale=`defaults read -g AppleLocale | cut -c 1-2`
cpu_name=`sysctl -n machdep.cpu.brand_string | sed -e 's/ *$//'`
target="/System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/Resources/${locale}.lproj/AppleSystemInfo.strings"

if [ $# -ge 1 ]; then
  cpu_name=$1
fi

echo "Locale: $locale"
echo "New Name: $cpu_name"
read -p "ok? (y/n): " yn

case $yn in
  [yY])
    sudo mount -uw / &&
    sudo cp $target $target.`date +%Y%m%d%H%M` &&
    sudo plutil -replace IntelSpeedAndTypeFormat -string "%1\$@ $cpu_name" $target
    echo "Finished."
    ;;
  *) echo "Aborted."
esac

 

Some benchmarks for @fabiosun

 

  Reveal hidden contents

 

 

 

 

 

 

Thanks for replying.

I have reset CMOS and NVRAM a number of times and have CSM Disabled and Above 4G Encoding Enabled.

When I get back, I'll try removing all the other NVMes and SSD/HDDs and see how it goes.

41 minutes ago, TheDantee said:

@meina222 can you please share your EFI Folder with me we have very similar setup but mine gets stuck near the end of bar with the apple logo on loading the installer and then restarts my PC

Catalina, Mojave and Big Sur will not run with a Nvidia 1080 graphics card. You need an older supported Nvidia card or an AMD one. @meina222's EFI is a few pages back, you can download it from there.

Not getting anywhere fast here  I changed to a Catalina install rather than Big Sur. I am now getting “can’t perform kext scan: no kext summary”

and then

”** in memory panic stackshot succeeded ** bytes traced 4064 ••”

When I try with BS again I am now getting the same message and I don’t reach the [Configuring PCI] that I got to yesterday. 
 

I am away for the weekend but will try again next week  Aaaarrrrrrggggg 
 

Getting further than yesterday thanks to @meina222 but still no joy. Stops at

[Configuring PCI]

when trying to install Big Sur, and just stays there. Waited up to 10 minutes but it doesn’t progress any further. 
 

Will try with Catalina tomorrow but I don’t hold much hope of it progressing beyond this point, but who knows. 
 

10 hours ago, meina222 said:

@Ploddles

 

Try this EFI working on the TRX40 Designare which is very similar to the TRX40 Master. Just make sure to fill in your serial and ethernet ROM in the nvram section and try again

 

 

 

 

EFI.zip 6.89 MB · 1 download

Thanks, I’ll try it tonight. 

No luck so far for me, just error messages. I am on a different MB so will strip out as much as I can from the config.plist and try again. Have already tried without the SSDTs but exactly the same errors. 
 

17 minutes ago, iGPU said:

 

This might work. You'll need to fill-in SN parts. I also left kexts activated for BT/WiFi; turn-off it you don't want them. This is using compilation from yesterday for OC v061. Patches were from fabiosun's post above.

EFI-v061-08-09-20-BareMetal-public.zip 6.84 MB · 2 downloads

Much appreciated. Thanks. As soon as the weather here in the UK cools down a bit I'll start my 'playing'. I have a different MB (Gigabyte TRX40 Xtreme) to everyone else on this and Fabiosun's Proxmox thread so hopefully I can get it working.

This looks exciting. I haven't managed to get Proxmox working fully/correctly yet. I can create the Hack, use the Proxmox Console or VNC or Remote Desktop into macOS but not pass through my RX580 properly. Whenever I do that the Hack either fails to start or if it does I no longer have Console, VNC or RD control - the monitor flashes for a brief second and then displays a message saying no input is being received and goes back to sleep.. I've tried numerous different Proxmox configs but I haven't managed it yet.

I would much prefer to run it as Bare Metal, either Catalina or BS as I am far happier in that environment than Proxmox.

If someone would be willing to upload their full EFI I would be forever thankful. I've tried so many various things under Proxmox I'm pretty sure I've screwed everything up and need a nice fresh one that is known to work well.

On 7/19/2020 at 11:26 PM, meina222 said:

p.s.

As CCC doesn't copy the MacOS main disk EFI by default, you need to do that manually once only, when happy with your OpenCore config, else it won't boot of course. OC crashes badly if your try to use the NVME as a Time Machine or CCC destination and forget to fix the EFI. Then the only way to boot is to remove the NVME PCI, but that defeats the purpose of using it as a backup, so don't forget this step.

Have a look HERE,  at Step 13 Spoiler. There is a script in there that you can add to your CCC clone job to automatically clone your EFI partition to your CCC disk's EFI. There is a TEST_SWITCH so you can run it without actually copying the files but it outputs a list of what it would copy. Just change the switch to 'N' so that it does the copy if you are happy with the test.

My motherboard and CPU should be with me next week, so I am looking forward to building my first virtual Hackintosh.

I have got through about half of this thread, so hopefully I will be uptodate by the time I start my build. So much information here, thanks guys, but I will have probably forgotten most of it by the time I am up and running.

I have already downloaded the OC_EFI_Maker to get my OC.ISO built, with the latest kexts etc. but am wondering if I need any SSDTs like I use on my Z390 MB and i9-9900k CPU. I haven't seen any mention of SSDTs so I am guessing that I don't need any or I have to make my own.

A pointer as to where I can get any prebuilt ones, if I need them, would be gratefully appreciated.

Cheers.

2 hours ago, fabiosun said:

@Ploddleswelcome 😊

evaluate well 3960x

some user said it is difficult to pass all cores in proxmox

i have no direct experience on this

witn 3970x I can use all its cores

Thanks for letting me know so quickly. I have now changed my order to the 3970x.