Leaderboard

said what above .... 🙂 here is my full EFI To be filled in with the data of your platform in the section relating to SMBIOS Be careful this EFI is based on the official opencore debug version 061 with relative kexts and drivers Attention again, this EFI allows me to start all OSXs available as of today 16 September 2020 on my PC Big Sur 10.11 (beta 6) Catalina 10.15.6 (19G2021) Mojave 10.14.6 (latest security fix) High Sierra 10.13.6 (latest security fix) (see the signature for exact specs of it) I use a MMIO set that comes from a Bios version 1.60 with the 4G option enabled. In addition to this, I use quirks that may not be useful for you, I don't use the AppleALC kext, as it is useless for using any USB audio. I do not use any bootarg alcid as it is useless if not combined with the aforementioned kext I don't use ssdt at the moment and the ACPI ones you see are disabled By the way MMIO used combination should be evaluate better (imho) because the combination of their use can lead to undesirable effects in some circumstances ... not foreseeable by anyone who does not have the same setup as you to complete my description Slot 1 Nvidia Titan Xp Slot 3 AQuantia ethernet 10G card Slot 4 Gigabyte Titan Ridge Thunderbolt card (bios flashed) 1 Samsung 960 pro NVME 1 Tb (Windows) 1 Sabrent Rockets NVME 1 Tb (macOS High Sierra) 1 Samsung 840 EVO (other OSX I like to test, now Catalina) 2 ST6000 in raid (software raid used in windows) 2 ST10000 (ex fat formatted, shared from all OS) 1 Pioneer BDR 207M 1 Samsung 840 pro (Proxmox) connected to ASMedia USB 1 27'' Philips brilliance display (3d stereoscopic Passive FULL HD) HDMI connected 1 43'' LG UHD (3840x2160x60Hz) DP connected NO wifi, NO BT EFI.zip fabio’s iMac Pro.zip

If you like we can try.... send me via PM a proper Efi and a minimal description of your System i will put in OP so: efi main bios config and version hardware osx tested and so on for now i think we could have: Msi trx40 pro 10g Msi trx40 Creator ASRock trx40 Creator Gigabyte trx40 Designare ex Gigabyte trx40 Aoros Master Asus trx40 Extreme II alpha let me know in green..added to OP (EFI and Ioreg)

What you've written is important and there are 2 simple ways to go forward to keep the thread tidy, but first some prefacing. Problems will always arise as threads progress: due to new hardware, new macOS updates, changes in OC, and differences between individual builds. These problems are what threads help to resolve; a community effort to help each other. And while it's one thing to help someone who is confused or stuck with a particular problem. It's an entirely different issue if someone has no clue about OC or TRX40 issues and who does not want to expend any effort in learning how to get their system working (lazy), or, is trouble shooting a lousy EFI. The former, can be ignored. It's the latter problem that we should minimize (especially since it's obvious that people do not carefully read threads). So how can we limit problem EFIs? One way to limit lousy EFIs would be for all uploads to be cleared with fabiosun. Snippets could be uploaded, but not whole EFI folders. Only fabiosun would upload EFIs. This would allow greater consistency, but be time-consuming for fabiosun. The other approach would be to continue as is, but request that the individual who wants to upload an EFI have greater self-control. In other words, only upload EFIs if you: a) know what you're doing (truly understand the ins and outs of OpenCore), and b) are willing to support questions regarding it entirely on your own (since you claim to know what you are doing). Further, only upload EFI folders with full explanations (as fabiosun did above), describing which macOS it can boot (have you truly tested your EFI with various macOS versions or just thrown something together with no testing), what hardware it is meant for (a specific mobo or all mobos?), what are its limitations (e.g, 'no MmioWhitelist is included'), and what is unique or helpful about your EFI that warrants its posting (e.g., 'this EFI fixes such and such a problem'). Someone who uploads an EFI must have sufficient perspective to view their EFI in relation to other TRX40 systems (especially important for new-comers will also download it). If such guidelines cannot be followed, then perhaps fabiosun or a moderator can contact the poster to ask them to remove the EFI, or if necessary, the moderator can delete the post. Another suggestion would be to have the latest, or recommended EFIs, posted in a first post of this thread. (This would requires work on fabiosun's part to keep it updated). There may be even more than one EFI, such as one for installation, another for a special mobo, or perhaps one for each mobo commonly discussed in the thread. fabiosun could recruit contributions. There could be a sub-section in this first post of SSDTs, special kext files, and so forth. If there is no consistency, the thread will continually require trouble-shooting problematic EFIs, which to me is a waste of time.

1) You've not read the thread carefully or you'd not have downloaded a config with all of the original patches. We talked about this several days ago and most of us are running only 13 patches. *** EDIT: See this post for better Patches. *** 2) your config file shows that you're using an older version of OC. You should be updated to v061 for best function. When I started using OC in early 2019, I spent days studying all the posts at the Insanelymac thread, reading the docs and looking at the sample.config plist. Now, I'd instead recommend going to the Dortania guide as the best resource to learn OC (here) and how to keep it current. Then on each update, study the Docs section, specifically, the Changelog.md and Differences.pdf files. 3) your config file is a little short on kexts. AppleALC and ethernet kext are usually a good idea on most Hackintoshes. (Do you understand that your boot-arg of "alcid=11" doesn't work if you don't load the AppleALC kext?) In the Kernel/Quirks section should disable the DummyPowerManagement; it's not needed for TRX40 (discussed before). There is also a new addition for v061, specific for Big Sur (discussed before, here). 4) The WEG/RadeonVII DP issues you describe are known to happen when WEG is disabled with Radeon VIIs (and I think 5700XT too) On the Intel side this was found to be necessary (starting with Catalina) to prevent crashes (that is, +WEG with Radeon VII led to crash), so it was rec'd to disable WEG but knowing that you'd lose some ports. ( I've discussed this several times on this and the VM thread.) On Big Sur, I run Radeon VIIs and now keep WEG enabled. My only boot-arg is "-wegbeta". 5) If you don't want the on-board wifi, I uploaded some time ago an SSDT to disable. You need a proper SSDT to re-inject SB.S0D2.D2A0.BYUP.BYD8/XHC (address 0x03) and leave out PRT5 which supplies power to the BT/Wifi device on the Desginare mobo. 6) In your MmioWhitelist, I'd recommend adding Comments, so you know at some later date what the heck you did and how to trouble shoot (as shown below). Commenting in code is always a good idea. I've already seen this section before and you copied someone else's no-comment section instead of deriving your own (a how-to was posted here). Yours: Mine: 7) The FENVI has recently on other forums been found to have various problems. The YOUBO card (here), now seems to be the preferred choice. *** TO ALL: Reading the thread carefully, at least the last 2 or 3 weeks of posts, will avoid us all having to re-address old topics for each new person who comes to work on this build. But part of the problem isn't the new-comer naively downloading files. Instead, it is the fault of posters who don't self-edit their old posts and leave tantalizing files available to new-comers. I would encourage all of us who've upload files to removed those which are no longer valid, or amend some explanation. (I did this with the Mmiowhitelist Instruction, removing an earlier upload and explaining how an easier method was developed and provided links back and forth from the old to new post.) I think if an EFI is faulty or has been superseded, it should be removed. Unless posters self-edit, old EFI's and other uploads will haunt us all, as new-comers download these old uploads, have problems, then request fixes to issues that were previously solved.

