Hi guys, sorry for the intrusion.
Yep that’s right, The Rom field in the Config.plist is where you add your MAC address.Hi guys, sorry for the intrusion.
I have a curiosity: the MAC address must be put on the ROM line in the platform information of config.plist file, right?
At the moment I left the default detail, it seems 11223344, I don't remember. Can I use the MAC address found in the "About This Mac" details?
Yes, added all of the above. BIOS settings match what you laid out in the first post.
Top! Thx AudioGod, you also anticipated me, I was looking at your screenshots to understand whether or not to remove the : from the MAC address. So I put the address all attached with no spaces. Should I reset the NVRAM after correcting the config.plist file?Yep that’s right, The Rom field in the Config.plist is where you add your MAC address.
Go into system preferences then Network, Select your ethernet or WiFi and click on advanced, Once inside advanced select the hardware tab and there you will find your Mac Address.
When you put it into your config.plist make sure to remove the : and that’s it.
Download the EFI again and add fresh SMBIOS details and try again.Yes, added all of the above. BIOS settings match what you laid out in the first post.
Honestly no idea what's going on at the end of the log there.
I just realized I do have a fan hub connected to the internal USB, could that be causing an issue?
Also FWIW, I have 5900X as well, not sure why I wrote 3900X earlier.
You don't really need to for something like that but at the same time it will do no harm to clear it.Top! Thx AudioGod, you also anticipated me, I was looking at your screenshots to understand whether or not to remove the : from the MAC address. So I put the address all attached with no spaces. Should I reset the NVRAM after correcting the config.plist file?
Thanks so much again
Yeah, Don't use Proper Tree...lolYes, I have assumed that resetting the NRAM is a sensible and clean thing to do after the changes to the EFI.
I fixed my file. I would not like to go off topic, in case I close the discussion here, but a strange thing happened to me:
1. Monto EFI with MountEFI.command;
2. I open ProperTree.command.
and I crashed the Hack twice in a row, actually, to tell the truth I think it just crashed the video. I then opened ProperTree and mounted the EFI and had no problems.
Yup, I was testing it out last night. Big Ups to trulyspinach, He has done a Stella job as always.
Hi and Thanks for the kind words buddy.
Just checking the Buyers Guide regarding your GPU and it states….
Thats helpful isn’t it?
- R9 280x/380x (Hit or miss)
Its a case of give it a try and see what happens.
only suggestions I can think of is to have Above 4G disabled in the bios and add the boot argument npci=0x2000 to the Config.plist Plus remove agdpmod=Ignore from the boot arguments while you are in there.
If it’s going to work that’s all it should take for it to kick in.
Good Luck and let me know if it works for you.
Just an update here, I pulled a fresh EFI and loaded new SMBIOS info.Download the EFI again and add fresh SMBIOS details and try again.
Could even be a duff USB Installer as it does happen from time to time.
Shouldn’t be a issue as the mapping is correct and you use the same board as me.Just an update here, I pulled a fresh EFI and loaded new SMBIOS info.
I've tried full installers of Big Sur and Catalina, as well as recovery images of Big Sur, Catalina, and Mojave. Can't get a single one to boot to the installer.
I may try to create my own EFI just to see if I can get it to load the installer. Wondering if the USB mapping could be an issue? Still perplexed by this.
No, All you did wrong was not ask me or read the notes as all you had todo was press the space bar when you get to the bootpicker to reveal the option as I have the recovery drive hidden as standard. WhoopsI followed your guide and tried this with my ASUS rog strix x570-i, would not see the installer partition. So ended up following the opencore guide and built the EFI from scratch and installed without any problem.
so i guess the ASUS motherboards are different even within the same family