Leaderboard

@Vladimiro tutto questo cosa c'entra con hackintosh? Senza offesa ma basterebbe fare proprie ricerche... google è tuo amico.... Non siamo qui per fornire supporto dalla A alla Z riguardo a windows o altri sistemi operativi. Sul web ci sono innumerevoli guide, su come fare, installare driver etc.. Topic Chiuso perchè è andato completamente fuori "tema".

si ma il reset NVRAM esegui nuovamente l'aggiornamento nel senso che lo scarichi di nuovo

Porta pazienza @morfy se proprio devi riavvia e resetta la nvram dalla Guii di Open Core al prossimo riavvio va da favola almeno a me ha fatto cosi e poi è andato dritto come un treno fino alla fine tutto da solo problemi zero ed è scattante più di prima, spero ti aiuti a risolvere Saluti Perdu

nel frattempo ho aggiornato, nessun problema apparente.

BS 11.2.1 released but nothing of interest to us, mainly for MacBook Pros.

@mac-dev spero ti renderai conto che non hai risposto a nessuna delle domande poste quindi? che pc? sono mica veggente

Nuova 11.2.1 build 20D74

hai Clover ultime release, i quirks, configurati, openruntime come gestore memoria e ssdt ad hoc o ssdt-basic???

non ci pensare nemmeno tra le altre, ho applicato questo nell'ultimo config di OC bene ora che hai tutte le porte USB aperte, allaccia le cinture di sicurezza e: poi armati di pendrive USB 2 e 3 si avvia ioreg e una alla volta si infila ed espellono entrambe le pendrive in tutte le porte presenti, si prosegue con ioreg -> file -> save as si salva, si comprime e si posta nel proprio thread o in quello dedicato assieme alle ACPI estratte ed eventualmente la EFI senza all'interno la cartella APPLE o Microsoft che appesantiscono il tutto e non servono a niente. Nota 2 - estrarre e postare le ACPI Spesso viene fatta questa richiesta, ecco come fare: CLOVER: riavviare l'hack e fermarsi nella GUI (dall'inglese Graphical User Interface) di Clover, premere il tasto F4 e aspettare 30/40 secondi (a monitor non succede assolutamente niente) poi avviare regolarmente, montare la EFI, comprimere e uplodare la cartella origin che si trova nel percorso EFI --> CLOVER --> ACPI OPENCORE: scaricare dal repository Acidanthera la versione debug della release di OC in uso https://github.com/acidanthera/OpenCorePkg/releases sostituire bootx64.efi e opencore.efi nel config Misc --> Debug abilitare/impostare su yes/true la voce SysReport riavviare e al desktop montare EFI e nella root sarà presente una nuova cartella SysReport con all'interno una cartella ACPI, comprimere e allegare sul forum quando richiesto e ripristinare versioni release dei file

Devi cercare tutti i driver, di solito se vai sul sito del produttore con un altro pc li trovi tutti inserendo il modello esatto di notebook. Masterizzali su un CD vecchio stile e installali. Comunque ti consiglio di masterizzarti su DVD una iso di Windows 10, puoi fartela con Windows Media Creation tool, sicuramente riconoscerà molti altri drivers in automatico rispetto a Windows 7.

Grazie per le risposte, per quanto riguarda la iGPU, alemo nel mio caso ho dovutto aggiungere a mano la configurazione delle "porte", in pratica delle tre uscite video della UHD 630 una sola è utilizzata per la hdmi presente sulla z390, le altre 2 non sono ovviamnte utilizzate, ora con il monitor 4k che ho non ne voleva sapere di partire, leggendo la documentazione di WG e provando un po' così sembra funzionare.

@DriftwoodDo you use Davinci resolve for your job/hobby? if so can you test Candle scene benchmark if you have two radeon VII installed? I would like to see your results 🙂 and of all people who want to try

@cj750 send us a glass of scotch 😂 and yes it is a big step for you now you have the hope it can work also for you👍

I don't know if it is simpler or not than other motherboards, but I always wondered why other users need to block things in vfio when in my case you just have to pass them in the virtual machine configuration to be automatically passed to vfio. ... I started this journey by doing things as recommended by the proxmox wiki..to cross out all the useless things for me

@DriftwoodI thought you want to see other result.. 🙂

Your vga is on 03:00 group?

Sooner or later I'll have to switch to an AMD graphics card too. But all these small / big problems scare me a little 🙂

I do not think it will change your Proxmox World, but maybe it could help to solve 99 code error?

