fabiosun
-
Posts
11,473 -
Joined
-
Days Won
553
Content Type
Profiles
Forums
Events
Downloads
Everything posted by fabiosun
-
Se ti vede le usb hai raggiunto il massimo che puoi fare senza avere periferiche thunderbolt. poi se ti vuoi divertire scarica dcpimanager e prova a vedere se vedi qualcosa in pci device non credo ma è inutile in generale in quanto non hai le periferiche
-
si no 🙂 scherzi a parte io non avevo thubdebolt (periferiche) avevo la tua stessa scheda thunderbolt Ho messo il driver in windows messo sl0 in bios potevo far partire osx anche dalla sua USB e vedevo in ioreg qui da te non mi pare di vedere niente ah chiaramente sempre il thunderbolt attaccato e do per scontato che non sia rotta per prova puoi metterci una penna usb qualsiasi anche usb se la hai e vedi che accade ma se non la registry in windows non credo la vedrai mai il driver fa qualcosa..che se cerchi te lo spiegano bene
-
si dici che capisci bene ma non mi leggi bene 😛 se non ci attacchi thunderbolt (periferiche non vedrai mai niente in PCI Se ci vedi qualcosa puo' essere ssdt tarocco cmq nel bios delle mie precedenti schede madre x99 ed x299 la scheda andava montata su slot specifico e nel bios in security bisognava mettere SL0 prima di questo la scheda andava attivata in windows altrimenti su osx nisba questo e' quello che so.. poi se posti un ioreg qualcuno lo guarderà 🙂
-
no da quello che sapevo io senza periferiche non vedi nulla di base servirebbe un IOREG..e gengik84 che te lo controlla ma senza periferiche tb non fai nulla in pratica ssdt serve per fare vedere le periferiche anche dopo che sei partito , a caldo, a fereddo collegandole e scollegandole etc..ma se non le hai che provi?
-
@Driftwood I asked before post if you want your vm config your lspci -nnk output your modules file your kvm.conf file..and all thing could be useful motherboards are different and you have a radeon which could be more problematic...but solutions could be similar for others controller.. Stay for now with Imacpro1.1 @AllubzV I think did an example to explain that more GPU are possible also in real Mac (and obviously in our hackintosh)
-
in security level 0 o simile poi la scheda va attivata regolarmente da windows mettendo i suoi driver.. e poi serve il famoso ssdt miracoloso hai periferiche da provare thunderbolt? le usb dovrebbero andare facile
-
ok a big improvement for me.. trying to solve audio problems I have had an idea to try to pass impassable USB controller in my case they had an id like this: 10:22,148c so I asked @Pavoto compile for me new kernel adding this patch: diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c index 308f744393eb..9806bff34b9b 100644 --- a/drivers/pci/quirks.c +++ b/drivers/pci/quirks.c @@ -4999,6 +4999,9 @@ static void quirk_intel_no_flr(struct pci_dev *dev) DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1502, quirk_intel_no_flr); DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1503, quirk_intel_no_flr); +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x148c, quirk_intel_no_flr); +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x1487, quirk_intel_no_flr); + static void quirk_no_ext_tags(struct pci_dev *pdev) { struct pci_host_bridge *bridge = pci_find_host_bridge(pdev->bus); -- 2.24.1 He compiled it successfully and I have inserted in my Proxmox now all controller are passed under vfio driver (in my case no need to declare it on vfio.conf or block any drivers) Pavo added this patch in his GitHub . I think this could also be useful to pass other problematic controllers (ie thunderbolt?? ) 🙂 below my passed controller now: 04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: Micro-Star International Co., Ltd. [MSI] Starship USB 3.0 Host Controller [1462:7c60] Kernel driver in use: vfio-pci Kernel modules: xhci_pci 23:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: Micro-Star International Co., Ltd. [MSI] Starship USB 3.0 Host Controller [1462:7c60] Kernel driver in use: vfio-pci Kernel modules: xhci_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 for now I haven't tested if I have additional problem using this patch.... we are on the bleeding edge..using not tested hardware for our task 😉
-
allora puo' andare..ma e' un campo abbastanza complesso
-
@paul lo hai il Thunderbolt header sulla piastra madre? altrimenti per farla funzionare e' un delirio vero... @iCanaroha una Asus Thunderbolt 3 Ex ma se non ha l'header la piastra meglio non pensarci per nulla
-
@AllubzV yes i think so for internal device..also i have bought a cheaper USB audio device and it has the same problem For your problem try to see if you have your KVM.conf file (MSR related) in my case that was the problem
-
Hi 1) yes you can use it* 1b) no no clean installation is required 2) if you want to use an exist OSX instalaltion yes, if you use a disk in a virtual file no 3) success dipend from your skill and patience. It is not simple but many users with your same rig (a vanilla Patches supported system) are trying proxmox having less problem with compatibility for app (0 problem) and better gpu performances It is Tricky but it could work 🙂 * you have to pass your disk controller or single disk (SATA, NVME..) To have a detailed answer you have to read all the post here and also in main guide.. you can also check @Pavo GitHub , there you will find a system more similar to yours
-
@Driftwood if better results are obtained with a VM file disk..they are not accurate (sorry for this 🙂 ) if instead they are achieved with a passed drive or entire controller...are very good almost impossible but very good @iGPUyou can use multiple gpu (not in crossfire or SLI), software like davinci resolve and other have a great benefit with dual gpu system
-
I have had also before more than 10 pci device passed i do not see big improvement for us backup your main proxmox config files in my case I have updated via shell then I did also a fresh installation with new iso without problems
-
Hi Paul, this "hole" for audio related part is a bit risky by now. Internal audio of TRX40 mb is bridged (maybe) with usb controller so this for now it is problematic I have bought also a cheap USB sound adapter and also this has problems. Display Port audio from my Nvidia GFX is perfect and I have tested with it audio features ( I am not an audio expert) but I can affirm which Proxmox/osx you can use any plugin without problem if this plugin works well in OSX Proxmox/osx installation is not affected from problem you may have with Vanilla patches method..
-
@paulthesparkywelcome here yep I did test you said without screen software recording I have 580 tracks as I said in this thread or in the main guide thread 🙂 take a look if you want also in this channel: FYI we have here this system working from first days of February 🙂 so a bit first of Theresa 😛 we did a free guide to build from yourself if you have one 🙂 🙂
-
@iGPU I monitor my temps with my motherboard led code display in bios there is an option to monitor temps trulyspinach app does not work one kext seems to output a missing cpu Id in verbose
-
I did..in my case yes..no improvement but it is latest available so could have some benefit I cannot see by now I f you are unsure stay with old version
-
ok solved 🙂 root@pve:~# pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve) pve-manager: 6.2-4 (running version: 6.2-4/9824574a) pve-kernel-5.4: 6.2-1 pve-kernel-helper: 6.2-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.3-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.15-pve1 libproxmox-acme-perl: 1.0.3 libpve-access-control: 6.1-1 libpve-apiclient-perl: 3.0-3 libpve-common-perl: 6.1-2 libpve-guest-common-perl: 3.0-10 libpve-http-server-perl: 3.0-5 libpve-storage-perl: 6.1-7 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.2-1 lxcfs: 4.0.3-pve2 novnc-pve: 1.1.0-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.2-1 pve-cluster: 6.1-8 pve-container: 3.1-5 pve-docs: 6.2-4 pve-edk2-firmware: 2.20200229-1 pve-firewall: 4.1-2 pve-firmware: 3.1-1 pve-ha-manager: 3.0-9 pve-i18n: 2.1-2 pve-qemu-kvm: 5.0.0-2 pve-xtermjs: 4.3.0-1 qemu-server: 6.2-2 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-1 zfsutils-linux: 0.8.3-pve1 root@pve:~# it was simple..a file....kvm.conf 🙂 🙂 🙂 no improvement for our common problem for now I would like also to remark: useful file for my rig to modify after a clean Proxmox VE 6.2 iso: etc/modules vfio vfio_iommu_type1 vfio_pci vfio_virqfd etc/modprobe.d/kvm.conf options kvm ignore_msrs=1 /etc/default/grub.cfg quiet iommu=pt amd_iommu=on then I have used my previous VM.conf file recreating in it only EFI disk
-
Ok, it is a not new kernel problem related..Probably new QEMU has some conflict with our bootloaders... for now stay away from this or try with a solid backup
-
do not update for now now also my minimal Vm hangs on ++++++++ end seed both with clover 5107 and opencore 0.58 try to revert to old kernel by now i hope it is enough to start again my VM 😂 upgrading deleted my lvm.conf file so this was the reason for the hang on ++++++++ phase (MSR related)
-
https://forum.proxmox.com/threads/proxmox-ve-6-2-released.69647/
-
@AllubzV this could be the command (boot parameter) for me to test...adding where? they say boot argument.. I have tested in grub.cfg with no success for now pcie_no_flr=1022:148c,1462:cb60
-
to all: Maybe it is not well shown in the guide but you have to remember a thing: Clover/OpenCore iso image we upload on Proxmox appropriate folder if associated in our VM config it become a normal bootable EFI as we have in a "real" hackintosh So, if you modify it you automatically modify uploaded iso file in proxmox. ie my clover.iso I have in proxmox now inside has Opencore 0.59 boot loader.. So pay attention on this. In my experience is better to have uploaded a clean and simple working iso you can use only for repair bad things gone wrong, also in my case I have a commented line in VM with opencore/clover working iso that I never modify Usually I boot from EFI in my NVME drive, when things go bad (for osx I mean) I uncomment that line and from OVMF Proxmox bios I choose that iso to boot fine.
-
@iGPU scp command are in the guide and then are also obsolete in some case from an advice @Rocket88gives about using FileZilla ftp client(if you search you can find easily) link here A remainder as you did is good too 🙂 about lane sharing..this could be the big task for all of us togheters multiple "bridge" connection we have.. I think it is also an unexplored territory also for Proxmox guy and maybe in many case Windows VM is not affected from the same our problems because in there more supported stuff is (virtio drivers, spice and so on) I am convincing myself ( 🙂 ) that audio problem is not related to my poor knowledge but it is more a "system" problem I can have it perfectly working but it is not stable at all as it should be and also how Nvidia DP/Hdmi is. I would like to share an example: with many tries I have "a working" Realtek audio I launch DaVinci Resolve to produce some video you can find in macOS86 you tube channel edit video cutting, scribbling audio perfectly.. I put a cross dissolve ( a simple cross dissolve to insert macOS86 logo as a super on main video ) audio scratch during cross dissolve effect... Our system (mine in particular) can work with multiple 8k layer without any problems) but using this problematic audio it fails (I repeat..with DP audio is perfect) so it should be OSX audio driver not working well with VM previously configured part .. Searching on the net many talking about problematic audio in VM but no one gives a solution to try
-
Good, If you think it could help other people and if you want , describe your procedure to have it working 🙂 I have had private conversation with many AMD radeon VII and seems some Radeon VII card has not a UEFI BIOS It is not confirmed directly by me, but it is a sort of "rumours", and this should be the cause of many AMD GPU card users.