fai fare un giretto a ONYX della titanium software manutenzione poi eventualmente, fai backup di questo config poi fai generare tutti nuovi seriali riselezionando lo stesso SMBIOS che hai ora esegui check coverage riavvia e riprova i vari iservizi

I think this user’s brainstorm is very good to have a better discussion i like the idea to have in OP all verified EFI but we have to find a verified method to have proper EFI i think is it possible i like also github idea, i would like however this or similar thread here stays alive 😉

In my opinion we shouldn't be putting EFIs or snippets in the thread itself but use a GitHub repo so everyone can collaborate with forks and merges or if there is major differences, have configs to specific systems in the repo. This would eliminate anything in the past to present issue. The config structure is the same for all systems and change on OC updates, which can be maintained on the repo itself.

I'll go though my previous posts and remove old EFIs and edit them noting that I have deleted them. I am thinking about possibly replacing the EFIs with a link to a dropbox folder that just contains my latest one. My motherboard has twin 10G network cards built in so is different from all of the others on here and requires a different kext so I'd include the whole folder rather than just a config.plist. This removes the old EFI's and anyone clicking the link would just get the latest and greatest - probably not greatest out there 😀 but what works for me and my Gigabyte Xtreme. At the moment I think there are just 2 or 3 of us on here with the Xtreme. @fabiosun, if you don't like that idea just let me know and I'll just delete the old EFIs instead of replacing with a download link.

Figurati, meglio che mi sia capitato, almeno non ci si scontrano altri

prova a riscaricarlo da download

allora è gatekeeper che entra in funzione senza disabilitarlo, basta fare destro mouse sull'app e selezionare apri

e allora che ti interessa della differenza tra orario BIOS e macOS? mica passi del tempo nel BIOS

stai parlando di audio HDMI o analogico? se analogico, esegui DUMP codec audio (clicca e leggi FAQ che ho in firma per come fare) che si prova altri layout se invece HDMI, così su 2 piedi al momento non mi viene in mente niente devi provare con qualche valore di darkwake oppure sentire il boss @Gengik84 se ha qualche valido consiglio alternativo orario BIOS e orario macOS non coincideranno mai, tutto normale, esiste un .reg per windows per fare in modo che l'ora sia coincidente a quella di macOS UTC_7_8_10.reg.zip @dandi98 metti in firma la composizione di questo hack

Risoluzione puoi avere quella che vuoi, le Macchine Virtuali sono fatte per altri scopi, senza le quali, in molti settori, si tornerebbe indietro di vent'anni... - Grazie alle soluzioni delle VM è possibile ottimizzare una quantità praticamente infinita di attività che, in assenza delle tecnologie di virtualizzazione, richiederebbero così tante risorse energetiche e hardware da rendere spesso antieconomico il servizio offerto.