Leaderboard

TB3 Device: GC Titan Ridge https://www.amazon.it/gp/product/B07K6PW4M1/ Eprom programmer: https://www.amazon.it/gp/product/B07SNTL5V6/ Digital Multimeter: https://www.amazon.it/gp/product/B0872RY4CC/ in this thread we can talk about progress with this latest important goal to achieve. useful link: https://github.com/ameyrupji/thunderbolt-macpro-5-1/blob/master/GC-TitanRidge.md guide to flashing programming from CaseySJ DISCLAIMER: this is a very risky procedure also for experienced users. TAKE NOTE OF THIS. DO AT YOUR OWN RISK

@fabiosun - I think I am also close to giving up but not yet. I am still baffled by the restarts on shutdown and lack of sleep but I guess this is not uncommon for early hacks - all in all the fact that this is the only issue (and perhaps the seemingly worse power management) is not bad at all. I will definitely go through @iGPU's exercise. I feel like I want to script this so you can avoid all the manual steps - just auto parse the OC debug output from 1 run and generate X pre-calculated configs that you can then just drop and re-try. I'll see what I can do - it'd be fun exercise. To me the biggest draw of Proxmox is the isolation layer it provides and the ease of back ups / replication / reinstalls - no worries if I brick my VM with an update, and much less likelihood of a break. That paired with superior power management in the newest Linux kernel, makes it quite compelling. Due to the AMD reset bug I am now forced to emulate a bare metal workstation - host shutdown on macOS shutdown via hook, but when the reset bug is finally solved with new hardware this will be close to perfect setup minus the TB and less physical ports. Btw Linux kernel / Proxmox 5.8.1 is out. This is labeled as 'stable' by the Linux community - suitable for production use. Fabian has a release already in 2 flavors (reset and no reset, but this does not affect our OS).

@fabiosun credo abbia pasticciato patchandoli con non so' cosa.... infatti da hack_info risulta anomalo il plist di un webdriver non conosce gli script di gengik e non ha visto la release dei webdriver, quella pubblicata per errore da nvidia e poi ritirata, che si installa quasi ovunque

On attempting to refine the config file, I found that WEG does prevent a boot into bare metal BS (but is okay for Catalina). If left enabled, then one must enter the boot-arg "-wegbeta". Similarly, AMDRyzenCPUPowerManagement kext prevents a bare metal BS boot (but is okay for Catalina). Lilu, VirtualSMC, AppleALC, the ethernet kexts, the AirportBrcm kexts and NVMeFix are all okay, using latest versions. booter-fileset-basesystem and booter-fileset-kernel are not required as shown below. Most importantly, this config.plist file boots into both Catalina and Big Sur bare metal (one config to rule them all...). Booter and Kernel Quirks: NVRAM: UEFI:

You won't see anything attached to USB devices; it's just a take off point, like PMCR which was 'attached' to MCHC, but actually appears elsewhere. And no you do not need to enter for each USB device; it doesn't work that way. In reviewing your IORE, if you want to change this section to have USB ports, use the attached SSDT file labelled D1B8. If you want to do the same at the USB device at D0B8, use the file labelled D0B8. Each will re-name to XHC1 and XHC2. Yes, the other file may not be necessary for you, but it was for my MSI mobo. While the TRX40 has our USB devices showing up exactly the same, the responses may be a bit different.

Ok, I'm posting this from Big Sur running in bare metal! A 2nd NVMe drive in the computer contains Big Sur (the other is for Catalina). So I simply booted into a working Big Sur; no installation was done. My current config.plist file will boot into both Big Sur and Catalina. The AMD patches were identical; I changed nothing in that section. I initially could not get a boot with WEG enabled. Now -wegbeta" is added based on information from a later post here. But you can see what kexts I had either enabled or disabled from the config file. AvoidRuntimeDefrag = enabled seemed key to getting Big Sur to boot. You'll need to update ACPI sections, MmioWhitelist (which now blank); look at everything! Especially notice the NVRAM sections which reflect the changes for Catalina and Big Sur. You'll also need to update the PlatformInfo section with your own SNs. I've pasted in values (but not verified to be un-used). EDIT: MmioWhitelist is very important for bare metal functionality.

Finalmente si dorme

Buon ferragosto

Buon Ferragosto ☀️

Non ci sto capendo una beata mazza ahaha. Ho reinstallato la grande supposta, la beta pubblica, ed ho riestratto le acpi tramite clover. Beh adesso mi da 11547 come table lenght 🤔 origin.zip

hi @meina222if you know my history in trx40 task you will see I do not give up easily.. but here my main problem is GPU I do not want a radeon VII because it similar in benchmark to my Nvidia and I am waiting for Big Navi I have tested all I can for Nvidia and High Sierra but I am alone in this..and I am not able to debug clearly where my problem is However I have my disk ready and an usb pen to test if something new happen Redoing all debugging in MMIO as I did in the past to have this system working ...mmmhh now I have less strength for this..because trx40 in Proxmox works 🙂 If you have any ideas to test or a Nvidia to try on your rig..I will happy to be into this game again! 🙂 🙂

io ti saluto... preparata EFI ad hoc ed ora salta fuori OC con me caschi male, chi me le fa girare, poi con me ha chiuso

va bene che sei su una isola, che vi è lo spostamento della crosta terrestre, che ogni 15.000 anni cambia inclinazione asse terrestre... ma tu sei in orario come i treni in itaglia

l'idea sarebbe di fare la procedura insieme utilizzando una usb2.0 e poi una usb3 per vedere i risultati in ioreg (usb in uso associate alla procedura)

Buon Ferragosto a tutti.