fabiosun

si ora più' del log e' capire se hai tutte le funzionalità critiche come 1)Reboot 2)shutdown 3)Sleep/wake poi se ti vuoi divertire puoi provare a togliere RebuildAppleMemory ed attivare solo EnableWriteUnprotector.... e se va pure da te farai parte di una sezione tipo scisma di Martin Lutero o simili andando contro oltre che a Dortania....(che me ne frego ampiamente) anche alle sacrescritture opencoriane 🙂 🙂 PS scherzo rimani come sei che e' corretto!

disabiterei il rosso di sicuro e poi se parte toglierei anche Devirtualize

ok allora per me puoi ripulire il config se desideri seguire le linee guida dei devs di opencore

config.plist.zip scusa non avevo salvato il 67

@netgear https://mega.nz/file/5CcylBqb#vXclBGiQkl2yMyx_ZavPz8c6OW8rpYnnAAU88L4inXY questa e' identica alla tua Debug (target 67 e .efi versione 084 debug)

MAT come lo hai? io partirei da li è lascerei dortania per altri scopi😂😎

<key>RebuildAppleMemoryMap</key> <true/> <key>SetupVirtualMap</key> <true/> secondo me uno e' di troppo ma se metti una debug vedi la faccenda del MAT0 e o MAT1 e poi metti quelli indicati dal doc di opencore anche se e' possibile che ti funzioni regolarmente anche in diverse combinazioni

non ricordo che patch abbiamo usato per il kernel (se quella di Algrey o quella di Shaneee) Se abeam usato Shaneee e' un problema che hanno alcuni nel caso va usata al suo posto quella di Algrey che ha come controindicazione che manda più' piano la GPU in molti casi

grazie per i complimenti, ma non servono! 🙂 Fai solo attenzione che dagli ultimi monterey e soprattutto su Ventura salta il supporto per molte schede di rete Quindi potrebbe essere un problema Non ricordo se la tua e' ancora supportata o meno tramite kext o tramite bootarg quando sarà capiremo come muoversi!

EFI.zip Se vuoi provare questa eì la precedente aggiornata a Opencore 084 con alcid=5

se stai usando la EFI postata qualche mese fa, per Monterey e Ventura andrebbe aggiornata alle ultime versioni di Opencore (bootloader, driver e kext)

@kokoz I would not like to kill the illusion that it could go But these you mentioned are the same results that were achieved some time ago with Proxmox Unfortunately there are some bridges related to thunderbolt that you can't get through Then, on motherboards that don't see thunderbolt in the bios, it's impossible to see the USB part of it USB can be used to charge e.g. Apple Watch, but you don't see connected peripherals and this is not only in proxmox but also in bare metal Boards such as designare, on the other hand, have thunderbolt-related options in the bios, and therefore also show connected USB devices such as disks, hubs, etc. if you like attach your full ioreg as file

Before was impossible to pass some thunderbolt bridge so we ever had the chance to see it working properly It seems to be the same of your results

I do not know if USB mapping for TRX40 chipset is useful What I know that some TRX40 gigabyte users use that SSDT USB reset in its motheboard It should be modified following your IOREG ACPI path I would try to use keyboard and mouse on other backplate USB ports if they are available only to see if errors is the same but no more ideas and I do not know what is changed in OSX internal USB 2 drivers for your previous OSX used and working faster than latest you are trying by now sorry!

this could be the culprit maybe you need to map them ( but I can't solve this, no experiences)

Archive.zip put SSDT in ACPI folder of your EFI and overwrite your config.plist with this one in zip backup yours

@shrishahave you usb led connected in your motherboard ? could you take a photo of your internal USB 2.00 ports? or are they empty like this photo?

@shrisha could you try to disable on bios your ethernet card? both do not work from Monterey and greater if you have ethernet cable connected on them it could creates problems in OSX

config.plist.zip questo non dovrebbe dare errori se lo ricontrolli controlla anche qui se hai aggiornato drivers e kext

no solo il config se hai solo quegli errori

run and save as then zip it and post it does not work for us from Monterey and greater OS

have you an USB audio device connected? have you tried to disconnect or to change its usb port? also you can try to enable a quirk (XHCIPortLimit) I do not think it is useful for us also a user with a similar motherboard use a SSDT USB reset I do not know also if it is useful or for what it is useful SSDT-USB-Reset.aml.zip if you want try you have to copy in your ACPI folder and then declare it in your config plist in ACPI section (and probably to adjust for your IOREG output before)

post a picture like this and then check if you use internal USB 2.0 ports

mmh I think no try to disable wifi on bios ( I do not know if it also disable BT)

also a simple try could be disabling from bios BT usually BT take the power from internal USB2 and if with it disabled you do not have those thousand of lines, maybe your Motherboard needs USB mapping (internal port) Usually to set them as internal