Jump to content

tomnic

Moderators
 View Profile  See their activity

  • Posts

    907

  • Joined

  • Last visited

  • Days Won

    36

 Content Type 

Posts posted by tomnic

    Intel HD 630 e dintorni

    in Off Topic

    Posted

    7 hours ago, Perdu said:

    vorrei configurarlo solo per win che dite potrebbe andare bene 

    Asrock Z690 PHANTOM GAMING 4 Intel Z690 LGA 1700 ATX

    Crucial MX500 500GB 3D NAND SATA da 2,5 pollici SSD Interno - Fino a 560MB/s - CT500MX500SSD1

    CPU Intel Core i5-12400 6 Core 2.5GHz

    AOC 24B2XDAM - Monitor da 24 Pollici FHD VA Panel, speaker, (1920 x 1080, 75 Hz, VGA, DVI, HDMI) Nero

    Simpletek Case Gaming Nero Con Alimentatore 500W | ATX MICRO-ATX MINI-ITX mATX non si capisce se è ATX  

    Corsair Vengeance LPX16GB DDR4 3600 Memoria Desktop, ‎Nero

     

    La build suggerita è buona per il budget indicato, poi un domani metti una gpu compatibile e diventa un Hackintosh ^^

    • Thanks 1

    ASRock Z690 Phantom Gaming 4 + Alder Lake i5 12600k + RX 6600XT Monterey iMacPro / MacPro build

    in Desktop

    Posted

    On 12/27/2023 at 7:37 PM, iLoveOSX said:

     

    Ciao @tomnic

    Grazie per la tua EFI.

    Ho come CPU i7-13700k, rx6600, ram 2x32gb @3600mhz e m.2 samsung 990 pro

    Sono riuscito a concludere l'installazione di Sonoma 14.1.2, ma ho notato che ogni volta il sistema deve riavviarsi 2-3 volte prima di raggiungere la schermata di login.
    Non ho avuto modo (tempo) di verificare altro (mappa usb ecc...)
    Allego la EFI e ioreg. Se dovesse servire altro chiedi pure. Grazie in anticipo! 

     

     

    EFI.zip 10.44 MB · 1 download ioreg.zip 655.95 kB · 0 downloads

     

    Prova a togliere il -v al boot, so che tende a far incastrare le RX 6x00 con windowmanager nella fase in cui deve switchare da modalità testuale a grafica. Se non risolvi può essere colpa del firmware del tuo sabrent, io ho risolto passando a dei lexar, più lenti ma più amati da macOS, o comunque prova ad aggiornarne il firmware se possibile.

    • Like 2

    Improvvisi problemi Logic Pro X su Monterey

    in General Discussion

    Posted

    Se hai il trim attivo lo vedi da qui:

     

    image.thumb.png.579823a7d629c0d3f21dd78c8962c82a.png

     

    Poi alla voce SetApfsTrimTimeout del config.plist di OpenCore puoi settare i valori 999, -1 e 4294967295 rispettivamente e vedere se cambia qualcosa.

     

    Puoi anche attivare o disattivare il trim stesso con i comandi, rispettivamente:

      

    sudo trimforce enable
