fabiosun

@iGPU in verbose maybe you can see where it hangs before login ?

Mmmmh maybe you have to revert to a not patched kernel? my booting time is very fast and all usb controller are on without problem I have opened a thread on proxmox forum for audio problem but it is hard to explain and I do not think is a proxmox problem because with same distro config a Windows vm is working perfectly usb part of your thunderbolt is working?

@AllubzVif you read I said before only problem I have i think is an OS X driver problem because with same proxmox setting in a window vm it is perfect patch is useful to pass controller but it is also possible to pass without i have asked @pavo to insert 148c address for us (trx40 user) but as I said not useful to solve @iGPU has a working usb Dac audio, but in my case I have no others usb to test..only cheaper ones and these have the same problem

devi provare io posso solo garantirti che da me e da diversi utenti che conosco..la sage ha consentito di avere il miglior hack di sempre come stabilità ed utilizzo poi ogni caso e' differente.. E la variabile negativa e' dietro l'angolo... ma spesso la più' grande variabile siamo noi 🙂 🙂

cerca sul forum c'e' una guida sia in italiano che in inglese e' una caratteristica che hanno i sistemi operativi mac bisogna solo attivarla Poi non so se puo' essere comoda anche per te ma esiste da sempre

io li leggo e scrivo senza mettere software da sempre... pero' magari a e serve altro... onestamente il problema di Nvram..e' abbastanza simpatica come risposta che ti hanno dato..ma tutto puo' essere 😉 fatti spiegare bene come risolvere magari si impara qualcosa 🙂 questi sopra sono i miei dischi nfs che leggo in OSX

mi dispiace qui non so aiutare anche se vedo che hai un software paragon mi pare installato e finche' non hai un sistema solido al 120%..io metterei pochissima roba... pero' ognuno deve fare come crede sia meglio per se 🙂

Io ero ad esempio un funerale cmq un hub di solito vale una porta poi @Extreme™non rispondi su che problemi hai o pensi di avere quando fai la domanda.. ed è complesso a volte seguire

Purtroppo non ho affrontato mai la situazione negative..a me e' andato al primo colpo e pure a @thenightflyer ed altri utenti che hanno provato Pero' a sensazione che se sbagli non vada piu' la rete nemmeno in windows

@Extreme™la risposta verrebbe cosi': Lo stai limando perche'? io con questa piastra non necessito ne di port limits ne di kext usb particolari.. Riscontri particolari problemi in relazione alle USB? Nel caso, sei sicuro che siano quelle eventualmente interessate da un probabilmente inutile kext?

si ma non era per quello lo citavo qui in quanto insieme ad altri utenti grandissimi appassionati del PCI pieno... cmq @Extreme™ non ti preoccupare di @thenightflyer non credo se la sia presa ma lui frequenta i forum a tratti 🙂

@Extreme™non conosco bene la periferica.. ma al più' su OSX vedi se ci colleghi qualcosa a questa ma potrei sbagliare