Dear Customer, Thanks for your mail and feedback. Have a nice day. ASRock TSD ________________________________________ 寄件者: Fabio**************** 寄件日期: 2014年1月21日 下午 02:11 收件者: Asrock TSD 主旨: Re: Re Cold boot problem Thank you for your fast answer. Yes i would like to install osx 10.9.2 I have ha success with your 3.90 firmware having OSX working perfectly with X79 Extreme 9 and xeon v2 cpu i have only limited osx speedstep control with msr unlock should be ok today i will try with 3.90 firmware all is working except game blaster audio, it is not supported thank you again Inviato da iPhone > Il giorno 21/gen/2014, alle ore 05:10, Asrock TSD <Asrock_TSD@asrock.com.tw> ha scritto: > > Dear Customer, > > Thanks for contacting ASRock. > > Please update BIOS L3.91 from attached file for try, it unlock the specific bit of MSR. > Can you tell us what's the application of that, install Mac OS? > > Thanks for your mail. > > Cheers, > ASRock TSD OT 🙂

Deb files are not relevant for nvme I think

pve-blacklist has stuff inside you should have in blacklist.conf file..not there for your gpu passthrough problem take a look here I added an experience of an user with 5700XT

if you have only an ethernet cable connect seems to be impossible to have both internet navigation and web interface access .. I did some tries but deleting vmxnet in config and passing Aquantia (which is the same I have installed proxmox) Aquantia take IP address of "web interface" so it is not possible to reach Proxmox Host if I manually insert a different IP I can navigate on the web but always web interface is not reachable (or vice versa) I stay with vmxnet which is bridged with my acquantia I have a little experience in this field so my "finding" could not be so accurate

and this link can be useful to understand how I proceeded when I understood the situation better. However, it is important to follow the main guide to learn some (or presumed) bases for me 🙂

@Rox67er i have tested during this journey all bios available for my motherboard with all of these i have the same functionality and group separation i do not think Agesa is your problem now also your motherboard has agesa 1.0.0.4 with latest bios posted few messages above ehm sorry for asrock 1.0.03 patch c only for now

@Driftwoodall my cores and about 119 Gb of my 128 Gb installed System run perfectly in this way If I have had to limit my system only of 1 core less..I would have thrown proxmox out of the window! 🙂 I can push a bit memory but if I exaggerate the system becomes unstable agent: 0 args: -smbios type=2 -cpu host,vendor=GenuineIntel,+invtsc balloon: 0 bios: ovmf boot: d cores: 64 cpu: host efidisk0: local-lvm:vm-100-disk-1,size=4M hostpci0: 21:00,pcie=1,x-vga=1 hostpci1: 46:00.1 #USB hostpci10: 46:00.3 #USB hostpci11: 47:00 #SATA hostpci12: 48:00 #SATA hostpci2: 01:00.0 #NVME hostpci3: 02:00.0 #NVME hostpci4: 04:00.3 #USB hostpci5: 23:00.3 #USB hostpci6: 23:00.4 #Audio (not useful) hostpci7: 44:00 #I211 hostpci8: 45:00 #I211 machine: q35 memory: 121856 name: sierra net0: vmxnet3=xxxxxxxxxxx,bridge=vmbr0,firewall=1 numa: 0 ostype: other sata0: local-lvm:vm-106-disk-0,cache=unsafe,size=48G,ssd=1 #catalina on a VM disk scsihw: virtio-scsi-pci smbios1: uuid=43051c32-3e2e-4f80-b7cc-d50def662b0b sockets: 1 startup: down=20 tablet: 0 vga: none vmgenid: xxxxxxxxxxxxxxx

This kind works fine

I hope many people, also silent people following here without participating, share their experiences to do a more useful and generic guide possible. i take note of all your observation and when I can verify by myself I will add o. Original post to improve my guide😉

Apple hates our Realtek 2.0 audio sorry I choose wrong Realtek 2.0 audio on my sound settings it is gone again now, no audio Also in 10.15.6 first beta is working well and the only problem is jack detection as before Cheap usb audio is always working fine as in 10.15.5 release

beta 10.15.6

my advise is to install proxmox on a minimal SSD disk connected on USB type c (ASMedia) this escamotage will allow you to pass easily all others controllers you have like NVME, SATA, USB (USB with all caution you must have also reading entire this thread) In my particular case I have all sata disk connected and two NVME passed happily.. I think also for your creator could be the same then everyone must adopt best way for his pipeline...and for now..if you follow what I have written here and in the guide..with latest 10.15.5 you have also a perfect working internal audio.. Only with latest 10.15.5 because with previous version scratch could appear some time...but it is a driver problem with our "weird" usb audio (two chip for this task)

