Jump to content

fabiosun

Supervisor
  • Posts

    11,136
  • Joined

  • Days Won

    510

Everything posted by fabiosun

  1. There is no safe efi because this is an unexplored territory patches, boot loader and so on we have to find a proper mix of combinations of it to have, maybe a stable system. if you analyze your boot log I think now you will find in it some errors like unsincronized Tsynch Cpu or similar.. so maybe additional kexts are needed.. in my case executing cpu benchmark with cb 15 or 20 could cause an instant system reset.. using some apps instead like adobe or davinci need perl command patches ..but it is an Amd rig features for now
  2. when we will have more stable bare metal system we could create a sort of database...(config/bios I mean) in my case CSM is off and all settings are the same I use in Proxmox Bare metal for my standard is not stable During benchmark some time it reboots In proxmox I never had a reboot... But happy I can use also this with a proper GPU acceleration
  3. No, you have not missed any thing For my personal experience different users with gigabyte master or extreme have had some problem..but I have not tested directly this thing Some user with designareEx have had success @Jaidy
  4. io invece vorrei capire @SemanticA anche se sai difenderti..sei stata offesA da qualcuno?
  5. cmq ultimamente un sacco di gente preparata sul forum.. che bello 🙂
  6. Ok, I have removed all my ssdt and used some booter quirks I do no use in Proxmox and now system does not reboot randomly 🙂
  7. Cuda benchmark I am using same disk I am using in Proxmox.. I will carbon copy it in a new ssd and I will patch all app (adobe and davinci) to do real life benchmark
  8. cb 15 FPS in baremetal 50 cb 15 FPS in Proxmox 120 to interested people, same Proxmox EFI in config added all patches as you can find in this thread
  9. a bit OFF Topic Clover boot loader booting fine on an AMD 3950 x thanks @iCanaro for filming 🙂 more infos here:
  10. Mmio adjustement could be tricky if you do not have any big problem i will stay away from touch it trx40 works for now but it is not clear why.. patches are the same, bios version in my case seems to be irrelevant Only opencore could have done the job for us but opencore’ s devs do not support AMD cpu so it is so difficult to understand and also on AMD-osx people is not interested on a ‘niche’ product as trx40
  11. poi fixshotdown sembra un film di Nicole Kidman e Tom Cruise cmq mi appunto il consiglio 😛
  12. non ho capito hai provato a partire con la spunta/flag attiva su nv_disable? perche' se non ti parte cosi' e' cambiato altro posta una EFI che ti funziona ed un hackinfo (e' una app che trovi in download) Comprimi e poi cerchiamo di arrivarne a capo 🙂
  13. quando sei nel menu iniziale di clover premi spazio e poi metti la spunta su nv_disable toglila se c'e' da nvda_drv e vedi se parte o se hai sempre lo stesso blocco
  14. I have had to revert to old fabian 5.78.1 kernel for me this one is latest which works perfectly With 5.8.x I have an instable system. it reboots my VM in a random way I have associated this problem to my 2 10TB exsata disks or to my two 6tb data disks (not seen in osx because they are formatted in windows software raid) these disks some time appear after few minutes in desktop..and often with 5.8.x kernel produce a vm reboot with 5.78.1 this fact does not happen and system is perfect
  15. quando il driver si attiverà ne potrai usare anche quattro rimetti un config che ti arriva al desktop (senza accelerazione) e poi modifichi il config che ti ho messo con clover configurator: puoi anche con lo stesso config che ti si blocca quando vedi il menu di clover premi o (options) premi invio dove vedi la scritta -v (boot args) e ci scrivi vicino nvda_drv=1 e vedi se cambia qualcosa questi sono i passaggi corretti per attivare il driver se ancora si blocca allo stesso punto devi provare a verificare meglio i tuoi settaggi del bios
  16. Siamo quasi al login prova a forzare il caricamento del driver anche nei boot args
  17. 5) many apps need to be patched to work and some does not work well as in proxmox 6) if some thing change in the kernel...pufff ..our rig does not boot anymore these 2 points are common in every AMD rigs 3) Nvidia web driver seems to have problems to activate (only for me maybe)
×
×
  • 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.