Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/27/2020 in all areas

  1. I'm sorry to hear about your problems, but it's not related to my uploaded EFI, but a result of whatever you did with MmioWhitelist. The process I went through for MmioWhitelist was documented earlier in this thread, but was simply a more fleshed-out version of what's on Dortania's OC guide. I didn't invent any of those things. It was tedious to go through, but uneventful for me. While it's obvious there was a problem in how you processed MmioWhitelist, as I've mentioned several times, since every mobo's MmioWhitelist is different, few of us can help you. (And this is why I didn't activate mine in the EFI, but only left as a reference.) Once you get your system back up running, I think you should stay away from using MmioWhitelist. Things will work without it. Or, if you definitely want NVRAM, use NVRAM.plist following Dortania's guilde and OC documentation. The EFI I uploaded was to help for BS Installation and debugging. I view it as a tool, not necessarily a daily driver: this is why I uploaded a basic, stripped down version without fancy SSDTs. I mentioned in the upload post, that Shutdown only seemed to be working in BS, not Catalina. All kexts and drivers were latest commits (drivers and other OC efi files must match for current commit; any substitution of a different commit dated efi file could crash a system: this is esp important for BOOTx64.efi, OpenCore.efi, and OpenRuntime.efi). A few Hackintosh caveats: 1. Hackintoshes are fun to experiment with; they can be changed unlike a real Mac; but they're not real Macs. 2. And since these are Hackintoshes, they're guaranteed not to be as stable as a real Mac. If you want reliable and stable, buy a real Mac from Apple. 3. If your system is working and you have a relatively stable machine and it's needed for your work, don't update anything (this includes BIOS, boot-loader, kexts/SSDTs, drivers, and esp a beta OS). 4. Always have a back of your main drive. (I use CCC to keep a clone of everything I work on. If something fouls up, I clone the backup to the main drive.) 5. Have back up EFI's ready for alternative access booting. 6. If things seem unstable, re-flash BIOS. BIOS can become corrupted with crashes and hard reboots. This is not uncommon on Hackintoshes (even on the Intel side). It only takes a few minutes (and if you have a saved configuration, only seconds to re-load all settings as long as the BIOS is the same version.) 7. AMD is the most unstable Hackintosh platform and the TRX40 platform the least supported of all.
    2 points
  2. I still don't know how ... more or less ... but I managed to activate the driver again .... hurray.. the hard head always rewards if it also joins a good blow of .... ass (colorful way to say that I was lucky)
    2 points
  3. se ti funziona ovunque lo stop, รจ una prova inutile ๐Ÿ™‚
    1 point
  4. Gande ora funzionano alla meraviglia !!! Grazie
    1 point
  5. This is where I got to for Asrock board owners! MMIO whitelist Child 2 is a problem child!!!!
    1 point
  6. First, I just re-tested the EFI I uploaded, leaving it exactly the same with no entry for MmioWhitelist, and it booted into Catalina without any problem. Second, in your first post here, you mentioned things were working well with the EFI. What exactly did you change from that point where it was working, to the point when it did not? (No matter what, not booting doesn't mean the drive's contents are affected.) And what you've shown does not indicate a problem with BIOS. Where it stops suggests some change in settings, particularly with one of the Quirk settings. Did you change any of those or anything else? To try and get you "re-set", I included 2 extra config.plist files in the EFI folder as an internal backup. First re-name your current config.plist file to save your MmioWhitelist work. This way you can access that list later. Then, duplicate the extra named "config-basic-genPI.plist", then rename this duplicate "config.plist". This new config file should boot as it re-sets things to what I originally uploaded. As for the MmioWhitelist, since few of us have the exactly the same mobo with the same components, no one can work up an MmioWhitelist for anyone else. Each person has to do it on their own, but only if you want native NVRAM. If you don't want to go the MmioWhitelist route, leave the MmioWhitelist array empty and setup an NVRAM plist by reading the OC Docs. Assuming you ran the MmioWhitelist test correctly, and you wish to try it once more, I would suggest that you set all entries in the list you displayed to 'Yes', except set 15, 16 and 17, setting those to 'No'. ***** And here I would remind anyone else that one always should have an alternative method of booting into a drive (even running a VM). With bare metal, at the very least, you want to have a USB thumb drive with a known, good EFI for access to your drives. Personally, I have 2 NVMe drives (1 Catalina, 1 BS), 1 SATA with Catalina and an external USB with BS. Each can have a unique EFI, but one has an older, working EFI so that there is always bootable access. The known, working EFI is how I tested the MmWhitelist. When a boot failed, I simply forced a shutdown and re-booted using the alternative EFI. Furthermore, the external drive can be connected to my laptop to work on a problematic EFI separate from the Hackintosh.
    1 point
  7. What I will write below is a bit OffTopic. I remind everyone, in particular those who read us but do not actively participate in the forum, that it is very important to respect some rules dictated mostly by common sense: 1) give due credit to people who share their experiences for free 2) not to steal, clone users' github without their direct permission The spirit that I would like to create and that in part I think is already in place is to share with all the people with a minimum of salt in the pumpkin (pumpkin is an acronym for head in Italian :)) our experiences on this new and fascinating possibilities we have with the TRX40 I hope you understand. I also take advantage of this OffTopic to remind you that any EFI posted is used at your own risk ... just a simple advice is valid ... do all your necessary checks before using the EFIs provided (kindly and free of charge) by the most 'willing ๐Ÿ™‚ users
    1 point
  8. Fatto prova , nel mio caso funziona sia senza che con . Ho fatto prova solo su Suppostone........ Grazie
    0 points
  9. si ma le cose da fare su macOS sono indipendenti da che boot loader si usa
    0 points
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.