@Rox67erif port 8 is an ASMEDIA Port it seems pretty identical to my situation Connecting there Proxmox disk you can pass all others controllers (SATA,USB,VGA and so on) easily This DO NOT MEAN you do not have lag problem If you passthrough all controllers (also problematic one like Audio /usb controllers), but you can pass both sata controllers and use well all disk connected to them as I do

Are you sure about this? 23:00.4 in my case is Matisse audio 46:00.1 and 46:00.3 are many usb I think internal 3.2 slot and a bunch of rear usb

@Driftwood47:00.3? Don’t use it?

@Driftwoodare you in 10.15.5?

@iGPU it is very weird all things have been happened with 2 different motherboard and different linux distros I can't say what you can do more to debug.. I can only say that in my experiences (with all bios available on my motherboard (I have tested all during this experience)) I have no difference behaviour IOMMU group are always the same as it is always the same group separation.. so it is difficult for me to understand

@Driftwood Apple has worked for me 🙂 catalina 10.15.5 solved my audio problem and then I have said to Pavo this and also him reached my same situation with his trx40 system (audio perfect but jack detection problematic) Now I think he is trying with Unraid and see if there could be the same or better. For now I stay in Proxmox. system is production ready and no so much time to invest to learn Unraid

Also I do not use actual patch you can find in pavo GitHub but older ones. I think he is doing multi platform experiment with this patches to try to solve Problem for other platform. I think also @Pavo could confirm this as he did in private few hour ago @iGPUif you have another working Linux you can compile by yourself I prefer @Pavogive you clear instruction because he has helped me to understand how. to all audio is working and the only problem now is audio jack Detection. by the way now i think pavo had some success we audio in unraid. Maybe it could be useful also in proxmox understand well how Unraid works

@Driftwood you are not informed well😀 Audio is working well in latest Catalina and it is not flr patch related

Thanks @iGPU it is similar to mine 04:00.3 25:00.3 could be passed with flr patch (148c) 48:00.1 and 48:00.3 pass as is without patch 44 is asmedia..i do not pass it because i have proxmox on it i do not consider any additional device you can have but msi creator has pretty similar group also @pavo has one and he is achieving the same my result

This is my last schema. I can pass more stuff but all usb in my motherboard are owned by 46:00 controller...ah also audio is in there VM OS system limit USB3 detection (High Sierra) Catalina and Windows 64 have a better USB management (their drivers allow to see USB 3 devices if connected . So to a clean installation in my MSI TRX40 Pro 10G I do not use any FLR patch (no need to passthrough 23:00.3, 4:00.3 USB Controllers or 23:00.4 audio controller it is also mandatory to pass 4:00.3 and 23:00.3 (FLR Patch 148c) (do not pass 23:00:4 audio controller) All I need is 46:00, 4:00.3 and 23:00.3 controllers which I can passthrough in two different way: Hostpci5: 46:00 or hostpci6: 46:00.1 hostpci7: 46:00.3 then hostpci7: 04:00.3 hostpci7: 23:00.3 I think also for you should be the same (you have also to find your main USB controller and your exact groups). Interesting is also to check this schematic picture, inside USB/audio/chipset connections with AMD CPU:

@iGPU i cant say where your problem is but i am pretty confident is about proxmox if you see also on proxmox forum the staff answer are often not clear..like “you are on bleeding new hardware untested and so on “ apart of this i think proxmox is the best linux distro for our goal and maybe more simple to master in many aspect. As advise for all and also for me is to pass less things possible related to usb..because main problem are there in relation with osx driver and qemu pve.cfg. i loose so many time to have a working audio in highsierra when in windows it was working well and the solutions was in front of my eyes...driver. catalina solved this problem and i am using the same linux and vm config previously used. and also catalina is using audio driver in a worst way than windows..but now it works. So this is a fact not in our hands. i can now using my system professionally with highsierra using dp audio but i have to accept some limitation (usb 3 device are not seen if i pass controllers or single device) but system is solid rock and fast as windows in cpu/gpu jobs Osx for me has a sense only with highsierra and catalina for now it is a no solution for me.. also in catalina i could no accept amd gpu reset bug! but in general our needs could differ

@iGPUare your memory tested? I think also you have verified this failure in a different os environment than proxmox/OS X

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

@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

If I understand well it seems more probable it is related to amd Gpu reset bug?

@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?

@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)

@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

10.15.5 combo update: https://updates.cdn-apple.com/2020/macos/061-78576-20200520-5dfa5569-76e4-4b87-b11c-9e53eb7651a4/macOSUpdCombo10.15.5.dmg