Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 09/28/2020 in all areas

  1. Chiacchierando su Discord con @fabiosun sono emersi alcuni aspetti interessanti: la degradazione di prestazioni nel 3d è sostanzialmente responsabilità della patch che recita Fix Pat nei commenti. Se viene tolta in sistemi TRX40 le prestazioni 3d sono FINALMENTE PIENE, mentre se viene tolta in sistemi X570 la macchina non è utilizzabile e al 90% degli utenti si blocca ad una schermata gialla. A me si carica il sistema dopo un'infinità di tempo di attesa poco prima della schermata di login... poi si ha il boost prestazionale nel 3d, ma a costo di corruzioni grafiche pazzesche. A questo punto parrebbe che le cpu AMD per TRX40 funzionino correttamente col codice originale Apple per il modulo mtrr.c (quello a destra), mostro in figura quanto gira in rete riguardo alle modifiche che fece Bronzovska (aka Bronya) al kernel di High Sierra nella versione 10.13.3, che, tradotte adeguatamente, sono le attuali patch "vanilla" applicate a tutte le cpu AMD e a tutte le versioni di macOS. https://github.com/AlGreyy/AMD-xnu-4570.41.2-High-Sierra-10.13.3 Inoltre se l'accelerazione 3d non è attiva il boot avviene regolarmente su piattaforme X570 e B550 senza alcuna corruzione grafica... ma chiaramente senza accelerazione 3d non è possibile valutare gli effetti dell'eliminazione della patch 😞 ...qualche esperto di XNU che può aiutarci ad adattare questo codice alle cpu AMD consumer? https://github.com/AMD-OSX/bugtracker/issues/5
    2 points
  2. CloverX64-5122-jief-2709.1.zip attuale configurazione quirks sulla Z370 se qualcuno usa FakeSMC al posto di VirtiualSMC, meglio inserisca la versione di Slice inclusa in Clover iso o quella di Rehabman modificata da FreeJHack https://www.macos86.it/topic/3210-fix-fakesmc-backtrace-con-opencore/ da me funzionano all'apparenza correttamente, mojave, catalina e BS non fanno il boot e si bloccano immediatamente alle biglie rotanti i win10 e linux mageia, sia che vengano avviati con le custom entries che lasciato il setup nel config su auto.
    2 points
  3. Ciao, devi aggiungere l'opzione di boot manualmente sul bios per farlo puoi usare la shell (c'è la mia guida per efi shell) oppure app da windows ci sono guide sul forum a riguardo
    2 points
  4. si di fatto è questo, diciamo che non è corretta al 100% Se leggi la mia guida, ormai scritta da anni, quando al tempo 8 persone su 10 se ne fregavano della mappatura solo per il fatto "eh ma tanto ci sono le patch"... poi nel corso del tempo visto i problemi sempre più frequenti, l'instabilità delle patch stesse etc.. è stata poi fatta e usata sempre di più fortunatamente Nella guida vi è proprio scritto la motivazione, il come e perchè si effettua una mappatura, la parte successiva a questa è la definizione dei connettori delle usb, la quale è un ulteriore miglioria ma solo quest'ultima non può essere vista come mappatura sensata nel vero senso della parola quando poi si continua a usare patch etc Ma figurati nessun problema e per come si dice "nessuno nasce imparato" 🙂
    1 point
  5. Built-in Intel WiFi now working (ax200) in BS, as well as the Bluetooth. Speeds a little slow but another thing to tick off the list of working things. No doubt the drivers will improve to increase speeds.
    1 point
  6. only for the sake of testing I have installed successfully Catalina using an USB full installer and same EFi Instead, Big Sur hangs here: I have not removed my Thunderbolt card I am not using any ssdt in ACPI, only DevirtualizeMMIO in booter boot loader quirks Other stuff identical to the Proxmox config.plist (obviously with different kernel patches)
    1 point
  7. @valmeida our sata controllers are seen well in osx if you have big sata disk greater than 4tb they could be appear (sometime) after a bit , if you see in disk utility app they are there but osx loose some time to mount them in my case it happens with two 10tb exfat formatted drive i do not know if your asus extreme ii use differents kind of sata controller maybe you can check but i do not think so
    1 point
  8. IGPU same conclusion I did before Some openGL (old stuff) work worst About stability I have to proceed in a more systematic way cpu benchmark with Cinebench have a big probability to reboot my system for now this morning also acquantia ethernet does not connect well...but yesterday I have done many tests so I can't be more specific It seems also I can't load a simple ssdt in my rig I am locked to high Sierra (my main interest is in it) so I can have also additional problem Tested nullcpupowermanagement kext, dummy quirk and different sets of kernel patches, but this instability it is not solved as side note with AMD Power Gadget I see a power draw of about 80 watt in idle..about 370 in full Cinebench 20 stress Idle seems a bit high tested also in different PBO state results is the same
    1 point
  9. Bios corruption could be your problem @meina222 try to re flash your bios I think it could solve your actual freeze main task should be to find exact things that inhibit us to shutdown or in my case to understand why in my rig now I have gpu acceleration with my same previous efi nvram could be related to this quirks but for now we have to study with classic process of errors and tries
    1 point
  10. @tsongz i will try as you said thank you for now problem is stability.. benchmark is sure is oretty good in many tests i did i am now trying others kernel patches and a tsynch kext togheter dummy quirks in OC maybe i will resume also nullcpupowermanagement kext
    1 point
  11. This is not good imho maybe it is related to shutdown problem we have, in old chipset it could reset bios and produce weird corruption problem as in old chipset older than our i noticed in my case my reboots happen only when i use cinebench i think bare metal is a way to try, but by now it is not advisable for a production environment proxmox is safer but in baremetal we have all the chances to use any device we have without bridges problem
    1 point
  12. There is no safe efi because this is an unexplored territory patches, boot loader and so on we have to find a proper mix of combinations of it to have, maybe a stable system. if you analyze your boot log I think now you will find in it some errors like unsincronized Tsynch Cpu or similar.. so maybe additional kexts are needed.. in my case executing cpu benchmark with cb 15 or 20 could cause an instant system reset.. using some apps instead like adobe or davinci need perl command patches ..but it is an Amd rig features for now
    1 point
  13. 1 point
  14. Cuda benchmark I am using same disk I am using in Proxmox.. I will carbon copy it in a new ssd and I will patch all app (adobe and davinci) to do real life benchmark
    1 point
  15. cb 15 FPS in baremetal 50 cb 15 FPS in Proxmox 120 to interested people, same Proxmox EFI in config added all patches as you can find in this thread
    1 point
  16. 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! 🙂 🙂
    1 point
  17. with my previous installation done yes now I have deleted that disk and try to reinstall I can't see macOS installer icon in boot menu (after first installation part went fine)
    1 point
  18. I have said above memmap is the way and it could be different also in an exact same rig
    1 point
  19. Gigabyte users have to compare their bios settings and maybe agesa version in it msi and asrock seem to be less tricky to configure
    1 point
  20. 1 point
  21. @all are you sure nvram is working and maintained in your trx40 system? in guide section there is a way to verify it very curious about it
    1 point
  22. kext seems not to load Last login: Thu Aug 13 08:35:01 on console fabios-iMac-Pro:~ fabio$ kextstat | grep -v com.apple Index Refs Address Size Wired Name (Version) UUID <Linked Against> 36 2 0xffffff7f83318000 0x2a000 0x2a000 as.vit9696.Lilu (1.4.6) E1988EED-9336-3A82-A361-9F31FDE22EDE <7 5 4 3 2 1> 37 0 0xffffff7f8335b000 0x145000 0x145000 as.vit9696.AppleALC (1.5.1) F3D6D4E7-6EEF-37E9-B814-027E16746B95 <36 12 7 5 4 3 2 1> 50 0 0xffffff7f83342000 0x19000 0x19000 as.vit9696.VirtualSMC (1.1.5) D8B947B4-805E-357E-AD37-F96AB13AB87B <36 11 7 5 4 3 2 1> 64 0 0xffffff7f834a9000 0x1a000 0x1a000 com.smalltree.driver.SmallTreeIntel82576 (1.0.6) F6C5E33A-97AA-37A0-8794-64FAA19FC153 <15 12 5 4 3 1> 101 0 0xffffff7f817e9000 0x3000 0x3000 com.nvidia.NVDAStartupWeb (10.3.3) 4F3B6943-C73B-378C-9EA7-D36569B4B6D3 <12 4 3> fabios-iMac-Pro:~ fabio$
    1 point
  23. @iGPUcould you post your bare metal IOREG with Alpine Ridge? thank you I think I have to populate this: like this I mean:
    1 point
  24. @iGPUI have used previous one these are my results fabio’s iMac Pro IGPU SSDT SET.zip I can't see any device if I connect via usb (type c)
    1 point
  25. @iGPU i think only you for now are in bare metal could you post output of this terminal command? csrutil status thank you i think problem i have with nvidia driver is an old SIP problem
    1 point
  26. I use 060 release important and mandatory setting is DevirtualizeMMIO quirk enabled
    1 point
  27. @meina222 i have posted only a config efi was posted by IGPU @iGPU great job usb is working? @all could you post output for this terminal command? csrutil status thank you
    1 point
  28. I can test only with different usb type c device..for now I can't see them
    1 point
  29. @iGPU I think you win 🙂 fabio’s iMac Pro IGPU DevicePROP.zip
    1 point
  30. have you GPU acceleration? before sleeping could you do a test with cinebench15 (GPU part)? I am too curious 🙂 🙂 🙂
    1 point
  31. 1 point
  32. here you go 🙂 TY fabio’s iMac Pro IGPU.zip
    1 point
  33. @iGPU and latest for non apple kext loaded sob no Nvidia 😉 fabios-iMac-Pro:~ fabio$ Kextstat | grep -v com.apple Index Refs Address Size Wired Name (Version) UUID <Linked Against> 36 3 0xffffff7f827d5000 0x31000 0x31000 as.vit9696.Lilu (1.4.6) 847B9586-1BE1-315C-B2AC-5E832A407C7B <7 5 4 3 2 1> 37 0 0xffffff7f8283f000 0x72000 0x72000 as.vit9696.WhateverGreen (1.4.2) 9B4CBD0D-14DC-3DA1-B99E-1430023979C2 <36 12 7 5 4 3 2 1> 38 0 0xffffff7f8281f000 0x20000 0x20000 wtf.spinach.AMDRyzenCPUPowerManagement (0.6.4) 1C8D6AF1-3F8A-3298-BCAE-5CAEE5D4A19B <36 12 9 7 5 4 3 2 1> 51 0 0xffffff7f82806000 0x19000 0x19000 as.vit9696.VirtualSMC (1.1.5) E1D2507A-5E1A-328D-85B0-6A8D4263F019 <36 11 7 5 4 3 2 1> 63 0 0xffffff7f828b7000 0x1a000 0x1a000 com.smalltree.driver.SmallTreeIntel82576 (1.0.6) F6C5E33A-97AA-37A0-8794-64FAA19FC153 <15 12 5 4 3 1>
    1 point
  34. @igpu i see without ssdt stuff in systeminfo/thunderbolt
    1 point
  35. @meina222if you have a disk with any osx installed...not a virtual file ..a disk i mean put my config and use a minimal set of kext and driver efi important things are: patches devirtualizeMMMIO enabled and then start it from that efi it is pretty simple. you could have some headache due radeon vii..or your xt..but it is more simple to try that to explain
    1 point
  36. yes 😉 thank you, in Bare Metal I see 32Gb module in Proxmox I see as you
    1 point
  37. Ok it works bare metal works in Catalina 10.15.6 for now I have no audio e no ethernet (aquantia is seen by default but no cable connected message) cpu benchmark are the same like Proxmox i can’t test gpu Performance Ok audio is fine and also ethernet is working (no Aquantia but intel i211 with SmallTreeIntel82576.kext
    1 point
×
×
  • 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.