sudo trimforce disable

     

    Vedi cosa migliora / risolve la tua situazione.

    Mac Pro consiglio vassoio doppio processore

    in Desktop

    Posted

    7 hours ago, Xam said:

    Buongiorno, di recente ho aggiornato il bios del mio Mac Pro 2009 e sono passato da 4.1 a 5.1. 

    Ora vorrei sostituire il vassoio della cpu e passare a quello con doppio processore e aumentare i core da 6 a 12.

    Dato che ho fatto l'upgrade da 4.1 a 5.1 che tipo di vassoio devo acquistare? Posso installare quello di un Mac Pro 5.1 del 2010/2012, oppure devo utilizzare un 4.1 del 2009 ?

     

    Grazie

     

    Devi usare un vassoio di un 4.1, quello del 5.1 ti darebbe problemi di ventole sempre a palla, anche col firmware 5.1, l'SMC è diverso e si incastra con quello nella logic board restante che è 4.1 fisicamente.

    • Like 1

    Nuovo Hack su AM5

    in General Discussion

    Posted

    36 minutes ago, miciola67 said:

    Ciao @tomnic e grazie per la risposta, quindi niente visto che la scheda è nuova per ora non ri faccio l'hack su questo pc , invece è possibile farlo sul pc che ti elenco ora? volevamo venderlo ma se è possibile farci l'hack lo teniamo , tanto il negozio lo aveva valutato circa 120 euro ,  quindi possiamo anche tenerlo, ti scrivo qui le caratteristiche:

     

    9600k

    Z390 - i rog strix gaming

    16gb ddr 4

    nvme da 500gb , a questo punto se questa configurazione và bene uso quello che ho in questo pc 

    rx 570 8gb bi ventola ... non ricordo il modello esatto

     

    Sì fattibilissimo! Anche Sonoma

    • Thanks 1

    [Guide]VirtualBox on Sonoma and AMD Hackintosh

    in Guide

    Posted

    Virtualization on AMD based Hackintosh on Sonoma real hardware... possible!
     
    The key program is Virtualbox 6.1.46 or its minor latest updates + related USB 3 extensions, where the code to support AMD-V/SVM are still present. VirtualBox 7 is not ok because it only works with VT-X/VT-D owned only by Intel CPUs now, nobody created a wrapper yet.
     
    But how can we get Virtualbox running on recent macOS? The prerequisite is to disable SIP and use the AMFIpass.kext with the bootflag -amfipassbeta in order to allow VirtualBox kexts to be loaded once installed, nothing more. In fact, once rebooted and allowed the kexts to run in Security section you can even disable the loading of AMFIpass.kext and remove the related bootflag, by now the kexts have bypassed the blacklist, forever!
     
    After that you can also install Windows 11 as a VM, direct without any issue, and the performance is also great if you don't overdo the number of cores (my maximum is 2 then it starts to slow down)!!!
     
    Me and @fabiosun have also experimented with various macOS: all of them work with the original ISO/DMGs starting from Tiger Server to Monterey... probably Ventura and Sonoma need an updated bootloader than the internal EFI one (which I'd like to understand what it is because it even performs better than clover and OC imho).
     
    Let's go through all the attempts made with the various macOS, as there is often a need for CPU spoofing since we have an AMD based host. For all Apple VMs the GPU will be emulated in EFI and should be set with 128Mb or where possible 256Mb RAM.

     

    Starting from Mojave till Monterey use the Mac OS X 64 bit template. Don't give more than 2 virtual CPUs to the VM or it will slow down. Set in Ports, USB -> USB 3.0 Controller (xHCI), hence the need to have VBox extensions installed. Set everything as per the screenshots where I do not specify anything else.

     

    image.thumb.png.8e06460cb76ee4b4e338b1829dc19e66.png

     

    image.thumb.png.9450726815440dfbec0cad926fdaf390.png

     

    image.thumb.png.f9f6ca105491ff2c42c8c0232816a8a5.png

     

    image.thumb.png.485b0778bb35e2f415d10c4e824d7323.png

     

    image.thumb.png.fbbe7d434b6fd83533ae47c86e707194.png

     

    image.thumb.png.15fa9d490605e24b43ee76b5136e1cc6.png

     

    image.thumb.png.f596fbe0e907cba2589e2ddce618ee8c.png

     

    image.thumb.png.cc1fb2a2ace69be0f29423dbd82e4b75.png

     

    image.thumb.png.3ebb8910dfbbb976cb7f100eaec5374f.png

     

    image.thumb.png.59072ac79cf5c0e7fff603e69c11b83b.png

     

    With Tiger, I was only able to start the installation via Tiger Server 10.4.7 since the previous stock kernels do not work even with spoof. If we create the virtual machine with the name Tigro, the following commands are needed to start the installation, after selecting Mac OS X and Mac OS X 32 bit as Guest OS. Also set ICH6 as the controller for the disks, IDE. It is mandatory to choose only one CPU as processor otherwise we will have a panic:

      

    tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion EFI32..Virtual.Box                                           
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro VBoxInternal/Devices/efi/0/Config/DmiSystemProduct "MacBookPro3,1"                                            
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663"  
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro VBoxInternal/Devices/efi/0/Config/DmiUseHostInfo 0   
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Tigro --cpu-profile 'Intel Pentium 4 3.00GHz'
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Tigro --cpuidset 00000000 00000004 756e6547 6c65746e 49656e69         
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Tigro --cpuidset 00000001 00000f43 00020800 fbffffff ffffffff
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Tigro --cpuidset 80000001 00000000 00000000 ffffffff ffffffff
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro VBoxInternal/Devices/smc/0/Config/DeviceKey "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC 1   
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Tigro VBoxInternal2/EfiGraphicsResolution 1280x800

     

    The startup speed is impressive! Here it is as I am upgrading the operating system to 10.4.11:

     

    image.thumb.png.95a8407e488628067c7508aa0387019d.png

     

    For Snow Leopard select Mac OS X and Mac OS X 64-bit Snow Leopard, always one CPU. I used a retail installation DVD version 10.6.7 in ISO format. Startup always lightning fast! These are the commands by calling Snow the VM:

      

    tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Snow --cpu-profile "Intel Xeon X5482 3.20GHz"    
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Snow --cpuidset 00000000 00000004 756e6547 6c65746e 49656e69     
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Snow --cpuidset 00000001 00000f43 00020800 fbffffff ffffffff  
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Snow --cpuidset 80000001 00000000 00000000 ffffffff ffffffff     
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Snow VBoxInternal2/EfiGraphicsResolution 1280x800

     

    image.thumb.png.324c27b7a83f8e5967b517bbd8cdde4d.png

     

    @fabiosun reports to me that the lines with cpuid definitions are redundant. You can omit them!

     

    For El Capitan always create a virtual machine by choosing Mac OS X 64 bit El Capitan from the templates, only strings to enter by hand, assuming you have named it ElCap:

      

    tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm ElCap --cpu-profile "Intel Xeon X5482 3.20GHz"                                                                    
tomnic@MacProAMD ~ % /Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata ElCap VBoxInternal2/EfiGraphicsResolution 1280x800

     

    To create the iso I used the script https://gist.github.com/coolaj86/8c36d132250163011c83bad8284975ee. Place script and downloadable file directly from Apple InstallMacOSX.dmg in your home, give chmod +x to the script and run it. You will always get the el-capitan.iso file in your home ready for installation.

     

    Note that you can also use 2 CPUs this time, increasing the number as well as slowing down the boot may generate panic so watch out.

     

    image.thumb.png.522b33644196b191d0f7d985dc085e67.png

     

    For other versions of Mac OS X we will have to create the bootable media suitable for VBox ourselves.

     

    For Mavericks after downloading from the App Store and copying Install Mac OS Mavericks to the Applications folder we need to create a temporary 8 Gb blank volume using disk utility, File, New Image, Blank Image:

     

    image.thumb.png.8e5772145ccc1f812c0dbb6591482c1f.png

     

    The command to create the bootable media is:

      

    sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/Mavericks --applicationpath /Applications/Install\ OS\ X\ Mavericks.app --nointeraction

     

    We must then convert it to a disk image for VBox because an ISO would return an error since the Mavericks installation app must reside on a medium where it can also be written to:

      

    /Applications/VirtualBox.app/Contents/MacOS/VBoxManage convertdd ~/Desktop/Mavericks.dmg ~/Desktop/Mavericks.vdi

     

    Now the commands to be able to run the VM, named Mav, are:

      

    /Applications/VirtualBox.app/Contents/MacOS/VBoxManage modifyvm Mav --cpu-profile "Intel Xeon X5482 3.20GHz"  
/Applications/VirtualBox.app/Contents/MacOS/VBoxManage setextradata Mav VBoxInternal2/EfiGraphicsResolution 1280x800

     

    Create a Mac OS X 64 bit Mavericks VM, you can also use 2 CPUs, add among the storage devices a Hard Disk and give it the Mavericks.vdi image. Bring in Hard Disk as the first boot device. Inside the VM, before partitioning the virtual disk where you will install Mavericks, open Terminal and type:

      

    date 0202020216

     

    Proceed slowly with partitioning and you will have Mavericks installed.

     

    image.thumb.png.05ed2f0a76409616161b539da8638a68.png

     

    For Yosemite proceed similarly, mutatis mutandis. The command for the date is:

      

    date 1020170014

     

    image.thumb.png.38f8b2de22c1f254714ac46274469387.png

     

    From Catalina on up an empty 16384 MB image must be created in disk utility. To get the Installers from High Sierra and up use our blazoned Runme_downloaderV4 which I attach.

     

    The commands to create the bootable and writable installation media are respectively:

      

    sudo /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/HighSierra
sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/Mojave
sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/Catalina
sudo /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/createinstallmedia --volume /Volumes/BigSur
sudo /Applications/Install\ macOS\ Monterey.app/Contents/Resources/createinstallmedia --volume /Volumes/Monterey

     

    ...and to generate the bootable vdi disk:

      

    /Applications/VirtualBox.app/Contents/MacOS/VBoxManage convertdd ~/Desktop/HighSierra.dmg ~/Desktop/HighSierra.vdi   
/Applications/VirtualBox.app/Contents/MacOS/VBoxManage convertdd ~/Desktop/Mojave.dmg ~/Desktop/Mojave.vdi
/Applications/VirtualBox.app/Contents/MacOS/VBoxManage convertdd ~/Desktop/Catalina.dmg ~/Desktop/Catalina.vdi
/Applications/VirtualBox.app/Contents/MacOS/VBoxManage convertdd ~/Desktop/BigSur.dmg ~/Desktop/BigSur.vdi
/Applications/VirtualBox.app/Contents/MacOS/VBoxManage convertdd ~/Desktop/Monterey.dmg ~/Desktop/Monterey.vdi

     

    In particular, to allow, for example, the installation of Big Sur, assuming you have called the VM Mac, the commands to be given are:

      

    /Applications/VirtualBox.app/Contents/macOS/VBoxManage modifyvm mac --cpuidset 00000001 000106e5 00100800 0098e3fd bfebfbff
/Applications/VirtualBox.app/Contents/macOS/VBoxManage modifyvm mac --cpu-profile "Intel Core i7-6700K"
/Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac19,1"
/Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
/Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
/Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1
/Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac “VBoxInternal2/EfiGraphicsResolution 1280x800
/Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac "VBoxInternal/TM/TSCMode" "RealTSCOffset"
/Applications/VirtualBox.app/Contents/macOS/VBoxManage setextradata mac "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-AA95B1DDAB278B95"

     

    image.thumb.png.352fb3aa6656a7c6cdb1242817d4e663.png

     

    The installation of Ventura and Sonoma is under consideration... for now they crash during the second pass of Sealing... I will try loading a generic OpenCore. Stay tuned!

    RunMe_DownloaderV4.zip

    • Like 1
    • Thanks 1
×
×
  • 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.