Jump to content

fabiosun

Supervisor
 View Profile  See their activity

  • Posts

    10,505

  • Joined

  • Days Won

    433

 Content Type 

Everything posted by fabiosun

  1. fabiosun
    @iGPUhave you mounted in your TRX40 a Titan Ridge card? I am not be able to adapt the old SSDT used in Proxmox with new ACPI address...
  2. fabiosun
    thunderbolt 🙂
  3. fabiosun
    PCI Device in Baremetal
  4. fabiosun
    Acquantia in HighSierra (no driver or patch needed) Thunderbolt without SSDT I have to change the one I have had by IGPU and test all my sata devices My two NVME drive and finally my GPU and my two monitors connected on it
  5. fabiosun
    I agree with all above message Usually I do not put entire EFI because I know that for a better learning curve user have to solve some minimal stuff I appreciate all @igpu efforts in this thread And I hope..with his job we can improve all our knowledge..and thunderbolt device 🙂 🙂
  6. fabiosun
    caro Giulio io seguirei le guide che ha in firma @icanaro e ripartirei da zero 🙂
  7. fabiosun
    MMIO I see on you excel page is weird it seems two of the start part are the same with a name changed For this I was asking if you have back upped on Bare metal efi that log no need to start again in BM but only booting in Proxmox, mounting BM efi and copy your boot log about your problem if it is the only change you have done a simply CMOS reset could restore your ideal situation Maybe you can save firstly on a txt file your actual bios configuration to restore after this
  8. fabiosun
    then I have also seen here his EFI completely changed by user..and this is not good if then EFI is posted again for others.. my role here as a moderator should impose the rule on me to delete all the efi taken and modified by other users than the one posted originally to avoid problems But I prefer to leave the discussion very free
  9. fabiosun
    I am using mine and I have no checked IGPU EFi Usually all EFI posted are to be verified for owner system @iGPUdoes a great job to offer a complete EFi..but he has a system which differ from mine or your..so not all can be "copied" as is but this is only my 2 cents to this subject
  10. fabiosun
    ah ok then check all kext you are using and verify you are using latest--things change faster in this time 🙂
  11. fabiosun
    if I remember well maybe you posted something here...
  12. fabiosun
    sorry @Driftwoodthese are yours? could you put a fresh open core log if your bare metal rig boots?
  13. fabiosun
    I would try to start from your Proxmox EFi also in Baremetal Adding full set of AMD patches and nulling all ssdt you are using in proxmox Then Devirtualize MMIO on this should be the starting point for all people who have a working Proxmox EFI You (AMD GPU user) should have less problem than I have had because AMD driver is in OSX Evaluate also well, how in your system act some quirk (booter quirk) relative to memory remapping... For me this was the key MMIO whitelisting is useful for debugging restart and shutdown problem you can have This, without using any ssdt only enabling blacklisted MMIO MSI users should not need of npci 0x2000 boot arg, also with 4g disabled in Bios I have the same bios setting I use to boot in Proxmox Now I will test more extensively the apps I usually use, but as first impressions they acts in the same way
  14. fabiosun
    Seems old problem with prelinled kernel and big sur
  15. fabiosun
    @meina222may I have your fully working EFI in proxmox and your mmio plist (bare metal I mean)? if you want loose some time again with bare metal I will prepare an EFI for your system I would also suggest an important thing to consider Proxmox threats ddr4 in its way so maybe a more conservative memory settings in bare metal could help if system acts weird
  16. fabiosun
    Ah..as other infos I would like to share in a very happy way.... Sleep is working 🙂 🙂 🙂 🙂
  17. fabiosun
    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)
  18. fabiosun
    I would like to suggest during testing MMIO stuff to leave verbose boot on to see verbose data during reboot (often during reboot there is a fast KP, you can solve with proper quirks and MMIO skipped)
  19. fabiosun
    @Pavo SSDT is loaded and variable stay there also after a reboot same behaviour of emulated NVRAM For now not useful for my problem (Nvidia web driver not loaded properly) @iGPUwaiting for your idea to try... I wonder way during my test..without doing nothing of special I have it loading well then after a problem with default secure boot parameter I have had to clear my cmos and from there no joy fabio’s iMac Pro Pavo SSDT.zip attached my IOREG with Pavo's SSDT
  20. fabiosun
    thanks I will try
  21. fabiosun
    No I am using emulated one..but it does not solve my Nvidia driver problem
  22. fabiosun
    @meina222 our MMIO are pretty similar they diverge in the latest 4, these ones are also problematic to skip in my case
  23. fabiosun
    this is what is working for me
  24. fabiosun
    opencore-2020-08-26-142151.txt.zip this is my 061 log 🙂 not tested for now, but I think it will be the same.. before I have had the same problem with both OSX now I have to re clone my VM Catalina.. before I would like to solve my real problem in OSX
  25. fabiosun
    No I have my idea about ssdt only new open core and MMIO playing with these two I have posted all my logs and you can try with your MMIO address About SSDT I would like to explain better I have no skill to build any SSDT, so I can't do fo my self I do not like to add stuff under PCI tab and some SSDT functionality is possible to have using device properties in OC
×
×
  • 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.