Jump to content

fabiosun

Supervisor
  • Posts

    11,113
  • Joined

  • Days Won

    509

Everything posted by fabiosun

  1. All problem we have (except gpu amd reset bug) are related to proxmox—->OS X usb driver version then stuff like WiFi or Bt could also be related to our weird problem in conjunction with passed usb controllers later I will try to explain more in detail and I would grateful if some of you could do some tries to confirm this @Jaidy to start you have to connect to cabled ethernet it seems your WiFi card is not seen by default proxmox driver you can also find a driver for it but in this way you are adding additional difficulty to your starting proxmox/Linux learning curve
  2. @pavo and other user seem to have solved audio problem with this parameter to add in grub : pcie_aspm=off In my case it is not necessary but just in case you can try to use only 10.15.5 solved for me this problem @Rox67er audio problem is surely related to usb or as usb audio drivers works in OS X with our audio double bridged
  3. If I understand well it seems more probable it is related to amd Gpu reset bug?
  4. hai provato aq lanciare qualche bench grafico? di solito alcune schede moderne iniziano a farle girare vicino a 60 gradi
  5. @Rox67er no benefit to pass SMBus. I have tried to pass all controllers I can during my test about 99 error, have you tried to reflash your bios and clear CMOS before configure it as you need?
  6. seeing your VM conf I could imagine which some problem could happen to your system because you allocate (maybe) to much memory for VM if you have in total 128Gb..in my case in my previous attempts I have had put about 122000..and vm not was stable in that case I am not using also huge page stuff.. is it useful for you? and so when/where do you see benefit?
  7. Catalina OS seems to push a bit more about performance..obviusly same EFI to boot
  8. Hi first of all thank you to you and all people are keeping updating this thread with their experiences I appreciate it so much About 7-5 error when you boot proxmox, you should have to update your proxmox.I opened a thread on Proxmox support site time ago. Now with latest proxmox kernel that errors could not appears anymore Instead a bunch ACPI error could always happen For both (7-5 errors and acpi errors) a man of proxmox stuff said it is not a problem at all. I have not specifically competence to understand if It is true..so I have to accept as it is link to thread I said before
  9. updated to latest security fix for now I have to patch Nvidia web to have acceleration as usual..waiting for Nvidia new updated driver
  10. if I have understood your problem.. when you stay in proxmox ip/ethernet step, you can see all ethernet device installed (and that proxmox sees) in your system try to choose wifi one if there. I have no wifi so I can't say more about this
  11. @iGPUyou are not the one to have problem with Gigabyte/3970x... so maybe I have to stay with mine for now 🙂 for me all is perfect (except internal audio in High Sierra) I can do my job inside it as I do in windows...no more no less I hope you solve soon as you can your problem (trx40 creator for me is not a choice because I have 8 internal sata devices connected)
  12. @Rox67er have you solved understand your 99 code Error? searching on the net could be a simple bios corruption or a big problem with cpu pin socket about vfio.conf my motherboard has no wifi/no bt i can pass all controller if i use Flr, and i have all usb on my rig active now i am not using anymore flr kernel patches because I have the same functionality without passing audio controller/ 2 usb controller also important to say is that osx driver is the main actor imho. high sierra does not recognize any usb3 controller but osx catalina i installed from 10.15.5 beta to the release have nice improvement for usb i loose many time for this problem but problem was inside high sierra. For me is important to have it working in high sierra cause my gpu is not supported from newer osx i would also suggest you to install on a vm disk file also windows 10 64 bit you can install in a flash it and from there you can verify if your problem is a linux configuration problem or if it is a Os problem.
  13. I think (I repeat my self) you do not need many stuff you have in your config.. but this boot args are wrong 😛 And I am remarking it (as we were friends from long time (to be less serious or "master" because if people use that args then VM does not start When you have time correct it (please) Then, I am very happy when you (and others) post their results..but for learning some more detailed explanation is necessary... ie why for you pcie=1 and rombar stuff is mandatory and others things... do not thing also here we have not a job... 🙂 🙂 But the desire to have this Chip working and to share it (for free) to all hackintosh community for me was a pleasure and an honour 🙂 🙂 Now I am thinking to buy a Gigabyte Designare.because my main goal will be to have thunderbolt working (and let think..I do not need for my job) 🙂
  14. @Driftwood your VM config files seems weird..and I think you copy and pasted bad here this quoted lines instigated me to ban you from here because I can't understand well (joking for banning) "Hope this helps anyone. Pavo has been instrumental in getting this working and he clearly knows what he is doing, so rather than spend days sorting this (i understand more what he tells me all the time) I think advice from an expert is advise-able if you haven't got the time atm - got jobs on." I know Pavo is good for you (you repeat here so often) and he is helping you in private..but this seems a bit unrespectful for me and for other users which could benefit also of "your" finding 😉 Also I can confirm that most of stuff you put in your config is unesuful...but if it is working for you I am happy By the way could be useful (and not for me) to explain what this args does for you 😛 -machine q35,kernel_irqchip=on because you do not need of it and cranking audio is another problem (if you read on Proxmox forum you can understand better) but maybe it is a my problem again no offence for me (and I hope for you) To be clear I repeat that my goal is to grow here my knowledge also with your help... if I had done this in private..maybe you, Pavo and others still would waiting at Morgonaut site with her telenovelas on fastest hack ever.. 🙂 🙂 Have a nice day
  15. App updated (1.0.7) to support 10.15.5 download (full and reinstall mode)
  16. 10.15.5 combo update: https://updates.cdn-apple.com/2020/macos/061-78576-20200520-5dfa5569-76e4-4b87-b11c-9e53eb7651a4/macOSUpdCombo10.15.5.dmg
  17. OT. stessa EFI hanno tolto di loro il precedente unknown...
  18. Both usb Realtek audio and cheap USB audio work well in latest OS X release... for more infos read also main fix in this release...
  19. fabiosun

    Hi

    Welcome here @Jaidy great build 🙂
  20. @Driftwood i would like to suggest you to read this thread https://forum.proxmox.com/threads/vm-w-pcie-passthrough-not-working-after-upgrading-to-6-0.56021/ Here is possible also to understand what that args you add in your vm does i think not necessary but reading that thread you can understand better how a working pcie root/ bridge are related to qemu config... about 47:00 controller..in my case 46:00... you should investigate better 😜
  21. It is weird in my opinion how it is possible our motherboard act in so different ways in my case vfio.conf it is not usefull at all maybe it is about Agesa difference in our mb? Or for what? i have tested also old agesa but for me vfio.conf it is not important at all. @iGPU about pci bridge maybe we could find a way to ask on proxmox forum how qemu pci bridge virtual device interact wth real pci bridge and if they interact how to Add on that file missing ones
  22. @iGPU this is mine, I use a script given on amd discord by @pshirshov user, he should be also here I think with maybe other nickname: IOMMU Group 49: 42:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4] 46:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] 46:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] 46:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] IOMMU Group 50: 42:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4] 47:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) IOMMU Group 51: 42:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4] 48:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) to copy examples you did 46:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] Kernel driver in use: vfio-pci 46:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:1486] Kernel driver in use: vfio-pci Kernel modules: xhci_pci 46:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:148c] Kernel driver in use: vfio-pci Kernel modules: xhci_pci 47:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: vfio-pci Kernel modules: ahci 48:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: vfio-pci Kernel modules: ahci and this is achieved only with: hostpci9: 46:00.1 hostpci10: 46:00.3 hostpci11: 47:00 hostpci12: 48:00 47:00, 48:00 are my sata controllers: Qemu hard disk here is my Catalina on disk file the others are my mechanical disks installed and passed thanks to 47:00, 48:00 controllers
  23. I would like suggest to all of you to try do run an ACPIDUMP in this way: download acpidump.efi and put in OC/tools (thanks @Gengik84for this) https://www.macos86.it/topic/1560-acpi-come-estrarle/?tab=comments#comment-40152 https://www.macos86.it/applications/core/interface/file/attachment.php?id=6306 Boot directly with your OSX disk (with opencore EFI and not via Linux) in my case my NVME Sabrent obviously you can access only to opencore shell try to reach your EFI folder (in my case FS1:/EFI/OC/Tools and then run: acpidump.efi boot in your system and mount your EFI backup this data then start proxmox and do the same inside proxmox/OSX/opencore you will see how VM interact with our original ACPI... Maybe some of you have the skills to understand better than me and use it to improve our VM 😉
×
×
  • 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.