tanto per giocare... per vedere se funziona tutto ci devi attaccare le periferiche thunderbolt a freddo, a caldo etc... punto 🙂 State diventando (anche l'amico @thenightflyer) seguaci di kgp 😛 😛 lui la capisce la battuta 😉

@Extreme™quello che c'e' li e' puramente un fatto estetico..guarda qui: io ho tolto anche Nvidia da qui...pensi che non mi funzioni la grafica?

non credo sia importantissimo anzi forse per te si.. ma la parte platforminfo e' un disastro 🙂

ciao Benvenuto metti in firma il tuo sistema, cosi' chi puo' darà un parere più' mirato in generale comunque tra SSD e NVME per il caricamento di sistema non c'e' grossa differenza La maggiore velocità NVME sarà più' evidente se utilizzi applicazioni audio video che fanno uso intensivo dei dischi In generale il boot su un sistema SSD/Nvme di OSX da quando ti compare la scelta del boot loader dura pochi secondi se il pc e' configurato a dovere

I would like to share something that could be useful for Full PCi tab lovers in about my Mac / System Report /PCI from Proxmox shell (this naming for path is for latest 6.2 proxmox VE installation: nano /usr/share/qemu-server/pve-q35-4.0.cfg you will see: GNU nano 3.2 /usr/share/qemu-server/pve-q35-4.0.cfg #[device "ehci"] # driver = "ich9-usb-ehci1" # multifunction = "on" # bus = "pcie.0" # addr = "1d.7" #[device "uhci-1"] # driver = "ich9-usb-uhci1" # multifunction = "on" # bus = "pcie.0" # addr = "1d.0" # masterbus = "ehci.0" # firstport = "0" #[device "uhci-2"] # driver = "ich9-usb-uhci2" # multifunction = "on" # bus = "pcie.0" # addr = "1d.1" # masterbus = "ehci.0" # firstport = "2" #[device "uhci-3"] # driver = "ich9-usb-uhci3" # multifunction = "on" # bus = "pcie.0" # addr = "1d.2" # masterbus = "ehci.0" # firstport = "4" #[device "ehci-2"] # driver = "ich9-usb-ehci2" # multifunction = "on" # bus = "pcie.0" # addr = "1a.7" #[device "uhci-4"] # driver = "ich9-usb-uhci4" # multifunction = "on" # bus = "pcie.0" # addr = "1a.0" # masterbus = "ehci-2.0" # firstport = "0" #[device "uhci-5"] # driver = "ich9-usb-uhci5" # multifunction = "on" # bus = "pcie.0" # addr = "1a.1" # masterbus = "ehci-2.0" # firstport = "2" #[device "uhci-6"] # driver = "ich9-usb-uhci6" # multifunction = "on" # bus = "pcie.0" # addr = "1a.2" # masterbus = "ehci-2.0" # firstport = "4" # FIXME: Remove this audio0 device at the next possible time # see: https://pve.proxmox.com/pipermail/pve-devel/2019-July/038417.html # https://pve.proxmox.com/pipermail/pve-devel/2019-July/038428.html #[device "audio0"] # driver = "ich9-intel-hda" # bus = "pcie.0" # addr = "1b.0" [device "ich9-pcie-port-1"] driver = "pcie-root-port" x-speed = "16" x-width = "32" multifunction = "on" bus = "pcie.0" addr = "1c.0" port = "1" chassis = "1" [device "ich9-pcie-port-2"] driver = "pcie-root-port" x-speed = "16" x-width = "32" multifunction = "on" bus = "pcie.0" addr = "1c.1" port = "2" chassis = "2" [device "ich9-pcie-port-3"] driver = "pcie-root-port" x-speed = "16" x-width = "32" multifunction = "on" bus = "pcie.0" addr = "1c.2" port = "3" chassis = "3" [device "ich9-pcie-port-4"] driver = "pcie-root-port" x-speed = "16" x-width = "32" multifunction = "on" bus = "pcie.0" addr = "1c.3" port = "4" chassis = "4" ## # Example PCIe switch with two downstream ports # #[device "pcie-switch-upstream-port-1"] # driver = "x3130-upstream" # bus = "ich9-pcie-port-4" # addr = "00.0" # #[device "pcie-switch-downstream-port-1-1"] # driver = "xio3130-downstream" # multifunction = "on" # bus = "pcie-switch-upstream-port-1" # addr = "00.0" # port = "1" # chassis = "5" # #[device "pcie-switch-downstream-port-1-2"] # driver = "xio3130-downstream" # multifunction = "on" # bus = "pcie-switch-upstream-port-1" # addr = "00.1" # port = "1" # chassis = "6" [device "pcidmi"] driver = "i82801b11-bridge" bus = "pcie.0" addr = "1e.0" [device "pci.0"] driver = "pci-bridge" bus = "pcidmi" addr = "1.0" chassis_nr = "1" [device "pci.1"] driver = "pci-bridge" bus = "pcidmi" addr = "2.0" chassis_nr = "2" [device "pci.2"] driver = "pci-bridge" bus = "pcidmi" addr = "3.0" chassis_nr = "3" [device "pci.3"] driver = "pci-bridge" bus = "pcidmi" addr = "4.0" chassis_nr = "4" In there I commented many lines (old USB related) , this to have a better and clean situation in PCI device output in app like dpcimanager or Hackintool My tries it is always related to acquire a perfect functionality on internal audio I miss 😉 with this emu vm config I achieve this: so a bunch of EHCI and UHCI device are not loaded anymore in my system..and functionality of it seems to be the same. From picture above you can see some stuff also passed from the pve-q35-4.0.cfg file, I mean QEMU PCI-Pci bridge.. I am trying if is possible to avoid also some of this loading.You see also other stuff (first 6 lines) it seems not present in this file.. Main task/goal could be to inject here some devices we have in our rig? We will see Previous situation without commenting those lines: here less controllers passed..it is a VM I use to test so I pass few devices! DO NOT DO IT IF YOU PASS USB MOUSE OR KEYBOARD OR OTHER DEVICE AS A SINGLE USB IN WEB INTERFACE

If you have windows installed you can use it in my case I use grub bootloader (proxmox) to boot and decide what I want use you have to find a solution for you better for you I mean 👍

@lvtzi would use a smaller drive for proxmox but it is a your choice as advice starts more simple you can and then when you know what are you doing you can go deeper

proxmox start very fast..and when you have your system well calibrated you can start in automatic way also your VM so you click on your power button and you reach your OSX desktop 🙂 for proxmox I have a SSD Samsung 840 Pro in a cheaper external enclosure 🙂 in my test I have had also for proxmox a cheaper laptop 2.5 '' mechanical hd... in my opinion if you do not use 100000000 VM you can use a small disk for proxmox..so you can also backup entirely in a flash..then you can have different disk with different OSX as a real pc/hack/Mac @lvtz have you a working OSX in this system or it is your first experience?

la tua CPU senza quello 0xF01 verrebbe vista come Sconosciuta mettendo quel type ti da il nome Xeon (che e' presente nei veri mac) La tua cpu non e' utilizzata su un vero mac ma e' solo estetica

Hi @lvtz USB controller is integrated on my motherboard and in the main guide I show where I connect my "proxmox" disk. in 1) and 2) question you mix some different subject.. to install Proxmox you have to create an USB Pen (CD/DVD or what you desire) to install it Then you can choose a disk to install Proxmox (proxmox = linux) I have chosen an external USB disk..why? in this way I have all others controller (sata, NVME, and so on to pass to my VM) Best solution is to have your guest OS system in a separate drive from Proxmox disk ie if you have now a working OSX on your system you can use it with only a proper EFI to boot with it.. if you instead install OSX on a file, you can have it on your Proxmox disk..in my opinion it is better to use Proxmox disk only for few things and leave all other OSX separated from it so you need: 1) an USB/CD/DVD for iso installation file 2) boot from this one and from here you have to configure Proxmox (5 minute of your time) 3) in there you choose disk fr proxmox installation (in my case an external disk on back USB) 4) then you can create following the instructions your VM if you have an existing OSX on a separate disk you can try to "pass" that disk..I did for my NVME High Sierra Be prepared to solve different problems..but when you succeed in this task you will be happy 😉

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) Subsystem: ASRock Incorporation FCH SMBus Controller [1849:ffff] Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:66af] (rev c1) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:081e] Kernel driver in use: vfio-pci Kernel modules: amdgpu 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20] Kernel driver in use: vfio-pci Kernel modules: snd_hda_intel 05:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: ASRock Incorporation Starship USB 3.0 Host Controller [1849:ffff] Kernel driver in use: xhci_hcd 23:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:66af] (rev c1) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:081e] Kernel driver in use: vfio-pci Kernel modules: amdgpu 23:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20] Kernel driver in use: vfio-pci Kernel modules: snd_hda_intel 25:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: ASRock Incorporation Starship USB 3.0 Host Controller [1849:ffff] Kernel driver in use: xhci_hcd 25:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:d102] Kernel modules: snd_hda_intel 43:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation Device [1987:5016] (rev 01) Subsystem: Phison Electronics Corporation Device [1987:5016] Kernel driver in use: nvme 44:00.0 USB controller [0c03]: ASMedia Technology Inc. Device [1b21:3242] Subsystem: ASMedia Technology Inc. Device [1b21:3242] Kernel driver in use: xhci_hcd 45:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:07b1] (rev 02) Subsystem: ASRock Incorporation AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1849:d107] Kernel driver in use: atlantic Kernel modules: atlantic 48: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: xhci_hcd 48: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: xhci_hcd 49: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: ahci Kernel modules: ahci 4a: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: ahci Kernel modules: ahci 4b:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation Device [1987:5016] (rev 01) Subsystem: Phison Electronics Corporation Device [1987:5016] Kernel driver in use: nvme @Driftwoodin my experience you can pass all of these listed above using previous FLR posted Kernel patch It is also possible to have some problem if you use sata or nvme disk (for proxmox installation)..I use ASMedia usb 3.2 type controller for Proxmox so I do not share with proxmox my sata or nvme controller when VM starts, and I pass entire sata/nvme controllers to boot in "vanilla" OSX/Windows VM I would like also to suggest to comment amdgpu,radeon and nouveau lines in blacklist.conf to have a more friendly AMD system (you can run command from this instead to use another pc/device to modify things) if you try..be prepared to solve possible problems 🙂